Appian Community and Appian Academy are being upgraded. From July 24–August 3, the Appian Community will be in read-only mode. During this time, the site will be read-only and user registration will be disabled. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
There are two button in my form, one is submit another is cancel. I have many validations in my form, but I notice that, the validations are applied to both buttons. I've also tried the validation group, but the behavior is after I click the button the validation will take effect.What I expect is that the verification will be performed after the user has entered the content, and it will only take effect on the submit button. Is this possible in Appian? If the validation group is the only way I can achieve, Is it possible to disable the submit button after the validation triggered?
Discussion posts and replies are publicly visible
The Cancel button issue occurs when its validate property is set to true - switch this to false to prevent validations from firing. To ensure validations only execute when Submit is clicked, assign a validationGroup property to your Submit button, then apply this identical group name to every field requiring validation. This approach means validations remain dormant until Submit is pressed. Regarding disabling the Submit button after validation triggers - this isn't feasible with validationGroup since the button must remain clickable to actually fire those validations in the first place.
Shubham Aware said:This approach means validations remain dormant until Submit is pressed.
Be cautious, though, because adding a Validation Group to a field (still(!!!)) hides its "required" indicator, and there is still(!) no manual workaround for this that I know of. Due to this I usually avoid validation groups altogether except in very small, niche, unusual cases where it's a better approach than other options (like conditionally disabling buttons, etc).