I’m looking at the GS release calendar and noticing that starting in June, the Sandbox and Production org updates are now aligning with one other on the same dates. Why is this changing?
I understand that NXT does not provide an opt-out capability, and it seems like with the change to the release calendar Gainsight may be trying to move to a no-opt out scenario.
That can be problematic for large enterprise organizations.
I have my org opted out of Production updates because we need time to evaluate any new features to determine:
- if there will be any immediate impact to our current processes - if so, we need to make plans to address those changes and adjust our priorities accordingly before pushing the update to Production
- if there are any new features that will be immediately available to end users (outside of Admin control to enable/disable) upon update. If there are (such as the Email from Timeline and Slack Notifications in the latest 6.14 update) we need time to test and become familiar with those features so we can
- Provide our users with release notice of new features
- Be prepared to update documentation and provide enablement on the features
- Be prepared to support the features.
These are very important steps when you are working in an organization supporting 2000+ users. I have had instances in my previous roles where new features were released that, had we not been opted out, would have broken existing processes and/or introduced significant confusion to my end users.
With the May 6.14 release (which we have not yet rolled into production) the Slack Notifications piece was auto-updated in my org because it was an MDA/backend update of which I am not able to opt out.
Do you know how embarrassing and frustrating it is to be notified by end users of the existence of a new feature and questions about how it works? It undermines trust and confidence.
Advance sandbox releases and opt-out functionality is very important.