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-117923 · Issue 171578

Remedied spurious size alert from the attachments viewer

Resolved in Pega Version 7.1.7

When listing attachments from History & Attachment display, the work object was re-read for each attachment. If the work object had many attachments, the alert "PEGA0004 alert (50MB DB threshold)" would appear regardless of the actual attachments' size. This has been adjusted so the RUF attachment access makes use of the existing WorkPage instead of re-reading it from the database.

SR-118061 · Issue 175102

CorrNew activity can send email in sync or batch

Resolved in Pega Version 7.1.7

When attempting to send email correspondence in synchronous mode i.e. not via the agent processing, the activity always queued it to the agent even when the Activity CorrNew SendNow param was set to true. To correct this, the system will pass the value of a BatchSend param based on the value of the SendNow param: email will be sent immediately If SendNow is set to 'yes', or will be queued for batch processing if SendNow is set to 'no'.

SR-118170 · Issue 171859

Property History TaskName field expanded

Resolved in Pega Version 7.1.7

Previously, the TaskName field was limited to 32 characters. This has been expanded to 128 characters.

SR-118190 · Issue 172520

Drag and drop work reassignment corrected

Resolved in Pega Version 7.1.7

An error was found that prevented the ability to drag and drop a request from workbasket to worklist or from worklist to workbasket in the Case Manager portal. This has been corrected.

SR-118738 · Issue 172565

Handling corrected for drag and drop image attachments from Outlook

Resolved in Pega Version 7.1.7

If a document containing an image was added to a work object from Outlook via drag and drop, it would be corrupted when opened. This was caused by an encoding/decoding mismatch - the encoding differed depending on whether the file was first saved to the desktop or not, but the decoding did not take that into account. This has been corrected.

SR-94370 · Issue 119519

AddChildWork updated to allow child case creation from step flows

Resolved in Pega Version 7.1.7

When attempting to create nested sub cases for rows in a page list with a Split for Each sub flow by calling the pyCreateSubCases flow, an error was generated. There was a workaround of using a utility shape to call pxAddChildWork instead of a split for each calling pyCreateSubCases, but pxAddChildWork has been updated in order to allow creating child cases using the step page as the primary page and not always defaulting to pyWorkPage.

SR-113396 · Issue 162534

Smoothed background Bulk Processing processing

Resolved in Pega Version 7.1.7

If the setting for BPUnitsToProcessForeground is given as 0 in all cases, attempting to run Bulk Processing in the background failed and logged an "Index out of bound" exception in the system logs. To cover this condition, a check has been added to handle zero items in the foreground processing when running background Bulk Processing.

SR-113919 · Issue 170809

Made page displays consistent between Java versions

Resolved in Pega Version 7.1.7

"pxflow" pagegroup values in pywork page were being placed differently depending on the version of Java used in the environment. This was caused by a handling error in situations where there is no classname, and has been fixed.

SR-114882 · Issue 164513

Validation error display corrected for screen flow harness

Resolved in Pega Version 7.1.7

Inconsistencies were appearing in the error display on the harness of the screen flow. The issue was due to the "Allow errors" value being set to true even when "Save on last step" was unchecked. While there was a workaround of unchecking both "Allow errors" and "Save on last step" options, this has been fixed.

SR-117855 · Issue 171394

Resolved NPEs during case creation

Resolved in Pega Version 7.1.7

If a null pointer error was generated during the case creation process, all subsequent records being processed also generated the error. This issue occurred when adding and later removing work party data, and was found to be related to a stack trace not being generated for the reported issue and an attempt to index a change to a page that's no longer available. To correct this, a code change now handles the condition which caused the NPE (writes an index for a non-existent page and then skips it) then logs information for analysis.

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