Agreement Express Release Notes
The 22.02 Release is scheduled for deployment to US Production on February 16th, 2022. Updates will be available in your production environment on February 17th, 2022 unless otherwise noted. Included in this release will be net-new features in addition to enhancements to current features you may already be familiar with. Please reach out to your Customer Success Manager (CSM) should you have any questions about features in this release and their impact on you or your end clients! The Release to Canadian Production will be on Friday, February 18th.
Google Chrome Auto-Fill Removal
Description: We've disabled browser auto-population (ie, Google autofill) for Signing Documents. This change was made in response to feedback from our customers who wished to increase data privacy and predictability during data entry. As an individual populating a Signing Document (ie, all roles - Recipient, Publisher, Company Admin), you wish to ensure that the data populated on your forms are accurate and complete. Oftentimes browser Autofill incorrectly detects fields on the forms to populate and data is overridden erroneously or populated without intention. This fix will cover the majority of use cases, and you should only see the occasional field arise, this fix confirms no overwriting of data occurs.
Who is impacted? End-client signers and Publishers, as this fix will improve the integrity of all signing documents used in Agreement Express.
Is any Action Required? No, this fix will automatically be deployed to your Production Environment. If your company prefers to offer browser auto-population it can be manually enabled for you. Just reach out to our Support team for details.
Increasing Landing Page Speed
Description: After obtaining feedback that some landing pages had very slow load times, we made some changes to enhance the Landing Page performance. Most notably, a user should see an increased speed when using the “Next” and “Save” functions.
When you click on the Next button to move to the next landing page, the new page will load much faster. On the new page you may see the Next button disable with the spinner (see below). The system is processing some background processes. Once the processing is complete, the Next button will become enabled again. The idea is that the user will enter data while the next button is disabled and by the time they have finished the next button will be enabled. In the future we will be enhancing/improving the backend processes so that the time that you see the disabled next button will be reduced.
Who is Impacted? All users will benefit from this enhancement to increase the performance of landing pages.
Is any Action Required? No, this fix is automatic and will be in your production environment immediately.