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-153423 · Issue 615666

Timing update for Signature Capture Control

Resolved in Pega Version 8.4.4

A signature could be lost when using the signature capture control if a signature was drawn then the Accept and Submit links were clicked in quick succession. The problem occurred more frequently (although was not limited to) when there were multiple signature capture controls on the screen. This issue was due to transaction mismatch error for few pzAttachSignatureWrapper requests (signature post requests) caused by triggering the next accept request before completing the previous accept request. To resolve this, an update has been made to display busy indicator immediately when the first accept button is clicked.

INC-154290 · Issue 613471

Signature capture exception resolved

Resolved in Pega Version 8.4.4

The signature capture control was throwing a JSON parse exception when the value was set and section was refreshed. This was caused by the signature for PIMC passing incorrect data which Preview could not parse, and has been resolved by ensuring the correct data for PIMC local store.

INC-154495 · Issue 613700

Null check added to DT set action

Resolved in Pega Version 8.4.4

Attempting to open row item details in a repeating dynamic layout in which a data transform was called on click action resulted in the error "Failed to run data transform error ". This has been resolved by adding a null check in Set action.

INC-155214 · Issue 617007

GetBinaryFilesRef updated for resolving wildcard

Resolved in Pega Version 8.4.4

After upgrading from 8.2 to 8.4, errors related to "Unable to serve file java.lang.IllegalArgumentException: Illegal characters detected in the path" appeared numerous times during full syncs, either on first time login or after cache clear. This was traced to normalizeRelativePath failing, and was caused by a resource declaration in pzGetBinaryFilesRef that encountered an issue where wilcarded URLs were not automatically resolved while packaging Static resources. This has been resolved.

INC-155971 · Issue 616031

Handling added for missing data transform in offline mode

Resolved in Pega Version 8.4.4

A "data synchronization failed" error appeared when trying to login to a Mobile App that had offline mode enabled. The login worked when offline mode was not enabled. Investigation showed that when the pyDataTransformWhitelistForOffline application rule contained an entry for a data transform that did not exist, DataTransformPackager.canProcess() was throwing a null pointer error trying to access it. This has been resolved by adding a null check.

INC-156211 · Issue 620192

Verbose comments removed from wrapper

Resolved in Pega Version 8.4.4

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

INC-127102 · Issue 602699

Synchronized BatchStatus email available for multi-node

Resolved in Pega Version 8.4.4

An enhancement has been added which will handle synchronization between BatchStatus used in different events on different nodes and send email notifications.

INC-133482 · Issue 605004

Corrected isExternal flag not resetting

Resolved in Pega Version 8.4.4

If an extraction referred to external tables, an isExternal flag that was set to true during the Extraction process did not get reset to false for the tables which were not referring to external. This has been corrected.

INC-140110 · Issue 600400

Large filter values accepted in Report Definition edit

Resolved in Pega Version 8.4.4

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 596467

Scheduled tasks landing page shows all tasks

Resolved in Pega Version 8.4.4

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.

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