Finally we add the Incident Form to our App as well to change the "Resolution Information" section as required:

(Optional) Linking to Source Control

If desired, the changes can also be easily stored in git to unlock Source Control capabilities on them.

A summary of the benefits of Source Control can be found here.

Cautionary Tale: Working outside of Studio

Even with the property enabled, ServiceNow allows to modify global objects outside of Studio as well.

However even if the Global Scoped App is selected as the current Application Scope, a modification of a baseline object does not add it to the Application Scope.

It stays in Global Scope instead of being "claimed" by the Global Scope App.

"Claiming" objects in Global Scope is besides Studio only possible via the List Action "Move to Application":

So remember to always first add the baseline objects to your Application Scope before editing them.

This does not not apply to creating new objects, these are always created directly in the Global Scope App.

Optionally you can also create an Update Set to capture your global changes and then add the objects via the Update Set filter:

Deployment Management

To move your changes to the Test and Production instances, Update Sets can be used as before.

It's also possible to have multiple Update Sets across different scopes together in an Update Set Batch.

However since these objects are now inside a Scope, we can also use the Application Repository to publish the Incident Management Application and then install it on Test and Production via the Repository.

Migrating to Global Scope Apps

In case certain processes have been customized already, it is also possible to retroactively move the objects into Global Scope Apps.

The easiest way is to do this either via the Update Set search or via the Table filter. As objects can only be claimed once, it is not a problem if multiple versions of those exists in multiple Update Sets.