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-156211 · Issue 620193

Verbose comments removed from wrapper

Resolved in Pega Version 8.5.3

Comments with references to external links have been removed from some harness wrappers.

INC-157317 · Issue 620573

Signature Capture supported in RDL

Resolved in Pega Version 8.5.3

An enhancement has been added which supports using Signature Capture on forms in repeating dynamic layouts.

INC-157596 · Issue 624124

Mobile channel upgrade wizard correctly initiated

Resolved in Pega Version 8.5.3

After upgrade, the offline mobile app was not loading the correct portal. This was traced to missing properties needed to launch the upgrade wizard for channels upgrading from a previous release to v8.5, and has been resolved by setting those properties in upgrade activities.

INC-158468 · Issue 626380

RecordFieldValuesList page cleared

Resolved in Pega Version 8.5.3

Investigation o0f web node crashes traced the issue to a condition where the RecordFieldValuesList page was not cleared. This has been resolved.

INC-143925 · Issue 597289

Documentation update to alternate URL for mobile build

Resolved in Pega Version 8.5.3

The documentation located at https://community.pega.com/knowledgebase/articles/mobile/85/setting-alternative-host has been updated to reflect current information and instructions for setting an alternative host.

INC-147844 · Issue 612899

Check added for type of value in scheduling adaptive reports

Resolved in Pega Version 8.5.3

When scheduling the pyAdaptiveModelsOverview, pyAdaptiveModelsPredictorOverview and pyModelsActivePredictorsOverview reports, the error "atest.Snapshot_Time is not a valid date/time value" was occuring in step 1 of the pzRDExportWrapper activity. The reports worked as expected when run standalone; the failure only occurred when running from scheduled tasks. Investigation showed that the system was trying to parse a property reference as a datetime, and the failure and error caused the report scheduler to refuse to send the generated report. This has been resolved by adding logic to ReportFilter.java to check if the value is a property reference before attempting to parse it as a datetime value.

INC-149143 · Issue 613143

Report category error messages made accessible

Resolved in Pega Version 8.5.3

In order to improve accessibility while creating new reports, labels have been added to the error messages on the category name field.

INC-150193 · Issue 613916

Corrected page counts for 'save-as' reports

Resolved in Pega Version 8.5.3

The total pages count and last page icon were not displaying when the Preview button was clicked after a save-as of a report in the Report Browser. Investigation tracked this to a visible when condition on those fields that was being changed to the default of false during the save-as, and this has been resolved.

INC-151102 · Issue 615016

Cross-Site Scripting update

Resolved in Pega Version 8.5.3

Cross-Site Scripting filtering has been added to Shortcut Handle.

INC-151185 · Issue 618730

OptimizeForLargeResults flag set in BasicListSpecification to avoid OOM

Resolved in Pega Version 8.5.3

As soon as dedicated indexing started for a data type, the JVM heap occupation went beyond 99 and eventually caused a system crash due to an out of memory error. This was traced to the use of the BasicListSpecification API for retrieving results from the database always having the autocommit mode on, which loaded all instances for indexing into memory and interfered with PostgreSQL's cursors (query encapsulation). This has been resolved by adding an OptimizeForLargeResults flag that will be set to on in the BasicListSpecification activity before fetching the keys from the database.

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