"Default" Revisions

What
Default revisions let you point an association at whichever Fileset revision is marked as the default, instead of hard-coding that association to a named revision. This is useful when you test a new revision with a small group first, then promote it for production without editing every production association.
When/Why
In this example, Firefox v79 is assigned to all devices through two associations:
In the screenshot, the Production group is associated to <default> (currently v79), while the Beta Testers group is associated directly to v79. Both groups install v79 today, but only the Production association will follow the default revision when that default changes.
How
Test the new revision before promoting it. In this example, edit the patch testers association first so that group receives v80:
Once we save this association and update the model, all patch testers will get the new version.  No deleting of the association or creating a new one is required.
After testing, you could edit every production association one by one, but default revisions are designed to avoid that. The Production association points to the default revision of the Fileset, not directly to v79.
Change the Fileset's default revision to v80, then update the model.
Once we save that change, and update the model, you'll see the change reflected in the association:
And, upon next check-in, all "Production" devices will upgrade to v80.
FileWave handles the revision transition through the model update and normal client check-in process. Use a test group first so you control when the new revision reaches production devices.
Related Content
Managing Revisions
"Default" Revisions
Creating a New Revision
Editing Fileset Revisions
Removing/Deleting a Revision