LLH4v1.16.0 (Released: 01/21/2026)

Overview

This release focuses on improving clarity and control for admins and staff working with email templates and data mapping. It adds better tools for managing Lightning Email Templates and strengthens how SSO and field mappings are handled behind the scenes.

🐞 Bug Fixes

LHH-22614 – Improve Lightning Email Template usability

• What was the issue?

• Admins working with Lightning Email Templates had limited visibility and control over how templates were being used. This made it harder to troubleshoot when the “wrong” email was sent or to understand how template selection was working.

• What was solved?

• We enhanced the logic and supporting tools around Lightning Email Templates so that:
  • Template selection behavior is more predictable and consistent.
  • It’s easier to confirm which template is in use for a given notification.
  • The system avoids edge cases that could cause the wrong template to be selected.

LHH-22511 – Clarify behavior around template and configuration changes

• What was the issue?

• Certain configuration changes related to emails and templates could have side effects that were not obvious, leading to confusion or unexpected behavior.

• What was solved?

• We refined how the system interprets these settings and adjusted supporting logic so that configuration changes produce more intuitive, consistent results.
• Result: Admins are less likely to encounter surprises when updating configuration, and email-related behavior is more in line with expectations.

LHH-21781 – Improve internal handling of template and notification rules

• What was the issue?

• The internal rules and code for handling templates and notifications had grown complex over time, making some behaviors harder to predict or adjust.

• What was solved?

• We cleaned up and streamlined the internal logic to make it easier to maintain and less error-prone.
• Result: The notification system is more stable and predictable for admins and staff, and it is better positioned for future enhancements.

🆕 New Features

None of the issues in LLH4v1.16.0 were classified as new features. This release is entirely focused on reliability and admin experience improvements around templates and configuration.

 

LLH4v1.16.1 (Released: 02/11/2026)

Overview

This release improves the partner and volunteer experience in HOC4 by fixing layout and usability issues in date/time pickers, ensuring partner staff land on the right dashboard, and strengthening visual settings and SSO field mapping. It also includes a customer-specific fix to prevent date parsing errors.

🐞 Bug Fixes

LHH-22609 – Partner Staff cannot cancel D&TS future occurrence

• What was the issue?

• Partner staff were unable to cancel certain future “Done & Time Scheduled” (D&TS) occurrences, even though they should have had permission to do so. This blocked them from managing their own schedules.

• What was solved?

• We corrected the permissions and logic that control cancellation for future D&TS occurrences from the Partner Portal.
• Result: Partner staff can now cancel eligible future D&TS occurrences as expected, giving them proper control over their events.

LHH-22559 – Visual Settings oversight

• What was the issue?

• Some visual settings changes (such as branding or style updates) were not being fully applied or recognized by the system, leading to inconsistencies between what admins configured and what users actually saw.

• What was solved?

• We fixed gaps in how visual settings are read and applied so that updates are consistently reflected in the UI.
• Result: Branding and design changes made in Visual Settings now appear reliably, giving sites a more consistent look and feel.

LHH-22412 – Calendar picker icon covered by time field (DomusVi)

• What was the issue?

• On certain pages for DomusVi, the calendar picker icon was partially or fully covered by the time field. This made it difficult for users to click the date picker and select a date, hurting usability.

• What was solved?

• We adjusted the layout and styling for the date/time inputs so the calendar icon is clearly visible and clickable.
• Result: Users can easily open the date picker, improving the overall experience when scheduling or editing occurrences.

LHH-22488 – “String was not recognized as a valid DateTime” (Endesa)

• What was the issue?

• Endesa encountered errors where certain date/time values were not recognized as valid, causing failures with messages like “String was not recognized as a valid DateTime.”

• What was solved?

• We updated the date/time parsing and handling logic to better support the formats and data patterns used by Endesa, preventing these errors.
• Result: Date/time values are now processed correctly for Endesa, reducing errors and improving stability.

🆕 New Features / Enhancements

LHH-22650 – Add font to Visual Settings

• What was the issue?

• Admins had limited options for customizing the site’s font via Visual Settings, which constrained branding and design flexibility.

• What was solved?

• We expanded Visual Settings to support an additional font option, allowing admins to better align their HOC4 site with their organization’s brand guidelines.
• Result: Sites have more control over how text looks, creating a more on-brand and polished experience for volunteers and partners.

LHH-22549 – Partner Staff should be redirected to Partner Dashboard, not volunteer account

• What was the issue?

• After logging in, Partner Staff were sometimes taken to the volunteer-facing account area instead of their Partner Dashboard, adding extra clicks and causing confusion.

• What was solved?

• We updated the post-login routing rules so Partner Staff are correctly redirected to the Partner Dashboard.
• Result: Partner Staff land where they need to work immediately, streamlining their daily tasks.

LHH-21995 – Allow an SSO field to map to multiple fields

• What was the issue?

• Previously, a single SSO attribute could only be mapped to one field, which limited how organizations could reuse the same data across multiple fields in the system.

• What was solved?

• We enhanced the SSO mapping capability to allow a single SSO field to be mapped to multiple internal fields.
• Result: Organizations have more flexibility in how they use SSO-provided data, making integrations more powerful and reducing duplicate configuration work.