LLH4v1.21.0 (Released: 03/18/2026)

Overview

This release fixes a volunteer signup success page displaying inaccurate spots remaining, a dropdown display error when selecting multiple populations, a page layout issue, a login header block editing issue, and a CMS gallery template popup typo. It also introduces a CMS data migration tool (Part II), AI-assisted automation for Salesforce picklist translation, a mass CMS block translation feasibility study, redesigned CMS configuration screens for Content Types and Page Settings, custom fonts for a customer, and a review of the HOC4 form data export process.

🐞 Bug Fixes

LHH-22894 – Signup Success Page Showing Incorrect Spots Remaining

• What was the issue?

• After a volunteer signed up for an opportunity, the success page displayed the total number of spots (e.g., 50) rather than updating to reflect the remaining spots (e.g., 49). Because the underlying trigger updates only every 5 minutes, the spots remaining shown on this confirmation screen was inaccurate and caused confusion.

• What was solved?

• We adjusted the success sign-up page so that it no longer displays the spots remaining count in a context where real-time accuracy cannot be guaranteed.

Result: The volunteer signup success page no longer shows misleading spots remaining data.

LHH-22990 – Error When Selecting Multiple Populations in Dropdown

• What was the issue?

• Partners were receiving an error when selecting 3 populations while creating an opportunity in the portal, even though the configuration allowed it. The issue only occurred when using the Dropdown display type; switching to Checkboxes worked correctly.

• What was solved?

• We fixed the Dropdown display type logic so that it properly handles multi-select population values without triggering an error.

Result: Partners can now select multiple populations using the Dropdown display type without errors.

LHH-22950 – White Space Appearing Below Footer

• What was the issue?

• A customer's page displayed a large white section below the footer that could not be adjusted or removed through the CMS.

• What was solved?

• We identified and removed the excess white space below the footer on the affected page.

Result: The page now displays correctly without the extraneous white space below the footer.

LHH-22973 – Login Header Block Cannot Be Edited

• What was the issue?

• The login header block in the CMS was not editable — the edit icon (pen and pad) could not be clicked, preventing administrators from making changes.

• What was solved?

• We fixed the login header block so that the edit icon is properly clickable and the block can be modified as expected.

Result: Administrators can now click the edit icon on the login header block and make changes.

LHH-22981 – Typo in CMS Gallery Template Popup

• What was the issue?

• When templates were added from the CMS gallery to a site, the confirmation popup contained a typo: "Worflow" instead of "Workflow."

• What was solved?

• We corrected the typo in the popup message.

Result: The CMS gallery template popup now correctly displays "Workflow."

🆕 New Features / Enhancements

LHH-22958 – CMS Data Migration Tool from HOC3 to HOC4 (Part II)

• What was the issue?

• The initial migration tool covered basic data transfer, but additional work was needed to handle more complex CMS data structures when migrating from HOC3 to HOC4.

• What was solved?

• We completed Part II of the CMS data migration tool, extending its capabilities to handle additional data types and structures.

Result: The migration tool now supports a broader range of CMS data for HOC3-to-HOC4 transitions.

LHH-22955 – AI-Assisted Automation for Salesforce Picklist Translation and Language File Processing

• What was the issue?

• Translating Salesforce picklist values and processing XLF language files was a manual, time-consuming process.

• What was solved?

• We researched and implemented an AI-assisted automation workflow for translating Salesforce picklist values and processing XLF files, significantly reducing the manual effort required.

Result: A streamlined, automated approach is now available for Salesforce picklist translation and XLF file processing.

LHH-22938 – Evaluate Mass Translation of CMS Block Items

• What was the issue?

• A customer needed a straightforward method for mass translation of CMS block content, including HTML blocks, block titles, block labels, and menu labels.

• What was solved?

• We completed a feasibility evaluation for mass translation of CMS block items, identifying which item types (text-only items like menu labels, form labels, block titles) can be translated in bulk and outlining a potential built-in translation feature for future CMS blocks.

Result: A validated approach and scope for mass CMS block translation is now documented, enabling future implementation.

LHH-22960 – Redesigned Content Type Configuration Screen

• What was the issue?

• The Create Content Type configuration screen needed a redesign to prioritize frequently used settings and apply updated styles consistent with recent CMS improvements.

• What was solved?

• We reorganized the Create Content Type configuration screen, prioritized essential settings, applied new styles, and reduced the prominence of rarely used options.

Result: Admins can now configure Content Types more efficiently with a cleaner, more intuitive interface.

LHH-22961 – Redesigned Page Settings Configuration Screen

• What was the issue?

• The Create Page – Page Settings configuration screen needed updating to match the new CMS block layout design standards.

• What was solved?

• We redesigned the Page Settings configuration screen, reorganizing settings by priority and applying the updated visual styles.

Result: The Page Settings screen now has a cleaner, more intuitive layout consistent with other CMS blocks.

LHH-22944 – Review Form Data Export Functionality in HOC4

• What was the issue?

• A review was needed to determine if the HOC4 form submission export process properly handles large data volumes through batch processing, to prevent recurring 500 errors during export.

• What was solved?

• We reviewed the form data export functionality and confirmed it incorporates batch processing to handle large volumes, preventing the errors seen in HOC3.

Result: The HOC4 form data export process has been verified to handle large volumes reliably.

 

LLH4v1.21.1 (Released: 03/20/2026)

Overview

