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.

SR-B38330 · Issue 297411

Added code to ensure cursor closes on null-pointer exception

Resolved in Pega Version 7.3

Open cursor issues were occurring with out-of-the-box queries.SPPR_SYS_RESERVEQUEUEITEM_B Stored Proc when an exception was raised. Code has been added to ensure the cursor is closed in this situation.

SR-B38339 · Issue 302549

Commented out unnecessary external link from jsonscript.js

Resolved in Pega Version 7.3

During a vulnerability scan it was noted that jsonscript.js contained a link to external site. This was a link to a library in the public domain that is not necessary for the script to function, and it has been commented out.

SR-B38472 · Issue 296794

Repaired Connect SOAP with MTOM enabled

Resolved in Pega Version 7.3

After upgrading, Connect SOAP request messages were failing on the back end server with the error "xop 3.2.2.a: xop:Include must be the sole child of element". This was caused by the base64binary not being substituted correctly with the expected "XOP Include" element, and has been fixed.

SR-B38472 · Issue 299159

Repaired Connect SOAP with MTOM enabled

Resolved in Pega Version 7.3

After upgrading, Connect SOAP request messages were failing on the back end server with the error "xop 3.2.2.a: xop:Include must be the sole child of element". This was caused by the base64binary not being substituted correctly with the expected "XOP Include" element, and has been fixed.

SR-B38472 · Issue 295746

Repaired Connect SOAP with MTOM enabled

Resolved in Pega Version 7.3

After upgrading, Connect SOAP request messages were failing on the back end server with the error "xop 3.2.2.a: xop:Include must be the sole child of element". This was caused by the base64binary not being substituted correctly with the expected "XOP Include" element, and has been fixed.

SR-B38578 · Issue 295917

Fixed null-pointer exception in external DB extract

Resolved in Pega Version 7.3

When using a class which maps to a table in an external database, running an extract caused a database permission error when trying to access the pr_log table in the PegaRULES database. This exception was caught and logged but then processing continued, resulting in a NullPointerException being thrown. To correct this, the sequence number generator has been modified to use the pr_log table instead of the class on which extract is defined.

SR-B38578 · Issue 272419

Fixed null-pointer exception in external DB extract

Resolved in Pega Version 7.3

When using a class which maps to a table in an external database, running an extract caused a database permission error when trying to access the pr_log table in the PegaRULES database. This exception was caught and logged but then processing continued, resulting in a NullPointerException being thrown. To correct this, the sequence number generator has been modified to use the pr_log table instead of the class on which extract is defined.

SR-B38602 · Issue 296751

Login error message modified for increased security

Resolved in Pega Version 7.3

When an operator was configured to use External authentication and then attempted to login through other servlets, the error message included the operator ID. This could be used maliciously to discover valid IDs on the system, so in order to improve security, the process has been modified to remove the ID from the failure message. If authentication fails, the message "The information you entered was not recognized." will be displayed and the system will log an error message in the PegaRULES log file with the actual message "Error authenticating , : This user must use external authentication."

SR-B38602 · Issue 297290

Login error message modified for increased security

Resolved in Pega Version 7.3

When an operator was configured to use External authentication and then attempted to login through other servlets, the error message included the operator ID. This could be used maliciously to discover valid IDs on the system, so in order to improve security, the process has been modified to remove the ID from the failure message. If authentication fails, the message "The information you entered was not recognized." will be displayed and the system will log an error message in the PegaRULES log file with the actual message "Error authenticating , : This user must use external authentication."

SR-B38619 · Issue 298574

Action item refresh properly triggers

Resolved in Pega Version 7.3

Refresh was not clearing the temporary filters applied on the report definition results if the refresh option was triggered by the actions button. This has been fixed by adding a new java step to pzRunWrapper activity to clear the previously applied filters.

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