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
  • 2 replies
  • 29 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. 

2 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. 

 

 

AmitVishwakarma
Community Advisor
AmitVishwakarmaCommunity Advisor
Community Advisor
February 20, 2026

@pathikparmar19 
Your direction is right: for PTM / pixel-perfect PDFs, go XDP + Output Service / Forms Service, not PDF -> Adaptive -> PDF. Refs: https://experienceleague.adobe.com/en/docs/experience-manager-65-lts/content/forms/use-document-services/output-service  https://experienceleague.adobe.com/en/docs/experience-manager-65-lts/content/forms/use-document-services/forms-service

 

Assembler is not for translation; it only assembles/manipulates PDFs. Use locale-specific XDP templates/fragments for 12 languages and select template by locale at runtime. Ref:https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/developer-reference/programming-aem-forms-jee/performing-service-operations-using-apis/assembling-pdf-documents

 

For 6000+, don’t run manually—use Watched Folders (or workflow) to batch-generate PDFs and control throughput. Ref:https://experienceleague.adobe.com/en/docs/experience-manager-learn/forms/document-services/watched-folders-document-services-article-use
 

Store/manage templates in Forms & Documents (bulk import supported). Ref:https://experienceleague.adobe.com/en/docs/experience-manager-65-lts/content/forms/manage-administer-aem-forms/get-xdp-pdf-documents-aem

 

So, Assembler is not for “translation” — it’s for merge/split/manipulate PDFs (headers/footers/TOC, etc.). You still need your own localization strategy for strings/templates.

 

1. Go “XDP-first” (not AFCS) for PTM / pixel-perfect PDFs

  • Use Output Service to generate flat print PDFs: XDP + XML -> PDF
  • Use Forms Service when you need interactive / prefillable PDFs from XDP

2. Multilingual strategy (12 languages)

  • Maintain separate XDP templates per locale (or use shared fragments where possible), and pick the template by locale at runtime (do not expect Assembler to “translate”).
  • If you later move to Adaptive Forms, use AEM translation workflow, but for pure PDF/XDP pipelines, template-per-locale is the most predictable.

3. Batching at scale (6000+)

  • Use Watched Folders (or a workflow) to run Output/Forms service in batch mode and control throughput.

4. Repository management

  • Store templates under Forms & Documents (and you can bulk upload via ZIP).

5. Version sanity

  • Your AEM Forms add-on 6.1.176 aligns with AEM 6.5 LTS Forms packages add-on.

Thanks,
Amit

Terms & ConditionsAccessibility statement

Loading footer...