Question

On-Prem Workflow - "is not in" does not return proper FALSE value

Workflow Self-Hosted

Updated August 19

asked on August 13 • Show version history

This should return false because the student number is in the data.

The workflow documentation does not explicitly say what parameters is not in takes so we googled it and it said either a collection or CSV values.

We tried a collection first as a multi-value token and after finding that it kept returning true we tried CSV files in a single line token.

Neither is returning the correct output

0 0

Replies

replied on August 13

Is the list on the right side of that condition a single value that you set to a comma-delimited list?

If yes, then the behavior is expected. You cannot inject the list like that, it is treated as a single value, so the evaluation fails because "13955" does not match the full value on the right side.

A correctly configured condition will look like this:

The evaluation looks like this;

I'm not sure why Google told you CSV files, those are not supported in conditions.

0 0

replied on August 13

First we tried a collection (multi-value) then we tried the CSV after the multi-value returned true when it should have returned false. So we need to use a space delimiter instead of comma?

0 0

replied on August 13

The right side of the condition does not take a multi-value token. If you put one in, it will only use the first value from it. So in the example above, it would check whether 13955 equals 10094.

0 0

replied on August 18

In your image your putting all 3 options with a space delimiter. So why don't we just do that? I thought we use comma as the delimiter, but it seems space is the proper delimiter here.

0 0

replied on August 14 • Show version history

looks like the best way to process if a value is in a multivalue token is to use a repeat. change the extension of the attached file to wfi and then import it into workflow to see this in action.

Here is how it is configured, but the solution provided by @████████ is simpler.

Demo Not In Collection (MultiValue).txt (28.56 KB)

| Download

0 0

View 2 previous replies

replied on August 17

You could flatten the multi-value token into a single value delimited by a distinctive character that's unlikely to be in the values and then check against that.

For ex,

will produce an evaluation like this, where the @ ensures that we're matching full values rather than a subset:

2 0

replied on August 18

I can't seem to import this to my cloud system and don't have easy access to an on-prem system.

Did you put a for each value inside a for each value to check on a value by value case? For 2,000x2,000 values that is 4 million activities. We would go from 2,000 activates to 4 million in this case where we are checking against 2,000 students and up to 2,000 submissions to verify that each student submitted their form.

0 0

replied on August 18

I think this "contains" will likely work on a comma delimited string. Or in this case we are looking for does not contain. I am going to recommend they try that. I am not sure how is not in is any different than does not contain.

Google description of the 2 methods

Is not in: You look at an item first. You ask if it lives inside a group.

Does not contain: You look at the group first. You ask if it holds the item.

0 0

replied on August 18

We tried that and it took 2 hours to finish checking 2k values against 2k values.

0 0

replied on August 19

Self-hosted workflows can be imported into Laserfiche Cloud via Deployment Manager. In your Cloud account, create a deployment package and add the WFI file to it, then deploy it into that same account.

0 0

You are not allowed to follow up in this post.

Question

Question

On-Prem Workflow - "is not in" does not return proper FALSE value

Replies

Sign in to reply to this post.