October, 2017 Release Notes
Monthly releases are changes and improvements to the HOC managed package (which controls functionality on the Salesforce side of things). This package was not released earlier in the month, so that any adjustments needed to ensure compatibility with Salesforce's Winter '18 release could be factored in.
A variety of updates were made to HandsOn Connect to improve performance in SF Lightning for those who decide to migrate to the lightning experience in the future. We'll have more info on HandsOn Connect for Lightning in the coming year.
Here are highlights in this release - including recommended admin updates to email templates.
A typo and a merge field error that produces a bad URL has been discovered in the email template "Teams: New Team Member". This can be quickly corrected by editing the email template. Here's how:
1. Go to setup / email templates, click on the letter "T" and then select the email template "Teams: New Team Member"
2. Click on "Edit HTML version" button, and edit the email template as follows:
Wherever you see the merge field:
{!Volunteer_Team_Member__c.Domain_Name__c}
Replace it with:
{!HOC__Volunteer_Team_Member__c.Domain_Name__c}
Also:
in some templates: you'll see the word 'of' instead of 'on' in the sentence
"After signing up, you'll find your team membership on the "My Teams" page.
(Make sure it says 'on' and not "of the "My Team" Page.
3. Save
4. Click on Edit Text Version, and click the button "copy text from HTML version". Agree to the popup and then click Save.
Here is the complete text for this email template when corrected. (Feel free to copy the code below and paste it directly into the email template if that's easier than correcting one merge field at a time.
Dear{!HOC__Volunteer_Team_Member__c.HOC__Contact__c},
You have received this message because a Team Captain of the{!HOC__Volunteer_Team_Member__c.HOC__Volunteer_Team__c}teamhas added you as a member of their volunteer team on the{!Organization.Name}web site.
Team Name: {!HOC__Volunteer_Team_Member__c.HOC__Volunteer_Team__c}
Team Description:{!HOC__Volunteer_Team__c.HOC__Description__c}
If you already have an active volunteer account at
{!Organization.Name}, you'll find the team on your "My Teams" page.
{!HOC__Volunteer_Team_Member__c.Domain_Name__c}my-teams
If you are not currently a registered volunteer at the website for {!Organization.Name}, click here to register for a volunteer account so you can manage your own signups as part of this team. Be sure to register using the same email address that this invitation was sent to:
{!HOC__Volunteer_Team_Member__c.Domain_Name__c}volunteer-sign-up
After signing up, you'll find your team membership on the "My Teams" page.{!HOC__Volunteer_Team_Member__c.Domain_Name__c}my-teams
As a member of the team, you are allowing the team captain(s) to act in your behalf and sign you up for volunteer opportunities as part of the team.
Thanks for being part of this volunteer team on the website of {!Organization.Name}For Kiosk customers who have requested enablement of QR code scanning functionality for their kiosk, checking the box "Enable QR check-in" in the occurrence record shows a link to download the QR code on both the success page, and on the my accounts page.
If you wish to ALSO have a link to the QR code sent in the confirmation email for occurrences that will allow check-in via QR code, there is a small edit that needs to be done to your confirmation email template(s) in HandsOn Connect:
This is 'conditional code" that will display the QR link only IF the occurrence being signed up for has had the "Enable QR check-in" box checked.
This code can be added to any of the following email templates (depending on the type of volunteer opportunities you will be using the QR code with):
Opportunity Sign-up Confirmation - Affiliate Managed
Opportunity Sign-up Confirmation - Partner calendar full sign-up
Volunteer Status has been confirmed
Opportunity Reminder - Affiliated Managed
Opportunity Reminder - Partner Managed
Add the following code to the bottom of the desired email templates above:
{!IF(HOC__Connection__c.HOC__Enable_QR_Check_In__c='FALSE','','This opportunity offers an option of quick check-in on the day of the opportunity by presenting an access pass code you can print out or display on your mobile device. Click Here to download your access pass.')} {!IF(HOC__Connection__c.HOC__Enable_QR_Check_In__c='FALSE',"",HOC__Occurrence__c.HOC__HOC_Domain_Name__c+"check-in/accesspass/"+HOC__Connection__c.Id)}This will add a message and a link to the QR code IF the occurrence has Enable QR code active.
When copying the code above and pasting it into the email template, don't use the normal 'paste' function. Instead, right-click before pasting and choose "Paste text without formatting' to avoid unwanted html from going into the template.
HOC administrators and opportunity coordinators often choose to add connections administratively for dates in the past. The managed workflows that send out confirmation emails have been updated so that volunteers will not receive a confirmation email if a connection is administratively added for a date and time < NOW.
Salesforce, for many years, used text fields in its native address forms for Country and State.
In it's Winter '17 release, Salesforce introduced standardized, predefined picklists for Countries and States. HandsOn Connect has now been updated so that depending on an organization configuration - HandsOn Connect can support the new SF global picklists IF your organization wishes to enable them in SF.
Note: If your organization has a need to enable Global State and Country/Territory picklists in Salesforce -- please open a support ticket and we can configure HOC to work with this configuration.
Enabling State and Country/Territory picklists in Salesforce DOES require converting your existing address data in all your SF records. So we do not recommend doing this unless you have a very specific need for this change.
A regression in functionality was discovered, in which contacts created by team captains were put in status 'not registered' rather than the usual "pending (Team registration) status.
The bug has been fixed, and going forward contacts created by team captains will be put in the status pending (Team Registration) again.
There is no functional impact to the contacts that were created with status 'not registered' so there is no need to update your data.
For those who found the status "pending (team registration)' useful for reports or to quickly see that a contact was created by a team captain -- you CAN create a report to see any team members in 'not registerd' status, and then do a bulk update to place them in pending (team registration) status if you like. There is no need to do this however.
The wrong email template was being sent when a volunteer signed up for a grouped occurrence of a date and time specific, express interest opportunity. This has been corrected.
One of the following four email templates will be sent depending on whether the project is affiliate or partner managed, and whether it is full sign-up or express interest:
0 Comments
Add your comment