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-A21304 · Issue 242768

Corrected Case Stages rendering on Perform harness

Resolved in Pega Version 7.2.1

After upgrade, the case stages were not rendered properly on the Perform harness. This was an issue with the InsHandle parameter and has been fixed.

SR-A21322 · Issue 241736

CaseDesigner SLA flows updated for MSSQL and PostgreSQL compatibility

Resolved in Pega Version 7.2.1

When the SLA for a process in Case Designer is given the internal flow(pzInternalProcessFlow) as companion flow for the process, the order of pxFlow pages is different on the pyWorkPage between MSSQL and PostgreSQL based 7.2 systems. This was due to the differences in iterating these loops and removing the completed flows, and the system has been updated to produce consistent results.

SR-A21337 · Issue 240900

Bulk transfer includes correct assignment status

Resolved in Pega Version 7.2.1

The pyAssignmentStatus value was being blanked out when doing a Bulk Transfer. This was caused by the system attempting to set a status using an empty field, and has been corrected to ensure the correct assignment status has been set.

SR-A21501 · Issue 242372

Search improved for case tags

Resolved in Pega Version 7.2.1

Search functionality for tags in cases was updated from Lucene search to elastic search, but the change class context was not properly set in all cases. It is now updated to run in workgroup as well as class.

SR-A21835 · Issue 243872

Flow names can now be found when using duplicate search mechanism

Resolved in Pega Version 7.2.1

When using the duplicate search mechanism and trying to resolve a case as duplicate, an error appeared indicating that the flow name could not be found. This was a handling error, and has been fixed.

SR-A21917 · Issue 243020

Added calendar conversion support for Thai locale

Resolved in Pega Version 7.2.1

With locale set to Thailand, the date/time returned caused a substitute operator to be selected. This was an issue with the action time being calculated in the Buddhist calendar used in Thailand whereas the goal time was calculated in the Gregorian calendar. The Buddhist calendar is 543 years ahead of Gregorian, so the isAvailable RUF will convert this date by subtracting the difference.

SR-A22107 · Issue 241929

Empty workbasket names localized

Resolved in Pega Version 7.2.1

In the dashboard of the Case Manager portal, the names of empty Workbaskets were not visible due to missing initialization in the localization. This has been fixed.

SR-A22200 · Issue 242371

Bulk actions filters refresh corrected

Resolved in Pega Version 7.2.1

The values entered into the right side column of the bulk processing filters were not getting submitted to the clipboard when default filter conditions were changed. The refresh action has been updated to correct this.

SR-A22298 · Issue 243924

Refresh corrected for tabbed screen flow perform harness

Resolved in Pega Version 7.2.1

When using the "TabbedScreenFlow7" perform harness, an incorrect refresh call caused the Actions menu on the work object to disappear from the screen. This has been resolved.

SR-A22615 · Issue 244189

Fixed positioning for Options lightbox

Resolved in Pega Version 7.2.1

The Options lightbox in the calendar was floating with the screen while scrolling due to absolute positioning, 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