Adding Transitions Based on Errors

You can transition based on a specific error that occurs during an execution step. You can then branch the business process based on likely execution errors, such as Command Execution Error or Invalid Token (see Table 3-4. Workflow transition errors). As you add a transition, select Specific Error option in the Define Transition window, and then select the error.

Table 3-4. Workflow transition errors
Transition Option	Meaning
Multiple Return Results	The package level subworkflow receives multiple results from package lines that traversed it.
No consensus	All users of all security groups, or users linked to the workflow step need to vote, and there is no consensus.
No recipients	None of the security groups linked to the workflow step has users linked to it. No user can act on the workflow step.
Timeout	The workflow step times out. Used for executions and decisions.
Invalid token	Invalid token used in the execution.
ORACLE error	Failed PL/SQL execution.
NULL result	No result is returned from the execution.
Invalid integer	Validation includes an invalid value in the Integer field.
Invalid date	Validation includes an invalid value in the Date field.
Command execution error	Execution engine has failed or has a problem.
Invalid Result	Execution or subworkflow has returned a result not included in the validation.
Parent closed	For wf_receive or wf_jump steps, a package line is expecting a message from a request that is cancelled or closed.
Child closed	For wf_receive or wf_jump steps, a request is expecting a message from a package line that is cancelled or closed.
No parent	For wf_receive or wf_jump steps, a package line is expecting a message from a request that has been deleted.
No child	For wf_receive or wf_jump steps, a request is expecting a message from a package line that has been deleted.
Multiple jump results	For wf_jump steps in a package line, different result values were used to transition to the step.