AnsweredAssumed Answered

Why does approving a task create a new document version in the document library?

Question asked by tcl on Mar 21, 2018
Latest reply on Mar 22, 2018 by tcl

I have a rather simple workflow on a document library. When a new document is created or modified in a document library the workflow initiates. In the workflow I basically have only a few workflow variables to set, and then a "Start a task process". This sends a task to each person in a list, with a task with only one outcome. With this task each user 'sign' that they have read the document. The workflow ends without waiting for tasks to complete.

That all goes well.

A user opens the task form, marks he has read the document, and saves. That also goes well.

BUT - the document somehow gets a new version no - and that again kicks off the workflow...

Can anyone shed some light on this?