You are here: Business Rules > Attached Rules > ValidateExpressions

Oracle® Insurance XML Configuration Guide Release 9.4.1.0 E23637_01

# ValidateExpressions

## Description

The Validation Expressions section in a screen rule or a transaction supports the ability to configure "hard" edits or pop-up error messages and to optionally suggest fixes.

Note: This business rule is overridden at the transaction level.

ValidateExpressions Element/Attribute Table
Element/Tag | Definition | Attribute | Element/Attribute Value and Description
--- | --- | --- | ---
<ValidateExpressions> | The opening and closing tag for the business rule. |  |
<Expression> | Required and Repeatable Element; This tag specifies the error messages to be displayed on the screen when a specific Condition is evaluated to be True/ False. |  | Required Element value; Expression Specifies the condition that needs to be evaluated upon trying to process the transaction.
|  | TYPE | Optional Attribute; ErrorOnTrue/ErrorOnFalse Tells the math engine to error if the expression is evaluated to True or False. ErrorOnTrue If the Expression is true then displays the error message. ErrorOnFalse If the Expression is false then displays the error message. Note: ErrorOnFalse is a default value if TYPE="ErrorOnTrue" is not specified.
|  | FIX | Optional Attribute; ="ErrorFixTipMessage" To provide instructions to the users to guide them in correcting the issue that caused the error message. The actual error fix tips should be specified as the value. Example: =========================================== ERRORNUMBER ErrorFixTip =========================================== LH001 - Change The Members Age or Override U001 - (null) =========================================== If the LH001 Error Number is specified in "ERRORNUMBER" attribute then in the "FIX" attribute the "ErrorFixTip" should be configured.
|  | OVERRIDABLE | Optional Attribute; Yes: the error messages will be displayed with a check box in the Error window. Clicking the checkbox will allow the user to override the error. Auto: Defines the ability to automatically override the error. SecurityRole: This attribute value is used to indicate the error message can only be overridden by someone with a specified security role. The security role name from the AsSecurityRole database table can be used to specify the security role as comma separated list. For example, OVERRIDABLE="Yes, SecurityRole1, SecurityRole2, SecurityRole3". No: If set to "No" errors cannot be overridden.
|  | ERRORNUMBER | Optional Attribute; ="ErrorNumber" Indicates the field value to define error message activity. Code values for error message from the AsErrorCatalog database table. Example: LH001, U001, V000, V001, V012, V020
|  | MESSAGE | Required Attribute; ="ErrorMessage" This attribute is used to specify the error message that should be displayed upon evaluating the condition.

## XML Example

    <ValidateExpressions>

    <Expression TYPE="ErrorOnTrue" OVERRIDABLE="Yes, Super" MESSAGE="Complex
     policy change event must process within current modal period." ERRORNUMBER="UOO1"
     FIX="To process on this date, at least one Premium transaction must
     be reversed" >DaysDifferenceBetweenPreviousPaidToDateAndEffectiveDate &lt; Zero

    </Expression>

    </ValidateExpressions>

Copyright © 2009, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices

Open table of contents