None

No output behavior defined.

Duplicate

Duplicates the transaction so it can follow each path leaving an activity.

Count – Enter the number of transaction to be created by the duplication.

New Family – Assigns duplicated transactions to a new family.

Note: If the count is not specified (blank), or is 1, no duplication will occur. The ‘New Family’ option will be applied if it is specified.

Duplicate By Member

Duplicates the transaction into a count equal to the number of members of an attribute type. Non-numeric Transaction type attributes and members are required to display attributes and members in the Attribute and Member Names lists.

Each transaction created is assigned a unique member value. The duplicated transactions can later be joined by attribute member.

Attribute – Select an attribute.

New Family – Assigns duplicated transactions to a new family.

Member Names – Displays the members of the selected attribute.

Discard

Discards transactions or all members of a transaction family. Discarded transactions do not leave the activity and do not count as completed in the final report statistics.

Always – The Discard options you choose are Always applied. Uncheck this option to set a condition expression for when the Discard will occur.

Discard Transaction – Discards the transaction.

Discard Family Members – Discards the family members of the transaction.

Only from this process or its subprocesses – Does not discard family members in parent processes.

Unbatch

Unbatches previously batched transactions.

Message

Transaction generates a message to a messaging partner. The message can either trigger an event that causes the process to continue if the event was waiting for the message, or changes the flow for exception handling.

Name – Select a defined message.

– Add, define, delete, or edit messages.

Partner – The shape with which the selected activity exchanges messages.

Signal

Transaction generates a signal. The signal can either trigger an event that causes the process to continue if the event was waiting for the signal, or changes the flow for exception handling.

Name – Select a defined signal.

– Add, define, delete, or edit signals.

Fault

Throws a Fault to a parent process. The transaction generates the fault, which can be caught by an exception in parent process hierarchy.

Always – Throws the fault for all transactions reaching this activity. For example, if credit is not approved, all of the orders from that company are stopped.

Expression – Throws the fault only when the expression is true (Available when Always is not checked).

Name – Choose a defined fault.

– Add, define, delete, or edit faults.

Value – Only displayed when the fault chosen was defined with the ‘Has attribute value’ option. Enter the value associated with the fault when it is thrown.

Escalation

Throws an Escalation. The transaction generates the escalation, which can be caught by an exception. May be non-interrupting.

Always – Throws the escalation for all transactions reaching this activity. For example, if a review condition is not met, a manager is informed.

Expression – Throws the escalation only when the expression is true (Available when Always is not checked).

Name–Choose a defined escalation.

Add, define, delete, or edit escalations.

Value–Only displayed when the escalation chosen was defined with the ‘Has attribute value’ option. Enter the value associated with the escalation when it is thrown.

Cancel

The transaction cancels the Business Transaction that uses this activity.

Compensate

The transaction throws a compensation to any specified or eligible compensating activities, in reverse order of when those activities were completed. May hold the transaction until compensation is complete.

Wait for Completion – Select this option if the transaction will wait for all specified or eligible compensation activities to complete before it completes this shape.

Target – Indicate which activities catch the compensation. You may specify a single shape, or all eligible shapes:

• Choose a shape from the list to compensate a single activity. The list may include shapes ineligible to catch this compensation during simulation.

• Choose <All Eligible> to broadcast the compensation to any shape, with a catching compensation, that the transaction has completed in this Pool (top-level swimlane) and process.

Note: To compensate within a subprocess, you may use a compensation event subprocess in that process, or mark the process itself as Compensable.