New and changed in PolicyCenter 10.1.1

Advanced Product Designer

See the Advanced Product Designer Guide for more information.

Editions

New in this release, editions define the product model properties on a product line. You can use editions to introduce changes to product model properties after a product has gone into production. These changes can be deployed without restarting PolicyCenter.

Conditions on clauses in Advanced Product Designer

For clauses and clause terms, you can now specify conditions that refer to other clauses.

New flag for products created using Advanced Product Designer

In this release, the following files in generated products now include a new apdManaged flag:

product.xml in configuration/config/resources/productmodel/products
product_line.xml in configuration/config/resources/productmodel/policylinepatterns

This flag is set to true for products created using Advanced Product Designer. When true, the product appears in the APD Managed tab on the Product Management screen.

The apdManaged flag is an XML attribute. When you regenerate an APD product, the attribute is added to product.xml and product_line.xml and is set to true.

The apdManaged attribute does not appear in existing products that were created without using Advanced Product Designer. Those products appear in the Externally Managed tab.

REST API Client

As of this release, the REST API Client is generally available. The InsuranceSuite REST API Client provides functionality that Guidewire applications and integrations use to make outbound HTTP calls to internal or third-party OpenAPI Spec-compliant REST services.

See the REST API Client Guide for more information.

Configuration parameter changes

For descriptions of configuration parameters, see the Configuration Guide.

Added configuration parameters

The following configuration parameters have been added:

AbsoluteMaxSessionLength
EnableAbsoluteMaxSessionLength
EnableChargeBreakdownCommissionable
EnableCreditCardCollectionUI
SingleSignOnAuthenticationEnabled

Changed configuration parameters

The following configuration parameters have been changed.

Parameter	Description of change
SerializationWhitelistEnabled	Default changed from `false` to `true`.

Maximum session length configuration parameters

Two new configuration parameters are available:

EnableAbsoluteMaxSessionLength
AbsoluteMaxSessionLength

These parameters allow you to enable session timeout for any sessions longer than a maximum number of minutes. This feature is disabled by default.

If the value of the EnableAbsoluteMaxSessionLength parameter is true, then the server immediately invalidates any session with a creation timestamp of more than the value of the AbsoluteMaxSessionLength parameter (in minutes before the current time.) Any session that passes this threshold with in-progress, unsaved work loses that work. The default value of EnableAbsoluteMaxSessionLength is false.

Inbound payments feature

PolicyCenter now includes a demonstration-only feature to simulate how a credit card payment can be accepted for a policy submission. This feature demonstrates the use of InsuranceSuite integration extensions for inbound payments. The integration framework utilizes a simulated payment gateway to process collecting a PCI-compliant collection of a tokenized credit card for future use.

A reference HTML page is provided to simulate collecting a credit card to the PolicyCenter user. The page uses a JavaScript library to send the credit card information directly to the payment gateway and retrieves the payment token. Another JavaScript library, the GWEmbedded InsuranceSuite library, is used for communicating with PolicyCenter. This library enables PolicyCenter and its PCF files to communicate with an HTML iframe hosted on the application server. For more details on this new feature, see the PolicyCenter Integration Guide.

Partially commissionable charges for itemized billing in integration with a billing system

A billing system might need to pay commission to an agent on only a portion of a charge amount, such as the portion of the charge that is premium and not the portion that is tax. PolicyCenter supports charge breakdown to itemize the components that make up a single charge.

You can now specify that charges are partially commissionable.

To enable charge breakdown for itemized billing in PolicyCenter, set the configuration parameter EnableChargeBreakdowns to true.

To specify that the billing system supports partially commissionable charges, in PolicyCenter, set the configuration parameter EnableChargeBreakdownCommissionable to true.

To integrate PolicyCenter with BillingCenter, set the value of EnableChargeBreakdownCommissionable as follows:

To keep the default behavior, which is to not send commissionable information, set EnableChargeBreakdownCommissionable to false.
To send commissionable information to BillingCenter release 2020.11, set EnableChargeBreakdownCommissionable to true.
For BillingCenter release 2020.05, BillingCenter release 10.1.0, or previous releases of BillingCenter, set EnableChargeBreakdownCommissionable to false because these releases of BillingCenter do not support commissionable information in charge breakdowns.

Amazon S3 supported in production for archiving

With this release, Guidewire PolicyCenter supports the use of Amazon S3 (Amazon Simple Storage Service) for archiving in production environments, as well as development and testing environments.

Studio uses IDEA_HOME environment variable for standalone IntelliJ IDEA

To configure Guidewire Studio to run with your own installation of IntelliJ IDEA, set the IDEA_HOME environment variable to the location of the IntelliJ IDEA installation. The use of the studio.ultimate file is deprecated. See the Configuration Guide.

Note: If you have an existing standalone IntelliJ IDEA installation, then the IDEA_HOME environment variable is likely to be already set. If so, when you run Studio, it automatically attempts to run the IntelliJ IDEA that is installed at that location. If that is not a compatible version of IntelliJ IDEA, then Studio reports an error. To have Studio run the bundled IntelliJ IDEA instead, unset IDEA_HOME.

Plugin implementations of the base URL builder interface

PolicyCenter now provides the following two implementations of the base URL builder interface in the gw.plugin.baseurlbuilder package, as well as the default implementation. You can use either of these implementations as is. Alternatively, copy one of these classes and modify the code to suit your business needs.

FixedBaseURLBuilder: This implementation is the same as the implementation in the base configuration but supports forcing the base URL to a value that you provide. To avoid cross-site scripting (XSS) vulnerabilities, any client-modifiable data values, including those in the HTTP Host header, are ignored.
ForwardAwareBaseURLBuilder: This implementation parses HTTP Host, Forwarded and X-Forwarded-* headers to determine proxy information for the base URL.
Note: Be aware that these headers are vulnerable to malicious client-side XSS attacks. You must use this plugin only in deployments where these security risks are accepted or mitigated.

For more information on the base URL builder and these implementations, see the Integration Guide.

Apache Solr updated to Solr 8.5.2

Guidewire updated the version of the Apache Solr free-text search engine to Solr 8.5.2.

Database support

Guidewire added support for the following database configuration:

SQL Server 2019