Skip to main content

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 Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-C1144 · Issue 344593

Missing columns added to InstanceList RD

Resolved in Pega Version 7.4

After upgrade, .pyItemId and .pxProcessingNodeId were missing from the pyInstanceList Report Definition. This was due to these two columns being missed during the conversion to Report definition, and this has now been fixed.

SR-C1738 · Issue 345628

Timestamp fixed for Export to Excel

Resolved in Pega Version 7.4

When trying to do a Export to Excel on a report definition with one of the columns being a Date time property, an extra 'a' was seen in the date time columns in Excel. In this case, 'a' is valid for formatting Java datetimes while 'AM/PM' is the equivalent for Excel, so the 'a' will be replaced with AM/PM in the summary viewexcel data.

SR-C2850 · Issue 348798

Missing buttons returned to Marketing report browser

Resolved in Pega Version 7.4

After upgrade, the Report Browser in the Pega Marketing portal was missing the 'Add Category' and 'Add Report' buttons. This was due to a difference in the UI-kit for the header, and has been fixed.

SR-C2920 · Issue 344845

Summary report count fixed when using filter prompt

Resolved in Pega Version 7.4

The summary data count was not getting updated in a report unless the "Prompt for filter changes before displaying report" option on Report Viewer tab (Actions -> Refresh) was unchecked. This was an error in the refresh code related to the display prompt filter check and has been corrected.

SR-C9779 · Issue 351372

Performance improvement for data page sourced by RD

Resolved in Pega Version 7.4

Performance improvements have been made to using a Data page sourced by a report definition by removing the step that creates an unneeded parameter page.

INC-174785 · Issue 651461

Flow connector attachment point control updated

Resolved in Pega Version 8.8

Previously, attempting to change the target point for a connector in the flow modeler to a different point on the same shape did not work without placing the point on an intermediate connector first. An enhancement has now been added to support moving the connector directly to a different constraint point on the same shape.

INC-179727 · Issue 704543

Modified batch requestor handling to ensure cleanup

Resolved in Pega Version 8.8

A large buildup of batch requestors was seen, and restarting the node did not clear it. Investigation showed that in the case of one class reading a DSS value, a Pega requestor was being created when it was unable to retrieve any Pega context, and this requestor was not cleaned up afterwards. To resolve this, an update has been made to the way the requestor and Pega context is being created along with ensuring it will be cleaned up properly after use.

INC-180246 · Issue 664948

Support for apostrophe added to keyword tokenization

Resolved in Pega Version 8.8

A keyword containing an apostrophe was not detected properly in Text extraction model. This has been resolved by updating the annotator used in the tokenization.

INC-180762 · Issue 666291

Calendar gadget correctly displays event of >31 days

Resolved in Pega Version 8.8

When using the pxCalendar gadget to display a hotel reservation of duration > 31 days, the entire bar was not displayed on the PEGA calendar. Investigation showed that eventslist was not considering the month value, and this has been resolved by updating the pzEventPreProcessing activity to check for month.

INC-194348 · Issue 682339

Resolved multiple copies of Pega0050 alerts

Resolved in Pega Version 8.8

The PDC alert Pega0050 was seen multiple times for the standard pxgetoperatordetails activity, step 6.This has been fixed by removing the pagecopy and updating the data page properties.

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us