Is there a way to have a submit button that runs a validation group but doesn't care about required fields?

RE: Is there a way to have a submit button that runs a validation group but doesn't care about required fields?

davids0001 — Mon, 14 Aug 2017 19:04:08 GMT

One other solution might be to build the entire form out of sections that are conditionally displayed based on a variable. The "Next" and "Previous" buttons aren't Submit buttons, they just increment and decrement that variable. Only the final button, which you only display when the value is set to display the last page, is a Submit. All the required fields stay required, they stop you from submitting, but you can freely navigate to every part of your form.

Nice bonus is that it only takes up 1 User Input node on the process model and you don't have to create a bunch of loops.

RE: Is there a way to have a submit button that runs a validation group but doesn't care about required fields?

Jason Ruvinsky — Thu, 03 Aug 2017 19:02:54 GMT

That is definitely a good potential solution, thanks for the tip!

RE: Is there a way to have a submit button that runs a validation group but doesn't care about required fields?

Mike Schmitt — Thu, 03 Aug 2017 15:05:42 GMT

If your desire is that the user can't progress to a subsequent page when one of the complex validations (as opposed to "required") has fired, my suggestion would be to consider evaluating the validation logic inside WITH() variables, and disabling the "next page" buttons if there are any errors. I know this won't work in some specific use cases but it's a powerful workaround to this type of situation.