Best Practice for capturing in Update Sets

[Siva]

When any skill is being activated, if we turn on an update set 

For ex: Lets say we are cloning or updating small configuration in the guided setup of the Incident Summarization skill , we are seeing that updates are capturing in Three Applications (ITSM Mobile Agent, Now Assist for ITSM and Global) but we might have started our update set to capture the config changes in the skill in Now Assist for ITSM Scope, as the skill record in the table shows the record in this scope, 

Now in order to transfer these changes to next instances, do we need to do pre-work of creating three update sets in the above mentioned scopes and then batch under a story based update set ? 

[Rafael Batistot]

Hi @Siva 

Yes. Since Update Sets are application scoped, you should create an Update Set for each scope where changes are captured (Global, Now Assist for ITSM, and ITSM Mobile Agent), then move them together, typically using a Batch Update Set if appropriate.

[Siva]

Hm, Thanks for the quick update Rafael, I would just wait for some more responses and then would Accept as solution as I just wanted to check if there are any latest changes that i am not aware of .. 

Thanks for the reply btw.

[Dr Atul G- LNG]

Hi @Siva 

https://www.servicenow.com/community/developer-forum/best-practice-update-sets-scoped-applications-o...

https://www.servicenow.com/community/developer-articles/everything-you-need-to-know-about-using-upda...

[yashkamde]

Hello @Siva ,

No, you don't need to manually pre-create three separate update sets.

When your active update set captures a change to a record owned by a different scoped app, Platform auto-generates a scoped child update set for that target scope and links it to your current update set. You'll see these auto-created ones if you check System Update Sets > Local Update Sets, they'll be named things like <scope name> with a note field showing they were auto-generated, and they'll reference the same parent.

Also for migration use Batch Install to group your base update set with the auto generated scoped ones and commit them together as a batch rather than individually, this avoids cross scope dependency errors. Just confirm all three apps exist on the target instance first.

If my response helped mark as helpful and accept the solution.