New and changed in PolicyCenter 10.0.1

A new createSpatialIndex parameter controls whether PolicyCenter creates an index for spatial point data. The default setting is to create such an index. However, if an index reflects duplicative or otherwise excessive spatial point data and degrades performance, consider opting out of creating the index.

The createSpatialIndex parameter applies only to columns with a spatial point data field. If the createSpatialIndex parameter has the default value of true in a column of an extension or custom entity, PolicyCenter creates an index for spatial point data. If the parameter has a value of false, PolicyCenter does not create such an index. In the latter case, PolicyCenter avoids creating an index regardless of whether the parameter is in a <columnParam> subelement of a <column> element or a <column-override> element.

See also

• <columnParam> subelement
• <remove-index>

The ArrayLoader class allows you to load a multidimensional array with at most a single pull from the PolicyCenter database.

Assuming no data stored in cache, when you load a multidimensional array manually, you must query the PolicyCenter database for each array element. Thus, for manual array loading, you must query the database N*M times. Here, N is the number of array elements in the first dimension array, and M is the number of array elements in each of the N second dimension arrays.

This number of queries arises from the fact that a multidimensional array is really an array of pointers. The array is not a data structure where all of the array elements are combined in the same location. Hence, manual array loading degrades performance due to the overhead bandwidth requirement for the N*M queries and due to contention with other database queries.

The ArrayLoader class eliminates this challenge by combining the N*M queries into at most single query. The special case where all of the required data is stored in cache requires no database queries. Thus, the ArrayLoader class reduces the overhead bandwidth requirement and the risk of database contention for loading a multidimensional array.

Guidewire has added a new optional <param> element to file batch-process-config.xml to use in defining a value for the RetryIfInitialConditionsFail parameter. This parameter governs the behavior of a batch process depending on the return value of batch process class method checkInitialConditions. The name of the parameter is case-insensitive.

See also

• Batch process prioritization

In PolicyCenter 10.0.1, Guidewire adds new logging category Server.Database.PerfReport to the set of available logging categories. If set to the INFO log level, PolicyCenter writes detailed messages to the application server log during the generation of Oracle AWR reports or SQL Server performance reports. To minimize the data that PolicyCenter writes to the log, set the value of this log category to ERROR.

In this release, there is a new RateBookPreloadEnabled configuration parameter that you can use to specify whether Rating Management components are loaded on system startup.

In PolicyCenter, parameter sets are always preloaded when the server is in development mode. In this release, you can modify the code that preloads the parameter sets.

See also

• RateBookPreloadEnabled
• Preload Rating Management components

In prior releases, casting a non-numeric String value such as Hello, world to a Double or a Float generated a NaN (Not a Number) value. Casting a non-numeric String value to a Long generated a value of 0. The behavior for all these types has now changed to throw a NumberFormatException exception. This behavior matches casting to other numeric types.

The following are changes to the configuration of PCF files.

See also

• Accessing the PCF Format Reference