Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-D56293 · Issue 536779

Resolved timeout errors related to getIndexInfo

Resolved in Pega Version 8.4.1

When attempting to import large files (around 300MB) via Designer Studio a time out error was seen, but the same upload worked as expected from the command line. Investigation showed that the "approximate" argument in getIndexInfo caused wasteful analytic operations to be run on the database, hampering performance. To resolve this, areas where the results of the analysis are not needed have been modified to have aApproximate set to be true so it will not be run.

SR-D66986 · Issue 539415

BIX command line support improved

Resolved in Pega Version 8.4.1

Post-upgrade, it was seen that changes to the engine which validate that Data-Admin-DB-Name is not defined multiple times caused the BIX command line extracts to no longer work the same way. In order to improve backwards compatibility, updates have been made to loosen the validation in JdbcConfigurationFactory to always prefer prconfig settings if there are multiple definitions.

SR-D76150 · Issue 539455

Logging updated for EmailListener and Data-Agent queue items

Resolved in Pega Version 8.4.1

In order to avoid the pr_sys_queue_ftsindexer table being overwhelmed with Data-Admin-Connect-EmailListener and Data-Agent-Queue instances for queued items, the Data-Admin-Connect-EmailListener and Data-Agent-Queue class definitions have been modified to filter queue items to incremental indexing if updates are from system and instance type is data- .

INC-173452 · Issue 666440

Quorum capability check added for external Elastic Search

Resolved in Pega Version 8.6.2

The error "java.lang.UnsupportedOperationException: Not supported for client/server mode at search.indexmanager.internal.ESIndexAdminHTTP.isQuorumAvailable" was appearing when attempting to use external Elastic Search to index a dedicated index, and the queue processor was running but showed multiple broken items. This has been resolved by adding a capability check with ES_INITIALIZE_EMBEDDED_CLUSTER to prevent a quorum check with external elastic search.

INC-174686 · Issue 670540

Handling updated for INativeSQLBuilder with ABAC enabled

Resolved in Pega Version 8.6.2

When trying to import into a data type, the error "Exception occurred during data import pxW-886: java.lang.IllegalArgumentException: INativeSQLBuilder not initialized properly" was generated. Investigation showed that when Add or Update was chosen with ABAC enabled during import, a null pointer exception occurred while getting the class definition. This has been handled by adding an extra null condition check.

INC-175797 · Issue 662046

Date/time filter works in source column

Resolved in Pega Version 8.6.2

The date/time filter was not working in the Source column for a report definition. This was traced to "pxCreateDateTime" resolving and storing the pyDataType in the report as "DATE TIME". While "DATE TIME" is an acceptable data type it was not supported by pzGridSortPaginate and thus the filter did not work. This was a missed use case, and has been resolved by updating pzGridSortPaginate to check the dataType as both "datetime" and "date time".

INC-176158 · Issue 664347

Max number of rows setting properly honored

Resolved in Pega Version 8.6.2

The setting for the maximum number of rows to retrieve was still used in a report definition even when it was disabled. This was traced to the report definition being sourced from a data page and having pagination enabled, and has been resolved by updating the handling for this use case.

INC-178663 · Issue 659806

Updated handling for batch indexing cancellation

Resolved in Pega Version 8.6.2

Entries were seen in the pyBatchindex QP even when indexing was not in progress. Investigation showed that if an exception occurred during the cancel process, the pyStatusWork property in Log-Cluster-FTSIndex instance was not correctly updated and the value remained as CancelInProgress. As a result, SLP silently remained in the state of waiting for the completion of cancel operation. This has been resolved by updating the handling of the cancellation process to ensure the queue is correctly cleared and email notifications are sent as expected.

INC-179362 · Issue 660589

Display limitation removed for scheduled reports

Resolved in Pega Version 8.6.2

When looking at Configure >> Reports >> Scheduled Reports only 50 reports were shown across two pages instead of all of the reports retrieved by pzGetScheduledTask. This was a limitation set in pyScheduledTasksGadget, and has been removed.

INC-181394 · Issue 662097

Handling added to avoid incorrect manifest count

Resolved in Pega Version 8.6.2

Extracted Record counts in the manifest file were incorrect if any updates were made during the extraction process. This has been resolved by modifying the code to prevent the issue.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us