SR-D5404 · Issue 446468
Support added for nested grids with child categorization
Resolved in Pega Version 8.1.6
Show Details and Expand All were not working as expected in a repeat grid with a nested grid scenario where the parent grid had Show Details enabled and the child grid had categorization enabled with one column selected for categorizing. Investigation showed that a null page was being passed (final @baseclass pzGridSortPaginate activity) due to a lack of support for considering page lists that are embedded in a page different than the step page. To add this support, the activity has been modified to use tools.getProperty(...) instead of myStepPage.getProperty(...) if the data source page list is not an embedded property in the parent row page.
SR-D7798 · Issue 463292
Grid reordering has correct row numbers in embedded panes
Resolved in Pega Version 8.1.6
When using an expand pane grid with row numbering and row reordering enabled, normally reordering any rows handled the row numbers as expected. After a new record was added in the Embedded Pane and the rows were interchanged/reordered, the row numbers were not reordered with respect to the numbers. Expanding a row and reordering it with the previous row resulted in the numbers being correct and swapped, but collapsing that expanded row then showed its old number. Attempting to expand the above collapsed row/wrong number row instead expanded the previous row. To resolve this, the performModalAction function in ui_grid JS has been updated so the row page and primary page will be recalculated even for single expand reordering case.
SR-D9610 · Issue 476235
Check added for null values in boolean filter of column properties
Resolved in Pega Version 8.1.6
Null values in the filter were showing as "NO" when 'Filter by Format' was enabled for filtering a boolean property (Checkbox) in the Column Properties of the table. This has been resolved by adding a check for empty values.
SR-C97399 · Issue 439743
Button type added to allow grid expand in Edge
Resolved in Pega Version 8.1.6
When using an expand pane grid in a modal with the Edge browser, clicking on the expand icon using the enter key was throwing an error in new window. This was traced to an issue with a hidden non-auto-generated button in the pzModalHelp control not having a default type, and has been resolved by adding type="button" in the control so Edge will treat it as a submit button.
SR-D12530 · Issue 482722
Spinner wheel dom correctly cleared after incomplete case closure
Resolved in Pega Version 8.1.6
Incorrect behavior of the spinner wheel during a case search following the browser being closed while a case was open has been resolved by updating pzpega_ui_doc_actionRouter to ensure the wheel dom is correctly cleared.
SR-D18960 · Issue 499911
Logic updated to resolve busy indicator delay
Resolved in Pega Version 8.1.6
On click of submit in the main interaction flow, the busy indicator was not getting displayed or was displayed after a delay whenever there were a series of Ajax requests being made. The logic has been updated to resolve this issue.
SR-D23700 · Issue 497920
Repaired setValue(Boolean) clipboard mapping
Resolved in Pega Version 8.1.6
A Set Value for an Hidden Control associated property was not mapped to clipboard as expected. This was an unintended side-effect of work done to resolve an alert generated while attempting to post a feed even though there was no Pulse gadget used in the work object, and was due to the read-only option being considered for hidden input in spite of no design time configuration. A hidden field check has been added so that by default it will be readonly false irrespective of editable and non-editable.
SR-D9119 · Issue 481679
Handlng improved for rollback of Hfix with dependent HFixes
Resolved in Pega Version 8.1.6
Attempting to rollback an HFix with dependent HFixes resulted in a Hazelcast jar exception. Investigation showed the DL included the same jar multiple times in the dependent hotfixes, which was a result of how the DL was created via the hotfix process. In order to better handle this scenario, when there are multiples of the same entries to delete the message will be logged and the process will continue if the entry is not found in the database.
SR-D17660 · Issue 486702
Resolved OOM error for system scan
Resolved in Pega Version 8.1.6
In some installations, performing a system scan would cause an Out Of Memory Error. This was traced to the process used to de-serialize the catalog metadata, which caused the unzipped version of the catalog (containing data going back to v6 releases) to grow to 125 MB. To resolve this issue the system will make use of streams, but as that still requires the entire catalog object to be available, the system will also cull redundant objects from the hotfix catalog. Going forward, platform-specific catalog files will be created to minimize their size and improve efficiency.
SR-D10171 · Issue 482471
Updated UtilsEmailListener to handle additional special characters in the email ID
Resolved in Pega Version 8.1.6
When the Email Listener tried to map the properties from the email body and message header to the Pega Default out-of-the-box properties or user provided text properties, the mapping worked for simple alphanumeric email IDs, but mapped only the trailing part of the address if the Email ID contained an apostrophe or single quotes. For example, "toast.'[email protected]" was mapped as "[email protected]". This was due to a missed special character in the regex pattern, and UtilsEmailListener.java has been updated to correctly handle special characters in the email address as specified in RFC 5322.