Hi,

you could:

create a validate rule named IsItemApproved under Data-Item to check .Approval != false (here you validate one object) and set a message

call an activity on your Flow Action

Activity step = loop on each Data-Item     method = obj-validate     step page = .ItemList      (Add ItemList in you Pages&Classes tab)

    Validate = IsItemApproved

Add a child,    when hasMessages is true Exit Activity     is false skip step

No need to call a method here

You will have only one message, not many

Damien

Hi IKondrashov

You can do this in validation rules itself.

You need to have two conditions, 

1. First one is to calculate the length of pagelist which you can do using the Utility function, @sizeOfPageList()>0

2. Another condition is to see if the Approved property inside you page list is true, you can use @isInPageList(x,y,z) to evaluate this, 

So, if the first codition is true and second one is false, show the message, otherwise the validation is passed.

Solution given by Dileep_Incessant is better in terms of performance, as you will only pass the parameters to the existing functions instead of creating the new rules like activity. Also, you don't have to iterate on the pagelist and call the Obj-Validate. Say your list grows to a higher number of items, then iteration will take that longer, but the function will still take lesser time.

I have used both the functions mentioned by Dileep in my applications, though for a different scenario, and they work very well.

Moreover, the functions are still going to be called from the single validation rule, so it is a better option.