Integration graphs

An integration graph is a special base configuration schema and mapper that certain base configuration outbound integrations use to send information about a parent object and its children objects. Integration graphs are not used by Cloud API, but the files that define them are a part of Cloud API.

As of this release, Cloud API has the following integration graphs:

  • The ClaimCenter claim_graph, whose parent is Claim
  • The PolicyCenter policyperiod_graph, whose parent is PolicyPeriod
  • The PolicyCenter quote_graph, whose parent is Quote
  • The ContactManager contact_graph, whose parent is Contact

There are several outbound integrations that make use of integration graphs. For example, integration graphs reflect the structure of the event payload that App Events generates for downstream systems.

Guidewire recommends against insurers configuring integration graphs directly. However, if you create an extension entity that is a descendent of one of the parent entities listed above, you can add that entity to the appropriate integration graph. This is done through the REST endpoint generator. For more information, see Integration graphs.

Warning: Guidewire recommends against insurers using the integration graph schema/mapping files for custom outbound integration points. This is because, if not used properly, the integration point could attempt to generate a payload so large that it compromises server performance or prevents the server from running.

Apply filters to the quote_graph

PolicyCenter includes quote_graphs in the quote requests it sends to Quote Orchestrator. You can apply filters on the quote_graph to exclude data that is not relevant to quoting. For policies that typically have large payloads, such as a commercial auto policy, a smaller request payload can improve quote response time.

For more information on the Quote Orchestrator and Quoting Services, see the Application Guide.

You can define filters for quote_graphs that apply to all lines of business or to a specific line of business.
Filters for all lines of business
Update the following filter configuration file to define filters that can apply to all lines of business: pc/app-pc/pc-content/config/integration/api/filters/integration_graph_filter_config.all.yaml
Filters for a specific line of business
Create and update the following filter configuration file to define filters for a line of business: pc/app-pc/pc-lob-<lob_prefix>/config/integration/api/filters/integration_graph_filter_config.<lob_prefix>.yaml

Filter configuration parameters

When defining filters, ensure that the information required to quote each product remains in the quote_graph and that you only filter information that is not relevant to quoting.

In each quote_graph filter configuration file, you can configure the following properties:
Property Description
productCode In integration_graph_filter_config.​all.​yaml file, set this parameter to All. When you configure a integration_graph_filter_config.<lob_prefix>.​yaml file, set this parameter to the product code identifier, for example PersonalAuto.
includePaths Defines fully qualified schema property paths to include in the quote_graph. You can use wildcards(*) to specify the path.
excludePaths Defines fully qualified schema property paths to be excluded from the quote_graph. You can use wildcards(*) to specify the path. This parameter takes precedence over the includedPaths.
excludeSchemaProperties Defines common schema properties specified as <definition>.​<property> to exclude from the quote_graph. This parameter takes precedence over the includedPaths.
Note: When you use wildcard(*) in the includedPath, parent objects in the specified path display as an empty object when their child objects are not part of the filtered quote_graph. If you enter a wildcard(*) in a includedPath or excludedPath without a path, this configuration is ignored.
Review the following examples:
Using includePaths
This configuration example includes the entire account node and question fields associated with the current period in the quote_graph.
productCode: PersonalAuto
includePaths:
 - Quote.account
 - Quote.currentPeriod.slices.answers.*.questions
...
Using includePaths and excludePaths
This configuration example includes questions and all of its properties except for the id property. It also includes all coverages and modifiers.
productCode: PersonalAuto
includePaths:
 - Quote.currentPeriod.slices.answers.*.questions
 - Quote.*.slices.lines.PALine.*.coverages
 - Quote.*.slices.lines.PALine.*.modifiers
excludePaths:
 - Quote.currentPeriod.slices.answers.*.questions.id
...
Using includedPaths and excludeSchema
This configuration example includes jobType and all its child objects and properties except for the name property. It also includes coverages and all its child objects and properties except for the clauseType property.
ProductCode: PersonalAuto
includePaths:
 - Quote.currentPeriod.jobType 
 - Quote.*.slices.lines.PALine.*.coverages
excludeSchemaProperties:
 - TypeKeyReference.name
 - Coverage.clauseType
...

How PolicyCenter evaluates quote_graph filters

PolicyCenter evaluates the graph filter configuration files as follows:
  1. Selects a filter configuration file.
    • If pc/app-pc/pc-lob-<lob_prefix>/config/integration/api/filters/integration_graph_filter_config.<lob_prefix>.yaml is available for the line of business (lob), this file is selected.
    • Otherwise, pc/app-pc/pc-content/config/integration/api/filters/integration_graph_filter_config.all.yaml is selected.
  2. Applies the filters specified in the selected file.
    Note: The excludedPaths and excludedSchemaProperties settings take precedence over the includedPaths.For example, if you specify the same path in both excludedPaths and includedPaths, or if you specify the parent node path in excludedPaths but the child node path in includedPaths, the paths will be excluded from the output