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

andrear over 10 years ago

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.
...

Discussion posts and replies are publicly visible

Parents

0 andrear over 10 years ago

The idea is to take from an external source (e.g. by performing a polling on a filesystem folder) a document (let's call it "myDoc_v2_candidate") that is candidate for being a new version of a document already existing in the knowledge center("myDoc_v1_approved").

myDoc_v2_candidate is in fact a modified version of myDoc_v1_approve. (that's the reason for the upgrade).

After passing few steps of approval, the candidate should be moved in the system as the new version of myDoc_v1_approved (myDoc_v1_approved).

Do you have any suggestion about how to achieve this behaviour?

I was thinking to implement it by loading the previous version of the document in another process variable, but, as you told me, it's not possible.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 andrear over 10 years ago

The idea is to take from an external source (e.g. by performing a polling on a filesystem folder) a document (let's call it "myDoc_v2_candidate") that is candidate for being a new version of a document already existing in the knowledge center("myDoc_v1_approved").

myDoc_v2_candidate is in fact a modified version of myDoc_v1_approve. (that's the reason for the upgrade).

After passing few steps of approval, the candidate should be moved in the system as the new version of myDoc_v1_approved (myDoc_v1_approved).

Do you have any suggestion about how to achieve this behaviour?

I was thinking to implement it by loading the previous version of the document in another process variable, but, as you told me, it's not possible.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data