INC-209399 · Issue 708570
Handling added for indexing items exceeding Kibana max size
Resolved in Pega Version 8.6.4
Indexing cases was generating errors from Kibana indicating "Failed to index document: java.lang.IllegalArgumentException: Document contains at least one immense term in field="_m_MailBody" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped." To resolve this, if an embedded property exceeds the max length defined by Kibana, it will be truncated at 32k bytes in order to allow indexing to proceed.
INC-211726 · Issue 705071
Parameter logic updated for metrics activity counter
Resolved in Pega Version 8.6.4
An error was causing the PushCDHMetrics agent to fail. This was traced to an undefined parameter in the activity which was used as a counter, and has been resolved by replacing it with a local variable of type integer. In addition, an agent has been added to support publishing the model metrics.
INC-
218457 · Issue 713986
Updated debug logging
Resolved in Pega Version 8.7.2
Debug logging within IndexReferenceSynchronizer and FastLoader has been updated. With this update, IndexReferenceSynchronizer debug logging will indicate what the action is for each instance, FastLoader will include information about the keys being loaded and statements being executed, and duplicate logging has been removed from BatchSQLExecutors.
INC-202004 · Issue 705170
Hotfix documentation updated to point to Hotfix Manager page
Resolved in Pega Version 8.7.2
The readme file attached to hotfix downloads contained an outdated reference to use "PRPC Hotfix Installer on the Update Manager landing page." This has been updated to point to the Hotfix Manager landing page.
INC-205181 · Issue 697801
Warnings pull from report definition page
Resolved in Pega Version 8.7.2
When a report definition filter was used in the "Class instances to include" section of the Product rule, severe warnings appeared noting "Report definition filter performance issues for LookupDataMigration : Using a custom HTML control to format a column may result in poor performance displaying query results. Consider using auto-generated HTML controls". However, the report definition used, LookupDataMigration, has no Custom HTML control in the latest version of the rule, and the "CheckForWarnings" rule for the product was running a report definition in the "Index-Warning" class which has the warnings for all the versions of the rule. This was due to warnings being displayed in the product for the report definition filter without applying rule resolution for report definition, resulting in warnings from all report definition version rules from a ruleset given a report definition name. This has been resolved by adding an update which will use Obj-Open to read the warnings from report definition page instead of looking up for warnings from Index-Warnings table.
INC-205453 · Issue 706570
Pega Keystore supported for hotfix signature verification
Resolved in Pega Version 8.7.2
In order to support custom trust managers which require an alternate method for supplying the root certificate via a platform trust store, an enhancement has been added to allow Pega Keystore to be used as a hotfix verification source. Detailed information on this can be found in https://docs.pega.com/keeping-current-pega/87/verifying-hotfix-authenticity-using-pega-keystore
INC-208516 · Issue 705099
Patchdate values made unique
Resolved in Pega Version 8.7.2
The hotfix manager was incorrectly indicating that a previous hotfix was not installed or was partially installed and should be reinstated. This scenario was created during security updates where the missing/incomplete hotfix had been deliberately deleted from the database, and has been resolved by adding an update which will force patchdate to be unique when adding duplicate code resources during tests.
INC-209435 · Issue 707376
Column population error downgraded to warning
Resolved in Pega Version 8.7.2
A Column Population job run after deployment for some classes was logging the error "Class does not exist", but no property was identified and no impact to the system was seen. This error has been downgraded to a warning.
INC-211299 · Issue 706317
Handling updated for rule export errors
Resolved in Pega Version 8.7.2
After exporting the rules from E2E, the import to the production mirror failed. Investigation showed that the process encountered a time out from an Adaptive Decision Manager table when exporting the product rule, resulting in the product file not containing the mandatory jar files. This has been resolved by updating the handling of errors during export, and suppressing auto-chaining when generating app JSON.
INC-215877 · Issue 715233
Handling added for Oracle "NUMERIC" type
Resolved in Pega Version 8.7.2
When a product rule was created in an environment using Oracle, importing the product into the cloud environment with database table schema changes resulted in errors. This was traced to a change in Oracle's JDBC driver which was reporting Number as a JDBC "NUMERIC" type instead of the previous "DECIMAL". Pega uses the NUMBER data type and expected a type=DECIMAL for an Oracle number, causing the errors. This has been resolved by adding a check for flex numbers if column is NUMERIC.