SR-A69786 · Issue 251702
EmailService CC parameter correctly mapped
Resolved in Pega Version 7.2.2
After upgrade, the inbound email processing was not capturing the Email Service request parameter "CC " in the service page. This was due to an unwanted space in the CC field name mapping which has now been removed.
SR-A20058 · Issue 250683
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
Fixed default node values error in XML
Resolved in Pega Version 7.2.2
An issue was found where a default value set for node elements was not overriding the optional checkbox and blank tags were being created in the XML page. This has been fixed.
SR-A64734 · Issue 251922
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-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 that are received without the expected URL encoding.
SR-A76475 · Issue 255252
SOAP Service generates nillable attribute in WSDL
Resolved in Pega Version 7.2.2
Attempting to generate WSDL with the Nillable attribute was not working as expected. This was due to an error in referring to the property name to fetch the nillable checkbox value in XMLTreeViewUtils.java and has been fixed.
SR-A22374 · Issue 247987
Node.isUsable() has been updated to return more accurate startup status
Resolved in Pega Version 7.2.2
Previously, Node.isUsable only checked whether the node is initialized or not. This created the possibility that if an Agent was started late in the engine start-up, node.isUsable() could return true while the agent was still null. In order to retain backward compatibility, a new API isStarted() has been added to the system to determine whether the server is completely up or not.
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.