CancellationScope
This activity allows you to specify an activity for execution and cancellation logic for that activity.
Activity Parameters
The CorrelationScope activity has no parameter that can be provided by manually inserted values or via IN arguments or variables other than the DisplayName, but has two properties manageable in the workflow designer area:
ParametersProperties:
- Body: Specifies the activity for which cancellation logic is provided.
- CancellationHandler: Specifies the activity that is executed in the event of cancellation.
CompensableActivity
This activity defines a unit of work that can be confirmed or compensated after successful completion.
Activity Parameters
The CorrelationScope activity has one parameter that can be provided by manually inserted values or via IN arguments or variables other than the DisplayName, and has four properties manageable in the workflow designer area:
...
- Body: Specifies the return value of the CompensableActivity.
- CompensationHandler: Specifies the activity to be executed when compensating for the Body activity. This handler can be explicitly invoked using the Compensate activity.
- ConfirmationHandler: Specifies the activity to be executed when confirming the Body activity. This handler can be explicitly invoked using the Confirm activity.
- CancellationHandler: Specifies the activity that is executed in the event of cancellation.
Compensate
This activity explicitly invokes the CompensationHandler for an activity contained in a CompensableActivity. If the Compensate activity is not used within the CancellationHandler, CompensationHandler, or ConfirmationHandler of a CompensableActivity, then you must specify the Target property.
The CompensationToken specified by the Target provides a means to explicitly confirm or compensate a CompensableActivity once the Body of the CompensableActivity has successfully completed.
...
The Compensate activity parameters can be provided by manual inserted values or via IN arguments or variables:
Parameters:
- Target (text box editor type) (type: CompensationToken): Specifies the InArgument that contains the CompensationToken for this Compensate activity.CancellationHandler: Specifies the activity that is executed in the event of cancellation.
...
Confirm
This activity explicitly invokes the ConfirmationHandler for an activity contained in a CompensableActivity. If the Confirm activity is not used within the CancellationHandler, CompensationHandler, or ConfirmationHandler of a CompensableActivity, then you must specify the Target property.
The CompensationToken specified by the Target provides a means to explicitly confirm or compensate a CompensableActivity once the Body of the CompensableActivity has successfully completed.
Activity Parameters
The Compensate Confirm activity parameters can be provided by manual inserted values or via IN arguments or variables:
Parameters:
- Target (text box editor type) (type: CompensationToken): Specifies the InArgument that contains the CompensationToken for this Compensate activity.CancellationHandler: Specifies the activity that is executed in the event of cancellation. Confirm activity.
TransactionScope
This activity executes the contained activity in a single transaction. The transaction commits when the Body activity and all other participants in the transaction have completed successfully.
Activity Parameters
The CorrelationScope activity has three parameter that can be provided by manually inserted values or via IN arguments or variables other than the DisplayName, and one property that is only manageable in the workflow designer area:
Parameters:
- AbortInstanceOnTransactionFailure (checkbox control) (type: boolean): Specifies the activity for which cancellation logic is provided.
- IsolationLevel (combobox control) (type: String): Specifies the IsolationLevel for this TransactionScope. The options are:
- Serializable: Volatile data can be read but not modified, and no new data can be added during the transaction.
- RepeatableRead: Volatile data can be read but not modified during the transaction. New data can be added during the transaction.
- ReadCommited: Volatile data cannot be read during the transaction, but can be modified.
- ReadUncommited: Volatile data can be read and modified during the transaction.
- Snapshot: Volatile data can be read. Before a transaction modifies data, it verifies if another transaction has changed the data after it was initially read. If the data has been updated, an error is raised. This allows a transaction to get to the previously committed value of the data.
- Chaos: The pending changes from more highly isolated transactions cannot be overwritten.
- Unspecified: A different isolation level than the one specified is being used, but the level cannot be determined. An exception is thrown if this value is set.
- Timeout (text box editor) (type: Time): Specifies the interval of time (formatted as 00:00:00, which indicates hours:minutes:seconds) that the transaction has to complete. The default value is 1 minute (00:01:00).
Properties:
- Body: Specifies the activity to execute in a single transaction.