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.

SR-D37275 · Issue 519027

Enabled PDF attachment for iPad Safari

Resolved in Pega Version 8.1.8

It was not possible to select the PDF option when attempting to attach a file while using iPad Safari. This has been corrected.

SR-D76134 · Issue 542160

"Offline" icon shows when simulating offline mode

Resolved in Pega Version 8.1.8

When simulating offline mode by selecting "Settings->SystemInfo->Simulate Offline checkbox" and moving to MyWork, "Offline" did not appear in the header. This has been corrected.

SR-D71408 · Issue 534932

DIrty check flag triggered by adding columns and filters

Resolved in Pega Version 8.1.8

If a report was edited and closed without saving, the dirty check worked as expected. However, if new columns or filters were added and the report closed without saving, the dirty check did not appear. This has been resolved by updating the check logic.

SR-D53176 · Issue 541793

Error when adding function filter will persist

Resolved in Pega Version 8.1.8

When an exception occurred while adding a filter in the report viewer, the error was shown but cleared due to an immediate refresh of the parent section. Analysis found that step2 of pzGetFiltersFromContent was failing, after which the error was shown, the section reload happened, and the error disappeared. To resolve the error being cleared prematurely, the pzOnLoadReloadReport control has been modified so that when there are messages on the top level page (pyReportContentPage), a parameter will be set on HarnessContextMgr to not to clear them during the next refresh call.

SR-D76204 · Issue 543591

Index conflict resolution logic updated

Resolved in Pega Version 8.1.8

After configuring a dedicated index on delivered Class - PegaCA-Interface-Contact, trying to generate the index resulted in an error indicating a type conflict in delivered classes/properties. This has been resolved by updating the conflict resolution logic.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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