Oracle published a closer look at several platform changes in Oracle APEX 26.2 on November 11, 2026. The post covers APEXlang import and export, new PL/SQL APIs for locking applications and creating working copies, a bigger Mail Queue page and the end of REST Workshop.
Together they affect how teams move applications between workspaces, script their release process and manage REST services. One of them, the REST Workshop removal, may require a change in how you work today.
Translations Now Travel With APEXlang Exports
An APEXlang export in Oracle APEX 26.2 can include the translation repository. The translation data is packaged as SQL artifacts next to the APEXlang application export, in a generated-artifacts folder with a translations.sql file. The language mapping sits in application.apx.
On import, APEX uses the component information in the export to attach each translation record to the right region, item, button or shared component. This works when you install the export as a new application and when you replace an existing one. For a replacement, APEX keeps the internal identities of translatable components, so existing translations stay linked.
You can switch it on in App Builder through Export, APEXlang, Custom Export and the Translation toggle. The SQL Developer extension for VS Code needs version 26.3.0. In SQLcl 26.3, you add the -expTranslations option to the apex export command.
Subscription Mapping in App Builder Imports
When you import an APEXlang application in App Builder, APEX now checks whether the export refers to master application IDs that need mapping. If none do, you click Install. If some do, the button reads Next and opens the existing subscriptions step.
There you map each source master ID to an application in the target workspace. Oracle's example maps master application 700 in development to application 800 in test. The usual ORDS and workspace REST requirements for APEXlang imports still apply.
Public APIs for Locking and Working Copies
APEX 26.2 adds three documented PL/SQL procedures to APEX_APPLICATION_ADMIN:
- LOCK_APPLICATION: locks the main application to control editing in App Builder.
- UNLOCK_APPLICATION: unlocks it again.
- CREATE_WORKING_COPY: creates a working copy of the main application.
A working copy is a separate copy of the application definition. You change and test it first, then merge selected changes back into the main application.
Oracle ties these APIs to SQLcl Projects, AI-assisted development and CI/CD. A script can lock an application while an update runs and unlock it afterwards. An AI coding assistant can create a working copy before it edits anything, so you can review its changes before a merge.
If you already deploy with SQLcl, see our guides on deploying APEX applications with SQLcl Projects and exporting and importing APEX applications with SQLcl.
A Mail Queue Page Built for Troubleshooting
The Mail Queue page under Administration Services, Manage Instance, Manage Meta Data now works as a dashboard across workspaces. Its tabs include:
- Overview: an interactive report showing how long each email has waited, the number of send attempts, the last error and the next retry. Saved reports cover waiting, delayed and failed emails.
- Metrics: emails delivered in the last 10 minutes, the current backlog, errors in the retry queue and emails waiting over five minutes.
- Operational and Triage: workspaces with high volumes, slow deliveries or a delivery limit reached in the last 24 hours.
- Trending and Monitoring: the top 10 workspaces by volume, plus period-to-period comparisons and daily delivery-time charts.
REST Workshop Is Removed
APEX 26.2 removes REST Workshop, the RESTful Services interface in SQL Workshop. You now author and maintain ORDS REST modules in SQL Developer Web. Existing modules and metadata stay available there, and REST Data Sources for consuming services are unchanged.
The path is SQL Workshop, then SQL Developer Web. APEX lists the workspace schemas and shows which are REST-enabled. You can enable a schema, set its ORDS schema attributes and open it in SQL Developer Web.
It requires SQL Developer Web to be enabled in Administration Services, a REST-enabled schema and ORDS running over HTTPS.
What It Means for Developers
The translation export closes a gap for multilingual apps, where translations used to need a separate migration step. If your team uses APEXlang in source control, add the translation option to your export scripts and test a replace import.
The REST Workshop change is the one to plan for. Before upgrading, check that SQL Developer Web is enabled, that ORDS uses HTTPS and that the schemas you need are REST-enabled. Our article on Oracle Deep Data Security with APEX 26.2 and ORDS 26.3 covers another 26.2 change.
Conclusion
APEX 26.2 makes APEXlang moves more complete, gives release scripts supported locking and working copy calls and gives administrators a clearer view of mail delivery. Test the upgrade in a non-production instance first, and prepare your REST authoring for the move to SQL Developer Web.
Sources
See my articles more often when you search Google.
