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

INC-176113 · Issue 661468

Duplicate messages removed from hover over smart info

Resolved in Pega Version 8.7

If a particular mandatory field was not selected and saved, scrolling over any help text bubble in that screen caused the error messages to pop up multiple times. This was an issue with the recreation of error tables on hover over smart info and has been corrected.

INC-176403 · Issue 653575

Security updated for buttons

Resolved in Pega Version 8.7

Cross-site scripting protections have been updated for Button controls.

INC-176734 · Issue 655177

Invalid manual time value stops progress and displays error

Resolved in Pega Version 8.7

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.

INC-176742 · Issue 657070

DX API JSON response maintains special characters

Resolved in Pega Version 8.7

When processing a Pega workflow with external UI through the DX API, entering some value with special characters like "(" and saving the case resulted in "(" being replaced with junk characters that were displayed on the UI when the case details were sent back from Pega. This was traced to special chars not being supported in the validation error message when displayed on c11n system, and has been resolved by consuming the 'message' value in the error object instead of localizedValue.

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