INC-170551 · Issue 656560
Rule Assembly update for pxTextInput and pxDisplayText
Resolved in Pega Version 8.6.1
After the application restart, multiple rule assembly alerts were seen for pxTextInput and pxDisplayText . During first access, Assembly is done and container is cached in VTable; investigation showed that in this case, the Load class without the package name had a class not found issue, and then subsequent access tried to use the container from cache and assembly was not done. To prevent this, an update has been made to perform the class lookup using the package name and class name.
INC-170599 · Issue 645224
DSS partition count setting made backward compatible
Resolved in Pega Version 8.6.1
After update, the DSS to limit the number of partition counted was no longer working and instead used the default value of 20. This has been corrected and made backwards compatible.
INC-164405 · Issue 640183
Enhancement added to support incremental update
Resolved in Pega Version 8.6.1
In order to support incremental updates between versions of Pega and versions of Oracle, an enhancement has been added that will allow the engine to handle a mix of database version and JDBC driver version and issue the query that will work on Oracle 11g database despite using a newer driver version.
INC-170950 · Issue 652331
Handling added for datetime set by relative reference
Resolved in Pega Version 8.6.1
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.
INC-163043 · Issue 645392
PEGA SOAP Service MTOM attachment handling updated
Resolved in Pega Version 8.6.1
After configuring a PEGA SOAP service with the Enable MTOM checked, sending a SOAP request with attachment to the service returned an invalid request error stating "Value of content length header is greater than zero - [762], but this request has empty POST". Investigation showed that when the input request reached the getPostBytes method and inputstream tried to read it, there were no available bytes and end of file was detected. This was due to the inputstream having already been read in getMultiPartSOAPHandler() method in FileUploadHandler class. To resolve this, the system will update an 'if' condition in getPostBytes method to skip reading the request attachment when contentType is "multipart/related".
INC-172692 · Issue 650612
InsID will be derived from handle if null after update
Resolved in Pega Version 8.6.1
Updating from Pega 7.2.x to Pega 8.4.x failed with a null pointer exception in the “Upgrade Context” target. This was traced to a rule where the pxInsID was null. To resolve this, an update has been made to derive the InsID from handle when needed.
INC-176785 · Issue 656078
Validation on DateTime property working for mobile
Resolved in Pega Version 8.6.1
A mandatory DateTime field with "Allow text entry" set to 'No' was not restricting validation when no value was provided. This was an unintended consequence of recent work done to validate input type date along with input type hidden, and has been reverted.
INC-175205 · Issue 652530
Agent restart made more resilient
Resolved in Pega Version 8.6.1
During a timeout outage, agents intermittently encountered a NoClassDefFound error and were disabled. After the database connection was restored, the agents were not automatically restarting. This has been resolved by making the code more resilient to errors; agent will be restarted when a temporary issue is detected, and the restart will be immune to most exceptions.
INC-161737 · Issue 639845
Queue processor correctly moves items to Broken Items
Resolved in Pega Version 8.6.1
When an exception occurred while Queue Processor processed an item, he queue item was not moved to Broken Items. The error " inconsistent datatypes: expected - got CLOB DatabaseException caused by prior exception" was generated. This has been resolved by modifying the NativeSQL builder and NativeSQLBatchExecutor to allow the batch of queries to be retried. Additional changes were also added for Oracle databases to identify the correct column types.
INC-168983 · Issue 645791
Jobs restart after system failure
Resolved in Pega Version 8.6.1
Several key standard CLUSTER type jobs were left in disabled state after a performance break test with rolling restart of the nodes. This was traced to prevention code that was originally intended to disallow stopping the scripts, but had an unexpected result after a system failure when the request to restart the standard pzDelayedQueueProcessorSchedule was rejected if the check of the job name matched the deny list. This has been resolved by removing the preventative code.