Explanation/Reference:
A: To enable a bounded task flow to run as a transaction:
1. In the overview editor for the called bounded task flow, click Behavior and expand the Transaction
section.
2. Choose one of the following from the dropdown list:
<No Controller Transaction>: The called bounded task flow does not participate in any transaction

management.
Always Use Existing Transaction: When called, the bounded task flow participates in an existing

transaction already in progress.
Use Existing Transaction If Possible: When called, the bounded task flow either participates in an

existing transaction if one exists, or starts a new transaction upon entry of the bounded task flow if one
doesn't exist.
Always Begin New Transaction: A new transaction starts when the bounded task flow is entered,

regardless of whether or not a transaction is in progress. The new transaction completes when the
bounded task flow exits.
D: 1. Select the task flow return activity in the called bounded task flow.
2. In the Property Inspector, expand the Behavior section.
If the called bounded task flow supports creation of a new transaction (bounded task flow specifies Use
Existing Transaction If Possible or Always Begin New Transaction options), select one of the following in
the End Transaction dropdown list:
commit: Select to commit the existing transaction to the database.

rollback: Select to roll back a new transaction to its initial state on task flow entry. This has the same

effect as cancelling the transaction.
References: https://docs.oracle.com/cd/E15523_01/web.1111/b31974/
taskflows_complex.htm#ADFFD1710