Skip to main content

APEX (Multi) Application Settings

By
Most applications need some sort of "configuration" table. A simple key-value store where you can put values that might change on a different environment, like URLs, minimal password length, API keys, etc. And very conveniently APEX has this implemented as "Application Settings": A simple table containing a key and a value - and a few other properties like "valid values". In your code you can reference these values using either the apex_application_settings view - that contains all Application Settings in your Workspace - or the apex_app_setting API - that you can use to get or set a value based on the Application Settings Name.

That's all great. Until I ran into this situation: Our "application" consists of 2 APEX applications, one Internal (INT), backoffice kind of application and one external (EXT) facing one. And now I needed to set the Application Setting of the EXT application from the INT application. While I can see the current values of the EXT Application Settings - as the apex_application_settings view shows me all settings in my Workspace, I cannot simply set it using the apex_app_setting API as "This procedure changes the application setting value in the current application". So how can I use that to set that API to set the value in another application?
My first idea was to create a Form Page with a Process calling that API in the EXT app and just link to that Form Page from my INT app. That could have worked if both applications would have used the same Authentication cookie. Which of course they didn't!

So as the API can only set a value in the current application .... I had to switch the current application during a Form process that does the update. And there the apex_session package comes to the rescue!
So upon update, when the Application Setting is not a setting of the current application, I have to detach from the current (APEX) session and create a new session for the other (EXT) application. Then I can set the value using the apex_app_setting API. Once done, I can delete that APEX session and attach back to my original session. So the next processes in my APEX page (like "Close Dialog") will still work. 

begin 
  if :P235_APPLICATION_ID = :APP_ID then         
    apex_app_setting.set_value( :P235_NAME, :P235_VALUE );
  else
    -- Switch to other / new session in the other App
    apex_session.detach;
    apex_session.create_session (p_app_id => :P235_APPLICATION_ID, p_page_id => 0, p_username => :APP_USER);
    apex_app_setting.set_value( p_name => :P235_NAME, p_value => :P235_VALUE );
    apex_session.delete_session;
    -- Return to the original session
    apex_session.attach( p_app_id => :APP_ID, p_page_id => :APP_PAGE_ID, p_session_id => :APP_SESSiON );
  end if;  
end;

Simple. Elegant. And just using the APEX API's! 

Comments

Post a Comment

Popular posts from this blog

Filtering in the APEX Interactive Grid

By
Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good o...
1 comment
Read more

Stop using validations for checking constraints !

By
 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function ...
Post a Comment
Read more

Refresh selected row(s) in an Interactive Grid

By
In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...
Post a Comment
Read more