Siebel Business Process Framework: Task UI Guide > Task UI Concepts > Language Concepts for Task UI >

Error Handling

You can implement error handling to gracefully intercept and handle processing errors that occur during the execution of a task. The following topics describe how errors are handled in Task UI:

• Handled Errors
• Unhandled Errors during Task Navigation
• Errors during Task Cancellation
• Errors during Task Pause

Handled Errors

Explicit error handling is implemented using a combination of exception branches and error steps. Exception branches may be terminated with an error step. The semantics of the Error step are similar to the default exception handling. When the Error step is executed, the existing error message is replaced with the error message configured for the Error step and returned to the user at the current task view. In this way, the user is presented with a more informative and contextual error message.

Unhandled Errors during Task Navigation

During task execution, if an exception occurs in a task step where no exception branch is defined, a generic error message is displayed to the user in a message box on top of the current task view. After acknowledging the error message, the user may correct the data on the task view or may navigate to a previous task view to correct the data. This is also known as default exception handling.

Errors during Task Cancellation

When the end user clicks Cancel, a dialog box prompts for confirmation, for example:

You are about to delete or undo changes to this task. Click OK to continue.

Errors during Task Pause

There is no exception handling when a task is being paused. If pausing a task fails, the end user receives a standard error message, not a special pause error. The end user can cancel the task, or continue with the task and submit it.