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-123642 · Issue 187841

Resolved MultiSelectList control issues for Microsoft Internet Explorer 9+

Resolved in Pega Version 7.1.8

The MultiSelectList control was no longer working for Microsoft Internet Explorer 9+. When a user attempted to select one or multiple items in the MultiSelectList control, the values were not captured when going to the next screen and a JavaScript exception was thrown. This was due to an API change in newer versions of the Internet Explorer (Microsoft Internet Explorer) browser. Microsoft Internet Explorer is following a more strict standard about how the createElement function is used, which caused the JS error to be thrown, and the system has been updated to resolve this issue.

SR-123663 · Issue 184330

Multi-cell paste supported for Excel Map Value edits

Resolved in Pega Version 7.1.8

When trying to paste multiple rows into a Map Value using the 'Edit in Excel' feature, a runtime error was generated. The root cause was a refactoring code snippet that assumed only one cell for a change / paste, and the logic failed for multi-cell paste. The property used in the original logic becomes nonexistent (Target.Value) when multiple cells are being pasted. To resolve this, a different property (an array called Target.Value2 ) has been incorporated to populate and adjust the target cells.

SR-123678 · Issue 185155

Resolved issue with duplicate thread creation

Resolved in Pega Version 7.1.8

In Designer Studio, a new thread was created on every click of New Item in the recent list. This was due to the contentID generated not being passed at the document launch time, and the APIs have been updated.

SR-123681 · Issue 187957

AddTime calendar function corrected for calculating expiry times

Resolved in Pega Version 7.1.8

Using the out-of-the-box @addTime function to calculate expiry time was not calculating the correct time or was reporting a missing calendar when passed a calendar instance. The root cause of this problem was due to the calendar instance not using the time zone field while acquiring Gregorian Calendar in the class CalendarUtility. java. This datetime problem has been fixed.

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.

SR-123712 · Issue 184471

Resolved schema qualification for dedicated tables

Resolved in Pega Version 7.1.8

When creating a data table / data class via the wizard, selecting "Create Dedicated Table" would show success on the wizard screen but the class was mapped to "pr_other" and an error was logged. This was caused by incorrect schema qualification for WorkHistory, and has been resolved by inserting a requirement for implicit schema privileges.

SR-123717 · Issue 192182

Purging of covered objects improved

Resolved in Pega Version 7.1.8

When purging a Cover item, the history of certain covered objects was not purged. This happened when the Cover and Covered classes belonged to different class groups. This happened because the 'getHistoryKeys' function tries to fetch the history details of a given key by looking into its history table. This was using the class group information from the archive configuration, which was not always the same for covered objects. To resolve this, the classgroup info will be fetched from its key - looking up Class map using the constructed class name will give the actual History Class name.

SR-123724 · Issue 184667

Updated RDEs invoked by collection rules

Resolved in Pega Version 7.1.8

Collection Rule was not invoking an RDE when the RDE is configured to be "When applied by a Rule Collection". However, it worked fine when the RDE is configured to fire "Whenever inputs change". This was found to be a problem with declare expressions not fired a second time. The RDE is configured with change tracking "when applied by a rule collection". In certain cases the system will try to avoid caching auto chaining status on to property as YES, so chaining is skipped the second time. Because this was not leading to the desired results, the code has been changed to cache the auto chain status for RDEs for collections.

SR-123741 · Issue 186119

Collapsible header text updated for accessibility

Resolved in Pega Version 7.1.8

When a UI layout/section used a collapsible header, JAWS read the field values "Click to expand" and "Click to collapse." Using the word "Click" is not optimal for accessibility, and this field has been changed to "Disclose contents" and "Hide contents."

SR-123750 · Issue 189489

Smoothed multiple portal tabs handling

Resolved in Pega Version 7.1.8

After opening the Case Manager developer portal, if a user portal was opened in a second tab using the 'Switch Portal' option shown in operator menu, returning to the developer portal tab caused that tab to be refreshed and the user portal tab to close. Previously, attempting to open a second portal session in a tab of the same window resulted in a 'Multiple sessions running' error. This limitation was removed in Pega 7.x. However, in this case the 'ShowDesktop' activity could not determine the 'ThreadName' parameter and defaulted to the 'Standard' thread and this change caused the refresh. The logic for determining the thread name has been updated to remove this issue.

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