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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-D47583 · Issue 518040

IsMobile 'when' configurations are properly displayed in mashup preview

Resolved in Pega Version 8.4

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-Functionchecks 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-Functionneeding to handle the scenario of Mashup Preview by checking if the thread was from the mashup preview, and that has been implemented.

SR-D47689 · Issue 520830

EvaluateConditions properly sets context for refresh section

Resolved in Pega Version 8.4

Rule Not Found and Unresolved Assembly Errors were seen in production logs after upgrade. Investigation showed that the method context used by pzpega_ui_changetracker.js in "evaluateConditionsOnXThread" was not reset correctly, causing the refresh section response for the Recents List to not be properly updated. This has been resolved by updating the evaluateConditionsOnXThread method to set the proper context after evaluateClientConditions is run.

SR-D47886 · Issue 514780

Home icon retains correct color after refresh

Resolved in Pega Version 8.4

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 512590

Left panel content visible after window resize

Resolved in Pega Version 8.4

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-D48887 · Issue 512946

Read-only text inputs remain read-only after browser refresh

Resolved in Pega Version 8.4

Read-only text inputs were changing to editable after a browser refresh. This was traced to work done to better handle a displayOnPage GET request that was sent with all of the parameters in the parameter page (data-model) that was causing a 400 Bad Request due to the browser URL length limitations. That issue was resolved by removing the parameters which are not actually required for the displayOnPage GET call during the refresh case; to resolve this issue, the readonly parameter for displayOnpage action has been restored and will be passed.

SR-D49182 · Issue 513737

Check added for special characters in parameter for table source

Resolved in Pega Version 8.4

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 519366

Tab layout group handling improved

Resolved in Pega Version 8.4

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 516324

Parent harness context passed for reference properties in Ajax containers

Resolved in Pega Version 8.4

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.

SR-D49527 · Issue 516297

XSS security added to CKEditor in Richtext Editor

Resolved in Pega Version 8.4

A scenario where HTML objects could be copied and pasted into CKEditor and the click action modified to perform different actions was traced to Pega event attributes present in the RTE content. This has been corrected by blacklisting Pega event attributes like data-click, etc.

SR-D50069 · Issue 514342

Image Attachment File Type error localized

Resolved in Pega Version 8.4

Localization has been added to the error message generated when an unsupported image is uploaded while in live-chat.

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