SR-A22547 · Issue 252633
Cookie handling added to CMIS
Resolved in Pega Version 7.2.2
Support has been added to use cookies with CMIS to allow connecting to FileNet via connect-cmis.
SR-A24408 · Issue 248682
Page clearing added for AuthReqContex
Resolved in Pega Version 7.2.2
The page "AuthReqContex" was loaded up during SAML authentication and then passivated, but the pages were retained in the clipboard and improperly activated by an unknown thread, causing an error. This has been resolved by adding Page-Remove steps wherever needed in auth activity and logout activity (AuthReqContext, LoginInfo, ReqInfo, RelayStateInfo, and SessionInfo) to remove the pages that are no longer needed.
SR-A22699 · Issue 248560
RuleServiceFile.parseRecordAtTime and RuleServiceFile.parseByRecordType Timer function corrected
Resolved in Pega Version 7.2.2
The Timer function used in the RuleServiceFile.parseRecordAtTime and RuleServiceFile.parseByRecordType functions was not properly halting when it encountered an exception, causing any subsequent invocation to these methods to start the Timer again. This created errors and incorrect results. The parseRecordAtTime and parseByRecordType methods have now been updated to enclose inbound mapping related stopTiming within a finally block for accuracy.
SR-A87711 · Issue 255629
REST query key maps invalid characters to underscore
Resolved in Pega Version 7.2.2
When creating a REST Service with query key=value pairs that contains keys with dots/periods, the inbound mapping could not handle the keys and failed with an HTTP 500 error. To resolve this, changes have been made in the service API to locate any invalid character (according to ParameterPages) in a key to be mapped and substitute an '_' (underscore) character.
SR-A76677 · Issue 253493
IDP SAML 2.0 schema validation error resolved
Resolved in Pega Version 7.2.2
When generating the Pega SP metadata after importing the Shibboleth IDP metadata, the error "The metadata does not pass the SAML 2.0 schema validation" appeared. This has been resolved by modifying the pzDownloadSPMetadata activity to generate a unique secure random ID prefixed with an underscore.
SR-A99521 · Issue 266569
Localization added to DisplayStages
Resolved in Pega Version 7.2.2
Localization has been added to 'Show all steps' and 'Hide Steps' in pxDisplayStages.
SR-A75956 · Issue 250547
D_OfflineWorkIDs DP performance improvements
Resolved in Pega Version 7.2.2
The logic of D_OfflineWorkIDs DP has been updated to improve performance for the SA PROD App.
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.