SR-A98390 · Issue 252437
Scheduled report cleanup error resolved
Resolved in Pega Version 7.2.2
Exceptions were thrown in the logs by the scheduled reports task when trying to clean up the previous day's generated attachment reports. This was due to the name exceeding the length restriction on the property (60 characters) and failing validation, and has been fixed by truncating the field.
INC-154290 · Issue 613471
Signature capture exception resolved
Resolved in Pega Version 8.4.4
The signature capture control was throwing a JSON parse exception when the value was set and section was refreshed. This was caused by the signature for PIMC passing incorrect data which Preview could not parse, and has been resolved by ensuring the correct data for PIMC local store.
INC-141322 · Issue 594510
Resolved drill up doubling the filter box
Resolved in Pega Version 8.5.2
When opening a report with a visual graph, clicking on one of the filtered options, leaving this box open (not submitting it) and then clicking on a bar in the visual graph of the report showed the contents of the graph, but then clicking on the report link to go back to the report overview caused a doubled filter box to be displayed. The report would then have to be reopened before being able to continue. The problem was that the value of .pyUI.pyConfigSecToShow was still set to "filter" after the drill down. When the drill back up happened, the report was trying to show the filter configuration section from before but the context was no longer available and it failed. This has been resolved by adding a call to pzCancelFilterLogicChanges in pzDrillUpReport to set the filters to the previous values and reset the value of pyConfigSecToShow.
SR-A76252 · Issue 253236
String filter values treated consistently
Resolved in Pega Version 7.2.2
Attempting to schedule a report with a string value in the filter condition caused a parsing error even when the report ran correctly in DesignerStudio. To resolve this and make the behavior consistent, the logic has been updated such that If filter value is string but not a property reference, then do not resolve it.
SR-A94342 · Issue 263882
Inserted missing word in property-set-html doc
Resolved in Pega Version 7.2.2
The missing word "is" has been added in In the doc article that comes up when the "?" is clicked while filling in the parameters for the property-set-html activity method, which previously read "Identify the property that to receive its value from stream processing".
SR-A20694 · Issue 255166
Added overlay modal dialog check in service intent
Resolved in Pega Version 7.2.2
The enter key press was not working as expected when initiating a search for a new service intent. While another service intent was currently open, 'enter' jumped back to the open service intent. This has been corrected by adding a target check for an overlay modal dialog.
SR-C61479 · Issue 405988
Bix extract performance improved by only checking cipher type for encrypted properties
Resolved in Pega Version 8.1.1
Previously, if no cipher was configured in extract Rules the cipher type defaulted to null and wasn't cached. This caused performance issues when running against the database. In order to improve performance, the code has been modified to only check for cipher type if the property is encrypted.
INC-135313 · Issue 596098
Correct circumstanced version of portal loads
Resolved in Pega Version 8.5.2
Desktop users were seeing the mobile circumstanced version on the application portal immediately upon login. This was a missed use case for a user logging into a mobile portal first and then into a desktop, caused by data between the two sessions being shared in an invalid way. This has been resolved by updating the save work in progress feature to prevent UI data from being shared between mobile and desktop.
SR-C61596 · Issue 402901
Fixed escaping of double quotes in UI control Tooltips
Resolved in Pega Version 8.1.1
Adding a tooltip to a UI control (such as a button) where the tooltip had both text in "double quotes" and outEx: foo "bar" baz caused a compile time error due to the double quotes not being escaped correctly. This has been resolved by using StringUtils.crossScriptingFilter at design time in pzGenerateLinkOrButton for non template and {{{}}} (triple braces) for template.
INC-140272 · Issue 595250
Report definition performance improvement
Resolved in Pega Version 8.5.2
Performance issues were seen with the pzOperatorsByWorkGroup report definition. This was traced to the report definition is adding an UPPER function for edit filter properties which caused it to take more time to run when combined with an ignore case check in the filters of the Report Definition. This has been corrected.