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-119537 · Issue 174774

Improved speed for deleting repeat grid rows with Dynamic Select

Resolved in Pega Version 7.1.7

When deleting rows from a repeat grid with Dynamic Select and heavy HTML, deleting the first one was very fast but a delay appeared when there was one row left in the repeat grid. The browser message "Pegacloud not responding due to a long-running script" would also be displayed. This was found to be caused by a list-to-list control function being invoked for each processOnBeforeSubmit call which generated an increased number of input elements in the form. This has been corrected.

SR-A2 · Issue 203635

Updated use and edit of the 'Search for work' rule

Resolved in Pega Version 7.1.9

After upgrade, an out-of-the-box functionality to search for work items by selecting the case status and selecting a particular field to add as filter on that search was not working correctly and the search icon (which gives the list of status window dynamically) was missing. An attempt to perform a private check out of of the rule generated an error and did not allow 'save as' because it was unable to identify a property pyStringType. This issue was traced to a missing property 'pyStringType' in @baseclass, and this has been added.

SR-A1199 · Issue 206250

Updated Email Listener mProtocol

Resolved in Pega Version 7.1.9

It was noticed that testing mail connectivity was working, but the Email listener was failing to start. This was happened when the "getStore" function on a Mail Session in the connection test passed a protocol argument that included [pop3, pop3s, imap, imaps]. EmailListener did not update the "mProtocol" variable to have the "s" for SSL, so it was only ever one of [pop3, imap]. To resolve this, the protocol name in Email Listener has been abstracted so that the 's' appears when telling java mail the protocol name.

SR-A469 · Issue 210020

Reworked config file search to prevent WebSphere looping

Resolved in Pega Version 7.1.9

During server startup, the engine tries to populate the environment properties by reading the config files for the application server. A problem was found in some installations with WebSphere where trying to locate the XML file containing the information on the server port created an infinite loop that caused the engine startup to hang. To resolve this, the search function call now has been replaced by another method that tries to obtain the same information from config service without having to locate the XML file.

SR-A6521 · Issue 216380

Removed correspondence classname case sensitivity

Resolved in Pega Version 7.2

An error was generated when trying to save correspondence with value 'lookup classname' in source editor. Designating the value as a className worked as expected. This was caused by the innerHTML being set inside the ckeditor, forcing the attribute names to be small and therefore fail validation. To solve this, the presubmit function has been updated to maintain case and allow the classname to be entered in a case insensitive manner (i.e., even if you enter classname before submit, the classname will be replaced as className) and the file can be checked in.

SR-A12357 · Issue 230904

Corrected error handling logic when using KeepMessages

Resolved in Pega Version 7.2.1

Actions such as PostValue, RunActivity, Run DataTransform, and ShowMenu were clearing the error messages on the client even when the KeepMessages flag was set. There was also a clearing mismatch that left the error messages in the table even though the messages were cleared on the client. This happened when there was a click on a check box that "posts" value or when moving from one tab to another in tabbed layout with "refresh when active" enabled. This was an issue with the error handling logic for those functions and has been corrected.

SR-A12357 · Issue 231872

Corrected error handling logic when using KeepMessages

Resolved in Pega Version 7.2.1

Actions such as PostValue, RunActivity, Run DataTransform, and ShowMenu were clearing the error messages on the client even when the KeepMessages flag was set. There was also a clearing mismatch that left the error messages in the table even though the messages were cleared on the client. This happened when there was a click on a check box that "posts" value or when moving from one tab to another in tabbed layout with "refresh when active" enabled. This was an issue with the error handling logic for those functions and has been corrected.

SR-A22240 · Issue 245501

Progressive load grid display corrected for expand pane

Resolved in Pega Version 7.2.1

In an expand pane grid with progressive load, expanding the row details and switching tabs in the row details led to skewed UI on the first display (the second tab inside the row details contains larger amount of markup), but corrected itself on the second expansion. The expand pane in this configuration contained a tab group in which the height of the contents in the second tab was greater that the height of the contents in the first tab, and the resize function has been updated to correctly register and display this difference.

SR-A4719 · Issue 230767

Fixed improper ID carryover after reset all loggers

Resolved in Pega Version 7.2.1

When a user reset the logs, the same user ID was then being populated in the log entries of master agent and requestor lock exceptions from that point on even when the exceptions were from other users. This was due to the username not being cleared correctly after the reset all loggers operation is done, and to fix this, the reset all loggers functionality has been changed such that no data from main thread is copied onto the child thread(the dispatcher thread).

SR-A15970 · Issue 249633

Data population clipboard updated to handle mixed copy type

Resolved in Pega Version 7.2.2

Trying to load the auto populate property 'Address' with a data page was not working due to a Ref-Type AP that was present inside a Copy-Type AP. This was found to be a flaw where all the pages in the subtree of the copy type AP have a special java status set, whereas the property elements have the special java status unset, causing the Ref-type AP inside copy-type AP to fail to populate. The data population clipboard functions have been updated to handle this case.

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