Task Editor Redo Tab

The Task editor Redo tab appears for activation task types.

Use the Redo tab to define part of your compensation strategy for activation tasks: to redo tasks that are affected by amendments. Complete the compensation strategy for activation tasks on the Undo tab. See "Task Editor Undo Tab" for more information.

Field	Use
Compensation Strategy	Specify the compensation strategy to redo a task when it is affected by an amendment: Select Manual if manual intervention is required at run time. Select Ignore to instruct OSM to skip this task. Select Undo then do to instruct OSM to undo the task and redo the task as two separate transactions. The task is redone using the same request mapping defined on the Request Data tab. Select Redo (amend existing order) to instruct OSM to undo the task and redo the task as a single transaction, sending the oderByValueRequest parameter with the replace command, replacing the original order with the new command. The task is redone using the same request mapping defined on the Request Data tab Select Redo (new order) to instruct OSM to send a new order to the activation system. The new order can be configured with new request mappings.
Use existing request mapping	When Compensation Strategy is set to Redo (new order), the Redo operation uses the same request mapping settings as the original order.
Re-configure request mapping	When Compensation Strategy is set to Redo (new order), you can specify new request mapping settings for the Redo operation. The Task Data area and Service Actions area behave as they do on the Request Data tab. See "Task Editor Request Data Tab" for more information.

Field

Use

Compensation Strategy

Specify the compensation strategy to redo a task when it is affected by an amendment:

Select Manual if manual intervention is required at run time.
Select Ignore to instruct OSM to skip this task.
Select Undo then do to instruct OSM to undo the task and redo the task as two separate transactions. The task is redone using the same request mapping defined on the Request Data tab.
Select Redo (amend existing order) to instruct OSM to undo the task and redo the task as a single transaction, sending the oderByValueRequest parameter with the replace command, replacing the original order with the new command. The task is redone using the same request mapping defined on the Request Data tab
Select Redo (new order) to instruct OSM to send a new order to the activation system. The new order can be configured with new request mappings.

Use existing request mapping

When Compensation Strategy is set to Redo (new order), the Redo operation uses the same request mapping settings as the original order.

Re-configure request mapping

When Compensation Strategy is set to Redo (new order), you can specify new request mapping settings for the Redo operation. The Task Data area and Service Actions area behave as they do on the Request Data tab. See "Task Editor Request Data Tab" for more information.