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

Question

Question

Forms 10.2 Validation

Version 10 Forms
Updated September 26, 2024
asked on March 16, 2017 • Show version history

Could someone please explain the use of the new Forms Validation?

  • No validation
  • Validate User Input
  • Validate All

This is very little information on this in the help files.

0 0

Answer

SELECTED ANSWER
replied on March 17, 2017

To add on this, validation options give the Forms designer more control over their process. Validating all input applies to forms submitted by users, but also through Workflow, either through the HTTP Form Post or the Invoke Business Process activities, as well as any other direct posts to the Forms server without loading the user interface. Since there is no user interface, required fields and such would not be enforced by the front end when forms are submitted directly from WF. For data consistency, you may want the back end to double-check the proper values have been submitted.

In certain cases, you may want WF to be able to submit the form with missing data while still enforcing completeness when the same form is submitted by a user. This would be when you would set validation to "user input only".

Obviously, "no validation" is the least desired state, but it is provided for completeness.

1 0

Replies

replied on March 16, 2017

This is for backend validation which will validate the data in the backend after user submit the data. The front validation is always available when user fill the form.

No validation means it won't do backend validation, so the behavior is consistent with Forms 10.1 or before.

Validate User Input means it will only do backend validation for those nonr read-only fields.

Validation All means it will do backend validation for both editable and read-only fields.

4 0
SELECTED ANSWER
replied on March 17, 2017

To add on this, validation options give the Forms designer more control over their process. Validating all input applies to forms submitted by users, but also through Workflow, either through the HTTP Form Post or the Invoke Business Process activities, as well as any other direct posts to the Forms server without loading the user interface. Since there is no user interface, required fields and such would not be enforced by the front end when forms are submitted directly from WF. For data consistency, you may want the back end to double-check the proper values have been submitted.

In certain cases, you may want WF to be able to submit the form with missing data while still enforcing completeness when the same form is submitted by a user. This would be when you would set validation to "user input only".

Obviously, "no validation" is the least desired state, but it is provided for completeness.

1 0
replied on April 11, 2017

Hi Miruna/Xiuhong,

Just having a look into this functionality - when you say "back end validation" I take it this means the inputs are validated when they are received by the server?

If so, what happens if the validation fails? Does the request just not get processed? Or is there a notification it has failed somewhere?

Thanks, Dan.

0 0
replied on April 12, 2017

If it failed, user will get an error such as following screenshot when submit  and the submission won't be processed.

 

2 0
replied on March 16, 2017 • Show version history

Hi Peter

When you use Validation, it provides a visual queue to the user by the field turning green when the users input has met the Validation regex or other validation assigned to the field. Useful whenever an input string may have a special for at such as combination of letter or numbers such as phone, acct, serial numbers, etc. Also ability to set limits on number fields and more, such as a field input needs to be between 1 and a 1000 and more. You kind od just have to dig into it a bit and play to get the full scope of what it can do.

1 0
replied on September 25, 2024

Thank you all for the explanations as I had the same question. 

If I set up the for settings to "Validate All", will it still respect the Field rules for hidden variables? 

Example: a variable is set as required, but I set up a field rule to Hide always but with the "Ignore data when..." option selected, will it respect that?

 

Thank you!

0 0
replied on September 26, 2024

Hi Patricia,

I've just tested on latest Forms (11.0.2311.50553), with this scenario: a variable is set as required, but I set up a field rule to Hide always but with the "Ignore data when..., it won't block the submission, so the answer is yes, it still respect the field rules to ignore the field.

1 0
replied on September 26, 2024

Thank you!

I couldn't test it because the process is in production, so I appreciate your time to test it. 

 

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

Sign in to reply to this post.

Details
Related Posts
Loading ...