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-D43776 · Issue 510763

Clipboard ExecuteActivity button updated to get classname

Resolved in Pega Version 8.4

In Clipboard, clicking the execute activity button did not trigger any action in the backend. Investigation showed that previously the ID attribute for the HTML element used to be same as the property name, and the value of property "pyClassName" was found in the document.getElementById function. Due to work done to provide a feature that generates unique IDs for UI elements (auto generated controls), this must be done through other functions such as document.querySelector to get the value of the property from DOM. The necessary updates have now been made to the javascript function in control pzExecuteActivityButton.

SR-D47975 · Issue 514014

OpenRuleAdvanced updated

Resolved in Pega Version 8.4

After upgrade, the Update Page and Append and Map to step in Data transform was generating the error "No Server connection while giving page name to Target and Source". This was traced to the OpenRuleAdvanced_OverLabel control, and investigation showed that a variable was not being resolved when invoking pzEncryptURLActionString. This has been resolved by updating OpenRuleAdvanced and reimplementing two parameters as well as moving the call of these variables to the beginning of the script. Security has also been improved by moving some of the encryption to SafeUrls.

SR-D48248 · Issue 517239

XSS filtering added to URLs

Resolved in Pega Version 8.4

XSS filtering has been added to prevent the injection of a script into a URL using ViewXML.

SR-D48751 · Issue 515538

Pega unit for case type records user inputs

Resolved in Pega Version 8.4

When creating a Pega unit for the case type by selecting Actions -> Record test case for Case, the user inputs were not recorded for embedded page properties. This has been corrected.

SR-D52138 · Issue 537507

Property setting corrected for On Join and Exclusion shapes in Expression Builder

Resolved in Pega Version 8.4

The properties for the defined page did not appear when using the type-ahead feature to select properties for the On Data Join and Exclusion shapes in Expression Builder. This was an issue related to the property being referenced for setting the context in the expression builder, and has been corrected.

SR-D65401 · Issue 528958

Parameter page retained after strategy test case checkout

Resolved in Pega Version 8.4

After a test case for a Strategy was created, it passed in the initial run but then failed after checkout of the test case. This was traced to an issue with the activity pzCheckAndUpdateParameters for strategy, and has been corrected.

SR-D67614 · Issue 527487

Tracer issues resolved for Google Chrome broswer

Resolved in Pega Version 8.4

Tracer was running in the background even after the tracer window was closed. Attempting to run a Tracer in this condition resulted in an error indicating the Tracer was being run by another operator and should be restarted, and in the Dev environment, attempting to start a Tracer once it was closed resulted in the message "Cannot launch multiple Tracer sessions for a requestor." Investigation found that the Tracer session was not being closed when the tracer window was closed because the browser specific method intended to do so was not being called. This was found to be an issue caused by the Google Chrome browser changing the signature of the method, and has been resolved by updating the method name in the TraceMain HTML rule.

INC-164439 · Issue 657994

Setting added to customize using blank Map values

Resolved in Pega Version 8.5.5

After upgrade to from Pega 6 to Pega 8 some of the Map Value rules were not working. This was due to the handling for blank default values which was changed in Pega 7. In order to support backwards compatibility, a new 'when' rule has been added which allows customizing whether or not blank values are allowed for the Map value default columns. pyAllowBlankValues will default to "false".

INC-165256 · Issue 657036

Improvements for Offer Eligibility rules loading time

Resolved in Pega Version 8.5.5

After opening the Proposition filter/Action rule and clicking on Add Criteria, the pxAnyPicker drop down load was taking an excessive amount of time. Performance improvements have been made by adding a precondition at step 2 to avoid data page refresh for specific scenarios when it is not required.

INC-168914 · Issue 659661

Updates added against Cross-site Scripting

Resolved in Pega Version 8.5.5

Cross-site Scripting (XSS) protections have been updated for the UI.

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