Validation classes in the base configuration

PolicyCenter performs class-based validation on policy-related entities any time that you call for validation on the entity. In the base configuration, Guidewire provides validation classes that you can use with a specific entity. The name of the validation class contains the name of the entity to which it applies or its purpose. The validation classes extend PCValidationBase or PolicyLineValidation, directly or through inheritance. Some examples of validation classes are:

All Lines of Business

AnswerValidation
FormPatternValidation
InvariantValidation

Personal Auto

PALineAssignmentValidator
PALineCoveragesValidator
PALineDriversValidator
PALineQuickQuoteValidation
PALineStepsValidator
PALineValidation
PALineVehiclesValidator
PersonalVehicleValidation

There is nothing particularly special about these entities. Thus, they are not validatable entities in the sense that rule-based validation entities are defined as validatable. Guidewire provides these validation classes to illustrate how to create validation classes for specific purposes. For example, the base configuration validation classes illustrate:

How to create a Gosu class that validates an entity in the PolicyCenter data model. PALineValidation.gs is an example of a class that validates the PersonalAutoLine entity.
How to create a Gosu class that validates a wizard step, such as the Policy Info step in the submission wizard. WCPolicyInfoValidation.gs and BOPPolicyInfoValidation.gs provide examples of this type of validation. See Invoking class-based validation for an example of how to invoke validation from a wizard step.

You can write your own Gosu validation classes and implement validation logic on any entity that you choose. However:

Each validation class that you create must implement the PCValidation interface. A convenient way to do this is to extend PCValidationBase or one of its subtypes.
Each validation class that you create must provide an overridden validate function.