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.

INC-128923 · Issue 594161

Cross site scripting security update

Resolved in Pega Version 8.6

Cross site scripting protections have been added to OpenNoteDetails.

INC-132590 · Issue 590493

Exported Excel from Decision Table wraps correctly

Resolved in Pega Version 8.6

After upgrade, entries were displayed in a single line on exporting a decision table to Excel despite WrapText cell formatting being set. This was traced to the WrapText cell formatting set under the UpdateGridCells() function being overridden inside an addDataFormat() function callas part of DecisionTableWorkBookConverter.java. This has been resolved by adding the new function "setWorkAreaCellStyles" and calling it after generateWorkbook() function call of super class (AbstractWorkBookConverter.java).

INC-132930 · Issue 600294

Updated UpdateDateTime handling for branch merge SaveAs

Resolved in Pega Version 8.6

After Pega API's standard branch/merge service was consumed, the service was not returning response as expected due to the system encountering listing conflicts on the branch merge. The error "a rule in lower version has been updated more recently than when the checkout was created" was generated. This has been resolved by updating the Record API (pxUpdateRecord / pxCheckIfStale) to handle setting pxMergedSynchronized property to the pxUpdateDateTime of the base rule instance when doing a Save As into a branch ruleset from a non-branch ruleset / non personal ruleset. Please note - this fix is only applicable to Record API SaveAs, and will not work if customized logic is used to perform the SaveAs.

INC-136186 · Issue 592969

JAWS reads the name of the field/instructions

Resolved in Pega Version 8.6

JAWS was not reading the name of the field/instructions in a work group. This has been corrected.

INC-136187 · Issue 596093

Mask hidden as expected in small window/tablet view with Dragon

Resolved in Pega Version 8.6

When using Dragon in a small window/tablet view, the mask was not getting removed as expected. Performing a mouse click on the tab was successful for hiding it. To resolve this, Data-portal!pzProfileMenu has been modified to run the script removeScreenLayoutMask after clicking Profile, Preferences, Operator, Access Group, and My Favorites > Edit .

INC-139300 · Issue 590272

Additional security for encrypted passwords

Resolved in Pega Version 8.6

Handling and cleanup has been updated for encrypted values to enhance security.

INC-139337 · Issue 595221

RefreshRequestors security update

Resolved in Pega Version 8.6

Security improvements have been added for RefreshRequestors.

INC-140272 · Issue 595253

Report definition performance improvement

Resolved in Pega Version 8.6

Performance issues were seen with the pzOperatorsByWorkGroup report definition. This was traced to the report definition is adding an UPPER function for edit filter properties which caused it to take more time to run when combined with an ignore case check in the filters of the RD. This has been corrected.

INC-140789 · Issue 597800

Added handling for validation after inactivity

Resolved in Pega Version 8.6

A Validate rule was configured to add an error to a field if MyPageList had any page where MyProperty was not empty. The rule worked correctly if there was no pause in using the UI, but if the UI was left for a few minutes and then the field was changed, the Validate rule always evaluated the expression to true. This has been resolved by adding a null check in Utilities.countInPageList() function.

INC-141261 · Issue 595465

Document generation corrected for table outcomes

Resolved in Pega Version 8.6

An issue with generating a Microsoft Word file of table outcomes using the Document generate smart shape was traced to the system not being able to parse the necessary details from a referenced page group. This was caused by a syntax error for regex in the document file, and has been resolved.

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