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-127173 · Issue 192701

Resolved save error for custom date format

Resolved in Pega Version 7.1.8

A custom date entry given Display mode 'Text Input + Calendar' and the option 'Display value using read-only formatting' and using the format dd.MM.yyyy returned the error 'Entered date value is Invalid' when attempting to save. This was an issue where the processOnBeforeSubmit function code exists to replace the client formatted value with the value which need to be submitted but doSave was using the submitWhenFail API where it has its own logic to process elements. To resolve the issue, the system will call a common function from both places to obtain the proper setting.

SR-128261 · Issue 192779

Corrected accessibility for buttons assigned a menu role

Resolved in Pega Version 7.1.8

With JAWS accessibility active, navigating to a menu button titled "Other Actions" causes JAWS to read "Menu. To move through items press up or down arrow...O." If the JAWS instructions are followed, it reads out the caption/title of the next field rather than actually reading out the options in the menu. This was caused by JAWS not reading the label of a button which has popover window on click action and has the 'menu' role added to it. To resolve this, if there is a role in the button generation RUF, its value has been set to "menu".

SR-130147 · Issue 196723

pxCWOptionsMenu now localized

Resolved in Pega Version 7.1.8

Localization has been added for the section pxCWOptionsMenu.

SR-130249 · Issue 199071

Resolved validation error for modal window with right tabs

Resolved in Pega Version 7.1.8

Validation errors in a modal window could cause the user session to hang when the content of the modal window was configured to use a tab group with tabs positioned to the right. This was a div ordering error in the API, and a check was added for tab position right.

SR-130269 · Issue 197947

SmartInfo call updated for Listview in standards mode

Resolved in Pega Version 7.1.8

After upgrade, instances of SmartInfo configured on listview showed improper styles. This was due to the older version of the SmartInfo control being used when the document was in standards mode. The listview function has been updated to use the updated SmartInfo control for proper rendering.

SR-130363 · Issue 200006

Dynamic decimal place value setting added

Resolved in Pega Version 7.1.8

Previously, the 'pxNumber' control had Decimal Places set to 2. This setting became Auto in ML7, which resulted in no decimal values being displayed for whole numbers in some installations with custom settings after upgrade. To facilitate overriding this out-of-the-box function, a dynamic setting has been added: create a dynamic system setting rule with purpose "DecimalPlacesforpxNumber" in the ruleset "Pega-UMicrosoft Internet Explorerngine" with a given value from -1 to 10, and it will override the Auto value in the pxNumber control decimal places setting.

SR-130563 · Issue 201651

Resolved script errors for dynamic container refresh

Resolved in Pega Version 7.1.8

When a screen designed with Tab Group and Dynamic Container was refreshed through Button/ModalWindow/f5, a JavaScript error was generated and the buttons were not clickable. To correct this a null check will be performed while initializing tabs.

SR-130604 · Issue 198248

Improved handling of load balancer cookies

Resolved in Pega Version 7.1.8

When going through the load balancer and custom authentication, two Pega-RULES cookies were being added to the requests as the user progressed through using the application and errors were displayed on the login screen for subsequent sessions. One of the Pega-RULES cookies was from the previous user session, and a file cookie was being added at the browser level that contained the Pega-RULES cookie. This was an issue where if the responseheader object had a iac-nongateway string in lower case when run through load balancer (like webseal or cisco f5), it collected the second cookie due to the case mismatch in the API. The system has been updated to shift the case of the responseheader object name to better handle differences related to various load balancing applications.

SR-130655 · Issue 198806

Validation handling improved for date value

Resolved in Pega Version 7.1.8

When a value was provided from the Calendar Icon, the value was not going to the clipboard automatically from pxDateTime control when the "Enable client side validation" checkbox was not checked in the advance tab of the harness. The pxDateTime control should not have been relying on the client side validation, and this has been corrected.

SR-130671 · Issue 198217

Sort and filter check added for embedded sections in repeat grid columns

Resolved in Pega Version 7.1.8

In a repeat grid where sort and filter options were enabled on all the columns and one of the columns contained an embedded section, the sort and filter functions were not working on the column with the embedded section if the name of the embedded section was the same as the name of any property used for other column in the repeat grid. This issue was due to an incorrect call to pzGenerateControl for the cell containing the section include, and has been fixed by adding a check for section includes.

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