Skip to main content
circle-square
Outline Circle
square-square
Little Circle
square-square
Little Circle

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the SR ID number in order to find the associated Support Request.

SR-D18589 · Issue 495716

Google Map API correctly loads pointer the first time

Resolved in Pega Version 8.1.6

When using Address Map control with enabled markers whose source is a datapage, the location in the map was redirected as expected to the address populated by the datapage, but the marker overlay that appeared by default containing address details and a link to "Open in Google Maps" did not load. Clicking on random places on the map caused it to load correctly. This has been corrected with the creation of a custom activity to get section markup that will use reload section with proper context to fix the issue.

SR-D11942 · Issue 484611

Tab label added to Report browser launch

Resolved in Pega Version 8.1.6

The tab label name was not populated when a report was launched from the Report browser. This was caused by the label for the tab not being included in the harness, and has been resolved by including RDWinTitle in pzRRDisplayCustomFilterSection.

SR-C96394 · Issue 438672

Report data query updated to better handle exceptionally large queues

Resolved in Pega Version 8.1.6

If the database queue was exceptionally large (more than 3.5 million items), the report data query aggregating the results was timing out and showing 0 items queued on the management landing page. To resolve this, the summary view has been changed to rely on the data pages of the detailed view instead of aggregating the results by firing another query with RD.

SR-D10966 · Issue 477274

IH summary behavior change reverted

Resolved in Pega Version 8.1.6

Changes introduced to Interaction History aggregations in 8.1 intended to better align them with the existing behavior of the Interaction History shape in Strategy produced the unexpected side effect of lots of empty records. Based on feedback, the decision has been made to revert the IH aggregation behavior change.

SR-D10969 · Issue 477275

Logic for the Materialized/Not Materialized feature updated

Resolved in Pega Version 8.1.6

The Materialized/Not Materialized feature was not working properly. When there was an aggregate dataset entry in the Advance page set to use "No" for materialized, doing "Materialized" in IH Summaries LP on that dataset materialized the dataset and created a duplicate entry in the aggregation config page where one was "No" and one was "Yes'. This has been corrected. It was also observed that after an application changed its name while the access groups remained the same, changing a dataset from "Not Materialized" to "Materialized" worked, but changing from "Materialized" to "Not Materialized" did not. Instead, a warning message was posted at the top of the page indicating the problem. Investigation showed that the pzChangeStatus activity failed because the current application name did not match the application name of the access group set for the aggregation configuration record. To resolve this issue, the logic has been updated to remove the reliance on the application name.

SR-D10970 · Issue 477277

Datasets created from the IH summary component correctly listed as aggregate

Resolved in Pega Version 8.1.6

Attempting to create an aggregate data set from the IH Summary shape did not properly list it as aggregate due to a source dataset error. This has been corrected.

SR-D22686 · Issue 493518

IH summaries working with external Cassandra

Resolved in Pega Version 8.1.6

Summaries were not working for external Cassandra. This was an issue with the IH summary component using the aggregated dataset as a reference, and this fix contains several components to improve this function. An issue where the IH aggregates dataset does not materialize when DDS is external Cassandra has been resolved by modifying the code that checks the DDS availability. A filter that was used to match “” did not work when pre-aggregation is off : this was due to the IH Browse operation being done outside of a DF context, and has been fixed. The IH Summary shape not working properly in a strategy if it referenced an aggregate dataset with pxInteractionID as part of the group-by properties was traced to an issue with it generating a pxInteractionID value when executing the strategy, and has been resolved by excluding pxInteractionID from the group keys in the IH Summary shape.

SR-D10598 · Issue 485934

Corrected persistent modal dialog thread

Resolved in Pega Version 8.1.6

When a flow was configured as a modal dialog action inside service cases, closing the modal dialog flow caused the main flow to crash and leave the modal dialog flow thread running. This was traced to a conflict with the harness context on the triggered reload, and has been corrected.

SR-D17919 · Issue 491581

Corrected thread switching when moving between interactions tabs

Resolved in Pega Version 8.1.6

When using Create New for a Phone Call-Consumer in one tab and Create New for an Outbound Phone Call on another tab, the thread was not changing when switching between the tabs of the interactions. Closing the Outbound call interaction resulted in null pages on the clipboard. This has been resolved by updating the pzpega_ui_doc_tabsupport file so it switches to root document context if called from onActivate function using a flag.

SR-D26589 · Issue 496721

Logic updated to populate pagelist data on uploaded multi-sheet Excel files

Resolved in Pega Version 8.1.6

When trying to use the activity pxParseExcelFile on an Excel file containing three sheets where each sheet had a different pagelist, the properties mentioned in sheet 1 were populated on upload but the remaining sheets only showed the error message "Could not get clipboard property for reference Work Queues.". This was caused by an error in Row index handling for the additional sheets, and has been resolved by updating the logic to populate the data in the clipboard.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us