Jared,

First of all, Thank you for your input here.

Okay, I'm trying to follow you. So, each user task uses a different form. How do I handle capturing each of the signatures they are stored in different fields? Do I only use one and add all the signatures to that one form?

No the user tasks can stay the same as you have them. My concern is with your two merging inclusive gateways "Collect All Required Signatures" and "Rejections Gateway Signatures". Keep your user tasks and have them use different signature fields. Then just have one inclusive gateway after them for "Merge branches". After that, use an exclusive gateway with conditions to either Route to IT security approval OR send the rejection email. 

Your process branches, then for each branch has user task then exclusive gateway to either inclusive gateway 1 or inclusive gateway 2. 

You need it to branch, then for each branch go to user task, then the same inclusive gateway. AFTER the inclusive gateway, then do that exclusive gateway logic. 

Okay, so correct me if I am not following:  1) Inclusive split to send the tasks then 2) Inclusive merge to Collect signatures tasks, then 3) run a Exclusive condition for whether there are any rejections or not 4) send to Security. Am I following you?

This is my hardest form so far, and I do appreciate your help. :)

Yes exactly. 

In principle, once you branch with an inclusive or parallel split, make sure you then merge each branch with the same inclusive parallel merge. You will run into trouble if you use gateways within each branch and then use different gateways to merge. Your new solution of merging THEN using an exclusive is perfect. 

This is how I changed it, but it still terminated and not sure what I did wrong? In my test I only chose two of the applications and got both signed, then it didn't know what to do to send to Security and terminated.

Maybe my conditions were wrong or am I missing another gateway?

see below

Your process diagram looks correct so long as the inclusive gateway can EITHER go up to Route to IT security Approval OR branch into 1 - 7 of those user tasks. If it goes that top route and a few of the user tasks, that merge gateway may get confused. 

That said, what step is throwing the error and terminating the process? 
Can you show your gateway conditions on that step and possibly what variable values you are using? 

It looks like the Exclusive gateway decision is throwing it out.  For each signature request they are asked the question "Are you rejecting this form?", then they answer Yes and hit the Reject button if rejecting or hit  No and the Approve button.  So I am using this question's answer in my decision tree.  Each application has to Approve to go to Security; or Any 1 selection can reject to end the form.  

See my Approved conditions, then my Reject conditions below. I may not be getting this "And/Or" part right.

This is why I had 7 separate Exclusive decisions before.

I think the problem is in the formatting of the conditions. I would make one branch the "Any rejection" case and get that working with just 

/dataset/rejectAnsBC="Yes" first. 

Then get the first or working with

/dataset/rejectAnsBC="Yes" OR /dataset/RejectAnsDIV="Yes"

once you get that working, add the rest of the ORs. 

For the other branch, make that a default branch so every instance has a place to go. 

So I'm trying to follow, the second branch doesn't have conditions, just make it the default?

And for the Rejections, do you mean for me to add a condition gateway for each of the questions?  Or do you mean just add more rejections once I get the first one working, then test with two and so on?