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-116479 · Issue 170952

Elapsed Time reporting corrected

Resolved in Pega Version 7.1.7

Two out-of-the-box reports, Elapsed Status Time Trend and Average Elapsed Time Per Status, were causing the browser to freeze and stop responding if there were more than 1000 records. This was caused by an invalid value for the datetime units on the category for the chart causing looping behavior. This has been corrected.

SR-116508 · Issue 170253

Large flow handling improved for IE8

Resolved in Pega Version 7.1.7

When opening a large flow in IE8 which includes multiple sub flows, a long-running script warning is displayed. This is caused by too many calls being executed at once on IE8, and has been remedied by turning on the asyncProcessing parameter for IE8.

SR-116510 · Issue 171699

Handling corrected for testing rulesets with multiple versions

Resolved in Pega Version 7.1.7

If two rulesets with multiple versions were moved to a test environment, when the product rule was created only one of the version's instances was in the .jar file. This issue was caused by incomplete clearing of the ruleset spec after collecting the rules, and has been corrected.

SR-116556 · Issue 170813

AllLinksForParticularRule changed from Final to Available

Resolved in Pega Version 7.1.7

The list view reporting limit AllLinksForParticularRule has been changed from a Final rule to an Available rule in order to allow an increase in the number of links shown in the Application Profile. The default is 500.

SR-116585 · Issue 167063

Screen flow previous button repaired in obfuscated IAC

Resolved in Pega Version 7.1.7

When using IAC with obfuscation is enabled, the screen flow 'previous' button was not responding. This was caused by the '\' at the end of the URL parameter being accidentally obfuscated as well, and has been fixed.

SR-116587 · Issue 170222

Clarified default values for Create Class

Resolved in Pega Version 7.1.7

The Create Class screen was offering default values that had the potential to lead to classes being created in an incorrect / invalid part of the Class Structure. This has been corrected.

SR-116597 · Issue 169929

Correct report name displaying on chart reports

Resolved in Pega Version 7.1.7

In Case Manager reports, maximizing a report containing a chart showed the URL as the report name if the report title parameter did not have a value. This field has been updated to default to the report's title if the name has not been explicitly set.

SR-116606 · Issue 169617

Error display settings improved for modal windows

Resolved in Pega Version 7.1.7

If a flow was run in a modal window, the Field-level error display setting on the harness was not being accurately reflected, i.e. if the field level error display option is set to "Full Text", a validation icon is displayed instead or in addition to the text. This has been corrected.

SR-116608 · Issue 173164

Removed periods after page numbers to improve accessibility

Resolved in Pega Version 7.1.7

In some cases the JAWS screen reading software was reading out page numbers for paginated grids including a trailing period / full stop character, such as "2." reading as "two point". Since the page number will always be a whole number, the period/point character has been removed.

SR-116613 · Issue 170409

JAWS no longer reads out table structures

Resolved in Pega Version 7.1.7

When JAWS encountered tables, it considered them to be data tables if there were no aria labels or roles defined on it and proceeded to read out the table structure to the user. If one of the td had ' ' it read out as blank. Table tags being generated for layouts are now given a "role" attribute as "presentation" for accessibility compliance: this will mark the table structure not to be read out by JAWS. In addition, JAWS will read out any html associated to the input rather than the aria-label format information.

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