Moving from Update Sets to Scoped Applications

Hi all,

I just need someone to check my understanding of update sets vs scoped applications.

After reading this article (When to use update sets) I've started thinking that a scoped application should be the preferred way to develop customisations in the future.

I've got a workflow that exists in the global namespace.  I want to create a customisation that will add a new field to the core_company table, and update the workflow so that it can make use of this new field.

FYI: The workflow in question manages notifications for SLA warnings and breaches.

So if I understand things correctly, in order to 'package' my customisations in Studio, I would need to delete my global workflow and replace it with a near identical scoped workflow in Studio.  I'd also add the new table field via the Studio application.

Does this sound correct?

Cheers,

Adrian