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

Question

Question

Gateways

Forms
Updated May 31, 2022
asked on May 13, 2022

Hi, I working on a process to merge the all the workflow (wait until everyone approved the form) and go to the next task. I tried using the inclusive gateway and Parallel gateway to wait for everyone to sign, but its calling twice for the next step.

 

 

FMO - PWF Verification Form Main Process.png
FMO - PWF Verification Form Main Process.png (140.2 KB)
Download
0 0

Answer

SELECTED ANSWER
replied on May 13, 2022

It sounds like you probably want to use an inclusive gateway for the merge.

Help file regarding gateways: https://doc.laserfiche.com/laserfiche.documentation/11/administration/en-us/Default.htm#../Subsystems/Forms/Content/Gateways.htm

An Exclusive Gateway will proceed from each incoming path.

A Parallel Gateway will wait for all incoming paths, which will be a problem if some of them are not active.

An Inclusive Gateway will wait for all active incoming paths before proceeding.

Since it looks like you have three paths coming in to the merge, and it looks like only two will ever be active, I think you're going to need Inclusive to merge them.

 

1 0
View 9 previous replies
replied on May 13, 2022

Thanks Mathhew,

I tried adding inclusive gateway as well, but if two path is active, i am getting two task when it merges.

0 0
replied on May 13, 2022

Can you share a screenshot of the process flow details from an instance where it resulted in the duplicate flow?  Comparing that with the screenshot you already shared of the process would be helpful in trying to determine what is going wrong.

0 0
replied on May 13, 2022

 

0 0
replied on May 13, 2022

I changed to inclusive gateway to merge, and tried the process. its duplicating twice.

0 0
replied on May 13, 2022 • Show version history

That screenshot isn't including quite enough detail to speculate.  We'd want to see both paths that are leading into the Inclusive Gateway and that screenshot is only showing one.

And can you also share the updated screenshot of your process after you changed the merge to be inclusive?

0 0
replied on May 13, 2022

0 0
replied on May 13, 2022

Hmmm...  Sure looks like that should be working.

What version of Forms are you on?  I know there was a bug a while back that would cause this behvaior, but I believe it was fixed in 10.3 (which is several years old at this point).

0 0
replied on May 16, 2022

Hi Matthew, we are in version 10.4.5.324

0 0
replied on May 16, 2022

Damn, I guess that's not it.

Okay, you have three pathways leading into that merge.  Am I correct in understanding that the first pathway is always active, and then either pathway 2 or pathway 3 are active?  So there is always two active pathways coming in to the merge?

If that is correct, then perhaps you could first use an exclusive gateway to merge pathway 2 and pathway 3 back into a single pathway.  Then you could have a parallel gatway to merge the always active pathway 1 and the now combined pathway 2/3.  That should always wait for both pathways before proceeding.

0 0
replied on May 16, 2022

Thanks Matthew, I will try and let you know.

 

 

1 0
replied on May 31, 2022

Hi Matthew, I tried as you mentioned, instead of parallel gateway i tried inclusive gateway to merge all the path and it worked.

 

Thanks for your help.

Mano

 

 

1 0
replied on May 31, 2022

That's great!  Glad you got it working.

0 0

Replies

replied on May 16, 2022

You need to get a little more creative to take care of the extra paths. You were correct in using a Parallel Gateway as a Merge, you just need to change how the paths work.

In the following example, the workflow will split into 3 paths EVERY time because of the parallel gateway. The Parallel Gateway Merge will wait for all 3 paths to come back before proceeding. That becomes a problem if one of the user tasks never happens.

One solution to this issue is to add Exclusive Gateways in front of each User Task and after as follows.

This way it will ALWAYS split into 3 paths, but if it is not required to go to a specific user task a condition is set on the Exclusive Gateway that skips it and proceeds to the merge gateway and satisfies the incoming path.

If I'm off in my understand, please let me know.

 

2 0
replied on May 16, 2022

Damn, I guess that's not it.

Okay, you have three pathways leading into that merge.  Am I correct in understanding that the first pathway is always active, and then either pathway 2 or pathway 3 are active?  So there is always two active pathways coming in to the merge?

If that is correct, then perhaps you could first use an exclusive gateway to merge pathway 2 and pathway 3 back into a single pathway.  Then you could have a parallel gatway to merge the always active pathway 1 and the now combined pathway 2/3.  That should always wait for both pathways before proceeding.

You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Attachments
Related Posts
Loading ...