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-231195 · Issue 734205

Additional logging for businessCalendar.CalendarUtility.java

Resolved in Pega Version 8.8

Enhanced logging has been added in order to assist with identifying issues related to the Business Calendar.

INC-232338 · Issue 739258

Data_views Pagination in v2 DX API working as expected

Resolved in Pega Version 8.8

When attempting to use the pagination features available with the v2 DX API '/data_views/{data_view_id}", all results were returned and no pagination was performed. This has been resolved.

INC-RCA-1953 · Issue 716176

ReportStats delete query performance improvements

Resolved in Pega Version 8.8

database connection spike was maxing out the allowed database connections, causing login delays and termination of stream nodes. Investigation traced this to the delete query on pr_log_reportstats, which was a full table scan generated from SQLGeneratorPostgres.purgeTableContainingClass. To improve performance, the full table scan sub-query has been removed and 'limit' syntax has been added to run the necessary deletion in batches.

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.

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