Convert PDF forms to adaptive forms convert-print-forms-to-adaptive-forms
AEM Forms Automated Forms Conversion service (AFCS), powered by ۶Ƶ Sensei, automatically converts your PDF forms to device-friendly and responsive adaptive forms. Whether you are using non-interactive PDF forms, Acro Forms, or XFA-based PDF forms, the Automated Forms Conversion service (AFCS) can easily convert these forms into adaptive forms. For information about the capabilities, conversion workflow, and onboarding information see Automated Forms Conversion service.
Pre-requisites pre-requisites
-
Prepare the to be applied to converted forms: Using a template allows you to apply consistent branding across all the adaptive forms. Moreover, Automated Forms Conversion service (AFCS) does not extract and use header and footer of source PDF documents. You can use adaptive form templates to specify header and footer. Header and footer specified in the template are applied to the adaptive form during conversion. When you create a folder for the templates, select the Browse configurations option for everyone.
-
Prepare the to be applied to converted forms: Using a theme allows you to apply a consistent style to all the adaptive forms of your organization.
Start the conversion process start-the-conversion-process
After you connect your AEM instance with AEM Forms Conversion Service, you can convert your PDF forms to adaptive forms. Perform the following steps in the listed order to convert the forms:
Upload PDF forms to your AEM Forms server upload-pdf-forms-to-your-aem-forms-server
The conversion service converts PDF forms available on your AEM Forms instance to adaptive forms. You can upload all the PDF forms at once or in a phased manner, as required. Before uploading the forms, consider the following:
- Keep the number of forms in a folder less than 15 and keep the total number of pages in a folder less than 50.
- Keep the size of folder less than 10 MB. Do not keep forms in a subfolder.
- Keep the number of pages in a form less than 15.
- Do not upload the protected forms. The service does not convert password-protected and secured forms.
- Do not upload source forms with spaces in the filename. Remove the space from the name of the file before uploading the forms.
- Do not upload . The service does not convert a PDF Portfolio to an adaptive form.
- Read the Known issues and the Best practices and considerations sections and make suggested changes to forms.
Perform the following steps to upload the forms to be converted to a folder on your AEM Forms instance:
-
Log in to the AEM Forms instance.
-
Tap ۶Ƶ Experience Manager
-
Tap Create> Folder. Specify Title and Name of the folder. Tap Create. A folder is created.
-
Tap to open the newly created folder.
-
Tap Create> File Upload. Select the forms to upload, click Open, and click Upload. The forms are uploaded.
Run the conversion run-the-conversion
After you have uploaded the forms and configured the service, perform the following steps to start the conversion:
-
On your AEM Forms instance, tap ۶Ƶ Experience Manager
-
Select a form or the folder containing PDF forms (forms to be converted) and tap Start Automated Conversion. The Conversion Settings dialog appears.
-
In the Basic tab of the Conversion Settings dialog:
- Select a cloud configuration. When you select a configuration, default template and theme are already specified. You can specify a different template or a theme, if required.
- Specify a location to save generated adaptive forms and corresponding schema. You can use default paths or specify custom paths.
- Use the Generate adaptive forms without data model bindings option to select if you want to generate an adaptive form with or without data model bindings.
If you do not select this option, the conversion service automatically associates the adaptive forms with a JSON schema and creates a data binding between the fields available in the adaptive form and JSON schema. The Save generated data model schema at field displays the default location to save the generated JSON schema. You can also customize the location to save the generated schema.
If you select this option, the conversion service generates an adaptive form without data model bindings. After a successful conversion, you can associate an adaptive form with a Form Data Model, XML schema, or a JSON schema. For more information, see .
-
In the Additional tab of Conversion Settings dialog,
- Select the Extract fragment from adaptive forms option to allow the conversion service to identify, extract, and download form fragments for converted forms. When you select the Extract fragment from adaptive forms option, the options to specify paths for saving extracted form fragments and corresponding form fragments schemas is enabled.
- Specify the location of existing adaptive form fragments, if you have some existing JSON schema based and schema less adaptive form fragments and you plan to use these fragments in automatically generated adaptive forms. Conversion service matches available JSON schema based and schema less adaptive form fragments with input PDF Forms (non-interactive PDF Forms only), if there is a match, the matched adaptive form fragment is used in corresponding adaptive forms.
note note NOTE - You can use only ** Extract Fragment** or Use existing adaptive form fragments option at a time. You cannot use both the options simultaneously.
- You can use the Use existing adaptive form fragments option only with non-interactive PDF Forms. Other form types are not supported yet.
- You can use only unbound fragments or fragments bound to a JSON schema with Automated Conversion Service. Do not use XFA fragments. XFA fragments are not supported.
-
Select the Auto-detect multi-column layout of input forms option to retain the layout of the source form for large screens like desktops and laptops. The option is helpful in preserving the multi-column layout of source forms. For example, when a source PDF has a two-column layout, the service generates an output adaptive form with a two-column layout for large screen displays and single-column layout for small screen devices like mobile phones. The feature has some known issues with data source schema structure. For details, see the known-issues article.
-
By default, the service creates a separate top-level panel for each page of a PDF form. Now, you can use the Auto-detect logical sections option to not create page level panels (page number-based panels) and create only logical panels. It also clubs the fields which do not belong to any section with preceding logical section and fields of a logical section spread across two adjacent pages into a single logical section. For example, if some fields of a logical section are at the end of page one and some are in the starting of page two, all such fields are clubbed into a single logical section.
note note NOTE You require the connector package 1.1.38 or above to use the Auto-detect logical sections feature.
-
(AEM Forms as a Cloud Service Only) The [Auto-convert sections to fragments] option applies to PDF Forms with more than 15 pages. It converts the detected top level sections to fragments. It also enables lazy-loading for all the created fragments. It helps improve rendering speed of converted forms and makes it easier to load large forms in adaptive form editor.
note note NOTE Do not use responsive layout template while using the Auto-convert sections to fragments option.
Use the review and correct editor to merge small panels to a large one. It helps reduce the number of fragments in the converted adaptive form.
If you experience the “too many calls” exception,- restructure the form to create a simplified hierarchy
- [increase the value of the sling.max.calls parameter]to a high enough number until the exception disappears.
- increase size of the cache. The error occurs if the form is too complex, has a large number of tables, and multi-level hierarchical structure.
-
Tap Start Conversion. The Conversion is started. Conversion progress is displayed on the folder or the form until the conversion is in progress. The message is replaced another status message (Converted, Partially Converted, or Conversion Failed) after the conversion is complete. A status email is also sent on the configured email address on completion of conversion:
- On a successful conversion, the converted adaptive form and related schema are downloaded to the path specified in the Basic tab of the conversion dialog. Form fragments and corresponding schema are downloaded only if the Extract Fragment option is selected before starting the conversion.
- On a failed conversion, the Conversion Failed message is displayed if all the input forms fail to convert or the Partially Failed message is displayed when only a few of all the input forms fail to convert. A status email is sent on the configured email address and an error is logged to the error.log file.
If you are converting an XFA-based PDF form in to an adaptive form, the conversion service automatically associates the PDF form to the converted adaptive form as the Document of Record template. After conversion, you can open the adaptive form properties to view the Document of Record template in the Document of Record Template Configuration section of Form Model tab.
The conversion service automatically uploads the PDF form to the converted adaptive form as the Document of Record template only if you enable the Tools > Cloud Services > Automated Forms Conversion Configuration > Properties of selected configuration > Advanced > Generate Document of Record option.
note note NOTE If the conversion process takes more than 60 minutes and the PDF form is still not converted to an adaptive form, create a folder on AEM Forms instance, upload the PDF form to the newly created folder, and restart the conversion.
Review and correct the converted forms review-and-correct-the-converted-forms
Real world forms have complex data capture requirements. Once the automated conversion is complete, customers can review the conversion quality of the form and make necessary updates to the form. AEM Forms provides a review and correct editor to make required changes. It allows you to improve automated identification of form fields and convert identified fields from one type to another. For example, you can help identify two-column layout of a form and change a field automatically identified as radio button to multiple choices field.