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-A23473 · Issue 246023

WordTextArea function tuned for Microsoft Internet Explorer 11

Resolved in Pega Version 7.2.1

The WordTextArea was displaying base64 encoded text in the IE11 browser. This was a compatibility problem, and the WordInclude.js ' after edit' functionality has been tuned.

SR-A23527 · Issue 247288

Extension point added to enable/disable CMIS integration

Resolved in Pega Version 7.2.1

The implementation for the extension points of the CMIS integration to invoke other integration mechanisms (e.g. SOAP) that can bring the document back and forth from/to the DMS system were public (e.g. trigger pySaveContent, pyDeleteContent, activity pyRetrieveAttachmentContent, etc.) , but the actual 'when' rule needed to enable/disable the functionality was final. To correct this, a new py when rule has been added as an extension point, and pxCMISEnabled is used with it as an OR condition.

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-A23694 · Issue 246996

Timeliness functions modified to return 0 in place of NULL

Resolved in Pega Version 7.2.1

The "Timeliness" function aliases returned NULL for all the CASE statements that returned false, but NULL value using the AVERAGE summarize function in a report definition returned an incorrect result. The following Function Aliases have been updated to return a 0 instead of NULL when the result is false: - pxSLAAgeByClassTimeliness - pxSLAAgeTimeliness - pxSLAHistoryTimeliness - pxSLAAssignTimeliness

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.

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