The Configurable Validation (BORULE) page is available in Advantage Administration, Financial, Vendor Self Service, Performance Budgeting, and Human Resource Management applications. The Configurable Validation pages are maintained by a System Administrator to define validations/preconditions/rules specific to a transaction or a reference page. Edits defined on these pages will work as an additional validation for a specific reference page/transaction in addition to what is indicated at the application code level.
These edits are applied to business objects and are not page specific. For example, if in the Financial application a validation is added to the Purchase Order Header component (PO_DOC_HDR) then it is evaluated for each transaction (including clones) referring to the Purchase Order Header component.
The following key fields can be defined on this page:
Active – Only validations that are marked active will be considered for evaluation.
Priority – Defines the priority or sequence in which the validation will be evaluated. If there are more than one validation defined for a business object, then evaluation will be based on Priority. Records with a low number gets a higher precedence (that is, a record marked with Priority 1 will be evaluated before a record marked with Priority 2). If two records for the same business object are added with identical Priority, then the one added first takes precedence (based on Validation ID). Default Priority is set as 999.
Validation Type – Indicates the type of record.
Validation – Records marked as a Validation are edits, which on evaluating (expression as part of Validation) as successful will issue an error message as configured.
Precondition – Records marked as a Precondition are just verification points and on evaluating (expression as part of Validation) as successful will continue processing the next set of records (Validation or Precondition). Otherwise, evaluation of additional validations will stop for the selected record.
For example: If there are 5 validations defined for PO_DOC_HDR and the first (Priority) one has a Precondition for Transaction Department Code 010, then a PO transaction with any other Transaction Department Code will not process beyond this first rule.
Business Object - Validation will be applied to the provided business object. This is the Business Object Name in Performance Budgeting. This is the technical table name in all other Advantage products.
For example, if applying a validation for the Financial application’s Purchase Order Header component then use PO_DOC_HDR.
For example, if applying a validation for the Performance Budgeting application’s Fund Header component then use Fund2.
Trigger Action - The Trigger Action specifies the system event validation associated with and activated. This is an optional field and is not applicable if the Validation Type is Precondition.
Note:
For validations configured on transaction business objects, even if the Trigger Action selected is Inserted, Updated, or Inserted or Updated, the validation is still invoked on the Validate and Submit actions.
The Audit Logging Trigger Action is used to trigger validation during the Audit Logging event. This validation is not performed during the regular business object events. It is validated only during the Asynchronous audit logging action. Audit logging rules are evaluated using an internal admin session as these rules are executed on a different thread where the existing session won’t be available.
Validation – Defines the actual edit or expression that needs to be evaluated to validate a record for the given business object. The expression used should evaluate as true or false.
For a Validation Type of Validation, the record will be rejected (to issue error message as configured), if the expression is evaluated as successful.
For a Validation Type of Precondition, the record will be accepted (to continue evaluating the rest of the Validations for the Business Object), if the expression is evaluated as successful.
The following fields capture the user feedback details associated with the validation. This section is only displayed if the Validation Type is Validation.
Message Code - Allows you to select an existing Code defined in the system on the Messages table and associate it to the validation. When an existing Code is selected, the system will use the Severity and Text defined on the Messages table. This field cannot be populated if a value is provided in the Validation Severity and/or Validation Text field. This is not available in Performance Budgeting.
Validation Field - Specifies the attribute name of the field that should be validated on the selected Business Object. This information will be used show a visual error indication on the field to the user when validation fails and the record is rejected.
Validation Severity – This field allows you to provide a validation severity instead of choosing an existing Message Code. This field cannot be populated if a value is selected in the Message Code field. Validation severity works in conjunction with Validation Text to render a custom user feedback message when validation is not met.
Validation Text – This field allows you to provide custom validation text instead of choosing an existing message code in the system. This field cannot be populated if a value is selected in the Message Code field. Validation Text works in conjunction with Validation Severity to render a custom user feedback message when validation is not met. Note: Message Code does not exist in Performance Budgeting; therefore, only the Validation Text field is available.
Refer to the following topics for additional information: