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-137100 · Issue 604057

Added predictive text handler for Japanese on iOS

Resolved in Pega Version 8.5.2

The autocomplete function was not working well in MobileView when using Japanese IME on iOS. This has been resolved by adding a new input handler for IOS mobile, which will be triggered when predictive text is selected in mobile.

INC-147643 · Issue 605386

Corrected filtering logic for Report Definition with declarative join

Resolved in Pega Version 8.5.2

When using a report definition with declarative join enabled, running the report produced the correct results, but filtering on any other column resulted in all values being shown. This has been resolved by modifying the logic used for pzGetGridColUniqueValues.

INC-144103 · Issue 599681

Updated filter logic for filtering on a DateTime column

Resolved in Pega Version 8.5.2

When a class join was used in a report definition, the error "The Filter Logic used in the report is invalid" appeared while filtering rows of a report definition results on a DateTime column. This was a missed use case, and has been resolved by modifying pzGridSortPaginate to convert the data type value into the proper casing.

INC-147621 · Issue 604282

Updated filter logic for filtering on a DateTime column

Resolved in Pega Version 8.5.2

When a class join was used in a report definition, the error "The Filter Logic used in the report is invalid" appeared while filtering rows of a report definition results on a DateTime column. This was a missed use case, and has been resolved by modifying pzGridSortPaginate to convert the data type value into the proper casing.

SR-C90467 · Issue 429609

Validations are correctly run on rescheduled reports

Resolved in Pega Version 8.1.4

When using the OOTB schedule report functionality, UI validations were bypassed if the existing schedule was deleted and the report was rescheduled. This has been corrected by updating the Review harness to display the Perform harness when clicking Update.

INC-191356 · Issue 679163

External Input setting available on Strategy Batch Performance Test

Resolved in Pega Version 8.7

It was not possible to specify the External Input as part of a strategy when using a Batch Performance test. This has been resolved by updating the pzDisplayTestStrategyContext When condition to "true" the so external input selector is properly displayed.

INC-191902 · Issue 677412

Updated security for importing Excel to a decision table via a delegated rule

Resolved in Pega Version 8.7

An error was seen when attempting to import an Excel file into a delegated decision table when using the case manager portal. This has been resolved by correcting a BAC issue for decision table import in the pzRuleDeclareDecisionTableStandard.js file.

INC-172521 · Issue 651553

Email template content visible in user application

Resolved in Pega Version 8.7

An issue was seen with email templates functionality where the body content given during the email template creation was not visible when the template was used in the application by an end user. This was a missed use case for recent security updates, and has been resolved.

INC-139619 · Issue 597334

Agent tracing handling updated

Resolved in Pega Version 8.5.2

When attempting to trace agents the error "Unable to trace the agent" appeared on screen. Investigation showed that the data page used by the Tracer was not always available in a thread that was displaying the section, most commonly if the section was using deferred loading. This has been resolved by using a data page available in a thread that opens a Tracer's section.

INC-140879 · Issue 596571

Agent tracing handling updated

Resolved in Pega Version 8.5.2

When attempting to trace agents the error "Unable to trace the agent" appeared on screen. Investigation showed that the data page used by the Tracer was not always available in a thread that was displaying the section, most commonly if the section was using deferred loading. This has been resolved by using a data page available in a thread that opens a Tracer's section.

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