How to implement a logic any validation is triggered, the button is disable.

RE: How to implement a logic any validation is triggered, the button is disable.

Harsha Sharma — Tue, 22 Jul 2025 08:40:25 GMT

I agree! Better to hide the buttons then show it disabled.

Yet I have seen users inclined to see the disabled buttons - to be aware of an action that might enable when certain conditions match rather than forgetting that there can be an action here and is just not visible now.

RE: How to implement a logic any validation is triggered, the button is disable.

Stefan Helzle — Tue, 22 Jul 2025 08:00:43 GMT

I do not allow disabling submit buttons in any of my projects. IMHO this just leads to a bad or clunky UX.

RE: How to implement a logic any validation is triggered, the button is disable.

Shubham Aware — Tue, 22 Jul 2025 07:52:43 GMT

Create one expression rule with all validations that returns a dictionary/map of errors. Use it in both component validations (accessing specific fields) and button disabled (checking if any errors exist).
This gives you single source of truth for all validation logic - no duplication, easy maintenance.

RE: How to implement a logic any validation is triggered, the button is disable.

Yashwanth Akula — Tue, 22 Jul 2025 07:49:20 GMT

Hi Peon

You can use the "validate" parameter in the submit button, so if any validation is triggered in any of the components, the submit button will not submit the form.

But if you need to disable the submit button, I suggest creating a rule for validations, keeping every component validation in that expression rule, and using the rule in components and also in the submit button at the disable parameter. Whenever any validation occurs, make disable true.

Hope this helps! Looking forward to seeing other approaches as well.