uCosminexus Service Platform, Basic Development Guide
Flow activities define the division of flow of a business process into multiple sequences and the concurrent execution of these sequences. Flow activities include flow start and flow end activities. Deploy a flow start activity at the starting point of a flow process and a flow end activity at the merging point of multiple sequences.
Of the multiple sequences that branch from the flow start activity and that are executed concurrently, a sequence that ends in a throw activity need not be linked to the flow end activity. In addition, if all sequences that branch from the flow start activity and that are executed concurrently end in throw activities, no need exists to deploy a flow end activity.
The following figure shows the concurrent execution of processes using flow activities.
Figure 5-16 Concurrent execution of processes using flow activities
You can provide multiple sequences under a flow start activity, and execute processes concurrently. You can also specify the processing order among the multiple sequences.
For example, to execute A-3 after processing of A-1 and A-2 finishes, use link connections (link1 and link2) to link the link sources A-1 and A-2 to the link destination A-3. In addition to specifying processing completion of A-1 and A-2, you can also specify linking conditions to control the linking of A-1 and A-2 to A-3.
In this example, processing of the link destination A-3 starts in the following sequence:
Processing of activities following the flow end activity is executed after all multiple sequences being concurrently processed finish.
To define flow activities:
To define links among multiple sequences that are concurrently processed:
Figure 5-17 Processing flow when a link is defined from a flow start activity or switch start activity
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.