The Drafts & Submissions Component is used to display forms that are saved as drafts for completing later and submitted forms.
To add the Drafts & Submissions component, you can either drag and drop it from the Components pane or select it from the Insert New Component dialog. To configure it, select the component and click on the Configure icon. Specify the title for the form listing, choose between draft or submitted forms, and select the desired format (card or list).
Users interact with the Search & Lister Component by using it to list adaptive forms on a page and to implement search functionality for the listed forms.
To configure the Search & Lister component, select the component and click on the Configure icon. In the Display tab, specify the component title, layout format, and optionally hide search and sorting features. In the Asset Folder tab, define the folder location from where forms are listed. In the Results tab, set the maximum number of forms to display per page.
The Link Component allows users to provide links to adaptive forms on a page. To configure it, select the component and click on the Configure icon. In the Display tab, provide the link caption and tooltip. In the Asset Info tab, specify the repository path where the asset is stored, and in the Query Params tab, specify additional parameters in key-value pairs.
To configure asynchronous form submission using Adobe Sign, open an Adaptive Form in edit mode, select the Properties icon, and expand the ELECTRONIC SIGNATURE option. Enable Adobe Sign and configure the Submit Form action to trigger after every recipient completes the signing ceremony.
Forms can be saved as drafts by creating a "Save Form" rule on a form component (e.g., a button) or by enabling the Auto-Save feature. The "Save Form" rule triggers when a button is clicked, while the Auto-Save feature saves the form automatically based on predefined events or time intervals.
To create a "Save Form" rule, open an Adaptive Form in edit mode, drag the Button component to the form, configure the button to trigger the rule, open the Rule Editor, create a rule with "is clicked" as the trigger and "Save Form" as the action, and save the rule.iuytre.
To enable Auto-Save, open an Adaptive Form in edit mode, select the Properties icon, and expand the AUTO-SAVE option. Enable the checkbox to enable auto-save and configure the Adaptive Form Event to trigger auto-save based on events or time intervals.
Creating accessible adaptive forms in AEM involves ensuring that the forms are perceivable, operable, understandable, and robust for all users, including those with disabilities. Key considerations include providing text alternatives for non-text content, ensuring keyboard accessibility, organizing content in a logical structure, and using semantic markup.
Text alternatives for non-text content can be provided by using descriptive alt attributes for images, captions or transcripts for multimedia content, and descriptive labels for form fields. This ensures that users with disabilities who may not be able to perceive the non-text content can still understand its purpose and meaning.
Keyboard accessibility in adaptive forms can be ensured by ensuring that all form elements are accessible via keyboard navigation, using appropriate focus styles to indicate the currently focused element, and ensuring that interactive elements such as buttons and links are operable using the keyboard alone.
The purpose of integrating AEM Forms with Adobe Analytics is to collect and analyze data about how users interact with forms and documents. This integration allows organizations to gain insights into user behaviour, form completion rates, and the effectiveness of their forms and documents. These insights can then be used to improve the user experience, optimize form design, and make data-driven decisions.
AEM Forms integrates with Adobe Analytics through the use of Adobe Experience Manager Forms SDK and Adobe Analytics integration tools. These tools enable the collection of form data, such as submission times, user interactions, and form completion rates, which can then be sent to Adobe Analytics for analysis. The integration also supports the tracking of document interactions, such as downloads and views, providing a comprehensive view of user engagement with forms and documents.