Invariant validation checks
The validateImpl method in the gw.policy.PolicyPeriodValidation class also calls the following code:
new InvariantValidation(Context, Period).validate()This code initiates what Guidewire calls invariant checks. PolicyCenter uses these checks to determine whether a policy has been modified in ways that violate implied constraints to the data model.
The method call creates a new InvariantValidation object, whose validate method initiates the actual invariant tests and checks.
In the base configuration, these tests perform the following entity checks:
Entity |
PolicyCenter checks that... |
|---|---|
|
|
|
If the Business Auto Line exists, then the correct policy line pattern is applied. |
|
|
|
The rate modifier value is within the allowed minimum and maximum values. |
|
|
|
The referenced policy line pattern is compatible with this product. |
|
|
Constraint Errors
If a check indicates that the user-defined product model violates one or more constraints, PolicyCenter generates an appropriate error message.
PolicyCenter stores the invariant errors in display keys. In Studio, in Project view, navigate to . Assuming that you are modifying the display key for U.S. English, open display.properties and search for the following text string:
Java.Invariant.*For example:
Java.Invariant.Modifier.RateAboveUpperBoundcontains the display key:
The rate modifier value “{0}” cannot exceed the allowed maximum “{1}”.
During product model verification, PolicyCenter
replaces the variables {0}
and {1} with the actual
values.
