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-D40605 · Issue 510917

Corrected mobile password control behavior on failed validation

Resolved in Pega Version 8.2.5

Given a section on mobile where the out-of-the-box password control was used on a textbox with input field of type Password to set a new password, failed validation on the field caused the cursor on the input field to jump to the left. It was then not possible to delete the text or correct the placement of the cursor. This was traced to a missing type check for password in isTextBox(), and has been corrected.

SR-D42437 · Issue 513648

Pulse @mention will avoid triggering search request if no suggestion list is available

Resolved in Pega Version 8.2.5

Search threads were causing requestor Lock Exceptions due to poorly optimized queries sent to ElasticSearch when a Pulse mention was attempting to look up a person (e.g. "@"+typing) and the search of case objects to match to that search were performing poorly. To resolve this, an update has been made to avoid triggering requests if the suggestions list is not available for the search query.

SR-D43272 · Issue 516440

Local user lookup modifed to use requestor level data page to improve performance

Resolved in Pega Version 8.2.5

In a system with many users (over 40k), attempting to search for a user to send a private message was taking an excessive amount of time. Analysis found that all of the users were being loaded at once in a page list of type Code-Pega-List. This led to errors indicating the Page List property had more elements than the specified threshold, but pagination could not be added as the activity and Report Definition are final. To improve performance, this process has been modified to use a data page at the requestor level instead.

SR-D44012 · Issue 509881

Added more error handling in pzCreateThumbnail

Resolved in Pega Version 8.2.5

In activity pzCreateThumbnail, a null pointer error was generated at step 2. This was traced to the value of originalImage being null even though there was no error in the image file itself, and has been resolved by adding an error check .

SR-D50725 · Issue 516514

Page cleanup processes updated to facilitate Pulse Task creation

Resolved in Pega Version 8.2.5

Attempting to create a Pulse Task in an assignment resulted in a "The Operation completed successfully, but returned no content" screen after clicking submit. This was traced to an incorrect usage of createworkpage. To resolve this, the system has been updated so that before calling createworkpage, a page-remove will be done so createworkpage will not clean the assignment page.

SR-D53266 · Issue 516396

Synchronization continuation updated so mobile attachments properly preview

Resolved in Pega Version 8.2.5

Clicking on attachments in mobile would open them if the attachment had just happened, but otherwise would not open them at all. This was traced to an issue with Synchronization continuation: the page was properly loaded from database but its content was not used to fill the named OfflinePackage page (which contains only the search keys). This has been corrected by replacing the empty page with the one loaded from the database.

INC-175994 · Issue 667480

Removed redundant Microsoft Outlook email interaction chain

Resolved in Pega Version 8.5.6

When opening an email interaction case, the email editor user interface area showed the complete email chain of the email for every new message that came in related to the case. This was traced to the difference in the selectors that various email clients use to construct a response to an email with email history in it, and has been resolved by updating the selectors for Microsoft Outlook in pyRichTextEmailHistorySelector so no conversation is repeated when using that client.

INC-184155 · Issue 673073

Entity Detection prefers first detected entity

Resolved in Pega Version 8.5.6

Entity detection shown in the "Training data" tab of the email channel did not match with the results of running the corresponding text analyzer rule. This occurred when a single piece of text was detected as multiple entity values, which led to the last entity detected being picked for case mapping because of the unclear scenario of duplicate entities. To resolve this, pxmapresponseentities has been updated to prefer the first detected entity.

INC-184243 · Issue 682331

Page data preserved for WebChat timeouts

Resolved in Pega Version 8.5.6

Attempting to change the font size in Webchatbot after the interaction time-out resulted in a DisplayError screen. This was traced to the page data not being available, and has been resolved by preserving workPage and newAssignPage for this use.

INC-184902 · Issue 669451

Corrected portal image display for authenticated request

Resolved in Pega Version 8.5.6

Email images for the user portal were not displayed in the browser but were showing correctly in the manager portal. The URL to the image was the same in both cases, however for the user portal the URL request was requiring authentication. This has been resolved by updating the API to use currentsessionURL.

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