Persisting Application Parameters Across Browser Refreshes in VBCS
Summary:
I have a standalone Oracle Visual Builder (VBCS) application launched from Oracle Fusion SaaS via a custom tile. At launch, a crucial parameter (the Fusion username) is passed to the VBCS application. While the parameter is successfully consumed during the initial flow across multiple pages, a browser refresh (F5) results in the loss of this parameter, disrupting the application logic.
Since the application is not embedded (precluding the use of certain Fusion-native context sharing), what is the recommended approach to persist this initial launch parameter for the duration of the session to ensure state resilience during manual page refreshes?
Tagged:
1