Modeling Execution
Once you have modeled your business process on the diagram pane, you can add execution parts to this process to bring it to life. The execution pane is the place where you make your model executable.
You need to perform two steps to implement executional parts to your model:
Provide all necessary data types and operations for the implementation of your process. These types and operations reside in the Service panel of the BPMN editor.
You can use the Base Types that are provided with the Designer.
You can create other necessary types yourself in the Implementation section.
Refer to Modeling Data Mapping for further information.You can import a library that provides additional types and operations.
Refer to Administrating Libraries for further information.
In the second step, select data types and operations from the Service panel, and add them to your process at the right places.
How this is done will be explained in this chapter.
The execution pane is displayed below the diagram pane. It is shown as soon as you click on one of the BPMN elements:
Creating an Execution Model
The content of the execution pane depends on the BPMN element. For some elements the execution model must be created manually when you want to add execution, for others a default execution diagram is created automatically. Some BPMN elements allow for no execution at all.
Execution Diagram | BPMN Elements | Possible Execution Models | Description |
|---|---|---|---|
No Execution Diagram |
| - | You cannot add execution to the listed BPMN elements. The Add Execution Model button is disabled:  |
Manual Creation |
| On Event | Click Plus to add an execution model:  |
| On Exit | ||
| Get Data | Click Plus next to the name of the existing execution model to create an additional one for Get Data:  | |
Automatic Creation |
| On Event | All listed BPMN elements have an incoming message that is automatically generated to the execution model:  You need to change the type of this incoming message to the actual type of the incoming content. Refer to Adding Variables > Changing the Type for more information on how to do this. |
| On Exit | ||
| On Exit |  | |
 | Decision | The execution model on a gateway decision is a mandatory model that cannot be deleted.  |
All execution models (except for the Decision model) can be deleted with opzion Delete next to the model name.
Contents of the Execution Model
Execution models consist of the following elements and areas:
Nr. | Section | Description |
|---|---|---|
(1) | Operations Flow | Every execution pane contains an empty operations flow with start and end node. |
(2) | Persisted | Variables created in section Persisted are usable in all executions of the BPMN model. |
(3) | Local | Variables created in section Local are only available for use within the current execution. |
(4) | Message | Section Message is shown for all BPMN elements that need to process an incoming message. As per default, the incoming message has type any. To gain access to the data used in your process, you have to apply the correct type from a customized library. |
(5) | Return | For outgoing relations of Exclusive Gateways section Return is displayed, containing the unchangeable variable return of type boolean. |
(6) | Execution Tabs | You can add and delete the execution model of a BPMN element. For each execution model a corresponding tab is displayed at the bottom of the execution pane. The tab name indicates the time of the execution. Possible tabs are:
|
Idea_Management_Example
Click here to download a simple example model that shows what you can do with Lanes and Forms in Scheer PAS Designer. It also contains a configured instance list and shows the usage of trigger events.