Well, I actually tried using the Obj-Validate in the activity.
But the 1st problem is that: the value of the property -on which we're going to perform the validate rule-, taken in the activity is the one stored in DB and not the new one entered by the user. I couldn't use the value entered by the user because the Validate rule doesn't take parameters as Input.
The 2nd problem is: when the Validate rule is performed, the result isn't shown on screen and doesn't forbid the user from moving to the next action. Instead, I can see it on the tracer; on the page of the Obj-Validate.
Is the page xp your primary page? I assume you want the messages on pyWorkPage if you're performing a flow action. Try ensuring the messages are on the page that is the primary page of the object you are working on. If that doesn't work I'd look at the context of the section. Does it have a different page? Try putting messages there. Once you figure out which page you need to hit, target the validate with that.
Once we figure out the context, we can go back and try and understand what you meant by the property being from the DB and the user entering a parameter. I don't understand what you mean by that, but let's avoid confusion by focusing on one problem at a time.
>>> in case we "Hide the default action section buttons" and use our own, the validate rule is not executed.
If you trace the working version where you have default buttons, and non-working version where you hide those buttons, how do traces differ ? In particular, pay attention in the tracer to what the primary and step pages are. /Eric