Steve,

Thanks for your help, question:

What would the rule look like to check for the number of signatures required?

Do you send all three tasks regardless of how many signatures are required?

That will make a big difference because Inclusive Gateways wait for all active branches, meaning if you only had 2 active tasks out of the possible 3, it would only wait for those 2 without any special rules/conditions.

If you send all 3 tasks no matter what, then things would be a bit more complicated.

Hi Jason

What is your logic to determine how many signatures are required? Is it based on a value in  a field or a user selection. In the BP, you would have an inclusive branch to all 3, but the rule would determine which branches to take. If only 2 were required, it would only follow those 2 paths, and then on the merge side, would only be waiting for those branches to be completed

https://www.laserfiche.com/support/webhelp/Laserfiche/10/en-US/administration/#../Subsystems/Forms/Content/Gateways.htm?Highlight=inclusive%20gateway  

It varies from process to process, but it is almost always based on a form variable derived from the user selections. An inclusive gateway before the tasks decides which ones paths become active, and an inclusive after the tasks merges the active paths.

I think it would help to see an earlier part of the business process to see how it branches out and assigns the different signature tasks.

Here is a larger view:

When one is selected it works fine and when all three are selected it works, but when only 2 are selected it sends two emails.

Which email is coming twice? Were you also getting duplicate tasks?

What is the purpose of the "not required" branch after the signatures? I would have expected the task not to even occur if signature wasn't required.

I'd suggest taking a closer look at the instance history for one that only required 2 signatures to see what activities occurred and in what order.

The Route to IT Security (Final Signature) is getting two emails after the Only Signatures Required Exclusive Gateway, when two signatures are needed.

As for the "Not Required" branches, I thought I needed a No branch to go with the Yes branches and haven't thought through that piece yet. It should really never get there unless the approvers are out of the office and it hangs up while waiting for a signature mode.  Suggestions?

Yes, on duplicate tasks as it shows up twice in the inbox. Is that what you mean?  Sorry, I'm slow replying I've looked at this all day and tired

What happens immediately following the signatures tasks really depends on your process flow. Do the users need to indicate whether or not a signature is needed, or should they not even get a task if a signature isn't required?

The signatures I have are all required depending on the Application access selection that is chosen on the form. If they choose General AD access that goes to one Application owner for their signature; if they choose the MeF Application it goes to that owner and if they choose the LCM Application it goes to that owner, then once all have been signed it goes to IT Security to grant the access and sign the final approval. Vary rarely will I have all three on the form, but it could happen.

Okay, so remove all of the gateways asking if they are signed and set the task straight to the Inclusive Gateway?  Do I need conditions on these branches?

I made the changes you suggested and Wow!! I was trying to make it more complicated that it needed to be.  It worked!!!!!

Thank you Jason I really appreciate your help!  This was only my 2nd form to create.  The gateways were confusing me, but I think I have a better understanding now.

Below is how I changed it:

I appreciate all of the input received on this question! It always helps to get another perspective on things after staring at it, over and over.  THANKS!!!!

Robin

Yes, in the inclusive gateway you should have a rule for each of the outflows to determine which of the branches are to be followed.

From what I read above you have 3 outflows based on the Application access selection : 

Application access selection=General AD

Application access selection=MeF Application

Application access selection=LCM Application

In the example below I used a Checkbox selector on the form to choose Application Access