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

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

parallel review... sort of.

lucille_arkenst

Hello everyone,

I have a parallel review workflow. Once a certain number of people approve, I want it to act sort of like a group parallel review, such that the task disappears from the other people in the group's task list once approved.

How can this be done?

Thanks!

Find more posts tagged with

Comments

sethatrothbury

It would have to change from a Parallel review to a Pooled review. You'd need two completely separate task-node sections with logic in a decision node for when to jump from one to the other.

lucille_arkenst

Hi Seth

One of the questions that had been driving me bonkers is what makes a task "parallel" and what makes it "group"… and I thought I figured it out but now I think I am wrong.

For this conversion from parallel review to "pooled" review that you described… could you please provide pseudo-code? That might help me to understand.

Thank you!

lucille_arkenst

I think I got it:

&nbsp;&nbsp;&nbsp; <!– PARALLEL REVIEW –>
&nbsp;&nbsp;&nbsp; <action class="org.alfresco.repo.workflow.jbpm.ForEachFork">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <foreach>#{people.getMembers(people.getGroup('GROUP_blah'))}</foreach>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <var>reviewer</var>
&nbsp;&nbsp;&nbsp; </action>
&nbsp;&nbsp;&nbsp; <event type="node-enter">
‍‍‍‍‍‍‍‍

Transition to node…

&nbsp; <!– GROUP REVIEW –>
&nbsp; <task-node name="somebody_review">
&nbsp; <task name="blah:somebody_Review" swimlane="aSwimlane" />
‍‍‍‍‍

The swimlane versus the foreach makes the difference