Process Developer

Back Next

Scope

BPMN Implementation: Embedded Subprocess

The Scope activity provides a context for a subset of activities. It can contain ault, event, and compensation handling for activities nested within it and can also have a set of defined variables and a correlation set.

A Scope can encompass a logical unit of work, making it manageable to execute, and then, if need be, reverse an activity. For example, if a customer cancels a paid travel reservation, the money must be returned, and the reservation must be canceled without affecting other reservations. By enclosing activities in a Scope, you can create the structure and conditions in which to manage activities as a unit.

Each Scope has a primary activity that can be a complex structured activity.

Required Properties	Optional Properties
Isolated. Refer to Setting Isolated to "Yes" in a Scope	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
	See 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.

To build a Scope:

From the Control Flow
palette, drag an Embedded Subprocess
activity to the Process Editor canvas.

You can add a background color to the embedded subprocess if it is collapsed. Right-mouse click on the embedded subprocess and select Collapse Container. The color property will appear in the Properties view.

In the Properties view, set Isolated to Yes or No.

On the Process Editor canvas, right-mouse click the Scope activity to add declarations, including:

Correlation Set. For more information, see Correlation.

Variable. For more information, see Using Variables.

Participants. For more information, see Using the Participants View.

From the Handlers
palette, add event fault and compensation handlers:

Compensation Handler. For more information, see Compensate and Compensation.

Event Handlers. For more information, see Event Handling.

Termination Handler. For more information, see Using a Termination Handler for a Scope

From the Task
palette, drag activities to the Scope container, and select activity properties.

The following illustration shows a sample scope activity with all handlers displayed.

You can save an activity, or group of activities to the Custom palette for reuse. Because a Scope can be complex, it is a good candidate for reuse. For more information, see Creating a Custom Activity.

XML Syntax

<scope isolated="yes|no"? exitOnStandardFault="yes|no"?
  standard-attributes> 
    standard-elements
    <variables>?
     ...
    </variables>
    <partnerLinks>?
     ...
    </partnerLinks>
    <correlationSets>?
     ...
    </correlationSets>
    <messageExchanges>?
     ...
    </messageExchanges>
    <faultHandlers>?
    ...
    </faultHandlers>
    <compensationHandler>?
    ...
    </compensationHandler>
    <eventHandlers>?
    ...
    </eventHandlers>
    <terminationHandler>?
     ...
    </terminationHandler>
  activity
</scope>

Example:

<scope isolated="no">
    <faultHandler>
     <reply>...</reply>
    </faultHandler>
    <flow>
      <invoke partnerLink="Seller" portType="Sell:Purchasing"
        operation="SyncPurchase"
        inputVariable="sendPO"
        outputVariable="getResponse"/>
      <invoke partnerLink="Shipper" portType="Ship:Orders"
        operation="OrderShipment"
        inputVariable="sendShipOrder"
        outputVariable="shipAck"/>
    </flow>
</scope>

Rename Saved Search

Table of Contents

Process Developer

Process Developer

Scope

Scope