INC-219995 · Issue 717158
Security update enhanced to support custom implementations of InvokeAxis2
Resolved in Pega Version 8.6.5
The QueueProcessor activity indirectly invokes a Connect-SOAP. After installing the Security A22 patch, custom implementations on InvokeAxis2 reported runtime failure. This has been resolved by replacing reflection library use with explicit type checking and casting to get the array length in step 14 of InvokeAxis2.
INC-220652 · Issue 721386
Added explicit clearing for AsyncServiceManager cache
Resolved in Pega Version 8.6.5
Heap size for multiple JVMs increased after update. Investigation showed data pages loaded via Load-DataPage during service processing using requestor pools were cleared after each service interaction but the AsyncServiceManager cache was not cleared. To resolve this, an update has been made that will clear the async cache when the requestor is returned and when flush all is called.
INC-222791 · Issue 721372
GET API will skip case locking
Resolved in Pega Version 8.6.5
After update, performing a GET call on an assignment was unexpectedly locking the case. This was traced to a difference in handling: Pega 8.3 performed an Obj-Open-By-Handle of the workobject without acquiring a lock, while Pega 8.6 calls Assign-.acquireWorkObject which acquires a lock on the work object thereby affecting the other requestors from accessing the case. An initial fix for this issue enabled optimistic locking, however this did not resolve the issue in scenarios where there were concurrent calls and optimistic locking was not used. This additional update will skip locks on the work object for V1 GET assignments/{id}, GET assignments/{assignmentId}/actions/{actionId} and GET cases/{caseId}/actions/{actionId} and corresponding action refresh APIs.
SR-103429 · Issue 136984
Rule-Service-Java authentication in a stateless session re-enabled
Resolved in Pega Version 7.1.7
When exposing Rule-Service-Java through a service package, a proxy jar file is created. If the 'Requires Authentication' option was checked on the service package, the generated java did not contain the required code to pass through the username/password and authentication failed. This method of passing credentials via proxy method parameters was previously withdrawn for the stateless processing mode, but the java code has been reinstated to enable authentication for a stateless session if this method is desired.
SR-108346 · Issue 166436
Corrected purging for History and Attachments
Resolved in Pega Version 7.1.7
A problem was found with purging the History and Attachments for cover and folder items. This was traced to history tables using datetime columns as key properties: many databases round these values to less precision than PRPC uses, and the keys did not match. The purgeitems function has been updated to delete the instance specifically and bypass recalculating the InsKey.
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.
SR-112535 · Issue 164337
Portal rendering errors under z/OS
Resolved in Pega Version 7.1.7
Under z/OS, new installations were missing the login icon and the portal was not rendered correctly. This did not impact system performance. The problem was traced to an index setting in the DDL generation, and has been fixed.
SR-113384 · Issue 162788
Explicit schema mapping could cause migration script errors
Resolved in Pega Version 7.1.7
While running the migration script, the presence of a custom rule table that explicitly mapped the Data-Admin-DB-Table schema could cause the script to fail. This was caused by the GRANT statements in the SQL script not having the proper assignment for the user name with the "USER" keyword; a group name that is the same as the user name that we are trying to GRANT rights to was ambiguous. The workaround was to temporarily map the custom table to an empty schema, then manually copy this table to the RULES schema afterward, but this issue has been addressed by updating how privileges are granted for the table, procedure and function elements in a split schema.
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.