Designer 10.7 | webMethods BPM Process Development Help | Process Engine Processing | Handling Process and Step Errors | About Boundary Event Error Behavior in a Subprocess
 
About Boundary Event Error Behavior in a Subprocess
Boundary error events can be added to tasks within a subprocess, to the subprocess itself, or to both. In general, when a error occurs, it is caught by the boundary error event placed on the step or subprocess where the error occurred. If no boundary error event is present, the subprocess fails and is waiting to be resubmitted.
The following table describes the behavior of subprocess activity step errors in various situations:
An error occurs in a subprocess activity step
The activity step has a boundary error event
The subprocess has a boundary error event
Process has a process error step
Result:
Green check mark
Yes
No
Not applicable
Error is caught by the activity step boundary error event.
Green check mark
Yes
Yes
Not applicable
Error is caught by the activity step boundary error event.
Green check mark
No
Yes
Not applicable
Error is caught by the subprocess boundary error event.
Green check mark
No
No
Yes
The status of the subprocess is set to Failed and the subprocess is waiting for resubmission.
Green check mark
No
No
No
The status of the subprocess is set to Failed and the subprocess is waiting for resubmission.
The following table describes the behavior of subprocess errors in various situations:
A subprocess executes an boundary error event
The subprocess has a boundary error event
Process has a process error step
Result:
Green check mark
Yes
Not applicable
Error is caught by the subprocess boundary error event.
Green check mark
No
Yes
The status of the subprocess is set to Failed and the subprocess is waiting for resubmission.
Green check mark
No
No
The status of the subprocess is set to Failed and the subprocess is waiting for resubmission.
Related Topics