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-D62732 · Issue 527695

V-Scroll bar retained after dirty modal check return

Resolved in Pega Version 8.4.1

A modal dialog of a repeating grid with 'flexible' and numbers of field items that required a v-scroll bar with auto-size layout (Standard layout) had the scroll bar disappear after returning from pyDirtyCheckConfirm /Cancel. This was traced to the dirty modal setting some inline styles to modal, and has been resolved by updating Dirty modal to clean up any styles set on modal once it is closed.

SR-D64244 · Issue 532984

Support added for recording with sIngle-option radio button inside a repeating grid

Resolved in Pega Version 8.4.1

Recording a test case was not working when a single option radio button (i.e., radio button control with property of type boolean) was configured inside a repeating grid. In this case, it was found that the Radio button markup did not have a data-test-id attribute for non-template single option; this has been added.

SR-D64667 · Issue 531808

Cursor issue resolved for tab within expandable row

Resolved in Pega Version 8.4.1

When pressing the “Tab” key on an expanded row, the cursor was not moving inside the expanded part. This has been fixed by adding a check to get the correct first focusable element.

SR-D65762 · Issue 527556

Updated logic for Spinner API used in DateTime control

Resolved in Pega Version 8.4.1

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 .

SR-D67012 · Issue 537310

Invalid dropdown time will retain entered time

Resolved in Pega Version 8.4.1

If a datetime control using dropdown mode and a timeofday property had a validation error, on refresh the current time was being set in the dropdown. This occurred when selecting only one part of the time property (only minutes or only hours), and included an error indicating that the provided time was not a valid time of day value. To resolve this, an update has been made so that if this combination has a validation error, on refresh setting the user-entered time will be given in the dropdown instead of the current time.

SR-D67674 · Issue 537589

Check added to skip validationtype for disabled controls with Accessibility

Resolved in Pega Version 8.4.1

On enabling Accessibility, a disabled DateTime control was throwing a 'required' error. This was due to the dropdown markup having the validationType="required" attribute set if the control was configured with a required 'when' expression. Even though the expression evaluated as false, validationType="required" was still set. This issue was seen only in non-template datetime control, and has been corrected with a check to skip adding a validationType attribute for a disabled control in Accessibility mode.

SR-D68277 · Issue 541817

Added logoff check for requestors

Resolved in Pega Version 8.4.1

After upgrade, the error "java.lang.InterruptedException. Requester has been destroyed" was appearing in the logs. Investigation showed this was related to unregister requests being submitted after logoff, and has been resolved by updating the system to check for logout before sending unregister requests.

SR-D69452 · Issue 536401

Layout management corrected for nested gadget sections

Resolved in Pega Version 8.4.1

Post-upgrade, some buttons were missing or mis-aligned, specifically the 'Reopen' and 'Cancel this Assignment' buttons were missing, and if 'Cancel this Assignment' was clicked, the Back button was missing. Investigation showed that when using nested gadget section includes, the necessary stack management to pop previous gadget parameters was not present. This has been resolved by adding a check for template rendering, as there is separate handling for template rendering to manage the stack.

SR-D70064 · Issue 541963

Case UI correct following multiple approval levels

Resolved in Pega Version 8.4.1

After proceeding through different levels of approvals, the UI of the case was incorrect on the final approval submit. This was traced to the forceSkinGeneration parameter, which was set to true, being used by a workformstyles fragment. This has been resolved by changing pzUsePreferenceSkin to "once" and setting the parameter forceSkinGeneration to false after the pyAttachAsPDF activity call.

SR-D70310 · Issue 537141

Window type check added for icon display logic

Resolved in Pega Version 8.4.1

When a Role had privileges to use Live UI, Agile WorkBench and Scenario Testing, the Scenario Testing tool icon intermittently did not show. This was traced to an incorrect condition used to check whether current window was of type desktop (portal) window, and has been resolved by adding a check that will also ensure consistency with Agile Studio icon display logic.

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