non-readonly reviewers

I am confused about how a review task that should be able to modify content should work.

Joe Author locks files 1,2,3, makes his changes & submits them to WF

Reviewer gets the task and decides he wants to modify file 2,
but since he is an author/reviewer he cannot since the lock is still in place.

So, I see a couple options, first have the WF unlock the files much earlier in the process (I do not like this option)

I could make the reviewers log in as editors so they can do that, but they have already been trained on webdesk & that will hurt.

Anyone else run into this ?

ANdy

Find more posts tagged with

Comments

Migrateduser

I made my own TakeTask CCI link that locks all files in non-readonly tasks to the user taking ownership. This only works if they take ownership through email.

Also, between every two user/grouptasks is an externaltask that at least sends email notification to the next user/group (probably also checks for content errors, regenerates output files, etc.). In that externaltask I lock all files attached to the job to SYSTEM. That way anybody who tries to edit files through the GUI that area attached to a job will know that they are locked/involved in workflow.

Edited by john on 06/05/03 08:51 AM (server time).