Configuring Actions

To configure actions:

From the Solution view, double-click an Action entity to open the entity in the Action editor.
On the Data Map tab, define the applicability of the data elements to the action.

You can specify whether a data element is required by an action by defining applicability to specific action codes (for service actions) or by defining applicability to specialized aliases defined for the action codes (for technical actions). For example, you can specify whether a data element value must be supplied to or returned by each action in an associated action family.
Click the Data Elements tab and configure the data elements required by the action.

The data elements that have applicability to the action appear on this tab. You cannot add or remove data elements from the Service Action editor Data Elements tab.
Click the Action Codes tab.
(Optional) Add or remove action codes.

Do one of the following:
- For service actions, add or remove action codes. The action codes that initially appear are those defined by the action type (or functional area). For example, when modeling service actions, the action codes default from the Service functional area.
- For technical actions, add or remove action codes and define a corresponding specialized action name that is specific to the application role. The action codes that initially appear are those defined by the action type (or functional area). For example, when modeling technical actions, the action codes default from the Technical functional area.
Note:

You can add only those action codes that are included in the associated functional area. The functional area is specified in the Action Type field.

You can define multiple specialized technical actions against a single action code. Each specialized technical action can define a unique parameter selection on the Data Map tab.
Click the Properties tab.
If the action should inherit the data elements defined for the associated conceptual model entity (the subject of the action), select Extend Subject.
In the Target field, enter the resource or resource facing service that represents an instance of an entity in the network against which the action executes.
In the Key field, enter a value to enable the Order and Service Management order transformation manager to identify order line items of this type at run time.
In the Implementation System field, define the system where the application entity is used.
In the Realization Design Pattern field, select a design pattern to realize the action.

You can create your own design patterns if no patterns are available. See the Design Studio Developer's Guide for more information.
In the Implementation Method field, define how the action realizes.

Service actions realize in Design Studio for ASAP projects as service actions. Technical actions can realize in Design Studio for Inventory projects as rulesets or in Design Studio for Network Integrity projects as scan actions.
If you want to synchronize the action and the realized application entity automatically, select the Run Realization Design Pattern Automatically option.
(Optional) To extend an existing action, click Select in the Extends field.

When you extend one entity from another, the target entity inherits all of the data elements defined for the extended entity. This option is not available if you select the Extend Subject field.
Click Save.