Integration Data Manager
Integration Data Manager is a JSON document storage service for integration developers. Integration Data Manager makes it easy to store third-party data for use with InsuranceSuite, and allows you to view this data or use it in business logic without having to change the InsuranceSuite data model. This process simplifies the InsuranceSuite configuration and makes it easier to perform upgrades.
GET
/pools/{poolId}/documents
endpoint is disabled. You must use the
getDocument
endpoint, instead.The need for Integration Data Manager
It is common to enrich InsuranceSuite data with data from third-party systems. For example:
- Information about a policyholder might be supplemented by a credit report from a credit agency.
- Vehicle data might be enriched with external data about the vehicle's driver, prior accidents, and prior insurance policies.
- Information about a building might be enriched by a risk assessment that indicates natural hazards or the distance from a fire station. In both of these cases, an integration enriches a small amount of information from InsuranceSuite with data retrieved from a third-party system.
This information must be stored before it can be shown to the user. However, extending the InsuranceSuite data model for external data has disadvantages:
- It complicates the core data model with non-system of record data.
- Data model changes and associated Gosu code can complicate upgrades.
- It interleaves data managed by InsuranceSuite with data managed by a third-party system, which complicates data governance.
The Integration Data Manager approach
Integration Data Manager stores the third party data outside the InsuranceSuite data model. This helps maintain a separation between InsuranceSuite system-of-record data (which is managed by InsuranceSuite), and non system-of-record data (which is managed by an external system).
Integration Data Manager enables a streamlined user experience for accessing data without the need to log into multiple systems or dynamically retrieve it from external systems. This approach simplifies the core system configuration, which then simplifies platform updates and improves data governance.
Integration Data Manager is well suited for storing data from an external system that enriches claims, policies, buildings, and people. Use cases include fraud scoring reports, credit score reports, building risk reports, police reports, credit reports, pre-filled data, and car rental information.
Features:
- Create data pools for different use cases. Each pool has its own JSON schema and retention policy.
- Grant Integration Gateway apps access to individual pools.
- Pool and schema-level configuration lifecycle is managed by Guidewire Lifecycle Management.
- Share documents across Integration Gateway apps within the same project with appropriate permissions. Documents are partitioned by tenant, project, and environment, while pool and schema information is accessible across environments within the same tenant and project.
- Documents are protected against updates (read-only), since Integration Data Manager is not the system of record. Data can be written, read and deleted, but it cannot be edited.
- Specify a retention period for documents within a pool.
- Integration Data Manager clients are provided for InsuranceSuite and for Integration Gateway.
- Integration Gateway access to pools is managed through an administration user interface.
- Use Integration Data Manager in conjunction with the Assessment API to associate assessment documents in Integration Data Manager with core InsuranceSuite entities.
Comparing Integration Data Manager with other data storage methods
Integration Data Manager | Integration Gateway Key Value Store | InsuranceSuite | |
---|---|---|---|
Usage | Access data from third-party systems outside of InsuranceSuite | Store short-term transient data for integrations. | Store of system of record claim, policy, and billing data. |
Goal | Simplify InsuranceSuite configuration, data governance, and development operations. | Short-term store of data for integration purposes. | Store of system of record claim, policy, and billing data. |
Example uses |
|
Accumulating items for a batch integration. | |
Data retention | Retention period can vary from hours to days. Retention period is configured for each data pool (a pool is used to store data of a specific type). | Maximum of ninety days. | No control over third-party retention. Data is retained indefinitely until claim is purged or archived. |
Integration Gateway app data access | Each Integration Gateway app needs to be granted access to a particular pool. | Any Integration Gateway app can access data in the key value store for the tenant. | |
Maximum object size that can be stored | Maximum 400Kb. | ||
Schema management | Supported. Schemas are defined for each pool. Use schemas to enforce the quality of the stored data. Schemas can also be accessed from different Guidewire services. | Not supported. | Not available. |
Document retrieval | Documents are retrieved by document ID. | Documents are retrieved by document ID. | |
Querying by attribute | Not supported | Key value store allows a single attribute to be set when writing the document. Key value store can be queried to find documents matching that attribute. | |
Claim and policy association | When an Integration Data Manager document is stored it can be associated with a claim or policy entity using the ClaimCenter or PolicyCenter assessment APIs. Subsequently, all Integration Data Manager documents associated with a claim or policy entity can be found. | Documents are retrieved by document ID. | Not available. |