Importing and Replacing APEX application with build status “Run Application Only”

1
votes

I recently had an issue where a developer "unknowingly" made direct changes to code on an APEX app in the production environment.

To prevent developers from being able to do this; I was suggested importing the app with the 'Run Application Only' Build Status. It sure does prevent users from making "accidental" changes to the production environment, but now we can't import and override the application with the same App ID now. It tells us... 'The application could not be installed because its build status is Run Application Only. If you wish to install the application, you must first log in as a Workspace Administrator. ' Okay, cool...but we are logged in using the workspace admin.

I guess we can change the build status back to 'Run and Build Application' when we want to import and override the application, but that seems rather excessive for just importing apps. What can be done here?

Thanks in advance :) APEX v5.0.4 Oracle 11g

1
oracleoracle-apexoracle-apex-5
I've never really seen a good reason to use Build Status - I prefer to use the Run-time Only option to lock Prod down completely (deployments are only done via the command-line). - Jeffrey Kemp

1 Answers

3
votes

You can still overwrite the application if you run the application export script. Export your application from your dev environment - this gives you a SQL*Plus script (e.g. f100.sql) that you can then run directly on the prod environment.

(tested in Oracle APEX 5.0.3)