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-D92913 · Issue 553903

Aria-collapsed replaced with aria-expanded to improve accessibility

Resolved in Pega Version 8.3.3

Previously, the system used the aria-collapsed attribute for the left and right navigation toggling. In order to improve accessibility, this attribute has been changed to aria-expanded and the value will be set to true/false accordingly.

SR-D80696 · Issue 548822

Autocomplete context fetched for dropdown in nested case

Resolved in Pega Version 8.3.3

The autocomplete dropdown was empty when using SmartTip and the down arrow was clicked while opening an autocomplete case within an Interaction case. Opening the service case directly in a new tab populated the dropdown values as expected. This has been corrected by registering context changes just before the content is fetched for the overlay.

SR-D86429 · Issue 551371

Badge text Control Format supports declare expression target

Resolved in Pega Version 8.3.3

In the user screen, some properties are shown in 'Text' control with 'Badge text' control format. When the value of this property was set in Data Transform, it appeared correctly. When the property value was set in Declare Expression, no background color was set. This was traced to a missed use case in the implementation work for vtable, which resulted in the control format mentioned in presentation tab of control not being applied on markup when the property was a declare expression target. This has been corrected.

SR-D88057 · Issue 549110

Calculation logic updated for SLA with Goals and Deadline

Resolved in Pega Version 8.3.3

The DateTime control was displaying the date reduced by one day in runtime if it was configured with an SLA using Goals and Deadline. This has been resolved by removing the seconds and milliseconds in the calculation.

SR-D85339 · Issue 548180

Calendar AM/PM corrected for Chinese locale

Resolved in Pega Version 8.3.3

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-D73224 · Issue 542628

Case manager portal links working with SVG file

Resolved in Pega Version 8.3.3

After modifying the pyPortalHeader to show a custom logo in the Case manager portal by saving the pyapp-logo.svg file into a ruleset and uploading the logo, none of the Case manager portal links or menus were working and a console error appeared. Investigation showed the SVG file stream was decoded and then encoded using the Base64Util.encode and decode, which was adding new line characters. To resolve this, step 4 in Rule-File-Binary.UploadFile Activity has been modified to remove the Base64 encode and decode.

SR-D78557 · Issue 551840

Check added before generating aria-label

Resolved in Pega Version 8.3.3

To improve accessibility, logic has been added to dynamic layout generation that will check whether the text value is empty, and if so an aria-label will not be generated.

SR-D75964 · Issue 542685

Check added to ensure enter key triggers autocomplete onchange

Resolved in Pega Version 8.3.3

Tenant details were not loading, and no requests were seen being generated after the selection of the tenant. Investigation showed that for autocomplete control, a dummy onchange attribute was added, i.e., data-change = "[]". When the value was selected using the enter key, fireACOnElem was not executed in processEvent function as the condition isExplicitConfig(target) was true. To resolve this, an additional check attr(data-change) != "[]" has been added for ClientConditionExecutor to trigger fireACOnElem.

SR-D79526 · Issue 544787

ClassName will be updated when element model page is updated

Resolved in Pega Version 8.3.3

In the event of traversing from Parent to Child, The Declare_pyDisplay datapage in clipboard was not in sync for the Child as the Active UI Element. This was traced to reliance on the pyClassName field of data element model (Declare_pyDisplay.pyDisplay(Developer).pyUIActive(1).pyClassName) to update the client side UI based on a particular condition evaluation. Because some of the properties in the element model are updated only if the page is newly created, using a page which was already present and updating values with some other UI actions was only updating specific properties which did not include pyClassName. To support this use, modifications have been made so the pyClassName will also be updated whenever the page is updated.

SR-D91846 · Issue 550789

Complex question checkbox labels displayed

Resolved in Pega Version 8.3.3

Checkbox labels were not shown when a survey was rendered in read-only mode. This has been resolved by updating pzComplexQuestionCheckBoxTemplateRowDetails and ComplexQuestionCheckboxTemplate section to show labels and icons for check boxes when a complex checkbox question is displayed in read-only mode.

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