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-A23665 · Issue 248776

Percentage calculated by control carried into Excel export

Resolved in Pega Version 7.2.1

If a Report Definition calculated the percentage by using the control, the percentage would display in the report browser but 0.00% would be displayed in the Export to Excel. The step page for the control being executed at display time and export are different, so the activity is unable to get the ".pySummaryCount(1)" from the step page. To fix this, pzGetHTMLPropertyValue has been modified so it acts on the step page of the property rather than the primary page the function was executed against.

SR-A23668 · Issue 245756

Corrected syntax for pyAdjustAssignmentSLA

Resolved in Pega Version 7.2.1

An extra space present in the label prepended for pxTaskLabel caused severe warnings to be generated by pyAdjustAssignmentSLA that were lowering the application compliance score. This syntax error has been corrected.

SR-A23689 · Issue 245765

Unnecessary diagnostic message removed from logging

Resolved in Pega Version 7.2.1

The Server log of PegaRULES was displaying the confusing message "Here Thru the Branch Code": this was an unnecessary diagnostic trace and has been removed.

SR-A23692 · Issue 245660

Scheduling dialogue correctly releases lock on browser pop-up exit

Resolved in Pega Version 7.2.1

Opening the scheduling dialogue for a currently scheduled report created the proper locking, but "X"-ing out of the pop-up report window without editing it was not releasing the lock and the report was then not executed as scheduled. To avoid this, a Rule-Obj-Casetype has been added to control when the schedule is locked and will also release the lock when the changes fail validation.

SR-A23709 · Issue 247989

Performance improvements for Scheduled Export to Excel

Resolved in Pega Version 7.2.1

Some memory usage improvements have been made for exporting reports to Excel through the scheduler.

SR-A23735 · Issue 248542

Image/Label of Report checkbox clickable

Resolved in Pega Version 7.2.1

In the Report Browser, icons and text labels have been linked to the checkbox and are clickable to check/uncheck the list/chart/summary filters.

SR-A23817 · Issue 246191

Enabled SLA calculations for drag and drop reassignments

Resolved in Pega Version 7.2.1

SLA was not firing when an assignment was dragged and dropped from a workbasket to a work list and vice versa. This was due to a missing update to the assignment handle for the queue item, and has been fixed.

SR-A23912 · Issue 246952

Custom filters won't display header container icons

Resolved in Pega Version 7.2.1

Unwanted icons were appearing when using a custom filter section that has a grid with a header/title, such as an 'X' close icon displaying next to an included section/repeat grid coupled to the filter section launched from the report browser for a report definition. The harness that displays the filter section has been modified to not include the icons that come with a container that has a header.

SR-A23997 · Issue 248204

ResumeFlow copied to @baseclass to support Split For Each Advance flow

Resolved in Pega Version 7.2.1

Split For Each Advance Flow Fails on Data Instances with error: Failed to find a 'RULE-OBJ-ACTIVITY' with the name 'RESUMEFLOW'. This was traced to the context of the assignment being on a Data- instance while ResumeFlow is defined at Work-, causing all processing to fail for the resume. This has been fixed by creating a version of ResumeFlow in @baseclass which in turn calls Work- ResumeFlow.

SR-A24114 · Issue 246936

Removed hardcoding from pyWorkPage

Resolved in Pega Version 7.2.1

The function pzIsAFollower contains "pyWorkPage", which is hard-coded to get the handle of the Primary Page. However, if the primary page was a different named page and not pyWorkPage, an exception was generated. This has been resolved by removing the hardcoding in pzIsAFollower().An overloaded function has been created for pzIsAFollower() which takes reference page name as parameter, and the when rule which calls this utility function to pass the parameter has been updated.

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