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

SR-D19299 · Issue 511323

Support added for calling Export to Excel directly from Report Definition

Resolved in Pega Version 8.2.5

When using Export to Excel directly from a report definition, a date column specified using pxDatetime was shown as applied date format in the resulting Excel file. The column was formatted as expected if the export was called from an activity. This was traced to the recent refactoring of Export to Excel: it was not expected that it would be called directly, but rather that it would be invoked from a report viewer ruleform. In order to support this direct use, step calls have been added to the pzRDExportWrapper activity to call pzMergeAutoGen before the engine call. This step will merge the pyModes pages from pxDateTime control.

SR-D34655 · Issue 513421

Deferred load works inside custom row section of Report Definition

Resolved in Pega Version 8.2.5

Deferred Load was not working inside a custom row section of a report definition. This was traced to the non-auto-generated mark up written for the customRowSection include not having the node_type="MAIN_RULE" name="BASE_REF" id="RULE_KEY" base_ref="" attributes. This led to the load manager which performs the defer load to get the base_ref as "pyReportContent" from the "ReportDisplay" section dom node. To resolve this, the RRDataListGeneration has been modified to set the proper base_ref to customRowSection include so the context/base_ref is passed to the customRowSection.

SR-D36265 · Issue 509607

Export to Excel total result count disabled

Resolved in Pega Version 8.2.5

After upgrade, an imported report with more than 30k records took an excessive amount of time (6-7 minutes) to be exported to Excel after being run, and the resulting Excel file only contained one record. A child report having around same number of records was exported successfully in around 30 seconds. Analysis showed that during the export process, a thread dump was originating from the thread responsible for performing export. Co-relating this with alert logs showed a PEGA0042 alert around the packaging of the query. This was traced to the paging settings on the pyContentPage not getting properly set from the activity pxRetrieveReportData on step 14: the boolean that sets .pyContent.pyPaging.pyReturnTotalResultCount used a page that will always be empty on the upgraded system, leading to an error in calculating the total result count. To resolve this, fetching the total result count on Export to Excel has been disabled.

SR-D37115 · Issue 515839

Onclick handler updated to resolve Report Definition UI issue

Resolved in Pega Version 8.2.5

After modifying the function logic in Report Definition, reopening it in the configuration modal dialogue displayed the function multiple times and it was not possible to open/edit the function. This issue was cosmetic and related to the UI representation of functions: the underlying clipboard page had the correct details regarding the custom logic and functioned as expected. Investigation showed the UI error was related to the onclick handler, and this has been resolved so the system correctly removes the onclick handler when required.

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