Properties Page | Property | Description |
Implementation | Integration Server Name | Assigned Integration Server Name (logical server). |
Type | The type of process to be invoked. Choose BPMN Callable Process (default) or webMethods Referenced Process (Deprecated). Note: The ability to invoke a webMethods referenced process from a call activity step is deprecated. You are advised to implement all call activity step invocations with a callable process. | |
BPMN Callable Process | Click the Browse button in the Process Name/Process ID area to select a statically-invoked BPMN callable process. Designer populates the Process Name and Process ID fields in the call activity. For more information, see Call Activity Concepts. | |
webMethods Referenced Process (Deprecated) | Click the Browse button in the Process Name/Process ID area to select a statically-invoked webMethods referenced process. Designer populates the Process Name and Process ID fields. For more information, see Call Activity Concepts. | |
Allow this step to dynamically invoke one or more processes at run time | Select the check box to invoke one or more processes dynamically.  If the Type selection is BPMN Callable Process, only callable processes can be invoked.If the Type selection is webMethods Referenced Process (Deprecated), only webMethods referenced processes can be invoked.For more information about dynamically invoking process in general, see About Dynamically-Invoked Processes. | |
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. This field is not displayed when configuring a dynamic referenced process. 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. This field is not displayed when configuring a dynamic referenced process. | |
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. | |
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. See About Joins. 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. | ||
Start / Return Documents | Available Input Documents | From the Available Input Documents list, select an input document. Use the Add >> and Remove << buttons to move it to the Document Inputs list. |
Document Inputs | This becomes the Start Document for the referenced process. | |
Available Output Documents | From the Available Output Documents list, select an output document. Use the Add >> and Remove << buttons to move it to the Document Outputs list. | |
Document Outputs | This becomes the Return Document for the referenced process. | |
Loop | Loop Expression | Define the loop expression using the table and provided operators. For more information, see Configuring a Call Activity Standard
Loop. |
Test Loop Expression | Select one of the following options to define if the loop expression is evaluated before the step activity begins, or after the step activity completes: before activity or after activity | |
Maximum Loop Count | Set the maximum number of loop iterations using a static value or a field. |