Agile Process : webMethods BPM Process Development Help : Activity Steps : About User Tasks : Advanced User Task Properties
Advanced User Task Properties
Properties Page
Property
Description
Implementation
Integration Server Name
Assigned Integration Server Name (logical server).
Task Name
Name of the task. Click the ... button to select from the tasks available in the workspace.
Task Type ID
ID assigned to the task type.
Task Control Set
If a task has available control sets, select the control set you want to use from the drop-down list.
Generated Service Name
Name of the generated flow service used at run time.
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.
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.
Copyright © 2017 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback