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 va