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-166444 · Issue 642112

FlexModalTemplate Modal window size consistent

Resolved in Pega Version 8.6.1

The FlexModalTemplate modal window size was changing on second click. This was a missed use case for dirty dialog CSS implementation, and has been resolved by moving the CSS necessary into the isDirtyDialogOpen if condition.

INC-166561 · Issue 645650

ADM Models correctly updated

Resolved in Pega Version 8.6.1

The ADM models were not being updated when responses were processed either via the CaptureResponse API or when the time elapsed that should result in an update reflecting a non-response. This was traced to incomplete handling for a response coming for some other model which was converted to EMPTY, and has been resolved by modifying the logic so that the default responses and other responses are processed properly.

INC-163154 · Issue 638098

Code updated for bulk actions buttons

Resolved in Pega Version 8.6.1

After update, hovering over the "Filter case" button in pzBullkUpdate and the "Create" and "Clear" buttons in pzBulkAddActions caused them to disappear. The warning "This button generates markup that was used to support the older browsers. It is recommended that you update it to the newer markup" was shown, and an update code button appeared. Some custom rules exhibited the same behavior initially, but worked as expected after updating the code and saving them. This has been resolved by updating the buttons in pzBulkUpdate and pzAddBulkActions with the latest UI technologies used for button control codes.

INC-174475 · Issue 650108

Removed unnecessary commit in pyGetAttachmentsByCids

Resolved in Pega Version 8.6.1

Attempting to reply to inbound emails generated the error "This action is not allowed as it is outside the current transaction". Investigation showed a commit was occurring for pygetattachmentsbycids even when there was no change in attachment, and this interfered with the subsequent transactions and resulted in the Transaction id mismatch issue. To resolve this, the commit has been removed and the system has been updated to save only when needed for backwards compatibility.

INC-176385 · Issue 657671

Corrected blank lines for hidden report filter criteria

Resolved in Pega Version 8.6.1

When the report browser had five filter criteria for a report and only the last two were made visible due to conditions, three blank lines were shown above the visible filters. This was traced to the Report Definition column filter showing the grid row as empty space when "Filter Not Visible in Viewer" was selected, and has been resolved by adding an inline style to PzPromptGrid.

SR-D36970 · Issue 504985

Calendar icon updated to properly display the set number of years

Resolved in Pega Version 8.2.4

By default, the Calendar icon showed a date range of 10 years when -/+100 was expected. This issue was traced to the existing DSS setting (pyNumberofYears under Pega-UIEngine), which enables overriding the date year range, not being honored when the pyNoOfYears property was set to -1. To honor the pyNumberofYears setting, pyNoOfYears should be 21. This has been corrected so the value will be set properly.

SR-D36704 · Issue 504808

Repaired Pega validation report

Resolved in Pega Version 8.2.4

The Pega Usage validation report was not working. This was traced to the UVO O/P file having a null value and not containing any data regarding the environment daily usage. This has been corrected by updating the java used in getElementsByTagName.

INC-176734 · Issue 655178

Invalid manual time value stops progress and displays error

Resolved in Pega Version 8.6.1

When an invalid time was manually entered, eg. 11, the system previously remained in an error state until the time was corrected. Post-update, the current time of the user's session / browser was populated into the time field when an invalid time was entered. Although the error still displayed, the current time was saved and the user could continue. This has been resolved by adding a condition to show the entered time value and not continue if the entered time value is invalid.

SR-D60830 · Issue 533028

Logic update for classloading synchronization

Resolved in Pega Version 8.1.8

The synchronization logic for classloading has been updated to resolve intermittent deadlocking seen when two DataFlow threads are executing a distribution test.

INC-165964 · Issue 656816

Harness context set for modal dialog on interaction portal

Resolved in Pega Version 8.6.1

An AddDelete refresh condition on a page list property was not triggering a ReloadSection as expected. This was a special use case in the interaction portal where a modal dialog was opened but the harness context was not set properly, and has been resolved by ensuring the harness context is correct.

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