AEM Forms

AEM Forms

Types :

PDF forms : Can be filled offline and the data is sent when you're online next.

HTML forms : Can be viewed on mobile and desktop. Can be signed using scribble or esign service.

Adaptive forms : Dynamically changes as per user inputs. Reusable XML templates to create the form.

All form types support the following features:

• Dynamic layout
• Form field validation
• Context-sensitive Help
• Scripting and XML data handling
• Accessibility design and checking
• Ability to save forms on the server-side
• Support for file attachments
• Integration with HTML Workspace for Data Capture

Forms workspace can be used to save the data offline and the data can be synchronized the next time you're online.

Forms can be used for personalized communication

Forms can be created using :

1. Form data model : RDBMS data table rr similar database system.
2. XDP form template : If you already have XDP form, those can be converted to AEM forms easily.
3. XSD Schema or Json : Structure of the form can be determined using xsd or json
4. Without a form model

guideContainer is the root of the form. This component can have following nodes

• Mobile UI
• Thank you page
• Submit action
• Styling

rootpanel is the main panel inside which there can be subpanels

toolbar can be attached to the form

assets contains additional information regarding form.

Automated form conversion service helps in converting pdf forms to adaptive forms.

Interactive communication : 

Interactive Communications centralizes and manages the creation, assembly, and delivery of secure, personalized, and interactive correspondences such as business correspondence, documents, statements, marketing mails, bills, and welcome kits. Interactive Communications can be delivered using two channels: Print and Web.

Building blocks of interactive communication are data model, document fragment, templates.

Interactive communication can be created using forms console on author.

Interactive communication can be sent over email by configuring email client.

AEM forms reference collaterals : Reference site for the form.

Deployment topology for AEM Forms : 

AEM forms architectural components :

• AEM services
• Forms Sevices
• Web layer for authoring, rendition creations, submissions and REST API

AEM Forms can be be on OSGI or JEE

AEM Forms authoring user interface does not support creating Document of Record (DOR), PDF Forms, and HTML5 Forms. Such assets are designed using the stand-alone Forms Designer application and uploaded individually to AEM Forms Manager.

There can be three instances for AEM forms - Author, Publish and Processing. On processing instance no user is assigned to forms manager. This ensures only processing of the forms happen on this instance. Which can be processing raw forms data arriving from a publish instance and secure storage for the forms data. Post processing and HTML workspace hosting can be there. HTML workspace hosting is used for review and approval of the forms.

Processing instance takes the data from publish using reverse replication so it is configured as author instance. It also utilizes the AEM workflows.

Please read here for 5 recommended topologies 

Choosing persistence type for for and AEM forms installation : MongoMK or RDBMK

Synchronization scheduler for assets

AEM DS Setting service configuration is required for adaptive forms when the forms are submitted from publish instance.

Adaptive forms cache can be useful to retrieve previously filled data and to reduce the loading time of a form.

AEM forms can be connected to LiveCylce and connection to microsoft sharepint happens through livecycle connector.

AEM Desktop app to connect to AEM forms. Desktop app uses webdav to connect to AEM instance.

Forms user groups - forms-user, forms-power-user, forms-submission-reviewers, template-authors, fdm-authors, workflow-editors, workflow-users, fd-administrators.

Add non supported locale for forms using following

• Add a locale to the GuideLocalizationService service
• Add XFA client library for a locale
• Add adaptive form client library for a locale
• Add locale support for the dictionary
• Restart the server