We received a notification from servicenow for defect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2024 09:41 AM
Hi Community,
Currently UAT instance version is as below
And we received below notification from ServiceNow vendor
Can we ask ServiceNow vendor to deploy in Xanadu Patch 3 and above in UAT instance, if Yes but we have upgraded ServiceNow dev instance version is to this
Could you please suggest which version is go with "Xanadu Patch 3" or xanadu_patch1-hotfix2a?
Thanks,
Srinivasu Sagiraju

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2024 08:49 AM - edited 12-05-2024 08:52 AM
That is not fully true. Otherwise I would not be able to move update sets into prod while I'm still testing the patches. I just move catalog items into prod last night when prod is on Washington DC patch 7 and while dev/test are on Washington DC patch 8 host fix 3.
It could be if you are tying to move updates to an out of the box script include (for example) that was updated by the patch but otherwise you can move updates between different patch levels and even versions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2024 08:59 AM - edited 12-05-2024 09:07 AM
Sorry -- I am referring more specifically to different family versions. While it is possible, it is not supported nor recommended by ServiceNow (KB0550934). With patches, you technically do run the risk of seeing errors. (Edit to add: especially as you have mentioned Brian with functionality touched by upgrades, e.g. OOTB script includes.)
Anytime an admin is trying to move updates from newer family versions into older family versions (for example, Eureka into Calgary), be aware that this is not supported by ServiceNow in any circumstance. Because of the same code changes mentioned above, the older instances do not know what to do with the new code. This results in the majority of the updates being ignored during commit. Additionally, those updates that do commit may overwrite the original code with functionality not supported by the older instance.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2024 09:43 AM - edited 12-05-2024 09:44 AM
Yes this is going the Opposite direction. I.E. dev is on Calgary but test is on Eureka which is a newer version. Note sure why they would have to have a KB article for something like this. This is almost the same as Costco recalling butter because they forgot to put include contains Milk in the ingredients section.