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

Question

Question

Matching a Not In statement to a multivalue field

Workflow
Updated September 28, 2021
asked on September 5, 2019

I have a multivalue field with claim numbers. Workflow has a conditional statement - If Current Claim Number is not in MultivalueClaimToken. The Apply Index option has been chosen, I've tried using comma, semi colon and line break all with the same results. Even though the claim number is in the token, it sees all the values as one value instead of evaluating each value separately.

I also tried Does Not Contain with no luck. 

0 0

Answer

SELECTED ANSWER
replied on September 5, 2019

This expected behavior. Workflow does not have handling for sets. So each value is compared individually and because the first one is not the one you're looking for, the condition evaluates to true.

 

I think if you flip the order, use a delimiter to "flatten" the multi-value token and change the condition to "contains", you'll get the desired result ("a,b,c" contains "b").

4 0
replied on September 6, 2019

Thanks, Miruna. flipping the order worked!

0 0
replied on September 28, 2021

Wait, because the first one is not the one we are looking for, it evaluates to true. This is not true.

To say that something is in, means that it is part of the contents, not all of the contents. Evaluating only the first thing you find can never lead to a result.

How does flipping the order solve this? Then it will check the last thing and decide true or false returning again an incorrect response.

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 ...