I have a question regarding the validation behavior in a form.
For one field control, I enable the “Show field input warning” option and configure both the validation condition and the corresponding warning message. However, upon submitting the form, the submission is still allowed even when the condition is not satisfied, and only the warning message is displayed.
In contrast, for another field configured as required, the system triggers an error message and blocks the form submission when the validation criteria are not met.
Could you please confirm whether this warning behavior is expected by design? If so, should an additional validation rule be implemented to enforce blocking the submission when the defined conditions are not fulfilled?
Field warnings are not hard stop for the users to move forward. This is working as designed.
Form Views now support contextual messages about the fields that provide users with real-time feedback. The messages, which support When Rules and custom logic, can be paired with a standard Dynamic Text Rule, enabling you to tailor your message through field inserts. This feature improves the quality of data gathered from users, as it reduces the number of ambiguities and errors that can potentially affect Case processing.
Given that field warnings are non-blocking by design, what would be the recommended approach to enforce validation that prevents form submission when specific conditions are not met?
Should this be implemented through a dedicated validation rule?
