Transaction section
The third section of the DataConnect
task properties form is labeled Transaction.
The purpose of the Transaction section
is to specify the scope of the transaction being processed. The Transaction
setting only applies to the outermost DataConnect task. If a DataConnect
task is nested within another DataConnect task, the first, outer task
specifies the Transaction value. The choices for Transaction are as
follows:
- None
- Indicates that the record created or updated is committed before the DataConnect task processes the tasks inside the body of the DataConnect task, right after the record is created. No transactions are created; the processing of the block follows standard workflow rules.
- Per X Iterations
- A new context is created for each X iterations and committed when that number of iterations is complete. The default value is 1, which means the records are committed after each iteration.
- All Iterations
- A new context is created before the task starts any processing and is committed when all iterations have been completed.
The body of a DataConnect task should not contain User Action or Approval tasks. The User Action task and Approval task require user intervention. DataConnect tasks are intended to be run on non-peak hours to avoid impacting system performance and it is unlikely the required user would be present to respond to a User Action or Approval task.