Overview

All forms must pass specified validation rules. These rules ensure that a form has been configured to collect and integrate key pieces of critical information, depending on the designated form type. 

Validation Status

On the Forms list screen, under the Admin menu, there is a column labeled Valid. Each form is designated as either Valid or Invalid in this column. Forms that do not have a Valid status will never be displayed in the Forms list for users to begin submission on, regardless of other factors such as Publish status. 

Validate Form

A form's validity can be checked and updated on the Form Details screen. On the right sidebar, click the Validate Form button under Other Actions. Once clicked, the Form Validations panel is displayed, listing the form validation rules. Rules with a green check mark have been met and successfully passed.

Rules that are not validated appear in red or orange. Rules displayed in orange, with an exclamation mark icon, will not prevent a form from changing to Valid status, but should serve as suggestions to consider the form configuration before proceeding. Rules displayed in red, with an "X" icon, have failed to pass validation and must be addressed before the form status will change to Valid. One or more failed rules will cause a form to be invalid and prevent use. 

Form Validation Rules

The full list of nCORE's form validation rules can be found below:

• 100 - Form Type must be specified

• 105 - Applications, Service Requests, and Permit Change Forms must have a Program Area assigned *

• 110 - Form Tag must not be blank

• 120 - Form Tag must be unique from other forms

• 122 - Form must have at least one section

• 124 - Form Sections must have at least one control. Section Name: ZZZ

• 125 - Form, Section, and Control Tags must not begin with a number

• 130 - Section Tag values must not be blank

• 140 - Each section, grid control, and table control tag must be unique. Tag XXX is used N times.

• 150 - Control Tags must not be blank. Section XXX Control YYY is missing a tag value

• 160 - Section Control Tags must be unique across non-repeating form sections

• 170 - Section with prefill or autofill enabled must use a prefill/autofill-enabled section Tag (Warning)

• 200 - Application and Request forms should have one section tagged SITE (Warning) *

• 300 - Permit Change forms must have one section tagged PRMT *

• 400 - Sections that use a select list to determine affiliation types must only have 1 contact control.

• 410 - Contact control in section XXX must either be tagged with an Affiliation Type Code, labeled with an Affiliation Type Description, or have a Select control in the same section with tag 'AFFIL' (Warning)

• 420 - Feature location control in section XXX must either be labeled with a Feature Type Description or have a Select control in the same section with tag 'FEATR_TYPE' (Warning)

• 430 - A form should have at least 1, and must have no more than 1, contact with Affiliation Type Code "Applicant", and it cannot be repeatable. This form has Z section(s) that can yield an applicant. (Warning OR Error)

• 500 - Form's short description default text should be changed (Warning)

• 500 - Form's short description default text should be changed

• 510 - Form has a fee but no Fee Category assigned *

• 520 - 'Entity Category to Create' must be selected *

• 600 - Lookup Lists with more than 100 values must be configured as Type Ahead Input controls.

* Not all validation rules apply to all forms. A form's designated Form Type will determine which validation rules apply. Rules listed above are applicable to each form type with the following exceptions:

• Rule 105: Applies only to Applications, Requests, and Permit Change forms

• Rule 200: Applies only to Applications and Request forms

• Rule 300: Applies only to Permit Change forms

• Rule 510: Applies only to Applications and Request forms

• Rule 520: Applies only to Applications, Requests, and Complaint forms

On this page

Related Content