Different kinds of typelists

PolicyCenter organizes typelists into the following categories:

Category	Description	More information
Internal	Typelists that Guidewire controls because PolicyCenter requires these typelists for proper application operation. PolicyCenter depends on these lists for internal application logic. Guidewire designates internal typelists as final (meaning non-extendable). Thus, Guidewire limits what you can modify for these typelists. You can override the following attribute values on these types of typelists: `name` `description` `priority` `retired`	Internal typelists
Extendable	Typelists that you can customize. These typelists come with a set of example typecodes, but it is possible to modify these typecodes and to add your own typecodes. In some cases, these extendable typelists have internal typecode values that must exist for PolicyCenter to function properly. You cannot remove the internal typecodes, but you can modify any of the example typecodes. PolicyCenter designates internal typecodes by placing their `code` values in gray, non-editable cells. This makes these values inaccessible, and thus, impossible to modify.	Extendable typelists
Custom	Typelists that you add for specific purposes, such as working with a new custom field. These typelists are not part of the Guidewire base configuration. Guidewire Studio™ automatically makes all custom typelists non-final (meaning extendable).	Custom typelists

Internal typelists

A few of the typelists in the application are internal. Guidewire controls these typelists because PolicyCenter needs to know the list of acceptable values in advance to support application logic. Guidewire makes these typelists final by setting the final attribute to true in the data model. For example, ActivityType is an internal typelist because PolicyCenter implements specific behavior for known activity types.

Guidewire Studio™ disables your ability to add additional typecodes to internal typelists.

The following are examples of internal typelists that you cannot change:

ActivityStatus
ArrangementType
BindOption
BOPCost

Overriding attributes on internal typelists

While you cannot change an internal typelist, you can override the following attributes on the typecodes of an internal typelist:

name
description
priority
retired

Studio does not permit you to add additional items (typecodes) to an internal typelist. However, you can create a filter for the typelist.

To override a modifiable typelist attribute, first open the typelist in Guidewire Studio by selecting it under configuration > config > Extensions > Typelist. Then, select the typecode cell that applies and enter the data. You cannot change the typecode itself. You can change only the attributes associated with the typecode.

Extendable typelists

Many of the existing typelists are under your control. You cannot delete them or make them empty, but you can adjust the values (typecodes) within the list to meet your needs. PolicyCenter includes default typelists with sample typecodes in them. You can customize these typelists for your business needs by adding additional typecodes, if you want.

The ActivityCategory typelist is an example of an extendable typelist. If you want, you can add additional typecodes other than the sample values that Guidewire provides in the base configuration.

Custom typelists

If you add a new field to the application, then it is possible that you also need to add an associated typelist. You can only access these typelists through new extension fields. For more information on how to add a new field to the data model, see Extending a base configuration entity.

To create a custom typelist, in the Project tools window, navigate to configuration > config > Extensions > Typelist. Right-click on Typelist, and then click New > Typelist. Enter a name for the typelist, and then define your typecodes. PolicyCenter limits the number of characters in a typecode to 50 or less.