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.
SR-A69773 · Issue 249802
Failed SOAP OOM error corrected
Resolved in Pega Version 7.2.2
If a workflow included heavy use of Connect-SOAP operations and the back-end SOAP service was down, the extensive SOAP exceptions were leading to a JVM OOM error. This was due to the cleanupTransport not properly accounting for failed cases, and changes have been made to do an explicit cleanup in the catch block.
SR-A96437 · Issue 265628
Modified declare expression truncation for integration class
Resolved in Pega Version 7.2.2
If the name of the integration class picked by the wizard from the request XML exceeded 64 characters. an error appears. This is expected behavior. However, the error was persistent even after changing the class name, and the issue has been addressed by updating the truncation used by the pyAuthentication declare expression.