Hi, is there a way to manage document versioning directly from a process v

Hi,
is there a way to manage document versioning directly from a process via automated tasks? (i.e. without using attended tasks).

For example, in a document approval process, I want to be able to set a "candidate" document (the document to be approved, stored in a document variable pv!toBeApproved) as the new version of another document, already existing in the knowledge center.
This should be made at the end of the approval process, and is not possible to use (as suggested in the documentation) an attended task with a File form component.
...

OriginalPostID-112736

OriginalPostID-112736

  Discussion posts and replies are publicly visible

Parents
  • Are you looking for two process variables to hold two different versions of the same document within a process instance? If so, no it's not possible.
    With regards to versioning, when you created the candidate document, then that version automatically becomes the latest version (or newer version). The end user always accesses the latest version of the document. Why would you want to upgrade the document version when no change has been made to it? It defeats the purpose of document versioning. If you want to manage the status of the document (such as generated for candidate, read and accepted by candidate etc) then you'd do it by a process variable that manages the status life-cycle.
Reply
  • Are you looking for two process variables to hold two different versions of the same document within a process instance? If so, no it's not possible.
    With regards to versioning, when you created the candidate document, then that version automatically becomes the latest version (or newer version). The end user always accesses the latest version of the document. Why would you want to upgrade the document version when no change has been made to it? It defeats the purpose of document versioning. If you want to manage the status of the document (such as generated for candidate, read and accepted by candidate etc) then you'd do it by a process variable that manages the status life-cycle.
Children
No Data