Explore Known Issues

Underwriter fields are empty or show the previous underwriter (Explore for Policy)

Issue

In Explore for Policy solution content, the following underwriter fields are null or show the previous underwriter, even though PolicyCenter shows the correct current underwriter:

In polperfinal: underwriterusername, underwriteractualname, underwriterusernamepublicid, underwritergroupname, and underwritergroupnamepublicid
In pc_uwissue_curation: assignedunderwritergroupname and assignedunderwritergroupnamepublicid

This issue occurs when an underwriter is assigned or reassigned to a job after the policy period was last updated. Explore for Policy only considers underwriter assignments made on or before the policy period's last update time. In PolicyCenter, underwriter assignments don't count as an edit to the policy period.

Workaround

Guidewire is aware of this issue.

Duplicate loss amounts in the Profitability solution (EFR for Claims)

Issue: In the Profitability solution content, efr_fact_profitability contains duplicate loss records for claims whose policies have been refreshed or reselected in ClaimCenter. This issue causes loss amounts to be overstated. The premium side of efr_fact_profitability and the loss fact efr_fact_loss_calendaryear are unaffected.; Each policy refresh replaces the claim's policy snapshot (cc_policy) with a new one that has a new Public ID. efr_wrk_profitability_loss_calendaryear builds its record key from that Public ID, so each refresh creates a new set of loss rows while keeping the previous rows.; The duplicate rows have the same amounts and differ only in bkey, skey and updatetime. For example, a claim whose policy was refreshed twice shows the same loss amount three times in each snapshot period. This affects every snapshot period for that policy, not just one accounting period.
Workaround: Guidewire is aware of this issue.

Can't create custom calendars

Issue

When you try to create a custom calendar, you always get an error message. For example:

You don't have enough privileges to the selected database.
Maximum limit reached to create a calendar.

All errors are caused by a limitation in the underlying database permissions.

Workaround: There’s currently no workaround. Guidewire is aware of this issue.

Search keywords sometimes don't match filter keywords

Issue: Keywords used in the search bar sometimes don't match the resulting keyword displayed in the chart's filter. For example, last hour and last 1 hour. This issue doesn't affect the accuracy of search results.
Workaround: Guidewire is aware of this issue.

Iterative change analysis sometimes causes the page to crash

Issue: When you analyze a value within a change analysis, the page sometimes crashes.
Workaround: Guidewire is aware of this issue.

Pivot tables reload after expanding or collapsing rows

Issue: After you expand or collapse rows in a pivot table, the table unexpectedly reloads.
Workaround: Guidewire is aware of this issue.

Sorting a pivot table sorts only by rows

Issue: If you try to sort a pivot table by adding a sort to the search query or by updating a measure, the table can't sort by columns.
Workaround: Hover over the column name and select the More ellipsis, then select Sort.

Filters in Explore mode don't work for line charts

Issue: This issue only occurs on line charts. After selecting the Explore button on an answer, you can apply filters to it. Applying filters to a column that already has them causes the existing filters to disappear.
Workaround: Edit the filters that appear below the answer title instead of using Add your own filter or select a suggestion.