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-182150 · Issue 669853

DSS added to control Pega Version Banner

Resolved in Pega Version 8.7

Nuisance errors were being logged related to the application trying to connect to Pega to confirm available versions. This has been resolved by adding the 'when' rule pyShowVersionBanner to pzStudioHomeWrapper which allows disabling/enabling the Version Banner based on the setting used in the DSS ShowVersionBanner. pyShowVersionBanner defaults to true when DSS ShowVersionBanner does not exist.

INC-220652 · Issue 721384

Added explicit clearing for AsyncServiceManager cache

Resolved in Pega Version 8.8

Heap size for multiple JVMs increased after update. Investigation showed data pages loaded via Load-DataPage during service processing using requestor pools were cleared after each service interaction but the AsyncServiceManager cache was not cleared. To resolve this, an update has been made that will clear the async cache when the requestor is returned and when flush all is called.

INC-175990 · Issue 652089

Browser check added to ensure on-click event trigger

Resolved in Pega Version 8.7

Clicking Submit from the screen after opening the case from the worklist did not trigger the click event action when using Microsoft Internet Explorer 11. This was due to a change in that browser, and has been resolved by adding a check.

INC-221955 · Issue 719288

Archival association supported without data retention policy

Resolved in Pega Version 8.8

Previously, configuring an archival association when the data retention policy had not been created resulted in an error and the associations were not saved. Handling for this use has now been added in order to support the archival of custom-associated data.

INC-234874 · Issue 739874

Cursor moves via arrow buttons

Resolved in Pega Version 8.8

Using the keyboard arrow buttons to navigate between numbers was not working. Nothing happened when clicking on the left arrow, and clicking on the right arrow moved the cursor to two digits. This has been resolved by updating pzpega_control_textinput.

INC-220770 · Issue 718026

Null check added to getBaseRef

Resolved in Pega Version 8.8

When using a customized Cosmos portal that included tabs, some of the Pega APIs were not available in the child frame and javascript errors were generated when calculating the clipboard path for live UI elements. This was traced to invalid references to "pega.api.ui.util.getBaseRef", and has been resolved by adding null checks to the getBaseRef API call to make sure javascript errors are not thrown.

SR-D6978 · Issue 481763

Mandatory field confirm popup text and focus corrected

Resolved in Pega Version 8.1.6

When a mandatory field is tabbed out (with TAB key), using cancel to proceed to the next field instead retained the focus in the same field. This was traced to work previously done to prevent an infinite confirm dialog loop, and has been corrected.

SR-D37326 · Issue 504935

Resolved clipboard formatting issue in Reply Thread and Send Correspondence

Resolved in Pega Version 8.2.4

Issues were seen with the table formatting of client data after mail was sent. This has been resolved by ensuring all borders are retained in RTE when used in both "Send Correspondence Task" and "Reply Thread".

SR-D42143 · Issue 509316

Tab names maintained after Ajax container refresh

Resolved in Pega Version 8.2.4

When using an Ajax container in Tabs mode, a browser refresh with multiple tabs opened caused the active tab name to be changed to the main tab name. This was caused by the work object name being lost during the refresh, and has been corrected.

INC-180762 · Issue 666291

Calendar gadget correctly displays event of >31 days

Resolved in Pega Version 8.8

When using the pxCalendar gadget to display a hotel reservation of duration > 31 days, the entire bar was not displayed on the PEGA calendar. Investigation showed that eventslist was not considering the month value, and this has been resolved by updating the pzEventPreProcessing activity to check for month.

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