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.

SR-B36260 · Issue 296921

Fixed mobile native control submit clearing property/date

Resolved in Pega Version 7.3

When the "native control on mobile" option is checked for a date-time property, a runtime error on submit cleared the property value/date value. To correct this, if the datetime property gets any error messages on submitting the screen, the response of the datetime control will not generate the Value or overwrite it.

SR-B36431 · Issue 293350

SOAP simulations restored

Resolved in Pega Version 7.3

SOAP simulations were not executed as expected due to the hard coded value SOAP being removed and made generic. This has been fixed by updating the service type to SOAP in the parameters passed to the simulations section.

SR-B3657 · Issue 274527

SAML authentication enhanced to detect encoded/decoded response

Resolved in Pega Version 7.3

Even though SAML authentication was working as expected, an error message was being logged when the system attempted to process the authentication response as encoded before falling back to process it as decoded. To remove confusion, Fallback has been removed and instead the system will intelligently identify the response as encoded/decoded and handle it appropriately without generating an unnecessary error.

SR-B3657 · Issue 280763

SAML authentication enhanced to detect encoded/decoded response

Resolved in Pega Version 7.3

Even though SAML authentication was working as expected, an error message was being logged when the system attempted to process the authentication response as encoded before falling back to process it as decoded. To remove confusion, Fallback has been removed and instead the system will intelligently identify the response as encoded/decoded and handle it appropriately without generating an unnecessary error.

SR-B3657 · Issue 285983

SAML authentication enhanced to detect encoded/decoded response

Resolved in Pega Version 7.3

Even though SAML authentication was working as expected, an error message was being logged when the system attempted to process the authentication response as encoded before falling back to process it as decoded. To remove confusion, Fallback has been removed and instead the system will intelligently identify the response as encoded/decoded and handle it appropriately without generating an unnecessary error.

SR-B36909 · Issue 301697

JSON API added

Resolved in Pega Version 7.3

An enhancement has been added via an API to create JSON from clipboard page. This API will get the JSON of the clipboard page, expand Autopopulate Properties, and return Dates and Times in ISO format.

SR-B37301 · Issue 295750

Repaired REST Connections with proxy

Resolved in Pega Version 7.3

After upgrade, connections to external internet websites/services were failing when using a proxy. This has been fixed.

SR-B37351 · Issue 296014

FTP connection test loads authentication profile

Resolved in Pega Version 7.3

The FTP Server Test connectivity button was not working if the server did not allow anonymous connections. This was due to tests not loading the Authentication Profile, and the system has been updated to load the profile during the connection build process.

SR-B37819 · Issue 296299

SAML SessionInfo cleanup enhanced

Resolved in Pega Version 7.3

The following SAML issues have been corrected: 1) when IDP logout URL was empty, SAMLSingleLogOff activity generated an exception; 2) the SAML Session info record was not deleted during logout process even when given a valid IDP logout URL; 3) the SAML session info record was not deleted for both SP and IDP initiated logouts.

SR-B37988 · Issue 298759

Fixed Addressing checkbox error in Connect-SOAP

Resolved in Pega Version 7.3

The addressing checkbox on the SOAP connector rule form was not being honored. This was a defect in the third party library 'praxis2-1.6.2-1.jar', and code has been added to disable the processing of WebSphere addressing headers when WebSphere addressing is false.

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