Using .jspx in Bounded Task Flows
In cases in which the end user clicks the Back button to navigate back into an ADF-bounded task flow that was already exited, you can specify task flow–reentry options for the task flow definition. These options specify whether a page in the ADF bounded task flow can be reentered.
reentry-allowed: Reentry is allowed on any view activity within the ADF-bounded task flow.
reentry-not-allowed: Reentry of the ADF-bounded task flow is not allowed. If you specify reentry-not-allowed on a task flow definition, an end user can still click the browser’s Back button and return to a page within the bounded task flow. However, if the user does anything on the page such as clicking a button, an exception (for example, InvalidTaskFlowReentry) is thrown indicating the bounded task flow was reentered improperly. The actual reentry condition is identified when the reentered page is submitted.
reentry-outcome-dependent: Reentry of an ADF-bounded task flow using the browser Back button is dependent on the outcome that was received when the same ADF-bounded task flow was previously exited through task flow return activities. If specified, any task flow return activities on the called ADF-bounded task flow must also specify either reentry-allowed or reentry-not-allowed to define outcome-dependent reentry behavior.