Model BPM|Flow processes
You can create and model BPM|Flow processes in the model overview via the separate Apps | BPM|Flow processes area:
Special features of the modeling of BPM|Flow processes
To successfully transfer a process from Aeneis to BPM|Flow, you must model it as follows:
-
Note that the display name in the swimlanes corresponds to the users or groups of your BPM|Flow system.
-
For each event, activity or gateway, specify by assignment who is responsible for its execution.
-
Assign an Owner, Starter, and Deployer at the start event.
-
Define to which activity the respective events belong.
-
For gateways, model the Yes path first and then the No path.
-
Close loops again on parallel activities.
-
Model at least one start event and one end event.
-
Do not use special characters for gateways.
See also: How processes are generally created and modeled in WebModeller is described in the documentations Create model objects and BPMN diagrams.
See also: For the transfer of Aeneis into the BPM|Flow system you have to parameterize your BPM|Flow process additionally. For all information on the topic, see Parameterize BPM|Flow processes.