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

Question

Question

Users are able to approve forms when required fields are not complete

Forms Version 10
Updated November 14, 2018
asked on November 7, 2018

We rolled out our first form and users are utilizing the button that appears on the right column (summary/action history) that mimics the buttons at the bottom of form. The issue is when this occurs, there is no validation! All the required fields are left blank and the task is finished, which causes issues in later steps.

Button sample "Setup Complete"

 

How can I stop this from happening?

0 0

Answer

SELECTED ANSWER
replied on November 7, 2018 • Show version history

Go to the user task in the process designer and turn off Direct Approval for this task. If you allow Direct Approval (the buttons on the right side), you are allowing an approver to directly approve the task with no field information. If you want to require the fields, you have to disallow direct approval to force the approver to open up the form and fill out fields. 

1 0
View 3 previous replies
replied on November 7, 2018

Super helpful! Thanks!

0 0
replied on November 7, 2018

Is there any way to populate these fields after the fact? Or to undo the approval?

0 0
replied on November 7, 2018

If the instances have completed, you cannot populate these fields after the fact. If the instances are still in progress, you could add a new user task to the end of the process that is assigned to you (or a team/approver). This user task could show the same form and would allow you to fill in the fields that were missed. 

Once all the missing fields are filled in, you can remove this last user task. 

0 0
replied on November 7, 2018

@████████, I should have been more specific. The process is stuck on a Save to LF task and the data missing is for a required metadata field. Therefore, it can't save to LF.

What can I do in this case?

0 0
replied on November 7, 2018

The two easiest ways to clear out the in-progress instances:

1. Go into your save to repository task, and switch out the variable for some static value (like "a"). Then all the forms will save with "a" in that field instead of the intended value. Once they are all saved to the repository, change the save to repository task back to the variable and go update the metadata in the repository with whatever values you want. 

2. Go into the web admin console and temporarily make the field not required. Then the forms will all save with blank values, you can update the values, then make the field required again. 

1 0
replied on November 14, 2018

#1 worked. Thanks!

0 0

Replies

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

Sign in to reply to this post.

Details
Related Posts
Loading ...