Overview
Suppose you have a vault that utilizes Compliance Kit's Version Control Lite module in one of its workflows, and you have encountered the following situation with some document using the workflow: When the document has been moved to a specific state in the workflow, the document's file content is reverted to what it was in one of its earlier versions.
The behavior can be related to the normal functionality of Version Control Lite's "Editable States" configuration, if the specific state has been defined in this configuration.
The Compliance Kit - Configuration Manual describes the functionality in the following way:
"4.18.2 REVERT TO EDITABLE FUNCTIONALITY
Defining some workflow states into Editable States[] will enable a functionality that can be used to revert the Controlled Working Copy files to earlier editable state. All the workflows states which are not included in this list are considered as non-editable.
When a Controlled Working Copy enters any editable state from any non-editable state the objects file content is reverted to file content from the objects history when it last was in any editable state. This revert will lose all file content related changes made in the intermediate non-editable states, such as file modifications, new file additions and removals.
Example use case: Draft is an editable state, where the word document is edited. Then it's moved to non-editable approved state and gets replaced with a read-only PDF file. Then the object continues to another non-editable state where it's published. When the object returns to the editable Draft state after versioning the document gets reverted to its last editable word document version allowing further modifications."
Solution
If you have defined "Editable States" in the configuration of Compliance Kit's Version Control Lite related to a specific workflow, check if the behavior is related to that configuration.
