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-A85804 · Issue 255413

Support added for Word2016 with macro templates

Resolved in Pega Version 7.2.2

After creating a document in Word 2016 based on a Pega macro as the template, saving the document and closing it would lead Word to crash the next time the document was reopened. This was traced to a file conflict between in Word2016 and the macro file, and has been resolved by updating the Office2010 version WordMerge macro file to enable the support of Word2016.

SR-A89074 · Issue 258503

Resolved upgrade issues with ConnectSOAP using MTOM

Resolved in Pega Version 7.2.2

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" . Analysis showed the base64binary was not being substituted correctly with the expected "XOP Include" element. Axis uses Axiom to write Multipart messages and multiple XOP writers are involved in writing and encoding the message. When the writer stream is flushed , it depends on SimpleNsStreamWriter to write the bytes. SimpleNsStreamWriter is currently packaged as part of WStx-2.3-asl.jar and webservices-rt.jar, but this was not true in previous versions. As a result after upgrade, Webservices-rt classes is taking precedence over wstx-asl classes, which was generating the XOP:include elements with inline content. For better backwards compatibility, the WS-TX jar references have been removed from the webservices-rt.jar so that now it will rely on wstx-asl-3.2.3.jar which is already shipped with the product.

SR-A20058 · Issue 257774

PEGA0020 alert updated for full interaction time

Resolved in Pega Version 7.2.2

An error with PAL timer statements caused an Null Pointer Error during connect SOAP execution due to socket read time not being accounted for in the PEGA0020 alert. This has been fixed.

SR-A22183 · Issue 249190

Elements given correct default value in XML

Resolved in Pega Version 7.2.2

An issue was found where blank tags were being created for node elements given a default value in the XML Stream rule. Analysis showed that when the optional element in the XML Stream rule was set with "" and had a default value, the "StreamXML/DetectEmptyProperties" empty string was getting displayed in the output XML instead of default value. This has been fixed.

SR-A95474 · Issue 262004

HTML email rendering fixed for mobile

Resolved in Pega Version 7.2.2

An issue was found with the rendering of HTML type emails sent out from the platform and viewed on mobile devices. This was traced to a missing DOCTYPE tag, and has now been fixed.

SR-A94119 · Issue 260854

Attachment names preserved for ECM docs

Resolved in Pega Version 7.2.2

Attachment names were being corrupted with the loss of all extensions from ECM Documents. A check has been added to ensure proper handling.

SR-A64734 · Issue 252332

OpenSAML decoder updated to allow Okta implementation

Resolved in Pega Version 7.2.2

Attempting to configure Okta was generating exceptions due to decoding issues with the XML. In order to better support this third-party program, flexibility has been added to handle IPD responses received without the expected URL encoding.

SR-A101242 · Issue 270252

STS Policy parsing fixed for Apache Rampart

Resolved in Pega Version 7.2.2

Changes to the Apache Rampart code in Pega 7 introduced an error with parsing the the Web-Service-Policy with a PRCustom activity that writes the SAML token to the requestor during login with an STS / SSO context. This has been rectified by creating an object of com.pega.apache.ws.secpolicy.model.HttpsToken class and setting values based on the parameters set in the received policy assertion.

SR-A102018 · Issue 270086

Creating REST integration works from JSON file

Resolved in Pega Version 7.2.2

Creating REST integration from JSON file was failing due to the same name attribute 'agent' in the JSON having different modes - page and string. Code to perform a rename in case of conflicts was already present, but in the given case (JSON file) properties were created in descending order but saved in ascending order and the error occurred. To resolve this issue, the conflicting properties will be renamed when created such that the order of creation does not affect the creation of the properties.

SR-A22374 · Issue 247987

File Listener waits for PRPC node usability

Resolved in Pega Version 7.2.2

During server start up, it was noticed that the file listener started processing files waiting in the target directory before the agent was instantiated. This caused an Null Pointer Error. The file listener has now been modified to process the files only if the PRPC node is usable.

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