- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2022 11:43 AM
We have been promoting Catalog Items with Workflows for years by creating them all in the Global scope and using Update Sets to promote. We are just beginning to start using App Engine Studio to build Scoped Applications, which, if I understand it correctly, typically does not involve you having to use Update Sets, as you just publish them.
It sounds great to me, but I admit I do not have a full understanding of App Engine Studio and Scoped Applications yet, as it pertains to this. My question really revolves around, does EVERYTHING get picked up when you try to promote the published application?
For example, let's say that we start a new project using App Engine Studio, and do most of the development there, but let's say that there are some more "advanced" features that we want to do that we cannot seem to do using App Engine Studio, so we do it outside of it (i.e. it doesn't look like you can do Catalog UI Policies from App Engine Studio). Will those things I do outside of App Engine Studio get picked up when I try to promote the published application, or will I need to promote an update set too (that contains things like the Catalog UI Policies)?
Or perhaps, maybe a better way of asking it is like this: is there ANYTHING that wouldn't get picked up when I try to publish/promote the application, that I would need to manually promote using an update set? Does EVERYTHING created in that scope get promoted, regardless of how it is created?
I imagine that there may be some things that might require manual update promotion, if they are created in the Global scope. For example, let's say that I create a Client Script that I want to share across multiple applications, so I create it in the Global scope, but elect to make it accessible from ALL applications. I imagine that would not get picked up in the promotion since it lives outside of the Scoped Application (and is in the Global Application). Is that right?
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2022 02:22 PM
If you do publish your scoped app, the result will be that "everything" in that app will be included. Data records not so as those are part of the app definition. You will be creating 'new version' for updates. If you do partial development in App Studio, and other development outside for the same scoped app, be sure you have the current Application scope selected and some update set to capture those. But you not being able to make some changes (Catalog UI Policies) in App Studio doesn't seem right. Some others may comment on that aspect. As you shouldn't need to apply update sets when publishing an app version. Here are some resources:
and
You can publish to the 'application repository' as described in the above link.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2024 05:07 AM
@Dan O Connor thank you. Is there any documentation available on how to connect instances? From "My Company Applications" I see the apps we've developed and all show in "In Development" tab. There's no way that I see to install it even on the instance it's been developed on.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2024 01:43 PM
If you publish the application to the Servicenow Application repository, all sub-prod and prod instance will have access to it. See:
PublishAppsToTheAppRepository.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2024 09:31 PM
@Bert_c1 just tried but getting a very unhelpful message
This happened right at the very end (99%). Any ideas where I can go to decipher such a message?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2024 09:38 PM
Found the issue in system logs. git integration was broken. Thanks for your help everyone.