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.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

INC-151446 · Issue 614446

#resolvedissues note:HTML tags removed for Survey Question tooltips

Resolved in Pega Version 8.4.4

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 616319

Offline mobile RDL attach updated

Resolved in Pega Version 8.4.4

It was not possible to attach any file using the attach content control while the mobile app was configured as offline and property reference was used for the file name in the attachment control. No issues were seen if a static file name was used. This has been resolved by updating the RDL Attach content handling.

INC-152217 · Issue 613928

Activity updated for Mobile attachment access

Resolved in Pega Version 8.4.4

Preview and download were not working for attachments stored in Pega Cloud Storage repository for mobile devices. Attempting to open an email attachment to preview or download resulted in a console error and the tracer showed the message 'Class pxLinkedRefTo does not exist'. This has been resolved by updating "pzpega_control_attachutil" to use the activity "GetAttachmentReference" for interactions with the attachments from any storage type.

INC-153133 · Issue 612727

Updated encryption and decryption handling for non-auto control

Resolved in Pega Version 8.4.4

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 615666

Timing update for Signature Capture Control

Resolved in Pega Version 8.4.4

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.

INC-154290 · Issue 613471

Signature capture exception resolved

Resolved in Pega Version 8.4.4

The signature capture control was throwing a JSON parse exception when the value was set and section was refreshed. This was caused by the signature for PIMC passing incorrect data which Preview could not parse, and has been resolved by ensuring the correct data for PIMC local store.

INC-154495 · Issue 613700

Null check added to DT set action

Resolved in Pega Version 8.4.4

Attempting to open row item details in a repeating dynamic layout in which a data transform was called on click action resulted in the error "Failed to run data transform error ". This has been resolved by adding a null check in Set action.

INC-155214 · Issue 617007

GetBinaryFilesRef updated for resolving wildcard

Resolved in Pega Version 8.4.4

After upgrading from 8.2 to 8.4, errors related to "Unable to serve file java.lang.IllegalArgumentException: Illegal characters detected in the path" appeared numerous times during full syncs, either on first time login or after cache clear. This was traced to normalizeRelativePath failing, and was caused by a resource declaration in pzGetBinaryFilesRef that encountered an issue where wilcarded URLs were not automatically resolved while packaging Static resources. This has been resolved.

INC-155971 · Issue 616031

Handling added for missing data transform in offline mode

Resolved in Pega Version 8.4.4

A "data synchronization failed" error appeared when trying to login to a Mobile App that had offline mode enabled. The login worked when offline mode was not enabled. Investigation showed that when the pyDataTransformWhitelistForOffline application rule contained an entry for a data transform that did not exist, DataTransformPackager.canProcess() was throwing a null pointer error trying to access it. This has been resolved by adding a null check.

INC-156211 · Issue 620192

Verbose comments removed from wrapper

Resolved in Pega Version 8.4.4

Comments with references to external links have been removed from some harness wrappers.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us