ÃÛ¶¹ÊÓƵ

Which version of AEM Forms does the Automated Forms Conversion service (AFCS) support?

Automated Forms Conversion service (AFCS) supports AEM 6.4 Forms and AEM 6.5 Forms. It works with both AEM Forms on OSGi and AEM forms on JEE. You require the latest AEM Forms add-on package on top of AEM author instance to use the service. For detailed instructions, see Configure the Automated Forms Conversion service.

Can the service be installed on-premise?

ÃÛ¶¹ÊÓƵ trains AI and ML algorithms of Automated Forms Conversion service (AFCS) on a regular basis with new data set to improve conversion accuracy. The updated algorithms are deployed to the conversion service running on ÃÛ¶¹ÊÓƵ Cloud at periodic intervals. All the customers of the service are benefitted from the updated algorithms. So, cloud-hosted central deployment is best suited for Automated Forms Conversion service (AFCS) to continuously learn and deliver improvements to all the customers.

The service converts blank forms to adaptive forms. The service does not support filled forms and extraction of data from filled forms. Remove data from filled forms and remove or allowlist proprietary information from the forms before sending the forms to service for conversion

Does the service support all formats of PDF forms? What all languages are supported?

The service can convert non-interactive PDF forms, XFA-based XDP and PDF forms, and AcroForms to adaptive forms. The service does not support scanned or filled forms. For other limitations, see the known issues article.

We are regularly adding support for other source types. Keep the supportedPDF forms section on your watchlist for a regular update on newly added features and capabilities.

The service can convert only English, French, German, Spanish, Italian, and Portuguese language forms to adaptive forms. You can translate the generated adaptive forms to another language using

Can the service produce an XDP instead of an adaptive form?

The service does not produce an XDP output. We are regularly adding features and to the service. Keep the supported languages and PDF forms section on your watchlist for a regular update on newly added features and capabilities.

What is the type of generated schema?

You can use the service to generate:

• an adaptive form bound to a JSON schema and
• an adaptive form not bound to any schema

Can the service convert a Microsoft Word form to adaptive forms?

No, the service does not convert a Microsoft Word form to adaptive form. You can save a Microsoft Word forms to PDF form and convert the PDF form to an adaptive form. The complete process is

1. Use ÃÛ¶¹ÊÓƵ Acrobat to .
2. Use ÃÛ¶¹ÊÓƵ Acrobat to .
3. Use ÃÛ¶¹ÊÓƵ Acrobat to manually update and fix form fields.
4. Save the PDF form. Now, you can use the form with the conversion service to generate an adaptive form. You can also use the form as a Document of Record template.

Can the service convert scanned paper forms and colored forms to adaptive forms?

The service can convert color PDF forms to adaptive forms. The service does not support scanned or filled forms. For other limitations, see the known issues article.

Can the service convert a scanned form or only image of a form to an adaptive form?

The service does not support converting scanned forms or an image of a form to an adaptive out-of-the-box. However, you use ÃÛ¶¹ÊÓƵ Acrobat to convert the image of a form to a PDF Form. Then, use the service to convert the PDF Form to an adaptive form. Always use a high-quality image of the form for conversion in Acrobat. It improves the quality of the conversion.

Some XDP-based forms use form fragments, where should these form fragments be uploaded?

Upload form fragments to the conversion folder and preserve the original folder structure. It helps preserve relative paths used in XDP-based forms and form fragments.

Does the service support schema bound XDP forms? If I have an XDP bound to a schema, do I need to embed schema to XDP?

Yes, the service supports schema-bound XDP forms and requires the schema to be embedded to the source XDP form. When you convert a schema-bound XDP form, the service generates a JSON schema. The JSON schema is structurally similar to the XSD schema of source XDP forms.

The service has failed to convert forms. What is the reason and how to resolve the issue?
The most common reasons for the conversion to fail are:

• Secured PDF forms are provided for the conversion. Do not use password protected or secured PDF forms for conversion.

• Internet connection is interrupted. Ensure that you are connected to the internet during the conversion.

• Source PDF has an image of the form instead of the actual form.

• Service is configured incorrectly, service URL is not provided, or provided service URL is incorrect. Check the service configuration at AEM > Tools > Cloud Services > Automated Forms Conversion configuration.

• IMS Configuration is not configured properly. Perform a health check on the IMS configuration to ensure it is working properly. To check if the IMS Configuration is correct or not:

  1. Go to http://[servername]:[port]/libs/cq/adobeims-configuration/content/configurations.html
  2. Select the configuration. Click the Check Health from the header and click Check. If successful, you get Token retrieved successfully! message.

Does using custom fonts impact conversion?

When a non-interactive PDF form is converted to an adaptive form, to improve the quality of conversion, the fonts are embedded in the PDF form. The support for embedding fonts is restricted to non-interactive PDF forms. To optimize the conversion of AcroForm and XFA-based PDF forms, fallback fonts are used.

Only forms available in the custom fonts directory listed in the Customer fonts directory field of the CQ-DAM-Handler-Gibson Font Manager Service configuration are embedded in non-interactive PDF form.

