TransactedReceiveScope Activity Designer
The TransactedReceiveScope designer is used to create and configure a TransactedReceiveScope activity.
The TransactedReceiveScope Activity
The TransactedReceiveScope activity enables you to flow a transaction into server transactions created by a workflow or dispatcher.
Using the TransactedReceiveScope Activity Designer
Access the TransactedReceiveScope activity designer in the Messaging category of the Toolbox. The TransactedReceiveScope activity designer can be dragged from the Toolbox and dropped on to the Workflow Designer surface wherever activities are usually placed. This creates a TransactedReceiveScope activity with a default DisplayName of TransactedReceiveScope. The DisplayName can be edited in the header of the TransactedReceiveScope activity designer or in the DisplayName box of the property grid.
The TransactedReceiveScope designer contains Request and Body boxes. These are used to configure the Request property, which specifies a Receive activity and a Body property, which specifies some other Activity. The Request creates a transaction. The transaction then is made ambient for the scope of the Body so that any activity within this scope executes inside this transaction.
The TransactedReceiveScope Properties
The following table shows the TransactedReceiveScope properties and describes how they are used in the designer. These DisplayName property can be edited in property grid or on the Workflow Designer surface, but the others must be edited on the design surface.
| Property Name | Required | Usage |
|---|---|---|
| DisplayName | False | The optional friendly name of the TransactedReceiveScope activity. The default is TransactedReceiveScope. Although the DisplayName name is not strictly required, it is a best practice to use a display name. |
| Request | True | Drops a Receive activity into the Request block on the activity designer surface. |
| Body | False | Drops an Activity into the Body block on the activity designer surface. |