When a document has been included in a workflow, it is not possible to disable the version. Sometimes it is necessary to be able to disable the version instead deleting the whole document.
|
Practical use of functionality?
When a document has been included in a workflow and we discover that the file is corrupted or it is wrong, we cannot disable the version because the document has been included in a workflow and the only option is to delete it. There is no problem if the document is in the first version, but when it happens in next versions, we cannot delete the version and the only option is delete all the document. |
|
|
What is the impact of not doing this?
If the problem is in a document with more than 1 version, you must delete the document and upload again the previous version, losing all the information of previous workflows. If the problem is that the file is corrupted, it is not correct to upgrade to a new version because there is no modification. |
Hi @Guest ,
Thank you for submitting this idea.
One mechanism that can be used when all documents are going through automated workflows is to use the automated workflow to control the "status" of a document.
Documents that are "rejected" could be marked with a status of "do not use" and not distributed to the larger team.
This would maintain the audit trail of what happened whilst making it clear to users the suitability of each document version.
Best regards, Paul