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.

INC-173382 · Issue 653442

Security update for previews

Resolved in Pega Version 8.7

Security updates have been made around the sanitizing of preview streams.

INC-173760 · Issue 658069

Table Filter save uses correct harness

Resolved in Pega Version 8.7

After creating a new view for table and then relaunching the portal or switching between tabs, the created views were not visible. Investigation showed that the views were saved under the incorrect pycaseworker harness on initial load, causing them to not be visible when returning from the switch and using the correct pyCWPortalContent harness. This has been resolved with the addition of the new parameter innerHarnessName to get the harness name when creating a personalization instance.

INC-173944 · Issue 660180

Cancel button on embedded GridRow cancels single action

Resolved in Pega Version 8.7

When a modal Flow Action contained a Table with the Row operations configured as Master-detail and the Detail flow action was specified, if a validation error defined in a Validation rule (i.e. other than required field error) occurred while entering details for one of the rows and the Cancel button for that row was clicked, the entire action was cancelled and the modal window was closed without saving anything. This has been resolved by updating the system to prevent the modal closure if a row is added and then cancelled.

INC-174020 · Issue 650891

Performance improved for Directed Web Access (DWA)

Resolved in Pega Version 8.7

Slowness when using a Directed Web Access (DWA) link has been resolved by refining the code of the PZPEGA_UI_DOC_EVENTSCONDITIONSCHAINING script to improve performance.

INC-174144 · Issue 651772

Scenario testing records upload attachment click in Cosmos

Resolved in Pega Version 8.7

Scenario testing was not recording the click to upload the attachment in the Cosmos UI. Investigation showed this was caused by the attach icon in the CaseRelatedContent section in Work- class not having the test ID generated as expected. This has been corrected.

INC-174921 · Issue 652322

Client Side required validation applied to dropdown Date field

Resolved in Pega Version 8.7

The mandatory validation on submit of the screenflow screen was not being triggered even though 'Required' was configured on the Date field. This was traced to the validation being applied to a hidden field when the date time control is configured in dropdown mode, and has been resolved by adding a condition for validating this configuration.

INC-175322 · Issue 658650

Focus set correctly on the modal window in theme-Cosmos

Resolved in Pega Version 8.7

In theme-Cosmos with touch enabled, clicking on a button to open a modal window set the focus on the background instead of in the modal window, forcing tabbing through the full page to reach the modal window. This was traced to the templates not using the pzModalCancel control which has the necessary container_close for the modal dialog close icon, and has been resolved by adding a check to set the focus correctly.

INC-175394 · Issue 661455

Date Time format corrected for Chinese locale

Resolved in Pega Version 8.7

The DateTime input field displayed the error message "not a valid date/time value" for the Chinese locale when the time zone source configuration was set as "CET". This has been resolved by setting the moment object's locale to the operator locale while converting the date time values to the operator time zone.

INC-175892 · Issue 651962

Updated logic for Spinner API used in DateTime control

Resolved in Pega Version 8.7

When selecting 11, 22, 33, 44 in minutes in the DateTime picker, 11 was rounded off to 10, 22 was rounded off to 20, 33 was rounded off to 30, etc. This was due to the match and increment behavior in the UI Spinner Js API used by the DateTime control, and has been resolved by modifying the logic used to calculate the nextIndex in the keydownHandler API under ui_spinner.js .

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.

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