Working With Custom Scoped Applications

[jmiskey]

We created some Custom Scoped Applications for various Catalog Items and Flows.  We publish them and promote them to other environments.  

One of our Developers has a bunch of minor changes to make to a bunch of Catalog Items across various Custom Scoped Apps.  He wants to promote these changes using Update Sets instead of publishing each Custom Scoped App individually (so he can use a Parent update set and do them all at once). 

Will this present any problems?  Especially if at some point after that, users make other changes and Publish the Custom Scoped App to promote them?

Here is my concern.  Let's say that you are on version 2.2.2 of a Custom Scoped App.  If you make changes, and promote them, the version number of the scoped add doesn't change (it is still 2.2.2).  Are the new changes added to the last version number?  Or do they become part of the next version of that Custom Scoped App that is published (when it is published)?

Just trying to understand best practices and any issues with going about it they way they want.

Thanks

[GlideFather]

Hi @jmiskey,

I have been doing most of the deployments by update sets. I deployed via app when it was a complex or bigger app for example a CSM delivery from scratch, we deployed all via app and additional minor changes (catalog item's title renaming, typos etc) were done by update sets.

Perhaps you should consider doing cloning some time after successful implementation in PROD, and then you just need to stick to 1:1 across all the environments (DEV - TEST - PROD or any other if you use).

[kaushal_snow · Accepted solution]

Hi @jmiskey ,

In general it can cause problems down the line to mix Update Sets and App Repository / publishing workflows for custom scoped applications, because once you publish a scoped app you typically want all future changes to flow through the application repository (and new versions), and mixing in update sets to push changes can lead to versioning conflicts or lost dependencies, so best practice is to pick one method (publishing / app repo) and consistently use it for that app, rather than trying to patch scoped app changes via update sets and later publish over them...

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.