Assigned Integration Server Name (logical server).

The type of process to be invoked. Choose BPMN Callable Process (default) or webMethods Referenced Process (Deprecated).

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.

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.

Select the check box to invoke one or more processes dynamically.

For more information about dynamically invoking process in general, see About Dynamically-Invoked Processes.

Name of the generated flow service used at run time.

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.

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.

Lock the step at run-time to allow it to be executed by multiple threads.

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.

Input fields to log. Inputs are logged before the step executes. For more information, see Log Inputs and Outputs.

Output fields to log. Outputs are logged after the step executes.

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.

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:

For more information, see About Join Timeouts.

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.

These deprecated properties are not available for unsynchronized OR joins.

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.

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.

From the Available Input Documents list, select an input document. Use the Add >> and Remove << buttons to move it to the Document Inputs list.

This becomes the Start Document for the referenced process.

From the Available Output Documents list, select an output document. Use the Add >> and Remove << buttons to move it to the Document Outputs list.

This becomes the Return Document for the referenced process.

Define the loop expression using the table and provided operators.

For more information, see Configuring a Call Activity Standard Loop.

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

Set the maximum number of loop iterations using a static value or a field.