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-D54984 · Issue 529208

Resolved ruleset save issue for Google Chrome/IE

Resolved in Pega Version 8.1.8

When using particular versions of Google Chrome or IE, the intermittent error "pyComponentInterfaceClass: <user> does not exist or is not a valid entry for this ruleset and its prerequisites" appeared when attempting to validate an application, and the ruleset could not be saved. This was traced to changes made in the browser around password handling, and has been resolved by explicitly clearing out the pyComponentInterfaceClass if that value is not in use.

SR-D70447 · Issue 533598

SQL injection protection added to Circumstanced Search

Resolved in Pega Version 8.1.8

Parameters used by the PegaAccel-Task-CircumstanceSearch.pzGetCircumstancePropValues activity are now encoded to prevent SQL injection attacks.

SR-D72672 · Issue 536387

Security updated for CreateOperator

Resolved in Pega Version 8.1.8

In order to improve security, CreateOperator in Pega-ProCom will require authentication to run with pxCanManageUsers privilege.

SR-D75469 · Issue 538120

Resolved null-pointer exception in Expression Builder launch from activity rule

Resolved in Pega Version 8.1.8

A NullPointerException occurred in SafeURL when trying to launch the Expression Builder from an activity rule. This was trasced to a failure to get a value property in a target field due to the target element and its parent element containing the same value for name attribute. This caused the parent element to be considered instead of the target element. To resolve this, the search for the target element in parent tag will use '$p' along with 'target element name' in query selector.

SR-D87673 · Issue 548628

PegaCESvcsIntegrator security updated

Resolved in Pega Version 8.1.8

Security updates have been made which now require authentication to consume the services from the PegaCESvcsIntegrator package.

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.

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