Question

Forms 10.3.1.635 Not Recognizing Blanks in Branch Logic

Forms Version 10

Updated February 5, 2021

asked on August 14, 2018 • Show version history

Hello,

We just upgraded to Forms 10.3.1.635 and immediately had established Forms business processes failing and choosing incorrect branches.

We were using language like the following:

/dataset/FOM_Invoice_Amount!=""

To say that we wanted the branch to execute only if that field weren't blank - since it's an amount field, it could be any value. It was working in our last version, 10.2 something, but as soon as we switched this failed. We still have the need to evaluate whether or not fields are blank to make branch decisions, and are curious how we can do that now. The following does not work:

/dataset/FOM_Invoice_Amount!=

Any advice is appreciated. I'd hate to have to hit all our business processes and put in superfluous fields just to figure this out.

0 0

Replies

replied on August 14, 2018

Thanks for bringing this issue to our attention. We are looking into it to determine if this is a bug.

0 0

replied on August 14, 2018

I just tested this with a number field and it worked as expected for me. I'm also on 10.3.1.635

However, when I took a closer look I noticed that the condition wrapped something new around my variable because it was a number type.

number(/dataset/numberTest)!=""

Is your field set as a number type? If so, try removing and recreating the condition, or manually adding the type wrapper around it to see if that makes a difference.

0 0

replied on August 16, 2018

Ours was evaluating a currency field, and did not wrap it upon re-creation - we'll do some tests and see if this works for currency as well. Thanks, Jason!

0 0

replied on August 16, 2018

Ok, so we actually had more issues, and it seems to indicate it's not a problem with blanks but rather with "!="

In the above example, we used != to indicate the field shouldn't be blank.

In another instance, a branch would work only when it used =, and not !=. We were evaluating whether or not a vendor had a W-9 on record with us, and so we used /dataset/W9_Status!="Approved" to indicate that we should run the workflow that asks for the W-9. It was not functioning, so we switched which branch was the default and indicated that the other branch should run if /dataset/W9_Status="Approved" and now we're ok.

With both of these examples, it seems to point to an issue with the "does not equal" or "!=" piece of the language.

Not sure if anybody else could verify this?

0 0

replied on July 7, 2020

I posted a similar question today and then came across this one...I hope someone can chime in on this, because my logic tests for blank or not blank on a field and it's not working.

0 0

replied on February 4, 2021

We're using 10.4.5.282, and also having this issue. Just swapped to ="" in the alternate path vs !="".

I'll update results next week, when I confirm it's working.

0 0

replied on February 4, 2021

I can confirm this did NOT work, we had 4 more forms submitted with the field not having any data.

I'm testing = '' now (vs ="")

0 0

replied on February 5, 2021

I was able to prove that SINGLE QUOTE works, where DOUBLE QUOTE does not for BLANK fields.

0 0

You are not allowed to follow up in this post.

Question

Question

Forms 10.3.1.635 Not Recognizing Blanks in Branch Logic

Replies

Sign in to reply to this post.