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-A33 · Issue 206096

Addressed XML attachment corruption

Resolved in Pega Version 7.1.9

A document file response generated by Connect-REST and attached to the work object was becoming corrupted if it was content type XML. This was an issue with the code converting the doc data to string, and invokerestconnector has been updated to handle this use case.

SR-A3869 · Issue 209484

Corrected REST logic for missing/blank query parameters

Resolved in Pega Version 7.1.9

When running a REST connector with a resource path that contained multiple parameterized areas of the query string where the value of the first and/or last query string parameters were blank or missing, the request URL was missing the query string parts that have an equals sign delimiter but a blank/empty value. This was unexpected behavior traced to a change in the generation logic, and the system has been modified to produce the expected behavior of query parameters with blank values appearing as "val1=" instead of not appearing or missing the equals sign.

SR-A3869 · Issue 210205

Corrected REST logic for missing/blank query parameters

Resolved in Pega Version 7.1.9

When running a REST connector with a resource path that contained multiple parameterized areas of the query string where the value of the first and/or last query string parameters were blank or missing, the request URL was missing the query string parts that have an equals sign delimiter but a blank/empty value. This was unexpected behavior traced to a change in the generation logic, and the system has been modified to produce the expected behavior of query parameters with blank values appearing as "val1=" instead of not appearing or missing the equals sign.

SR-A3992 · Issue 211563

WSDL generation updated

Resolved in Pega Version 7.1.9

A coding error for the constants used in generating WSDL was creating a problem for some installations with the resulting data. This has been corrected.

SR-A4918 · Issue 211744

Reverted WSDL naming convention to previous style

Resolved in Pega Version 7.1.9

In earlier versions of the system, the exposed Pega-generated WSDL had ComplexType named "CreateCaseWSRequestType" with uppercase "T". A recent change to naming the ComplexType "CreateCaseWSRequesttype" with lowercase "t" required a manual override to use previously generated WSDLs after upgrading, so the naming has been reverted to using the uppercase "T" format.

SR-A5413 · Issue 212956

Null check added to ParseXMLSAXRuleWrapper

Resolved in Pega Version 7.1.9

Thread lock error messages were being generated in the clipboard when trying to access a property pyNote whose value has been initialized with XML content. This was traced to ParseXMLSAXRuleWrapper adding a null value to the Clipboard Value list, and a null check has been added to prevent this.

SR-A959 · Issue 205668

Enhanced locking for EmailListener to detect and process auto-reply

Resolved in Pega Version 7.1.9

Due to thread locking timing, the EmailListener was not detecting 'autoreply' emails, causing infinite loops. This has been fixed by adding code to look for DSS Email/AutoReplySubject. If present, it will lock the requestor before getting the custom AutoReply setting and processing as expected.

SR-D16427 · Issue 497220

Multi-nodes rebuild LibraryMetadata to ensure all Rule-Utility-Functions are present on change

Resolved in Pega Version 8.3.1

When performing a complete Application import into a clean installation, references to certain Rule-Utility-Functions went unresolved during the initial assembly. Investigation showed that after introducing a new Rule-Utility-Library or Rule-Utility-Function on one node in a cluster and then generating that, the other nodes in the cluster did not have the correct LibraryMetaDataCache for that Rule-Utility-Library. Therefore assemblies on those other nodes could be bad and throw a runtime UnresolvedAssemblyError. This has been resolved by modifying the way the Library subsystem processes the node changes events for Library Generation to ensure that each node completely rebuilds the LibraryMetadata for that Rule-Utility-Library so it contains all the Rule-Utility-Functions.

SR-D32441 · Issue 502572

Multi-nodes rebuild LibraryMetadata to ensure all Rule-Utility-Functions are present on change

Resolved in Pega Version 8.3.1

When performing a complete Application import into a clean installation, references to certain Rule-Utility-Functions went unresolved during the initial assembly. Investigation showed that after introducing a new Rule-Utility-Library or Rule-Utility-Function on one node in a cluster and then generating that, the other nodes in the cluster did not have the correct LibraryMetaDataCache for that Rule-Utility-Library. Therefore assemblies on those other nodes could be bad and throw a runtime UnresolvedAssemblyError. This has been resolved by modifying the way the Library subsystem processes the node changes events for Library Generation to ensure that each node completely rebuilds the LibraryMetadata for that Rule-Utility-Library so it contains all the Rule-Utility-Functions.

SR-D22113 · Issue 498312

Multi-nodes rebuild LibraryMetadata to ensure all Rule-Utility-Functions are present on change

Resolved in Pega Version 8.3.1

When performing a complete Application import into a clean installation, references to certain Rule-Utility-Functions went unresolved during the initial assembly. Investigation showed that after introducing a new Rule-Utility-Library or Rule-Utility-Function on one node in a cluster and then generating that, the other nodes in the cluster did not have the correct LibraryMetaDataCache for that Rule-Utility-Library. Therefore assemblies on those other nodes could be bad and throw a runtime UnresolvedAssemblyError. This has been resolved by modifying the way the Library subsystem processes the node changes events for Library Generation to ensure that each node completely rebuilds the LibraryMetadata for that Rule-Utility-Library so it contains all the Rule-Utility-Functions.

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