Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Inheriting from PegaIns-Data-Structure

Updated on May 17, 2021

The PegaIns-Data- class structure is set up to inherit from the Piif class structure (IAA) to provide access to the many properties provided in the Piif layer. The sub classes under PegaIns-Data- point to a Piif class to get maximum reusability.

The Piif class and its children provide the foundation data structures of the application. It contains over 550 classes, and over 2,000 properties that can be used to represent the data aspects of insurance products, agreements, and life-cycle processing.

The structure is based on the Interface Design Model of the IBM IAA version 2006TR with one exception: the application also leverages the extensive party classes and associated rules of Pega Platform. The Pega Platform party classes are organized into subclasses, with each new class directly inheriting from their Piif equivalent. This provides direct access to both Pega Platform and Piif party properties.

As you customize the application to meet the needs of your own environment, you can leverage the Piif class by having your data classes directly inherit from the corresponding Piif class and then making customizations as necessary to meet your business needs.

The structure can also inherit from the PegaIns-Data-PolCmp classes. These classes provide many of the common elements required to create products and their associated policies.

They typically aggregate multiple Piif classes to provide more generic objects than using Piif alone.

The PegaIns-Data- class structure provides these data classes.

Data representingClass
PegaIns-Data-InsurancePolicyRepresents a general insurance policy. It is specialized by its subclasses that represent lines of business (LOB) and product groups, similar to the class structure in PegaIns- PAB-Work-.

Contains several subclasses that represents components in a product. These classes are used when defining product and component rules in the Product Builder for Insurance application. Subclasses defined here inherit from the Piif class structure to take advantage of the many insurance properties provided by IAA – IBM’s Insurance Application Architecture.

PegaIns-Data-PartyContains classes that define parties.
PegaIns-Data-SubmissionRepresents a general submission data work object. It is specialized for various LOBs’ specific submission data.
PegaIns-Data-ApplicationRepresents a general application data work object specialized by its LOB.
PegaIns-Data-QuoteRepresents the estimated premium amount for an applicant based on several factors including the type of insurance, coverage amount, length of coverage, age, gender, health, and medical history, family history, build, and approximate rating class. Then, the selected quote is proposed for policy issuance.
PegaIns-Data-CustomerRepresents the customer information, either individual or business. Captures information such as address, communication options, and personal information.
PegaIns-Data-PriorCarrierCaptures the previous carrier insurer information such as policy number and the effective and expiry dates.
PegaIns-Data-PriorClaimCaptures the previous claims filed with carriers.
PegaIns-Data-VehicleInfoCaptures vehicle information such as make, model, annual mileage, and vehicle use.
PegaIns-Data-AgencyLOBContains the list of LOBs that an agency is licensed to sell in a given jurisdiction.

All the data classes that appear under the Data Explorer are defined in the Cases & data tab of the PegaInsurance Application rule. You can add or delete the data types based on the application or the built-on-application relevance and requirement. This also provides a snapshot of all the data types currently used in the application.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us