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

Question

Question

Forms Gateway not taking the right path using the Not This option of !=

Forms Version 11
Updated July 14, 2022
asked on July 13, 2022

Could someone help me troubleshoot why I can't get a Forms process Gateway to take a path based on a field variable being NOT this or that (being NOT this supervisor or that supervisor)?  Of note is that it was working when there was only one supervisor they wanted to skip this step.  But now that I'm trying to make it skip for two different supervisors, I can't get it to work.  Here is my last configuration attempt and negative result:

  • It did assign him to the Supervisor step:

 

  • This was the name in the Supervisor field:

 

  • This is how the design process Exclusive Gateway was set up:
0 0

Answer

SELECTED ANSWER
replied on July 13, 2022

You are saying: Not equal to A OR not equal to B OR not equal to {empty string}.

This will always avaluate as TRUE because any one of the three options being true will evaluate the whole thing as TRUE.  A is false for one, but true for the other two - same with B and empty string - C is true for all three.

I think you want to use AND instead of OR.

Not equal to A AND not equal to B AND not equal to {empty string}.

Now all three have to evaluate as TRUE for the whole thing to evaluate as TRUE.  It cannot be A and it cannot be B and it cannot be an empty string.

0 0
View 8 previous replies
replied on July 13, 2022

Hi Matthew.  Ahha!  Thank you!  I did try And/or, but I didn't think AND would be right because I figured it would be saying that the field had to have Randy's name in it AND Nicks name in it AND be blank.  So, I was reading it opposite of what it was.  Thanks, I will give this a try!

1 0
replied on July 13, 2022

Yeah, it can be easy to get these turned around in your head, and sometimes you just need another pair of eyes. cool

0 0
replied on July 13, 2022

Thanks, Matthew.  I've marked your response as Answer for now, although I won't truly get the answer until tomorrow when the seasonal workers all start out their new day.  I'm sure this is it, though!

1 0
replied on July 13, 2022

Okay, it didn't like the AND's...  The forms are suspending  with this error:  "Routing cannot be split to any subsequent branch."

0 0
replied on July 13, 2022

it's not being picky about and versus AND is it?

0 0
replied on July 13, 2022

Ummm... ?   and versus AND ?

0 0
replied on July 13, 2022

I was just debating whether it was case sensitive or not.  When you use the buttons to help built the outflow definition the and command is lowercase, but as we've been discussing here, we were using the AND command in uppercase.

I'm not immediately seeing what the issue is.  Can you share the full details of all three outflow options as you see them now?

0 0
replied on July 13, 2022

Okay, I've set those as lowercase now.  I'll let you know if that was it!  Thanks again!

0 0
replied on July 13, 2022

Ho!  That worked!  I decided to run a test immediately instead of waiting for the next shift of workers tomorrow morning.  Confirmation will have to come tomorrow morning for sure, but I'm positive that was it!  Thanks!

1 0
replied on July 13, 2022

Great!

0 0
replied on July 14, 2022

Everything is working perfectly this morning!  Thanks again, Matthew!

1 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...