New and changed in PolicyCenter 9.0.3

In 9.0.3, Guidewire added the following option to the list of options to use in generating a set of performance reports from the Server Tools Oracle AWR Information screen:

Include native Oracle report

Selecting this option ensures that PolicyCenter generates an Oracle Standard AWR report automatically as you generate a Guidewire AWR report.

See also

• Automatic generation of Oracle standard AWR reports

Labels on an XML GX model enable instances of the model to be created that include only the properties required for a particular context. For complete information, see GX model labels.

Element <work-queue> in work-queue.xml contains a new optional attribute named blockWorkersWhenWriterActive. If set to true, PolicyCenter blocks work queue workers from acquiring work items while the writer is writing new work items to the work queue. The default is false.

See General work queue configuration for details.

Support has been added to the distributed messaging process to force the Before Send plugin to be called even on retries where the message has already been bound. Forcing the plugin call is desired if an update to the message payload is necessary before retrying to send the message. By default, forcing the plugin call is disabled.

For more information, see Use the Messaging editor to create new messaging destinations.

A new command, gwb exportWsdl, exports the WSDL for all WSI web services to a single JAR file.

For more information, see Integration tasks.

A new command, gwb genSchemaJar, improves build times.

After an integration project is finished and stable, the XML and XSD schema files that are created during WSDL code generation will rarely change. Instead of having each build recreate these static files, the files can be created a single time and stored in a Schema JAR file. The JAR file is then made available to all developers for general access. Subsequent builds use the contents of the preprocessed JAR to reduce build times.

For more information, see Creating an XML Schema JAR file.

Guidewire has added configuration parameter BizRulesCacheStaleTimeMinutes. Use to manage cache eviction times for the RuleVersion cache. See Business rules parameters for more information.

Guidewire has made the following changes in PolicyCenter 9.0.3 to support the rolling upgrade of very specific updates to product model patterns.

1. Guidewire modified the rolling upgrade process to support making changes to the following product model types in a rolling upgrade:
   • Coverage, Condition and Exclusion, Coverage Term, and Coverage Term Option Patterns
   • Offering and Offering Selection Patterns
   • Question Set and Question Patterns
   • Modifier Patterns
   • Lookup, Grandfathering, and ModifierMinMax
2. Guidewire added batch process ProductModelPatternActivation, which you run after completing a rolling upgrade to activate any new product model patterns added during the rolling upgrade.

Guidewire disables (makes inactive) any changes to these product model types until you fully complete the rolling upgrade on all servers. You must then run the ProductModelPatternActivation batch process to activate your changes.

See also

• Updating product model patterns in a rolling upgrade

PolicyCenter 9.0 added a new business rules framework which provided a user interface for defining underwriting rules. You can view this new interface by navigating to the Administration Business Settings > Business Rules > Underwriting Rules screen.

When upgrading from PolicyCenter 7.0 and 8.0, legacy underwriting rules have a corresponding underwriting rule in the Underwriting Rules interface. The Gosu code that implements the rule continues to work, and accesses the corresponding rule in the Underwriting Rules interface. You can choose whether to keep the Gosu implementation, or reimplement the rule in the Underwriting Rules framework.

In PolicyCenter 9.0.0 through 9.0.2, these imported underwriting rules implemented in Gosu are marked as invalid in the Error column on the Underwriting Rules screen. Although the rules are marked as not enabled, the Gosu implementation continues to run.

As of PolicyCenter 9.0.3, these rules are marked as externally managed in the State column on the Underwriting Rules screen. On the underwriting Rule screen, the Applies to, Rule Context, Rule Condition, and Underwriting Issue Details sections do not appear. A rule, UWRule object, that is externally managed has its ExternallyManaged property set to true.

Externally managed rules have their rule condition and action defined outside business rules, often in Gosu code. Externally managed rules include, but are not limited to, upgraded underwriting rules implemented in Gosu.

Messages are sent to a particular destination, usually an external system. If Distributed Request Processing is enabled for a particular message destination, then its before-send messaging operations can be configured to run on a specific server or group of servers. The server that runs a destination’s before-send operations can be different from the server running its other messaging operations.

This capability enables greater flexibility in balancing the execution load associated with messaging operations.

For more information, see Use the Messaging editor to create new messaging destinations.

Implementations of the Document Metadata Source plugin method retrieveDocument must initialize the internal properties of the returned Document object. The internal properties are initialized by calling the new method DocumentsUtilBase.initOriginalValues.

For more information, see the description of the retrieveDocument method in Implementing an IDocumentMetadataSource plugin.

Guidewire now sets the allowable maximum number of writer runs to show in the Work Queue Info report at 150. Previously, the allowable maximum number was 25.

The following components have been removed from Gosu in PolicyCenter 9.0.3:

• Command-prompt options

  The -i, -interactive, and - options for the gosu command are no longer available. Gosu does not provide an interactive shell or accept a program from the standard input stream.

• Package gw.lang.cli

  The gw.lang.cli package is no longer available. To get the full list of command-prompt arguments as a list of String values, use the RawArgs property of the gw.lang.Gosu class.

• Class gw.util.Shell
• Support for definition of class path in registry.xml

  Use either of the following techniques to set the class path:

  • Use the classpath command as the first line in a Gosu program file.
  • Use the -classpath option to set the class path for a Gosu program that you run from the command prompt with the gosu command.