Using conditions as a Flow Action input

[Uncle Rob]

I'm building a custom Flow Action that asks for the Table and Conditions as inputs.

Here I am entering the table and conditions

And here's what Flow Designer thought the conditions were at runtime.

It LOOKS like that's an encoded query.... except there's nothing that joins one line to the other.  So when I leverage this in the script....

The results I get are consistent with it only processing the first line of the conditions.

So... am I wrong in thinking Conditions should store in the database like an encoded query?  Here's a business rule I wrote with teh exact same conditions:

So I guess my questions are....

1)  Why does Flow Designer store the conditions in such a weird way?

2)  MORE IMPORTANTLY:  How can I Table and Conditions in a SCRIPT in a custom Flow Action?

[OlaN]

You are in great luck, there an awesome video, that covers this specific topic. 😄

Also, you need to update your go with the flow collection page with the latest addition.

[Uncle Rob]

HAH!  I see what you did there.

[kalyan vallams1]

Hi,
were you able to figure this out ? i am having a similar issues when i am looking up a document ID field and passing it to a wait for condition. I have reviewed the video posted below however i dont see a technical reason why a custom action would work vs a OOB wait for condition action.

i am trying to pass the condition from a condition field on a table.

kal