Skip to main content
Level 2
Nov 18, 2026 7:02 PM UTC
Question

AEM Forms in 2026.10.0: What Just Graduated From Early Access to GA (and What Hasn't)

Last month I wrote about the AEM Forms Early Access program. The 2026.10.0 release (October 29, 2026; notes last updated November 16) changed the picture. Several items I’d listed as Early Access now appear under “New features in AEM Forms”, with text saying they are now generally available.

Now generally available (per the 2026.10.0 notes)

These were new to GA in this release, not new features. They had been in Early Access before:

  1. Table component for Core Components based Adaptive Forms. Structured, multi-record data capture (employment history, expense lines) with customizable rows and columns.
  2. Visual Rule Editor enhancements. API integration without a Form Data Model, by entering a JSON URL or importing a cURL command, using the Invoke Service action.
  3. Accessibility improvements for Adaptive Forms Core Components. WCAG-oriented <fieldset>/<legend> markup for checkbox groups, radio groups and panels.
  4. Locale support in the Interactive Communication Editor. Regional date, number and currency formatting, limited to supported locales.
  5. Forms Service APIs. Interactive PDFs generated from Designer templates (XDP/XML), plus data import, extraction and validation.
  6. Document Conversion APIs. HTML to PDF, PostScript to PDF, PDF to image, PDF to PostScript and PDF transparency flattening.
  7. Direct upload of generated PDFs to Azure Blob Storage. Requires your own Azure Blob Storage.

The feature descriptions come from Adobe’s Early Access page, written before these items went GA, so check the current docs for limits that changed. “Generally available” means supported, not proven for your documents. Test PDF fidelity, conversion edge cases and locale formatting on your own forms before migrating anything.

Other new Forms items (no status label on the page)

Listed under “New features in AEM Forms” with no label: Adaptive Form authoring in CX Coworker, CAPTCHA v3 support, and Forms Manager improvements. I only have the names, so check the notes for details.

Still “Early Adopter” (the heading isn’t a standard status label)

Interactive Communication Editor enhancements, Theme Editor for Core Components based Adaptive Forms, Dynamic Media images in Adaptive Forms, and custom submit actions in Universal Editor. Treat these as not production-ready.

What I couldn’t confirm

Agentic Form Filling, Conversational Forms, the File Attachment Virus Scanner/Validator and the Forms Scaffolder CLI were on the Early Access page last month. They are not listed in the 2026.10.0 notes, so I can’t say whether they’re still EA. Check Adobe’s Early Access page before relying on any of them.

What to do

  1. If you waited for GA on tables, the Visual Rule Editor or the Document Conversion APIs, pilot them now in a lower environment.
  2. Re-run accessibility tests on forms using groups and panels, since the markup changed.
  3. For conversion and PDF generation, compare output against your existing pipeline on real documents.
  4. Release 2026.11.0 is planned for November 19, so re-check the notes for further changes.

Bottom line

Seven Forms capabilities moved to GA in a single release, which removes the main objection to adopting them. The ones still labeled “Early Adopter”, and the AI-driven features I couldn’t find in the notes, still need caution.

Has anyone moved a production form to the GA table component or the Document Conversion APIs? Fidelity issues or surprises would help others decide.