'Remand' is assumed if correction needed for approval flows such as Business travel, Expense Reimbursement, Procurement, Decision making, and application flow of Personnel or Labor. In the other hand, there are operations that do not needed 'Remand', such as shipping procedure, etc. Setup 'Remand split' by connecting remand route in Flow Diagram (Workflow Diagram), For processes that need to be assumed to be remand.
Put three 'Swimlanes (long rectangular)', put one 'Task (rounded corner rectangular)' on each swimlane, and name them. Put a 'Start Event (red circle)' on the left end of the first swimlane, put 'End Event (bold red circle)' on the right end of the third swimlane.
Connect those items with arrow (Flow). Task goes only to the direction the arrows show. From [Approval], connect Flow to both of [Application] and [Process] . When it is reverted, it goes to [Application].
Only one Flow comes out from [Application] and [Processing]. There is only one way of going ahead (to end) for the task reached to [Processing], and it cannot be 'reverted'.
Open [Split Condition] setting page. Select the following option of [Split type] to enable to select the destination of the Flow by clicking the button. [The flow moves to the Destination that a user selects. (The number of buttons for executing tasks corresponds with the number of destination)]. Then input the names of buttons according to the destination , to the Condition data field.
In the [Approval] task screen, there are two buttons of [Approve] and [Revert]. After finishing data input, executing person can select the destination of the process depending on the clicked button. On the other hand, Task screen of [Processing], only the [Finish] button is indicated. (Button on the right is the same for both). There it cannot be reverted back.
*It is also possible to setup to revert back with one [Finish] button with setting of Split Condition.
workflow, business process management, saas, bpmn, software
