This is front-end validation which will be triggered after leaving the field, right? Is this a custom password reset? Then you can trigger the validation in a microflow after clicking the button.
by doing the validation into the microflow instead of doing it in the properties
this doc:https://docs.mendix.com/howto/data-models/setting-up-data-validation tell you what is the best practice for validation
If I may suggest – it would be possible to add a second button with the same description, but slightly opaque; The button has no attached action. Make sure you show that button (conditional visibility) only when the field is empty. Otherwise, show the button you already have there.
Here is an example:
In the settings for this button, you see the Continue button that is highlit: it is only shown when the form is properly filled.
Here you see the slightly opaque button (disabled style); it does nothing, and is shown when the field is empty.
This is what both buttons would look like side by side, but you only ever see the one or the other in the actual application:
And yes, the working continue button has a validation sub as its first activity.
In any case, this pattern allows you to disregard field validation – you can only click the button when the field is filled. You could extend this in any way you like. In this application, we have chosen to do the content validation of the fields within a microflow, because we can reuse that microflow in other contexts.
Hope this helps.