HOC3 Release Notes 184.108.40.206 (May 2, 2018), 220.127.116.11 (May 10, 2018)
People have asked - "What's the different between a monthly release (like May, 2018) and the HOC3 release notes with names like 18.104.22.168. Well here's the scoop:
The HOC3 release notes are changes made on the front end and sharing portal of HOC. And the 'month-based' releases that update the icon in SF - are changes made to the HOC package in Salesforce. For some things, changes have to be made in both parts of the system before a new feature or improvement is fully implemented. Got it? :-)
Included in this release are additional improvements to the reliability of the check-in kiosk, improvements to the image block and image slider block, improvements to the management of images in HOC, improved display when using search results block, and improvements to opportunity detail page display in Universal Template, and improvements in performance in supported versions of Internet Explorer. Also addressed were issues affecting International customers.
Here are some of the goodies in this month's release for the public site and sharing portal - including two new, much requested improvements for teams and partners using the sharing portal!
Team Captain's have been able to add team members, but not been able to update information about their team members subsequently. That meant, that if they wanted to add (or edit) an email address or phone number for an existing team member, it was not possible. Also, in cases where a team was created but the names of the team members weren't known - a team with with team members like "Volunteer One" "Volunteer Two" - could not be updated to reflect the actual names of the team members.
With these release we've added the long-requested ability for a team captain to edit info on their existing team members.
You can edit the name, email address or phone number of a team member, as long as that contact has not already registered and created an account in HandsOn Connect. (i.e. if the contact is in status "Pending (team Registration)" they can be edited.
If the team member's contact is in status "Registered" - the team captain CANNOT edit the team members info. (This is so that a team captain doesn't accidentally lock a registered volunteer out of their account by changing their email address / user name / (login). Was a team member has their own account in HOC - only that person can edit their own personal information.
To edit members or your existing teams, go to My Account / My teams and choose your team. Click on the "Manage Team" button:
You will see 'edit' icons in the Name, Email and Phone columns for any team members who are still in Pending (team registration) status. No icons will be available to edit team members who have already registered and have an active log in. In this example, we can edit info for Fran Fish and Suzie Kay, but not Vanessa Volunteer who already has an active account in HandsOn Connect.
After editing info on the page --- click the SAVE button to save your changes!
This now makes it possible for team captains who created teams with anonymous names like "Volunteer 1" and "Volunteer 2" to eventually give real names to those anonymous team members, and enter their email and/or phone number as well!
For customers using the /searchresults block for search, the number of available slots was being displayed for ISO and legacy TBS opportunities. Because this number is automatically set to be quite high (its really the number of allowed express interest connections) - it was confusing to volunteers. Slots available is not a relevant piece of info in the case of ISO or TBS opportunities. So now 'slots available' will only be displayed for Date and Time Specific Opportunities as it is elsewhere in standard search.
The code used to create an email to send to an opportunity leader from the opportunity detail page - made it possible for spambots to 'scrape' the site and get the email address of the opportunity leader. The code has been updated for this icon so that the email address itself can not be found in the source code of the page - thereby protecting the email addresses from spam bots.