Task Editor Compensation Tab

The Task editor Compensation tab appears for Manual, Automated, and Transformation task types.

Use the Compensation tab to define your compensation strategy for Manual and Automated tasks.

Field	Use
When this task needs to be re-evaluated, compensate by:	A task is re-evaluated by the system if it has visibility to order data (data that is defined as significant) that has changed as a result of an order amendment or as a result of amendment compensation performed on another task to which the task has visibility. The default option, which is to redo the task, applies to tasks that are linear in nature and have the same completion status (no branching). Select Redo (one single operation) to instruct the system to perform Undo and Do operations in a single operation. This option is recommended, when possible, as it performs the fewest number of Undo and Do operations necessary for compensation. Select Undo then do (two separate operations) to undo this task and all successor tasks and roll back all order changes, then perform the Do operation again. Use this option to rollback all order changes and re-perform the task from the beginning. Select Do Nothing to instruct the system to bypass updating the affected task. For example, you might select this option if a similar task downstream in the process will be compensated, thereby optimizing the compensation plan. Select Compensation Expression to create an XQuery expression in the Compensation Expression field that dynamically selects a compensation strategy (Redo, Undo then do, or Do nothing) based on revision order data. For more information about compensation strategy XQuery expressions, see "Task Compensation Strategy XQuery Expressions".
When this task is no longer required, compensate by:	A task or subprocess is no longer required when: The order is canceled. When an order is canceled, the system executes an undo on all of the completed tasks and subprocesses and returns the order to the creation task. The tasks and subprocesses associated with the order are no longer required because the order has been canceled. A branch becomes obsolete. A branch becomes obsolete when the redo processing of a particular task or subprocesses causes that task or subprocess to a) exit with a different completion status and b) start a new branch. Because the tasks and subprocesses in the obsolete branch are no longer required, they are undone, one task or subprocess at a time, starting with the last completed task or subprocess in the branch. In both scenarios, the system rolls back the order changes. The difference between them is the creation of a compensation undo task. Undoing the task and rolling back order changes creates an undo task; automatically rolling back order changes does not create an undo task. Undo compensation tasks created for manual tasks appear in the Task Web client Worklists and must be manually acknowledged in order to be rolled back. Select Undo to create an undo read-only task in the Task Web client. Select Do Nothing to instruct the system that no compensation is necessary. Select Compensation Expression to create an XQuery expression in the Compensation Expression field that dynamically selects a compensation strategy (Undo or Do nothing) based on revision order data. For more information about compensation strategy XQuery expressions, see "Task Compensation Strategy XQuery Expressions".

Field

Use

When this task needs to be re-evaluated, compensate by:

A task is re-evaluated by the system if it has visibility to order data (data that is defined as significant) that has changed as a result of an order amendment or as a result of amendment compensation performed on another task to which the task has visibility. The default option, which is to redo the task, applies to tasks that are linear in nature and have the same completion status (no branching).

Select Redo (one single operation) to instruct the system to perform Undo and Do operations in a single operation. This option is recommended, when possible, as it performs the fewest number of Undo and Do operations necessary for compensation.

Select Undo then do (two separate operations) to undo this task and all successor tasks and roll back all order changes, then perform the Do operation again. Use this option to rollback all order changes and re-perform the task from the beginning.

Select Do Nothing to instruct the system to bypass updating the affected task. For example, you might select this option if a similar task downstream in the process will be compensated, thereby optimizing the compensation plan.

Select Compensation Expression to create an XQuery expression in the Compensation Expression field that dynamically selects a compensation strategy (Redo, Undo then do, or Do nothing) based on revision order data. For more information about compensation strategy XQuery expressions, see "Task Compensation Strategy XQuery Expressions".

When this task is no longer required, compensate by:

A task or subprocess is no longer required when:

The order is canceled. When an order is canceled, the system executes an undo on all of the completed tasks and subprocesses and returns the order to the creation task. The tasks and subprocesses associated with the order are no longer required because the order has been canceled.
A branch becomes obsolete. A branch becomes obsolete when the redo processing of a particular task or subprocesses causes that task or subprocess to a) exit with a different completion status and b) start a new branch. Because the tasks and subprocesses in the obsolete branch are no longer required, they are undone, one task or subprocess at a time, starting with the last completed task or subprocess in the branch.

In both scenarios, the system rolls back the order changes. The difference between them is the creation of a compensation undo task. Undoing the task and rolling back order changes creates an undo task; automatically rolling back order changes does not create an undo task. Undo compensation tasks created for manual tasks appear in the Task Web client Worklists and must be manually acknowledged in order to be rolled back.

Select Undo to create an undo read-only task in the Task Web client.

Select Do Nothing to instruct the system that no compensation is necessary.

Select Compensation Expression to create an XQuery expression in the Compensation Expression field that dynamically selects a compensation strategy (Undo or Do nothing) based on revision order data. For more information about compensation strategy XQuery expressions, see "Task Compensation Strategy XQuery Expressions".

Note:

Although compensation strategies are defined on an individual task basis, they must be analyzed within the context of the workflow.