Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

SR-D47795 · Issue 524674

Fallback to Pulse notification added for empty incoming account in CallEmailAutomation

Resolved in Pega Version 8.3.2

After upgrade, issues were seen with the sender receiving email notifications for sent messages when alias addresses were used for incoming emails. To resolve this, a fallback mechanism to use a Pulse notification has been added in cases where an incoming email account is not found in the pyCallEmailAutomation activity.

SR-D48246 · Issue 518689

TextAnalyzerClass will be populated during upgrade if not present

Resolved in Pega Version 8.3.2

After upgrading, the email channels were failing to process the emails and the error "Unable to load data page D_pyEntityClassMapping. Required parameters : ClassName cannot be blank" was seen in the tracer log. Analysis showed the email channels were failing to process the emails due to the pzUpgradeVersion property in Data-Channel-Email instances being inconsistent post-upgrade. To resolve this, the system has been updated so if the TextAnalyzerClass or name property is not present in old email channels (created in 7.4), it will populate that property in the upgrade activity with the default classname.

SR-D49782 · Issue 518047

Extension point added for ClearInteraction to support custom interactions

Resolved in Pega Version 8.3.2

In order to support clearing a custom interaction page after clicking the "Reset" button on preview console, an extension point has been added to pyClearInteraction.

SR-D54120 · Issue 541351

Improved handling for attachments not using UTF-8 encoding

Resolved in Pega Version 8.3.2

When an email was received that used a charset encoding other than UTF-8, special characters in the HTML body were not displayed and instead the replacement character was shown. To resolve this, the system will read the encoding from the email rather than use the meta tag, and will add the attachment's HTML encoding information in Data-WorkAttach-File so that the same can be used to process and display the original HTML properly.

SR-D57865 · Issue 520962

Added property check for outbound templated email reply

Resolved in Pega Version 8.3.2

When a template was used for the first time for outbound correspondence, email was generated correctly. If the same template was used as the content for reply, the generated email skipped all styles. This was traced to a missing property check, and has been resolved.

SR-D37115 · Issue 515838

Onclick handler updated to resolve RD UI issue

Resolved in Pega Version 8.3.2

After modifying the function logic in Report Definition, reopening it in the configuration modal dialogue displayed the function multiple times and it was not possible to open/edit the function. This issue was cosmetic and related to the UI representation of functions: the underlying clipboard page had the correct details regarding the custom logic and functioned as expected. Investigation showed the UI error was related to the onclick handler, and this has been resolved so the system correctly removes the onclick handler when required.

SR-D42095 · Issue 516669

Added validation function to 'apply filters' to handle custom filtering

Resolved in Pega Version 8.3.2

A custom filter section with the "Display custom section inline" checkbox checked and required input fields was not firing validation if the input fields were empty. Switching the focus away from the filter section caused validation to appear saying the filter could not be blank, but "Apply filters" (which is missing validation) was still clickable and the report updated. This has been resolved by adding a validateInput function to the "Apply filters" button of the pega_report_events file.

SR-D48173 · Issue 515338

Resolved hang caused by cancelling report calculation

Resolved in Pega Version 8.3.2

When dragging a calculation into the report editor filter area, clicking X on the cancel modal that appeared caused a JavaScript exception to occur. This exception later prevented the ability to click the "done editing" button on the report. This has been resolved by modifying the -- doRefresh API to pass the correct argument to reload the section API.

SR-D48442 · Issue 514045

ExportMode parameter sent to resolve duplicate rows in Export to Excel

Resolved in Pega Version 8.3.2

On performing Export to Excel for a report definition, duplicate rows were being exported for a column which had a TextAreaWithExpandSmall UI Control. Investigation showed that this control was looking for the exportmode parameter, which was not being sent. This parameter is now being sent.

SR-D50787 · Issue 520483

Excel time values will default to server datetime if operator time zone is null

Resolved in Pega Version 8.3.2

After upgrade, a scheduled report that contained a column using pxDateTime that was supposed to use EST instead used GMT when run and exported to Excel. This has been resolved with an update that will default to using the time zone of the server If the time zone of the operator is empty or null.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us