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-135159 · Issue 580673

Logic updated for deepMergeObj API

Resolved in Pega Version 8.2.8

Issues with the embedded page values being removed when navigating from a flow action and inconsistent localization of labels and captions in a mobile app were traced to the deepMergeObj API; the logic for the API has been revised to ensure the pxObjClass property is not removed from embedded pages during the doSave function.

INC-144948 · Issue 602275

Resolved JBoss memory leak

Resolved in Pega Version 8.2.8

JBoss logs indicated connection leaks. This has been resolved by limiting the scope of instance of ActionProvider, DataSyncRequestParser to a try-with-resources block which ensures that all resources are released.

SR-D95638 · Issue 556964

Added handling for mobile SharePoint attachments

Resolved in Pega Version 8.2.8

When an application was using SharePoint to store the attachments, adding an attachment in an offline-enabled mobile app and then synching resulted in the mobile app crashing if the user re-logged in and launched the same work object. This was due to the attachment handling. Attachments are downloaded during synchronization and they are base64 encoded: when a mobile phone processes the synchronization response, it decodes the base64 encoded attachment and saves the data in internal storage. In this scenario, attachments retrieved from SharePoint (REST Service) use a base64 conditional encoding that is different than in case Repositories or Pega Database storage. To resolve this, a check has been added to determine whether the base64 text contains newline characters, and if so the text is merged into one line.

INC-132859 · Issue 573486

ProductInfoReader updated to fetch only most recent version information

Resolved in Pega Version 8.2.8

Hfix scanner has been modified so that ProductInfoReader.runQuery will fetch only latest version of DAPF instances during a scan.

INC-131942 · Issue 574322

Orphaned CSS reference removed from DisplayReport harness

Resolved in Pega Version 8.2.8

An intermittent invalid CSS error was appearing in the DisplayReport harness when an operation resulted in the regeneration of the harness content. This was traced to a reference to the workform_pyReportingSkin CSS, which was used in old reporting features and is not in use anymore. The reference has been removed to resolve this issue.

INC-135719 · Issue 580689

Corrected reference exception for filter on a grid sourced from a parameterized report definition

Resolved in Pega Version 8.2.8

An Invalid Reference Exception was thrown after attempting to apply a filter on a grid sourced from a parameterized report definition. This was traced to work done to allow cross-scripting filters to allow filters to contain special characters, and has been resolved.

INC-140110 · Issue 600399

Large filter values accepted in Report Definition edit

Resolved in Pega Version 8.2.8

Report definition edit filter values were not accepting large comma separated values properly. This has been resolved by modifying the logic in RRFilters_Logic to use ReportFilter.getReportFilters.

INC-143191 · Issue 596470

Scheduled tasks landing page shows all tasks

Resolved in Pega Version 8.2.8

Due to pzGetScheduledTasks listview having a hardcoded limitation of 500 records to be fetched, not all scheduled tasks were being shown in the scheduled tasks landing page. This has been resolved by modifying the pyCreateSummary activity to use a newly created Report Definition to fetch data instead of list view.

INC-144756 · Issue 602724

Security improved for searches

Resolved in Pega Version 8.2.8

Authentication requirements have been added to activities associated with searching.

INC-120343 · Issue 573075

Explicit parent added for descendants in subreport to correct summary

Resolved in Pega Version 8.2.8

When using a Report Definition with a Summarize column and a subreport with join class, it was not considering implementation class work objects. As a result, the prepared values were only partially computed. This was traced to the SubReport in SetQuery not having reference to a parent for the descendants classes, and has been resolved by explicitly setting the parent value.

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