Does anyone have an example of a workflow transition with actions that can effectively undo a revision? Typical process that would warrant this, assume file starting out in Released state.
- User, change state "revision required"
- Sends file to WIP
- sets REV on data card to the next revision
- adds row in rev table of slddrw with the transition comment
- records other data to data card: user, date, etc.
- User makes changes and checks file(s) in several times but file never goes back to released, never "stamped" with the revision in history, the "Inc. Revision" transition action never happens.
- The change is canceled or is decided to take out new part number instead of revise existing.
How can the user undo the change? I'd like to send this file back to released without incrementing the counter and make a new version of the file that is a copy of the last REV Stamped version.
Currently the admin needs to do a Roll Back (don't like doing for various reasons) or the user manually gets last released version and checks that in then admin needs to us the Set Revision tool to fix the rev counter and revision on data card.
This is a fairly common action, I'm assuming there must be a good solution out there that encapsulates these actions in a transition from WIP to Released so the user can undo the revision and the history is all retained and the revision counter is still correct.