Page Validation Rules

Description

Displays the page name associated with the validation rule.

Note

The field displays if accessed from the WebApp Vertical View Import / Export tab.

Displays the event that runs on the page, or the name of the field that triggers the event rule to run.

Event rules can be created to run:

• OnLoad – Executes prior to the page displaying, allowing lazy data population.

• OnValidate – Executes when a record is saved or the user clicks the boaStatus icon.

• BeforeDelete – Executes before a record can be deleted.

• Columns – Executes at the record level when a user clicks a specific field.The options display as the names of the columns that can have record-level events added.

Note

The field displays if accessed from the WebApp Vertical View Import / Export tab.

Displays order in which the validations are executed.

Displays the type of validation for the selected page.

Options are:

• Stored Procedure – This setting executes a procedure to determine whether the associated record is valid. Returning a non-zero result will result in failing the validation.

• View – This setting binds the view against the current column key to determine validity. If the view returns any results, the validation rule is considered failed.

Displays the name of the name of the validation which is computed based on the type of the validation and the entity chosen (whether it’s a view, procedure, or plugin), for example, webdcsMARA_FullConstruct_DSP9587DupKeyVal.

Displays the severity level for the validation type for the selected page.

Options are:

• Error – If the record fails this validation, the status will be marked as invalid. Business rules not marked to “Run on Fail” will not run. If this is a row level validation, an inline red bordered text box will appear with the validations text.

• Message – This severity is an informative validation rule which works the same as other validation types but will not negatively affect (for example, failing a message will not fail the record validation) the validity of the record itself. This will show in the UI with a blue border.

• Warning – If the record fails this type of validation they will be prompted to click Yes or No on whether to pass or fail the record. If passed, all business rules set to “Run on Pass” will run. If not, only the ones set to “Run on fail” will run and the record will be marked accordingly. This type of validation will show with a yellow border.

Displays the text when records fail this validation.

If checked, the Validation rule is executed. If not checked, the Validation rule is not executed.

Description

Displays the page name associated with the validation rule.

Note

The field displays if accessed from the WebApp Vertical View Import / Export tab.

Displays the event that runs on the page, or the name of the field that triggers the event rule to run.

Event rules can be created to run:

• OnLoad – Executes prior to the page displaying, allowing lazy data population.

• OnValidate – Executes when a record is saved or the user clicks the boaStatus icon.

• BeforeDelete – Executes before a record can be deleted.

• Columns – Executes at the record level when a user clicks a specific field.The options display as the names of the columns that can have record-level events added.

Note

The field displays if accessed from the WebApp Vertical View Import / Export tab.

Validation Rule Properties

Displays order in which the validations are executed.

Displays the name of the SQL view associated with the validation.

If checked, the Validation rule executes.

If not checked, the Validation rule does not execute.

Displays the severity level for the validation type for the selected page.

Options are:

• Error – If the record fails this validation, the status will be marked as invalid. Business rules not marked to “Run on Fail” will not run. If this is a row level validation, an inline red bordered text box will appear with the validations text.

• Message – This severity is an informative validation rule which works the same as other validation types but will not negatively affect (for example, failing a message will not fail the record validation) the validity of the record itself. This will show in the UI with a blue border.

• Warning – If the record fails this type of validation they will be prompted to click Yes or No on whether to pass or fail the record. If passed, all business rules set to “Run on Pass” will run. If not, only the ones set to “Run on fail” will run and the record will be marked accordingly. This type of validation will show with a yellow border.

Displays the text that displays when records fail this validation.