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-188389 · Issue 672761

ComponentName fallback added for toggling page context

Resolved in Pega Version 8.6.2

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.

INC-188419 · Issue 671500

DSS added to configure usage of Topup

Resolved in Pega Version 8.6.2

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

INC-174785 · Issue 651461

Flow connector attachment point control updated

Resolved in Pega Version 8.8

Previously, attempting to change the target point for a connector in the flow modeler to a different point on the same shape did not work without placing the point on an intermediate connector first. An enhancement has now been added to support moving the connector directly to a different constraint point on the same shape.

INC-179727 · Issue 704543

Modified batch requestor handling to ensure cleanup

Resolved in Pega Version 8.8

A large buildup of batch requestors was seen, and restarting the node did not clear it. Investigation showed that in the case of one class reading a DSS value, a Pega requestor was being created when it was unable to retrieve any Pega context, and this requestor was not cleaned up afterwards. To resolve this, an update has been made to the way the requestor and Pega context is being created along with ensuring it will be cleaned up properly after use.

INC-180246 · Issue 664948

Support for apostrophe added to keyword tokenization

Resolved in Pega Version 8.8

A keyword containing an apostrophe was not detected properly in Text extraction model. This has been resolved by updating the annotator used in the tokenization.

INC-180762 · Issue 666291

Calendar gadget correctly displays event of >31 days

Resolved in Pega Version 8.8

When using the pxCalendar gadget to display a hotel reservation of duration > 31 days, the entire bar was not displayed on the PEGA calendar. Investigation showed that eventslist was not considering the month value, and this has been resolved by updating the pzEventPreProcessing activity to check for month.

INC-194348 · Issue 682339

Resolved multiple copies of Pega0050 alerts

Resolved in Pega Version 8.8

The PDC alert Pega0050 was seen multiple times for the standard pxgetoperatordetails activity, step 6.This has been fixed by removing the pagecopy and updating the data page properties.

INC-198914 · Issue 686938

PMML updated for nested 'if'

Resolved in Pega Version 8.8

Running a model on the openscoring API and the Pega PMML model gave different results. This has been resolved by updating the handling for nested 'if' in PMML.

INC-200802 · Issue 699966

Line break handling added for setting required question asterisk

Resolved in Pega Version 8.8

If a survey question was formed in multiple sentences, the asterisk marking it as required was not displayed in screen. The asterisk displayed as expected if the question was one sentence. This has been resolved by updating the setMandatoryIconforQP script handle linebreaks and set the required symbol as expected.

INC-202111 · Issue 710107

Logging extended for PRPCPropertyInfoProvider

Resolved in Pega Version 8.8

In order to assist with diagnosing issues with Kafka and JSON, additional logging has been added for PRPCPropertyInfoProvider.

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