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-123303 · Issue 176110

Corrected Case match rule reporting

Resolved in Pega Version 7.1.8

The Case match rule was not reporting results that were greater than the cut off score. This has been corrected by changing the rule RunDuplicateCasesReport to check on InsKey instead of pyID as InsKey is available for all pages of different classes where pyID is not.

SR-123492 · Issue 184136

Page properties cannot be configured in remote case types

Resolved in Pega Version 7.1.8

The implementation of the Case Type advanced tab allowing page properties to be referenced under 'publish as a remote case type' was sometimes generating a validation error. As this is a complex issue, the abilty to configure Page properties in remote case types has been removed at this time.

SR-123492 · Issue 183606

Page properties cannot be configured in remote case types

Resolved in Pega Version 7.1.8

The implementation of the Case Type advanced tab allowing page properties to be referenced under 'publish as a remote case type' was sometimes generating a validation error. As this is a complex issue, the abilty to configure Page properties in remote case types has been removed at this time.

SR-123533 · Issue 187272

Corrected calculation of WO SLA Goal,Deadline based on calendar input

Resolved in Pega Version 7.1.8

The calculation of Goal,Deadline for WO SLA was not showing the expected results based on business days in the calendar. This was caused by not passing the appropriate parameter (CalendarName) to Work-.DefineSLATimesFromNewProperties so that BusinessCalendar.addTime function could evaluate the SLA based on the calendars, and has been fixed.

SR-123623 · Issue 178641

Added clipboard clearing for correspondence

Resolved in Pega Version 7.1.8

External assignment was sending out the email correspondence that was configured in earlier stages/flows instead of sending the correspondence that is given in the external assignments rule form. This was a problem with the clipboard where CorrPage was not cleared after the CorrCreate is invoked. To resolve this, CorrNew activity has been modified to add a step to clear the CorrPage.

SR-123623 · Issue 184847

Added clipboard clearing for correspondence

Resolved in Pega Version 7.1.8

External assignment was sending out the email correspondence that was configured in earlier stages/flows instead of sending the correspondence that is given in the external assignments rule form. This was a problem with the clipboard where CorrPage was not cleared after the CorrCreate is invoked. To resolve this, CorrNew activity has been modified to add a step to clear the CorrPage.

SR-123968 · Issue 194580

Added special character handling to Process Modeler

Resolved in Pega Version 7.1.8

After migration, some sites attempting to open flows through Process Modeler saw only the 'loading' message for a long time and then an error was displayed. This was traced to the use of user-input strings containing special characters in the canvas-based rule data, and has been resolved by adding character escaping during the model generation.

SR-123968 · Issue 194306

Added special character handling to Process Modeler

Resolved in Pega Version 7.1.8

After migration, some sites attempting to open flows through Process Modeler saw only the 'loading' message for a long time and then an error was displayed. This was traced to the use of user-input strings containing special characters in the canvas-based rule data, and has been resolved by adding character escaping during the model generation.

SR-124054 · Issue 189568

Simulation delete timing issue resolved

Resolved in Pega Version 7.1.8

When attempting to delete a simulation, if the deletion process exceeded the system time-out or the space on the database required for undo was too small (as can occur when many simulations have been run and the simulation output table contains many millions of records), the mass deletion failed and the system became hung or returned a time-out screen which required logging out and in again. At that point it was seen that the simulation results had been removed from the list but the actual results deletion did not complete. This was caused by the simulation work item being closed first, followed by the delete of the table. In the case of a failed deletion because of any DB issue, manual intervention was required to delete the records from the table as the simulation object was no longer available. To resolve this, the sequence of steps while deleting the Batch WO from LPhas been updated to show the relevant error message in case of failures for any reason, and the work object is closed after the output table is deleted.

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.

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