Regarding of Update Set Deployment

[VishaalRanS]

Hi everyone,

Can you suggest me strategies for managing update sets in ServiceNow to minimize conflicts and ensure a smooth deployment process?

[Mark Manders · Accepted solution]

It really depends on the level of development, the number of instances and the number of people/teams that are working on the instance.

The main thing: batch them together if your update set A touches the same object as update set B, so you will be sure to get the latest update. But if at any time two requirements are about the same object, you will need to make them dependent on each other. So if you are working with stories that both touch the same flow, you need to make story A dependent on story B so they can't move to PROD without both being approved. Best thing would be to assign the same person to it, but we have limited information on your way of working.

Use instance scan to scan update sets, use scripts to validate every object is in the correct scope, use scripts to check if the object in your update set is also in an update set that is still open/created after yours. There are numerous things to do, but, again, it all depends on the things I started my answer with.

[Harish Bainsla · Accepted solution]

Hi @VishaalRanS  check below links 

https://sn-nerd.com/2023/06/13/everything-you-need-to-know-about-using-update-sets/

https://www.servicenow.com/community/south-carolina-snug/update-set-deployment-automating-the-previe...

https://www.servicenow.com/community/north-carolina-snug/automated-update-set-batching-and-deploymen...

If my answer helps you mark helpful and accept solution

[Mark Manders · Accepted solution]

It really depends on the level of development, the number of instances and the number of people/teams that are working on the instance.

The main thing: batch them together if your update set A touches the same object as update set B, so you will be sure to get the latest update. But if at any time two requirements are about the same object, you will need to make them dependent on each other. So if you are working with stories that both touch the same flow, you need to make story A dependent on story B so they can't move to PROD without both being approved. Best thing would be to assign the same person to it, but we have limited information on your way of working.

Use instance scan to scan update sets, use scripts to validate every object is in the correct scope, use scripts to check if the object in your update set is also in an update set that is still open/created after yours. There are numerous things to do, but, again, it all depends on the things I started my answer with.

[Harish Bainsla · Accepted solution]

Hi @VishaalRanS  check below links 

https://sn-nerd.com/2023/06/13/everything-you-need-to-know-about-using-update-sets/

https://www.servicenow.com/community/south-carolina-snug/update-set-deployment-automating-the-previe...

https://www.servicenow.com/community/north-carolina-snug/automated-update-set-batching-and-deploymen...

If my answer helps you mark helpful and accept solution

[brahmandlapally · Accepted solution]

Hi @VishaalRanS 

Use a naming convention for easy identifing your updateset

Like first_two_letters._story number_.short description of story.

[Anantha27]

Hi @VishaalRanS 

If you are confused on the update set which one to deployed, then you can use format-based naming convention like name_test1 or name_test2 like that so that you can have better understanding on which update set you need to take and deploy in instance.

Thank you