I've only just come to realize that Autodesk does not officially support editing of files in the Released state. In every vault implementation I've done, I've configured the file lifecycle definition so that the Administrator account has read/modify/delete permissions for the purpose of doing the occassional edit, without the need to transition to another state (e.g. "Quick Change"). In a related note, if a customer is working with item lifecycles in which the item state determines the ability to edit the file ("Apply Item security to related files"), granting the Administrator account read/modify/delete permissions could be used for the same purpose. In discovering that edits to files in the Released state is considered a bad practice, I asked about Job Processor which operates in the exact same manner but supposedly it does background operations that make these released-based edits an acceptable practice.
So, the purpose of me posting here is two-fold;
- How many of you have your lifecycle definitions configured in a similar manner (whereby the Administrator account is configured for read/modify/delete for the purpose of editing in Released state)? I am curious if others are making occassional edits to files in this state without the need to transition to "Quick Change".
- If you would like to see this workflow be officially supported, please add your comments to this post.
Ryan