Add Cross Scope Privilege to App in Studio?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2020 07:42 AM
How does one handle cross scope privilege in moving apps built in the studio between instances? For example, I have an app that needs to access a script include in the Global scope and I changed the include to allow for all scopes. That doesn't get captured in the app. What's the best practice here? Fix Script to add the cross scope records? Something else?
Thanks!
- Labels:
-
Scoped App Development
-
Studio
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2020 12:06 PM
If the Source field is filled in and is clickable then the item is in there. But let me ask you this, how are you moving the app to a target instance? Via update set or source control? If you are using an update set, navigating to the application and publishing it to an update set will create a new one and include all of the app's components. This would exclude the global items of course but you can link that as a child update set as mentioned earlier.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2020 12:10 PM
Wait, I see. Some are in Global Default UDS and some are in my scoped Default UDS. Ha, I've totally confused myself on these records.
I'm going to just move this via an UDS most likely.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2020 12:17 PM
Got it and that is where Default update sets can get confusing. So once you are done, navigate to sys_app.list, open your app record and under related links you will see "Publish to update set". This will capture all the app components into a new update set.
Then you will need to capture your other app/global items into an update set (not default) and I would set that update set's parent value to your app's update set so they migrate together in one XML and also commit together as well.
Years ago I created a Copy/Move popup that allows you to easily move Customer Updates (sys_update_xml) records between update sets. You might find this useful to move these records from your Global default update set to a new one:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2020 12:24 PM
Thanks for your help

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2020 12:32 PM
You are very welcome Christopher. Just to add, I recommend using app repo to push changes related to scoped app and use "Publish to update set" if you want to continue development activity in a target instance (This is excluding update set captured in global scope). Details here https://docs.servicenow.com/bundle/orlando-application-development/page/build/applications/task/t_Pu...
Let me know if that answered your question. If so, please mark appropriate response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.
- Pradeep Sharma