Category: Transaction
This activity groups all its child activities together, and makes them appear as a single atomic activity to the rest of the workflow.All changes made to the properties of any execution node during the transaction are visible outside the transaction only after the transaction has been committed i. But they are visible immediately within the transaction .Any suspend or terminate operation on the instance will wait for the transaction to be committed, as if all the child activities inside the transaction activity were together a single atomic activity .The transaction is committed automatically when the End transaction activity executes.
Properties
| Name | Description | Mandatory | Initial Value | Runtime Expression | Type | Conditional | |
|---|---|---|---|---|---|---|---|
| NodeType | Contains the type for node | No | No | No | Output | No | |
| Data Type: Text | Comments: | ||||||
| Name | Name of the workflow node | Yes | Yes | No | Input | No | |
| Data Type: Text | Comments: | ||||||
| Description | Description of the workflow node | No | Yes | No | Input | No | |
| Data Type: Text | Comments: | ||||||
| Committed | Contains true if the last execution of the activity was successfully committed, else contains false, e.g. if execution is in progress, or there was an exception that threw flow control out of the transaction before its end transaction activity could be executed. | No | No | No | Output | No | |
| Data Type: Boolean | Comments: | ||||||
| LogData | Any string to output to the workflow log | No | No | No | Input | No | |
| Data Type: Text | Comments: | ||||||
Comments
0 comments
Please sign in to leave a comment.