Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Multiexcerpt include | ||||||||
---|---|---|---|---|---|---|---|---|
|
Differences of Operations
Image Removed
Operations in a library can be static or non-static operations.
Tip |
---|
Use the execution pane context menu to display the parameter names / pin names. |
Image Removed
- Static operations are like functions. They have no self context, and thus no target pin - only input, output, and return pins.
Image Removed
- Non-static operations provide a self context. When added to the execution pane, they provide a target pin in addition to the parameters. Here, the user should provide the related element.
Image Removed
You have two options to determine the target of a non-static operation:
- Check the 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 execution pane.
Adding Operations
Select the operation you want to use from the service panel. Drag & drop drop the operation to the operations flow in the execution pane. Tip | . | |||||||||||||||
When the operation has been added to the operations flow, 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 element to which the operation is to be applied. |
| Now you need to connect the pins with the corresponding variables.
Depending on which data is required, you can use variables from the Persisted or Local section. |
Info | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Image Removed
- Persisted: Open the list of available persisted variables by using the
Image Removed icon in section Persisted and select the needed variable.
Tip |
---|
Go to page Persisting Data for detailed information about persisted variables. |
Image Removed
Image Removed
When the persisted variable is displayed on the execution pane, draw the necessary object flow to the operation call.
The color of the pins assists you during modeling, see Pin Highlighting for detailed information.
Got to Adding Variables for more information on variables and the difference between persisted and local variables.
Image Modified
Object flows on the execution pane are routed automatically.
You can use the execution pane context menu to change the algorithm of the relation path.
Image Modified
You can also hover over an object flow to highlight it in black.
Pin Highlighting
While dragging the object flow, the color of the pins assists youchanges to assist you with finding matching connection points.
When you start dragging an object flow, all pins of the same type and multiplicity are marked blue. Blue pins indicate that the relation will be validthis pin is a valid target for the object flow. | ||||||
White pins connection points of variables indicate that you are trying to connect pins variables that do not have the same type or multiplicity. The pins are connection point is marked in white only when you have reached them it with the mouse pointer. | ||||||
It will be is possible to draw a connection to a white pin, an object flow to an invalid connection point but the relation will be invalid and displayed in red. | ||||||
| A pin turns red if | a relation an object flow cannot be created at all. |
| For example, you cannot You cannot
| ,
| , or
| is already connected.
Special Case: Guard Expressions
|
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:
|
| 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 diagram pane, section Return is displayed in the execution pane 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:
|