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-123303 · Issue 185053

Corrected Case match rule reporting

Resolved in Pega Version 7.1.8

The Case match rule was not reporting results that were greater than the cut off score. This has been corrected by changing the rule RunDuplicateCasesReport to check on InsKey instead of pyID as InsKey is available for all pages of different classes where pyID is not.

SR-123303 · Issue 176110

Corrected Case match rule reporting

Resolved in Pega Version 7.1.8

The Case match rule was not reporting results that were greater than the cut off score. This has been corrected by changing the rule RunDuplicateCasesReport to check on InsKey instead of pyID as InsKey is available for all pages of different classes where pyID is not.

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-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-123492 · Issue 184136

Page properties cannot be configured in remote case types

Resolved in Pega Version 7.1.8

The implementation of the Case Type advanced tab allowing page properties to be referenced under 'publish as a remote case type' was sometimes generating a validation error. As this is a complex issue, the abilty to configure Page properties in remote case types has been removed at this time.

SR-123492 · Issue 183606

Page properties cannot be configured in remote case types

Resolved in Pega Version 7.1.8

The implementation of the Case Type advanced tab allowing page properties to be referenced under 'publish as a remote case type' was sometimes generating a validation error. As this is a complex issue, the abilty to configure Page properties in remote case types has been removed at this time.

SR-123533 · Issue 187272

Corrected calculation of WO SLA Goal,Deadline based on calendar input

Resolved in Pega Version 7.1.8

The calculation of Goal,Deadline for WO SLA was not showing the expected results based on business days in the calendar. This was caused by not passing the appropriate parameter (CalendarName) to Work-.DefineSLATimesFromNewProperties so that BusinessCalendar.addTime function could evaluate the SLA based on the calendars, and has been fixed.

SR-123623 · Issue 178641

Added clipboard clearing for correspondence

Resolved in Pega Version 7.1.8

External assignment was sending out the email correspondence that was configured in earlier stages/flows instead of sending the correspondence that is given in the external assignments rule form. This was a problem with the clipboard where CorrPage was not cleared after the CorrCreate is invoked. To resolve this, CorrNew activity has been modified to add a step to clear the CorrPage.

SR-123623 · Issue 184847

Added clipboard clearing for correspondence

Resolved in Pega Version 7.1.8

External assignment was sending out the email correspondence that was configured in earlier stages/flows instead of sending the correspondence that is given in the external assignments rule form. This was a problem with the clipboard where CorrPage was not cleared after the CorrCreate is invoked. To resolve this, CorrNew activity has been modified to add a step to clear the CorrPage.

SR-123686 · Issue 184976

Properly resolved HTML tags in ListView

Resolved in Pega Version 7.1.8

If any HTML tags such as were used inside the Full Description of ListView, the tags are were not being resolved and were instead displayed as-is. This was caused by how the XSS filter affected the way the tags were reference when returned to the browser, and has been fixed.

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