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-D44942 · Issue 518353

Guided tour popups handling added for right-to-left language locales

Resolved in Pega Version 8.1.8

Guided Tour Popups were still appearing in the default EN location after switching to the ar_AR locale. This was traced to a missed use case for locales using a right-to-left mode such as Arabic or Hebrew, and has been resolved by updating the guided tour engine openPopOver function to account for the HTML tag dir attribute for value of "rtl". This will anchor the pop over to rightBottom / and display the arrow on the rightTop instead of leftBottom / leftTop.

SR-D79266 · Issue 544531

pyStatusWork for parent case correctly resolved

Resolved in Pega Version 8.1.8

pyStatusWork was not getting updated for the parent case even though the case passed through the resolution stage. This was an unintended side effect of work done regarding resolving a subcase if it was opened from the review harness, and has been resolved by updating the findPageByHandle activity to return the correct page when there are multiple pages with the same key.

SR-D54963 · Issue 524113

Updated Decision Table validation for multiple OR conditions

Resolved in Pega Version 8.1.8

When the Decision Table had multiple OR conditions, the table was verified as consistent even when two rows had the same value. Analysis showed that when Show Conflicts encountered multiple 'or' conditions in a row that matched the same conditions in other rows, it considered them to be different rows. This has been corrected.

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-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.

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