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.

INC-151037 · Issue 609625

Enhanced ADM diagnostic logging

Resolved in Pega Version 8.4.4

Diagnostic logging enhancements have been added in order to better identify issues related to ADM models not being created or where learning is impacted.

INC-153223 · Issue 613703

DSS added to set Cassandra query page size limit

Resolved in Pega Version 8.4.4

When a site with a large number of nodes captured responses to the commit log, it was possible for nodes run out of heap space and cause system instability. This was due to the Cassandra query not having a specified page size, so the cluster-wide default setting of 5000 created an issue for large sites which could have over 150 nodes capturing responses. This has been resolved by specifying the page size on the Cassandra query that used to read responses from the commit log. This value will be set dynamically with a DSS to not read more than n responses from all shards combined in a single batch.

INC-154128 · Issue 614295

High thread contention in StrategySSAProgram resolved

Resolved in Pega Version 8.4.4

While Running inbound campaigns during peak times, high contention was observed around "threadSafeWrite" and "threadSafeRead". To resolve this and improve performance, the code around handling write locks has been updated.

INC-154889 · Issue 617191

Corrected export of zero value as '0E-9'

Resolved in Pega Version 8.4.4

File Data Set was exporting properties such as pxPriority and pyPropensity as '0E-9' if the value was 0.00000 . This has been corrected.

INC-155822 · Issue 618268

Locking added to avoid Null pointer exception for auto-populate property

Resolved in Pega Version 8.4.4

After configuring the auto populate property "OrgProduct" which referred to a data page, the system experiencing heavy load led to the property not getting properly initialized. This resulted in a WrongModeException and NullPointerException. To resolve this, the system has been updated to lock the requestor when Queue Processors execute their activity. This will prevent race conditions and concurrent modifications if other threads are accessing the same requestor.

INC-157097 · Issue 619995

REGEX In Expression Builder matches runtime values

Resolved in Pega Version 8.4.4

An expression builder statement was evaluating differently at runtime vs at testing. This was traced to a difference in escape character handling between old legacy code and the new strategy runtime engine, and has been resolved by ensuring the strategy runtime engine is supporting escape character use cases.

INC-157194 · Issue 620152

CheckRevisionDeployment requires authentication

Resolved in Pega Version 8.4.4

Authentication has been added to the CheckRevisionDeployment service package.

INC-132590 · Issue 590491

Exported Excel from Decision Table wraps correctly

Resolved in Pega Version 8.4.4

After upgrade, entries were displayed in a single line on exporting a decision table to Excel despite WrapText cell formatting being set. This was traced to the WrapText cell formatting set under the UpdateGridCells() function being overridden inside an addDataFormat() function callas part of DecisionTableWorkBookConverter.java. This has been resolved by adding the new function "setWorkAreaCellStyles" and calling it after generateWorkbook() function call of super class (AbstractWorkBookConverter.java).

INC-140789 · Issue 597799

Added handling for validation after inactivity

Resolved in Pega Version 8.4.4

A Validate rule was configured to add an error to a field if MyPageList had any page where MyProperty was not empty. The rule worked correctly if there was no pause in using the UI, but if the UI was left for a few minutes and then the field was changed, the Validate rule always evaluated the expression to true. This has been resolved by adding a null check in Utilities.countInPageList() function.

INC-141895 · Issue 601985

Options not cached by default for picker controls

Resolved in Pega Version 8.4.4

Properties created in the data model of the case type were not showing in the drop down of custom conditions in a decision step. The property did not appear on the left hand side 'when' rule of the case designer in App Studio or Dev Studio, but did appear on the right hand side of the same 'when' rule. The issue temporarily resolved when the context class parameter was hardcoded with the class name. This was traced to the properties being cached by pzInnerEmbedConditions, and has been resolved by unchecking "Enable caching of options" for any picker control.

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