An Issue will be split into multiple pathways if there is a splitting gateway in the middle of the Flow, and the tokens will be processed concurrently. However, when one of these tokens reaches a [Terminate End Event], all the other split processes will be aborted forcibly. In other words, a User who can flow an Issue to a [Terminate End Event] is granted permission to cancel all parallel Processes.
1. Overview of Cases where Parallel Splitting is Set
- a. All Steps must be Processed
- Start required Steps concurrently so as to shorten the time required for the entire Process
- b. Single Processing is Sufficient
- When processing parallel Tasks, only one person among a group is required to complete their Task, e.g. grant approval or to discover a solution
- c. Deriving Voluntary Steps
- Deriving work which is not mandatory
- Usually when Steps must be processed in parallel, the separate Issues go to the downstream process after all paths have been integrated at a Join gateway
- Computer Steps with no dependencies will be processed in parallel often
- In the cases where single processing is sufficient (first come, first served) the processes of other Users must be terminated when the processing of one Task is complete
- Agent action can be referred to as a "Single Processing is Sufficient" situation in which one of multiple people correspond in a coordinated manner
- Proxy action is essentially processing by a particular person. (The proxy is responsible in the absence of the principal.)
- In many cases, a workflow platform does not detect changing to the proxy, therefore, the settings of the proxy will be similar to the settings of the agent
2. Overview of Cases where Parallel Processing will be Terminated
- a. Termination by Human Judgement
- Soliciting advice from colleagues, detection of failures by computer, etc.
- b. Termination by Elapsed Time
- Checking typos at the time of publishing web pages, computer processing, etc.
- c. Termination by Dependency
- Multiple approvers, reminders and payment confirmation, etc.
- If it is a Human Task, it will disappear from [My Tasks] where it has been displaying
- When using the same process, such as with multiple approvers, using the [Team Swimlane] is also useful (M212)
- 2013-02-12 (Proxy Approval Request for Decision Flow): Request for decision Workflow, How to Design a 'Proxy Approval'
- 2015-03-30 Template Registration flow: Efficiency by 'Template Sentence'
- 2015-03-09 (Marketing Project Planning flow): Pump Up the "Approval Force"(?), A Mysterious Business Processes