Entity name types

An entity name definition is called the entity name type. Thus, most—but not all—entity names have a single type. However, it is possible for certain entities in the base application to have multiple, alternate names (types) and thus, multiple entity name definitions. Again, these can be either simple text strings, or more complicated Gosu expressions.

Studio displays each entity name type as a separate tab or code definition area at the bottom of the screen. You cannot add or delete an entity name type to the base application. You can, however, change the Gosu definition of an entity name type. Guidewire recommends, however, that you not modify an entity name type definition without a great deal of thought.

Most entity names have only the single type named Default. You can access the Default entity name from Gosu code by using the following code:

entity.DisplayName

Only internal application code (internal code that Guidewire uses to build the application) can access any of non-default entity name types. For example, some of the entity names contain an additional type or definition of ContactRoleMessage. PolicyCenter uses the ContactRoleMessage type to define the format of the entity name to use in role validation error messages. In some cases, this definition is merely the same as the default definition.

Note: It is not possible for you to either add or delete an entity name type from the base application configuration. You can, however, modify the definition—the Gosu code—for all defined types. You can directly access only the default type from Gosu code.