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 Elements tab, define the data elements required by the action.

If the related functional area specifies that data elements are inherited by the action family, the data elements defined for the conceptual model entity subject appear in the Data Elements area. By default, service actions inherit all of the data defined on the associated customer facing service. You can also add additional data elements, such as those defined on the entity components or from the Data Dictionary.

Data elements that you define on the action are those that are required only to create the action but that are not required to be persisted during the lifecycle of the service.
Click the Action Codes tab.
(Optional) 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. Service actions usually include multiple action codes. Technical actions usually include a single action code only.

Note:
You can add only those action codes that are included in the associated functional area.
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 Fulfillment Patterns field, click Select.

The Select Fulfillment Pattern dialog box appears.
Select a fulfillment pattern and click OK.

The action is now associated with the selected fulfillment pattern.
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.
(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.
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.
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.
If you want to synchronize the action and the realized application entity automatically, select the Run Realization Design Pattern Automatically option.
Click Save.