Review Task Reject issue

I have a Review task in my WFM. The task contains files in a workarea that is read-only to the reviewers. When selects the "reject" route at runtime... the workflow proceeds and the correct subsequent tasks are activiated. However, the Review task is also reactivated. I end up with 2 active tasks.

If I change the workarea permissions so that the reviewer has read/write to the workarea... then the reject flow works properly and the Review task is not reactiviated.

Does anyone know why this is happening?
Does a review task have to point to a workarea the reviewers have read/write access to? If so, is there a way to hide a workarea from the UI even if the user has read/write access to it?

Find more posts tagged with

Comments

nipper

1. Workflows are custom code (though they may be based off of OOTB samples).

2. Sounds like you have a bug in your workflow.

3. If a review task is marked read only then the reviewer does not need write access to the workarea. Otherwise they do.

Migrateduser

Thanks.

That's exactly what I would expect. Read-only task pointing to read-only workarea should be perfectly fine.

And, it is... as long as the reviewer doesn't "Reject". If the reviewer rejects, the Review task completes successfully, but then almost immideiately gets re-activated as if it were never "taken" and completed.

As soon as I make the workarea read/write, the behavior goes away.

hence, my confusion.

nipper

OK, this is all custom code. Hard to do much without digging into the code.

If you can trim down a sample workflow, maybe 3 steps or something, that you can post and will show the problem, maybe someone can help