This release fixes a critical partner registration failure caused by duplicate Salesforce Composite API reference IDs, a Packaging Manager UI issue that swallowed installation error messages, a form builder setting that failed to persist the redirection toggle, and a form where global-level changes were not saving correctly. It also resolves timezone inconsistencies across listing blocks and forms, and fixes a SOQL service that failed when the WHERE clause was lowercase.

🐞 Bug Fixes

LHH-22997 – Partner Registration Failing When Adding Multiple Contacts

• What was the issue?

• When submitting the Organization Registration form with both a Primary Contact and an Opportunity Coordinator, the Salesforce Composite API transaction was rolled back. The root cause was that the system generated two subrequests with the same internal reference ID, and Salesforce requires unique references, causing the full transaction to fail.

• What was solved?

• We replaced the per-contact processing with a single consolidated request that collects all contact lookup fields into one update, emitting the reference only once.

Result: Partner registration forms with multiple contacts now submit successfully without transaction rollbacks.

LHH-23005 – Package Installation Errors Not Displaying Correctly

• What was the issue?

• When a package deployment failed, the Packaging Manager UI displayed a "View Errors" link, but the error message was unreadable due to malformed HTML caused by improperly escaped characters in the error payload. Users could not see the actual failure reason.

• What was solved?

• We corrected the HTML escaping logic so that installation error messages are properly rendered, readable, and actionable in the UI.

Result: Package installation errors now display correctly with readable, properly formatted messages and clickable links.

LHH-23007 – Form Redirection Setting Not Saving

• What was the issue?

• In the form builder, the "Will have form redirection?" setting was configured and enabled, but when the form was updated/reopened, the setting displayed as off despite having been saved.

• What was solved?

• We fixed the setting persistence logic so that the redirection toggle correctly reflects its saved state when the form is reopened for editing.

Result: The form redirection setting now persists correctly across saves.

LHH-23008 – Global Admin Form Changes Not Saving

• What was the issue?

• When logged in as a global admin and making changes to forms, the changes were not saving correctly. The redirect button appeared disabled from the admin's view (while the dev team saw it as enabled), and profile selections were showing inconsistently.

• What was solved?

• We corrected the form save logic so that global-level changes are properly persisted and displayed consistently across all user views.

Result: Global admin changes to forms now save correctly and display consistently.

🆕 New Features / Enhancements

LHH-23003 – Consistent Timezone Display Across Listing Blocks and Forms

• What was the issue?

• On a multi-timezone-enabled instance, the timezone display was inconsistent across different pages. Some listing blocks and forms showed the timezone correctly while others did not, creating confusion for administrators managing opportunities across time zones.

• What was solved?

• We standardized the timezone display across all listing blocks and forms so that the opportunity's configured timezone is consistently shown.

Result: Timezone information is now displayed consistently across all listing blocks and forms, eliminating confusion for multi-timezone instances.

LHH-23011 – SOQL Dropdown Service Now Handles Case-Insensitive Queries

• What was the issue?

• The SOQL dropdown service failed when the WHERE clause was written in lowercase. Additionally, the dropdown did not retrieve options correctly when the returned attribute differed from the standard ID record.

• What was solved?

• We updated the service to handle the WHERE clause in a case-insensitive manner and to correctly process non-standard returned attributes.

Result: SOQL-powered dropdowns now work correctly regardless of the case used in the WHERE clause and with non-standard return attributes.

 

LLH4v1.21.2 (Released: 03/27/2026)

Overview

This release fixes a critical blocker where users could not complete email verification due to invalid/expired verification codes, and resolves an issue where the "Add New Occurrence" form pulled the default number of volunteers from the parent opportunity instead of the form's own default. It also adds support for timezone handling with multiple location fields in forms.

🐞 Bug Fixes

LHH-23033 – Cannot Complete Email Verification During Registration (Blocker)

• What was the issue?

• Users attempting to verify their email address during registration were encountering errors. After entering the verification code, the application displayed an error screen and closed immediately. On subsequent attempts, the system reported the code as invalid or expired, even though insufficient time had passed for expiration. This prevented users from completing registration and accessing entities.

• What was solved?

• We identified and resolved the issue in the verification code validation flow that caused the application to crash on the first attempt and incorrectly flag the code as expired on subsequent attempts.

Result: Users can now successfully verify their email addresses and complete the registration process without encountering errors or false expiration messages.

LHH-23050 – New Occurrence Showing Incorrect Default Number of Volunteers

• What was the issue?

• When adding a new occurrence through the partner portal, the "Number of Volunteers" field was pre-populated with the default value from the parent Volunteer Opportunity instead of using the form's own default value. This caused incorrect volunteer counts on new occurrences.

• What was solved?

• We corrected the form logic so that the "Number of Volunteers" field uses the form's configured default value rather than inheriting it from the parent opportunity.

Result: New occurrences now correctly display the form's default number of volunteers rather than the parent opportunity's default.

🆕 New Features / Enhancements

LHH-23123 – Timezone Support for Forms with Multiple Location Fields

• What was the issue?

• Three ride models select a standard location, but one model requires entering a starting and ending address using a different location field. The timezone logic for date/time fields in forms only supported a single default location field, so forms using the alternative location field did not display the correct timezone. Additionally, the "Ride Location" field was not appearing in edit mode for some forms.

• What was solved?

• We configured the timezone logic to support two different location fields, allowing the start/end date and time with timezone to work correctly regardless of which location field is selected. We also resolved the visibility issue with the Ride Location field in edit mode.

Result: Forms now correctly handle timezone calculations when either the default location or the alternative location field is used, and the Ride Location field displays properly in edit mode across all relevant forms.