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-A20761 · Issue 247086

New test Suite ruleform display resolved

Resolved in Pega Version 7.2.1

When attempting to create a new unit test suite, no ruleform was presented. Instead, raw XML was displayed. To correct this, the TestSuite Rule Form has been autogenerated so that it is viewable and openable in 7.2 in supported browsers.

SR-A20835 · Issue 239814

Resolved class cast exception for Administrator

Resolved in Pega Version 7.2.1

A class cast exception originating with StreamBuilderTools during logging a debug message caused an error when the Administrator account attempted to display records. This has been fixed.

SR-A20982 · Issue 243968

Repeat grid clipboard index fixed

Resolved in Pega Version 7.2.1

On deleting a row from the repeat grid and proceeding, the deleted row was reappearing due to the improper resetting of a clipboard index when a grid has multiple references. The indexing has been fixed.

SR-A21015 · Issue 239858

AddTime calendar logic updated

Resolved in Pega Version 7.2.1

An issue was found with the final output of using the AddTime function in a Business Calendar with Australian Time Zone to add the difference between GMT and Australian time. In the internal APIs being used by this function, whenever parameters to addTime() were given in such a way that the time to be subtracted was same as the difference between the time of a given input date, start time of a business day, it was considered that there was nothing to add to input time and hence incorrect result. The logic in the engine API, CalendarUtitlity.addTime() which is used in addTime() function, has been changed to correctly calculate the desired time.

SR-A21017 · Issue 239317

Parameter label mismatch corrected for import

Resolved in Pega Version 7.2.1

During upgrade, activities or functions which had Parameter type 'Double' were automatically converted to String data type upon Import into the target Environment even when the XML indicated DOUBLE. This was an issue with rendering the value in the UI: the pyLabel for double parameter type was "Double" not "DOUBLE" in the Data Transform rule pyLoadDataTypes, which didn't match. The activity has now been updated to use DOUBLE.

SR-A21569 · Issue 242079

Corrected persistence of deleted requirements links with multiple actors

Resolved in Pega Version 7.2.1

When checking in a specification with more than one actor specified on it, deleted requirement links re-appeared after the rule was closed and re-opened. This was due to an unnecessary section refresh, which has been removed.

SR-A21588 · Issue 241928

Name retrieval updated for node sub-units

Resolved in Pega Version 7.2.1

A retrieval error for the sub-unit name of a node was causing a "Cannot render section" error in the Organization Chart tab. This has been corrected.

SR-A21810 · Issue 231480

PreClose updated to better handle inactive DC documents

Resolved in Pega Version 7.2.1

The PreClose extension point was not always being triggered for inactive DC documents utilizing the pzClearRecentItem and pzClearAllRecentItems APIs due to stale settings. The correct this, the handlegadgetLoad method has been updated to delete the docObj after the document has loaded.

SR-A21830 · Issue 244836

Improvements made to History Compare

Resolved in Pega Version 7.2.1

The SMS treatment rule full history provided by Pega Marketing was not reflecting the actual changes that were applied in each revision and the compare differences functionality was not showing expected differences. The handling of the comparison has been updated to correct this, and the logic has been further improved to include the "initial creation" version when appropriate.

SR-A21830 · Issue 246779

Improvements made to History Compare

Resolved in Pega Version 7.2.1

The SMS treatment rule full history provided by Pega Marketing was not reflecting the actual changes that were applied in each revision and the compare differences functionality was not showing expected differences. The handling of the comparison has been updated to correct this, and the logic has been further improved to include the "initial creation" version when appropriate.

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