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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

INC-142216 · Issue 596667

VBD performance improvements

Resolved in Pega Version 8.6

Performance issues were seen when running a decision funnel simulation. As part of the simulation, a VBD collection was created on the fly to store the metrics and linked to the simulation. Before each insert, which happened in batches of 500 records, there was a check if such collection exists. This check was required in earlier versions as the process relied on the VBD service being running, and the run would fail otherwise. Recently, VBD handling became more resilient and was updated to allow inserts even if the VBD server is down. If the VBD service is stopped before the simulation is completed, the simulation will continue writing records. When the VBD service starts again, it reads the backlog, and the simulation displays the final results. To adapt to this resiliency and improve performance, the system has been updated so that the VBD collection is not created and checked before the insert call, but only when the simulation is run or scheduled.

INC-142669 · Issue 599061

JMX exception logging corrected

Resolved in Pega Version 8.6

Although the process of decommissioning a Cassandra node worked correctly, JMX errors were visible in the logs during the operation. This has been corrected.

INC-142674 · Issue 594495

Enhancement added for node heartbeat recovery process

Resolved in Pega Version 8.6

Nodes were not showing up in the admin portal even though they were up and running and could be seen in the pr_sys_statusnodes table. The exception "An exception was encountered while invoking the cluster membership listener callback" was seen. All nodes became visible again after multiple restarts. The root cause was traced back to a temporary database connectivity problem. The database itself was fine according to database monitoring reports, but a network problem, a slow database query, or another issue prevented Pega from establishing a connection for more than a minute. An enhancement has been made to resolve this: if a node becomes unhealthy due to the service registry missing due to a failed heartbeat, the heartbeat will try to recover after 60 seconds and keep trying every 30 seconds until it succeeds.

INC-143121 · Issue 610733

Timeout for loading predictors made configurable

Resolved in Pega Version 8.6

When using an extremely large number of predictors, the Report definition pzADMPredictorsFilter was suffering timeouts due to the time for loading predictors from the database exceeding the time threshold allowed. This has been resolved by marking the rule as editable to allow custom setting of the threshold according to need.

INC-143441 · Issue 608897

Strategy Simulation Runs made more resilient

Resolved in Pega Version 8.6

Intermittently, a decision funnel simulation would fail with particular strategy logic or a particular StrategyTracker would not contain the results for all components so the system would not be able to calculate input SRs. Handling has now been added to make the simulations more resilient so they will not fail with a null pointer error due to incomplete strategy inputs.

INC-147692 · Issue 605279

Date properties on DSMClipboardPages formatted by determined type

Resolved in Pega Version 8.6

When data flow data was sourced from a File type dataset, the destination data showed 2020101+ for a valid date like 20201016. This has been resolved by modifying the way Date properties are read for DSMClipboardPages: properties which are instances of Date will be formatted considering the type, which will be deduced with usage of "getType" method. Invocation of this method can decrease performance of DSMClipboardPages, so it will be executed only when property will be of date type.

INC-148006 · Issue 605582

Enhancements added for very heavy use of strategy decision logic

Resolved in Pega Version 8.6

Recent updates were made to improve memory performance for scenarios where a single request primary page had tens of thousands of pages under an embedded page list property and the decision logic involved a strategy running on all the pages in that page list. To further improve performance, the array iterator has been modified and a DSS has been added that makes the threshold (50) in SSAExecutionContextIteratorFactory tunable.

INC-148585 · Issue 617716

Revision modified to skip empty ruleset version

Resolved in Pega Version 8.6

When submitting a revision, the package created was empty and a ruleset version with empty label and version was created. The error "ArrayIndexOutOfBoundsException" was noted in the alert logs. This exception was traced to pzgetnextrulesetversion and was caused by the ruleset version being passed as empty. This has been resolved by setting an error message on the workpage when the ruleset version is empty, so the revision package will not proceed.

INC-148899 · Issue 615701

Adaptive models update correctly

Resolved in Pega Version 8.6

Some models had the recorded responses column updated, but the models (number of Positive, Negative and Processed Responses) were not updated. Investigation showed that deleting the modelRuleConfiguration through the stateManager/client did not delete modelFactories related to the configuration. If a new configuration came in with a different algorithm, the update issue occurred. This has been resolved by reseting the configuration according to its factory in that specific case.

INC-150854 · Issue 608369

Logic optimization disabled in offers

Resolved in Pega Version 8.6

Offers that should not be eligible to customers were passing through even though the offer was narrowed down to using “OR” conditions in the Engagement policies. This was traced to the logic optimization ignoring precedence, and has been resolved by disabling the optimization.

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