1. Business Process Framework: Task UI Guide
  2. Task Playbar Backward Navigation

Task Playbar Backward Navigation

Clicking the Previous button validates the data in the current view, and then returns to the last displayed view. This feature is most useful if you make a mistake during the task and need to return to an earlier view to correct this mistake. For example, if you enter erroneous data or choose the wrong option. Note the following:

  • Siebel CRM applies the original search and sort specifications to reconstruct the view before displaying it. It also attempts to reinstate the original current record. It does not reinstate original values.

  • The view displays the most current data that the transaction contains. If you modify this data, then Siebel CRM displays these modifications when you navigate back to the target view.

  • You can continue backward navigation until you reach the first view in the task. You can freely cross subtask boundaries.

  • Siebel CRM disables the backward navigation button in the first view of the task.

  • If you use backward navigation, and then make a choice at a decision point that varies from the original choice that you made, then subsequent forward navigation can cause the task to enter a branch in the task that is different from the branch that you first pursued.

For more information, see Disabling Backward Navigation.

Validation with Backward Navigation

Siebel CRM does backward validation in a way that is similar to the validation it does with forward navigation with the following differences:

  • If records are created in the current view in the task transaction, and if the deferred validation option is enabled, then it does not validate the record.

  • If the Defer Write Record property is set to TRUE on an insert step, then it performs deferred validation. For more information, see About the Defer Write Record Property.

  • If the user inserts data in the task transaction, and if Siebel CRM does not validate data before it runs the commit step, then it does not save the data to the Siebel database.

Siebel CRM validates transient data because it is not part of the task transaction. For more information, see Overview of Transient Data.