Enabling Transactions on a Task Flow (continued)
requires-transaction: When called, the ADF bounded task flow either participates in an existing transaction if one exists, or starts a new transaction upon entry of the ADF bounded task flow if one doesn’t exist.
new-transaction: A new transaction is always started when the ADF bounded task flow is entered, regardless of whether or not a transaction is in progress. The new transaction is completed when the ADF bounded task flow exits.
If you choose requires-existing-transaction or requires-transaction, you can optionally select true in the No Save Point drop-down list. If you select true, an ADF Model savepoint is not created on task flow entry. An ADF Model savepoint is a saved snapshot of the ADF Model state. Selecting true means that the overhead associated with a savepoint is not created for the transaction.
Note: You can also specify transaction start options on the Behavior panel of the Property Inspector.
Transaction Return Options
5. In the editor, select the task flow return activity in the called ADF bounded task flow.
6. In the Property Inspector, click Behavior.
7. If the called task flow definition supports creation of a new transaction (task flow definition specifies requires-transaction or new-transaction options), select one of the following in the End Transaction drop-down list:
commit: Commits the existing transaction to the database
rollback: Rolls back a new transaction to its initial state on task flow entry. This has the same effect as canceling the transaction.
8. In the restore-save-point drop-down list, select true if you want changes that the user made within the called ADF bounded task flow to be discarded when it is exited. The savepoint that was created upon task flow entry will be restored.