Scoped Application and Update sets

[Pranav Khurana]

Hello Everyone,

I am working on the development of Mobile Agent Application in ServiceNow. ITSM Mobile & ITSM Mobile Agent both plugins are already installed in our instance and I am working in the ITSM Mobile Agent Application in the Studio and i am using a local update set in that application to capture the changes.

While changing things in the studio, there are few things which are in ITSM Mobile Agent Scope, few are in ITSM Mobile Scope and others are in global scope. Now i don't know how i can capture the changes of global records and ITSM Mobile Scoped records in my update set. When i am trying to move the update set in our QA instance it gives me the below error:

Cannot commit Update Set <SCOPED UPDATE SET NAME> because: Update scope id 'global' is different than update set scope id <SYS ID OF UPDATE SET>. Resolve the problem before committing.

I am not using the publish application option because it is not showing me that as this application was already installed when we installed the plugins and we would like to utilise the things which are already created in this applications like Data Items, Applets, Applet Launchers etc.

The only option that i can see in Studio are below.

Please suggest what options do i have to capture these things in update sets or if there is any other option to utilise all the Application files in this scope in a new application.

Thanks in advance.

[Pranav Khurana]

and what can i do in the case where ITSM Mobile Agent is the selected application in Studio and Mobile_Agent_Update is the update set, But there are few application files such as quick actions which are in global scope and if i make some changes in them they are getting captured in scoped update set.

I cannot change the update set to global while in studio and i cannot access that quick action out of studio.

[Tom Sienkiewicz]

You can create a new global update set and go to sys_update_xml and manually move the global updates to your new update set. 

Then I would recommend to batch those update sets before you move them to another instance.

Disclaimer. I am not taking responsibility for any damage resulting from the above. Use with caution 🙂

[Pranav Khurana]

I tried that already and i moved few updates, But this is difficult for me to distinguish between those updates by just looking in that table. There are many updates which should be in global scope. is there any other way to achieve this?

[Tom Sienkiewicz]

Unfortunately I am not aware of any easy way to do this. You can try filtering those updates in the list by created by or some other field if that helps.

It is best to avoid those situations by doing what was suggested above, before you need to update any global file, make sure to switch to your global update set to ensure it will be tracked there. 

Unfortunately it still seems like scoped apps are not well suited to customizing OOTB applications. for me, a scope app should be something that is self-contained.