HOC Release Notes 3.0.10.83 (May 25, 2023)

This release provides under the hood improvements to make HOC public sites operate more efficiently when interacting with Salesforce. It also provides some bug fixes and new features as described below:

New Features

Listing Block ability to add text and actions to the listing block (HOC3-16539)

This new features allows us to add HTML text after the Listing Block title. This feature will be useful when a button is needed to create a new record from a Listing Block or when additional text is needed. There is a new section called "Pre content" in the Listing Block Settings that will be used to add this HTML content.

In the image below you'll notice the text added in the Pre Content section appears directly below the Listing Block title.

Users can also use special tokens for query string, URL and session parameters in the Pre Content section.

Additionally, a new option was added to the HTML Editor to enable users to insert a button with a dynamic URL action using special tokens. This means the button can use values from the list view associated with the Listing Block.

This feature solves the problem of needing multiple Listing Blocks when displaying data in a table or calendar and also needing an option to add text or actions (create records). Currently, this feature is only available to HOC Staff.  It will become public to all CMS Admins at a later date.

Improved Waitlist Logic with Spots Available (HOC3-17463)

Added logic and improved the validation so our service now checks the number of remaining volunteer spots and the guest volunteer number. This prevents a connection from exceeding the available spots. If a volunteer tries to include more guests than available spots, an error message will appear.

Bug Fixes

Cannot save payment processor field (HOC3-17566)

Fixed an issue that prevented a CMS Admin from saving a form when a payment amount was deleted.

Custom Forms: Location component not working for addresses outside this US (HOC3-17549)

Fixed an issue that caused the address component in custom forms to only work within the United States.

0 Comments

Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.