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-D91344 · Issue 560627

Resolved PageCannotBeSerializedForPassivationException in logs

Resolved in Pega Version 8.1.9

The exception "One or more properties could not be serialized during passivation and have therefore been lost. They will not be available on activation. Please ensure that all property data is Serializable" was observed in the logs. Investigation showed there was an HTML fragment in 'pzGridOpenAction' that was adding non-serializable properties to the clip board. This did not cause a functional issue, but has been resolved by modifying the way the system obtains and reuses the class definition.

SR-D91964 · Issue 551093

Negative values in optimized table filters show markup

Resolved in Pega Version 8.1.9

HTML markup was shown in the filter popup when Number control was used in a Table cell and there were negative values in the cells at runtime. This was traced to work done on template grid filtering, and has been corrected.

SR-D92571 · Issue 553116

Corrected ReportBrowser refresh section

Resolved in Pega Version 8.1.9

After bringing up the popup menu on a report shortcut in the report viewer and then dismissing it, the gear icon on the shortcuts in the upper section of the report browser stopped responding. This has been resolved by updating the system to refresh the pyReportBrowserInner section instead of pyReportBrowserAll.

SR-D99100 · Issue 564381

Character counter updates correctly with RDL refresh section

Resolved in Pega Version 8.1.9

When using a repeating dynamic layer with a refresh section, the text area character counter was not accurate. This was traced to the system sourcing server-side metadata for the remaining character count and refresh section updating the same remaining count to all textareas. This has been corrected by recalculating the count for each template rendering of textarea so that it works correctly inside templatized repeating structures.

INC-128279 · Issue 591379

Layout Group tab alignment correctly shown in Microsoft Internet Explorer

Resolved in Pega Version 8.1.9

Even though the responsive breakpoint for a layout group was disabled, the tabs were getting changed to Menus in Microsoft Internet Explorer. This was traced to Tab-overflow being triggered in very small viewports when using Internet Explorer 11, and has been resolved by adding DOM manipulations for all layout groups.

INC-131151 · Issue 572831

Resolved empty body for Reject email

Resolved in Pega Version 8.2.8

When using the pzEmailActions Section in Correspondence for Approve/ Reject functionality via email, there was no reply body in the email for Reject Option. This was due to the flow action for the Reject email being different than that of the Approve email, and has been resolved.

INC-131385 · Issue 573453

Swagger APIs updated

Resolved in Pega Version 8.2.8

The Swagger File APIs have been updated to ensure swagger document files generated meet specifications for editor.swagger.io .

INC-134370 · Issue 577633

Expanded Grid locking updated

Resolved in Pega Version 8.2.8

When using pyDashboadMyWorkList to show the cases of an operator with Master Detail in Read Only mode, the system was acquiring a lock on the expanded work object. To resolve this, the following changes have been made: - In activity Assign-pyAcquireObject, If the parameter bRODetails is true, do not call acquireWorkObject and do obj-open-by-Handle to get assignment and work page in pyAcquireObject activity. - In activity acquireWorkObject, the parameter skipWorkLock has been removed as acquireWorkObject should always acquire the lock.

INC-134557 · Issue 585646

Dropdown populated with parametrized data page source

Resolved in Pega Version 8.2.8

When configuring dropdowns or autocomplete controls with parametrized data page as a source in a section, the parameter configuration values and parameter names were not sent in the JSON created by the DX API view. This has been resolved by adding parameter support for DataPages in Dropdown, Autocomplete, and Radio buttons.

INC-134709 · Issue 579436

Updated endpoint Cross-site scripting protection

Resolved in Pega Version 8.2.8

Cross-site scripting security has been updated for Endpoints in Display activities.

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