Idea Summary
Enable developers to export Oracle APEX applications with selective file inclusion, allowing users to exclude static application files (images, CSS, JavaScript, fonts) from the export bundle while preserving application metadata, pages, regions, and database objects. This reduces export file size, accelerates deployment, and enables efficient version control and modular application distribution.
Use Case
Current APEX application export functionality includes all static files in the export bundle, creating several challenges for development teams:
- Large export file sizes make version control systems (Git, SVN) inefficient when tracking application changes; static files inflate repository size
- Deployment cycles are slower due to unnecessary file transfers; production deployments download/process static files even when only application logic changes
Preferred Solution (Optional)
Extend APEX export functionality with a Selective Export Configuration feature that allows developers to:
- Choose which artifact types to include in export: pages, regions, items, processes, validations, branches, static files, themes, preferences, translations, etc.
- Exclude static files by default with a single checkbox.