nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

updation of document in a workflow

screen123#

I have a query please provide expert opinion on it:

there is a document which has to go in a workflow.Few people in workflow modify the document after which it goes to approver who is also in the workflow.

my question is :

If approver accepts the change ......are the changes automatically applied to the document and its versioned ?

I mean no one has to manually apply the changes accepted by approver.

Find more posts tagged with

Comments

VadimYakovlev

The "changes" are "applied" to the object the moment the .save() or .checkin() method is called

screen123#

to put it another way:

3 people in workflow make changes to the document.....the version of the document should not change..... because none of them is approver.

If approver accepts the change.......this document should be versioned.

screen123#

hi vadim....

please reply to the the same question i have put in another way

DCTM_Guru

"...3 people in workflow make changes to the document.....the version of the document should not change..... because none of them is approver."

If you dont want the 3 people to modify the document, then you should get an annotation tool so that they can make annotations/comments. The approver can then read them and modify the document directly.

screen123#

documentum provides annotation tool? can people in workflow use this annotation tool to make comments?

kinly reply

screen123#

for which all formats documentum provides annotation tool?

PDF it provides ...I know...

tejrajs

not sure if it meets your requirement, but take a look at Brava. You can integrate Brava with webtop and it support a variety of formats and annotations.

kcrkarthik

How about something like this:

1) When starting the workflow, copy the document to another temp folder/cabinet and that document shall be attached to the workflow as the package instead of the original one

2) As the workflow proceeds, different users make change to the (temp) document and SAVE them

3) When it goes to the Approver and if he approves, make this (temp) document as a new version of the original document

4) if he rejects, just delete the (temp) document and the original document remains safe

This is definitely going to cost you extensive coding, but (I'm guessing) it is technically feasible.

-karthik