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.

INC-152776 · Issue 621244

Check added for HTML and linefeed combined in email

Resolved in Pega Version 8.5.3

In the Interaction right hand pane Email triage widget, additional line breaks were seen when displaying email message data that contained table tags. This was a missed use case for email which contains both HTML and '\n', which resulted in the system replacing '\n' with </br>. This has been resolved by adding a check whether the content has HTML tags which will avoid the replacement.

INC-156422 · Issue 617382

Updated email triage case creation to avoid unique key issue

Resolved in Pega Version 8.5.3

After upgrade, when the email listener queued the case and an agent picked up the queued item to create an Email Triage Case and then the interaction case, trying to commit the case failed with a Unique Key violation. Investigation traced this to the system trying to insert the record into the PC_WORK_TRIAGE table twice due to a timing issue in the workobject commit. This has been resolved.

INC-143036 · Issue 599190

SurveyPage loads when ruleset is locked

Resolved in Pega Version 8.5.3

When the ruleset containing the survey rules was locked D_pzSurveyPage did not load and errors were generated. Investigation showed that if the flow was in a locked version, the PopulateShapeNodesFromFlowData activity did not call EvaluateConnectorState, causing the mapping of the transitions for connectors to fail in the activity MapBranchShapeConnectors. This has been resolved.

INC-148392 · Issue 610670

File type handling added for cloud downloads on mobile app

Resolved in Pega Version 8.5.3

When using the Pega cloud storage repository (Application -> Integration -> Content Storage) with the mobile app, it was possible to upload attachments but re-downloading the attachments failed. Investigation showed that this was due to the content-type appearing as application/* so the file type was not able to be identified. This was a missed use-case for returnFileForDownload(), and has been resolved.

INC-150578 · Issue 607477

RTE control handling updated for survey display text

Resolved in Pega Version 8.5.3

After upgrade, Display text in the survey was missing for the question rules which used Rich Text Editor control. This has been resolved by updating the system to copy DisplayText and QuestionText into DisplayTextWrapper.

INC-150762 · Issue 609548

Support added for Android mobile app with _ in AppId

Resolved in Pega Version 8.5.3

Login on Android devices was not working for a non-offline mobile app built with with Pega and PIMC 8.5.204. This was traced to the use of an underscore in the AppID. PIMC launches authentication in a custom tab which is fully isolated from the mobile application; after providing valid credentials, the mobile client gets notified by meta-tag "refresh", which contains a redirect uri with authentication code & state. According to RFC 3986 the scheme should not contain underscore "_" character, so the Google Chrome custom tab was not respecting redirect uris with an underscore. To resolve this, underscore will be allowed in Certificates > Add certificate set, but the system will replace all underscores with hyphens during handling.

INC-151446 · Issue 614448

HTML tags removed for Survey Question tooltips

Resolved in Pega Version 8.5.3

After upgrade from v7.1 to v8.4, question rules with rich text along with styles and answer mode as dropdown were not loading in the survey UI and the error " Exception Occurred in Rule-HTML-Section for question QuestionName" was generated. This was traced to the use of HTML tags in the "pytooltip" property. To resolve this, HTML tags will be removed using a regex and the property will be correctly handled from there.

INC-151998 · Issue 616320

Handling added for comma value in FusionCharts XML

Resolved in Pega Version 8.5.3

After creating a Summary Report through the report browser and adding that report to the Dashboard, clicking on the report to drill down generated the error "Can't open the rule with the specified keys". Investigation showed that if a category or series in a Report Definition chart contained a comma, the drilldown would not work because of an incorrect pyclassname being passed. This was traced to the use of XML to configure the chart: the FusionCharts third-party library parses the link XML incorrectly and splits JS arguments at any comma. This was a missed use case for having a comma in the name, and has been resolved by adding encoding for the comma value in pzMultiSeriesData FusionCharts XML rule. Then this will be decoded in the drilldown JS APIs pzPega_chart_legacydrilldown and pega_report_summary.

INC-153133 · Issue 612728

Updated encryption and decryption handling for non-auto control

Resolved in Pega Version 8.5.3

After encrypting the pyMessage from PegaSocial-Message, the message was displayed in Pulse in the encrypted form. This was caused by a difference in handling between auto and non-auto controls, where the decryption was only handled automatically in the auto controls. To resolve this, explicit encryption and decryption handling has been added to the non-auto control.

INC-153423 · Issue 615667

Timing update for Signature Capture Control

Resolved in Pega Version 8.5.3

A signature could be lost when using the signature capture control if a signature was drawn then the Accept and Submit links were clicked in quick succession. The problem occurred more frequently (although was not limited to) when there were multiple signature capture controls on the screen. This issue was due to transaction mismatch error for few pzAttachSignatureWrapper requests (signature post requests) caused by triggering the next accept request before completing the previous accept request. To resolve this, an update has been made to display busy indicator immediately when the first accept button is clicked.

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