Configuring Service Action Requests

You configure service action requests by mapping OSM order header and task data to Activation order header, service action, and global parameters. Additionally, you can define conditional logic to determine when service actions should be added to a work order request.

Note:

See "Modeling ASAP Services" and "Defining Service Action Properties" for more information about creating and configuring service actions.

To configure service action requests:

Associate service actions with the activation task:
1. On the Request Data tab, right-click in the Service Actions area and select Add Service Action.
  
  Note:
  
  Service actions for IP Service Activator are available in reference Design Studio IP Service Activator projects or are generated by Design Studio when a CTM template is imported into an Activation IPSA project. See "About CTM Templates" for more information.
2. Right-click the service action to either change the sequence of service actions, open them in the Service Action editor, or remove them from the task.
(Optional) Define new global parameters.

You can define service actions as global parameters to avoid mapping the parameter multiple times:
1. In the Request Data tab, right-click in the Service Actions area and select Add Global Parameters.
  
  The Add Global Parameter dialog box is displayed.
2. In the Name field, select the desired parameter, enter the value, and click OK.
Map OSM data to Activation order header, service action, and global scalar parameters:

Note:

For details about mapping and optionally transforming OSM data to service action XML parameters, see "Mapping OSM Data to Service Action XML Parameters."
1. In the Request Data tab Task Data area, select Order Header or Task Data.
  
  Depending on your selection, the fixed order header data or the task data defined for the activation task is displayed in the Task Data area.
2. In the Service Actions area, expand the Activation Order Headers folder, the Global Parameters folder, or any service action folder to display the parameters.
  
  Required service action parameters are displayed with an asterisk after the parameter name.
3. Drag an OSM order header or a task data node onto an Activation order header, service action, or global parameter.
  
  A check mark appears next to the parameter to indicate that it is mapped to OSM data. Right-click the parameter and select Properties to review the mapping information, default value, and condition expression, depending on the parameter.
  
  Note:
  
  To automatically build XPath expressions, press and hold the Alt key, then drag OSM data from the Task Data area to the Properties view Binding field. Constants or default values must be enclosed within apostrophes (' ').
(Optional) Automatically map task data to global parameters:
1. In the Request Data tab Task Data area, select Task Data.
2. In the Task Data area, right-click a data structure and select Auto map parameter.
Design Studio automatically maps the data structure, including its child elements, to a global parameter of the same name (case sensitive).
Define conditional logic for service actions and parameters.

You define conditional logic (as an XPath expression) to determine when to include a service action on a work order request. See "Properties Service Action Binding View" for more information.
Add service action parameters to OSM task data.

You can add all parameters of a service action to a selected OSM data structure. Service action parameters are not added to the structure if it contains a child element with the same name as the parameter. See "Task Editor Request Data Tab" for more information.

Note:

Design Studio limits the maximum length of service action parameters to 1000 characters when adding them to a structure. If you create data elements for service action parameter fields manually (using the Data Schema editor), ensure that you set the maximum length of the new data element equal to the maximum length defined for the service action parameter.