Scribd
Upload
151 views

Transaction Unit Helper

The TransactionUnitHelper class allows delineating the user interface "transaction unit" to identify inappropriate navigation patterns after a transaction commits. This helps when multiple discrete UI tasks share the same root application module and database transaction. The transaction unit identifier indicates when a specific UI task begins and ends, and if a user navigates unexpectedly, the transaction unit status can be checked to ensure inappropriate actions are not performed and unwanted cache data is not committed. For example, creating an employee involves starting a create transaction unit, committing changes ends the unit, and checking the unit status on a back button prevents further edits.

Uploaded by

hisham_476
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
151 views

Transaction Unit Helper

The TransactionUnitHelper class allows delineating the user interface "transaction unit" to identify inappropriate navigation patterns after a transaction commits. This helps when multiple discrete UI tasks share the same root application module and database transaction. The transaction unit identifier indicates when a specific UI task begins and ends, and if a user navigates unexpectedly, the transaction unit status can be checked to ensure inappropriate actions are not performed and unwanted cache data is not committed. For example, creating an employee involves starting a create transaction unit, committing changes ends the unit, and checking the unit status on a back button prevents further edits.

Uploaded by

hisham_476
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

The oracle.apps.fnd.framework.webui.

TransactionUnitHelper class lets you delinea


te the user interface "transaction unit" for the purpose
of identifying inappropriate navigation patterns after a transaction commits.
This is particularly helpful in those cases where multiple discrete UI tasks (ea
ch with their own commit points) share the same
root UI application module -- and therefore the same database transaction. With
the transaction unit identifier, you can indicate when
a specific UI task begins and ends, and if the user navigates in unexpected mann
er (using the browser Back button, for example)
you can check the transaction unit status and react to ensure that inappropriate
actions are not performed, and unwanted data
in the BC4J cache is not committed. For example:
The user searches for employees in an Employee Summary page and selects a Create
Employee button (you begin a create transaction unit).
The user enters some data in the Create Employee page and selects Apply to commi
t her changes (you end the create transaction unit).
As part of the Apply button handling, the Create Employee page forwards to the s
ummary page where a confirmation message is displayed.
The user then selects the browser Back button to return to the Create Employee p
age where she tries to make data changes and select
the Apply button again. By checking the transaction unit status (there is no cur
rent create transaction unit since the user didn't
navigate by Create Employee button which would have prompted the start of a new
create transaction unit), we can display an error dialog
since updates to newly created rows are not allowed in this example module.

You might also like