INC-139619 · Issue 597333
Agent tracing handling updated
Resolved in Pega Version 8.6
When attempting to trace agents the error "Unable to trace the agent" appeared on screen. Investigation showed that the data page used by the Tracer was not always available in a thread that was displaying the section, most commonly if the section was using deferred loading. This has been resolved by using a data page available in a thread that opens a Tracer's section.
INC-139626 · Issue 592389
Enhancement added to fix corrupted operators
Resolved in Pega Version 8.6
After upgrade, an issues were seen with older operator IDs: it was not able to save the operator ID, switching the portal to admin studio was not working correctly, and it was not possible to launch the case manager portal with the migrated operator IDs. The issues were not seen with operators created after the upgrade. This was traced to corruption in the BLOB, and has been resolved by adding an enhancement to run a utility that will fix the existing corrupted operators.
INC-139627 · Issue 604761
Legacy and new ID generation logging enhanced
Resolved in Pega Version 8.6
Legacy and new ID generation logging enhancedA DuplicateKeyException was generated when attempting to create a case. The root issue was related to the local modification of the reserved ID field in the database through a custom activity and was able to to be fixed with a local change. In order to improve diagnosing events such as this in the future, enhanced logging has been added to to the legacy and new ID generation.
INC-139695 · Issue 593084
Mountain time zone format updated
Resolved in Pega Version 8.6
If an operator was created with any calendar instance time zone mapped to "Canada/Mountain" and made unavailable for the current period, routing an assignment to that operator using the standard ToCurrentOperator activity resulted in a null pointer error when the Rule-Utility-Function was executed to find a substitute operator. This was traced to the time zone format Input to DateTimeUtils API (parseDateTimeString) having the wrong time zone, for example, 20200819T080000.000 MDT (CA), and has been resolved by modifying the locale XMLs to remove (CA) from zone code so that MDT (CA) is updated as MDT.
INC-139802 · Issue 594032
Extra logging and more resiliency for cleanup daemons
Resolved in Pega Version 8.6
Null pointer exceptions thrown by daemon threads that clean requestors and handle agent changes can result in a high number inactive requestors. Additional logging has been out into place to help capture information to identify the offending data, and master daemons for requestors and for new agents have been made more resilient to any null pointer exception thrown by the diagnostics code so they do not stop their work.
INC-139810 · Issue 592835
New Rule-Utility-Function added to allow customizing filename formatting in repository
Resolved in Pega Version 8.6
When using S3 as file storage, uploading a file with a name such as "sample.tar.gz" resulted in the file name in the repository being formatted as "sample.tar_.gz" instead of the expected "sample_.tar.gz". This was caused by the handling in pzSaveToRepository, which was meant to include the CaseID for the customer use case of same-name attachments on every instance of a case. In order to handle attachments with multiple file extensions such as "<FILE_NAME>.tar.gz", the logic for the fileName formatting has been moved from pzSaveToRepository to the new Rule-Utility-Function pyFormatAttachmentName so that is is possible to override and customize the behavior.
INC-140341 · Issue 593706
Cross site scripting updates
Resolved in Pega Version 8.6
Additional cross site scripting protections have been added to pyActivity processing and pzTransformAndRun.
INC-140421 · Issue 595472
DSS added to enable short-term IBM MQ tracing
Resolved in Pega Version 8.6
In order to support on-demand MQEnvironment tracing, a DSS property has been added to enable tracing for a day. This is done by setting the DSS property IBMMQEnabler = true , which will set MQEnvironment.enableTracing(86400000); and tracing will be enabled for a 24-hour period.
INC-140750 · Issue 589926
Resolved post-passivation login issue
Resolved in Pega Version 8.6
An authentication error was seen when operators tried to log in again after passivation. This was traced to a corrupted BLOB, and has been resolved.
INC-140879 · Issue 596570
Agent tracing handling updated
Resolved in Pega Version 8.6
When attempting to trace agents the error "Unable to trace the agent" appeared on screen. Investigation showed that the data page used by the Tracer was not always available in a thread that was displaying the section, most commonly if the section was using deferred loading. This has been resolved by using a data page available in a thread that opens a Tracer's section.