Coverage term types

Direct coverage term type

For Direct coverage term types, you type a numeric values directly into a text box in PolicyCenter. Any numeric value is valid within the bounds specified on the CoverageTermPattern. For example, the limit for building coverage relates to the value of the building. The value you enter in PolicyCenter could be 100000 or 1592410.

Direct coverage terms are similar to ordinary numbers. Guidewire provides syntax support in Gosu that you can use to directly compare DirectCoverageTerm objects with number literals. For example, consider the following DirectCoverageTerm:

BOPLine.NewCov.DirectTerm

You can assign a value to this term and compare it directly to a numerical value. For example:

BOPLine.NewCov.DirectTerm = 100   //Assign a value of 100 to the term
BOPLine.NewCov.DirectTerm > 10    //true
BOPLine.NewCov.DirectTerm < 10    //false
BOPLine.NewCov.DirectTerm == 100  //true

Thus, you can treat a Direct coverage term as a number and use natural syntax in any Gosu code.

Option coverage term type

For Option coverage term types, you select a single numeric value from a predefined list of options in PolicyCenter. For example, options such as 100, 500, and 1000 enables you to select only those specific deductible limits. Option coverage term types enable you to choose specific values and do not let you freely specify any number.

You can assign Option coverage term type objects to, and compare them with, the string literals that are the OptionCode values of the coverage term options from their patterns. For example:

BOPLine.NewCov.OptionTerm = "100"   //Assign value of the term to the CovTermOpt with the value "100" 
BOPLine.NewCov.OptionTerm == "100"  //true
BOPLine.NewCov.OptionTerm == "1000" //false

Package coverage term type

A package coverage term type is a compound collection of limits or deductibles selected as a group, rather than a single value as with an Option coverage term type. You select a package in PolicyCenter from a predefined list of values.

After you define the multiple compound values in a Package coverage term type, you must also provide information to identify the meaning of each value. For example, you must identify whether a value is a limit, and, if so, to what it applies.

Each of the compound values in a Package coverage term type represents one set of multiple terms for a coverage that must be selected as unit. For example, a medical payments liability coverage for a commercial auto policy might have the following limits and permissible values:

• A limit for each person – 10000 and 25000
• A limit for each vehicle – 20000 and 50000
• A limit for each accident – 25000, 50000, and 100000

However, only some combinations of values make sense from a business or legal perspective. For example, selecting the combination 25000/50000/25000 does not make sense. This combination sets the limit for each vehicle to a higher value than the limit for each accident. If permitted, this combination would result in ineffective coverage if two vehicles are involved in a single accident.

To simplify selecting a valid and meaningful combination of coverage terms, PolicyCenter displays the limit combinations in a single list. In this list, each value is actually a set of the permissible values. For example, an automobile liability package might have the following coverages:

• Each claimant Bodily Injury
• Each accident Bodily Injury
• Each accident Property Damage

The permissible values for these coverages then appear as the following package limits:

• 10000/20000/50000
• 10000/20000/100000
• 25000/50000/100000

You can assign Package coverage terms to, and compare them with, string literals that are the PackageCode objects of the coverage term packages from their patterns. For example:

BOPLine.NewCov.PackageTerm = "10/50/100" //Assign the value with the code "10/50/100" 
BOPLine.NewCov.PackageTerm == "10/50/100" //true
BOPLine.NewCov.PackageTerm == "20/60/200" //false

Typekey coverage term type

For Typekey coverage term types, you select a value from a list of choices known as a typelist. Optionally, the list of choices can be filtered through the use of a typefilter. For information on typelists and typefilters, see Working with typelists in Studio.

Generic coverage term type

You define Generic coverage term types as custom values which must be a string, date and time, or Boolean value. A date and time value is formatted as yyyy-MM-dd HH:mm:ss.SSS. You cannot customize the Generic coverage term.

Although you can use generic coverage terms for numeric values, Guidewire recommends that you use direct coverage terms instead.