Home > Properties dialog box - Outputs page - Exceptions tab
Properties dialog box - Outputs page - Exceptions tab
Specifies alternate paths for transaction flow based on exception conditions. To display the Properties dialog box, right-click on a shape and choose Properties. Or, with the shape selected, on the Edit menu, choose Properties.
Element |
Description |
None |
No exception condition is given. If you want to specify an exception, click the drop-down menu and choose an exception type. The exception types are given in the following table cells. |
Timer |
Create and define a Timer-type exception event on an activity. Name – Enter a name for the timer.
Non-interrupting – Indicates that the exception does not interrupt normal flow. A duplicate transaction will be created and sent down the exception flow path. Maximum Time – Set the maximum time since the transaction entered the activity until the exception is triggered. Specify an expression or a numeric value and choose the unit of time. Event – Specify an existing scheduled event. Select from the drop-down list or click the Disable – Specify a point in the activity processing after which the timer is disabled. For example, After Resource indicates that when the transaction leaves the Resources page (after it has acquired Resources), the Timer is to be disabled. If the Timer triggers before Resources are acquired, the Exception path is taken. |
Message |
Choose or Create a Message-type exception event that causes the exception path to be taken when a message is received. Name – Shows the name of the chosen Message (see below).
Non-interrupting – Same as for Timer. Message – All available messages.
Partner – The available entity (swimlane) with which the selected activity exchanges messages. |
Signal |
Choose or create a Signal-type exception event that causes the exception path to be taken when a signal is received. Name – Shows the name of the chosen Signal (see below).
Non-interrupting–Same as for Timer. Signal – All available signals.
|
Fault |
Create and define a Fault-type exception event to catch any faults thrown as a result of the activity execution. Name – Shows the name of the chosen Fault (see below).
Any – Catches any fault, regardless of its name. Fault – All available faults. System-provided faults are <undeliverablemessage> and <Unnamed>. You can use <undeliverablemessage> to catch fault output resulting from a message that cannot be delivered, or specify the <Unnamed> fault for any generic purpose.
Attribute – Appears only when the fault was defined with the ‘Has attribute value’ option. Specify which attribute receives the value of the fault. You may click |
Escalation |
Create and define an Escalation-type exception event to catch any escalations thrown as a result of the activity execution. Name – Shows the name of the chosen Escalation (see below).
Non-interrupting–Same as for Timer. The escalation is non-interrupting by default, as escalations are intended to be like non-interrupting faults. Escalation – All available escalations. System-provided escalation is <Unnamed>. The <Unnamed> escalation may be used for any generic purpose.
Attribute – Appears only when the escalation was defined with the ‘Has attribute value’ option. Specify which attribute receives the value of the escalation. You may click |
Cancel |
Create and define a Cancel-type exception event on an activity that cancels a Business Transaction. Cancel-type exception events can only be specified for a Business Transaction (the shape itself is a Business Transaction or the subprocess it calls is a Business Transaction). Name – Name the Cancellation exception.
|
Compensation |
Create and define a Compensation-type exception event on an activity that specifies a compensating activity to undo an action. Name – Name the compensation exception association line. Note: This name is not used for catching thrown compensations. |
Expression |
Create and define an exception controlled by an expression (conditional). Name – Name the expression exception.
Non-interrupting – Same as for Timer. Expression Field – Specify an expression or click the Evaluation Options – Specify when transactions should take the exception path: Either when the expression becomes true while the activity is executing, or the next time the expression becomes true (when it becomes true after first going false). |
Multiple |
Specify that multiple combinations of the above triggers may, or must, occur when the exception path is taken. Name – Name the Expression exception.
Non-interrupting – Same as for Timer. Edit – Click the Edit button to specify the multiple triggers for the exception. |
Add button |
Click the Add button to add another exception condition. Each exception path defined is independent of other exception paths. |
Delete button |
To delete an exception, click it and then click Delete. |
Related Topics