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-D84882 · Issue 551989

Resolved duplicate messages from HarnessErrorList section

Resolved in Pega Version 8.2.7

When using pyCaseErrorSection to call HarnessErrorList and display any errors on Clipboard page, when the Clipboard page had more than one error then the error message was shown multiple times. This has been resolved by adding a check that will iterate through the errors to see if it is present on the page already. If it is present it will be ignored, and if it is not present, then it will be added.

SR-D85339 · Issue 548181

Calendar AM/PM corrected for Chinese locale

Resolved in Pega Version 8.2.7

When using the Chinese locale (zh_CN), opening a calendar control in the Report definition to select filter values resulted in the Calendar tab dropdown showing "上午" (AM) when the system time was in "下午" (PM). Investigation showed that when generating a non-auto date time control, ampm text (i.e. string value) was compared with the generated select component using locale specific values which did not match any time, so AM was always selected as it was the first value in the dropdown. To resolve this, the system has been updated to use the locale specific AM PM values for non-auto-generated date time control.

SR-D86200 · Issue 549031

Resolved tab appearance issues related to resolution support

Resolved in Pega Version 8.2.7

When trying to add multiple tabs on larger screens, once the first row was filled with tabs then new tabs began appearing at the bottom of the layout group. The layout group worked as expected with the tab overflow having the right and left arrows with the dropdown on smaller screens. In addition, @1440px the overflow arrow on the right side was not working correctly, showing as grayed out even though focus was not on the last tab. These issues were traced to taboverflow with add icon not working correctly at certain resolutions. To resolve this, the todisableslide function has been updated to consider add icon width and layoutgroup has been updated to consider parent width.

SR-D86274 · Issue 552508

Resolved validation conflict with error message display

Resolved in Pega Version 8.2.7

Error messages set through property-set- messages or edit validate were disappearing when out of focus from the date field if the field had a mandatory condition. This was traced to an edge condition where required validation was conflicting with another error message, and has been resolved by modifying the code so the system will not validate required on blur if the input has another error message.

SR-D86694 · Issue 548668

TeamMembersWidget section include corrected for PortalNav

Resolved in Pega Version 8.2.7

An error was seen when attempting to include the pyTeamMembersWidget section inside a pyPortalNav section. Investigation showed there was a data corruption in the section. As a local change, it was possible to 'save as' the section to a ruleset and delete the section embedded in the grid, then drag an embedded section layout from Layouts, add it to the grid row, and select pyTeamMembersWidgetRow. As a permanenet resolution, the corrupted section has now been replaced.

SR-D87007 · Issue 550331

Handling added for special characters in radio button response value

Resolved in Pega Version 8.2.7

Adding a response with a single quote on a radio button caused the preview to hang. This was traced to the 'querySelector' API: because the argument selector syntax used [id='{idVal}'], the variable 'idVal' value in the selector argument containing an apostrophe formed an invalid selector argument to the API. This has been resolved by escaping any apostrophes from the querySelector argument.

SR-D89242 · Issue 555588

Corrected layout refresh for grid state page

Resolved in Pega Version 8.2.7

When the condition builder had an empty row, on submit an error was displayed as expected. However, attempting to delete the empty row resulted in an exception. Investigation showed that the layout refresh was causing the grid state page to get deleted upon submission of the modal. This has been resolved.

SR-D89672 · Issue 550525

Custom error label styles work for 'required'

Resolved in Pega Version 8.2.7

When using the default 'required' error message, the class "labelError" is added when the required field is empty. However, when the default 'required' is replaced by a custom error message, a UI error was seen because the class "labelError" was not added when the field was empty. This was traced to an error in the non-template to template code transform, and has been resolved by updating webwb_pzpega_ui_dlcelltemplate_js to add the labelError class based on the presence of an error message.

SR-D90284 · Issue 551472

Added 'when' condition to class change in ShowColorPicker activity

Resolved in Pega Version 8.2.7

When using an included color picker control in a section, selecting a color resulted in the color picker pyworkpage class content changing to Embed-Skin-Controls. This has been resolved by modifying the previous behavior of always changing pyWorkPage's obj class as part of the ShowColorPicker activity by adding a 'when' condition to change the class only if it is empty.

SR-D90331 · Issue 553607

Context-specific APIs used for RefreshHarness with AJAX container

Resolved in Pega Version 8.2.7

After creating an interaction case and letting it go idle, attempting to continue and process the service cases in that case was intermittently resulting in a transaction ID mismatch error. This was traced to handling in the AJAX container, and has been resolved by updating the system to use context-specific APIs for refreshHarness case in doc_submit.

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