LHH-22704 – The login form is not working (stability & UX improvement)

• What was the issue?
  Some users encountered a non‑functional or unreliable login form, preventing them from signing into HOC4 as expected.
• What was solved?
  We fixed the underlying issues affecting the login form, improving its reliability and user experience.
  Result: Users can log in more consistently, reducing friction at the very first step of using the system.

LHH-22665 – Sync Account > Organization Logo across systems

• What was the issue?
  Organization logos stored in Salesforce (via the Organization Logo field) were not consistently reflected in HOC4 where logos are shown (such as in listings or public‑facing blocks).
• What was solved?
  We added and refined synchronization logic so that the Organization Logo can be used reliably in the HOC4 experience.
  Result: Organization branding is more consistent across HOC4, helping partners and agencies present a professional, recognizable presence.

LHH-22452 – Time zone feature in the Form Builder’s Address component (Part II)

• What was the issue?
  Forms that rely on the Address component needed better, more reliable time zone handling—particularly when scheduling or storing time‑sensitive data connected to locations.
• What was solved?
  We enhanced the Address component’s time zone behavior so form builders can more accurately capture and use location-based time zones.
  Result: Time and location data collected through custom forms is more accurate, especially for customers with multi‑time‑zone operations.

LHH-22558 – Improve ability to add new records from a form picklist lookup

• What was the issue?
  When users were working with picklist/lookup fields in custom forms, it was not always clear or easy to add a new related record on the fly.
• What was solved?
  We improved the “add new record” behavior directly from picklist lookups so that users can create and select a new value in one smooth step.
  Result: Data entry is faster and less frustrating, particularly in workflows where new organizations, contacts, or values are frequently added.

LHH-22446 – Review the logic of the search service to retrieve the Organization Logo

• What was the issue?
  The search service did not always locate or display the correct Organization Logo in results or blocks that rely on it.
• What was solved?
  We adjusted the search logic so that it reliably finds and uses the right logo field for organizations.
  Result: Search‑driven blocks and pages now show organization logos more consistently.

LHH-22353 – Allow search result block to change layout similar to search result page

• What was the issue?
  The search result block on CMS pages had more limited layout options compared to the full search result page.
• What was solved?
  We expanded the search result block so it can use additional layouts, aligning it more closely with the full search result page.
  Result: Admins have more flexibility to present search results in layouts that best fit their page design.

LHH-22338 – Listings: make display formats compatible with object and page types

• What was the issue?
  Not all display formats in listing blocks worked well for every type of object or page, which could lead to inconsistent or awkward layouts.
• What was solved?
  We reviewed and updated which display formats are supported for specific object/page combinations, ensuring only feasible formats are shown.
  Result: Admins see more sensible options when configuring listings, and site visitors see cleaner, more appropriate layouts.

LHH-22337 – Include counters for ListView and SOQL sources

• What was the issue?
  When using ListViews or SOQL queries as data sources, admins lacked clear counters or indicators of how many records those sources returned.
• What was solved?
  We added counters so that when a ListView or SOQL source is used, admins can see how many records are being pulled.
  Result: It is easier to validate data sources and ensure listings and blocks are showing the expected number of records.

LHH-21789 – HOC4 Template – Get Connected version

• What was the issue?
  A HOC4‑ready version of the “Get Connected” template was needed to support certain implementations and designs.
• What was solved?
  We created a HOC4‑compatible Get Connected template to bring that layout and experience into the HOC4 environment.
  Result: Customers who are used to the Get Connected look and feel can now leverage a similar experience in HOC4.

LLH4v1.17.1 (Released: 01/29/2026)

This release fine‑tunes HOC4 forms, file uploads, and dependent fields, and makes it easier to enable the Skills feature via the activation module. The focus is on resolving specific customer‑reported issues that impacted configuration and data collection.

LHH-22746 – Trouble enabling Skills via open activation module

• What was the issue?
  Admins ran into problems when trying to enable the Skills feature using the open activation module—the process didn’t always complete correctly, and Skills wouldn’t turn on as expected.
• What was solved?
  We corrected the activation logic so that enabling Skills through the module reliably updates the necessary settings and components.
  Result: Admins can now enable Skills without workarounds, ensuring the related pages and forms are properly activated.

LHH-22721 – Not able to upload PPTX file on Opportunity in the portal

• What was the issue?
  Uusers could not upload PowerPoint (.pptx) files to Opportunities from the portal, even though these files were needed to share documents with volunteers or partners.
• What was solved?
  We updated the file upload validations and settings so that .pptx files are accepted in this context.
  Result: Portal users can now upload PowerPoint files to Opportunities as intended.

LHH-22718 – Custom form lookup field not working

• What was the issue?
  A lookup field on a custom form was not functioning correctly—it either failed to return options or did not properly link the selected record.
• What was solved?
  We fixed the lookup behavior for this scenario so that the field correctly searches for and associates related records.
  Result: The custom form can now be used as designed, with lookups performing reliably.

LHH-22703 – HOC4 dependent picklists on CMS forms

• What was the issue?
  Dependent picklists used on CMS-driven forms in HOC4 were not always honoring the parent/child relationship, leading to incorrect or incomplete options being displayed.
• What was solved?
  We corrected how dependent picklists are handled in CMS forms so that child options consistently reflect the selected parent value.
  Result: Form builders can rely on dependent picklists to collect accurate, filtered choices from users.

This release is focused solely on fixes and does not introduce new features.

LLH4v1.17.2 (Released: 02/03/2026)

This is a focused stability and CMS usability release. It fixes issues with custom-form contact creation, listing block chart settings, and a set of documented CMS problems for a specific client.

LHH-22769 – Custom Form: “Add New Contact” modal not accessible

• What was the issue?
  When filling out a custom form, users could not access or properly use the “Add New Contact” modal, preventing them from creating a new contact on the fly during form completion.
• What was solved?
  We repaired the “Add New Contact” modal so that it opens and functions correctly within custom forms.
  Result: Users can once again create and select a new contact directly from the form, streamlining data entry.

LHH-22745 – Listing Block: chart field values disappear when editing

• What was the issue?
  In CMS listing blocks configured to display charts, the chart-related field values could disappear when a user edited the block settings, forcing them to re‑enter configuration.
• What was solved?
  We fixed how chart configuration values are stored and reloaded so they persist correctly across edits.
  Result: Admins can safely update listing blocks without losing chart field settings, saving time and avoiding configuration mistakes.

LHH-22733 – CMS issues documented

• What was the issue?
  A group of CMS-related issues affecting their day‑to‑day management of content and pages.
• What was solved?
  We reviewed and addressed their documented CMS issues (such as layout glitches or field behaviors) as part of this release.
  Result: CMS administration is smoother and more reliable. All customers benefited from the underlying stability improvements.

This release is entirely focused on bug fixes and does not add new features.