In Oracle APEX, the Working Copy feature lets developers make changes safely. However, if the underlying database objects (tables, views, procedures, etc.) are modified during this time, the Working Copy is unaware. This can lead to issues when the changes are published.

Use Case

• Alert developers if related DB objects change during Working Copy edits
• Avoid publishing outdated logic tied to modified database structures
• Improve collaboration between APEX developers and DB teams

Preferred Solution

Add a mechanism to either:

• Track schema changes for DB objects used in the app, or
• Notify developers when changes occur while a Working Copy is active