Set Revision and Roll Back

Unfortunately I have not experienced problems with the roll back feature that I can share.  The reason for this is that we do not use the roll back feature as it eliminates history that may be useful in the future.  To roll back a revision, we 1) transition the file into a change state, 2) use get version to get the older version of the file, 3) use set revision to set the revision to a value one increment before the target revision and then 4) process the release.  The result is a file in the previous condition, at the previous revision, but with our history intact showing the change backward.  The flaw in the process is that it's possible to choose the wrong version in the get version step or choose the wrong revision in the set revision step resulting in the wrong roll back.  I am always in favor of retaining history, however, and with this method, it can be corrected if mistakes are made.  Using roll back is like wielding an axe that removes history forever.

Hi Nhat MAI,

I personally recommend reserving rollbacks for admin only usage and should not be an operation that would be employed regularly to avoid creating suspicious data activity in your data management history.

That being said, I too use the method Amos mentioned for creating a fake rollback.

Tim CEPA

Believe in The Q!