May, 2017 Release Notes
The May Release of HandsOn Connect will be pushed to all customers May 4 - May 5. The most critical fix in this package was pushed to production in Mid-April. There were also a number of fixes for international and multi-lingual customers. But here's the highlight of what's fixed in this month's release.
Many HOC customers were experiencing an 'invalid integer' error when updating connections using the connections grid on the occurrence record in SF Administration. These errors came up when adding guest connections or editing the hours of an existing connection.
The culprit was a subtle change that appeared in the connection grid. The "Date" field was now populating a date and time value (instead of just a date), and as a result the grid was not functioning as expected and produced the errors.
This has been resolved and the connection grid should once again be working as expected.
Because of the critical nature of this bug - it was actually pushed out to all instances of HandsOn Connect in mid-April.
When an NonProfit partner is given the permission to 'auto-approve' its own volunteer opportunities and occurrences (rather than having them submitted for review and approval) the following behavior is in effect.
When a new Volunteer Opportunity and one or more occurrences are initially created in the partner portal, the volunteer opportunity will automatically be set to status active. They they are able to self-publish each of their individual occurrences.
The partner will see each occurrence they created in the posting status "Not yet published. Click on the Publish action to make this occurrence available for volunteers to sign up"
Previously - the partner saw an innaccurate posting status message that said "This is not published and has been submitted for approval".
Parners can then click on the "Publish" link in the occurrence record to self-publish occurrences when they are ready to publish them.
Messaging that appeared before:
Messaging that appears now:
Note: The screenshots above are from the 3.0 sharing portal. 2.0 customers will see the same posting status messaging in their portal -- (though the link for publishing the occurrence appears differently).
Many HandsOn Connect customers have been getting messages from salesforce that effective this July support for TLS 1.0 will be suspended.
What is TLS?
TLS stands for Transport Layer Security. It is a protocol that provides privacy and data integrity between two communicating applications. Its the most widely deployed security protocol used today, and is used for web browsers and other applications that require data to be securely exchanged over a network. TLS ensures that a connection to a remote endpoint is the intended endpoint through encryption and endpoint identity verification. The versions of TLS, to date, are TLS 1.0, 1.1 and 1.2.
What does this mean to you?
1) HandsOn Connect has been tested and found to be TLS 1.1+ compliant. So you don't have to worry that HandsOn Connect will break on July 22nd when support for TLS 1.0 is discontinued by Salesforce.
2) The best versions of browsers to use with Salesforce and HandsOn Connect are always the most stable current versions of:
- Chrome (chrome is always auto-updated - so you are usually using the most current version!)
- Safari (Recommended: Version 10.x but versions 8.x, 9.x on Mac OS X are also supported.)
- Firefox (most recent stable version. Its also recommended you configure firefox according to these instructions
- Microsoft Internet Explorer versions 9, 10, 11 (11 recommended) -- you should make sure however than TLS 1.1 and TLS 1.2 are enabled in Internet Explorer. Here are instructions for enabling these in IE
3) There may be errors generated by users who are using older browsers. When support for TLS 1.0 is dicontinued, users of older browsers will receive a "Stronger Security Required" error message, which will direct them to a Salesforce HelpDesk article which will suggest they update their browser.