Designer 10.7 | webMethods BPM Process Development Help | Activity Steps | About Subprocesses | Advanced Subprocess Properties
 
Advanced Subprocess Properties
The following table describes the advanced subprocess properties.
Properties Page
Property
Description
Implementation
Integration Server Name
Assigned Integration Server Name (logical server).
Type: webMethods Subprocess (Deprecated)
Click this option to specify that the subprocess is a webMethods subprocess type. This is the default setting when a subprocess is imported from an earlier version. This subprocess type is deprecated. For more information, see Recommendations On Changing the Subprocess Type.
Type: BPMN Subprocess
Click this option to specify that the subprocess is a BPMN subprocess type. This is the default setting when a subprocess is added to the process. For more information, see Recommendations On Changing the Subprocess Type.
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.
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.
Loop
Loop Expression
Define the loop expression using the table and provided operators.
For more information about configuring standard looping, see Configuring a Subprocess 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 loops using a static value or a field.
Related Topics