ServiceNow Update Set Batching - Best Practices & Lessons Learnt

[The SN Nerd]

Hi Community,

ServiceNow introduced Update set batching in Jakarta.

This is our experience so far:

Usage

At this stage, we have used it for Releases, where we create an empty Parent Update Set and relate Update Sets to be included in the release as children.

Pros

• Can remove individual items from the release at the last moment.
• Similar to merging, except you can essentially unmerge but unrelating a child at any time
• Easy to deploy, only need to commit Parent Update Set
• More Granular Update Sets makes it easier to tie changes to requirements and documentation

Cons

???

There isn't much information on it at the moment, especially around Best Practices, so I thought I would reach out and see what the Community Experience is so far.

Will you keep merging Update Sets, or will you start batching? Is this the way forward?

[Fred Jean]

Actually, what makes sense when asked not to deploy (ever) an update set is to make a back out on every platform where deployed.

And when we do that, the update set is removed from its parent batch.

[The SN Nerd]

Ideally, you would clone down from PROD through all environments after the release, so there is no need to remove the rejected enhancement.

It could also be possible that the rejected enhancement is simply deferred and implemented at a later date.

[timpreston]

Hi,

have you had any issues with update sets that are for different applications being in the same batch? 

From your other post (update set backup) I got the impression that it would not matter but wondered if you hand encountered any issues.

[The SN Nerd]

I have created multi-application batches with no issues.

[Daniel Billing]

Anyone tried merging batch update sets?

Seems like it works fine. as all the relationships is still there... but i wonder how it treats the hierarchy when it suddenly 1 update set.