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-A3384 · Issue 211149

Added negation(!) handling for 'when' functions in icon control

Resolved in Pega Version 7.2

After migration, the 'when' rule was not evaluating negation(!) correctly in the deprecated icon control. This was caused by changes in the assembly logic stream generation treating 'when' expressions differently when negation is present, and has been resolved by passing the compiled 'when' rule to the handleEvaluateWhen function.

SR-B82049 · Issue 341054

pxCoverInsKey set in audit history when childcase created

Resolved in Pega Version 7.4

On adding an audit note during the creation of the child case, the audit history did not contain the reference to the parent case. Eventually, when the case was referenced, the pxCoverInsKey was populated in the history table. This was caused by an ordering error in the logic and the system has been updated to correct it.

SR-B65131 · Issue 330322

Fixed 'when' rules for showing privileged escalation buttons

Resolved in Pega Version 7.4

Privileged escalation was displayed for a user with access to manager reports due to missing 'when' rules for hiding the Add report/Add category buttons. This has been fixed.

SR-B95191 · Issue 342664

Conditional Required fields fixed when working with accessibility

Resolved in Pega Version 7.4

When Accessibility is in place, the Conditional Required for fields was not working as expected, instead making the fields always required. To correct this, the tag will be generated conditionally after evaluation of required configuration.

SR-B95191 · Issue 341933

Conditional Required fields fixed when working with accessibility

Resolved in Pega Version 7.4

When Accessibility is in place, the Conditional Required for fields was not working as expected, instead making the fields always required. To correct this, the tag will be generated conditionally after evaluation of required configuration.

INC-185847 · Issue 669526

Handling added for disabling weekends when no weekends are available

Resolved in Pega Version 8.7

A browser exception was generated while selecting the option “Disable weekends”. This was traced to a malformed array of weekends in a scenario where the Data-Admin-Calendar instance had all business days checked (i.e., no weekends). To resolve this, DatePickerAssembly and pzGenerateDatePicker have been updated to handle the case when there are no weekends available in the Data-Admin-Calendar instance.

SR-B75373 · Issue 328291

Fixed error when updating change tracking in declare expressions

Resolved in Pega Version 7.4

An error occurred when trying to update the change tracking in a declare expression rule. This was caused by ACR using a reference to an old expression rule cache, and has been corrected by updating the code.

SR-A5110 · Issue 214245

Fixed exception generated by 'getclassname' used with autocomplete

Resolved in Pega Version 7.2

An issue was found in some new installations using autocomplete where trying to set and execute 'getclassname' after a name change caused a conflict between the old and new values. The problem was traced to a function that set the new value and then repeated a call to the old one, nullifying the change. This did not effect upgraded systems due to a difference in the storage stream versions, and the conflict has been resolved by updating the logic

SR-A4488 · Issue 214464

Improved system performance for SQL using ReserveQueueItem

Resolved in Pega Version 7.2

The SQL generated using the stored procedure sppr_sys_reservequeueitem_b has been tuned to improve system performance for all database implementations; DB2, MS SQL Server, and Oracle.

SR-B94506 · Issue 341185

Unneeded clipboard use cleared during sync

Resolved in Pega Version 7.4

During the "delta sync" process, a very large clipboard size (96 MB) was observed for offline sync service requestors. Further analysis showed that the application page contained a property pyOfflineCases which increased the application page size from 28K to 679K. Since the property isn't present in the saved application rule model, the pzDataSyncPackager rule will clear it from the clipboard to improve performance.

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