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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-C60129 · Issue 401825

Removed default height from pzTimeline_PresentationTab

Resolved in Pega Version 8.2

When using Timeline Control, the Default Height in the presentation tab was not being removed when it was changed to be blank and saved. When the control was opened the next time, it defaulted to show Height 300px and remained at that value despite repeated attempts to blank it. This was traced to a default height in the "pzTimeline_PresentationTab" section, and this default has now been removed.

SR-C71043 · Issue 411254

pzSendEmail returned to revious behavior of sending separate emails to work parties

Resolved in Pega Version 8.2

After upgrade, a change in behavior was seen when using the pzSendEmail activity. When pzSendEmail was called to send emails to work parties, a single email is sent to all recipients instead of separate emails to each recipient as it did in earlier versions. The SendSimpleEmail activity accepts a SendDiscreteMails parameter, the pzSendEmail activity has 'Pass current parameter page' checked so the default value for the SendDiscreteMails parameter was not used. This was a backwards compatibility error, and has been corrected by setting the SendDiscreteMails parameter to true by default in the pzSendEmail activity.

SR-C77088 · Issue 415532

Updates to controls and labels

Resolved in Pega Version 8.2

Issue 413604:When configuring a button with a disable condition, the condition was not returned in the readonly field. The PegaAPI has now been updated to support "disable". Issue 413597 / 413598: While calling the API to get the view of the screen as a JSON format, button type controls were not returning the label of the field using the OOB pxButton control. This has been fixed. Issue 413625: The PegaAPI section was missing when using clipboard page or data page with the rest method. To correct this, support for Embedded page has been added in the pyWorkPage for PegaAPI. Issue 415532 / 415533: When using the Pega API to get action details applied to an assignment (using the API GET {{url}}/assignments/assignmentID/actions/actionID), the control format value was not returned by the API for pxButton controls and other non input type controls like pxLink. It did work for input type controls like Text Input and Dropdown. This has been fixed by adding support to the control format for modes(1) and modes(2).

SR-C61154 · Issue 411073

Improved DB stability and retry for issues with RetryContext$ExceptionForDatabase

Resolved in Pega Version 8.2

The agent was crashing when there was a report using a pr_read_from_stream for the 'where' clause combined with a postgres version with 'on pr_read_from_stream'. This has been addressed by improving the stability of the database and adding code to better handle reconnect and retry when there is a database problem.

SR-C64292 · Issue 405248

Corrected multiselect dropdown event handling for IE11

Resolved in Pega Version 8.2

When using IE, multiselect dropdowns would work correctly the first time they were displayed, but disappeared on subsequent clicks. This has been fixed by correcting the event handling for IE11.

SR-C77459 · Issue 416897

Report tab names are correctly maintained after refresh

Resolved in Pega Version 8.2

When multiple reports are opened and the browser is refreshed, the tab names/labels failed to show up on reload. This was caused by an error in the method used to set the tab label, and has been corrected.

SR-C71053 · Issue 413208

Added handling for defer-loaded dynamic layout inside a flowaction grid

Resolved in Pega Version 8.2

When using a grid configured to show the details in expandable rows and the inner grid was a work bound grid, trying to expand the rows only showed the "Loading ..." message and never completed. This was traced to a missing use case for having a defer-loaded Dynamic layout which wraps the grid inside a flowaction embeddedpane grid, and has been corrected.

SR-C73608 · Issue 415510

Updates to controls and labels

Resolved in Pega Version 8.2

Issue 413604:When configuring a button with a disable condition, the condition was not returned in the readonly field. The PegaAPI has now been updated to support "disable". Issue 413597 / 413598: While calling the API to get the view of the screen as a JSON format, button type controls were not returning the label of the field using the OOB pxButton control. This has been fixed. Issue 413625: The PegaAPI section was missing when using clipboard page or data page with the rest method. To correct this, support for Embedded page has been added in the pyWorkPage for PegaAPI.

SR-C72114 · Issue 413597

Updates to controls and labels

Resolved in Pega Version 8.2

Issue 413604:When configuring a button with a disable condition, the condition was not returned in the readonly field. The PegaAPI has now been updated to support "disable". Issue 413597 / 413598: While calling the API to get the view of the screen as a JSON format, button type controls were not returning the label of the field using the OOB pxButton control. This has been fixed. Issue 413625: The PegaAPI section was missing when using clipboard page or data page with the rest method. To correct this, support for Embedded page has been added in the pyWorkPage for PegaAPI.

SR-C74858 · Issue 413603

Updates to controls and labels

Resolved in Pega Version 8.2

Issue 413604:When configuring a button with a disable condition, the condition was not returned in the readonly field. The PegaAPI has now been updated to support "disable". Issue 413597 / 413598: While calling the API to get the view of the screen as a JSON format, button type controls were not returning the label of the field using the OOB pxButton control. This has been fixed. Issue 413625: The PegaAPI section was missing when using clipboard page or data page with the rest method. To correct this, support for Embedded page has been added in the pyWorkPage for PegaAPI.

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