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-D45848 · Issue 515523

Added toggle to hold radio button value during multiple service case creation

Resolved in Pega Version 8.3.2

When a field was implemented with a radio button control in the service case screen, starting two cases of the same or different case type (with the same property and control) resulted in the selected value not sticking in the first case when selections were made for the second case. This was traced to multiple radio buttons with the same name in the dom for different AJAX containers: as per radio buttons behavior, only one could be selected if they have the same name. To correct this issue, updates have been made to change the name on radio buttons which are inside the hidden AJAX container and toggle the changes when the buttons should be shown.

SR-D46543 · Issue 516181

Error messages made more accessible

Resolved in Pega Version 8.3.2

In order to improve the accessibility of error messages, an aria-describedby attribute will be placed on the input that will link to the error message. To further support screen reader users, the focus will be moved to the first input field with an error after the user clicks submit.

SR-D47344 · Issue 519890

Single quotes escaped in RTE title field value

Resolved in Pega Version 8.3.2

A JSON parse error was caused by single quotes not being escaped in the RTE title field value. This has been corrected.

SR-D47401 · Issue 512616

Corrected multiplying errors on dirty flag

Resolved in Pega Version 8.3.2

The error message "Value cannot be blank" was appended on the screen every time the browser gave a dirty flag and OK was clicked. This was due to the context for the error message not being set correctly after toggleErrorMessage, and has been corrected. In addition, due to Context being incorrect when there was a check on the errors on the element, further work has been added to set the correct context before checking if errors exist.

SR-D47583 · Issue 518039

IsMobile 'when' configurations are properly displayed in mashup preview

Resolved in Pega Version 8.3.2

Given two layouts configured based on the 'when' rule pyIsMobile, the mashup preview did not work in the mobile form factor. This was only an issue with App Studio preview of a mashup and did not have an impact on the enduser use of the mashup, and the same mashup code viewed on mobile/desktop worked as expected. Investigation showed that the 'when' rule was evaluated correctly for the application level, but in mashup it was evaluated to false even when opened in mobile view from App studio. The Rule-Utility-Function checks to see if an overridden useragent has been specified and if it has, then it uses it for the preview in App Studio, however in mashup the userAgentDetails did not contain any of the satisfying conditions under which the condition might be returned as false. The issue in this case was traced to the Rule-Utility-Function needing to handle the scenario of Mashup Preview by checking if the thread was from the mashup preview, and that has been implemented.

SR-D47886 · Issue 514778

Home icon retains correct color after refresh

Resolved in Pega Version 8.3.2

By default, the home icon is a svg tag with dark or white filling (based whether it is selected or not), however if another tab was selected and the page refreshed, the icon went black and became a svg img tag. This has been corrected.

SR-D48046 · Issue 512589

Left panel content visible after window resize

Resolved in Pega Version 8.3.2

After maximizing or resizing the window, the left pane on Designer Studio or User Portal either did not show the left panel or did not show the panel separator and did not display any content after clicking on separator navigation icon. It was also not possible to expand the Explorers again. This has been corrected.

SR-D49182 · Issue 513736

Check added for special characters in parameter for table source

Resolved in Pega Version 8.3.2

A table with a literal string that included the @ symbol for a parameter to its data page source was unable to load the section if it had the optimize code checkbox enabled. This has been resolved with the addition of a check for special characters.

SR-D49305 · Issue 519363

Tab layout group handling improved

Resolved in Pega Version 8.3.2

A difference in scrolling speeds between left and right arrows and an issue with the cursor correctly being redirected to mandatory fields were traced to errors in the tab layout group handling. The right scrolling issue was due to the calculation for right tab movement being incorrect in certain resolutions with relatively positioned elements, and has been corrected. The cursor redirect was caused by an error in the layoutgroup focus when used inside a screen flow where the first focus goes to the screenflow navigation on load, and has been resolved by adding a try catch for an invalid selector in case of a div error.

SR-D49468 · Issue 516323

Parent harness context passed for reference properties in Ajax containers

Resolved in Pega Version 8.3.2

Attempting to save values failed for any property which was mapped to a parent property that was also a reference property. This was traced to an issue with the harness-level templating status: for the lazy loaded sections of a harness, the harness's template status was being passed instead of the parent harness template status when using an Ajax container. To resolve this, logic has been added to pzpega_ui_doc_serverProxy js for the invokeHandler function to add parameters based on the parent harness context to the safeURL object before invoking the post request.

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