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.

SR-B7620 · Issue 289885

PopulateCaseContents activity updated

Resolved in Pega Version 7.3

The PopulateCaseContents activity has been updated to better handle missing or empty properties to ensure the flow name and RefObjectClass values are populated properly.

SR-B7620 · Issue 290018

PopulateCaseContents activity updated

Resolved in Pega Version 7.3

The PopulateCaseContents activity has been updated to better handle missing or empty properties to ensure the flow name and RefObjectClass values are populated properly.

SR-B7620 · Issue 289885

PopulateCaseContents activity updated

Resolved in Pega Version 7.3

The PopulateCaseContents activity has been updated to better handle missing or empty properties to ensure the flow name and RefObjectClass values are populated properly.

SR-B7621 · Issue 278634

Activity created cases open correctly

Resolved in Pega Version 7.3

When a case was created through an activity, an error was generated when opening the case and clicking to open assignment. This was traced to an incorrect page name being passed if the primary page was different, and has been resolved by modifying the CompleteAssignment activity Step 19 to check the precondition of Page name.

SR-B7739 · Issue 278003

Backward chaining updated to work with Load-DataPage

Resolved in Pega Version 7.3

A Read only Data Page configured with backward chained declare expressions worked in browser and batch contexts but not with the Load-DataPage method. This was traced to the backward chained expressions were not being triggered when the data page was loaded asynchronously, and that has been enabled.

SR-B7942 · Issue 284735

PDF barcode generation from eForm given configurable parameter checkbox

Resolved in Pega Version 7.3

When generating a PDF file based on an eForm that contains barcodes displayed via base64 encoded images, making the file read-only by using ConcatenateEForm's PerformFieldFlattening option prevented the barcodes from displaying. This was due to an "append" flag being passed to the 3rd party iText Library API "PdfStamper", and has been resolved with the addition of a flag (EnableNewVersion) in the "GenerateEForm" activity. The parameter will be by default true and may be unchecked for false, and is accompanied by a tool tip on hover of the checkbox as well as iText help.

SR-B7942 · Issue 285735

PDF barcode generation from eForm given configurable parameter checkbox

Resolved in Pega Version 7.3

When generating a PDF file based on an eForm that contains barcodes displayed via base64 encoded images, making the file read-only by using ConcatenateEForm's PerformFieldFlattening option prevented the barcodes from displaying. This was due to an "append" flag being passed to the 3rd party iText Library API "PdfStamper", and has been resolved with the addition of a flag (EnableNewVersion) in the "GenerateEForm" activity. The parameter will be by default true and may be unchecked for false, and is accompanied by a tool tip on hover of the checkbox as well as iText help.

SR-B796 · Issue 283050

Report Definition updated to handle null value field grouping

Resolved in Pega Version 7.3

Report Definitions gave a blank count when grouped by a field with null values. An unnecessary check has been removed from the GenerateGridHTML RUF to correct this issue.

SR-B796 · Issue 277684

Report Definition updated to handle null value field grouping

Resolved in Pega Version 7.3

Report Definitions gave a blank count when grouped by a field with null values. An unnecessary check has been removed from the GenerateGridHTML RUF to correct this issue.

SR-B7965 · Issue 291732

Resolved mobile case switching exception

Resolved in Pega Version 7.3

The console error 'Exception while trying to set work item as completed in assignment list' was seen while context switching a case in a custom mobile app. This was caused by the configuration calling submit during preprocessing, and has been fixed by ensuring the onSuccess callback of finishAssignmentAction is called when there is no next Task.

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