JavaScript is disabled on your browser.

Edit the Validation of Form and Request Values

Enter the name of the parameter to be checked in Name, such as rq_Test, if you want to test a user-defined request parameter with this name. The following areas of validity can be selected: Items with greater areas of validity take precedence here. With the Systemwide area of validity, a parameter will always be checked, whereas selecting Restricted to application area will only check the parameter values within an application. If you wish to test, for example, whether your test parameter has the value “Hello” on the main page of an application, select the Restricted to application page area of validity.

Next, select the mode for the error output. Here you have the option of outputting it as a Warning in logfile or Error message in logfile and cancel action. For our example, the type Test valid values against a predefined list is appropriate.

After you have selected an area of validity that refers to an application, you can in the following, by clicking on Search, select the desired application, or if the area of validity Limited to application page is selected, also select the page.

In Error message, you can enter a text that will be output into the logfile if an error occurs. With ValueSetInputValidator, the allowed value must also be defined in the lower area of the dialog. Click on Add in order to enter a value. In addition, you must decide whether Empty values are allowed, and whether Capitalization should be taken into account.

The logfile portal.log, to which the portal log will be written, can be found in the portal directory \log.

For the parameter type Regular Expression Validator (see appendix), you can enter the Pattern that you want to search for. You can recognize a valid pattern with the symbol; an invalid pattern has the symbol. In the Test field, you can enter character strings in order to test your pattern. You can recognize valid entries with the symbol, and invalid entries with the symbol.