Recently I was struggling with a rather weird issue at Flow Designer, and it took me a lot of time and nerves to find out what caused it.
The issue occurs when checking in a condition whether a String field has any value or not. For better comprehension, I have prepared a very simple scenario: When an Incident record has a value not only for "Short description" but also for "Description" a log output should be written. So, the flow is pretty simple:
For the Incident with the number INC0006865 the condition should be fulfilled but for INC0007001 it shouldn't (yes, I made sure, that the field "Description" really has no value!):
The test run for INC0006865 works as expected. Both the short description and the description have a value and therefore the log output is written:
The second test run for INC0007001 shouldn't run into the Log branch, right?
But it did! So what's the issue?
To shorten it: The problem is that the Flow Designer smuggles in a blank char into the value field of the condition, but you don't recognize it, as it is invisible. Only if you select everything in the field, the blank char becomes visible:
After clearing all condition value fields, the Flow worked as expected:
I hope I was able to save you the trouble I had. You know of other bugs? Report them here in a comment!
6 Comments
