SR-D19639 · Issue 489966
Rule Security Analyzer failure corrected
Resolved in Pega Version 8.2.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-D19081 · Issue 490369
Logic updated to handle Report Definition with a join
Resolved in Pega Version 8.2.3
When using a multi-select element on the UI with a report definition as a data source where the report used a join to another class where it was referenced by a prefix, setting that data source property as prefix.property resulted in the multi-select no longer showing any results when tested on the UI although the report definition returned results when run manually. This was traced to platform differences revealed by an upgrade, and the idGenerator function has been updated to handle a report definition with a join to resolve this.
SR-D18741 · Issue 490419
GRS support added to Display name and Reply to for SendEmailNotification
Resolved in Pega Version 8.2.3
After upgrade, it was not possible to send email notifications when using a Datapage property in the email account rule. Investigation showed that there was a custom activity being used to call the SendEmailNotification activity and set the pyNotifyAccountName value as email account name by enabling Pass current parameter page, and the custom call was not functioning due to the SendEmailNotification activity being completely refactored in recent versions of the platform where GRS support (which was not a documented feature) was removed. For better backwards compatibility, this issue has been resolved by adding GRS support to Display name (pyFromFullName) and Reply to (pyReplyTo).
SR-D22594 · Issue 490653
Fallback handling added for Cryptographic exceptions
Resolved in Pega Version 8.2.3
Cryptographic Exceptions were being generated while decrypting query parameters. This occurred when a node restart happened before passivation time out: the existing encryption keys are lost and new encryption keys are generated on node restart, resulting in any requests encrypted with previous keys (before node restart) to fail decryption. This issue did not occur when a requestor was passivated or nodes were quiesced, only when a node was abruptly shutdown. To resolved this, handling has been added which will fallback and decrypt with an older key if an exception is encountered when decrypting with the current key.
SR-D20150 · Issue 491081
Added when check for Strategy and Event Strategy to preserve pagelist property
Resolved in Pega Version 8.2.3
When editing a test case that has been built from a strategy, clicking on the 'add properties' link in the side panel was not working. This was traced to the strategy rule being loaded each time while the data page is only loaded once per session, and has been resolved by adding a 'when' condition to the Strategy and Event Strategy rule that will check for the existence of an embedded page before the pagelist property which displays results is removed.
SR-D20144 · Issue 492520
Function LengthOfPageList resolves correctly for Insure framework
Resolved in Pega Version 8.2.3
When using the Insure framework, it was not possible to expand any steps in the activity. Investigation showed that the rule 'LengthOfPageList' was present in the library Utilities in two different rulesets – Pega Rules and Pega Insure CSB. When the rule was cached with an application stack containing Pega Insure CSB, it generated a "Failed to find instance" error for applications that did not use Pega Insure CSB in the stack. During the run-time call to the correct LengthOfPageList() RUF was not resolved because of ambiguity in the resolution. To correct this, the call to the RUF will now contain a fully qualified name.
SR-D22437 · Issue 492856
Handling added for Pagelist Reference Property in LegacyPageAdapter getMode API
Resolved in Pega Version 8.2.3
Post upgrade, a "Component Stack Mismatch" error appeared while opening a work item containing an embedded section that used a Data Page D_WorkApprovalCase input parameter as the Page Context. This was traced to an exception thrown by the getMode() API invoked on an auto-populate property because the property was in a read-only data page. By default, read-only data pages are light weight clipboard pages, but auto-populating properties on light weight clipboard pages was not handled via the failsafe page in the getMode() API. This has been fixed by adding handling to the getMode API of LegacyPageAdapter for properties not supported by redux ( eg: reference, autopopulate properties etc).
SR-D22175 · Issue 493193
Null check added to control_multiselect
Resolved in Pega Version 8.2.3
After upgrade, Multiselect control was not working in some classes. The values were getting loaded into the clipboard, but on clicking the down arrow none of the values were getting populated. This has been resolved with the addition of a null check in the control_multiselect file.
SR-D22858 · Issue 493329
Checks added for case resolution based on dependencies
Resolved in Pega Version 8.2.3
Post upgrade, using a design with a wait shape configured to resolve the Parent case when all the child cases were Resolved-Completed was not working. This was traced to the handling of the page dependencies in TopCaseWork, and checks have been added to ensure correct case resolution.
SR-D23611 · Issue 493422
Autocomplete dropdown scrolls with screen rather than remaining fixed
Resolved in Pega Version 8.2.3
On selecting dropdowns(autocomplete), if the dropdown list was left open and the screen was scrolled, the dropdown list did not move with the scroll but rather remained fixed to the screen. This has been resolved with the addition of scroll handlers which will attach the popover results to its parent while scrolling.