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-131816 · Issue 200787

Required date properties now working correctly in modal windows

Resolved in Pega Version 7.1.8

Marking a date property as required in a modal window was not actually setting the property as required. The problem was traced to a missing comma between 'date' and 'required' in the validationtype attribute on the field when there is an edit input associated. This datetime issue has been corrected.

SR-132002 · Issue 201652

Resolved date format changing with Microsoft Internet Explorer refresh

Resolved in Pega Version 7.1.8

When using the Microsoft Internet Explorer browser, the date format DD-MMM-YYYY was losing its format after refreshing or applying a validation rule or Data Constrain rule. The GenerateDatePicker logic has been updated for Microsoft Internet Explorer to correct this.

SR-132106 · Issue 200970

Decimal separator issues addressed for Microsoft Internet Explorer 9 and German locale

Resolved in Pega Version 7.1.8

Using the Microsoft Internet Explorer 9 browser and the German locale setting, the comma decimal separator was lost following several refreshes and the value was multiplied by the unanchored digits. In case of format type is "number" and "Display value using read-only formatting" enabled, the input type is generated as text but data-value was still being set with a clipboard value instead of localized value. This generation has been changed to a formatted value as data-value attribute on the input element to fix the issue. Please note that this will address customer configuration where "Display value using read-only formatting" is enabled. If this option is not enabled, the input will continue to be generated as a number and in such cases refreshes with separators may not work and can't be fixed due to browser limitation/behavior for input type number.

SR-132677 · Issue 201726

Resolved decimal property validation error

Resolved in Pega Version 7.1.8

On validation, an extra space was being added to a decimal property which then caused the validation to fail. This was caused by the pzPerformGridAction activity calling the ProcessAction activity with a new parameter page which was not receiving the inStandardsMode parameter value from the original request, leading pzGenerateFormat to assume that the browser is in Quirks mode. This has been fixed.

SR-132895 · Issue 201403

Fixed onchange while offline for PegaMobile

Resolved in Pega Version 7.1.8

If a post value on a checkbox or radio button controlled the visibility of another layout in Mobile, checking or unchecking a checkbox many times or running the screenflow several times while offline caused the visibility based on the post value to stop working. This has been resolved by changing the handling to click events for Checkbox and RadioButton in mobile instead of tap.

SR-133155 · Issue 202487

Modified locking to handle popup switch

Resolved in Pega Version 7.1.8

The lock on a Work Item opened in No Frame Portal was being lost when a Pop up was opened from the Work Item. In NoFrame portal scenarios, moving away from a Work Item releases the lock as per design, but the lock was also being released when a popup was opened. This has been corrected by adding a popup check that will maintain the lock .

SR-128373 · Issue 200522

RTE spellcheck maintains correspondence images

Resolved in Pega Version 7.1.8

After using the RichTextEditor control to edit correspondence, images were removed from the correspondence that was sent if spell check had been run using the control's built in spell check button prior to sending. The issue happened with only YUI RTE in quirks mode. YUI RTE is a deprecated control and is replaced by CKEDITOR in Pega7. The issue is not reproducible in CKEditor.

SR-128684 · Issue 194308

Corrected save-as for Activity using API "02"

Resolved in Pega Version 7.1.8

In drop down generation, if a value was empty then adding the selected attribute for the first option assuming no options should have the empty value other than no selection text. To make this work as expected, if the value is empty then the system will add the selected attribute on the option which has empty value to avoid setting first option value to the hidden field.

SR-128738 · Issue 200611

Corrected label text wrap for other template layout for Google Chrome/Firefox

Resolved in Pega Version 7.1.8

Text Wrapping for labels was not working for layout which uses other template with the FireFox and Google Chrome browsers, but was fine in Microsoft Internet Explorer. This has been fixed by setting the other style to White-Space:normal.

SR-132880 · Issue 201431

Design time clarification for radio button configurations

Resolved in Pega Version 7.1.8

Previously, it was possible to configure an on-click event on a radio button in a repeating grid. This configurability was an error - although it was possible to set it up, the actions would not actually fire as intended due to the way the radio buttons work. In order to remove confusion, the actions tab for radio buttons has been removed from design time and checkboxes should be used if on-click actions are desired.

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