Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space WDESIGNER and version 24.1
Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptNameexecution_preliminaries
DisableCachingtrue
PageWithExcerptINTERNAL:_designer_excerpts

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

Now the the Depending on which data is required, you can use variables from the Persisted or Local section.
  • Local: Draw a relation between the operation pin to the variable in section Local.
info

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

Go to page Adding Variables for detailed informationYou can do this with any operation: Operations from your data model or the Base Types, as well as operations from imported libraries or connectors.



When the operation has been added to the operations flow, the displayed pins indicate needed object flows.

Tip

Hover over a pin to see the name and the type of the expected object flow.

Pins on the left of the action node indicate needed incoming object flow.

Image Modified

Pins on the right indicate outgoing object flow.

Image Removed

Target pins indicate the target of the operation which is the element to which the operation is to be applied.

Image Added

To provide the necessary input data to the operation,

Image Removed

you need to connect

its pins with

corresponding variables.


Refer to Drawing Object Flow Execution for detailed information about object flows.




Pin Highlighting

DisableCachingtrue

Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptName

local

pin_highlighting

PageWithExcerptINTERNAL:_designer_excerpts

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

You can use the search to narrow down the content of the list.

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.

Image Removed

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 Removed

You can select an object flow to highlight it in blue - in larger models this helps to track the paths more easily.Image Removed

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 you.

Image Removed

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 valid.

Image Removed

White pins indicate that you are trying to connect pins that do not have the same type or multiplicity. The pins are marked in white only when you have reached them with the mouse pointer.

Image Removed

It will be possible to draw a connection to a white pin, but the relation will be invalid and displayed in red.

Image Removed

A pin turns red if a relation cannot be created at all.

Image Removed

For example, you cannot connect a local variable with another local variable, a persisted variable with another persisted variable, or draw a connection to a pin that is already connected.

Special Case: Guard Expressions

Image Removed

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.

Image Removed

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 pin of the operation call to the return object.

_big

Static And Non-Static Operations

Operations can be static or non-static.

Image Added

Static operations are like functions. They have no self context, and thus no target pin - only input, output, and return pins.

Image Added

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.

Image Added

To determine the target of a non-static operation, you can:

  • Jump to the service panel: The needed target is the class where the operation resides in (see screenshot on the left).
  • Hover over the target pin: The type of the expected target is displayed on the execution pane.