Class-based data object validation

PolicyCenter performs class-based data object validation on policy and policy-related data objects. Class-based validation is implemented in Gosu classes. In a Gosu class, you specify how PolicyCenter validates a particular data object. A database commit does not automatically trigger class-based validation.

At any time, you can invoke Gosu class-based validation from PCF files, job processes, wizard steps, workflow steps, integration plugins, and from any Gosu code. The validation class checks that certain conditions are met. The class can raise errors or warnings that includes the validation level at which it failed. For example, after entering vehicles on a Personal Auto policy in the submission wizard, your class-based validation code can check that the policy has at least one driver. If not, the code raises an error at a particular validation level.

PolicyCenter runs full validation on the policy graph at critical points in the job process, such as before quoting or binding.