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-108009 · Issue 154664

Execution plan reuse on SQL Server 2008 R2

Resolved in Pega Version 7.1.7

Due to the way a SQL server treats execution plans, each decimal bind value with a different scale is treated as a different type. To optimize the execution, the scale value for the execution plans will now be set the same as the table definition for obj- methods.

SR-109455 · Issue 172370

CSS generation fixed for attaching files after validation failure

Resolved in Pega Version 7.1.7

After a validation had failed, uploading a file (through the filePath Control) and submitting the flow action resulted in the page loading with no CSS applied. This has been corrected by changing how the uploading wrapper is applied in cases of validation failure.

SR-110773 · Issue 160105

WorkPage now properly deleted after rule checkin

Resolved in Pega Version 7.1.7

There was an issue with rule check-in where it created the WorkPage with the obj-class Work-ProjectManagement-CheckIn, but it did not delete WorkPage when the check-in was complete. To address this, protective code has been added that checks the class of WorkPage for the existence of expected properties in order to properly handle the related clipboard pages.

SR-111606 · Issue 163137

Improved consistency with multiple class inheritance rules

Resolved in Pega Version 7.1.7

A gap in the handing of multiple class inheritance was causing an issue with the consistency in picking the correct rule from a cache. If the entry was placed in a class where the applies-to class of the rule could not see it, that entry was missed from invalidation later on during the save. This could be temporarily remedied by clearing the cache, but the rule handling has been updated to consistently choose the correct rule from the cache under multiple inheritance.

SR-111945 · Issue 157966

Closing Lucene search popup in Firefox corrected

Resolved in Pega Version 7.1.7

When using Firefox, it was not possible to close the popup box generated by a Lucene search unless a work object was selected first. This was caused by an error the the method used to access the document id, and has been corrected.

SR-112147 · Issue 162872

Missing buttons from modal dialogues after manual resize

Resolved in Pega Version 7.1.7

After a launching a modal dialog from a local action and manually resizing it to make it smaller, selecting another layout from the dropdown menu was causing the re-size icon and OK/Cancel buttons to disappear. To eliminate this problem, the system has been modified to properly reset the height and width of the modal container before displaying the second layout was displayed.

SR-112357 · Issue 163326

Dynamic Select while editing Data Table instances

Resolved in Pega Version 7.1.7

When using DynamicSelect in a few properties under DataTable instances, editing or adding new rows in the DataTable failed to show a list of values from ReportDefinition and generated the error "Select element SwitchboardCategory is missing DSCaption". This was traced to HTMLPropertyParams not being properly passed on to DynamicSelect control, and has been fixed.

SR-112684 · Issue 166387

Updated Datetime extraction with BIX to ensure consistent time zone output

Resolved in Pega Version 7.1.7

When extracting Datetime values from BIX, the time zone returned in that datetime value was inconsistent. This was caused by variations in the save points of the extractions that resolved property types, and the function has been modified to use a consistent save point.

SR-113173 · Issue 163073

Localized ENTER key behavior for IMEs

Resolved in Pega Version 7.1.7

Previously, hitting the ENTER key during field entry created a new row and moved the cursor to it. However, this was not optimal in environments using IME where the ENTER key is typically used to confirm the input of a character for words (such as using Japanese characters). In order to facilitate input while using IMEs, the system now distinguishes whether or not IME is enabled and changes the result of hitting ENTER while entering text fields to confirm alphabet -> character conversion if IME is in use. If IME is NOT enabled (the user intends to input alphanumeric characters), the default behavior remains as creating a new row and moving the cursor to it. IMPORTANT NOTE: this IME feature is not available using IE8, as IE8 does not support the necessary composition events required for this handling, and hitting ENTER will create a new row as before.

SR-113411 · Issue 172581

Modal dialog box closing correctly from repeating rows

Resolved in Pega Version 7.1.7

When adding and removing data from a repeating row, the Popup Modal dialog was not closing when the corner (X) button was clicked. This occurred if there was an active grid in the document and flowaction buttons were hidden: the closemodalflowaction api, which is responsible for closing the flowaction modal on click of close icon, assumed the modal was launched from the grid and incorrectly called the grid's cancelModal. This has been corrected.

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