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-131323 · Issue 201113

RD operator filter max value increased

Resolved in Pega Version 7.1.8

The limit for items displayed by the RD filter pxCreateOperator has been increased to 1000.

SR-131522 · Issue 200840

Localization added for report name tooltips

Resolved in Pega Version 7.1.8

Tooltips in reports for report names are now available for localization.

SR-131538 · Issue 200108

Removed extra blank line from exported SV report

Resolved in Pega Version 7.1.8

An Excel spreadsheet exported from any Summary View (SV) report contained a blank row at the top. This has been corrected.

SR-132135 · Issue 202410

Smoothed 'save as' for private reports without checkout privs

Resolved in Pega Version 7.1.8

When a user did not have checkout option either at the operator level or at the design time rule-set level, trying to use 'Save As' on Report definition rules reports in Private category resulted in an error but actually saved the report at the back end. Opening the Case Manager portal and trying to do a 'save as' of an existing report led to the report category being populated as private but the standard categories got populated in the drop down. If OK was clicked, then the standard categories were replaced with private category. To improve this, a check has been added to detect a non-developer operator, who is then allowed to save in their personal category.

SR-132538 · Issue 201237

Updated RD handling for WorkBasketAssignments

Resolved in Pega Version 7.1.8

After upgrade, if the Assign-WorkBasket pyWorkBasketAssignmentsDefinition report definition included the WHERE criteria .pxSystemFlow== 'FALSE', workbasket assignments for existing cases were not displayed in the harness. This was due to the new PXSYSTEMFLOW column in the pc_assign_workbasket DB table not properly handling this criteria, and a check has been added to resolve this.

SR-132569 · Issue 201349

Corrected portal refresh after chart unload

Resolved in Pega Version 7.1.8

When a chart is unloaded, a separate request was sent to the server to remove all chart-bounded data pages, i.e. pzRuntimeChartCleanup. If nothing is returned, the ActivityStatusSuccess Message was seen instead of the Work Item when the portal was refreshed. The API has been updated to return the correct information.

SR-129239 · Issue 200337

Added handling for Flow not at Task error

Resolved in Pega Version 7.1.8

Flow not at task and flow removed errors were appearing sporadically. This happened when the trigger fired off the commit inside the post-processing called CorrUpdateNoWO and returned a stale copy of the Workobject, and was complicated by an assumption that was trying to iterate over "pzInternalCaseFlow". This has been addressed in the CORRUPDATENOWO activity.

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.

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