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-A23222 · Issue 244490

"Deadline date" corrected for German locale

Resolved in Pega Version 7.2.1

When a case was opened, the deadline shown in the top was in the wrong format for a German locale. This was caused by the standard translation method being used, and has been corrected by replacing the non-auto-generated pyCaseDeadline control with pxDateTime control to fix the issue.

SR-A23282 · Issue 245229

Checkout to branch ruleset handling improved

Resolved in Pega Version 7.2.1

The Checkout to branch option was not able to find a list of branches in Pega Marketing after a minor ruleset migration. To resolve this, the system will make use of a non versioned ruleset name for showing branches if an application is referring a ruleset whose major or minor version is different from the Ruleset of the Rule that is being checked out.

SR-A23339 · Issue 247921

Non-versioned class rule forms updated during upgrade

Resolved in Pega Version 7.2.1

The non-versioned class rules in an environment were skipped during upgrade due to an error in the RevalidateAndSave function. This has been corrected.

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.

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