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.

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-108805 · Issue 149539

Help updated to explain When Rule "ALL" Evaluation behavior

Resolved in Pega Version 7.1.7

A 'when' rule evaluating all pages in page list will only evaluate the properties on pages in the list that contain that property. This may cause a "true" result that does not match customer expectations. The hover help has been clarified to explicitly state that the evaluation results apply only for those pagelist entries where the property exists and not for all the page list entries.

SR-108838 · Issue 154989

Increased limit for Rule_Obj_CaseType

Resolved in Pega Version 7.1.7

Previously, Rule_Obj_CaseType was encountering a byte limit of 65535 in the JVM that impeded the ability to create a desired large number of coverable work types (54+). The system code has been modified to store the rule types differently to avoid generating extra lines of java code for each coverable case type.

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-112203 · Issue 156906

Corrected 'Top Performers' report

Resolved in Pega Version 7.1.7

The "Top Performers" report in the Case Manager portal was returning incorrect values in the 'Avg. Velocity' column due to an incorrect calculation based on the number of days in the selected period. This has been corrected.

SR-114573 · Issue 162421

Corrected 'Top Performers' report

Resolved in Pega Version 7.1.7

The "Top Performers" report in the Case Manager portal was returning incorrect values in the 'Avg. Velocity' column due to an incorrect calculation based on the number of days in the selected period. This has been corrected.

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.

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