Process Developer

Back Next

Break

BPMN Implementation: Terminate throw event

This is a Process Developer extension activity. When you save the process, a message appears informing you that the process contains an activity that is not in the BPEL specification.

By default, the break activity exits the nearest enclosing scope, while, or

forEach

activity. You can use a break inside a container to break out of processing.

When a break executes, control is transferred to the target of the break activity. The target does not execute any further iterations and completes normally. When multiple scope, while, or

forEach

activities are nested within each other, a break activity applies only to the innermost activity. In the case of a parallel

forEach

, the break activity causes all of the executing iterations to terminate all of their executing child activities and complete normally. The break activity allows the root scope of a

forEach

to complete normally so that it is compensatable. Early termination through a break activity is not considered a faulting state, and therefore does not prevent compensation.

Note that you can set the BPMN Terminate property to No to change the behavior of the break to break out of loops (while, for Each and repeat until), but not scopes.

You can use a break to exit normally instead of throwing a fault and forcing termination of the process.

Required Properties	Optional Properties
none	Name. See Selecting Activity Labels
	Join Condition. See Creating a Join Condition for an Incoming Link
	Suppress Join Failure. See Process Properties
	Comment. See Adding Comments to a Process
	Documentation. See Adding Documentation to a Process
	Setting Visual Properties and Using Your Own Library of Images
	Execution State. See Viewing the Execution State of an Activity or Link
	Extension Attributes and Extension Elements. See Declaring Extension Elements and Attributes.
	BPMN Terminate. If set to Yes (the default), stops execution out to the nearest scope, while loop or for-each loop, whichever comes first. Repeat-until loops are skipped, since they are not represented with a boundary (like a scope) and BPMN terminate does not see it as a loop. The scope or loop is considered to have completed successfully (same as throwing a fault and then catching it). If set to No, breaks out of loops (while, for Each and repeat until), but not scopes.

To add a break activity:

On the Process Editor canvas, select a scope, while, or

forEach

container.

Drag a Terminate throw event
to it.

The following illustration shows an example.

XML Syntax

<break standard-attributes>
   standard-elements
</break>

Example

<while>
   <targets><target linkName="Link2"/></targets>
   <sources><source linkName="Link5"/></sources>
   <condition>($counter &lt; 5)</condition>
   <flow>
     <links>
       <link name="Link5"/>
     </links>
     <if>
        <sources><source linkName="Link5"/></sources>
        <condition>($counter = 3)</condition>
       <extensionActivity>
         ext:break name="Break"/>
       </extensionActivity>
     </if>
     <assign>
        <targets><target linkName="Link5"/></targets>
        <copy>
            <from>($counter + 1)</from>
            <to variable="counter"/>
        </copy>
     </assign>
   </flow>
</while>

BPMN Tasks and Events

Download Guide

Watch

Comments

Cloud Application Integration Homepage