Entities in the archive domain graph
For PolicyCenter to consider an entity as part of the archive domain graph, that entity must implement one or more delegates. A delegate adds an interface and a default implementation of that interface to entity types that implement the delegate. Some delegates also add columns that the delegate implementation manages. The archiving delegates help define the extent of the archive domain graph and are necessary for successful operation of the archive process.
In addition, any new entity that you want to add to the archive domain graph must have an ownership relationship with another entity already in the graph. You can establish ownership in one of the following ways:
- By defining a foreign key in the new entity to another entity already in the graph.
- By defining a foreign key to the new entity from an entity already in the graph and
setting the attribute
archivingOwner="source".
The following table summarizes the entity types that exist in the archive domain graph.
|
Entity type |
Delegate Implementation |
More information |
|---|---|---|
|
Graph root entity |
The root of archive domain graph must implement the
|
|
|
|
Entities in the PolicyCenter archive domain graph implement the
|
|
|
Overlap table entities |
Overlap tables are tables in which individual table rows can exist
either in the archive domain graph or as part of reference data, but
not both. The database table itself exists in the archive domain
graph and as reference data. All overlap table entities, and only
overlap table entities, must implement the
In PolicyCenter, only The primary use for these types of entities is for Guidewire code. The use of overlap tables by non-Guidewire code is not common. |
