I have an application whereas we have multiple queues, these are Interactive reports with various limiters, each of which has a SCRIPT_ID link into the same updateable FORM page.
So, multiple entry points to 1 update needing to return to multiple entry points.
Building on the principle described by Sara, we need the previous page to be identified to tell the branch where to go.
1. Create a table called PREVIOUS_PAGE…Columns are PAGE_NUMBER & APP_USER.

2. For all 3 entry point pages (Queues), create 2 processes
a. 1 Before header & 1 After header (not sure it matters…These 2 just need to run each time the pages load via the TABs – In sequence)
b. Processes SQL
DELETE PREVIOUS:

DELETE FROM PREVIOUS_PAGE
WHERE APP_USER = :APP_USER;

PREVIOUS PAGE:

INSERT INTO PREVIOUS_PAGE (PAGE_NUMBER, APP_USER)
VALUES (:APP_PAGE_ID, :APP_USER);

So, essentially what you’re doing is clearing the entry & inserting the page number before you link-Branch to the update point. You should never have more than 1 entry “per user” at a time

3. Create an item (Text) on the Edit page called *P22_RETURN_PAGE (*your page #, this item is populated via a SQL Query:
(After you check it out, make this HIDDEN)

select
PAGE_NUMBER
from
PREVIOUS_PAGE
where APP_USER = :APP_USER

4. Do what Sara said, create the return button to submit & the Branch to redirect to the &P22_RETURN_PAGE.

Works great!

In you application, if you go to shared components > navigation bar entries then select the about entry. Now scroll to the conditions section and here you can select a condition that when true will display the about link in the navigation bar. I would suggest that you could use the condition ‘Current Page is Defined Within Expression 1′ as you can then list the pages in Expression 1 that you want it to display on making sure the page numbers are comma delimited.

Regards
Sara

I have tried this on my workspace and it works well. Is there any way in which I could use ‘about’ only on desired page, rather on the navigation bar, as it appears on all the pages.

thanks,
Toopran

In addition to using the branch, you could make the button a redirect instead of submit and put &P22_RETURN_PAGE. in the redirect page.

Regards,
Dan

I work for a group that is just starting APEX development. These tutorials are very good. I share these with my fellow APEX developers and we enjoy these very much.

Please keep up the good work.
Barry