SR-113703 · Issue 163067
Custom root certificate support added to Connect-REST
Resolved in Pega Version 7.1.7
Configuring a Connect-HTTP/REST rule that connects to a server using custom root certificates caused the error "javax.net.ssl.SSLPeerUnverifiedException". To remedy this, REST / HTTP now supports the merging of custom and jvm trust stores and runtime support for SSL in REST connectors.
SR-115779 · Issue 167907
Custom root certificate support added to Connect-REST
Resolved in Pega Version 7.1.7
Configuring a Connect-HTTP/REST rule that connects to a server using custom root certificates caused the error "javax.net.ssl.SSLPeerUnverifiedException". To remedy this, REST / HTTP now supports the merging of custom and jvm trust stores and runtime support for SSL in REST connectors.
INC-132769 · Issue 573198
ArrayList constructor added to jarList initialization
Resolved in Pega Version 8.4.2
During the Switch Schema and Rolling Restart phase of an upgrade, failure occurred on the all the tiers with the error "PRRuntimeException: Method Invocation exception". This was traced to the method used to implement list initialization from an array, and has been resolved by adding an ArrayList constructor for jarList initialization.
INC-170950 · Issue 652332
Handling added for datetime set by relative reference
Resolved in Pega Version 8.7
When initializing a datetime property contained within .pxPages() in a data transform rule, if the property being set applied to @baseclass it was initialized as decimal string while all other properties were handled as normal GMT-based Pega date time strings. Investigation showed that the decimal value was set when the target page was given by a relative reference like .pxPages(TEXT) which was also defined on Pages & Classes. This has been resolved with an update to detect relative reference as page name in Pages & Classes tab and fall back to the old assembler.
SR-D81911 · Issue 553095
Reference property copying updated
Resolved in Pega Version 8.4.2
An error appeared on screen when performing the local action "NonProceed case" after upgrading. This was traced to the way copying reference properties was handled as part of pxDeleteAssignmentsForWork, and has been corrected.
SR-111889 · Issue 157259
Some SOAP calls with WSTRUST generated exceptions in customized environments
Resolved in Pega Version 7.1.7
In some heavily customized environments, a SOAP connect call using the WSTRUST element generated an exception. This was due to uneven handling of the local custom elements in the SOAP STS request, and has been resolved by adding a method to pick up all custom code based on the tag in policy document.
INC-131629 · Issue 570035
Updated padding character handling for access group hash
Resolved in Pega Version 8.4.2
While generating an access group hash from an access group name, Pega was using the '(' character as padding. However, Siteminder blocks the '(' character, causing requests to be rejected. To resolve this, the padding character will be removed while encoding and decoding will handle hashes both with and without the padding character.
SR-D89835 · Issue 554303
Updated padding character handling for access group hash
Resolved in Pega Version 8.4.2
While generating an access group hash from an access group name, Pega was using the '(' character as padding. However, Siteminder blocks the '(' character, causing requests to be rejected. To resolve this, the padding character will be removed while encoding and decoding will handle hashes both with and without the padding character.
INC-177353 · Issue 658727
Debug logging improved for LibraryRuntime
Resolved in Pega Version 8.7
No error logs were generated when an access group was pointing to a base ruleset with different major version from that of the system. This has been resolved by improving the debug logging for the following classes: LibraryRuntime LibraryMetadataCache .findTripletForCurrentRulesetList
INC-189811 · Issue 679935
Updated XMLDataToPage privilege
Resolved in Pega Version 8.7
Cases were not being created or moved due to a privilege issue on EndUser portal after update. This was traced to the XmlDataToPage activity now including the OpenDeveloperForm privilege, which end user operator profiles do not have. This was a missed use case, and has been resolved by updating XMLDataToPage so it requires authentication but not privilege to run.