Statement of Direction
Oracle continues to invest in the development and support of Oracle APEX. This page highlights the roadmap for the upcoming release.
Key features planned for this upcoming release include:
The built-in support for REST-enabled SQL and Web Sources will be extended to Form regions and allow read and write access to remote data sources. The APEX_EXEC PL/SQL API will also be extended to support read and write.
New Data Loading
The data upload functionality in SQL Workshop will be modernized with a new drag & drop user interface and support for native Excel, CSV, XML and JSON documents. The same capabilities will be added to the Create App from Spreadsheet wizard and a new, public data loading PL/SQL API will be made available.
Enhanced Popup LOV
The built-in popup LOV component will be modernized to allow for dynamic, shared LOVs to include multiple columns and enhanced search capabilities.
Upgraded Oracle JET
Oracle JET will be upgraded to the latest version, Oracle JET 6.
Updated productivity and sample apps.
Release Plan and Naming Convention
Oracle APEX 18.1 was the first major release in calendar year 2018. The next release in the same calendar year will be APEX 18.2. Oracle APEX will no longer provide patch set releases, such as APEX 18.1.1, instead only offering full releases. The first release in calendar year 2019 will be APEX 19.1.
Note: Patch set exceptions (PSEs) will still be delivered for major defects and generally communicated on the Oracle APEX Known Issues page. Some PSEs will be delivered in a PSE bundle, rather than individually. Be sure to read the solution provided and search for the bug number specified on the Oracle APEX Known Issues page. For PSE bundles review the readme to determine all of the bug fixes included in the bundle.
This change in release strategy is of significant benefit to both cloud and on-premises deployments of Oracle APEX. The primary advantage of this release strategy is reduced downtime when upgrading an existing Oracle APEX installation. The architecture also provides the ability to immediately rollback if necessary. Utilizing patch sets, instead of a full release, requires significantly more downtime and with no easy way to rollback the patch set installation. This change in release strategy also provides a vehicle for features to be introduced sooner to our customers.
THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION. IT IS INTENDED FOR INFORMATION PURPOSES ONLY, AND MAY NOT BE INCORPORATED INTO ANY CONTRACT. IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL, CODE, OR FUNCTIONALITY, AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISIONS. THE DEVELOPMENT, RELEASE, AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLE'S PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE.