SR-D17694 · Issue 487181
Include Rule in RTE parameters are properly saved
Resolved in Pega Version 8.2.3
After creating a correspondence and including any rule, opening the parameters of the rule, and giving a Using page value before saving, reopening the parameters modal dialog showed the Using page value was null. No actions were performed on the Save button or the input value. Investigation showed that the rule parameters were not getting saved due to an incorrect element selector being used. This was traced to a recent change that modified the use of unique IDs for the selector, and has been resolved by setting the system to use a different selector independent of the ID.
SR-D18209 · Issue 487380
Check added to avoid unnecessary show-harness when offline
Resolved in Pega Version 8.2.3
After upgrade, clicking on the Optional Process from the Action menu resulted in the error "The Operation completed successfully, but returned no content". This was traced to an unnecessary call to a show-harness step when offline, and has been resolved with the addition of a 'when' check.
SR-D16327 · Issue 487447
Updated logic for Bulk Upload count when background processing is used
Resolved in Pega Version 8.2.3
When multiple items were queued as part of "Bulk Upload" and the "Transfer To" operation was used with "BULK PROCESS in BACKGROUND", discrepancies were seen in the email received. For example, if two items were selected for transfer, email notifications stated that 1 item was selected and 1 item was processed instead of 2. This was traced to using 'process in background': when selected during bulk processing, the first record is processed in the foreground and remaining records are processed in the background. When the system sent the email notification once the background process was done, the total records computation was not considering the foreground-processed record, and the count was off. The timing logic has been updated to account for the foreground record to resolve this.
SR-D17122 · Issue 487598
Updated code to resolve PMS variable errors when using the iframe container
Resolved in Pega Version 8.2.3
After building the iOS application using “Reuse web portal” (under channels & interfaces > layout) and with the default settings application, the Dashboard, My Work, and Pulse sections were not rendered and the error "Can't find variable pms" appeared. This happened only when the iframe container was used, as the pms object (PIMC API) is always injected into top window and does not exists in child windows like iframe embedded in a page. In order to ensure that undefined variable pms does not break the rendering, the code has been updated to use top.pms for all pms occurrences to avoid errors when API is invoked from iframe.
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.