Online Help for Oracle SOA Suite

2.87 Scope Dialog - General Tab

Use to create an activity that consists of a collection of nested activities that can have their own local variables, fault handlers, compensation handlers, and so on.

For more information about the scope activity, see the Business Process Execution Language for Web Services Specification (for BPEL 1.1) or the Web Services Business Process Execution Language Version 2.0 Specification at http://www.oasis-open.org.

Element Description

Element	Description
Name	Enter a name or accept the default value of `Scopenumber` for a scope activity. This becomes the name for this activity in the designer.
Variable Access Serializable	Select this checkbox for the activity to provide concurrency control in governing access to shared variables. This activity must not be nested, and must be a leaf scope. This checkbox is deselected by default. This checkbox displays in scope activities that support the BPEL 1.1 specification. For example, two concurrent serializable scopes, `S1` and `S2`, access a common set of variables (external to them) for read or write operations. This selection ensures that the results of their behavior are not different if all conflicting activities (read-and-write and write-and-write activities) on any shared variable are conceptually reordered so that either all activities within `S1` are completed before those in `S2`, or vice versa. The mechanisms are used to ensure that serializability is implementation-dependent.
Exit On Standard Fault	Select this checkbox for the process to exit immediately when any BPEL standard fault other than `bpel:joinFailure` reaches the scope. This is similar to encountering an exit activity. This checkbox is deselected by default. If not selected, the process can handle a BPEL standard fault with a fault handler. When this attribute is not specified on a scope activity, it inherits its value from its enclosing scope or process. This checkbox displays in scope and business rule activities that support the BPEL 2.0 specification.

Name

Enter a name or accept the default value of Scopenumber for a scope activity. This becomes the name for this activity in the designer.

Variable Access Serializable

Select this checkbox for the activity to provide concurrency control in governing access to shared variables. This activity must not be nested, and must be a leaf scope. This checkbox is deselected by default. This checkbox displays in scope activities that support the BPEL 1.1 specification. For example, two concurrent serializable scopes, S1 and S2, access a common set of variables (external to them) for read or write operations. This selection ensures that the results of their behavior are not different if all conflicting activities (read-and-write and write-and-write activities) on any shared variable are conceptually reordered so that either all activities within S1 are completed before those in S2, or vice versa. The mechanisms are used to ensure that serializability is implementation-dependent.

Exit On Standard Fault

Select this checkbox for the process to exit immediately when any BPEL standard fault other than bpel:joinFailure reaches the scope. This is similar to encountering an exit activity. This checkbox is deselected by default.

If not selected, the process can handle a BPEL standard fault with a fault handler. When this attribute is not specified on a scope activity, it inherits its value from its enclosing scope or process. This checkbox displays in scope and business rule activities that support the BPEL 2.0 specification.