Вы находитесь на странице: 1из 4

Data Model in GW

The Data Model in GW is the set of data object and information and their
relationships. Consists of entities and field, TypeList and typekeys. This data model
contains field validation and abstract data types.
In Gw data is saved in a one big table. ITs similar like inheritance in Java. All
entities are accessed with super class object with Dot operator.
1) Field validation, ITs field validator defines the format requirements for
specific field like postal code is not more than 5 characters it should contains only 0
to 9 numbers
2) Abstract data type, IT defines a datatype that is built on sample data type
and is used to ensure the consistent definition of similar fields like an Exchange
Rate data type could be defined as a decimal with a precision of 7 and a scale of 6.
Then, any field that is intended to store exchange rate value could use the abstract
data type, thereby ensuring that all exchange rate fields in the data model have
been declared in the same way.
In Guide wire data is categorized into 3 parts.
1) Entities
2) Entity Fields
3) TypeList
1) Entities It's nothing but a table. ITs abstract definition is group of
business objects used in an application. Business objects can be primitive data type
fields or sub group object or typekeys.
For an example. ABContact is the Entity It has Name, create time fields are
primitive data
types. Assigned user is subgroup object which is belongs to User group object.

An entity stores data in a database table, For an example ABContact data

saves in ab_abcontact. There is only 2 cases we dont save data in db
a) Entities that share the columns in an entity table such as subtype entity.
b) Virtual it's not persistent entities, these entities do not save data to the
database. These are
run time fields and when application is shuts down, this data is not going to save
that data in DB. These are derived from database fields for an example Entity has
First Name, Middle Name, Last Name, Full Name. Full name can be derived from
First, Middle and Last Names. We dont required to save in DB
FullName = FirstName+MiddleName+LastName.
Entity Field is Nothing but a column in a table. IT can be a value or foreign
key, reference key
1) TypeList is list of data is common to all users. ITs also like sub group. ITs
predefined Subgroup. Difference between TypeList and Entity Field is. TypeList can
be unique to all users. IT kind of predefined data which can be used to all.
For an Example: 1) in a UI page contains Male or Female dropdown. ITs
common to all user types. ITs common to all users. All subtypes stored in one
typelist. Subgroup is nothing but another table with PK and FK relation. Fields of
supertype entities are inherited by subtype entities.

In above diagram ABAttorney inherits from ABContact. So ABAttorney will

have its own properties and inherits properties. Some top level supertype entities
are abstract. Not possible to create an entity instance of an abstract entity.
Instantiated, but they can ABContact is a top level supertype entity. The ABContact
entity is an abstract entity (abstract=true). Abstract entities cannot be supertype. In
other words, this means that you cannot create instance of an ABContact, but you
can create entity instance of its subtypes such as instance of ABPerson, ABCompany
and its subtypes. (In Java subclass object can be referred by super class reference)
Not all top supertype entities are abstract. It is also possible to have subtype
entities that are abstract.
Subtype entity data Supertype parent table stores all instance of itself and
Subtype data. It contains parent fields and all subtype fields. Irrelevant fields are
null for specific subtypes. Subtype column identifies subtypes.
Subtype Entity, Subtype entity are stored in root entity. We cant create
object for subtype.
Subtype entity can access superclass fields. This below screenshot is belong to
ABcontact Subtype is a foreign key to a second table that stores subtype codes and
names. Columns with are irrelevant to given subtypes have null values.

This above screenshot shows rows from ab_abcontact table, which is the
table stores all instance of ABContact and its subtypes. 1 to 5 rows are longs to
ABPerson subtype. Row 74 to 46 are belongs to ABAutoRepairShop subtype.
Whenever an entity is subtypes, a typelist automatically created for it. This
typelist contains one typecode for every subtype of the parent entity. Typelist tables
are prefixed woth xxtl_, where xx is application code.

Entity fields
Data field
Foreign Key
Array key
Typekey fields and Typelists
The Data Dictionary Contains three kinds of data entity views. Full, Database
Entities link is full
Database view
Migration View

What is delegate



Please post your email for info

for guidewire Documents and
interview questions answers.

Will give access to my drive for

PC, CC and BC documents.