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-101011 · Issue 556725

Pulse mentions correctly tagged in Google Chrome

Resolved in Pega Version 8.4.2

Pulse mentions of spaces or users were not getting tagged correctly. This issue was due to recent changes in the way touch events are handled in Google Chrome: the latest upgrade removed the ontouchstart property in the window, causing the isTouchable capability identification method to fail. As part of the work done to resolve this, it was discovered that the initAutocomplete function in the pzJquerymentionsInput .js was failing to delegate the mousedown event. This has been corrected by delegating touchstart and mousedown while initializing if screen isTouchable.

INC-119803 · Issue 561686

Placeholder text added for question dropdown sourced by a datapage

Resolved in Pega Version 8.4.2

In a flow action with question pages where each question page was configured with a set of question rules, one question which displayed a country list in a dropdown sourced from a datapage always displayed the first value by default in the dropdown instead of place holder text (like Select..). In addition, the default selection value of the dropdown was not saving to the clipboard on submission of the flow action, causing it to appear in the UI like the first value had been selected even though nothing was saved on the clipboard. These issues have been resolved by adding place holder text in pzSetQuestionStreamSimpleDynamicSelect for a dropdown with a datapage source

INC-120326 · Issue 564438

Landing page refresh modified to avoid frequent reloads

Resolved in Pega Version 8.4.2

Approximately every two weeks, clients were able to login but it was not possible to work as the landing page refreshed constantly until all of the nodes were rebooted and the issue was cleared. Investigation indicated the frequent reloads were related to the cacheing of the operator details, and this has been resolved by updating the datapage reload strategy based on 'when' so frequent reloads will be avoided.

INC-126114 · Issue 562178

Spaces member count method updated

Resolved in Pega Version 8.4.2

When a space contained more than 50 members, it always displayed the count as 50 even though the Spaces section showed the correct count. This was due to a pagination setting that had a maximum of 50 records set, and has been resolved by using the GroupMemberCount DP instead of AllMembers to retrieve an accurate count.

INC-130727 · Issue 574268

Resolved mobile app java.lang.OutOfMemoryError

Resolved in Pega Version 8.4.2

After working with the mobile app for a period, logging in failed and the app crashed with java.lang.OutOfMemoryError exceptions. This was traced to each sync adding a new version of allow-list datapages to the client store which were not cleared, and has been resolved.

SR-D74246 · Issue 543727

Accessibility improved for Pega Survey Question pages

Resolved in Pega Version 8.4.2

Question Pages in Pega Survey lacked accessibility. This was traced to aria-label not being generated for Radio buttons and Drop-downs, and "title" not being generated for other controls used in Question and Question Pages. This has been resolved.

SR-D80886 · Issue 547291

Improved usability for long Pulse notes

Resolved in Pega Version 8.4.2

After a Pulse message exceeded 32 lines, the window scrolled to the top of the screen after each keypress, obscuring the typing. This was traced to the CSS on the textarea span, and has been resolved by modifying create-new-pulse to display:inline-flex; in pzpega_social CSS.

SR-D83630 · Issue 546144

IsQuestionHidden property added to skip validating hidden questions

Resolved in Pega Version 8.4.2

After configuring a simple question which had a validation rule defined on it and a display 'when' rule configured to show or hide it based on another question condition validation was still being fired on the hidden question and it was not possible to proceed. This has been resolved by adding code to skip validations for a question if it is hidden, based on the pzIsQuestionHidden property.

SR-D85624 · Issue 552698

Corrected Microsoft Internet Explorer displaying checkboxes as sliders

Resolved in Pega Version 8.4.2

Checkboxes were displaying as sliders in Microsoft Internet Explorer version11.1304.17134.0 due to Microsoft Internet Explorer returning Table pc 2.0. Since Pega HTML class includes tablet, .tablet related styles were getting picked up and displaying the checkboxes in tablet mode. To resolve this, a check has been added to pyIsTablet to evaluate correctly at runtime.

SR-D89427 · Issue 548938

Corrected Microsoft Internet Explorer displaying checkboxes as sliders

Resolved in Pega Version 8.4.2

Checkboxes were displaying as sliders in Microsoft Internet Explorer version11.1304.17134.0 due to Microsoft Internet Explorer returning Table pc 2.0. Since Pega HTML class includes tablet, .tablet related styles were getting picked up and displaying the checkboxes in tablet mode. To resolve this, a check has been added to pyIsTablet to evaluate correctly at runtime.

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