SR-C87086 · Issue 425608
Added explicit cleanup of non-serializable objects in the Connect-SOAP ParameterPage
Resolved in Pega Version 8.2.3
An error stating "One or more properties could not be serialized during passivation and have therefore been lost" was traced to a Serialization issue with Connect-SOAP leaving non-serializable objects in the ParameterPage. Code has been added to remove the pxHTTPServletResponse property after use to resolve this.
SR-D8279 · Issue 481606
Error enhancements added to Cases API
Resolved in Pega Version 8.2.3
Enhancements have been made to error handling for the Pega cases API:1) Any error added to an activity called in case creation, for example "ValidateNew", was generating a 500 error and not being returned. This has been modified to return and display a 4XX error along with the error message. 2) 'Put' now has an extension point for validating input and adding errors, and the errors added will be returned. 3) Post for assignments now also has extension points that will fire the validation errors while calling from Rest. If set, the error will be returned by the REST service.
SR-D9142 · Issue 482315
Support added for custom JVC arguments for Cassandra
Resolved in Pega Version 8.2.3
An enhancement has been added to support specifying custom JVM arguments for Cassandra. This allows uses such as enabling GC logging for cloud deployments, or to increase the native transport queue size for read-heavy deployments.
SR-D11980 · Issue 484186
Resolved missing feedback entry update
Resolved in Pega Version 8.2.3
An issue with the Feedback entry not being updated in the manual triage process was traced to a local configuration which loaded the D_pxEmailPosts data page on 'send feedback' instead of upon opening the email triage case (or Interaction case). This difference caused the required ChannelConfig page to be removed from the 'pyCheckIfHtmlOrPlainText' activity so ModelName was not populated for use by pzSendFeedbackToNLP. ModelName is a required property to send feedback. To resolve this, an update has been made to ensure Work-Channel-Triage.pyCheckIfHtmlOrPlainText will not remove the ChannelConfig page.
SR-D6721 · Issue 485209
Updated report widget drilldown logic for better non-ASCII character support
Resolved in Pega Version 8.2.3
When a report in the report widget had a drilldown chart with a parameter containing certain non-ASCII characters, no entries for the drilldown filter were shown even when there was data that matched that filter. This was traced to the drilldown JavaScript for dashboard report widgets encoding the drilldown parameter twice, causing characters that were Unicode but not ASCII to be corrupted. This has been resolved by updating the logic for pzpega_chart_legacydrilldown.js and pzpega_control_actions_reportdefinition.js to ensure the parameter is not encoded twice.
SR-D14189 · Issue 486281
Recent Content updated to accept more than one URL attachment
Resolved in Pega Version 8.2.3
An error was seen when opening Recent Content and attempting to attach more than one URL. Investigation showed that Assign Page was getting cleared after adding the first URL attachment so it did not have a page value available for the second use. The logic has now been modified so the value will not be cleared in the Recent Content gadget preprocessing activity.
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.