SR-B37351 · Issue 296014
FTP connection test loads authentication profile
Resolved in Pega Version 7.3
The FTP Server Test connectivity button was not working if the server did not allow anonymous connections. This was due to tests not loading the Authentication Profile, and the system has been updated to load the profile during the connection build process.
SR-B37819 · Issue 296299
SAML SessionInfo cleanup enhanced
Resolved in Pega Version 7.3
The following SAML issues have been corrected: 1) when IDP logout URL was empty, SAMLSingleLogOff activity generated an exception; 2) the SAML Session info record was not deleted during logout process even when given a valid IDP logout URL; 3) the SAML session info record was not deleted for both SP and IDP initiated logouts.
SR-B37988 · Issue 298759
Fixed Addressing checkbox error in Connect-SOAP
Resolved in Pega Version 7.3
The addressing checkbox on the SOAP connector rule form was not being honored. This was a defect in the third party library 'praxis2-1.6.2-1.jar', and code has been added to disable the processing of WebSphere addressing headers when WebSphere addressing is false.
SR-B38072 · Issue 297065
null-pointer exception fixed for REST XML samples
Resolved in Pega Version 7.3
The rule generation implementation for XML samples in REST wizard was faulty and throwing a NullPointerException if a resource name was the same as any of the complex node names in the sample XML. This has been fixed.
SR-B38248 · Issue 294657
Rule search works after indexer cancel
Resolved in Pega Version 7.3
If the indexer was canceled from within the engine, the rule search function would not work until node restart. This was an error in the method used to call the cancel API, and has been corrected.
SR-B38472 · Issue 296794
Repaired Connect SOAP with MTOM enabled
Resolved in Pega Version 7.3
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". This was caused by the base64binary not being substituted correctly with the expected "XOP Include" element, and has been fixed.
SR-B38472 · Issue 299159
Repaired Connect SOAP with MTOM enabled
Resolved in Pega Version 7.3
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". This was caused by the base64binary not being substituted correctly with the expected "XOP Include" element, and has been fixed.
SR-B38472 · Issue 295746
Repaired Connect SOAP with MTOM enabled
Resolved in Pega Version 7.3
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". This was caused by the base64binary not being substituted correctly with the expected "XOP Include" element, and has been fixed.
SR-B38649 · Issue 296249
Corrected ClassCastException error on Connect-REST
Resolved in Pega Version 7.3
After a REST Connector was run with the QUEUE Method Parameter, executing the "System-Queue-ExecutionRequest- ProcessQueue" activity resulted in an error. This was traced to the invoke activity of class RULE_CONNECT_REST, and has been fixed.
SR-B38649 · Issue 295456
Corrected ClassCastException error on Connect-REST
Resolved in Pega Version 7.3
After a REST Connector was run with the QUEUE Method Parameter, executing the "System-Queue-ExecutionRequest- ProcessQueue" activity resulted in an error. This was traced to the invoke activity of class RULE_CONNECT_REST, and has been fixed.