Condition in Flow Designer to see if a list collector contains a value

[Adam Robbins1]

What is the best way to use a condition in Flow Designer to see if a list collector field contains a value?

In my use case, I am trying to see if a certain Type is set on a Group record.  When the Flow executes, it keeps returning false even though the Flow execution shows:

4937c6c91b7e141034b485dae54bcbd1,1cb8ab9bff500200158bffffffffff62LIKE1cb8ab9bff500200158bffffffffff62

Thanks,

Adam

[Brian Lancaster · Accepted solution]

When I have done something similar with UI Policies as a conditions it is 

List Collector contains sys_id your want to act on.

I would think something similar would work in flow conditions.

[Adam Robbins1]

Thanks Brian!  Turns out when I copied the sys_id, it added a blank space at the end.  Once that blank space was removed, then the contains worked.

[psyherin]

We had similar issue and when we reached out to ServiceNow Support they advised addition of a blank space was related to a known bug when using flow designer on latest version of Chrome.

Most Probable Cause: The issue, is caused by the latest version of Chrome (105.0.5195.102). When saving a URL (or really any typed field) in IH, there were invisible Byte Order Marks (BOMs) being added to fields in Flow Designer, which would cause incorrect behavior.

Solution Proposed: The root cause of the issue is a defect that is being traced in problem PRB1606387. It is found that a when we edit a flow/subflow/action in a newer version chrome(version 105 and above) it tends to suffix an invisible character into few of the attributes like input variables.

Next Steps: Please use a chrome browser which is older than version 105 and reedit these keys in the payload builder step. Use the browser "inspect element" feature to validate the that the extra characters are no more exists.

Note: The above steps seem to ONLY work on Chrome (105.0.5195.102). This does not happen on older version of Chrome (103.0.5060.134). This was tested on an older version of Chrome (where it worked fine) before being upgraded to (105.0.5195.102) which caused the steps to fail. This issue doesn't seem to exist on Opera nor Firefox.