Flow Properties

To view or edit a flow's properties, double-click its diagram symbol or Browser or list entry. The property sheet tabs and fields listed here are those available by default, before any customization of the interface by you or an administrator.

The General tab contains the following properties:

Property

Description

Name/Code/Comment

Identify the object. The name and code are read-only. You can optionally add a comment to provide more detailed information about the object.

Stereotype

Extends the semantics of the object beyond the core UML definition. You can enter a stereotype directly in this field, or add stereotypes to the list by specifying them in an extension file.

Source / Destination

Specify the objects that the flow leads from and to. Use the tools to the right of the list to create, browse for, or view the properties of the currently selected object. You can also open the property sheet of the source and destination objects by clicking the buttons in the top section of the flow property sheet.

Flow type

You can enter your own type of flow in the list, or choose one of the following values:
  • Success - defines a successful flow

  • Timeout - defines the occurrence of a timeout limit

  • Technical error

  • Business error

  • Compensation - defines a compensation flow

The flow type is unavailable if you associate an event with the flow on the Condition tab.

Weight

Specifies the number of objects consumed on each traversal.

Keywords

Provide a way of loosely grouping objects through tagging. To enter multiple keywords, separate them with commas.

Note: You can view input and output flows of a process from its property sheet by clicking the Input Flows and Output Flows sub-tabs of the Dependencies tab.
The following tabs are also available:
  • Parameters - lists the parameters that are passed along the flow. The list is automatically completed if you draw the flow between two activity parameters .
  • Transformation - specifies a data transformation to apply to input tokens. For example, it could extract a single attribute value from an input object.