SR-D4649 · Issue 440202
Special character handling improved to ensure MTOM binary contains all data
Resolved in Pega Version 8.1.6
The presence of special characters was causing the data to be truncated when moving XOP elements in the SOAP envelope and encoding them into multi-part binary elements (MTOM). This was traced to Connect SOAP With MTOM Option missing some content in the Response data particularly in conjunction with Websphere using a specific JDK version, and has been resolved by modifying the setOptimizeOnChildren method in PRServiceUtilsPriv class to to get all the content.
SR-D3556 · Issue 446513
Requestor.OperatorID page updated to stay in sync with current OperatorID to enable post-Auth activity mapping
Resolved in Pega Version 8.1.6
The systems pages were not getting updated to the right operator's context when a post-Auth activity was used for mapping. To support this use, the UpdateOperatorID trigger has been updated to keep the pxRequestor.OperatorID page in sync with the current operatorID page during SAML. The operator will also be saved during provisioning.
SR-D4304 · Issue 446374
Locale object handling added to SimpleDateFormat
Resolved in Pega Version 8.1.6
Configuring an Authentication Service with signing certificates failed at runtime with a invalid date exception in non-English locales. This has been fixed by passing the locale object as parameter to SimpleDateFormat.
SR-C93873 · Issue 436425
BigDecimal division API updated
Resolved in Pega Version 8.1.6
A difference in strategy output was seen after upgrade due to a particular HFix regarding decimal values in strategy calculations not being previously installed on the system. To resolve this, updates have been made to the BigDecimal division API that specifically addresses Group By shape.
SR-D16829 · Issue 486657
Nodes start as new if replacement start fails
Resolved in Pega Version 8.1.6
Cloud upgrade was failing if there was any attempt to scale up the number of instances. Every node starts up with a flag, and in cases of scale-up scenarios, a new instance with this flag was handled as a replacement instance instead of a new instance. That led the new node to fail because it has nothing to replace. To resolve this, the system has been updated so that if an instance failed to start as a replacement, the process will allow the instance to join the cluster as a new node.
SR-D17741 · Issue 486921
Nodes start as new if replacement start fails
Resolved in Pega Version 8.1.6
Cloud upgrade was failing if there was any attempt to scale up the number of instances. Every node starts up with a flag, and in cases of scale-up scenarios, a new instance with this flag was handled as a replacement instance instead of a new instance. That led the new node to fail because it has nothing to replace. To resolve this, the system has been updated so that if an instance failed to start as a replacement, the process will allow the instance to join the cluster as a new node.
SR-D17743 · Issue 486917
Nodes start as new if replacement start fails
Resolved in Pega Version 8.1.6
Cloud upgrade was failing if there was any attempt to scale up the number of instances. Every node starts up with a flag, and in cases of scale-up scenarios, a new instance with this flag was handled as a replacement instance instead of a new instance. That led the new node to fail because it has nothing to replace. To resolve this, the system has been updated so that if an instance failed to start as a replacement, the process will allow the instance to join the cluster as a new node.
SR-D17770 · Issue 486925
Nodes start as new if replacement start fails
Resolved in Pega Version 8.1.6
Cloud upgrade was failing if there was any attempt to scale up the number of instances. Every node starts up with a flag, and in cases of scale-up scenarios, a new instance with this flag was handled as a replacement instance instead of a new instance. That led the new node to fail because it has nothing to replace. To resolve this, the system has been updated so that if an instance failed to start as a replacement, the process will allow the instance to join the cluster as a new node.
SR-D17774 · Issue 486928
Nodes start as new if replacement start fails
Resolved in Pega Version 8.1.6
Cloud upgrade was failing if there was any attempt to scale up the number of instances. Every node starts up with a flag, and in cases of scale-up scenarios, a new instance with this flag was handled as a replacement instance instead of a new instance. That led the new node to fail because it has nothing to replace. To resolve this, the system has been updated so that if an instance failed to start as a replacement, the process will allow the instance to join the cluster as a new node.
SR-D17775 · Issue 486931
Nodes start as new if replacement start fails
Resolved in Pega Version 8.1.6
Cloud upgrade was failing if there was any attempt to scale up the number of instances. Every node starts up with a flag, and in cases of scale-up scenarios, a new instance with this flag was handled as a replacement instance instead of a new instance. That led the new node to fail because it has nothing to replace. To resolve this, the system has been updated so that if an instance failed to start as a replacement, the process will allow the instance to join the cluster as a new node.