This update significantly improves the Form Signature component to be more compatible with ESIGN (Electronic Signatures in Global and National Commerce Act) requirements. While we do not claim full ESIGN compliance, these changes allow us to capture the key information used by ESIGN to prove an e-signature's connection to the signed document.

A new checkbox labeled "Track transaction info (e.g., signer details, date/time, geolocation, and IP address)" has been added to the Signature component. This option is available only if the form requires the user to be logged in.

When this checkbox is selected, the following information will be captured upon a user signing the document:

• Signer details: User's full name and email address from their Contact record.
• Date/time: The exact date and time of the signature.
• Geolocation: City, state, and/or country of the signer.
• IP Address: The IP address of the user.

For geolocation data, the system primarily uses the Google Maps library. If this is not enabled in the browser, a free external service (ip-api.com) will be used.

Deployment to Production: March 20, 2025.

This update enhances the URL redirect functionality, allowing CMS Administrators to set up redirects that preserve query parameters and utilize wildcard replacements.

Previously, redirects had limited control over query parameters. Now, you can:

• Preserve Query String: Maintain existing query parameters from the original URL in the redirected URL.
• Wildcard Replacement: Use wildcards in redirect rules for more flexible URL matching.

Deployment to Production: March 20, 2025.

This update significantly improves the URL redirect feature, providing more robust and flexible options for managing website redirects. Building upon previous enhancements (related to LHH-20598), this release allows for more specific and complex redirection scenarios.

Key improvements include enhanced wildcard functionality, supporting:

• Simple Redirection: Redirecting one static URL to another (e.g., /brito-page to /calendar).
• Simple Wildcard: Redirecting a base URL and any trailing path (e.g., /zap-test/* to /zap-test-final/*).
• Advanced Wildcard: Handling redirects that involve specific segments within a URL (e.g., /opportunity-signup-team/*/Yes to /hoc-reserved-slots-sign-up-step-01/p/*).
• Multiple Wildcards (Maximum 2 tokens): Supporting redirects with up to two wildcard tokens for highly specific URL patterns (e.g., /opportunity-signup-team/*/Yes/*/test to /test-final-page/p/*/*).

These changes provide greater control over how URLs are redirected, improving site navigation and SEO.

Deployment to Production: March 20, 2025.

This update significantly improves the user interface for administrators when creating and managing filters and facets within the Listing Block. The previous separate "Dynamic Filters" and "Facets" interfaces have been consolidated for a more consistent and intuitive experience.

Key changes include:

• New "Location in Block" Setting: A new setting has been added to the facet configuration modal, allowing administrators to specify the display location of facets (Top, Left, or Right).
• Dynamic Filters Integrated into Facets: The standalone dynamic filter section has been removed. Existing dynamic filters will now be handled as facets with "Top" as their default location in the block.
• Refreshed Look and Feel: The overall appearance of facets for end users has been updated for a fresh and improved look.

These changes streamline the configuration process for filters, making it easier for administrators to create and manage powerful filtering options for their listing blocks.

Deployment to Production: March 20, 2025.

This update enhances the security and reliability of file uploads within forms. Previously, the system used a "blacklist" approach to prevent the upload of known problematic file extensions. While effective, this approach could be less comprehensive.

This improvement introduces a more robust "whitelist" validation method. Now, the system will check if the uploaded file's extension is among the explicitly allowed extensions configured for that specific "File" field in the Form Builder. This provides a more secure and precise control over acceptable file types.

All functionalities related to file uploads have been updated to incorporate these new validation parameters, ensuring that only appropriate files can be uploaded.

Deployment to Production: March 20, 2025.

This update addresses an issue where the reCAPTCHA widget was covering the "next" button on forms, preventing users from submitting. This problem was particularly prevalent on desktop and laptop displays, but could also affect mobile views.

To resolve this, the AccessiBe widget has been relocated to the left corner of the screen, and the reCAPTCHA widget has been moved further down to the right corner. These adjustments ensure that both widgets are positioned correctly across desktop, tablet, and mobile views, preventing them from obstructing crucial form elements.

Deployment to Production: March 20, 2025.

This update resolves an issue in the new Content Management System (CMS) layout where Advanced Registration System (ARS) pages were incorrectly labeled as being associated with the "main" layout, even when the old CMS layout correctly showed them associated with a "subset" internal layout.

The fix ensures that the ARS page now correctly reflects its association with the "subset" internal layout in the new CMS, providing accurate information for administrators.

Deployment to Production: April 3, 2025.

This update resolves an issue where administrators were unable to edit pages in the new Content Management System (CMS) layout, particularly affecting forms configured as Advanced Registration System (ARS) items. The "edit" button was hidden by the "move" functionality, and converting to the old CMS layout would cause all edit options to disappear. This problem was reported on several sites.

The fix addresses the issue by ensuring that the edit button for pages, HTML editors, waiver blocks, and forms (configured as ARS items) in the new CMS layout correctly redirects to the ARS configuration interface, which has a specialized interface for setup.

Deployment to Production: March 20, 2025.

This update resolves a bug in the image slider where the "Auto Play" setting would unexpectedly disable if a user hovered their mouse over the slider or clicked on an image. This prevented users from seeing all images in the slider without refreshing the page.

A bug in the underlying library has been identified and the library version has been updated to fix this issue. The image slider's autoplay functionality will now work as intended, providing a smoother user experience.

Deployment to Production: March 24, 2025.

This update resolves a bug that occurred when attempting to save the Form Builder within the Advanced Registration System (ARS) in the new CMS Layout. Previously, administrators encountered issues preventing successful saves.

This fix addresses the underlying problem, ensuring that you can now reliably save changes made to forms within the ARS using the new CMS Layout.

Deployment to Production: March 24, 2025.