SR-C94042 · Issue 444586
Resolved JSON exception with refreshrow used for navigation
Resolved in Pega Version 8.3
After upgrade, a custom implementation of a grid that had a menu configured on right click of the row for the category/description in the uploaded case attachments was not working. This was traced to the RefreshRow(non-list) action generating quotes that made the JSON invalid for a navigation rule, and has been fixed by modifying pzProcessRefreshRowItem to remove quotes from navigation refreshrow action generation.
SR-D17037 · Issue 487531
Check added for backwards compatibility with Case Type when rules
Resolved in Pega Version 8.3
After upgrade, the When rules present on case type rules (used for skipping stages or showing/hiding stage-wide or case-wide actions) were not executing at run time. This was traced to the introduction of the pySkipOrAllowType property in recent versions, and was only reproducible when the ApplicationRuleset was locked and after upgrade irrespective of whether the condition for when was true or false. To resolve this and enhance backwards capability, a check has been added for the SkipOrAllowType property being empty.
SR-C86770 · Issue 426050
Case urgency value will not be reset when processing wait shapes
Resolved in Pega Version 8.3
When a Wait shape was configured with the ‘Users can choose to continue process’ option unchecked, the overall work object SLA urgency was overwritten to 0 when the SLA processed the Wait shape. This was due to the Wait shape using pzWaitTImer, which has all urgency values as 0. The SLA being set to 0 did not occur if ‘Users can choose to continue process’ was checked on the Wait shape because pxSystemFlow was not set to true in that case. To prevent the SLA override, a check has been added that will skip setting the urgency setting if there is a wait shape.
SR-C89656 · Issue 426424
Case urgency value will not be reset when processing wait shapes
Resolved in Pega Version 8.3
When a Wait shape was configured with the ‘Users can choose to continue process’ option unchecked, the overall work object SLA urgency was overwritten to 0 when the SLA processed the Wait shape. This was due to the Wait shape using pzWaitTImer, which has all urgency values as 0. The SLA being set to 0 did not occur if ‘Users can choose to continue process’ was checked on the Wait shape because pxSystemFlow was not set to true in that case. To prevent the SLA override, a check has been added that will skip setting the urgency setting if there is a wait shape.
SR-D21808 · Issue 490281
Filter values retained when editing a report with custom filters
Resolved in Pega Version 8.3
After running a report, if some filter values were selected and then the Edit Report button was clicked and simulated data and actual data fields were toggled, the filter values were lost when exiting the report editor. In the Edit Report Page, trying to drag a new filter condition was not working and the Change logic buttons were not visible. These functions worked as expected when a custom Filter section was not used. This was traced to the custom filter page being cleared in the pzCreateCustomFilterPage activity where the step for creating new page should be skipped if it already exists. To resolve this, a parameter will be set to show if the report was rerun in "reRunReport", and a check has been added in pzCreateCustomFilterPage to see if the report was rerun before running the other 'when' conditions.
SR-B45613 · Issue 302956
Fixed query for RD using dependent classes
Resolved in Pega Version 7.3
A runtime exception was generated when running a summary report due to an incorrect query being built for RD when dependent classes was checked. This was caused by pyGetDistinctRecords being set to true even for summary reports, and has been corrected by ensuring pyGetDistinctRecords is set to false for summary reports.
SR-C84921 · Issue 424316
Connection Manager uses keyring for null prconfig password
Resolved in Pega Version 8.3
After upgrade, credentials from BIX keyring were failing when using BIX via commandline rather than prconfig. This was traced to a behavior change in the Connection Manager, and has been resolved by modifying the Connection Manager to look up the password from the keyring when given a URL configuration where the password is null in prconfig (URL connection only).
SR-B39484 · Issue 296141
Calculation Builder made more robust for use in segments
Resolved in Pega Version 7.3
An error was generated when using the Calculation Builder in a segment, though the Calculation Builder for Report Definition worked. This was traced to code in the Calculation Builder which assumed the report page class would always be "Rule-Obj-Report-Definition", which failed for segments. To correct this, the logic has been modified to be more robust.
SR-D17056 · Issue 488085
Error messaging updated for using Float parameter in RUF
Resolved in Pega Version 8.3
After upgrade, using an RUF that had a float as an input parameter as part of its signature resulted in any callers providing a double type as an input generating an exception. This has been resolved by forcing a NumberFormatException to be thrown within the IL model when encountering a float value ('1.2f' or '1.2F') as the Double.valueOf() API used in IL correctly parses these values to double.
SR-B38317 · Issue 295056
Password expiry logic updated to use start of day
Resolved in Pega Version 7.3
Previously, the password expiry logic was based on a tight format of number of days+ timeStamp. This caused scenarios such as not prompting for a password reset when user logs in, but rather at the exact time stamp of the previous change even if that comes in the middle of work and throws the user out of the session. To avoid this behavior, the password expiry logic is now based on number of days logic with timeStamp defaulted to start of day (00.00) taking care of locale and getting difference in number of days.