INC-151418 · Issue 610231
Authentication updated for legacy activities
Resolved in Pega Version 8.6
Authentication updates have been made for several legacy activities invoked via URL by custom HTML.
INC-153138 · Issue 625568
Database primary keys generated as NONCLUSTERED for imports
Resolved in Pega Version 8.6
When a primary key was defined for a table and the table was exported and then imported, the primary key was generated as CLUSTERED. This resulted in an MS SQL Cluster Index violation because all Pega-shipped tables generated during installs/upgrades have a PK constraint index with NONCLUSTERED index type as it allows for a longer key. This was a missed use case, and has been resolved by updating the system such that when importing with MS SQL database, the primary key index is made NONCLUSTERED all the time so it will be consistent with the base platform.
INC-153182 · Issue 615758
Corrected import overriding class definition history save setting
Resolved in Pega Version 8.6
Importing Robot Manager RAPs was failing due to a bad class mapping between class History-Data-Robotic-AutomationPackage-DeploymentLevel and its corresponding table pr_hist_datadeplvl in database PegaDATA. This was traced to a conflict where the class wasn't designed to have history saved but import was passing a flag that forced history to be saved which was overriding the class setting. This has been resolved.
INC-154042 · Issue 621261
Pega Catalog custom upload control modified
Resolved in Pega Version 8.6
Attempting to upload a catalog.zip file caused the system to hang and thread dumps were seen in the logs. Investigation traced the issue to the custom control used to upload the catalog, which was posting the entire content in form data rather than sending a multi-part request. The control contained both legacy code which used form.submit() and encoding along with new code that used SafeURL and sent an async request. With this, encoding could not be set to multi-part in case of an AJAX request. To resolve this, the catalog upload control has been modified to use the appropriate legacy code that performs form.submit() and sets the encoding properly.
INC-155789 · Issue 622547
Third-party libraries upgraded
Resolved in Pega Version 8.6
The following third-party jar files have been updated to the most recent versions:ant: v1.10.9 httpclient: v4.5.13 xercesImpl: v2.12.1
INC-157196 · Issue 629297
Deprecated service package features now require authentication
Resolved in Pega Version 8.6
Authentication has been added to deprecated features of the standard service package to improve security. If issues are encountered during product migration, please use the Deployment Manager.
INC-158519 · Issue 625079
Filter considers all instances pages during deployment
Resolved in Pega Version 8.6
During package deployment, attempting to use Filter to skip some of the instances only displayed the result of the current active page instead of all pages. This was an unintended consequence of previous work, and has been resolved by adding the logic to strip quotes in the value and adding the "Pagination activity manages filtering" checkbox by default.
INC-159834 · Issue 632249
StackOverFlow logging improved
Resolved in Pega Version 8.6
Enhanced diagnostic logging information has been added to help find issues when StackOverFlow errors occur.
INC-160198 · Issue 632905
Enhancement added for attachment size handling with Kafka
Resolved in Pega Version 8.6
Attempting to send an email attachment larger than 2 MB resulted in the error "Caused by: org.apache.kafka.common.errors.RecordTooLargeException: The message is 8101592 bytes when serialized which is larger than the maximum request size you have configured with the max.request.size configuration." This has been resolved by updating the Stream SPI size to 2.0.5-14 to support custom producer configurations. The settings can be passed as environment parameters, for example 'Dstream.producer.max.request.size=500990'.
INC-160288 · Issue 626067
Kerberos handling updated for database remap
Resolved in Pega Version 8.6
After upgrade from Pega v7.2 to Pega v8.4, using Kerberos authentication was failing during the remap task. Investigation showed that null username and password values were being passed to SchemaAssignmentUtility along with the flags as arguments, causing the utility to misinterpret the arguments. As arguments should be populated only when flags and values are available and not null, an update has been made which will set the username and password flags only if they are not null in the Remap database tables target.