SR-D10100 · Issue 463307
Bulk actions filter works properly when additional filters are added
Resolved in Pega Version 8.2.2
The Bulk Actions filter was not working if other filters were used in conjunction with it. Investigation showed that when 'assigned to operator' was given a value, the values were fetched properly. When an additional condition was added, the section 'pyBulkProcessingSearchSection' activity called 'pzDefaultOperators' which then set the 'pyUserIdentifier' value to null, and no results were returned. As the activity already had a step to check if the .pyUsage!="Operator" and only then property-set, pyUserIdentifier = "", the subsequent step to set the pyUserIdentifier = "" and override the previous step has been removed.
SR-D10171 · Issue 482472
Updated UtilsEmailListener to handle additional special characters in the email ID
Resolved in Pega Version 8.2.2
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.
SR-D10281 · Issue 482814
Configuration settings introduced for VBD read/write consistency
Resolved in Pega Version 8.2.2
Exports of VBD data at different consistency levels showed data inconsistency between Cassandra nodes. VBD uses the default DSM consistency level of ONE for its reads and writes, which will not automatically repair data when inconsistency exists. Data inconsistencies can lead to VBD timeouts trying to load partition data. To support VBD read/write integrity, an enhancement has been added to allow configuration of VBD read/write consistency levels by way of the following DSS properties (Owning Ruleset: Pega-DecisionEngine): vbd/readConsistencyLevel and vbd/writeConsistencyLevel. R + W > N where R is the consistency level of read operations, W is the consistency level of write operations, and N is the number of replicas. These will override the default DSM read/write consistency levels (ONE).
SR-D10820 · Issue 482684
RDL checkboxes appear properly in minimized window
Resolved in Pega Version 8.2.2
Checkboxes in RDL were not appearing properly in Microsoft Internet Explorer when the window was minimized if a dynamic layout of type inline quadruple was used. This was traced to the responsive breakpoints of a format overriding the styles for custom checkboxes, and has been resolved by updating the checkbox controls for responsive breakpoints to use a min-width and min-height instead of auto.
SR-D10969 · Issue 477276
Logic for the Materialized/Not Materialized feature updated
Resolved in Pega Version 8.2.2
The Materialized/Not Materialized feature was not working properly. When there was an aggregate dataset entry in the Advance page set to use "No" for materialized, doing "Materialized" in IH Summaries LP on that dataset materialized the dataset and created a duplicate entry in the aggregation config page where one was "No" and one was "Yes'. This has been corrected. It was also observed that after an application changed its name while the access groups remained the same, changing a dataset from "Not Materialized" to "Materialized" worked, but changing from "Materialized" to "Not Materialized" did not. Instead, a warning message was posted at the top of the page indicating the problem. Investigation showed that the pzChangeStatus activity failed because the current application name did not match the application name of the access group set for the aggregation configuration record. To resolve this issue, the logic has been updated to remove the reliance on the application name.
SR-D10970 · Issue 476281
Datasets created from the IH summary component correctly listed as aggregate
Resolved in Pega Version 8.2.2
Attempting to create an aggregate data set from the IH Summary shape did not properly list it as aggregate due to a source dataset error. This has been corrected.
SR-D12530 · Issue 482723
Spinner wheel dom correctly cleared after incomplete case closure
Resolved in Pega Version 8.2.2
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-D1458 · Issue 437894
Property name mapping moved to DSM side to ensure consistent results
Resolved in Pega Version 8.2.2
If a Data Set rule was used to retrieve the records of the Data Class, the property names appeared to be changing randomly in the OperationResult Clipboard Page when the name exceeded 30 characters. This was traced to NativeSQL trimming and hashing any aliases that were longer than 30 characters, and has been resolved by moving the mapping back of property names to the DSM side.
SR-D211 · Issue 481406
Case Assignment issue lock corrected
Resolved in Pega Version 8.2.2
After upgrade, an intermittent error was seen when browsing the screen flows of a child case type application, indicating "Users have lost the ability to make this change because a change elsewhere has taken precedence over the change you made here. Please click on the assignment again to continue". This was traced to a change made to address an issue with the Opener not properly honoring the aUnlockOnCommit flag that was passed in via the openIfStale() API: in a very specific use case following that change, the system would unlock work objects during openIfStale when it should not. This has been corrected.
SR-D2400 · Issue 438740
Security for ExporttoPDF tool process improved
Resolved in Pega Version 8.2.2
In order to increase system security, the tool process around iframe HTML tags used in generating a PDF with chart image data has been improved.