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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-C40603 · Issue 383184

Europe/Ulyanovsk time zone will be handled as Europe/Samara to maintain local datetime values

Resolved in Pega Version 8.1

For some time zones, when a datetime value was provided it was changed to a default GMT value after a section refresh. This was caused by the Moment APIs utilized by Pega for time zone-based conversion on the client not including support for "Europe/Ulyanovsk". In order to work around this, if the operator time zone is "Europe/Ulyanovsk" it will be handled as "Europe/Samara" in the pzpega_ui_formatDateTime.js file.

SR-C40604 · Issue 378650

File Listener variable modified to resolve authorization exceptions

Resolved in Pega Version 8.1

An authorization exception was generated while running File Listener. This error was traced to a situation where the variable mEvaluateAuthorizationCheck was getting modified by more than one listener at the same time, and has been resolved by changing mEvaluateAuthorizationCheck from a static variable to an instance variable.

SR-C40673 · Issue 383958

Validation checks added to catch upgraded Application Rules with invalid characters

Resolved in Pega Version 8.1

When a system has been upgraded from 7.2 to Pega 7.4, the Application Rule created in 7.2 can inherit characters that are invalid in Pega 7.4 such as ":". These invalid characters result in exceptions being thrown on every rule. In order to better handle this difference, the system will now validate on 'New' and 'Save As' according to the current standard of "starts with a letter and can contain letters, ampersands, numbers, underscores, and dashes".

SR-C40759 · Issue 385658

Hover event works for modal text area

Resolved in Pega Version 8.1

A Hover event was not working in modal dialog on a text area or text input. If a link was placed then the issue did not happen. This was traced to the console being unable to get the property showsmartinfo because it was of undefined or null reference, and the shouldIncludeSIScript method has been updated to include text input and text area in ControlsInfo to correct this.

SR-C40884 · Issue 378655

Check added for button labels using keyboard access key markup

Resolved in Pega Version 8.1

If a button label was configured with a keyboard shortcut in nontemplate mode, the action string was not getting generated properly. This was due to the button label using access key mark up, and has been fixed by adding a check.

SR-C41067 · Issue 382608

Number type conversion from DSMClipboardPage matches platform page

Resolved in Pega Version 8.1

The DSMClipboardPage implementation behaved differently than the platform page regarding converting numbers to decimal and when rounding took place. To correct this, the behavior of number type conversion from DSMClipboardPage has been aligned with the behavior from the platform page by calling an API provided by the platform.

SR-C41076 · Issue 379073

Mobile buttons revised to workaround iOS browser click bug

Resolved in Pega Version 8.1

When using the iOS browser, buttons were getting stuck or frozen and requiring multiple clicks to execute. This was traced to an error in the iOS browser version 11.4 where click events are triggered with event.timeStamp as a negative number. To avoid this, the system will not rely on event.timestamp, but will instead get the current datetime and maintain it in prevEvent object.

SR-C41426 · Issue 378692

Resolved survey userscript JS error on mobile logoff

Resolved in Pega Version 8.1

A JS error was being generated from survey_ui_userscript_offline.js when logging out of the mobile application. This was caused by a missed null check for the QPREFPage before referencing property on it, and has been fixed.

SR-C41461 · Issue 386651

DateTime control fixed for year selection with unlimited Date Range

Resolved in Pega Version 8.1

After upgrade, there was a difference in behavior in the datetime control -> year range selection. With default configuration, it was possible to select a maximum of 10 years backwards and forwards, but if the Date Range option was not checked it was not possible to select any year. This has been corrected by implementing spinner functionality for an infinite number of years if the Date Range restriction is not used.

SR-C41540 · Issue 378722

Filter indicator color repaired for frozen grid headers

Resolved in Pega Version 8.1

The filter indicator color was not changing for columns when the header of grid was frozen. This has been corrected by updating GenerateGridHTML to generate the correct RDColumnName for freeze header grid columns.

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