I have been working on some workflows where I used the condition Value1 is not in Values, where Value1 is a single value token and Values is a multi-value token.

It seems logical that the parameter for this method is a multi-value token, since you would use equals to compare a single value token with another single value token.

However, when reviewing the workflow condition history I see that it only compared with the first item in the multi-value collection. It accepts the multi-value collection but it does not look at anymore than 1 item. How can this be logical? If I ask if something is not in a container, you must check every item in the container before you can return a result.

Looking at the first item you find and saying, this is not it, does not return a true status.

I searched the workflow documentation and there is no mention of the is not in method to explain how it could be used any differently.