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-A23378 · Issue 248193

Max limit removed from OperatorsInWorkGroup

Resolved in Pega Version 7.2.1

The Report Definition pzOperatorsInWorkGroup previously returned a max of 50 records per work group. This created difficulty when using pyTransferAssignment with groups larger than that. In order to facilitate large installations, this limit has been removed.

SR-A23395 · Issue 245032

Optimized decision data components

Resolved in Pega Version 7.2.1

Decision data component performance has been optimized to better handle the heavy demands of the java generated for every mapping using get property and set values API calls in all scenarios.

SR-A23395 · Issue 243235

Optimized decision data components

Resolved in Pega Version 7.2.1

Decision data component performance has been optimized to better handle the heavy demands of the java generated for every mapping using get property and set values API calls in all scenarios.

SR-A23445 · Issue 247673

Localization picks up existing translations in child applications

Resolved in Pega Version 7.2.1

If an operator is a member of multiple access group and has access to multiple applications, the localization wizard was not picking up existing translations when the operator switched to another, non-default, application. The UseCurrentAccessGroupForChild has been updated to provide the missing localization.

SR-A23457 · Issue 245079

Tab

Resolved in Pega Version 7.2.1

In a tabbed layout, opening a modal window resulted in the tab name being changed to that of any active window. This was an error in the drilldown window logic, and has been corrected.

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.

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