Jan 2017 Release Notes
The January 2017 release is primarily 'under-the-hood' improvements to HandsOn Connect that will ensure compatability between HOC 2.x and HOC 3.0. The process of beginning to migrate HOC 2.x customers to HOC 3.0 is underway and in 2017 we expect to eventually migrate all HOC customers to the exciting HOC 3.0 platform. We'll keep you posted on the timelines for migrating in the coming months.
The monthly releases will reflect changes that affect ALL HOC customers, whether in 2.0 or 3.0. Much of the work done this month has been to ensure that future migrations will go smoothly when 2.0 customers make the jump to 3.0
We've also begun posting release notes regarding the features and improvements to HOC 3.0 in this forum -- so HOC 2.0 customers can get a sneak-peek at what's coming when they migrate to 3.0
It was discovered that it was possible to create an occurrence or recurrence, where the start date and time and end date and time were identical. This resulted in an occurrence that lasted 0 minutes! This created issues with data integrity and search.
Granted - this isn't something someone should choose to do - but we've improved the validation rules so that no one will accidently create occurrences that last for no time at all (or negative minutes :-)
All occurrences will now have a duration of at least 1 minute :-)
A number of you have opened tickets asking about Critical Update Notifications you've received from Salesforce. The development team continuously reviews all critical updates and ensures that HandsOn Connect will not have issues related to these mandatory updates.
What action do you need to take?
None! Salesforce will automatically auto-activate all critical updates when the time comes. And you can be assured that these updates will not affect the smooth operation of HandsOn Connect. So you can ignore those notices, and don't need to take any action.
If however, you want to avoid the occasional 'nag' that comes up when you go to Setup, reminding you that you have critical updates to review, you can safely activate any of the following updates if you wish to at this time:
- Disable Access to Lightning Experience and the Salesforce 1 mobile browser app from Microsoft Internet Explorer 11
- Enable Lightning LockerService Security
- Enable Lightning LockerService Security for Communities
- Make Sure Records that are submitted behind the scenes are routed to the right approval process
- Add Clickjack Protection for Legacy Browsers to Visualforce Pages without Page header.
- Trust Percent Values in Flow sObject Variables Again
- Require TLS 1.1 or higher for HTTPS connections
Note: when this last update is activated, which will occur automatically on March 4, 2017, some older non-compliant browsers and older mobile devices may not be able to access your site. You can see the current minimal standards for browsers and devices in this post from Salesforce. https://help.salesforce.com/articleView?id=000221207&type=1 If you receive any 'I can't get to your site' questions from partners or volunteers -- refer them to this document. These changes are necessary to meet today's norms for Internet security.