Designer 10.7 | webMethods BPM Process Development Help | Activity Steps | About Receive Tasks | Advanced Receive Task Properties
 
Advanced Receive Task Properties
The following table describes the advanced receive task properties.
Properties Page
Property
Description
Implementation
Integration Server Name
Assigned Integration Server Name (logical server).
Receive Protocol
Type of receive protocol to use. Select Subscription (For Publishable Documents) (default), JMS (for JMS Triggered Processes), or Simple Service (For Synchronous Receive/Send) from the list.
Note:
The Receive Protocol is not editable in Adapter Notification steps.
Receive Document
The document type to receive.
*Click Browse to open the Choose Document dialog box and locate a service on an Integration Server or in CentraSite.
*Click New to open the Create a New Document Type dialog box and create a new document on a configured Integration Server.
*Click View to open the selected document in a document editor. The View button is available only when a document is specified in the Document field.
Note:
The Receive Document is not editable in Adapter Notification steps.
Note:
Selecting an e-form as the step's Receive Document automatically selects the Enable content repository support check box and enables E-form properties.
Protocol Properties
Available for JMS protocol only.
*Connection Alias. Accept the default PE_NONTRASACTIONAL_ALIAS or click the browse button to select another alias (an Integration Server connection is required). For more information, see Configuring a JMS-Triggered Process.
*Destination Name. Required. You must specify a destination name. Defined by default as: projectName_ProcessName_ SUBQUEUE. To specify another destination name, click the browse button (an Integration Server connection is required).
Subscription Filter
Available for the Subscription (For Publishable Documents) and JMS (For JMS Triggered Processes) protocols only. The instances of a subscription document that can trigger the process. See Working with Subscription Filters.
Generated Service Name
Name of the generated flow service used at run time.
Retry Count
Number of times the Process Engine retries the service in the case of an Integration Server run-time exception. The default value is 0, or no retries.
Note:
The retry mechanism is invoked only when a step service generates an ISRuntimeException error. Any other exception, such as an EXIT with a FAILURE error, causes the step to fail.
Retry Interval
Number of milliseconds (ms) the Process Engine waits between retry attempts in the case of an Integration Server run-time exception. The default value is 60000 ms, or 60 seconds.
Allow Parallel Execution
Lock the step at run-time to allow it to be executed by multiple threads.
Compensating
Places a BPMN compensation marker on the step, indicating that it is used for compensation. This is notational only and has no effect on the behavior of the activity.
E-form
Selecting an e-form as the step's Receive Document automatically selects the Enable content repository support check box and enables E-form properties.
Receive tasks that start processes and those that do not start processes can use e-forms.
For more information on working with e-forms, see Selecting an E-form Content Repository and the PDF publication Implementing E-form Support for BPM.
Important:
Incoming e-form instances must have the correct file name extension (for example, .xml for InfoPath forms, .xdp for LiveCycle forms). Otherwise, they will not trigger the receive task.
Content Repository
Select Browse to specify a My webMethods Server content repository where e-form instances are monitored by the Process Engine listener.
Template Name
Selecting an e-form as the step's Receive Document automatically populates this field.
For more information about using e-forms, see Using E-forms in a Process and .
Logged Fields
Inputs
Input fields to log. Inputs are logged before the step executes. For more information, see Log Inputs and Outputs.
Outputs
Output fields to log. Outputs are logged after the step executes.
Joins
Join Type
A join type defines the logic the process follows when a step has multiple incoming transitions. Options: OR, AND, COMPLEX, or Unsynchronized OR.
Note:
The Joins page is displayed only when a step has more than one incoming transition.
Join Timeout
The timeout duration value, after which this join fails. This option is available for AND and COMPLEX joins only. The source of this value can be:
*A static value that you define.
*A value from a field in the process pipeline. The field value is interpreted in milliseconds.
*A value based on a business calendar in My webMethods Server. You can specify a static number of days, hours, and minutes, or specify a pipeline field to set the day, hours, or minutes value.
For more information, see About Join Timeouts.
Join Condition
Use the join condition editor to define a condition for the gateway join. This option is available only for a complex join in a complex gateway.
When the terms of this condition are met (that is, the condition is true), the join is considered satisfied.
For more information about using the condition editor, see About Complex Join Expressions and Defining a Complex Join Expression.
Deprecated properties (not recommended)
These deprecated properties are not available for unsynchronized OR joins.
Suppress Join Failure
This option is not recommended except in very isolated cases. For more information, see Migrating Process Models with Join Steps to Version 9.7 and Later.
Ignore dead path notification
This option is not recommended except in very isolated cases. For more information, see Migrating Process Models with Join Steps to Version 9.7 and Later.
Correlation
Correlation
Select Not Used, Field, or Service. For more information, see Specifying Correlations.
Related Topics