The concept is simple enough. If you use Versioning, changes (if captured/actioned by a profile run) which mean that an existing file would otherwise/normally be overwritten or deleted mean that file is Moved to a Version repository instead. That Moved file is given a new stamp reflecting when that Move happened. Within that repository you can optionally set limits for how many such Versions to keep, and/or for how long to keep a Version after it was Moved there.
The ramifications of that concept in a particular set of circumstances may require you to think things through. For example, such aspects as "the Versioning limits are of course only referenced (and potentially applied) if you run the profile again". A profile that doesn't run can't act/process anything. And so on. There are too many potential 'variations on the theme' to describe them all in detail.
The ramifications of that concept in a particular set of circumstances may require you to think things through. For example, such aspects as "the Versioning limits are of course only referenced (and potentially applied) if you run the profile again". A profile that doesn't run can't act/process anything. And so on. There are too many potential 'variations on the theme' to describe them all in detail.