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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

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.

INC-137874 · Issue 599131

Cross-site scripting update for Dev Studio

Resolved in Pega Version 8.4.4

Cross Site Scripting (XSS) protections have been added to Developer Studio.

INC-140224 · Issue 604006

Corrected SAML SSO error

Resolved in Pega Version 8.4.4

After opening a case from the Pega-FCM portal or after logging in from SSO, closing the Pega window and opening it again resulted in the error "Unable to process the SAML WebSSO request : Violation of PRIMARY KEY constraint %27pr_data_saml_requestor_PK%27. Cannot insert duplicate key in object". This was a missed use case that happens only under the old SAML configuration, and has been resolved by removing a when condition that checks for stepstatus fail for the pySAMLwebSSOAuthentication activity.

INC-141595 · Issue 602715

CSRF and Browser fingerprint tokens added for testing custom scripts

Resolved in Pega Version 8.4.4

After upgrade, the test window appeared blank when attempting to test Decision Table rules. This was traced to there not being CSRF token and Browser fingerprint handling in the custom script used to show a prompt screen to the user. Because the CSRF token validation was missing, the request failed. To resolve this, CSRF and Browser fingerprint tokens have been added as hidden fields.

INC-141940 · Issue 601543

Revoke Access Token check removed from OAuth Client Registration

Resolved in Pega Version 8.4.4

When client credentials were implemented, the OAuth 2.0 Client Registration form was designed such that once the instance was created and a token issued, the access tokens were deleted on save. Process changes now indicate that it should be possible to save the form because it may only have History Description/Usage changes made to it and Revoke Token and Regenerate Secret buttons are already available. To address this, the Revoke Access Token check has been removed from the validate activity of Client Registration.

INC-144591 · Issue 601611

Oauth and beanutils jars upgraded

Resolved in Pega Version 8.4.4

The third party Oauth2 jars and commons-beanutils jar have been updated to the latest versions.

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