> #### 5.2.3 Workflow control

> The Interstage BPM flow operators control the sequence and timing of activities. Each operator is represented graphically in the Interstage BPM GUI by a distinct symbol, illustrated in the following chart.

> Operator | Symbol | Description | Usage Illustration
> Start Node |  | Identifies the start of the process. Every process must have one and only one Start Node. (See also "Creating and Modifying Process Definitions" and "Create or modify the workflow") |
> Arrow |  | Defines the flow of events. When an arrow originates from an Activity Node, it represents a choice, which the activity assignee can make in response to the activity. (For more information, see "Create or modify the workflow".) | See the other usage illustrations. Note: All arrows have a Name field, but this field has been omitted from the usage illustrations.
> Conditional Node |  | When the workflow reaches this node, the process continues along the arrow, which satisfies the condition specified in the node's Properties dialog. Use this type of node to do automated decision-making for you. When setting up the conditions for this mode, you must also choose a default arrow that will be invoked when none of the defined conditions apply. (For more information, see "Define Conditional Node attributes".) |
> Complex Conditional Node |  | When the workflow reaches this node, the process continues along the arrow, which satisfies the condition specified in the node's Properties dialog. Use this type of node to do automated decision-making for you. When setting up the conditions for this mode, you must also choose a default arrow that will be invoked when none of the defined conditions apply. The only difference between this node and the Conditional Node is that complex conditions can be defined using Expressions. (For more information, see "Define Conditional Node attributes".) |
> OR Node |  | Use an OR Node when you want to respond to any one of several activities. When an event occurs on any incoming arrow, all outgoing arrows convey an event to their target nodes, all of which are activated simultaneously. (For more information, see "Define OR Node attributes.") |
> AND Node |  | When the workflow reaches this node, the process does not continue until all activities, which lead to this node, are completed. Use this node to synchronize two workflow threads in a process. (For more information, see "Define AND Node attributes".) |
> Subprocess Node |  | When the workflow reaches this node, control of the process is passed to a sub process, and the node enters a Waiting-for-Subprocess state. When the sub process completes, control returns to this node, and all ensuing activities connected to the node are activated simultaneously. (For more information, see "Define Subprocess Node attributes".) |
> Remote Subprocess Node |  | When the workflow reaches this node, control of the process instance is passed to a remote sub process instance, and the node enters a Waiting-for-Subprocess state. When the sub process instance completes, control returns to this node. (For more information, see "Define Remote Subprocess Node attributes".) |
> Chained Process Node |  | When the workflow reaches this node, another process instance is activated similarly to a sub process instance. However, the node does not enter a suspended state, and the chained process instance operates as an independent entity. After activating a chained process instance, this node activates all activities connected to it simultaneously. (For more information, see "Define Chained Process Node attributes".) |
> Delay Node |  | When the workflow reaches this node, the process instance pauses until the first timer attached to the node fires. Then the node activates all activities connected to it simultaneously. (For more information, see "Define Delay Node".) | .
> Timers | (no icon) | Timers can be triggered at a specific time, after a time period, or at regular intervals. When a timer expires, Interstage BPM can send mail, evaluate a script, or change assignees. (For more information, see "Define timers".) |
> DB Node |  | Used for the purpose of implementing database Actions. Only database-type Actions should be used with this node. This node has the advantage of giving you a visual representation for your database Actions, so you can tell at a glance that this node is related to database operations. |
> Email Node |  | Used for the purpose of implementing Email Actions. Only Email Actions should be used with this node. This node has the advantage of giving you a visual representation for your Email Actions, so you can tell at a glance that this node is related to Email operations. |
> Exit Node |  | Identifies the end of the process. Every process must have at least one Exit Node. |

Business Process Manager Help-Fujitsu Computer Systems Corporation Interstage Website Voice: (888) 248-9273 Interstage BPM Information