Oracle Adds an AI Coding Skill to Rebuild Forms Apps Without Copying Their Screens

Oracle Forms applications can be rebuilt around their business processes rather than copied screen for screen with a new AI coding-agent skill. Oracle introduced the Modernization Forms to APEX skill on October 1, 2026. It uses functional requirements and database schema metadata to guide application generation, with rules organizations can adapt to their own modernization projects.

The release extends an earlier analysis workflow, not a new AI model. In May, Oracle described an agent that examined Forms files, checked database dependencies and identified reusable business logic. That process produced a requirements specification and modernization report. The new skill takes the resulting requirements and schema metadata as authoritative inputs for building the APEX application.

The requirements decide what survives

Before generation, Oracle tells teams to review the requirements for completeness and identify processes that should be improved, simplified or discarded. Its Customers and Orders example removes a standalone Customer Directory because the Customer Workbench absorbs that function. Order Detail remains available, but opens from the Orders Workbench instead of appearing in global navigation.

That design choice is explicit elsewhere, too. For parent-and-child records, such as an order and its items, the example uses a browse-and-filter page followed by a detail page. Oracle says organizations can change that rule to support inline editing instead. The skill excludes Forms-specific interface machinery, including windows, keyboard triggers and navigation commands, rather than treating every legacy component as something to preserve.

The workflow reconciles requirements with the database schema and existing business logic before designing native APEX components. A traceability matrix connects each requirement to database evidence and its intended APEX component. It then generates the application using APEXlang and validates it with the APEX compiler before import.

An application, plus a record of its checks

APEXlang is Oracle’s open application definition language. Its documentation describes human-readable, Git-friendly application files rather than large SQL exports, and skills that help coding agents generate the correct syntax. The modernization skill adds project-specific deliverables around those files:

• An application specification covering pages, workflows, validations, navigation and database dependencies.
• A user-experience contract defining page composition, actions, refresh behavior and acceptance tests.
• Application and page files, shared components, and validation evidence, with some evidence dependent on the checks actually performed.

Missing or contradictory requirements can trigger a requirements addendum. When safe generation is impossible, the skill can produce a gap and missing-input report instead. It also reports one of four completion states: BLOCKED, VALIDATED-BUT-NOT-IMPORTED, IMPORTED-BUT-NOT-RUNTIME-VERIFIED or COMPLETE.

The sample preserves rules—and exposes a navigation bug

Oracle’s demonstration uses the Customers and Orders modules from its Summit Sample Forms application. The company says the generated Orders form validates shipping dates and payment type, and prevents deletion of orders with associated items. A database constraint defining allowed credit ratings also becomes a select list in the customer form.

The example also reveals a practical defect. After opening one customer’s orders, navigating to the general Orders Workbench leaves that customer’s context cached. The page consequently shows only that customer’s orders. Oracle’s prescribed fix is to clear the Orders Workbench page cache in the navigation-menu entry.

To try the downloadable skill, teams need an Oracle APEX 26.1 environment, APEXlang skills installed in their coding agent, and the prepared requirements and schema metadata. Oracle’s earlier guidance keeps the human boundary clear: an agent should not be the final authority on page design, security, authorization, transactional boundaries or user experience.