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-A21298 · Issue 239141

NPE on mobile list open resolved

Resolved in Pega Version 7.2.1

A null pointer exception was being generated on mobile device when opening list items. A null check has been added to pega_ui_modaldialog to resolve this exception.

SR-A21298 · Issue 240041

NPE on mobile list open resolved

Resolved in Pega Version 7.2.1

A null pointer exception was being generated on mobile device when opening list items. A null check has been added to pega_ui_modaldialog to resolve this exception.

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-A21378 · Issue 245075

Resolved Interaction Portal unexpected close

Resolved in Pega Version 7.2.1

In Google Chrome, launching a secondary portal and encountering a Content Security Policy issue relating to an image caused the secondary portal to automatically close and the developer portal to be refreshed. This was an issue with a mismatch in the pyrequestor token, and has been corrected.

SR-A21487 · Issue 241066

Corrected GRANT generation for DB2 users

Resolved in Pega Version 7.2.1

When importing a RAP with a view into a DB2 10.1 LUW database, the GRANT statements were failing because of invalid syntax and the view creation was not executed. This was caused by the user name not being properly appended to the grant statement generation for DB2 users, and has been fixed.

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-A21514 · Issue 242070

DateTime calendar displays time in report filter view

Resolved in Pega Version 7.2.1

The DateTime calendar was not displaying time in the pre-report filter screen while the same calendar displayed both date and time in the report viewer screen. This has been corrected.

SR-A21526 · Issue 244743

Decimal formatting kept in autocomplete

Resolved in Pega Version 7.2.1

In some installations, clicking on the auto-complete field caused the decimal format to be lost. For ex: an initial value of 21,000.00 becomes 21000.00. To correct this, the function reload of ajaxengine API has been modified to pass an extra parameter in signature of processOnBeforeSubmit function (of ui_doc_submit API ) that checks 'layouts2refresh' in the function "processOnBeforeSubmit".

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