About Whole Form Validation
For both input tables and document libraries, you can add form validation, which validates the data as a whole, as opposed to validating individual data elements. This is done by creating a Tunnel script and enabling the extra form validation option in the table or library settings dialog box.
CAUTION: When using a Tunnel validation script for data that is input by a guest user, the DiveLine must have a license enabling a DivePort guest user, and that guest user must be configured in Workbench with enough access to run the script. Although there is an expectation that the guest user is entering data that we expect, if the portal is exposed to the internet, the input could come from an unauthorized user. Any code, including Integrator scripts, that uses this data, should handle it carefully.
DI recommends that the Tunnel script accept all table or library attributes and their values as parameters, and that logic validates relationships between columns as needed. The resulting memory model has zero rows if the values for the edit are acceptable. Otherwise, the model returns a set of rows with a dimension called error_tag and an information field called error_msg. These errors are displayed for the user to review when the submitted form has been processed.
For more information about Integrator Tunnel scripts and access control, see