What's new in PolicyCenter for Olos
Here are the Olos release highlights for PolicyCenter. For more details, see the PolicyCenter section of the InsuranceSuite Release Notes.
Splittable entities
A splittable entity enables flexible, accurate handling of policy changes by allowing entities to be divided into independently managed segments over the policy lifecycle. These segments are called splits.
A splittable entity refers to a data model object such as a risk or exposure that can be divided into multiple segments or "splits" based on changes in policy terms, such as effective dates, locations, or other relevant criteria. Splitting allows you to manage, rate, and apply rules to each segment independently, reflecting changes in risk or policy structure over time.
Key characteristics of a splittable entity include:- An entity can be split as of a specific effective date, creating separate slices for different periods or conditions within the policy term.
- When an entity is split, certain fields can have different values in each split, allowing for accurate rating and rule application for each period.
- Splitting is commonly used for exposures or risks that are basis scalable, for example payroll or sales amounts that change mid-term, or risks that need to be tracked separately due to changes in coverage or location.
- Values such as basis amounts are prorated for each split, ensuring that calculations and coverages are accurate for the split's timeframe.
For example, consider a case where a policy covers a building and there is a change in occupancy or a new location is added mid-term. The building risk entity can be split at the change date. Each split represents the risk for a specific period, with its own set of attributes and coverages.
For more information, see "Splittables entities" in the Creating Products with APD App documentation.
Bulk export and bulk import of large schedules
Bulk export and bulk import of large schedules are supported for APD-managed products with the following limitations:
- Subtypes: Abstract subtypes are excluded because APD products do not support subtypes.
- Unsupported Field Types: Fields of type Date-Time, Involved Party, and Other are not supported.
- PolicyLocation Fields: For risk fields of type Location,
flow.xmlgenerates field names fromPolicyLocationas hardcoded values (AddressLine1,City,State, and so on) under config/resources/exportimport. If you have customized field names forPolicyLocation, you must adjust the mappings manually inflow.xml.
New Autopilot templates for PolicyCenter
- Non-Payment Autopilot Template for Policy Cancellation: This template simplifies the non-payment process and fully automates the non-payment cancellation workflow across PolicyCenter and BillingCenter. It eliminates manual handoffs, which reduces errors, and it ensures regulatory compliance with timely notices, policy updates, and reinstatements.
- Personal Auto Submissions Autopilot Template: This template lets you fully automate the submission process for Personal Auto lines in PolicyCenter. You can create or search for the account; create and quote the submission; and then issue the policy. This template minimizes handoffs to improve response times and increase agent and customer satisfaction.
Cloud API for PolicyCenter (version 1.14.0)
The Cloud API updates for PolicyCenter help users effectively manage policy data, optimize storage, and ensure regulatory compliance. The new endpoints allow users to delete older policy terms, reverse previous transactions, and handle various contact roles with greater ease and flexibility.
New endpoints
The following endpoints have been added to Cloud API.
Account API
- GET
/accounts/{accountId}/job-groups - GET
/accounts/{accountId}/job-groups/{jobGroupId}
Admin API
- GET
/agency-bill-plan-summaries/{agencyBillPlanSummaryId} - GET
/commission-plan-summaries/{commissionPlanSummaryId}
Job API
- POST
/jobs/{jobId}/convert-to-full-app
Product Definition API
- POST
/sync-products
Seasonal coverages date range endpoints
The Policy API now includes endpoints that you can use to manage date ranges for seasonal coverages on coverables.
Ability to filter quote graphs
You can now use the Policy API to apply filters on the quote_graph. This feature allows you to exclude data that is not relevant to quoting. For policies with large amounts of data, such as commercial auto policies, a smaller request payload improves your quote execution time.
Improvements to the entity-schema endpoints
- API requests accept the
packageIDquery parameter. - API requests that include the
If-None-Matchrequest header are faster in cases where the ETag matches the request header. - API responses include the following endpoint links under
x-gw-actions:account/v1/producer-code/producer-codesadmin/v1/agency-bill-plan-summaries/{agencyBillPlanSummaryId}admin/v1/commission-plan-summaries/{commissionPlanSummaryId}admin/v1/geographic-zones/{geographicZoneId}