English version
Oracle announced APEX 26.2 on October 6, 2026. My original post asked a practical question: which parts of our development workflow should change as we adopt it?
More targeted development with APEXlang
File-level import lets developers import selected APEXlang files through SQLcl or the SQL Developer extension for VS Code. Oracle describes this as a development workflow; production deployments should use a full application import. It is not an App Builder file-import feature.
AI needs explicit boundaries
The release expands AI capabilities, including provider support and reasoning controls. Evaluate quality, latency, cost, and allowed actions for each use case. Navigation and data access still need authorization.
Reports, security, and workflow matter together
AI Interactive Reports gain enhancements, and the release introduces integration with Oracle Deep Data Security. Database-level controls complement application authorization. Workflow improvements include instance migration and additional activity capabilities; test changes against existing running processes.
My adoption sequence would be: review release notes, upgrade a development environment, test critical flows and integrations, then plan a controlled deployment. A feature list is not a substitute for regression testing.
Sources: Oracle's release announcement and 26.2 new features.
