SR-D14005 · Issue 487790
Bteer filtering added for Duplicate schema names in schema tools
Resolved in Pega Version 8.2.3
The database list drop down was showing duplicate database names. This was traced to Connection Manager managing Data Base configuration differently for corresponding Read Only, Admin and Standard, and not providing the unique database names. This has been resolved by adding support for filtering duplicate names from getDatabaseNames.
SR-D17056 · Issue 488084
Error messaging updated for using Float parameter in RUF
Resolved in Pega Version 8.2.3
After upgrade, using an RUF that had a float as an input parameter as part of its signature resulted in any callers providing a double type as an input generating an exception. This has been resolved by forcing a NumberFormatException to be thrown within the IL model when encountering a float value ('1.2f' or '1.2F') as the Double.valueOf() API used in IL correctly parses these values to double.
SR-D15495 · Issue 489735
Function in aggregate filter condition properly displayed
Resolved in Pega Version 8.2.3
After constructing a report definition with Filter conditions to apply after the aggregation filters with max as function, the function was not visible in the dropdown when the rule was opened. The Function was visible if the rule was checked out and remained visible if the checkout was discarded, but if the rule was opened and closed again the max function was not visible. This was traced to the Primary page not being considered properly while populating the data page D_pzGethavingFilterFunctions which loads the options for the filter dropdown. To resolve this, the activity pzHavingFilterFunctions has been modified to check for pzPrimaryHarnessPageName first before pzPrimaryPageName.
SR-D17575 · Issue 489952
Survey route to work queue optionrestored smartshape
Resolved in Pega Version 8.2.3
After upgrade, routing to workqueue was no longer available for the new create survey smart shape. This has been restored.
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.