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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-C31307 · Issue 355606

Attachment saved to external storage retains new name

Resolved in Pega Version 8.1

When files were saved in external web storage (configured via app definition "Integration & Security tab), an attachment name that was changed from the default was reverting to the default name when attached again. Handling has now been added to pzSaveToWebStorage to retain the override name for the file.

SR-C31469 · Issue 371885

PageList properties for List assertion resolve to correct class

Resolved in Pega Version 8.1

Errors indicating "pyStepPage can not be empty for List card" occurred when attempting to save Strategy related Test cases. This was traced to the system not not resolving to the correct class instance type when loading PageList properties for List assertion in strategy related Test cases, and has been corrected.

SR-C31617 · Issue 373206

Tooltip display fixed for two similar sections on the same screen

Resolved in Pega Version 8.1

A Tooltip was improperly displaying two similar sections on the same screen If the same section was included twice (similar sections), and if Smart Info was configured to one element, the tool tip was shown for the first element instead of the element action in which an action was done. This was caused by an element targeting error and has been corrected.

SR-C31733 · Issue 371646

Column Populator utility documentation clarifies pxInsKey ordering

Resolved in Pega Version 8.1

Due to confusion about the functioning of the Column Populator utility, comments have been added to the prpcUtils.properties file to clarify that the pzInsKey column contains strings and therefore uses lexicographical ordering and not numeric ordering.

SR-C31755 · Issue 373526

Updated LinkAttachmentstoCase for Data-Corr-Email attachments

Resolved in Pega Version 8.1

Data-Corr-Email attachments were not getting copied to Service Cases in NLP. This was due to the pxLinkAttachmentToCase activity attempting to read pyNote from the DataAttachPage when pyNote is blank for Corr attachments. To resolve this, pxLinkAttachmentToCase has been updated to use pyLabel if pyNote is empty.

SR-C31812 · Issue 371890

Fixed Runtime Toolbar access issue with Japanese locale

Resolved in Pega Version 8.1

The Runtime Toolbar in the Case Manager Portal screen could not be re-opened when using the Japanese locale unless the screen was reloaded by hitting the "F5" key. This was an issue with the localized value of Title not being properly handled for comparison when using the Google Chrome browser, and code has been added to resolve this.

SR-C32016 · Issue 374775

Handling added for JSON generation when special characters are given in operator fullname

Resolved in Pega Version 8.1

If an operator rule was saved with a special character (for example Horizontal Tab) in the full name field, it resulted in pyGetOperatorsForCurrentApplication producing an invalid JSON object. In order to correct this, the JSON created in step no 3 in pyGetOperatorsForCurrentApplication activity will use @(Pega-AppDefinition:Utilities).pzEscapeJSONSpecialCharacters() for .pyUserIdentifier (operator ID) and .pyUserName (Full Name).

SR-C32033 · Issue 371520

Locking modifications and Hazelcast upgrade added to remove OOM error for advanced agents

Resolved in Pega Version 8.1

Using advanced agents which have the option "Run this agent on only one node at a time" caused the system to take a key-based cluster-wide distributed lock on a distributed map, causing the node which had the distributed map to become unresponsive due to OOM. The subsequent OperationTimeoutException caused the agent to be terminated as per the functionality of agents. The resolution for this is in two parts: a tryLock() has been added to the Distributed Map Layer, and support has been added for Hazelcast enterprise edition EE 3.10 in place of v.3.8.

SR-C32097 · Issue 371954

Improved logic for CorrNew activity email IDs

Resolved in Pega Version 8.1

When there were only two work parties and their email IDs were same, for example using a Bcc address, the formation of email ID string to CorrNew activity included an extraneous quote mark that caused the email to fail. The formation logic has been reworked to resolve this problem.

SR-C32153 · Issue 366706

Autocomplete tags and screen mask corrected in Mobile

Resolved in Pega Version 8.1

On mobile devices with full screen enabled and an autocomplete control configured with onchange -> refresh section, entering some value and pressing the Enter / Go button in mobile refreshed the section but the full screen mask was not properly removed and tags could not be added. To correct this, a check has been added.

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