For automation interface information about a Call Operation Action, see
Action node (automation interface). For automation interface purposes, a Call Operation Action is an Action Node that has its Node Type set to Call Operation Action.
A Call Operation Action is an action that transmits an operation call request to the target object, where it may cause the invocation of associated behavior.
Create a Call Operation Action through a Modeler explorer pane or an Activity Diagram:
• In a Modeler pane, right-click an Activity or Structured Activity Node, point to New, point to Action Node, and then click Call Operation Action.
• On an Activity Diagram:
◦ Click the Call Operation Action toolbar button, and then click in free space or inside an Activity Partition, Interruptible Activity Region or Structured Activity Node. You are prompted to select or create the Operation that is used by the Call Operation Action.
◦ Drag the used Operation from a Modeler pane to the Activity Diagram, in free space or inside an Activity Partition, Interruptible Activity Region or Structured Activity Node.
A Call Operation Action's Linked Item is an Operation. On a Call Operation Action, an Input Pin or Output Pin represents the Return Type or a Parameter of the Call Operation Action's Operation:
• If when you create a Call Operation Action you select an Operation that has a Return Type, Modeler creates an Output Pin named after the Operation. The Data Type of the Output Pin is set to the Return Type of the Operation.
• If when you create a Call Operation Action you select an Operation that has Parameters, Modeler creates Input Pins and Output Pins on the Call Operation Action for those Parameters.
Modeler ensures that the name of an Input Pin or Output Pin that represents a Parameter matches the name of its linked item (a Parameter):
• If you change the name of the Input Pin or Output Pin, Modeler changes the name of the linked item to match.
• If you change the name of an Input Pin's or Output Pin's linked item, Modeler changes the name of the Input Pin or Output Pin to match.
Note that a Call Operational Action always has an Input Pin named Target Pin, which does not have a linked item.
When used on an Activity Diagram, a Call Operation Action's notation is as follows.
The View Options on an Activity Diagram allow you to show the name, action type and name of the linked item. The view options are set through the Action Node entry. For more information, see
Action node view options - activity diagram.
On an Activity Diagram, you can double-click a Call Operation Action to open child and associated diagrams of the linked Operation.
On an Activity Diagram, you can populate a Call Operation Action's missing Activity Flows, Input Pins, Output Pins, Comments and Constraints: right-click the Call Operation Action, point to Populate, and then click the appropriate command.
When you create a Call Operation Action you must create or select the Operation that is used by the Call Operation Action. After creating a Call Operation Action you cannot link that Call Operation Action to a different Operation. You can view which Operation is linked to a Call Operation Action through the Call Operation Action's property pages: on the Items tab, select Linked Item.
In the Dictionary pane, Call Operation Actions are listed in the UML\Action Nodes folder.
In the Modeler panes, a short-cut symbol on the Call Operation Action's icon indicates that the item is a stub. For more information, see
Stubs.
For information about creating Input Pins and Output Pins on a Call Operation Action, see
Creating an output pin.
The following sections provide information about how a Call Operation Action is used in the model. For more information about a property, item, model part or diagram, click it.
Properties
In addition to the
standard properties a Call Operation Action has these properties:
• Synchronous (Is Synchronous through the automation interface)
Control Flow - The Control Flow is owned jointly by the Call Operation Action and the associated item. The access permissions you have to a Control Flow are determined by the access permissions you have to its source item.
Dependency - The Dependency is owned jointly by the Call Operation Action and the other associated item. The access permissions you have to a Dependency are determined by the access permissions of the dependent item.
Exception Handler - The Exception Handler is owned jointly by the Call Operation Action and the associated item. The access permissions you have to an Exception Handler are determined by the access permissions you have to its source item.