INC-147643 · Issue 605386
Corrected filtering logic for Report Definition with declarative join
Resolved in Pega Version 8.5.2
When using a report definition with declarative join enabled, running the report produced the correct results, but filtering on any other column resulted in all values being shown. This has been resolved by modifying the logic used for pzGetGridColUniqueValues.
INC-147856 · Issue 607132
Description input for new reports restricted to 64 characters
Resolved in Pega Version 8.5.2
After saving a report with a description containing more than 64 characters, trying to delete the same report generated error messages saying the report description exceeds 64 characters. There was no maximum character limit set on the description input when creating/editing/save as a report. The delete modal shows any page-level warnings, so the guard rail warnings show up at that time. This has been resolved by disallowing the creation of a description greater than 64 characters in length.
INC-150054 · Issue 607387
Drilldown works for display of all locks
Resolved in Pega Version 8.5.2
In Developer studio, drilling down from the summary count of all locks to see the actual cases locked gave a generic error screen. This was a missed drilldown use case for List Views during security updates, and has been resolved.
SR-D91660 · Issue 555724
Updated document ID handling for deleting indexes
Resolved in Pega Version 8.5.2
When trying to delete a document for index name "work*", intermittent errors were seen indicating an invalid index name or index does not exist value. This has been resolved by updating the handling for delete by ID.
SR-A14386 · Issue 230949
Fixed issue with CSS incorrectly overriding skin rule
Resolved in Pega Version 7.2.1
The skin rule settings "Error Border" and "Error Background" were not having any effect on a text control which contained a validation error. This was an issue with the ErrorShade element being overridden my more specific CSS even though the HTML that used that CSS was never produced at run time. This has been corrected.
SR-A14619 · Issue 229625
Alignment resolved for repeating grid headers
Resolved in Pega Version 7.2.1
Headers were mis-aligned in the UI Gallery for a repeating grid when the freeze header option was chosen along with pagination and width of the content. This was an issue with the initScrollbars function, and has been corrected.
SR-A16012 · Issue 231256
Localization added for locking messages
Resolved in Pega Version 7.2.1
Localization has been added for locking-related messages in LockInfoAdvanced to facilitate translating messages such as "This case is locked by your operator in another PRPC session. Choosing the End other session to release lock option will log out your other PRPC session in order to release the lock. This option may not be effective immediately."
SR-A16406 · Issue 231876
Validation handling added for complex criteria values
Resolved in Pega Version 7.2.1
Incorrect validations were appearing when trying to save a List View rule with a criteria value that uses a property embedded in the pxResults page of a declare page in the Value field of the Content tab and that listed the top level declare page in Pages & Classes. This was due to the unusual structure of this referred property not automatically having the necessary links to retrieve the necessary pages and classes, and handling has been added for this special scenario.
SR-A16638 · Issue 233607
Changed edit control to prevent Google Chrome adding zeroes when localizing
Resolved in Pega Version 7.2.1
When using Google Chrome in some locales, zeros were being added to values in the skin and corrupting entered values. This was due to Google Chrome defaulting to localizing input type numbers, which caused dual localization after the control had already localized the value after reload. When input type is text, only the control localization will happen, so a workaround for Google Chrome has been added where the type of control has bene changed to text in the editable mode for the pyItemAlignment section.
SR-A16804 · Issue 244041
Fixed premature execution of export confirmation in Microsoft Internet Explorer
Resolved in Pega Version 7.2.1
Clicking on the 'Export to Excel' open/save file popup in Microsoft Internet Explorer before it changed color to signify readiness generated the error "unable to read." This has been corrected so the button will not execute until the data is ready.