When you create an Application Computation and set it to run "On New Instance (i.e. Login)", APEX doesn't yet have the APP_USER in session state.
I have an application where depending on the current user, many application-wide variables should be initialized. If I cannot access the APP_USER item, this cannot be done by using an Application Computation.
My alternative is to create Page Computations for the application items on Page 1 (or whatever the default page is after logging on).
I am not sure I understand what you are asking here.
Also could you provide what software and loadout you
DB: Oracle9i Enterprise Edition Release 22.214.171.124.0 - 64bit Production
We're already using VPD but there are some aspects of the system that have to be limited in the front-end rather than at the database level so that doesn't help my problem, but thank you for the suggestion.
The problem is simple, the value of APP_USER is inaccessable at the time when an application computation is run if that application computation is setup to run "On New Instance (i.e. Login)".
I've tried v('APP_USER'), :APP_USER and &APP_USER., and all return null, whether I use them in a SQL statement or even as Static Assignment.
Hopefully that makes sense.
Message was edited by:
You might want to put this "setup" code into the authentication scheme's Post-Authentication Process attribute. When this block is executed, APP_USER is set and it only executes once per session.