You are viewing limited content. For full access, please sign in.

Question

Question

Rejections Within a Parallel Review

Forms Version 10
Updated June 21, 2018
asked on June 20, 2018 • Show version history

I have a workflow with a parallel review. The 4 Discipline Leads receive the task to assign who in their discipline will prepare and verify the form next. Each Discipline Preparer writes up their portion of the form and forwards to the Discipline Verifier. The Discipline Verifier has the ability to check a box for Verified or Reject.

This is when the process terminates. I'm sure I'm not using my gateways properly (worked fine when I was using the Approve/Reject buttons, but I changed it to a radio button because I wanted to capture rejection comments), so now I'm only using one action button:

Can some provide guidance?

0 0

Answer

SELECTED ANSWER
replied on June 21, 2018

I forgot that I created four different Action fields: dpeVerifierAction, nuclearVerifierAction, structuralVerifierAction, and thermalVerifierAction. Once I changed them, the process worked as I expected without doing anything with the gateways.

Thank you for the detailed answer and making think about the various reasons for this failing!

0 0

Replies

replied on June 20, 2018 • Show version history

What termination message are you getting? My guess would be that it is not getting either of the expected results so it has no valid path.

Also, something to note is that if you're using the same "action" variable on all of those forms then they will overwrite one another's entries.

For example, if you have two parallel tasks and user 1 enters "Reject" then the next day user 2 enters "Verified" the only value you'll see at that point is "Verified."

 

As far as the variables go,

First, I would choose one to be your "default" path and remove the condition. I think best practice is to always have at least one default so it has somewhere to go no matter what happens with the conditions.

Second, check the variable values in the instance history to see what it is actually storing for your radio buttons. For example, it would fail if it is looking for "Reject" and the value is actually "rejected"

Third, you need another merge gateway before that first parallel. Forms does not like multiple incoming and multiple outgoing sequence flows on one gateway (The error should appear if you validate).

Basically, a gateway should only branch in one direction; multiple in, or multiple out, but never both. If you need to do that, you use one to merge and connect another to split it again.

0 0
SELECTED ANSWER
replied on June 21, 2018

I forgot that I created four different Action fields: dpeVerifierAction, nuclearVerifierAction, structuralVerifierAction, and thermalVerifierAction. Once I changed them, the process worked as I expected without doing anything with the gateways.

Thank you for the detailed answer and making think about the various reasons for this failing!

0 0
replied on June 21, 2018

Glad you sorted it out! I still highly recommend having at least one default path any time you have conditional branches.

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...