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-132637 · Issue 203591

Added path checking to FirstLogCreationTime.log

Resolved in Pega Version 7.1.9

FirstLogCreationTime.log was being written to a temp folder using hard-coded logic to use a relative path within the install directory. This caused errors if the installer was trying to write the logs in an absolute path. FirstLogCreationTime.log should be written to the same directory as the rest of the logs, and this issue has been fixed by adding a condition in LogDeleteUtil.getLogCreationTimeFile() method to check for absolute paths.

SR-133747 · Issue 203813

Corrected hashtag handling for Oracle SQL generation

Resolved in Pega Version 7.1.9

Given a column name with a hashtag in an Oracle environment, the system was compiling SQL statements which caused ORA-00904 errors due to replacing the # in one variable name with an _ but leaving it as a # in another. This has been corrected.

SR-133057 · Issue 205124

System updated to better handle multi-node rule resolution

Resolved in Pega Version 7.1.9

In an upgraded multi-node environment, the error 'com.pega.pegarules.pub.database.MultipleRuleVersionException: Rule resolution identified 2 versions of the rule' was sporadically appearing. Once the issue occurred, it would persist and the only way to resolve it was to bounce the server. This was an issue with an instance of one rule being found in one node and not found in other node, and was related to the trigger logic. This should not occur with the current Pega7 version, as trigger logic has been moved into the engine and there is no longer a database trigger to fix. In order to ensure continued smooth trigger resolution, tests have been added that will check for this condition in the updates cache table to ensure that this scenario does not occur again

SR-123525 · Issue 186662

Added handling to maintain f ordered list styles in send correspondence

Resolved in Pega Version 7.1.9

In the send correspondence, if the ordered list format was selected and then deselected and again selected, then the bullet points or numbers appeared differently. Handling has been added to maintain the correct appearance through multiple changes.

SR-125651 · Issue 189974

Error icons and localization corrected for repeating tabs headers

Resolved in Pega Version 7.1.9

The error message indication was not appearing on the tab header of repeating tabs. In addition, the tooltip of that icon was not being correctly localized. These issues have been corrected.

SR-127915 · Issue 203511

Resolved NPE for URLEncryption in grids

Resolved in Pega Version 7.1.9

When URLEncryption is enabled in a grid scenario, the property reference was not generated as expected. In this scenario, the AjaxTrackID was not being passed from client to server due to it being a new harness load where normally a new AjaxTrackID would be created at the server end. To resolve this, the pzActionOpenURLInWindow API has been updated.

SR-128119 · Issue 202650

All localization errors displayed as expected

Resolved in Pega Version 7.1.9

When localization wizard generated errors during translations import, it only displayed one in the UI. This was an issue with the errors pagelist not being fully populated with values correctly in pzImportTranslations Activity, and has been resolved.

SR-129722 · Issue 204564

Removed extra white space appearing with Microsoft Internet Explorer 8

Resolved in Pega Version 7.1.9

Using Microsoft Internet Explorer 8, extra white space appeared above the "Next" button in a screen flow when a declare expression was fired. This has been fixed.

SR-130340 · Issue 204442

Corrected date selection highlight for Date-Medium control

Resolved in Pega Version 7.1.9

When Date-Medium control was used in a section and configured with onchange->refresh section, selecting any date other than today's date and opening the calendar pop up again caused the selected date to not be highlighted in the pop-up. To resolve this, datetimecalendar.js has been modified to set the proper date in cases of cal.dateFormat == 3 (Date-Medium and DateTime-Medium control).

SR-130340 · Issue 207380

Corrected date selection highlight for Date-Medium control

Resolved in Pega Version 7.1.9

When Date-Medium control was used in a section and configured with onchange->refresh section, selecting any date other than today's date and opening the calendar pop up again caused the selected date to not be highlighted in the pop-up. To resolve this, datetimecalendar.js has been modified to set the proper date in cases of cal.dateFormat == 3 (Date-Medium and DateTime-Medium control).

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