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-A23979 · Issue 246353

Revamped help docs to clarify ServiceExport directory config

Resolved in Pega Version 7.2.1

An error in the help documentation did not correctly outline the method for changing the ServiceExport directory by modifying prconfig.xml. The directory location is hard coded to StaticContent/global/ServiceExport in the temporary directory, but the location of the temporary directory is configurable using the Initialization/explicitTempDir setting. Changes have been made to the help files to clarify this.

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-A24028 · Issue 245762

Null value support added to VBD partitions SQL

Resolved in Pega Version 7.2.1

VBD partitions fail to load when facts refer to dimensions of SQL type Timestamp, Time or Date, and the dimension value is null. With the partition failing to load, inserts into those partitions hang. The code has been updated to handle null values in these areas.

SR-A24052 · Issue 248427

Orphaned work objects purged by class

Resolved in Pega Version 7.2.1

Orphaned work objects were not purged when their parent was deleted from the database. To resolve this, selecting a Work- object class for purging will also purge all of the orphans in that class.

SR-A24110 · Issue 246955

Fixed new tab opened on manual refresh (F5) of the Case Manager portal

Resolved in Pega Version 7.2.1

Doing a manual refresh (F5) of the Case Manager portal caused a new tab to be created with the harness displayed in it This was caused by the pyKey being incorrectly updated for static tabs, and has been fixed.

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.

SR-A24183 · Issue 247604

Added visibility for XML Stream Rule Form fields

Resolved in Pega Version 7.2.1

The configurable fields "Stream Name" and "XML Type" have been made visible when "Mapping Mode" is "Apply Rule" in the XML Stream Rule Form.

SR-A24402 · Issue 246696

Tuned scheduled reports start calculations

Resolved in Pega Version 7.2.1

In recurring schedule - daily pattern, if the start date was more than one day in the future, either the next scheduled run time was wrongly calculated as tomorrow with the right hour or if the start date was tomorrow, the next scheduled run time was wrongly calculated as today with the right hour. To fix this, the Next execution time calculation in DailyPattern.java now considers the mStartDateTime value.

SR-A24421 · Issue 247092

Case Audit section localized

Resolved in Pega Version 7.2.1

The ChangeStageAutomatic field value was not showing the localized value in audit due to the ChangeStageAutomatic field value not being properly picked when encountering a blank field. To fix this, Embed-ListParams.getHistoryList will set the localized pyMemo instead of the direct pyMemo in pyMessageKey when it is blank.

SR-A24439 · Issue 247958

Operator ID always clickable link

Resolved in Pega Version 7.2.1

When the operator profile was opened from Operator menu drop down at the top right corner of Designer Studio or from the Case Manager portal, the ID link in the ?Operator Profile? popup was clickable in Microsoft Internet Explorer but not clickable in Google Chrome. The system will now present these as links regardless of browser.

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