The Oracle APEX team published a "Modernization Forms to APEX" skill for AI coding agents that have the APEXlang skills installed. The idea: keep the business process and the database, and rebuild the user experience natively in APEX, instead of reproducing Forms screens.
How it works
- Inputs: the functional requirements and schema metadata produced in an earlier analysis step (from the Forms modules and the database). The skill treats them as authoritative.
- It builds a traceability matrix: each requirement, its database evidence, and the target APEX component.
- Canvases, windows, keyboard triggers, alerts, tree controls and navigation built-ins are left out by design, and go on an evidence-backed exclusion list.
- The output is an APEXlang application, validated by the APEX compiler before import.
- Each run ends with an exact status: BLOCKED, VALIDATED-BUT-NOT-IMPORTED, IMPORTED-BUT-NOT-RUNTIME-VERIFIED or COMPLETE.
The requirements doc is the real deliverable
Vague words like "dashboard" give vague pages. Name the APEX component you want: Faceted Search, Interactive Grid, drawer, chart. The skill's prerequisites list an APEX 26.1 or later environment.
Source: Introducing the Modernization Forms to APEX Skill (Part 1, the analysis agent: here).
Get the Oracle + AI digest
One email when a new tested guide, template or APEX release note lands — English or Arabic. No spam; unsubscribe anytime.