Page History
| Multiexcerpt include | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Differences of Operations
Operations in a library can be static or non-static operations.
| Tip |
|---|
Use the Execution Canvas Context Menu to display the parameter names / pin names. |
- Static operations are like functions. They have no self context, and thus no target pin - only input, output, and return pins.
- Non-static operations provide a self context. When added to the execution canvas, they provide a target pin in addition to the parameters. Here, the user should provide the related object.
You have two options to determine the target of a non-static operation:
- Check your library: The needed target is the class where the operation resides in.
- Hover over the target pin: The type of the expected target will be displayed on the canvas.
Adding Operations
| Select the operation you want to use from the library service panel. Drag & drop drop the operation to the action operations flow in the execution canvaspane.
| ||||
| When the operation has been added to the action operations flow of the execution UML, the displayed pins indicate needed object flows.
| ||||
| Pins on the left of the action node indicate needed incoming object flow. | ||||
| Pins on the right indicate outgoing object flow. | ||||
| Target pins indicate the target of the operation which is the object to which the operation is to be applied. | |||||
| To provide the necessary input data to the operation, |
| Now you need to connect | the its pins with | the corresponding objects. Depending on which data is required, you can use objects from the Persisted or Local section.corresponding variables. |
Pin Highlighting
| Multiexcerpt include | |||
|---|---|---|---|
|
|
|
- Persisted: Open the list of available persisted objects by using the
icon in section Persisted and select the needed object.
| Tip |
|---|
Page Persisting Data contains detailed information about persisted objects. |
While dragging the object flow, the color of the pins assists you:
- Unavailable pins are highlighted in red.
- All valid pins are highlighted in blue.
Object flows on the execution canvas are routed automatically and cannot be changed.
Nevertheless you can select an object flow to highlight it in blue - in larger models this helps to track the paths more easily.
You can also hover over an object flow to highlight it in black.
Special Case: Guard Expressions
Guard expressions (conditions) of exclusive gateways are implemented to the outgoing relations of the gateway.
If you select the outgoing relation of an exclusive gateway on the BPMN canvas, section Return is displayed in the execution canvas automatically. This section contains the unchangeable object return of type Boolean.
Operations that should be able to be used on a guard need to have a Boolean return value. This value should transport the following meaning:
- true if the process flow should be continued on this branch.
- false if this branch should be omitted.
Set the return value of the guard expression by connecting the output of the operation to the return object.
|
Static And Non-Static Operations
Operations can be static or non-static.
| Static operations are like functions. They have no self context, and thus no target pin - only input, output, and return pins. |
| Non-static operations are related to a specific type. When added to the execution pane, they provide a target pin in addition to the parameters. Here, the user must provide an object of the related type. |
| To determine the target of a non-static operation, you can:
|
| Panel | ||
|---|---|---|
| ||
|
| Panel | ||
|---|---|---|
| ||
| Otp | ||||
|---|---|---|---|---|
|
| Rp |
|---|
Overview
Content Tools