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-184352 · Issue 671897

Predictive model snapshot generation updated for Java 11

Resolved in Pega Version 8.7

While the Simulation data export case type was executed as expected, the predictive stages showed zero records processed. This was traced to instances running on Java 11 which caused an issue with the snapshot process. This did not affect learning, but visualization and reporting were not working in Prediction studio. To resolve this, an update has been made to the snapshotID for Java 11 compatibility which will generate a random UUID instead of using a seed.

INC-185045 · Issue 672416

Performance improvements for action check-in

Resolved in Pega Version 8.7

The process of 'Saving As' an action to a higher ruleset, Saving, and then running Check-in was taking an excessive amount of time. This was traced to redundant page copy activities and performance has been improved by updating the implementation.

INC-186437 · Issue 685015

Updated entity attachment extraction tokenizers

Resolved in Pega Version 8.7

After creating an entity extraction model, it was seen that one of the entities worked when there was a space after the semicolon but the detection was not working if there was no space. This has been resolved by updating the Tokenizers with extra examples to address tokenization when ":" is present between two words without any spaces.

INC-186889 · Issue 674014

Unused DSS compiledExpressions now defaults to false

Resolved in Pega Version 8.7

After updating from Pega 8.2 to Pega 8.5, executing a test campaign failed with an error in logs. This occurred when running Distribution tests with "Include funnel analysis reports" checked, and was traced to the DSS setting "decision/strategy/ssaVM/compiledExpressions". As this was previously used to toggle a feature which is no longer in use, the default setting for this DSS has now been changed to false to resolve this issue.

INC-187070 · Issue 672106

Strategy execution queries tuned

Resolved in Pega Version 8.7

During NBA strategy execution, interaction history summaries were queried multiple times for a single strategy execution. To improve this function, the isChanged query will now be executed once after system startup if there are no changes instead of being executed every time the Aggregates DataSet BBK is executed. If the same Aggregates query is made multiple times as part of a Strategy in a REST request (i.e. likely multiple ADM models in a MakeDecision call), only one Aggregates BBK call will be made.

INC-187520 · Issue 677873

Actuals sync clears data from cache and persistence

Resolved in Pega Version 8.7

When sync attempted to clear the existing data from Actuals before copying data from the interaction history, the partition was cleared from the cache but not from persistence. IH data that was then copied to the same partition time ranges had new field descriptors created that did not match the format of the old data in persistence. As a result, when a query triggered the loading of such a partition, the mix of data with the old and new formats caused the load to fail. This has been resolved by updating the system to ensure the data is deleted properly from both the cache and persistence.

INC-188124 · Issue 672587

Multistage Prediction Logic improved

Resolved in Pega Version 8.7

When Predictions with Response wait time configured were executed as part of make decision, each decision that came out of the strategy caused a pxDR call to fetch the relevant model execution results and process them to stage the default outcome results for models. This has been improved by modifying the system to process the existing records rather than reading data again from pxDR.

INC-188124 · Issue 673106

Strategy updates

Resolved in Pega Version 8.7

Three issues with Strategies were addressed: * During NBAD-generated strategy execution, each interaction history summary is queried twice to check data relevancy. This update adds configuration options to disable topup in aggregate datasets. Topup can be disabled with the following configuration items: Set prconfig "ih/aggregates/last_customer_update_method" to NONE Set DSS "cep/aggregates_dataset/partition_proc_cache_time" to -1 * During NBA strategy execution, interaction history summaries were queried multiple times for a single strategy execution. To improve this function, the isChanged query will now be executed once after system startup if there are no changes instead of being executed every time the Aggregates DataSet BBK is executed. If the same Aggregates query is made multiple times as part of a Strategy in a REST request (i.e. likely multiple ADM models in a MakeDecision call), only one Aggregates BBK call will be made. * Summaries created with a list of filters for aggregation were intermittently truncating the generated Summary Dataset. This has been resolved by updating the Digest calculation strategy to not take into account Filter IDs which may change if a Dataset is generated from CPD.

INC-188309 · Issue 684702

Proposition filter populated for test business Issue

Resolved in Pega Version 8.7

When running the proposition filter rule, no drop down list appeared for a business issue. This was caused by the Issue list not being populated for the Action-Run test page, and has ben resolved.

INC-188389 · Issue 674671

ComponentName fallback added for toggling page context

Resolved in Pega Version 8.7

Whenever the External Strategy configuration was changed from "Another Page" to "Current Page", pyComponentName property was not being created. This was a missed use case for toggling page context for external substrategies in the user interface of the strategy designer, and has been resolved by setting pyComponentName to its default if reset when switching context.

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