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-B70222 · Issue 322936

Property value submit event for screen flow works in Microsoft Internet Explorer

Resolved in Pega Version 7.3.1

FinishAssignment Action was configured as an Enter Key event for Dynamic layout in order to submit the flow in screenflow, but at runtime when using Microsoft Internet Explorer some of the property values were not submitting to the clipboard as expected. The issue was a defect in the UI framework related to submitting a form through any event when the input had focus in Microsoft Internet Explorer, and a check has been added to resolve the error.

SR-B71754 · Issue 325868

OpenAssignment in WSS always opens in same window

Resolved in Pega Version 7.3.1

A difference was seen in the behavior of a button configured with OpenAssignment in the WSS portal; if the site was using prgateway the button would open the assignment in the same window, but if the site was using mashup code clicking the button opened the assignment in a new window. This was caused by a logic difference in the two cases, and has been fixed with changes in pega.desktop.support.openSpace to call openSpaceInGadget if the composite gadget is not available in the portal. This will cause the assignment to always open in the same window as expected.

SR-B72892 · Issue 323517

Error message display fixed for RG read-only field

Resolved in Pega Version 7.3.1

Incorrect behaviors were seen with displaying errors when a field in a repeat grid table was configured as "Read-only (always)" and "Show validation messages in read-only mode" was on. In Google Chrome, the UI form did not contain the corresponding error image in the field due to the only error icon div getting hidden. In Microsoft Internet Explorer 11, the UI form contained the corresponding error image in the field, but only part of this image was visible due to changes of column/field width not being honored. These issues have been fixed by updating the CSS in the pzbase-grids.css file.

SR-B73126 · Issue 323350

Fixed autocomplete cell value disappearing on blur

Resolved in Pega Version 7.3.1

After upgrade, an autocomplete configured with data page "onChange - Post Value" had cells whose entered value disappeared onBlur of the autocomplete cell. The reported issue is a UI framework defect with templating enabled, and was traced to an issue with the change tracker data not getting merged properly to context data after the postvalue response is received. This has been fixed.

SR-B73514 · Issue 324049

Added new function to bypass URLScan MaxURLLength

Resolved in Pega Version 7.3.1

When Pega is fronted by Microsoft IIS WebServer with either a proxy or Web Application Server plugin, the IIS advanced security options, URLScan, are used to limit the size of URLs. When the URLScan MaxURLLength is set below about 600 characters a major static content request for core PRPC UI JavaScript files is blocked. This is a known issue when using IIS Web Server, but to enable expanded use, a 'when' function named pyIsForcedSplitJS has been added that allows overwrite as required by dividing pzHarnessStaticScripts into 4 chunks to decrease length. The format is

SR-B73577 · Issue 322575

Localization added in Pega Express

Resolved in Pega Version 7.3.1

Localization has been added to the Pega express configuration channel and Interface display formats.

SR-B73599 · Issue 324612

Filtering fixed for properties defined by @@CaseWhen()

Resolved in Pega Version 7.3.1

Filtering was not applied for properties defined by @@CaseWhen() . This was due to some function alias calls needing double quotes for literal parameters. The double quotes are removed after section XML is submitted and hence the param available to the grid (via html attribute sortField) did not have the double quotes. To correct this, a function alias call in RD bound grid will set the pyColumnName to pyFieldName since the pyColumnName does not have the double quotes that are needed by some functions.

SR-B73664 · Issue 322173

Text area - Disable when fixed

Resolved in Pega Version 7.3.1

A Text Area control was not disabling with When conditions or expressions. The control was disabled correctly if set to "Always". This was due to an incorrect condition in pzpega_ui_template_textarea.js, and has been fixed.

SR-B76216 · Issue 325540

Localization support added for Indonesian

Resolved in Pega Version 7.3.1

pyLanguage has been modified to add the new value in_ID in the prompt list that will provide localization support for Indonesian (Indonesia).

SR-B77544 · Issue 326629

Scroll bar issues fixed for freeze column pane

Resolved in Pega Version 7.3.1

A vertical scroll bar was displayed on the screen and the horizontal scroll was not working as expected when the freeze column pane option was selected in the repeating grid. This was traced to styles missing from the base-grids.css that were needed for fixed column configuration, and these have been added.

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