The Scope shape provides a contextual framework for its contents. The first block of a Scope shape is the context block, or body, in which the basic actions of the scope take place; it is analogous to the try block in a try/catch statement. Following the body, the Scope shape may also include one or more exception-handler blocks and a compensation block.
To do this
This property is not used in BizTalk Server and it will be deprecated in the future release.
From the drop-down list, select Default or Custom to specify what type of compensation to perform on the scope.
Isolation Level property
From the drop-down list, select the degree to which data is accessible among concurrent transactions:
Report to Analyst property
Select True if you want to make this shape viewable in the Visual Business Analyst Tool.
From the drop-down list, select True or False to specify whether to retry the transaction if it fails.
From the drop-down list, select True or False to specify whether the scope is synchronized, which guarantees that shared data accessed within the scope will not be written to by a parallel action until the current scope has completed.
Enter an expression to specify the time in seconds until the transaction fails due to inactivity. If you do not want to use a time-out, set the value of this property to 0.
Transaction Identifier property
If this scope is transactional, specify an identifier for the transaction.
Transaction Type property
Specify whether this scope is an atomic transaction, a long-running transaction, or not a transaction. Different properties are available to you depending on the type.