This chapter provides some examples for building workflow processes, for including parallel task branches and how user tasks can lead to a reject.
Workflow module guidelines:
Transitions and sequence flows
Transitions stored in iPIM tables are mapped to sequence flows (arrows) in the diagram, but the mapping isn’t one-to-one in all cases.
These are the common cases of transitions:
Single transition from one task to another task
Two transitions from a Task, one “Accept” and one “Reject”
These are two sequence flows in the diagram, but they are mapped to one transition in database, which means that they will share the same User role, Message, Mailing, Prerequisites and Effects.
Fork & join transitions that have only one task in the branch
These are two sequence flows in the diagram, but they are mapped to one transition in database, which means that they will share the same User role, Message, Mailing, Prerequisites and Effects.
Transition of a “Join Task”
Sequence flow to an “End Event”
This flow doesn’t have any Configurations, Prerequisites or Effects.
Sequence flow that is going to a “Fork Gateway”
This flow doesn’t have any Configurations, Prerequisites or Effects.
Multiple fork and join
One of the cases that is invalid in the workflow module, is that a workflow T1 is forking into two parallel workflows P1 and P2, and another workflow T2 is forking into the same parallel workflows P1 and P2.
This will lead to a generated diagram like this, which is an invalid BPMN diagram:
The correct BPMN diagram should look like this:
And then “P1” & “P1-2” can have the same User role, so the user tasks will go to the same workbox, and the same can be applied to “P2” & “P2-2”.
Common workflow process use-cases
Attribute triggered workflow process without user tasks
In this workflow, we have only one “workflow” that is triggered by an attribute and perform an effect then goes to end, represented in modeler by a “Start Event” and goes to an “End Event”.
Workflow process with two user tasks
In this diagram, we have one “Start Event” and two “User Tasks” and one “End Event”.
Workflow process with one fork and join
This is a diagram that has one “Start Event”, 4 “User Tasks” and an “End event”.
“Task 1” is going to two parallel tasks “Parallel Task 1” & “Parallel Task 2”, and both are joining into “Join Task” and then the diagram ends with an “End Event”.
Workflow process with a reject task
This workflow has one “Start Event” and 3 “User Tasks”.
“Task 1” will go to “Task 2” in case it is accepted, and will go to “Reject Task 3” in case it is rejected.
To Set a transition as “Reject” transition, you should select it and enable the “Reject flow” switch.
