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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-131217 · Issue 199744

Stopped unexpected trigger caused by attaching note with gadget

Resolved in Pega Version 7.1.8

Declarative rules were being fired every time a note was attached to a work object using the "Notes" gadget (not advanced notes link). To fix this, the pxAttachNote activity has been updated to not trigger the declarative chaining in this scenario.

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-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-113557 · Issue 167227

Dynamic Select correctly expands drop downs with IE

Resolved in Pega Version 7.1.7

While using the WorkBasketGadget with dynamic select, drop downs were not expanding to the full width of the field value and parts of the values were hidden. This was caused by an IE bug. The WorkBasketGadget rule has been modified to overcome the issue.

SR-114545 · Issue 164887

Increased limits for Bulk Processing

Resolved in Pega Version 7.1.7

When attempting to filter cases for Bulk Processing, the Property-List LookupList activity only requested a maximum of 2500 records. This caused an issue with class inheritance chains that contained more than 2500 property records, as those excess properties were not being used to filter within Bulk Processing area. To remedy this, the activity now allows a maximum of 10,000 records for Bulk Processing.

SR-114723 · Issue 166462

Portal calendar display corrected

Resolved in Pega Version 7.1.7

No data was visible for the daily or weekly view when displaying the Calendar on the Portal. This was caused by the height of the time frame for Daily/Weekly being set to a fixed value, causing events which fall under 11PM-12AM to not be displayed properly. In addition, the cell width for monthly view was also set to a fixed value, causing it to show only 4 events and hiding the 'show more' option. To correct this, the Day/Weekly view now includes double height to show all events, and the Monthly view displays 3 events and correctly includes the 'show more' option.

SR-114728 · Issue 166514

Resolved locking problems with doubled flow submissions

Resolved in Pega Version 7.1.7

If a Page validation message was present and an additional flow action was submitted through a second action menu, a "Lock Lost" message was generated. This was traced to the "Release on Commit" checkbox defaulting to 'on', and it has been set to a default condition of 'off'.

SR-114807 · Issue 162848

"Transfer to an Operator" dynamic list was not sorted

Resolved in Pega Version 7.1.7

The "Transfer to an Operator" dynamic list was not sorted, while the "Transfer work from" dynamic list was. This was caused by different function calls in the system, and has been corrected so the lists sort properly by property name.

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