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-A19705 · Issue 246975

Hash table logic fixed for invokeMQConnector

Resolved in Pega Version 7.2.1

Logic issues were found and fixed related to hashtable usage for invokeMQConnector.

SR-A19858 · Issue 236943

Dialogue handling updated for WS-Security Profile password

Resolved in Pega Version 7.2.1

The presentation format for the password field of the WS-Security Profile outflow page has been changed to no longer display the password in the clear in any resulting dialogue.

SR-A19871 · Issue 237975

MS Transport supports Global Resource Settings

Resolved in Pega Version 7.2.1

Documentation indicated that the JMS Transport data instance supported GRS syntax, but attempting to do so generated an error. That support is now available as indicated.

SR-A19972 · Issue 238961

Expanded search re-indexing submit methods

Resolved in Pega Version 7.2.1

When creating an index in the 7 series, the Search Landing Page for indexing did not indicate that the page needed to be submitted to enable the indexes before attempting to start the re-indexing process. An error was thrown in the tracer, but nothing was displayed on-screen to indicate why the system hadn't started indexing. To ensure the expected results, the indexing will begin after the "Submit" button is clicked or if the enable indexing check box has been checked to indicate the system has permission to start indexing without having an explicit submit.

SR-A19986 · Issue 242898

getAppHashForApplication API updated

Resolved in Pega Version 7.2.1

When logged in from an end user portal, editing a decision table and clicking on the gear icon to add a function would show the Function's headers (Example, Activity, string, etc.), but the functions list would not be loaded. This was traced to a timeout resulting from having numerous functions running on the portal combined with a configuration that returned an unowned AppHash when calling a ruleset from the production layer rather than the application layer, and has been resolved by adding logic to write out the AppHash when the appInfo is created from opening the application.

SR-A20048 · Issue 237600

Error message for BIX DDL schema updated

Resolved in Pega Version 7.2.1

Attempting to create BIX DDL through the Designer Studio led to the error message 'No Instance found in the database' when an invalid schema path was used. This error message has been modified to more specifically identify the problem to assist in troubleshooting.

SR-A20058 · Issue 238045

PEGA0020 alert updated to include socket read time

Resolved in Pega Version 7.2.1

Socket read time was not unaccounted for in the PEGA0020 alert. Changes have been made to the invokeaxis2 activity to update the timer to include time related to reading the SOAP envelope.

SR-A20147 · Issue 238046

Caching added to improve login speed

Resolved in Pega Version 7.2.1

In order to improve login performance, caching has been added for the following classes accessed from the database on every login: DATA-ADMIN-SECURITY-AUTHSERVICE DATA-BROADCAST DATA-ADMIN-SECURITY-KEYSTORE

SR-A20504 · Issue 241375

Queue type validation updated in MDBListener

Resolved in Pega Version 7.2.1

Queue type validation failed when testing connectivity in MDBListener if the pyResourceName was set with queue name and there was no pyResQueueName defined in the page. To handle this, the getString function will use the pyResourceName instead of pyResQueueName.

SR-A20603 · Issue 241334

Post-upgrade Connect-SOAP multi-ref mapping fixed

Resolved in Pega Version 7.2.1

After upgrade, the Connect-SOAP responses including multi-refs were not getting mapped correctly and there were problems viewing the response message from the SOAP service. This has been fixed.

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