Modifying Disposition Tasks for a Strategy Branch

Procedure

You can modify any information for a strategy at any time. However, if the strategy is associated with a segment as a Champion or Challenger strategy, when comparing effectiveness metrics, select dates so that you are not mixing effectiveness metrics for the period before and after the changes were made.

To modify autonomous tasks for a strategy branch:

  1. Select Admin.
    The Admin Home Page appears.

  2. From the Policy Administration tab, select Strategy Setup.
    The Strategies screen appears.

  3. Select view/edit in the row for the strategy for which you want to modify a disposition task.
    The Strategy Definition screen appears.

  4. In the Branches section, select view/edit in the row for the branch that has the autonomous task you want to modify. The Task Type column lists Auto for autonomous tasks.
    The Branch Definition screen appears.

  5. In the Tasks section, click view/edit in the row for the Disposition task.
    The Task Definition screen appears.

  6. Change information for the task, such as the task name, the number of offset days, and the priority for the task. For a disposition task, the priority is only relevant if the task will ever be converted to an action item in a collector's Work Queue, such as when Error Notification is set to Yes.

  7. For Disposition Tasks, you must also select one of the following for the Action Type:

    • Halt: The strategy stops as the final task. Any tasks in the collector's Work Queue that were created by the strategy execution are cleared. The strategy can resume in response to system events.

    • Pause: The strategy is inactive as the final task. Any tasks in the collector's Work Queue that were created by the strategy execution remain, and the strategy can resume in response to system events.

    • Escalate: This action halts the strategy as the final task, and places an item in the collector’s Work Queue notifying them that the strategy has terminated. No other new action items are generated.

    • Start Branch: The specified branch executes as a final task in the branch. Any tasks in a collector's Work Queue that were already created by the strategy execution are cleared, and the control date for the start branch is set. Autonomous tasks for the start branch are executed, and interactive tasks are added to the work queue.

    • No Action: The strategy does nothing as a final task for the branch.

  1. You can select on of the following for Schedule Mode:

    • Opportunistic (the task executes as soon as its due date is reached)

    • Sequenced (the task executes when its due date is reached and when all tasks with previous due dates have executed)

    • Dependent (the task executes when its due date is reached, and another, specified task in the branch has executed)

  1. Select Yes or No for Error Notification:When an Auto task fails,if you want users to receive an action item, select Yes for Error Notification.

  2. Click Save.