Dec 2016 Release Notes

The December release includes a number of bug fixes that will increase HandsOn Connect performance.  Also, there is an Administrator alert - with instructions on a 5 minute update all System Admins should make to correct errors in two workflows that manage the sending of reminder emails.

Separate release notes will be published with the latest features and improvements for HandsOn Connect 3.0 users.

Administrator Alert: Action Required (Update Workflows for Reminder Emails)  (HOC-722)

This update will take you about 5 minutes as is recommended for all HandsOn Connect customers.

We've learned of a bug that exists with the workflows that send Reminder Emails to volunteers 4 days before the occurrence takes place. These emails are only supposed to be sent for Date & Time Specific Opportunities, and we've learned that the current workflows are sending these for TBS and ISO opportunities as well.  This is confusing for volunteers as the email reminds them to attend based on the occurrence end date. Since TBS and ISO opportunities have a single occurrence, the end date of the occurrence is of no relevance to the volunteer who would be scheduled for a connection at some time other than the end date of the occurrence. And they may receive this reminder months or years after they actually expressed interest to volunteer.  (It's sent four days before the expiration date of the TBS or ISO opportunity).  So reminder emails shouldn't be sent for TBS or ISO based occurrences, and a quick update to the two workflows involved with resolve this.

Because the two workflows that handle this are "unmanaged" - they have to be fixed directly in your instance and can't be 'pushed' as part of the release process. Admins should follow these simple steps to update the code for two workflows.  Here's what to do:

Find the two affected workflows

Go to Setup and type "workflow Rules" into the search box, and click on the link for workflow rules

Find the two affected workflows

Use view "All workflow Rules" and click on the letter O

The rules we are looking for begin with the words "Opportunity Reminder"

Find the two active workflows for opportunity reminders

Look for the 'active' checkbox on the right of the listing to see which Opportunity Reminder emails you are currently using.  For most customers these will be named "Opportunity Reminder - Partner Managed 1" and "Opportunity Reminder - Affiliate Managed 1"   -- for some customers these may not have the number 1 after them -- but they are unmanaged workflows (meaning they don't have the symbol with the arrow next do them.  (Those are older managed workflows that are no longer used).

Whatever their names, there are two active workflows, one for Affiliate Managed projects, and one for Partner Managed projects.  We're going to edit the code in each.   Click on EDIT, and then replace the code as instructed in the next step.  Let's start with "Opportunity Reminde r- Affiliate Managed 1"

Find the two active workflows for opportunity reminders

Opportunity Reminder - Affiliate Managed 1

Select all the contents of the current rule criteria and delete it.  Then replace that content with this formula:

IF( AND( ISPICKVAL( HOC__Status__c , 'Confirmed'),

ISPICKVAL(HOC__Volunteer_Opportunity__r.HOC__Managed_By__c , 'Affiliate'),

ISPICKVAL( HOC__Volunteer_Opportunity__r.HOC__Status__c , 'Active') ,

!( ISPICKVAL( HOC__Attendance_Status__c , 'Canceled')), (

( AND(( DATEVALUE ( HOC__Occurrence__r.HOC__Start_Date_Time__c ) - 4 )>Today(), ISPICKVAL( HOC__Volunteer_Opportunity__r.HOC__Schedule_Type__c , 'Date & Time Specific') ) ) ||

(AND (( DATEVALUE (HOC__Start_Date_Time__c ) - 4 )>Today() ,ISPICKVAL( HOC__Volunteer_Opportunity__r.HOC__Schedule_Type__c , 'Date & Time Specific')))

), ISPICKVAL( HOC__Occurrence__r.HOC__Status__c , 'Active')) ,

true, false) && IF( HOC__Occurrence__r.HOC__Send_Reminder_Email__c == TRUE, FALSE, TRUE)

 

------

Click on 'Check Syntax" to make sure there are no errors in which you've pasted.

Click Save.    1 down. 1 to go.

Opportunity Reminder - Partner Managed 1

Select all the contents of the current rule criteria and delete it.  Then replace that content with this formula:

IF(AND(ISPICKVAL( HOC__Status__c , 'Confirmed'), ISPICKVAL(HOC__Volunteer_Opportunity__r.HOC__Managed_By__c , 'Partner'), ISPICKVAL( HOC__Volunteer_Opportunity__r.HOC__Status__c , 'Active') ,

!( ISPICKVAL( HOC__Attendance_Status__c , 'Canceled')),

((AND(( DATEVALUE ( HOC__Occurrence__r.HOC__Start_Date_Time__c ) - 4 )>Today(),

ISPICKVAL( HOC__Volunteer_Opportunity__r.HOC__Schedule_Type__c , 'Date & Time Specific')))

|| (AND (( DATEVALUE (HOC__Start_Date_Time__c ) - 4 )>Today(),

ISPICKVAL( HOC__Volunteer_Opportunity__r.HOC__Schedule_Type__c , 'Date & Time Specific')))),

ISPICKVAL( HOC__Occurrence__r.HOC__Status__c , 'Active')

),

true, false)

&&  IF( HOC__Occurrence__r.HOC__Send_Reminder_Email__c == TRUE, FALSE, TRUE)

------

Click on 'Check Syntax" to make sure there are no errors in which you've pasted.

Click Save.    You're done!

Problems?

If you experience problems doing this update or have any questions or reservations, open a ticket in the help center and we will take care of this for you upon request.

Fixed: Business Page opportunities for companies with an "&" in their name not showing up (HOC-782)

We've fixed a known issue where invitation code opportunities (that appear on a company's business page) do not show up for organizations with an "&" in their name, such as "AT&T".

Fixed: Incorrect Posting Status for occurrences created via recurrences (HOC-777)

We've made a number of improvements to the accuracy of the "Posting Status" field as an indicator of whether or not a volunteer opportunity and/or occurrence is published and available for signup on the public site. It was discovered that when creating an active recurrence, the individual occurrences that were created had a posting status of "This is not published. The Date & Time is in the past" which wasn't the case.

This has been corrected and the posting status will now be accurately reflected when creating recurrences.   Posting status is a reliable indicator of whether an opportunity is on the public site, and is updated every night shortly after midnight to update expiring occurrences and volunteer opportunities.

Fixed: Incorrect Posting Status for occurrences created via recurrences (HOC-777)

Fixed: Dates missing from grouped occurrences (HOC-784)

For those using grouped occurrences, you may have noticed that the 'note' on the occurrence sign-up detail was missing the dates of the other occurrences in the series.  This occurred on the signup page and the success page.    This issue has been fixed and dates will now accurately show up for grouped occurrences.

Fixed: Dates missing from grouped occurrences (HOC-784)

Trigger filters updated for improved performance with large Salesforce databases (HOC-766)

A number of HandsOn Connect customers use their Salesforce instance for far more than volunteer management. They may have thousands of organizations and contacts that have nothing to do with volunteerism.  To improve performance and minimize  conflicts that can occur in these deep Salesforce databases, the triggers used by HandsOn Connect have been updated to only operate on contacts and organizations that are related to the functions in HandsOn Connect.  Customers with these sorts of SF instances will see improved performance and fewer trigger-related errors.

Fixed: Conflicts between HOC and NPSP batch updates (HOC-767)

Customers using the NonProfit Success Pack have reported trigger-related errors that occur when NPSP performs its nightly batch updates. This release will minimize the conflicts that have occurred and prevented batch updates from completing.

Fixed:  Errors related to "too many SOQL queries" (HOC-780)

A number of customers have reported errors that occur on the public site or administratively under some circumstances where a lot of records need to be updated at once.  We've seen reports of "Too many SOQL queries" related to signing up for grouped occurrences, self-reporting, and administratively adding connections.   This release includes a fix that streamlines the number of SOQL queries necessary for complex processes, so that it does not bump into Salesforce's limit of 100 queries per transaction.

0 Comments

Add your comment

E-Mail me when someone replies to this comment