Force-Complete Exception Handling Pattern
The following table highlights some important facts about the Force-Complete Exception Handling Pattern:
|
Signature |
Force-Complete Exception Handling Pattern |
|
Classification |
Exception Pattern |
|
Intent |
The intention is to complete the process, when the timer expires. |
|
Motivation |
To implement an Exception Handling Pattern that will forcefully end the process when the deadline/timer expires. |
|
Applicability |
The token is assigned to an activity. When the timeout exception occurs, the process flow from the Boundary Catch Timer Event to the Message End Event of the process. |
|
Implementation |
Check the process state diagram. It has a sequence flowing from TBE to message G & H (Message End Events). This sequence shows the process flows when timeout happens at the TBE. If the TBE is a noninterrupting timer, the process instance reaches a Message End Event when the timer expires. The token again reaches the activity (human task); however... |
