One of the great advantages of a bounded task flow is its out of the box support for declarative transaction management. Without this support you may end up writing a lot of plumbing code for managing transactions. In this section, we will take a closer look at the declarative transaction settings available for a task flow and how the framework manages the transaction behind the scenes.
The bounded task flow supports the following declarative transaction settings:
No Controller Transaction: The called bounded task flow does not participate in any declarative transaction management. However you can programmatically manage the transaction, if required. This is explained in the next section entitled Programmatically managing transactions for a task flow.
Always Begin New Transaction: The called task flow starts a new transaction.
Always Use Existing Transaction: The called task flows participate in the existing transaction.
Use Existing Transaction...