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-123228 · Issue 184623

Charts code updated for resizing with new browsers

Resolved in Pega Version 7.1.8

After upgrade, summary view charts viewed with the latest version on Microsoft Internet Explorer were not reflecting any change of height even when the height was increased in the parameter tab or the cell. This was due to the parameters for the chart control not containing an expected trailing 'px' on the number that the browser required to know the expected unit of measure. Checks have now been inserted into the code to handle the conversion for the browser.

SR-123313 · Issue 185096

Drilldowns fixed for reports containing text values

Resolved in Pega Version 7.1.8

In Summary view reports, Onclick functionality to open the drilldown report is not working for the non numeric values. This was an issue with the SummaryViewBodyTag.java not properly handling quotes around database values, and the code has been modified.

SR-123330 · Issue 188222

Resolved exceptions generated by empty property values

Resolved in Pega Version 7.1.8

Empty values passed to the java object were generating the exception "ProjectName.value is blank and the jar file expecting a value". This was an issue with a new code generation strategy on property set where the empty value set on a java property was not setting it on the wrapper. This has been corrected.

SR-123344 · Issue 185832

DeleteOrphanStaticContent activity modified to prevent CSS errors

Resolved in Pega Version 7.1.8

The DeleteOrphanStaticContent is used to delete any un-used assembled static contents, but it was sometimes deleting CSS files that were still in use by the system, causing 404 errors. This activity has been changed to use use the node statue query in order to ensure it clears items correctly.

SR-123344 · Issue 191091

DeleteOrphanStaticContent activity modified to prevent CSS errors

Resolved in Pega Version 7.1.8

The DeleteOrphanStaticContent is used to delete any un-used assembled static contents, but it was sometimes deleting CSS files that were still in use by the system, causing 404 errors. This activity has been changed to use use the node statue query in order to ensure it clears items correctly.

SR-123430 · Issue 185464

Right-click info calls corrected for tabs

Resolved in Pega Version 7.1.8

Calling an activity under "Right Click Smart Info Settings" section in Format tab in list view rule was not working properly. This was an issue with the smartinfo code when mousing out from the row, and has been fixed.

SR-123434 · Issue 183436

Smoothed post-upgrade ApplicationSetup that uses previously generated LDAP configs

Resolved in Pega Version 7.1.8

An LDAP configuration created under a previous version of the software was generating an NPE after upgrading. This was traced to step2 of the ApplicationSetup activity where the system was expecting a page which was missing at that point due to the user not yet being fully identified. To avoid this, a step has been added to check if the page is available and avoid the NPE.

SR-123444 · Issue 185535

DateTime conversion corrected for Excel

Resolved in Pega Version 7.1.8

When parsing an Excel file and extracting the values, the DateTime fields were being returned as a double value. This was an issue with the date to decimal conversion in the toLocal and toGMT functions, and has been corrected.

SR-123455 · Issue 184832

Java thread names corrected for Designer Studio developer activities

Resolved in Pega Version 7.1.8

When trying to run an activity from the Designer Studio developer window, the error "Section 'pxRunRecord' execution error on page 'RunRecordWindow' of class 'Pega-RunRecord" was appearing. This was caused by an error in the Java code relating to the thread name changes after upgrade, and has been modified.

SR-123581 · Issue 188015

Scrolling corrected for Safari on mobile devices

Resolved in Pega Version 7.1.8

When using the global search on a tablet or mobile device, the results are displayed in a modal pop up in the browser. However, scrolling was not working when using Safari on a mobile device. To correct this, the Search Panel CSS and js were modified to enable scroll support on mobile devices.

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