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-123809 · Issue 185686

Report schedule icon display fixed for SQL

Resolved in Pega Version 7.1.8

When disabling then re-enabling the task for a scheduled report through the report browser, the icon that indicates whether the report is scheduled will sometimes not show. That is, the report is actually scheduled, and will run at the appointed time, but there will be no icon in the report browser to show that it is scheduled. The SQL query to retrieve the list of scheduled reports was being generated incorrectly for certain databases (e.g., MS SQLServer). Therefore the rescheduled reports were omitted from the list, and no icon would be displayed for them. To resolve this, the custom getcontent activity 'pxgetRRContentForRB' has been inserted.

SR-123820 · Issue 185192

Fixed truncated custom datetime in RD

Resolved in Pega Version 7.1.8

If a report was created on work objects that used a property of type DateTime in Report definition output, custom datetime settings were truncated. This was a problem with the grid implementation where the modified GenerateGridHTML. "D" was set always to propTypeForFormatting even for DateTime. It has bene fixed.

SR-123911 · Issue 189019

Changed timing for retrieving autocomplete values after modifications

Resolved in Pega Version 7.1.8

When AutoComplete controls is used to populate Data, a wrong value was sometimes getting populated in the AutoComplete. The issue was due to the delay in change tracking request after the request is complete, causing it to take values from the server before the changes were committed. This has been corrected.

SR-123911 · Issue 192195

Changed timing for retrieving autocomplete values after modifications

Resolved in Pega Version 7.1.8

When AutoComplete controls is used to populate Data, a wrong value was sometimes getting populated in the AutoComplete. The issue was due to the delay in change tracking request after the request is complete, causing it to take values from the server before the changes were committed. This has been corrected.

SR-123960 · Issue 184251

Error message updated for report 'save as'

Resolved in Pega Version 7.1.8

The error message created when doing a 'Save As' report to a private category has been updated for clarity. Previously, the error generated was "The name you entered is not valid". This has been changed to "The name should start with letter followed by letter or digit or underscore".

SR-124198 · Issue 184897

Clarified messages for attachment deletion failure

Resolved in Pega Version 7.1.8

When trying to delete an attachment on the work item without proper authorization, the tracer shows a message being added on TempAttachmentPage in Work- DeleteAttachment activity reading "You are not authorized to delete instance DATA-WORKATTACH-FILE ATPEGA-TASK ". However, this message was not being propagated to the screen and the screen was refreshing as if it worked despite the failure. To clarify the actual results, the DeleteAttachment Activity has been modified to present any messages and to avoid page removal of the TempAttachmentPage and TempLinkPage if there is a message.

SR-124206 · Issue 186503

Clarified handling of unlocked work objects in multinode environments

Resolved in Pega Version 7.1.8

Release lock was not working correctly on a multinode environment. When trying to release the lock from same operator different requestor from different nodes, the error "Unable to unlock this work object" was generated. In a multinode environment, system pulse takes time to update the cache across the nodes, hence the option is not effective immediately. Messaging has been updated to reflect this delay. Once System pulse executes then other requestor will be able to work on this item.

SR-124232 · Issue 185697

Addressed issue with Advanced Notes attachments reopening the work object

Resolved in Pega Version 7.1.8

When a user attaches a note using the "Advanced" option, as part of the out-of-the-box activity it is recreating/retrieving the work object back from the database and causing any changes to the work object done prior to attachment to be lost. The issue was that the SaveNote activity InsHandle parameter was set but the PageName parameter was not, and the system would reopen the workobject assuming it was not in the workobject context. To solve this, the PageName parameter is now set in the SaveNote activity so that the AttachNote does not do an open of the workpage.

SR-124245 · Issue 188290

Clarified handling of unlocked work objects in multinode environments

Resolved in Pega Version 7.1.8

Release lock was not working correctly on a multinode environment. When trying to release the lock from same operator different requestor from different nodes, the error "Unable to unlock this work object" was generated. In a multinode environment, system pulse takes time to update the cache across the nodes, hence the option is not effective immediately. Messaging has been updated to reflect this delay. Once System pulse executes then other requestor will be able to work on this item.

SR-124313 · Issue 190024

FCM remote case type function restored

Resolved in Pega Version 7.1.8

FCM (Federated Case Management) has a button to discover remote case type, but attempting to use it out-of-the-box generated the error "Remote System is not available. Please check the settings". This was due to a lack of authentication in the Service HTTP rules CaseManagement, and the authentication requirement has been removed.

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