- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2020 01:44 PM
We are on New Yorkand begin to plan for upgrade to Paris, in long term only want to upgrade once a year but with ServiceNow's new policy to only support N and N-1 release how can a customer upgrade only once a year(i.e. skip a release) and still be on supported version of SN??
Just wanted to know how are you guys planning your upgrades now? Does this mean we have to sign up for early release of Paris and perform our upgrade testing in that version? Or are customers planning to upgrade multiple times an year?
Below article has some more information about ServiceNow's policy that i am referring to:
https://hi.service-now.com/kb_view.do?sysparm_article=KB0783520
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2020 02:52 PM
ServiceNow knows you will not upgrade the day a release becomes GA, so some time is given. This way you can do early testing with the Early Adopter release, then get the GA release, do your final testing and upgrade production. But don't take my word for it, read the "Plan for upgrades at least once per year" presentation on the Success site. Where it says:
"ServiceNow releases a new version of the Now Platform® twice per year. To make sure you can take advantage of new functionality, you should stay on the latest release. We recommend upgrading your ServiceNow® instances at least once a year to stay no more than one version behind the latest release. "
This post specifically talks about the grace period after a release goes GA.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2020 04:01 PM
Hi Ripu, The situation outlined has the starting point of the GA date of the release from ServiceNow. As Jeff outlines SNOW has available Release Testing and Early Access programmes to help customers with starting upgrade planning, testing etc before the next N release.
Roughly RT is 30 days, EA is 30 days and then EOL is 30 Days for the version that was made N-2 by the current release. So there is a window of ~3mths(ish) that you will have to work within before you are in a potentially uncomfortable spot.
Jeff makes excellent strategic thinking points around not just seeing the platform upgrades as a cost, but also as an opportunity to use new and updated features to help improve your operations. And the "automation" of testing to reduce overall load.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2023 01:12 PM
Going to a N-1 policy puts a heavy burden on the Intelligence Community and Department Of Defense Communities who have implemented your platform. Understand that Ideally communities should strive for N-1 but due to world situations and contractual issues, this will not always be met. an N-2 policy is much more practical and achievable. What allowances are or will be in place for those communities that are challenged to meet N-1?