Does the service identify and use fonts of source PDF in output adaptive forms?

Style and layout of a responsive HTML form is generally different from a PDF or paper-based form. To support consistent layout and styling across the organizations, adaptive forms use . The conversion service uses the fonts and font styles specified in the theme applied during the conversion. You can change fonts and font styles of the theme to provide a distinct look and feel to the components of an adaptive form.

Does the service automatically extract JavaScript from XDP-based forms and applies it to corresponding adaptive forms?

The service does not automatically convert scripts of XFA-based forms or Acro Forms to corresponding adaptive form rules. You (form-authors) can use the to add interactivity to an adaptive form.

Some form objects are not converted correctly to adaptive form components. How to resolve the issue?

Automated Forms Conversion service (AFCS) is trained on a large set of forms. But AI/ML-based applications are limited by their training data and patterns. There could be multiple field types, layouts, patterns, and context discernible to human perception but difficult for automated recognition. The service may fail to identify such objects or may recognize them incorrectly. You may use Review and Correct editor to make necessary modifications in the familiar paper form based layout of the input form.

Some corrections are repeated across forms. Can the service identify and fix all such instances in future conversions?

The service is consistently training on your forms and patterns. It learns new patterns on daily-basis. It is yet to start auto-applying corrections repeated across the forms. Keep an eye on prerelease forms for the availability of such a feature.

You can use meta-model to map the form objects to adaptive form component of your choice and pre-configure validations, rules, data patterns, help text, and accessibility properties for the components. All the specified properties are applied during the conversion. You can use meta-model to apply common properties to fields. It can help you reduce some repeated issues across forms.

What are the options for forms with sensitive data like personally identifiable information (PII) information?
The service supports only blank or unfilled forms. Do not upload filled forms or forms with personally identifiable information (PII). Also, remove pre-filled data, personally identifiable information (PII), confidential, and proprietary information in source forms.

Where should the header and footers be placed?

Place header and footer in an adaptive forms template. If the source PDF form has header and footer, the service detects and replaces detected header and footer with header and footer available in adaptive form template, during the conversion. If any extra header or footer is included in the adaptive form, you can use the Review and Correct editor to fix or remove such header or footer.

How much time does the service save in comparison to the manual process of planning, creating assets (themes, templates), creating, and publishing an adaptive form?

The amount of time depends on the size and complexity of input forms and number of requests. The service intends to significantly reduce time to value by converting PDF Forms to adaptive forms at a much faster pace in comparison to the manual process of converting forms.

What to do if I encounter an error related to RSA libraries? The error message is similar to the message mentioned below:

*ERROR* [0:0:0:0:0:0:0:1 [1565757652491] POST /content/dam/formsanddocuments/demo004.affBatchProcessor.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught Throwable java.lang.NoClassDefFoundError: Could not initialize class com.rsa.cryptoj.o.dl at com.rsa.jsafe.JSAFE_SecureRandom.getInstance(Unknown Source) at com.adobe.internal.pdfm.util.Util.appendRandomNumberToPrefix(Util.java: 169) [com.adobe.aemfd.adobe-aemfd-assembler:6.0.34] at com.adobe.internal.pdfm.logging.JobLog.<init>(JobLog.java:126) [com.adobe.aemfd.adobe-aemfd-assembler:6.0.34]

The aforementioned error occurs when boot delegation is not configured for RSA/BouncyCastle libraries. Perform the below steps to resolve the issue:

1. Stop the AEM instance. Navigate to the [AEM installation directory]\crx-quickstart\conf\ folder. Open the sling.properties file for editing. If you use [AEM installation directory]\crx-quickstart\bin\start.bat to start an AEM instance, edit the sling.properties located at [AEM_root]\crx-quickstart\.
2. Add the following properties to the sling.properties file:
   sling.bootdelegation.class.com.rsa.jsafe.provider.JsafeJCE=com.rsa.*
sling.bootdelegation.class.org.bouncycastle.jce.provider.BouncyCastleProvider=org.bouncycastle.*
sling.bootdelegation.xerces=org.apache.xerces.*
3. Save and close the file.
4. Start the AEM instance.

How to automatically change casing of adaptive form text?

You can use adaptive from themes or style editor to change casing of a field of adaptive form. For example, you can open the theme editor and set value of Case property of all the text of form to uppercase, lowercase, or camelCase. You can also use the CSS Override option in theme editor to create different types of styles.

Can I use ÃÛ¶¹ÊÓƵ Sign text tags with Automated Forms Conversion service (AFCS)?

When you use Automated Forms Conversion Service (AFCS) to convert a PDF form to an adaptive form and the PDF form has ÃÛ¶¹ÊÓƵ Sign text tags, those tags are converted to corresponding adaptive form fields and signer details are automatically populated. The feature is available for only for Acro Forms and adaptive forms support a limited number of ÃÛ¶¹ÊÓƵ Sign fields.

How to create an ÃÛ¶¹ÊÓƵ Sign enabled PDF form?

To create an ÃÛ¶¹ÊÓƵ Sign enabled PDF form:

Add to field names or use the option.