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.

INC-118907 · Issue 561072

ClearHighlight called after test steps complete

Resolved in Pega Version 8.3.4

When using a custom delay as part of a scenario test, an orange highlight square was unexpectedly persisting on the portal. To resolve this, an update has been made to explicitly call "_clearHightlight()" after every test case step execution completes.

INC-118923 · Issue 565231

Multiselect updated for server side error message display

Resolved in Pega Version 8.3.4

After configuring a multiselect control as a required field, a button configured to trigger property-set-message was not displayed in the UI. This was traced to Multislelect not showing the server side error message as its handle bar was not stamping, and has been resolved by utilizing the errormessage string for the handlebar.

INC-121205 · Issue 560035

Live UI working on modal dialogue

Resolved in Pega Version 8.3.4

Live UI was not working with modal dialogue if the modal was present in an embedded iframe on a shared system. This was traced to logic in Live UI that was adding a scrollTop offset to the highlights, shifting them down, and has been resolved by adding getElementDimension() in the Live UI utilities to not add the scroll top offset when in modals.

INC-121444 · Issue 561808

Added handling to force text area maxlength in Edge

Resolved in Pega Version 8.3.4

When using the Edge browser, it was possible to continue entering characters in excess of the value set for the 'max characters' property. Investigation showed that the Edge browser does not honor the maxlength attribute on text area; to resolve this, logic has been added to restrict the user from entering extra characters above the max limit.

INC-121490 · Issue 567183

Date/time will not format an invalid input

Resolved in Pega Version 8.3.4

Additional checks have been added to date/time that will return an invalid date without trying to format it.

INC-122068 · Issue 569607

Tooltip displayed when menu item not enabled

Resolved in Pega Version 8.3.4

Tooltip was not being displayed when menu item in the navigation rule was disabled. This was due to the pointer events not being supplied to the CSS selector, and has been resolved.

INC-122172 · Issue 560214

Scenario test APIs updated to better capture successive clicks on the same elements

Resolved in Pega Version 8.3.4

When recording a scenario test, the test recorder did not capture successive clicks of the same screen element. This could carry from screen to screen as pyCaseActionAreaButtons is used in the perform harness and is can be presented for two successive screens. To resolve the issue, the APIs have been changed to use code better suited to capture the correct elements.

INC-123112 · Issue 568699

Check added for multiselect in case of ABACSecurity

Resolved in Pega Version 8.3.4

A harness was created that had to be launched with 'section include' that contained more than one multiselect along with Dropdown controls sourced with different datapages and each control was visible based on conditions at runtime. When loading the harness with one multiselect based on condition, the clipboard and tracer was loaded with other datapages that were not visible at runtime but were sourced for other controls that were part of the section. When this was run, an error around the mode of the page list was generated. The same error was not observed when the configurations were made in the perform harness. This was traced to getAuthorizationHandle().getABACSecurityPolicyEngine().getPropertyInfoForDisplay, which should only be called for scalar properties, but in cases of multiselect the API was called on a vector property since multiselect uses pagelist as a source. This has been resolved by adding a check for multiselect in case of ABACSecurity.

INC-125105 · Issue 563381

Null checks added for incomplete autocomplete fields

Resolved in Pega Version 8.3.4

When using a page which has an AutoComplete text input and a button configured for search, tabbing out of the autocomplete field before the autocomplete list has appeared and then filling out the rest of the fields and clicking submit was sporadically resulting in the page becoming unresponsive. This has been resolved by adding null checks and improving the error handling.

INC-125398 · Issue 564976

Updated handling for checkboxes configured in the header

Resolved in Pega Version 8.3.4

After configuring multiple checkboxes where each checkbox had a different property and different DT as action set and then using them as a single column header in the table, the on-change of any one checkbox caused all of the checkboxes to be checked or unchecked in the column header. This was caused by the pega.ui.grid.prototype.checkAllIfInHeader, which selects or unselects all checkboxes present in table (header +. body) based on checkbox status in header. However, the header row should not be part of the iterator during this function, and the necessary update has been made.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us