Use case being that Workflow will sometimes need to perform actions such as updating metadata when a new version has actually been created by a user. Since updating the metadata will create a new version, the document now has 2 new versions added to the existing history. The user created one and the workflow created one.
Discussion
Discussion
Enhancement Request: Exclude Workflow from version tracking
It's an interesting idea. I'd be concerned that it would cause confusion for some user's changes to not show up in the version history. Their changes would essentially be merged in with the previous user's changes.
If you're concerned about creating too many versions, maybe you could either:
- Have Workflow place the document under version control after making its changes
- Have workflow delete the previous version from the history after it makes its changes
Hey Brian!
The document is typically placed under version control from the moment it is created. When a new version is created by a user, it triggers a workflow which then generates information about the changes in a Notes field. Since workflow is writing to a field, it causes the system to create another version on top of the user's. So now we have the 1)The original version 2) The user's new version 3) The workflow version with the updated Notes field
We could simply delete the previous version, however, this would result in a gap. So then the versions would read 1,2,4. Which the customer does not want.
Hope that makes sense!
Another thought, Brian, that would require even more effort: major and minor versions. Workflow could trigger a point update (2.1, 2.2), and then the user update could be a major update (2, 3).
Of course, this leads to a number of questions, like would document content changes be the major while metadata minor? User-specific? Etc.