SR-A101808 · Issue 269472
WebSphere deployment documentation updated to clarify JVM configuration advice
Resolved in Pega Version 7.2.2
The deployment guides for WebSphere have been updated to clearly distinguish between Oracle and IBM JVM when providing JVM configuration advice.
SR-A24989 · Issue 248910
WebSphere deployment guide updated to clarify scope settings
Resolved in Pega Version 7.2.2
The WebSphere Deployment Guide has been updated to indicate that the scope must be "server". If this is not set correctly in a split schema installation, the defaultSchema namespace bindings are defined at the cell level and will not be picked up at start, and the database user in the jdbc/PegaRULES datasource will not have the necessary privileges to run the system. Please see WAS deployment guides on the PDN for further information.
SR-A75998 · Issue 253191
Improved SOAP envelope cache for WSA/WSSE use
Resolved in Pega Version 7.2.2
After configuring and successfully using Connect-SOAP to a non-secure Endpoint, enabling WSA and WSSE for the connect-SOAP configuration and then disabling it again generated the error "Caused by: com.pega.apache.axis2.AxisFault: A required header representing a Message Addressing Property is not present". This was due to the way the SOAP envelope was being cached and the code has been updated to correctly reflect the desired header processing.
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.