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-D66387 · Issue 530841

ReloadSectionsCache handling improved

Resolved in Pega Version 8.3.2

Change Tracker was reporting changes properly and ExpressionEvaluator logic identified the correct DOM element related to layout refresh, but the refresh was not getting triggered due to _isInvalidRefresh logic. This was traced to reloadSectionsCache not being optimally maintained, and has been resolved by updating reloadSetionCache to avoid unnecessary reloads and only update the cache after a reload section is completed.

SR-D66436 · Issue 529670

Correct Value shown for Helper Text controls with labels

Resolved in Pega Version 8.3.2

Helper Text sourced from a field value was displaying the field value's 'Translate From' value rather than the 'Translate to' value. Analysis showed that the 'title' attribute of the corresponding icon on the DOM was being populated differently depending on whether it was a control with labels (not working) or a caption on a checkbox control (worked as expected). To address this, a check has been added for datetime and checkbox controls to send fieldname as pyCaption and pyActionPrompt respectively instead of pyTooltip to resolve the value.

SR-D67674 · Issue 537587

Check added to skip validationtype for disabled controls with Accessibility

Resolved in Pega Version 8.3.2

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 541814

Added logoff check for requestors

Resolved in Pega Version 8.3.2

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-D68311 · Issue 535984

Corrected table row highlighting on iPad

Resolved in Pega Version 8.3.2

A table row was highlighted when clicked on an iPad in landscape view, but when the device was rotated to portrait view the row was not highlighted. This was traced to the background CSS overriding the selected style, and has been corrected by modifying py-responsive-overrides.css.

SR-D68721 · Issue 532594

Corrected span tags in non-templated Autocomplete

Resolved in Pega Version 8.3.2

Span tags were seen in the auto complete list when Results display was selected as "In a list". This appeared only in non-template mode, and was traced to the application of a crossScriptingFilter after adding span.match element to the value. To correct this, the crossScriptingFilter will be applied before adding the span.match markup to the value.

SR-D69452 · Issue 536399

Layout management corrected for nested gadget sections

Resolved in Pega Version 8.3.2

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 541961

Case UI correct following multiple approval levels

Resolved in Pega Version 8.3.2

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 537139

Window type check added for icon display logic

Resolved in Pega Version 8.3.2

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.

SR-D71105 · Issue 532188

Corrected error when using CharCounter in non-template mode

Resolved in Pega Version 8.3.2

An error message was generated when trying to save a section with the TextArea's Display CharCounter set to True. This was traced to an error in the remaining character count span generation for non template mode and has been corrected.

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