Skip to content

FormsLang 2.0.0 — Oracle Forms to APEX Modernization Workbench

Choose a tag to compare

View all tags
@gevianajr gevianajr released this 21 Sep 12:29
· 96 commits to main since this release
v2.0.0
326d16e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

FormsLang 2.0 turns FormsLang into a complete, project-based Oracle Forms → Oracle APEX modernization workbench.

Instead of starting a modernization project by manually reading hundreds of Forms modules, teams can now create a project, inventory Forms and database source, map dependencies, assess modernization risk, review architectural decisions, generate eligible Oracle APEX 26.1 / APEXlang artifacts, validate them, and export a documented modernization package.

The guiding principle remains simple:

Automate what is safe. Assist what is complex. Escalate what requires human judgment.

Who it is for

FormsLang 2.0 is designed for:

  • Oracle Forms developers
  • Oracle APEX developers
  • solution and application architects
  • modernization consulting teams
  • application owners responsible for legacy Oracle estates

The machine inventories, correlates and triages. People retain responsibility for architecture, business intent, security decisions and UAT.

What’s new in 2.0

Project-based modernization

FormsLang now treats a Forms modernization effort as a persistent project instead of a collection of independent commands.

A typical workflow is:

Install → New Project → Select legacy sources → Analyze → Overview / Inventory → Review → Generate eligible APEX 26.1 / APEXlang → Validate → Export modernization package

Projects preserve source fingerprints, assessment revisions, review history, warnings, freshness and relink state.

Estate assessment

FormsLang can inventory supported Forms and Oracle database source and correlate them into a single assessment.

The Overview and Inventory surfaces help teams understand:

  • Forms modules and database objects
  • dependencies and cross-layer calls
  • modernization risks
  • recommended modernization directions
  • AUTO / ASSISTED / MANUAL intervention categories
  • source coverage and analysis limitations
  • high-priority findings requiring human attention

Static project assessment does not require external AI or Oracle database credentials.

Modernization review

The 2.0 review workflow keeps deterministic engine recommendations separate from human decisions.

Reviewers can:

  • accept recommendations
  • change modernization direction
  • record rationale
  • defer decisions
  • mark findings for further review
  • preserve annotations and history
  • safely revalidate stale decisions

Critical overrides and bulk operations are protected by server-side policy and revision checks.

Oracle APEX 26.1 / APEXlang generation

Reviewed project scope can generate Oracle APEX 26.1 / APEXlang artifacts where the current evidence and approvals make generation safe.

Generation checks architecture decisions, code approval, target prerequisites and current source/review revisions independently.

Generated artifacts are versioned and hash-bound. FormsLang does not automatically deploy them.

Validation and delivery

FormsLang can validate supported generated APEX artifacts through SQLcl and package the assessment for technical and consulting workflows.

Delivery outputs include:

  • executive assessment
  • technical assessment
  • modernization risk report
  • application inventory
  • modernization backlog in CSV / JSON
  • reviewed modernization decisions
  • architecture information
  • APEXlang artifacts where generated
  • database prerequisites and refactoring candidates
  • provenance, hashes, validation evidence and exclusions

CLI and API

The desktop Workbench, CLI and versioned project API use the same underlying services and project model.

Existing 1.x sessions and power-user workflows remain available.

Local-first by default

Static assessment, modernization review and deterministic generation can operate locally.

AI remains optional and explicitly configured. AI assistance does not automatically approve architecture, code, risk or generation decisions.

Default executive reports do not include source bodies or private reviewer notes.

Important boundaries

FormsLang is a modernization workbench, not a claim of fully automatic migration.

Current boundaries include:

  • supported Forms semantics require Forms2XML representation;
  • discovering FMB/PLL/MMB/OLB files does not mean FormsLang semantically parses those binaries;
  • project generation currently produces one independent eligible module application per generation scope rather than automatically merging an entire estate;
  • unsupported mappings, missing controls and stale approvals remain blocked;
  • SQLcl offline validation provides syntax and structural evidence, not runtime equivalence;
  • static analysis cannot infer undocumented business intent;
  • FormsLang does not replace architecture review, functional testing or UAT;
  • FormsLang is an independent open-source project and is not affiliated with or endorsed by Oracle Corporation.

Install and upgrade

Windows release assets are the exact EXE and MSI artifacts produced and accepted by the release pipeline.

Upgrade from FormsLang 1.6.0 was tested through the installer acceptance workflow, including preservation of existing review state and application data covered by the upgrade contract.

For exact verification evidence, hashes and remaining manual validation boundaries, see the quality acceptance documentation.

Documentation

FormsLang remains open source under the Apache License 2.0.

Assets 4
Loading