Changing the Attributes of Elements on the Activity Diagram

Name

Click here to insert or change the Name of the related element. Generated elements (like e.g. message) cannot be renamed.

Element names must follow certain naming rules. They

• must not contain blanks

• must not start with a number

• must not contain special characters

serviceAvailable

All activity diagram elements.

Symbol Type

Attribute Symbol Type displays the graphical type of the current element symbol.

• Activity Decision

• Activity Parameter

• Call Operation

• Control Flow

• Final Node

• Initial Node

• Local Variable

• Object Flow

• Operation Pin

• Throw Exception

All activity diagram elements.

Description

If you want to insert a description for your element, click here to open a text editor where you can enter and format your text:

• Call Operation Actions

• Control Flows

• Object Flows

• Exception Signals

• Throw Exception

Type

Execution elements always have a Type. These can be basic types or user defined types. Users can define their own types in the Implementation folder or in a library. For variables, you can change the type by clicking option Change type and selecting a class from the list of available types.

Base Types.String

• Call Operation Actions

• Local Variables (object nodes)

Direction

Call operation actions have pins that represent their parameters. The Direction specifies whether the pin reflects an input or output parameter.

in

Input pin.

Pins

out

Output pin.

Array

Use the attribute Array to enable multiplicity.

true

The variable has a multiplicity of 0..*.

Local Variables (object nodes)

false

The variable has a multiplicity of 0..1 (default).

Is static

Specify if the operation is static (default) or not.

• Static operations can be called without creating an instance of the related class. They get all necessary data via their input parameters.

• Wanting to call a non-static operation, you need to create a local instance of the related class, and call the operation on that object. This is called self Context.

true

The operation is static (default) and can be used outside the context of the related class.

Call Operation Actions

false

The operation is non-static and needs a self object as an input.

Guard

Control flows that are starting from a decision node need to have a guard expression. A guard expression is an expression that evaluates to true or false, and specifies which control flow branch to follow from the decision node on. One of the guard expressions must be else to define the branch to follow when none of the guard expressions are true.

true

Follow this branch.

Control flows starting from decision node

false

Do not follow this branch.

Order

If a decision node branches the control flow into multiple branches, order defines the order in which the guard expressions (see Guard above) should be evaluated. This is necessary in case multiple guard expressions evaluate to true. The else  expression does not need to have an order.

an integer

Order in which the guard expression on this control flow should be evaluated.

Control flows starting from decision node

empty

Undefined order of evaluation.

Get

The Get attribute extracts the value of a single attribute from a complex type object node respectively output pin, and transports the value to an input pin respectively an object node.

Limitations of Attribute Get

Using the Get attribute it is only possible to access properties of complex types.

The following is not supported:

• Multiple transformation flows to the same input pin.

• Adding Action Script statements to the Get attribute.

• Accessing single array elements, e.g. with myArray[0].

A valid class path e.g. customerAddress.street

Object flows

Stereotype

Use option Add Stereotype to add a stereotype to an action node.

By adding a stereotype, you can extend the attributes of an element with additional properties. For more information, refer to the related adapter pages.

REST Adapter

Call Operation Actions