What's new in PolicyCenter for Qusar

Here are the Qusar release highlights for PolicyCenter. For more details, see the PolicyCenter section of the InsuranceSuite Release Notes.

Advanced Product Designer updates

Generate line-level fields on a dedicated secondary entity

APD can generate line-level fields on a dedicated secondary entity linked to the main policy line through a one-to-one relationship, instead of placing every new field directly on the shared PolicyLine table. This capability prevents products from hitting the PostgreSQL 1664-column-per-table limit as they add more line-level fields. Enabled with the configuration parameter APDEnableLineEntitySplit (off by default), the split is fully transparent — Gosu access, APD rule evaluation, policy diffs, change events, and manual pricing all continue to work as before.

As APD products grow, line-level fields accumulate on the shared PolicyLine table. Because all policy lines share that table, products can approach the PostgreSQL hard limit of 1664 columns per table. When this occurs, no further line-level fields can be added. Enabling the line entity split routes newly added line fields to a separate {LineName}Ext entity, freeing column capacity on the main table and allowing products to continue adding line-level fields safely.

The split is transparent. When enabled:
  • Fields routed to the secondary entity remain fully usable from Gosu as if they still lived on the main line — APD generates shorthand accessors on the main line type, so existing read/write patterns continue to work.
  • APD rules that reference these fields evaluate correctly, regardless of whether an attribute lives on the main line or the secondary entity.
  • Writes to routed fields participate in policy diffs, change events, out-of-sequence (OOSE) detection, and bean versioning exactly as before.
  • Routed numeric fields remain available as manual-pricing basis sources.
  • REST product-definition and entity-schema responses for routed fields keep their expected shape, including field labels, precision/scale metadata, and app-event behavior.
Set the APDEnableLineEntitySplit configuration parameter to true. Optional per-product annotation overrides are available to customize the generated naming:
  • lineSecondaryEntityName — override the secondary entity name (default: {MainEntity}Ext).
  • lineSecondaryEntityFKName — override the one-to-one link property name on the main entity.

The feature is off by default; existing products are unaffected until you opt in. Enable it for products that are approaching, or expected to approach, the per-table column limit on PolicyLine.

Renewal Insights Dashboard

PolicyCenter includes a Renewal Insights Dashboard (available through Guidewire Explore) that provides insurers with real-time visibility into policy renewals. The Renewal Insights Dashboard gives underwriters and supervisors the ability to view consolidated renewal metrics across all lines of business over specific time periods. Insurers can use the information from the Renewal Insights Dashboard to identify pending renewals and to manage the renewal workload across multiple roles.

The Renewal Insights Dashboard offers near real-time visibility into policy renewals by providing metrics such as open renewal job counts by expiration date, status, and line of business. It also tracks the workload for each underwriter, identifies reasons for non-taken renewals, and monitors renewal retention over time.

The Renewal Insights Dashboard itself is completely configurable and can be accessed from the PolicyCenter desktop or from the Team tab.

For a short demo of what's available in the Renewal Insights Dashboard, watch this video:

Rebind transaction for bound submissions

PolicyCenter includes support for a rebind transaction that allows multiple binding actions on a bound policy submission before it is issued. The rebind transaction allows an agent to make updates to a bound policy submission without having to cancel or rewrite it. With this feature, you can move from bind to issuance faster by updating dates, coverages, and producers in one transaction. You can also negotiate faster with brokers by updating limits, terms, and endorsements without restarting the policy process.

You must enable the rebind transaction feature for it to become available in PolicyCenter. It is also governed by specific user permissions and is restricted to certain modifications on bound policy submissions.

For a short demo of the rebind transaction, watch this video:

Improved bind to issuance billing instructions

Issuance billing instructions were enhanced so that they use the same full offset/onset model as Rebind, instead of only sending deltas if needed. Specifically, PolicyCenter can now send clearer Final Issuance billing instructions to BillingCenter with a per-charge offset flag, allowing BillingCenter to offset prior charges, onset the new full premium, and refactor the invoice schedule while still supporting legacy delta-only integrations.

Search and bulk update for coverable entities

PolicyCenter includes support for a generic search and bulk update capability that improves large schedule management and can be extended to any non-splittable coverable entity (for example Buildings, Locations, Vehicles). These features are built directly into APD codegen.

All entity attributes are now available as search parameters in the base configuration search feature on the coverable screen. Guidewire recommends that customers modify this list based on their own requirements.

The search results are contained in a filtered list view. You can select, add, and remove items across multiple pages of search results, and then make bulk updates to your selected items in a single PolicyCenter transaction. The selections are persistent, which means they are not lost when you navigate away from the search results view.

ProNavigator for PolicyCenter changes

ProNavigator includes an interactive assistant and embedded agents that provide support within the PolicyCenter user interface and workflows that insurers are accustomed to. This release includes the following updates.

ProNavigator assistant suggestions

In this release, the Suggestions tab of the ProNavigator assistant provides questions that you might want to ask when the screen context is a Policy.

Policy servicing agent (Early Access)

The policy servicing agent can:
  • Reduce handling time by automating complex-multi-step servicing workflows.
  • Improve accuracy and compliance by validating requested changes against rules and the product model.
  • Maintain human oversight of agent-drafted change jobs for review and binding.
You can use it to complete the following tasks:
  • Initiate policy changes.
  • Add, modify, or remove coverables and coverages from a policy.
  • Ask questions to determine how your policy premium would change in different scenarios.
  • Withdraw an unwanted policy transaction.

See ProNavigator Integration documentation.

Quoting Service integrated with external rater (Restricted Availability)

Quoting Service supports synchronous and asynchronous quoting with an external rater. Asynchronous quoting with an external rater lets users work on other screens while the quote runs in the background.

For a short demo, watch this video:

High Volume Quoting with Quoting Service (Early Access)

High Volume Quoting (HVQ) with Quoting Service in PolicyCenter speeds quote processing and supports multiple quoting patterns.

You can use HVQ with Quoting Service to:

  • View real-time quote request and response data from the Quoting Service, and subscribe to these events with App Events.
  • Compare the initial quote cost with the cost calculated before issuing the quote.
  • Access quote data in Datadog dashboards.
  • Configure a single quote request to generate multiple quote offerings.
  • Transform (bump or slot) coverage limits and deductibles from the quote request to values that are available in the policy.
  • Rate quotes and apply rules in either PolicyCenter or a customer-managed external rater.

HVQ with Quoting Service also:

  • Accelerates quote response times with payload compression.
  • Asynchronously saves quote payload (JSON format) to the Quote Storage Service (QSS).
  • Provides an Integration Gateway quoting library with tools to configure the aggregator to submit high volume quotes to the Quoting Service.

For more information, see Application Guide.

Cloud API for PolicyCenter (version 1.16.0)

New endpoints

Policy API

  • POST /policies/{policyId}/rebind
High Volume Quoting (HVQ) with Quoting Service endpoint

The API supports the ability to generate HVQ quotes and store the quote payload in the Quote Storage Service (QSS) instead of the PolicyCenter system of record (SOR).

Rebind endpoint

The API supports the ability to re-bind a policy.

Support for FEEL expressions in APD Rules

The /entity-schemas endpoint now supports FEEL expressions in APD rules for installed and visualized products. Also, you can now exclude specific APD Edition rules from responses. The Cloud API also benefits from the following run-time improvements for FEEL expressions:
  • Numeric, arithmetic, and conversion functions have null-safe variants.
  • Decimal-to-null comparisons translate correctly to JsonLogic.
  • The additionalSymbols entry includes an explicit type field.