Demo overview terms legend

  1. Impersonate: Defined Users & Groups in AEM demo.

  2. Button: Colored rectangle or circled arrow for navigating.

  3. Click: To run an action in the user story.

  4. Links: At the top of the main menu in We.Gov site.

  5. User Instructions: A set of numerical steps to follow when navigating through the user’s story.

  6. Forms Portal: https://<aemserver>:<port>/content/we-gov/formsportal.html

  7. Mobile View:We.Gov user to replicate a mobile view with a resized browser.

  8. Desktop View: We.gov user to view demo on a laptop or desktop.

  9. Pre-screener Form: Form on the Home page of the We.Gov site.

  10. Adaptive Form: Enrollment application form for We.gov demo.

    https://<aemserver>:<port>/content/forms/af/adobe-gov-forms/enrollment-application-for-health-benefits.html

  11. Adobe We.Gov Site: https://<aemserver>:<port>/content/we-gov/home.html

  12. Adobe Inbox: Located top menu bar Bell icon in AEM backend.

    https://<aemserver>:<port>/aem/start.html

  13. Email Client: Preferred way to view your emails (Gmail, Outlook)

  14. CTA: Call to action

  15. Navigate: To locate a specific reference point on the browser page.

  16. AFC: Automated Forms Conversion

Automated Forms Conversion (Camila)

This section: Camila the CX Lead has an existing PDF based form that was used as part of a paper-based process. As part of a modernization effort Camila wants to use this PDF form to automatically create a modern Adaptive Forms.

Automated Forms Conversion - We.Gov (Camila)

  1. Navigate to https://<aemserver>:<port>/aem/start.html

  2. Login with:

    • User: camila.santos
    • Password: password
  3. From the main page, select Forms > Forms & Documents > AEM Forms We.gov Forms > AFC.

  4. Camila uploads the PDF to AEM Forms.

    Upload form

  5. Camilla then selects the PDF form and clicks Start Automated Conversion to start the conversion process. You may need to click Overwrite conversion if you have converted the form.

    NOTE
    The settings in AFC are preconfigured for the end user which means that they should not be altered.
    • Optional: If you wish to use the Accessible Ultramarine theme, simply click the Specify an adaptive form theme and select the Accessible-Ultramarine theme that appears in the list of options.

    Start conversion

    Ultramarine theme

    The percentage complete status displays during conversion. Once the status displays Converted, click the output folder, select the adaptive form and click Edit to open the converted form.

  6. Camilla then reviews the form and makes certain that all fields are present

    Review conversion

  7. Camilla then starts to edit the form and selects Root Panel > Edit (the wrench) > selects Tabs on Top from the Panel Layout dropdown menu > selects the Check box.

    Review properties

  8. Camilla then adds all the necessary CSS and field alterations to produce the final product.

    Add CSS

Form Data Model & Data Sources (Camila)

This section: After the document is converted and produces an Adaptive Form, Camila must connect the Adaptive Form to a datasource.

  1. Camila opens the Properties on the form that was converted in Automated Forms Conversion - We.Gov.

  2. Camila then selects Form Model > Selects Form Data Model from Select From dropdown > Selects We.gov Enrollment FDM from the list of option.

  3. Click Save & Close.

    FDM selection

  4. Camila clicks the output folder, selects the adaptive form, and clicks Edit to open the completed We.Gov form.

  5. Camila selects an adaptive form field and clicks Configure icon and creates binding with the form data model entities using the Bind Reference field. Camila repeats this step for all fields in the adaptive form.

Form Accessibility Testing (Camila)

Camila also validates that the created content is built correctly and fully accessible according to corporate standards.

  1. Camila clicks the output folder, selects the adaptive form, and clicks Preview to open the completed We.Gov form.

  2. Opens the Audit tab within the Chrome Developer Tool.

  3. Performs an Accessibility check to validate the adaptive form.

    Accessibility check