SR-C81829 · Issue 419227
pxCoveredCountOpen value decrease corrected
Resolved in Pega Version 8.2.1
When a flow reached the resolved stage (Resolved-Withdrawn), pxCoveredCountOpen was reducing the count by 2 instead of 1, eventually causing the value to go negative and prevent any further work objects from being marked as Withdrawn. Investigation showed the "Update status" activity was being called twice due to the Temporary WorkPage used to delete assignments persisting and appearing as a duplicate pyWorkPage. This caused an issue when using findPage by pzInsKey. To correct this, the "pxDeleteAssignmentsForWork" activity for Step-15 has been modified to explicitly remove the temporary WorkPage after the assignment is deleted.
SR-C81829 · Issue 419228
pxCoveredCountOpen value decrease corrected
Resolved in Pega Version 8.1.3
When a flow reached the resolved stage (Resolved-Withdrawn), pxCoveredCountOpen was reducing the count by 2 instead of 1, eventually causing the value to go negative and prevent any further work objects from being marked as Withdrawn. Investigation showed the "Update status" activity was being called twice due to the Temporary WorkPage used to delete assignments persisting and appearing as a duplicate pyWorkPage. This caused an issue when using findPage by pzInsKey. To correct this, the "pxDeleteAssignmentsForWork" activity for Step-15 has been modified to explicitly remove the temporary WorkPage after the assignment is deleted.
SR-C83615 · Issue 424946
Support added for hiding unwanted category reports
Resolved in Pega Version 8.2.1
After upgrade, a customization used to hide unwanted out-of-the-box category reports was not working. This was due to the pyServiceLevelPerformance and pxSimulations category rules not being included as part of the pyOOTBVisibleInBrowser 'when' rule that is specified for Display in the report browser 'when' setting. These two category rules - pxSimulations and pyServiceLevelPerformance - have now been modified to reference the 'when' rule pyOOTBVisibleInBrowser so categories may be hidden as desired.
SR-C77088 · Issue 417783
Pega API returns control format for pxButton
Resolved in Pega Version 8.1.3
When using the Pega API to get action details applied to an assignment (using the API GET {{url}}/assignments/assignmentID/actions/actionID), the control format value was not returned by the API for pxButton controls and other non input type controls like pxLink. It did work for input type controls like Text Input and Dropdown. This has been fixed by adding support to the control format for modes(1) and modes(2).
SR-C87881 · Issue 427100
Additional dropdown options exposed for RD column definitions
Resolved in Pega Version 8.2.1
When using Column formatting in Report Definition ruleform, the "Negative format" option was losing its custom style after opening and submitting the "Format" popup using the magnifying glass. This was caused by the submitted popup overwriting the inherited style reference. Previously, the style ref options were hidden from the dropdown because the same UI is shown in the ruleform and the end user portals and the desire was to avoid end user confusion. In order to support developer use, pzPopulateNegativeFormat has been updated to expose the missing options in the dropdown.
SR-C68993 · Issue 416163
Expression exngine correctly evaluates boolean type property with expression
Resolved in Pega Version 8.1.3
When using a dynamic layout with a visibility condition expression and 'Run Visibility Condition on client' checked, a condition such as .VehicleDetails != '' && .VehicleDetails = true was not being evaluated as expected after upgrade. This issue was related to changes made to the expression engine to get the initial evaluation result at the server side, and was caused by a missed use case for a boolean type property with expression. This has been corrected.
SR-C74648 · Issue 422905
Autocomplete arrow placement corrected in Right to left local mode
Resolved in Pega Version 8.2.1
When using the Autocomplete control, the blue arrow was seen to have an incorrect placement/orientation in RTL mode. This was traced to the autocomplete background-image in RTL mode being the same as that for LTR, and has been resolved by adding specific background-image for RTL.
SR-C76417 · Issue 430546
Check added for reference function in DB2 join
Resolved in Pega Version 8.2.1
In DB2, when a sub-report column contained a function that was used for a join condition in the main report, an invalid filter property error was generated while saving. This was traced to the edit validate rule checking for the data type of both of the properties used in the join, and has been resolved by adding a check to see if the join operand is of function 'reference'; if so, the system will resolve the function, check for data type property, and set it.
SR-C82480 · Issue 421487
Column Headers properly aligned after expand/collapse of Tree Grids
Resolved in Pega Version 8.2.1
When using a hierarchical table - tree grid with a configuration that included Width of content-Pixels(Fit Content), a Fixed (pixel) size grid, and Freeze Header, expanding and collapsing back the contents resulted in a misalignment of the column headers. The fixed header implementation makes use of multiple table layouts which have to kept in sync via javascript; this issue has been resolved by rewriting the fixed header implementation to call setHeadersWidth on expand/collapse of a treegrid row.
SR-C82480 · Issue 421488
Column Headers properly aligned after expand/collapse of Tree Grids
Resolved in Pega Version 8.1.3
When using a hierarchical table - tree grid with a configuration that included Width of content-Pixels(Fit Content), a Fixed (pixel) size grid, and Freeze Header, expanding and collapsing back the contents resulted in a misalignment of the column headers. The fixed header implementation makes use of multiple table layouts which have to kept in sync via javascript; this issue has been resolved by rewriting the fixed header implementation to call setHeadersWidth on expand/collapse of a treegrid row.