Defining a new data entity

You define all new data entity objects in declaration files that end with the .eti extension. You do this through Guidewire Studio. Studio automatically manages the process and stores the .eti file in the correct location in the application (in the configuration > config > extensions > entity folder).

Create a new entity

Procedure

In Guidewire Studio, in the Project tool window, navigate to configuration > config > Extensions > Entity.
Right-click Entity, and then click New > Entity.

In the Entity dialog, specify the entity definition values.

Data entity	More information
`<delegate>`	<delegate> elements and related data object types
`<entity>`	<entity> elements and related data object types
`<extension>`	<extension> elements and related data object types
`<nonPersistentEntity>`	<nonPersistentEntity> elements and related data object types
`<subtype>`	<subtype> elements and related data object types
`<viewEntity>`	<viewEntity> elements and related data object types
`<viewEntityExtension>`	<viewEntityExtension> elements and related data object types

Add fields to your new data entity. In the Field drop-down list, select the field type to add, and then click Add . For example:

XML tag

Use to add

<array>

An array of entities

<column>

A field with a simple data type

<foreignkey>

A field referencing another entity

<typekey>

A field with a typelist

For information on the possible XML elements that you can add to your new entity definition, see Data entity subelements.
Deploy your changes to the application server. You must redeploy the application after you make any change to the Guidewire PolicyCenter data model. See Deploying data model changes to the application server for details.

XML tag	Use to add
`<array>`	An array of entities
`<column>`	A field with a simple data type
`<foreignkey>`	A field referencing another entity
`<typekey>`	A field with a typelist

Default properties on a new entity

The following table contains the entity properties that PolicyCenter generates automatically when you create a new entity:

Property	Description
ID	Internally managed primary key
CreateTime	Timestamp indicating when the object was created. This property is only applicable for editable, effdated, effdatedbranch, effdatedcontainer, and retireable entity types.
CreateUser	User who created the object.This property is only applicable for editable, effdated, effdatedbranch, effdatedcontainer, and retireable entity types.
LoadCommandID	This property is included for entities where the loadable attribute has a value of true. However, PolicyCenter does not use this property.
New	Indicator of whether this object is a new object that has not been committed to the database.
NewlyImported	Obsolete.
PublicID	ID or primary key of the row in the external system to which this row is mapped
Retired	Derived property returning a Boolean value. The Boolean value is true if the RetiredValue property has a non-zero value. The Boolean value is false if the RetiredValue property has a zero value. The Retired property is only applicable for effdatedbranch, effdatedcontainer, and retireable entity types.
RetiredValue	Value indicating whether the object is still in active use. A zero value for the property means that the object is not retired. A non-zero value equal to the entity ID means that the object is retired from active use. Note that even if an object is retired, it can still be referred to by another object. The RetiredValue property is only applicable for effdatedbranch, effdatedcontainer, and retireable entity types.
UpdateTime	Timestamp when the object was last updated. This property is only applicable for editable, effdated, effdatedbranch, effdatedcontainer, and retireable entity types.
UpdateUser	User who last updated the object. This property is only applicable for editable, effdated, effdatedbranch, effdatedcontainer, and retireable entity types.

Note: New entities have constant properties that the PolicyCenter data dictionary lists. The table in this topic does not list these properties. Instead of using these constant properties, use feature literals to refer to the static properties of entities in queries.