Charting new frontiers in digital engagements

Gov Client - AEM Forms

 
AppealsForm_censored.jpg

As various governmental agencies look to modernize their online forms experience and move off of desktop only form types such as PDF and MS Word, they often turn to AEM and leverage the Adaptive Forms module. This takes the form experience off of a file and on to the browser, with a mobile responsive interface. This centralizes the form fill in process, allowing their end-users to access it from any device with a browser, and offers a seamless experience regardless of screen size. A single form for all devices. This means a single asset for all devices, and thus a single dev cycle. We’ve consistently leveraged AEM Forms in this way to provide a simple, consistent forms experience to our clients’ end-users.

We’ve worked with several government agencies to successfully deploy their forms using AEM. We were able to convert their existing form assets from PDF, MS Word/Excel, etc to the AEM platform and create custom dynamic workflows to automate the data processing and approval processes that were previously done manually.

In order to ensure the forms are easy to find, our team also customized and styled a forms portal to give end-users a simple interface to locate the form they need to fill given their current needs.

Our solutions have also leveraged AEM’s:

  • Data Ingestion API’s to prepopulate as much of the form as possible, saving time for end users

  • Validation Schemas to sanitize user input

  • Third Party Integrations to push and pull data from other systems while users are filling in a form

  • Digital Signatures to ensure an entirely digital flow without the need for printing, applying a wet signature, scanning and emailing

  • PDF Data Merging for secure storage and archiving

2-DBarcode.jpg

With PDF data merging, we ensure that all data ends up in a file format that is secure and easy to store long term.

So while the form fill in process is done in an engaging, adaptive, browser based interface, the data ends up merged into a safe file type that is easy to read and archive when the process is complete! It’s the best of both worlds!

PDFSignatureCert.jpg

By introducing Digital and Electronic Signatures into our workflows, end users no longer have to print the form, sign it manually, scan it and send it back. We effectively removed 4 annoying steps from any form fill-in process!

Still need a wet signature? No problem - we also added a 2-D barcode that can be scanned to digitize the form’s data so at least on your end, there is no more data re-entry!

 

Banking Client - AEM Sites

 
 
Branch Detail Page

Branch Detail Page

Branch Search Page

Branch Search Page

Branch Location Details and Search

Client had hundreds of branches that each needed:

  • Their own detail page

    • Created an Editable Template that allowed certain Authors to adjust the layout of all Location Detail Pages.

    • Authors could create new Location Detail pages using that template to populate the location’s data while ensuring a consistent look and feel

  • To be searchable in AEM

    • Integrated with Google Maps API’s and converted each location address to its associated lat/long coordinates

    • Created an algorithm that leveraged those stored locations’ lat/long coordinates and an address inputted by the end user to perform proximity searches

    • Closest results then get displayed in line and as pins on an interactive Google Map

  • Pushed to Google Maps and Google My Business

    • Used a 3rd party location service that could push data to Google Maps

    • Integrated with their API’s to gather all locations’ data as inputted by Authors

    • Created an automatic trigger to initiate a push to the location service

    • As Authors make changes to these Location pages via our custom templates and components, this triggers updates to the location service while therefore keeps our site and Google Maps in sync


Multiple Layouts, Same asset

  • Article search page had different layouts for result cards, some with portrait and some with landscape thumbnail images

  • The same article could show up in either a landscape or a portrait slot

  • Client wanted the same asset to be used in both layouts but it was hard to predict how it would scale in such different orientations

  • Solution: Created an interface to arrange the image for each orientation

Screen Shot 2020-05-25 at 5.17.24 PM.png

Interface to arrange the image for each layout to predict exactly how it will render without needing a second asset.


Account Comparison Table

  • Client wanted a visual way to compare different types of Accounts. We needed:

  1. A way for them to Input Account Details and associate them with a particular Account Type

  2. An interface for end-users to see all available Account Types and select which ones they wished to compare

  3. Logic to pull the details from the selected accounts and display them in a table

  • In order to fulfill the aforementioned requirements, we:

  1. Account Type page template with customized Page Properties that can capture Account Details in its metadata. This template is used to create a page for every account type and to input its details.

  2. Created a custom component that finds Account Type pages created with the aforementioned template and lists them as summary panels (left screenshot below) for the end-users to select which accounts they wish to compare.

  3. Component will automatically pull the details from the selected Account Type pages’ properties (metadata) and stack them side by side in an easy to understand table (right screenshot below)

  • This centralizes the Account Details on their respective Account Type page. Anywhere that page is referenced, the same details will be available to be displayed to the end user and modifying that one location updates all references. This ensures consistency, simplifies authoring, and provides an intuitive interface for the end user.

End user can select which accounts they want to compare. Each panel points to an Account Type page that holds its Account Details in its metadata.

End user can select which accounts they want to compare. Each panel points to an Account Type page that holds its Account Details in its metadata.

Component will gather the Account Types that the user selected (in the previous screenshot), pull the Account Details from their page’s metadata and generate a table with them, outlining the information and differences for each.

Component will gather the Account Types that the user selected (in the previous screenshot), pull the Account Details from their page’s metadata and generate a table with them, outlining the information and differences for each.