PolicyCenter 10.0.2 Release Notes
Major issues and changes
This section contains issues and major changes that may affect your installation. For more information on new features and major changes, see New and Changed Guide.
Guidewire InsuranceSuite requires Java 11
Guidewire InsuranceSuite now requires Java 11. For information about supported releases, visit the Guidewire Community and search for knowledge article 1005, “Supported Software Components”.
Support for application servers on Java 11
Because Guidewire InsuranceSuite now requires Java 11, it can run only on application servers that also support Java 11. At the time of this release, WebLogic and WebSphere do not support Java 11, and therefore are not supported on this release of InsuranceSuite. For current information about supported application servers, visit the Guidewire Community and search for knowledge article 1005, “Supported Software Components”.
Release notes now contains the archive of previous release notes
This release notes document now contains the archive of previous release notes. In previous releases, the release notes archive appeared in the New and Changed Guide.
Chinese language resources are for demonstration purposes only
This release includes Chinese language resources in the base configuration. These resources are provided only for demonstration purposes, and are not supported for production use.
Generated reports on changes
The following are generated reports of changes between releases.
Guidewire also provides a report detailing certain differences between the current release and your prior release. This report describes changes in display keys, entities, typelists, and the Gosu API. To obtain your custom Upgrade Diff report, visit the Guidewire Community and search for knowledge article 7898, "How to find reports detailing differences between earlier and later releases of Guidewire core products".
Changes between releases 10.0.1 and 10.0.2
- Base resources
-
There are no changes to the base resources.
- Base PCF files
- To view a report of the changes to the base PCF files, click here.
- Base rules
- To view a report of the changes to the base rules files for ContactManager, click here.
Improvements and resolved issues
Guidewire attempts to provide information for issues of primary importance to our customers. This list is not intended to be comprehensive.
PolicyCenter improvements and resolved issues
| ID | Description |
|---|---|
| ISPC‑103 |
This fix sets the reference date correctly when submission and issuance policy
transactions (or any policy transaction where period start can be changed) have
different start dates. In |
| ISPC‑105 |
If validation fails on a step dynamically generated by a Wizard Step Iterator, you can now link the error message to that step. |
| ISPC‑115 |
Fixed an exception that occurred in Rewrite New Account with a Cancellation that resulted in an exception that usually displayed "null" in the message bar. |
| ISPC‑123 |
Fixed an issue where an extra slice was created when copying a submission. An extra
slice was created if the submission was sliced on a new effective date, no actual
edits to the policy on that date (simply calling
|
| ISPC‑124 |
Fixed an issue that caused errors with checking for differences while merging contacts. |
| ISPC‑126 |
This fix is dependent on ISPC‑124 , which makes it now possible to mark certain
arrays as owned that could not be owned previously. The following line-specific
Important: To avoid a concurrent data exception,
PolicyContactRole arrays must be owned by their respective policy
lines. Verify that these arrays are owned in lines of business that you have
developed or customized. |
| ISPC‑145 |
When a policy had a policy change with an effective date in the future, the tab bar policy search widget (Policy/Policy#) opened the policy file with the date selector correctly set to the change's effective date, but the policy was incorrectly shown as it would be on the current date rather than how it would be on the change's effective date. This issue has been fixed. |
| ISPC‑150 |
Fixed an issue where |
| ISPC‑153 |
When viewing a bound transaction, some information on the Payment screen contained values different from the values returned by the billing system. This issue has been fixed. |
| ISPC‑176 |
Fixed an issue where the Rating Worksheet displayed the public ID instead of the code identifier of the coverage parameters of a rate table look up. Fixed an issue on the Rate Table Definition screen where the Argument Source drop-down list displayed the public ID instead of code identifier of modifiers. |
| ISPC‑181 |
Fixed an issue where Solr indexing created unnecessary duplicate entries when policies were updated in the PolicyCenter user interface. |
| ISPC‑186 |
If two users were both editing the same policy, an exception could occur if they both tried to bind or issue the policy. This has now been fixed. |
| ISPC‑187 |
Fixed an issue where preempting an audit with a policy change deleted all related Solr index records for a policy. |
| ISPC‑188 |
Fixed an issue which caused "Duplicate entity skipped" messages when importing rate books from XML. |
| ISPC‑189 | Fixed a previously known issue where applying a deleted then re-added effdated bean, such as a vehicle, to a future unbound renewal caused a null pointer exception. |
| ISPC‑223 |
Fixed an issue with rate table definition cache where updates to rate tables on one node of a cluster did not propagate to other nodes of the cluster. |
| ISPC‑338 |
Fixed an account transfer when running PolicyCenter on JBoss that caused the error
|
| ISPC‑425 |
The |
| ISPC‑433 |
Added the following convenience method to the
|
| ISPC‑438 |
The |
| ISPC‑444 |
Fixed an issue which caused an exception on the Quote Store screen when selecting Convert to Submission on a quote created in a version of PolicyCenter prior to 10.0.1. |
| ISPC‑486 |
Processing |
| ISPC‑744 |
Fixed an issue where the |
| ISPC‑745 |
Fixed an issue where the free text batch load command created duplicate entries in the Solr index. |
| ISPC‑854 |
The amounts in the preview of the payment schedule was incorrect after a policy
change for a policy period with a large amount of tax when using the
|
| ISPC‑887 |
Fixed an issue introduced in PolicyCenter 10.0.1. This issue prevented high volume quotes in the Quote Store from being converted to submission. See the Upgrade Guide for information on changes you can make to PolicyCenter 10.0.1 so that it produces high volume quotes that can be upgraded. |
| ISPC‑975 | Fixed an issue introduced in Policy 10.0.1 With this fix, high volume quotes produced in this release can be upgraded. See the Upgrade Guide for information about how you can modify existing high volume quotes created in PolicyCenter 10.0.0 and 10.0.1 so that can be upgraded. |
| ISPC‑996 |
Fixed an issue where rate table caches were cleared on any change to the global cache. |
| ISPC‑1012 | Product Designer has been updated to connect to PolicyCenter using
pc1000/productmodel/ ProductModelAPI. |
| ISPC‑1065 |
Importing some rate books failed when the language was set to a language other than English. |
| ISPC‑1070 | Fixed an exception that occurred when viewing or approving underwriting issues that were missing a Short Description. |
ContactManager improvements and resolved issues
|
ID |
Description |
|---|---|
| ISCM‑85 | ZipCode and State in
ContactHistoryDV.pcf are now translated correctly according
to the user-selected language and display.properties.
Additional translation changes to address field labels can be configured in
AddressHistoryFieldUtil.gs. |
| ISCM‑84 | API methods that are deprecated in Java 11 have been replaced. |
| ISCM‑54 | Fixed an issue in the Pending Changes list where a
BadIdentifierException no longer occurs after a contact with
pending update is deleted or merged. |
| ISCM‑44 | To prevent making an obfuscated user active again, the Active radio button in the User Details screen is now unavailable when editing a user. |
| ISCM‑24 | Fixed an issue in Pending Updates where a
BadIdentifierException no longer occurs when the address on the
Contact(kept) is excluded during contact merge. |
| ISCM‑23 | Fixed an issue in Pending Updates where the "The object you are trying to update was changed by another user. Please cancel and retry your change." error message no longer appears when the address on the Contact(kept) is null during contact merge. |
Platform improvements and resolved issues
| ID | Description |
|---|---|
| ISGOSU‑45 | Fixed an issue that caused a stack trace to appear when using the debugger to examine the value of particular Gosu expressions. |
| ISGOSU‑85 | Fixed an issue that prevented the debugger in Studio evaluating a Gosu expression in a static method. |
| ISGOSU‑122 | Fixed an issue that caused a null-pointer exception if code accessed a protected member from outside the defining package. |
| ISPL‑31 | Fixed an upgrade performance issue for Oracle databases. Index creation was not using parallel DDL, even if degree-parallel-ddl was set correctly. |
| ISPL‑96 | If the same shortcut key is defined more than once on a page, the last definition takes precedence. |
| ISPL‑207 | Enhanced the Oracle AWR database report 'Estimated DB Time Aggregated by (event)' page to arrange the database event execution times in descending order. The report also filters out events with execution times of 0. |
| ISPL‑286 | The valueWidth property on certain PCF inputs been deprecated. Instead, use valueSectionWidth, valueSectionMinWidth, and valueSectionMaxWidth to control the width of the value inside input columns. |
| ISPL‑287 | Fixed an issue where the parent and child navigation arrows in a paging control would always appear, and would be disabled if not applicable. These icons now appear only if applicable. |
| ISPL‑383 | Fixed errors that would occur when modifying the default Login page and hiding the username input field (for example, to implement single sign-on). |
| ISPL‑483 | Fixed a low-level issue that caused a divide-by-zero error when making changes to entity instances that had the same date for start and end dates. |
| ISPL‑532 | Modified the on-screen comments on the Server Tools Start Rolling Upgrade screen. |
| ISPL‑549 | Added the IIntegrationConfigSourcePlugin plugin to allow for loading JSON Schema, integration mapping, integration filters, or Swagger schemas from somewhere other than the standard config directories, or even to generate their source on the fly. Also added in the ability to specify a method named defaultHandlerMethod in a REST API handler class for use as the default method to invoke if there is no method found on the API handler classes that exactly matches an operation name. |
| ISPL‑559 | Fixed an issue during deployment on Tomcat 9.0.x and JBoss 7.1.x that caused websocket listeners to be registered twice on some application servers. This eliminates the warning message and stack trace that was logged for such occurrences. |
| ISPL‑563 | Fixed a database upgrade issue that could cause a ClassCastException when restoring a claim failed. |
| ISPL‑576 | Fixed a PCF issue in Server Tools Consistency Checks screen. PolicyCenter now disables the Description field on the screen whenever the DBConsistencyCheck work queue is running. |
| ISPL‑602 | The SQL Server JDBC driver was updated to version 7.2.2. |
| ISPL‑622 | Clarified the warning message that occurs if an index is specified as filtered but the index on the database is not filtered. |
| ISPL‑625 | Added verification to file database-config.xml so that if the file contains duplicate 'tablestatistics' elements, the application server fails to start and generates an error. |
| ISPL‑626 | Fixed an issue that caused Load History Download to not show the value of the numThreadsIntegrityChecking parameter. |
| ISPL‑715 | Fixed an issue that caused casting a non-numeric string to a number type to return 0 instead of throwing an exception. |
| ISPL‑727 | Upgraded to newer version of ICU4j. This version supports the latest Japanese Imperial Era. This version also uses the latest CLDR data, so there are some visible formatting changes. Formatters are also used for parsing numbers, so you may see commensurate parsing differences. Note on H2 (development quickstart) database use: ICU4j changed the naming scheme it exposes for locale data. To specify collation in an H2 database, use a standard locale name format, for example "de_DE" for Germany,"ja_JP" for Japan. |
| ISPL‑751 | Refactored the ActivityEscalationWorkQueue writer process to use an insert-select statement using the BulkInsertStandardWorkItemQueue class. The change improves performance. |
| ISPL‑756 | Fixed an issue where confirming one client alert event could prevent a subsequent client alert from displaying. |
| ISPL‑784 | The Login page now shows errors that occur before the Login page can be accessed, such as when the authentication server is not responding. |
| ISPL‑794 | Fixed an issue in which a configuration of over 2,048 typecodes in some typelists could cause runtime errors. |
| ISPL‑886 | If a key is stuck down or being pressed continuously, the application may send too many requests to the server. You can now set gw.globals.gwApp.EVENT_THROTTLE_MAX_REQUESTS_PER_SECOND to a value greater than 0 to set the maximum allowed server requests/second. If the maximum value is exceeded, then a dialog appears with a warning and asks you to confirm that you are intentionally sending that many requests. |
| ISPL‑889 | Added a new allowGoOrPush Boolean attribute to the PCF Forward. If specified and set to true, the Forward must always be pushed until the final destination expression is executed. The final destination can then be a go, push, exit point, or workspace, and the final destination executes as if there is no intervening Forward. |
| ISPL‑1037 |
The Oracle JDBC driver was updated to version 18.3. |
| ISPL‑1071 | Some integrity check queries related to "consistent children failure within staging tables" have been rewritten to perform optimally in all supported databases. |
| ISPL‑1084 | Added entity name to SEQUENCE related SQL statements to help identify the source of performance issues. |
| ISPL‑1086 | Pressing Enter in a list view to create a new row or navigate to the next row would incorrectly select the check box at the beginning of the row. Now the next editable input receives focus instead. |
| ISPL‑1119 | Fixed an issue with the LoadHistoryInfo Report Download REST API that returned the report, not a ZIP file. The LoadHistoryInfo Report Download REST API now returns a ZIP file. |
| ISPL‑1176 | inbound integration has been updated to support OSGi Release 7. |
| ISPL‑1180 | Upgraded the Jackson library that PolicyCenter uses to include resolutions to issues in the previous version. |
| ISPL‑1209 | For SQL Server, removed 'serverid' and 'thread number' from SQL comments. |
| ISPL‑1264 | To select multiple check boxes in a list view, click on the first check box and then Shift+click on the last one. |
| ISPL‑1332 | OSGi support for plugin development has been updated to an OSGi Release 7 compliant implementation that is compatible with Java 11. |
| ISPL‑1364 | Updated Solr to release 7.7.1. For customers deploying Solr, on upgrade from a previous release, it is recommended to rerun batchload to rebuild any existing indexes. |
| ISPL‑1391 | Updated log4j2 to release 2.11.2. |
| ISPL‑1392 | PolicyCenter is using a new version of the phone number library that is more lenient when parsing phone numbers than the previous version. The change in the file PolicyCenter/modules/configuration/gsrc/gw/api/validation/PhoneValidator.gs adds validation after parsing for phone numbers that are being persisted.
By default, this stricter validation is turned off. To enable it, set the PhoneNumberStrictValidation configuration parameter to true.
It may be easiest to leave this turned off in development environments if tests contain mock data with invalid phone numbers. It is advisable in most cases to turn it on during deployment (to acceptance test and production) so that phone data is validated. |
| ISPL‑1397 | Fixed a bug in which the date picker always showed the week starting on Sunday, even in locales for which the week is considered to start on a different day. The date picker now shows the correct start of the week depending on the locale. |
| ISPL‑1412 | Fixed an issue in XML code generation that caused a MethodTooLarge exception to be thrown if the generated code contained too many runtime resources, approximately 3500 or more. |
| ISPL‑1417 | Fixed an issue where the server would exhibit excessive CPU utilization, caused by inadvertent triggering of a JDK bug (JDK‑8129861). |
| ISPL‑1569 |
Changed the default format for the Japanese Imperial Calendar long date format in the Japan locale (ja_JP). The format used to be: EEEE, Gy年M月d日 But is now: GGGGy年M月d日EEEE The two differences are:
For example: 平成31年4月10日 水曜日 |
| ISPL‑1570 | Fixed the Load History report to include table row counts. |
| ISPL‑1585 | Allow JMX bean to access configuration variables whose datatype is Set without logging errors |
| ISPL‑1586 | Improved performance in looking up groups or users on some pages. |
| ISPL‑1600 | Whenever document template form field's display value is determined using the language
code to locate the correct locale, PolicyCenter uses
the following searches to determine the correct locale to use:
|
| ISPL‑1605 | Fixed an exception that would occur during logging with the Debug logging level set and no exchange rate sets in the database. |
| ISPL‑1617 | Compilation of ClaimCenter code fails whenever XML files with non-UTF8 characters are present during build, but only on Linux OS. The code compiles correctly on Windows and MacOS. The root cause for this issue is certain environment variables are not set as needed in the build environment forked by the Gradle Worker API task. This fix provides the value for LC_ALL and LANG variables that is then passed to the Gradle worker API task for use in the build process. |
| ISPL‑1641 | Optimized a slow workflow message query on SQL server. |
| ISPL‑1644 | For SQL Server, the SQL Server trace event 9481 has been replaced with the newer hint FORCE_LEGACY_CARDINALITY_ESTIMATION. This change also eliminates the need to grant sysadmin permission to the PolicyCenter schema owner. |
| ISPL‑1657 | The default value for the GW-UnknownPropertyHandling header option for JSON schema support has changed to reject instead of ignore. Any unknown JSON Schema properties on incoming requests are now rejected. To retain the previous behavior, explicitly specify the value of ignore for the GW-UnknownPropertyHandling header on requests. |
| ISPL‑1658 | Fixed an issue that caused the serialization of a JsonObject object containing a FastCompareDate instance to fail. |
| ISPL‑1659 | Fixed an issue in the usage of the Jackson library in internal methods to avoid library conflicts when those internal methods are referenced from Gosu code. |
| ISPL‑1661 | Fixed an issue that accepted primitive parameters in REST API handler methods in cases where the parameter was not required and had no default value and thus could have a null value at run time. A validation error is now generated in that case, so that the method parameter can be changed to the appropriate boxed type, be made the required, or be given a default value. |
| ISPL‑1663 | Added a rewriteErrorResponse method to the IRestDispatchPlugin interface to support rewriting responses on 4xx or 5xx responses, including adding in custom headers. Existing implementations of IRestDispatchPlugin must implement the new method if they do not subclass DefaultRestDispatchPlugin. |
| ISPL‑1665 | Removed a protected method for creation of log message parameters from the DefaultRestDispatchPlugin class to make it easier to retain the default logging behavior and override just the log message parameters. |
| ISPL‑1666 | Added the ability to specify a parameter set in a Swagger schema to define a standard list of parameters for reference within multiple operations. |
| ISPL‑1667 | JSON Schema definitions now support the x-gw-extend property, which can be used to inherit properties from another schema definition, to support reuse and composition. |
| ISPL‑1668 | Added the IRestSchemaWriterPlugin plugin interface that
supports adding or altering JSON schema properties when the
swagger.json file for a REST API is being written out. |
| ISPL‑1669 | Fixed an issue where an integration mapping property path returning a
byte [] would be incorrectly flagged as a validation
error. |
| ISPL‑1671 | Fixed an issue that caused validation of YAML configuration files to not report illegal null values in some cases. |
| ISPL‑1672 | Added the IRestConfigRefreshPlugin plugin interface to control
which configuration files in the file system the REST servlet watches in development
mode, and to control flushing additional configuration file caches when changes are
detected. |
| ISPL‑1673 | Rolling upgrade now tolerates changes to additional configuration files that some Guidewire add-on modules use. |
| ISPL‑1674 | Added support for the additionalProperties property in the .mapping.json files that define integration mappers. |
| ISPL‑1696 | The Server Tools Database Table Information download report now includes the Database Schema Verification report if any schema verification errors are detected. |
| ISPL‑1705 | Fixed an issue around how duplicate properties in JSON and YAML configuration files were reported. |
| ISPL‑1711 | Fixed an issue in which duplicate property keys in JSON and YAML configuration files were not being reported correctly as validation errors. |
| ISPL‑1712 | Changed the order in which some Swagger and JSON Schema properties appear when external schemas are generated or retrieved. This reordering makes the properties easier for a human to read. |
| ISPL‑1993 | Fixed a race condition in Integration View filter parsing. |
| ISPL‑2107 | Fixed an issue where a RangeValue input could
cause its input label to be clipped if the content of the drop-down
was wider than the parent input column. This issue affected only
Microsoft Internet Explorer. |
| ISPL‑2162 | Fixed an issue where errors that occurred while downloading a file were sometimes displayed in JSON format in a different tab. The errors are now displayed in the error messages section of the main window. |
| ISPL‑2163 | Fixed an issue in the Edge browser where long titles would run into other elements. |
| ISPL‑2164 | Fixed an issue that would cause the highlight around the QuickJump input to extend beyond its bounds. |
| ISPL‑2165 | Added a tooltip to the gear icon representing the Options menu. |
| ISPL‑2166 | Fixed some issues with the screen redrawing correctly after zoom or orientation changes. |
| ISPL‑2167 | Fixed an issue where the underlined letter for a menu shortcut was not showing for menu shortcuts inside action menus. |
| ISPL‑2168 | Fixed an issue where reflection was not being triggered when the selected values for a multiselect range input were changed. |
| ISPL‑2169 | Fixed an issue with meridian values in some Date Inputs that would cause erroneous validation warnings. Also ensured that undefined values in the global localization settings load as default values. |
| ISPL‑2171 | Fixed an issue where reflection was not being triggered when moving values between the left and right side of a shuttle widget. |
| ISPL‑2174 | Added support for validation exceptions to highlight the relevant user interface fields on open popups. |
| ISPL‑2176 | Fixed an issue where the contents of an Action menu were not being properly updated when navigating within the same Location. |
| ISPL‑2177 | Fixed an issue where shortcuts defined for an on-demand menu would prevent the on-demand menu from being successfully loaded. |
| ISPL‑2271 | Fixed an issue that caused calling PLDependencies.getLanguages().getAllKeys() to return keys for additional languages that were not configured in LanguageType.ttx. |
Additional resolved issues
This release also addresses the following issues related to developing PCF pages:
| Category | Issue IDs |
|---|---|
| General | ISPL‑96, ISPL‑889, ISPL‑886, ISPL‑881, ISPL‑784, ISPL‑756, ISPL‑559, ISPL‑383, ISPL‑287, ISPL‑286, ISPL‑239, ISPL‑214, ISPL‑1264 |
| Accessibility | ISPL‑66, ISPL‑70, ISPL‑72, ISPL‑119, ISPL‑163, ISPL‑196, ISPL‑224, ISPL‑582, ISPL‑586, ISPL‑610, ISPL‑653, ISPL‑655, ISPL‑698, ISPL‑700, ISPL‑714, ISPL‑757, ISPL‑769, ISPL‑789, ISPL‑815, ISPL‑1012, ISPL‑1264 |
| Improvements to PCF widgets | ISPL‑220, ISPL‑238, ISPL‑285, ISPL‑309, ISPL‑328, ISPL‑376, ISPL‑382, ISPL‑589, ISPL‑651, ISPL‑786, ISPL‑801, ISPL‑802, ISPL‑803, ISPL‑804, ISPL‑805, ISPL‑874, ISPL‑877, ISPL‑879, ISPL‑880 |
| Browser issues | ISPL‑70, ISPL‑20, ISPL‑169, ISPL‑165, ISPL‑1048 |
| Auto-complete | ISPL‑337, ISPL‑377, ISPL‑380, ISPL‑381, ISPL‑878 |
| Autofill | ISPL‑343, ISPL‑575 |
| Calendar | ISPL‑44, ISPL‑55, ISPL‑757, ISPL‑787, ISPL‑1200, ISPL‑1397 |
| Date | ISPL‑169, ISPL‑199, ISPL‑579, ISPL‑592, ISPL‑1569 |
| Navigation | ISPL‑742, ISPL‑1008, ISPL‑1083, ISPL‑1086 |
| Error handling | ISPL‑25, ISPL‑263, ISPL‑784, ISPL‑1265 |
| Visual improvements | ISPL‑314, ISPL‑333, ISPL‑345, ISPL‑365, ISPL‑1029, ISPL‑1039, ISPL‑1053 |