You are viewing limited content. For full access, please sign in.

Question

Question

Easiest Way to Reject a Form While Missing Some Required Fields

asked on August 12

I'm curious how other users are managing use cases like this.

Owner of the process I'm creating wants an approver to be able to click a "Reject" action button on the form to return it to an earlier stage in the process.  But they want to do it without filling in a dozen required fields on the form (basically make them required when submitting but not when rejecting).

I know I could do this with Field rules and a checkbox/radio button/etc. to make the decision - but they really want it to be with the submission buttons.

I handled this on the Classic Designer by having Javascript remove the required attribute from the fields when the Reject button was clicked, and they are wanting that same functionality in the Layout Designer.

Any suggestions or tricks that people have learned to make this kind of thing work in the Layout Designer?

0 0

Answer

SELECTED ANSWER
replied on August 12 Show version history

I usually handle this by creating my own Approve/Reject radio buttons with a single Submit button.

Then, I set field rules based on the radio buttons.

2 0
replied on August 13

Yeah, I think that might end up being the way to go.  Thank you.

0 0

Replies

replied on August 12

You can use a radio button to select your approve/reject decision instead of using a submit button for it. This way, you can conditionally require fields only when approve is selected.

3 0
replied on August 13

Yeah, I think that might end up being the way to go.  Thank you.

0 0
replied on August 12

Generally what I do in these use cases are to only enable the approve button if all the fields are completed while reject has none such requirements. We then add a note to said fields that must be completed before Approval is allowed. It is not as clean since it is harder to tell required fields, but does fit the use case. 

1 0
replied on August 12

That might work for some use cases.  Thank you.

0 0
replied on August 12

Have you taken a look at using Process Stages in your process?  I use them along with field rules to enforce the field being optional for operations in that Process Stage.

 

1 0
replied on August 12

I've done that in multiple cases - but I don't think it will work here where I have a form that is being considered by a user for approval or rejection (with rejection being to return it to the prior user).  With approval, we need to make sure the user has populated those fields, but with rejection they don't have to.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.