PolicyCenter 10.0.0 Release Notes

On UWIssue, to prevent duplicate issue types, an IssueKey with leading or trailing white space is no longer allowed.

Required coverages now have a check box showing that the coverage is selected. Because the coverage is required, the check box value cannot be changed.

There is now a warning-level version check for multiple rows with same ABUID for ContactManager linked entities. If this check is triggered, examine your data to determine the extent of the duplicate ABUID values.

Adding an existing Policy Location on a businessowners submission after adding a new policy location now appears in the Location list view.

For submissions, ProducerCodeOfRecord and ProducerCodeOfService are automatically synced up when modifying producerCode on EffectiveDatedFields.  The check for validating producer code is now always done on bind and not only when out of sync with ProducerCodeOfService.

Calls to JobProcess#canWithdrawJob are now null-safe in cases where the Branch has no attached Job, for example preemption branches.

Updated description of the RestrictSearchesToPermittedItems parameter in config.xml. This restricts search results to items that the user has permission to view in contact search screens. This does not impact any other searches in PolicyCenter.

The phone number tooltip on all search screens now uses the current user's phone country preference.

Fixed an issue where a policy renewal was not possible after cancellation and reinstate with a gap introduced by rewrite.

Fixed an issue where the product model generator added a coverage multiple times for a policy type in the PolicyType typelist. For example, in the generated PolicyType.ttx file in the product model generator output folder, some of the category values repeated.

Modifier type in policy versions diff tree is now localized.

Fixed a race condition in ModifiersListViewHelper.

If an effdated bean, such as a personal vehicle, is removed then added in a policy change, the changes are correctly taken into account when they are applied to an unbound renewal, with no loss of information.

Improved performance on policies with long underwriting histories. Changed gw.job.uw.UWIssueEnhancement get Histories().

Fixed an issue in RateQuery.Select method that caused a null pointer exception.

Fixed an issue where multiple users could concurrently change data on a popup, leading to duplicate results.

Fixed an issue where displaying the rating worksheet resulted in a SQL Server error because of reaching the limit on bind variables.

It is now forbidden to add lookups with Unavailable status during Rolling Upgrade. This was previously a known issue.

Improved performance for attaching the reinsurable risk to the applicable reinsurance agreements by eliminating unnecessary queries.

Also, to improve performance, in calls to RIRiskVLFinder#addVersionList(String, Bundle, PolicyPeriod), Guidewire suggests you pass in a null String if you want PolicyCenter to generate a new risk number using IReinsuranceConfigPlugin automatically. This is more efficient than generating it first and then passing it in.

The Policy Review screen now shows differences for entities that are zero-width, for example as a result of being removed on the same date that they were effective.

The method getFutureRenewals now returns all future renewal periods that are the most recent model and are not flat canceled. Previously, it only returned the next renewal of the current period and not all future ones.

The Apply Pending Account Data Updates process is now implemented as a work queue.

Fixed an issue where removing then adding coverages again caused an exception after changing the edit effective date.

Previously the Currency field was locked for the CovTermDefault and CovTermLimits product model patterns only, but now it is locked consistently across the CovTermDefault, CovTermLimits, CovTermOpt, and CovTermPack patterns.

In a submission with out-of-sequence objects, out-of-sequence objects are now correctly merged after quote.

When starting a renewal policy transaction, the term type on the renewal period will always be the default term type defined for the product.

Fixed an issue that occurred when a policy change was initiated and issued between the time the renewal was started and before it was quoted. This error appeared when quoting the renewal: The address for policy #XXXXXX has no corresponding contact address.

Improved performance in PolicyNamedInsuredEnhancement#getOfficialIDsForState by preventing unnecessary calls to an expensive query.

Fixed an issue where the Authority Profile screen for imported authority grants had incorrect values in the Comparison column. This occurred after importing administration data using Administration > Utilities > Import Data.

Fixed an issue that caused the renewal batch process to fail. This issue was related to the setting of MostRecentTerm on PolicyTerm.

In a rewrite policy transaction, Versions > Start Multi-Version is now available.

Rating worksheets now display CodeIdentifier of a coverage.

Fixed an issue where UW Authority Profiles with localized number formats caused validation errors.

Side-by-side quoting is now available for rewrite policy transactions.

Fixed an issue where SideBySideProcess did not set up the correct user locale and language when quoting alternate versions. This could lead to incorrectly localized strings in error messages.

Fixed an issue where revising a revised final audit generated an exception when quoting.

Fixed an issue which caused a false out-of-sequence cancellation warning after changing the Edit Effective Date of a cancellation to an earlier time.

In the integration with BillingCenter 9, PolicyCenter only sends the primary address when sending information about the Contact. Prior releases sent all available addresses for the Contact, identifying the primary address with a Primary flag. This change was made to address an issue where contacts were getting out of sync between BillingCenter and ContactManager.

ProductModelObjectBase#equals now takes into consideration product model pattern type. Both product model pattern type and public ID are required to uniquely identify product model patterns.

ContactManager was not using an ExternalID sent to it from PolicyCenter to set the LinkID for an associated Address and ContactAddress. ContactManager now correctly uses the ExternalID that PolicyCenter sends it for a Contact to populate the LinkID fields in ABAddress and ABContactAddress.