HOC 3 Release Notes 3.0.6.12 (July 26, 2018)

This release has a number of under-the-hood performance improvements and reliability enhancements. It also includes improvements to the Linked In login/registration Beta,

CMS: Intro text on calendar page can now be edited (HOC3-7562)

In response to the continued requests we get to allow modification of text on system pages - we've added yet another page that can have introductory text customized in the CMS:  The /Calendar Page and the /Search page.

By default, the following text appears on the /Calendar page:

 

To change the text, click on the edit icon for the block which opens the Calendar Block Settings page.

On this page, you can set which filters do or don't appear on the page, and NOW, in addition, you can enter your own text which will replace the default text.

To return to the default text - delete any content put into the intro information box.

CMS: Intro text can be edited on the Advanced Search Page (HOC3-7563)

The Advanced Search Block  (the page /search) has the introductory text "Click on column header to sort."   This text can now be replaced if desired.

When editing this block (by going to Blocks / Advanced Search / Advanced Search / Advanced Search Block) and in addition to setting the filters, you can add introductory text will be inserted on the page.

Note: Currently the replacement text only appears on the left half of the page.  This is a current limitation of the page template. In a future release we'll see if we can make the replacement text span the page width.

Sharing Portal: Duplicate Opportunity Coordinators will no longer appear in list of eligible coordinators (HOC3-7650)

When selecting an opportunity coordinator for an opportunity or occurrence, some names appeared on the list twice.  The logic has been improved so that no contact will appear in the drop down list twice.

Sharing Portal: Decline Reason now visible in connections view (HOC3-7553)

In the connections grid, its possible to see the Status of a connection, but if its a declined connection you cannot see the reason that the connection was declined.   (There is only room enough in the connection grid to show a certain number of columns easily).

Now - if you need to see the decline reason, you can click on "View" or "Edit" for the connection, and the Decline Reason will be visible in the connection record.

Forms now support pulling data as read-only fields (HOC3-7608)

Forms have previously had the ability to update existing records in Salesforce by mapping fields directly to Salesforce.   But it wasn't possible to bring in an existing value from a record without giving the user the ability to edit that field.

Now - Forms submit adding 'read-only' fields to a form.  That way the user can see existing information about themselves, but not edit it.

To use this feature the form should be set to:

  • Would you like to save data in Salesforce  = Yes
  • Turn on Record Update = Yes

Then, when you add a field and map it to salesforce, you'll have the option to set it to "Read Only".  This will bring in the value to the form, but the user will not be able to edit it!

Improvement to Business Pages (HOC3-7601)

If a user is logged in, and their contact record is associated with the Business Account associated with a Business Page, then the user will no longer have to enter the company invitation code to see the opportunities.  

Bug Fix: Volunteers with declined connections can now join waiting lists (HOC3-7226)

In a past release we made it possible for a person who had declined a connection to an opportunity, to sign up for it in the future. (The existing connection is just converted to confirmed).  However, it was still the case that if you have a declined connection, you cannot sign up to be added to the waiting list.  This has been fixed.  A person who removes themselves from an opportunity at some point, can now either sign up (if space is available) or Join the Waiting List (if the opportunity is full).  

0 Comments

Add your comment

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