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; } } }

Configuring Minimum Number of Reviewers

vbaijal

Hi All,

I have a review task which has 3 reviewers.I want it to proceed to the next task even if one of the 3 reviewers accepts it and to go back to the previous task if any one of the reviewers rejects it.

For this I tried setting Minimum number of Reviewers as 1 in the reviewers dialog box.

The reject functionality is working fine and the prevoius task gets activated if any one reviwer rejects the task.
But there is some issue when it comes to the acceptance part. Instead of moving ahead to the next task as soon as 1 reviewer accepts it, the task is still waiting for the rest of the 2 reviewers acceptance.

The review type is concurrent.

Could some please help me out as to what other configuration change needs to be made in order to make this work.

Thanks,
Vijaya

TS 6.7.1 SP1
WFM 1.0.0.1
Windows 2003 server.

Find more posts tagged with

Comments

cute_guy

Hi All,

I have a review task which has 3 reviewers.I want it to proceed to the next task even if one of the 3 reviewers accepts it and to go back to the previous task if any one of the reviewers rejects it.

For this I tried setting Minimum number of Reviewers as 1 in the reviewers dialog box.

The reject functionality is working fine and the prevoius task gets activated if any one reviwer rejects the task.
But there is some issue when it comes to the acceptance part. Instead of moving ahead to the next task as soon as 1 reviewer accepts it, the task is still waiting for the rest of the 2 reviewers acceptance.

The review type is concurrent.

Could some please help me out as to what other configuration change needs to be made in order to make this work.

Thanks,
Vijaya

TS 6.7.1 SP1
WFM 1.0.0.1
Windows 2003 server.

If you using AND Gateway then change to OR Gateway

vbaijal

Hi,

Number of reviewers is not fixed in the workflow, so I have used configurable variables on a single review task. I have not used any AND gate.

But when I select 2 reviewers out of the 3 then I can see 2 review tasks which connect to an AND gate and when I select all 3 reviewers then I can see 3 tasks connected to AND gate.(as seen in the webview of the Modeler).

How can I change that?

Thanks,
Vijaya

Adam Stoller

Hi All,

I have a review task which has 3 reviewers.I want it to proceed to the next task even if one of the 3 reviewers accepts it and to go back to the previous task if any one of the reviewers rejects it.
[...]
The review type is concurrent.

Could some please help me out as to what other configuration change needs to be made in order to make this work.

I'm not sure I agree with the logic, but you seem to be saying that you have N potential review steps, and whomever performs the review first makes the entire decision over whether the work is approved or rejected - yes?

As has been stated - if you want this - you need to use two OR conditional gateways - one connected to by all the reject options, one connected to by all the approve options - and in either case you need to make sure that you inactivate all the review steps when any one of them has been acted upon - in the case of reject, you would probably need to reset all of the review steps too.

Try working the idea out on paper first to see if you can make sense of what needs to be done, then try implementing it in WFM.

I still think the logic is flawed, but if it's what you want, you can do it - you just have to use OR conditionals.

PaulW

I think you guys are missing the point here. I am having the same problem.

I have review task, which has 5 available reviewers. I only need one of those reviewers to approve the content. So i set the minimum number or availabel reviewers to 1. And I set the review task to concurrent (so they all receive the notification email).

However, after the task still requires that all 5 reviewers approve the content. Is this a bug?

I am thinking I may have to change this to a group task.

Faizi

I think you guys are missing the point here. I am having the same problem.

I have review task, which has 5 available reviewers. I only need one of those reviewers to approve the content. So i set the minimum number or availabel reviewers to 1. And I set the review task to concurrent (so they all receive the notification email).

However, after the task still requires that all 5 reviewers approve the content. Is this a bug?

I am thinking I may have to change this to a group task.

Yes, I think its a bug with WFM 1.0.1, it was working in earliar version. I had raised in it earliar posting. It will be better if interwoven guy will give reply.

TroyP

Yes, I think its a bug with WFM 1.0.1, it was working in earliar version. I had raised in it earliar posting. It will be better if interwoven guy will give reply.

I agree that this should be viewed as a bug if it is not. I have the same problem with WFM 1.0.1 and TS 6.7.1 on linux.

stat.rptdesign

Firenze

Yes ideally workflow should be able to automatically remove the unneeded tasks.

Here's a workaround approach.

Default unassigned review tasks to a known id .

Use a background job to auto advance any tasks assigned to the known id.

Migrateduser

The same is working fine on WFM 1.0.1 , TS 6.7.1 on Win 2003 server.

I agree that this should be viewed as a bug if it is not. I have the same problem with WFM 1.0.1 and TS 6.7.1 on linux.

santosh013

Yes its a bug as we faced the same issue in WFM 1.0.1.
You should raise the issue with the support team.
Thanks,
Santosh