Policy object validation levels

In the base configuration, PolicyCenter defines a set of validation levels that you can use to verify how valid data is before continuing. You can also create your own validation levels. You can use these validation levels in your Gosu validation classes.

PolicyCenter defines a ValidationLevel typelist that you can use to set how valid data must be before continuing. You can create your own validation levels. PolicyCenter uses the priority attribute of the typekeys to order the validation levels. Low priority numbers are more restrictive. Thus, in the base configuration bindable with a priority of 6000 is more restrictive than quotable with a priority of 7000.

The validate-on-commit process always checks against the special validation level default, which is the second-least restrictive level (priority=8000).

In the base configuration, Guidewire defines three immutable validation levels. You cannot delete these validation levels because PolicyCenter code requires them.

Level	Priority	Description
loadsave	10000	The least restrictive validation level against which PolicyCenter validates policies entering PolicyCenter from an external application. All data must pass loadsave to be saved to the database.
default	8000	The default validation level against which PolicyCenter runs the ordinary validate-on-commit process. PolicyCenter executes the flowstep filter at this level.
quotable	7000	The level a policy must pass before it can be sent to a rating engine.

PolicyCenter provides other validation levels in the base configuration. However, as Guidewire defines these levels in the ValidationLevel typelist, it is possible to modify, remove, or even add to them using the Studio typelist editor.

Level	Priority	Description
bindable	6000	The level a policy must pass before it can be bound. Binding finalizes a given job and promotes an associated policy period to the main branch.
quickquotable	7200	The level a policy must pass before it is ready for a quick quote.
readyforissue	5000	The level a policy must pass before it can be issued. Issuance is the special job that occurs after submission, causing the policy to become legally in effect.