SR-C80388 · Issue 423760
Added denominator counter to avoid PMML average results error
Resolved in Pega Version 8.3
While running a PMML file with test data, the results were always infinity. This was caused by the denominator not being incremented when using the 'average' method, and has been corrected by adding a counter to the evaluator to avoid a divide-by-zero condition.
SR-D19639 · Issue 489967
Rule Security Analyzer failure corrected
Resolved in Pega Version 8.3
Running the rule security analyzer was generating the error "Remove the duplicate Regex". This was caused by RSA validation failing, which was traced to the activity using pyReGex property in invalid-case when the actual property name is pyRegex. This has been corrected.
SR-B35987 · Issue 296514
Improved backwards compatibility for migrated rules with Declare Expressions
Resolved in Pega Version 7.3
The current activity pzUpdateConditionsList did not have backward compatibility for "AND" and "OR" operators in rules created with older version of Pega Platform that allowed the use of "And" and "Or". This has been resolved by adding a check for equalsIgnoreCase when converting "And" to "&&".
SR-C82480 · Issue 421486
Column Headers properly aligned after expand/collapse of Tree Grids
Resolved in Pega Version 8.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.
SR-D23723 · Issue 503088
pxGenerateExcelFile updated for handling blank dates
Resolved in Pega Version 8.2.4
When using a custom template for exporting to Excel, blank DateTime property column values defaulted to the current date. To resolve this, the pxGenerateExcelFile activity has been updated to ensure that an empty date will be exported as blank and that given dates will appear in the correct datetime format.
SR-B33678 · Issue 292086
Bulk process with only 'case type any' properly assigns all processes
Resolved in Pega Version 7.3
When using Bulk Process with "Bulk Process in Background" checked and only the filter 'Case type is any', only the first process was getting assigned to the operator. This was due to the agent name not being properly set while populating the queue with this filter, and has been corrected.
SR-B33678 · Issue 292524
Bulk process with only 'case type any' properly assigns all processes
Resolved in Pega Version 7.3
When using Bulk Process with "Bulk Process in Background" checked and only the filter 'Case type is any', only the first process was getting assigned to the operator. This was due to the agent name not being properly set while populating the queue with this filter, and has been corrected.
SR-B38101 · Issue 299647
Corrected DateTime corruption
Resolved in Pega Version 7.3
If "Display value using read-only formatting" was selected for a Date field, entering an invalid value caused the resulting HTML DOM to be displayed incorrectly when the page was refreshed. This was traced to missing handling for the exception resulting from the invalid data, and has been fixed.
SR-B3893 · Issue 279435
Fixed focus move to top on refresh in tabs for Internet Explorer & Chrome
Resolved in Pega Version 7.3
The refresh event from a button control in a section containing a tabbed layout forced the focus to the top of the section when using Microsoft Internet Explorer 9 (IE9) / 11 or Chrome 54.X . To correct this, the initializeTabs method to set scrollTop value has been updated.
SR-B41106 · Issue 298379
Bulk process with only 'case type any' properly assigns all processes
Resolved in Pega Version 7.3
When using Bulk Process with "Bulk Process in Background" checked and only the filter 'Case type is any', only the first process was getting assigned to the operator. This was due to the agent name not being properly set while populating the queue with this filter, and has been corrected.