AFCS for AEM LTS on prem | Community
Skip to main content
P
pathikparmar19
Level 2
February 3, 2026
Question

AFCS for AEM LTS on prem

  • February 3, 2026
  • 3 replies
  • 54 views

So, I have a scenario, 

We’ve more than 5000+ pdf and XDP to convert.

we’re running on AEM on prem LTS. 

 

Has anyone here done something similar? As this is going to be a lot of configurations, implementations and then migration. 

I need some guidance on how to achieve it. I am closely following documentation and seems like it should be easier process after the right configuration. 

Configure the Automated Forms Conversion service (AFCS) | Adobe Experience Manager

 

I appreciate the help or any more documentation, if we have it. I have search on AEM forums but, didn’t find anything yet. 

    3 replies

    P
    pathikparmar19Author
    Level 2
    February 4, 2026

    Configuration part has been successfully done. 

    Issue: While converting PDF to adaptative forms it’s taking longer and it shows only 1% conversion,

    I have traced the sling log but, there is no error. I am not sure how long this is going to take. Do anyone in here phase same issue?

    P
    Adobe Employee
    Pranay_MAdobe Employee
    Adobe Employee
    February 5, 2026

    Hi ​@pathikparmar19,

    Following up on your question about configuring the Automated Forms Conversion Service (AFCS) for bulk PDF/XDP conversion on AEM 6.5:

    We recommend the following setup steps:

    1. Prepare AEM Forms 6.5

      • Ensure your AEM author is on 6.5 with the latest Service Pack and the latest AEM Forms add‑on installed.
      • Create an AEM user with a valid email and add it to the forms-users group.

    2. Enable AFCS access

      • Your Adobe org admin creates an AFCS product profile in Admin Console and assigns your developers to it.
      • A developer then uses Adobe Developer Console to create an AFCS API project (OAuth Server‑to‑Server) and obtains the API Key, Client Secret, Org ID, and Scopes.

    3. Connect AEM to AFCS

      • In AEM, create a single Adobe IMS configuration for “Automated Forms Conversion Service” using the OAuth details and verify via Check Health.
      • Then create an Automated Forms Conversion Cloud Service configuration (service URL https://aemformsconversion.adobe.io/), and select your default Adaptive Form template and theme.

    4. Validate with a pilot conversion

      • Upload a sample (non‑secured) PDF, use Start Automated Conversion, select your AFCS configuration, and verify the generated Adaptive Form.

    Once this is working, we can help you define batching and QA guidelines so you can safely scale conversion across your full set of 5000+ forms.

    Thanks
    Pranay

    P
    pathikparmar19Author
    Level 2
    February 11, 2026

    Hi ​@Pranay_M  that’s the configuration and base step. That has been already completed. 

     

    We need to migrate this from MS info path to Adaptive forms. Please provide Batching and QA guidelines, 

     

    We are extending the prepackage of themes and template as it suits our use case. As most of this PDFs are static and have very tight margins for the consumer view, also these forms will go for the PTM (Print to Mail) kind of implementation. 

     

     

    P
    Adobe Employee
    Pranay_MAdobe Employee
    Adobe Employee
    February 16, 2026

     

    Thanks for confirming that the AFCS configuration and base setup are complete.

    Since we now need to migrate from MS InfoPath to Adaptive Forms (with tight‑margin static PDFs and a Print‑to‑Mail workflow), here’s a concise proposal for batching and QA on top of your existing templates and themes.

    1. Batching strategy

    To keep control while scaling:

    • Per batch:

      • 8–15 PDFs per source folder
      • ≤ 50 pages total per folder
      • No subfolders; keep folder size < 10 MB

    • How to group forms:

      • Group by layout family (same page size, margins, and header/footer pattern).
      • Keep complex forms (heavy tables, many fields, conditional logic) in separate, smaller batches for closer review.

    • Execution approach:

      • Start with a pilot batch of ~10–20 representative forms.
      • Refine the process (conversion options, template/theme mapping, DoR settings).
      • Scale up to a steady cadence (e.g., 50–100 forms/day, depending on how much QA you can absorb).

    2. QA guidelines (focused on PTM and tight margins)

    For each converted form in a batch, we recommend:

    1. Structure & UX checks

      • All InfoPath/PDF fields are present in the Adaptive Form.
      • Reading order is correct (especially multi‑column layouts and tables).
      • Sections/panels align with the original logical grouping.
      • Required/optional flags and basic validations (format, length, date, numeric) behave as expected.

    2. Data & binding checks

      • Submit sample data and confirm:
        • All fields appear in the JSON/XML payload with expected names.
        • Repeated tables/panels serialize correctly.
      • Where possible, compare payloads to existing InfoPath/back‑end samples for compatibility.

    3. Print‑to‑Mail / PDF output checks

      • Generate the Document of Record or output PDF and verify:
        • Page size and margins match the original print‑ready PDFs.
        • No clipping or truncation, especially near the edges and in narrow columns.
        • Page breaks remain stable for typical and “long” data values.
      • For PTM, test at least:
        • One “simple”, one “typical”, and one “worst‑case” data set per template and review them with your print/mail team.

    3. Handling exceptions

    • Very tight‑margin or highly dynamic forms should be flagged early.
    • We still run them through AFCS, but assume extra manual adjustment in the Adaptive Form and DoR template.
    • If AFCS output deviates too far from the required print layout, we treat those as manual redesign candidates rather than trying to fully automate them.

    Thanks
    Pranay

    A
    AbhilashYS
    Level 1
    February 23, 2026

    pathikparmar19 - Thanks for the post - I have similar objective in near future - much appreciated your inputs here and what went and worked well for your case. Please keep adding as you run into perfect combination for migration.

    Also how about any design deviations from pixel perfect pdf to adaptive form , any challenges ?
     and do you have any workbench complex/simple process running for these and what is the plan for these ?

    Leave the updates here as you have . Thanks much

    Terms & ConditionsAccessibility statement

    Loading footer...