Task Playbar Validation with Forward Navigation
If a user clicks the forward navigation button, then Siebel CRM validates the data that the current view displays and then does the required logic. The following table describes validation for forward navigation and validation results.
Validation | Validation Result |
---|---|
A validation error occurs. |
An error message appears, forward navigation stops, and the user can fix the data. |
Siebel CRM successfully validates data in the current view. |
Siebel CRM follows the flow in the task, running task steps until it reaches the next view step or the next end step. |
An exception occurs that Siebel CRM does not handle. |
Siebel CRM stops forward navigation and displays the error message. It then returns control to the user in the same view where the user started forward navigation. |
Forward play of the task successfully arrives at the next task view step. |
Siebel CRM applies the task context that is associated with this step to the business component, and then displays the associated view. |
Labels for the Forward Button
You can modify the Forward Button Type property on the task step to modify the label for the forward button. The label does not modify the behavior of the task. It is a hint that provides the user with an indication of what happens when the user clicks the forward button. The label can include one of the following values:
-
Next. Used by default if the Forward Button Type property is empty and if the task includes more than one view. If the task includes only one view, then the default value is Submit.
-
Submit. Indicates that Siebel CRM is about to save transaction data for the task to the Siebel database for enterprise-wide consumption. After saving transaction data, roll back is not possible. This situation typically occurs at the end of the task. For tasks that include a commit step, the Submit button appears in the last task view that appears before the commit step.
-
Finish. Indicates that clicking the forward navigation button ends the task. You can use it only in a task where Siebel CRM fully saves the task transaction before it displays the last summary view. This situation also applies to a task that does not use a task transaction, but instead interacts directly with the Siebel database.