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-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-B73531 · Issue 325518

Missing check added for "Column Command Menu" on summary type report

Resolved in Pega Version 7.3.1

For a summary type report, the column command menu was still displayed even though the "Enable Column Command Menu" was unchecked on the report definition Report Viewer tab. This was due to a missing check for "Enable column command menu" before adding the showReportRCMenu onclick event, and has been fixed.

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-B74586 · Issue 325692

Fixed save-as for RD with sub-report and join

Resolved in Pega Version 7.3.1

A save-as for the existing Report Definition rule :USCANSaleEstimate was not working for a new ruleset version. This was an issue with an existing RD that had a sub-report and was joined by a column in the sub-report that was a function, and pzGenerateMsgForUderDefinedFunctions has been modified to correct this.

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-B76880 · Issue 326010

Repeat grid filtering option fixed for Microsoft Internet Explorer 11

Resolved in Pega Version 7.3.1

The repeat grid populated when running report definition was prompting for the filter of the data properly in Microsoft Internet Explorer 11, but no action was performed when clicking on it. This was an issue with missing navigation rule changes, which have been added.

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.

SR-B57565 · Issue 316702

Fixed encoded special characters in 'Field values'

Resolved in Pega Version 7.3.1

Special characters in 'Field values' were being displayed as encoded in the grid. This was due to missing handling, and has been fixed in the generateCellContent RUF.

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