How are applications (scope) moved within update sets?

[Dobbyn]

I've done a lot of development in instances that use Fuji or ealier, so working within scopes is new to me.   How are applications moved within update sets?   Do I always have to take the action to "Publish to Update Set" or is it captured in the initial update set used to create the application?   And what changes are in that newly created update set (when publishing to update set) versus what was captured in my other update sets created wihin the application?   Thanks a lot for your help!

[nthumma]

This is what we follow

1) Initially will publish whole application to update set. like say updateset 1.0

2) all other changes after that we make sure to capture in separate update set and will move only that update set, say updateset 1.1

we also tried 'Make App available on other instances' but we experienced numerous issues.

you can also check similar answered   thread : Moving Changes for an OOB Scoped Application

[robpickering]

Just some additional context.

Capturing changes for Scoped Applications doesn't have to be any different than changes to non-scoped applications.

If you start an update set and then build a scoped application, all of the updates will be captured in that update set.   Moving and promoting that update set to Production can happen the same way that you're used to...each of the updates just has a "scope" now.

You can even mix scoped and non-scoped updates into the same update set (though you probably want to avoid that from a best practice standpoint).

The only difference is that Scoped Apps can also utilize "Publish / Subscribe" in order to build an application in Development and then push those updates into Production through the "Application" interface (System Applications > Applications).   This method allows you to version your application and provide updates to it outside of the "Update Set" method.   You can read more about it here:   Application management

-Rob