Task Editor Request Data Tab
The Task editor Request Data tab appears for activation task types.
Use the Request Data tab to configure service action requests by mapping OSM order header and task data to Activation order header, service action, and global parameters.
See the following topics for more information:
Field | Use |
---|---|
Task Data area |
Select one of the following values:
See "Configuring Service Action Requests" for information about mapping. See "Defining Task Data" for information about adding OSM data to the activation task. |
Service Action area |
Displays the request parameters to which you can map OSM data. Expand the Activation Order Headers folder, the Global Parameters folder, or any service action to review the parameters available for mapping. Check marks indicate which parameters are mapped to OSM data. Note: Some Activation order header parameters require default values. Before mapping OSM data to Activation order header parameters, note which parameters are prepopulated with a check mark to determine those that require default values. Right-click in the Service Actions area to access the context menu. The Service Actions area context menu enables you to add service data to a task, define new global parameters, associate additional service actions to the tasks, remove parameters, and remove mapping information. Note: When adding 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. Design Studio limits the maximum length of service action parameters to 1000 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 service action parameter. |