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-116025 · Issue 174180

Corrected ability to add rows to a Row Repeat Grid Layout

Resolved in Pega Version 7.1.7

Previously, an error was generated when attempting to add more than 51 rows to a Row Repeat Grid Layout with two more layouts containing other fields. This was caused by a duplicate call to invoke the list section, and has been fixed.

SR-116042 · Issue 170124

Updated newline character for HTML

Resolved in Pega Version 7.1.7

On click-submit, some text paragraphs were being displayed without breaks between them. This was caused by a missing HTML tag and has been corrected.

SR-116130 · Issue 168010

StackOverflow errors during passivation remedied

Resolved in Pega Version 7.1.7

An issue was found with StackOverflow errors thrown by the passivation daemon, requiring a restart of the JVM. This was found to be related to the AutoPopulate API, and has been updated.

SR-116146 · Issue 169058

CreateUniqueID enhanced to allow custom instances

Resolved in Pega Version 7.1.7

The out-of-the-box PopulateReport activity previously used shorthand notation when referencing the CreateUniqueID function instead of referencing the function using the RuleSet or library name. This caused an issue with systems that contained a custom version of CreateUniqueID in the CMSUtilities library, resulting in "Multiple suitable instances found" errors. In order to accommodate custom instances of CreateUniqueID, long hand notation will be used for matching in place of shorthand.

SR-116157 · Issue 165994

Improved crash recovery in a complex system

Resolved in Pega Version 7.1.7

During crash recovery in a clustered, load balanced system, attempting to recover a user's progress displayed a message that the session was recovered but the page did not then properly load the recovered data. To ensure proper crash recovery failover on complex systems, the user is now authenticated on the STANDARD thread instead of a work thread when restoring work in progress.

SR-116209 · Issue 166698

Backslash '\' now showing as expected in autocomplete and search

Resolved in Pega Version 7.1.7

The AutoComplete control was filtering out backslash '\' characters when displaying the values in the list of matches, causing failures with search and autocomplete. The Rule-Utility-Function for the getProperty has been corrected to allow '\' to be handled properly.

SR-116272 · Issue 168880

Java error resolved for Smartinfo in list view

Resolved in Pega Version 7.1.7

A JavaScript error was being generated in IE8 after viewing the Smartinfo popup with a list view. This was caused by calling the focus API on top of an invisible element, and has been fixed.

SR-116359 · Issue 169895

Dynamic select modified to use display value instead of property value

Resolved in Pega Version 7.1.7

If two different properties were used for display and values in Dynamic select, the value property was shown instead of the display value. This has been corrected.

SR-116359 · Issue 174215

Dynamic select modified to use display value instead of property value

Resolved in Pega Version 7.1.7

If two different properties were used for display and values in Dynamic select, the value property was shown instead of the display value. This has been corrected.

SR-116379 · Issue 167270

Autocomplete enhanced for JAWS Accessibility Mode

Resolved in Pega Version 7.1.7

When using "Auto-Complete" functionality with the accessibility framework, the "Label For" field was not being read aloud by JAWS. For example if the property's label was defined as "Station Code" , the user only heard "Auto complete edit" instead of "Station Code Auto Complete Edit", causing the user confusion as to where they are on the screen. This issue was traced to the labels for the attribute and ID of the input element not being the same, meaning JAWS was not able to find the label for the autocomplete field. To fix this, the function setAriaLabelForAC has been created in pega_ui_doc to collect all of the autocomplete inputs and choose the attribute by figuring out corresponding label. This will work only if the label is in the previous or next cell to autocomplete, and accessibility mode is enabled.

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