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-A17670 · Issue 236156

New display control for attachment category delete privilege

Resolved in Pega Version 7.2.1

If an attachment category delete privilege was set to 'never' but there was no access group referenced for it, it was possible for the user to delete the attachment. This was a scenario where even though the delete-all option was enabled for the attachment category, the display of the delete icon was not controlled by this access specifier. A new when condition "HaveAttachmentDeletePrivileges" has now been added on the delete icon to control whether or not the icon appears.

SR-A17738 · Issue 234851

Authentication requirement removed from OnProcessEnd

Resolved in Pega Version 7.2.1

pzChangeStageWrapper calls pzOnProcessEnd, which requires Authentication and is a Final rule. This created an issue using the ChangeStageWrapper without authentication, and the authentication requirement has been removed from OnProcessEnd.

SR-A17852 · Issue 234570

Edit Validate passes parameters to message rule

Resolved in Pega Version 7.2.1

When using an Edit Validate rule in the condition, functions could not be passed as a parameter into a message rule. This has been fixed.

SR-A17938 · Issue 236489

Custom header section of Calendar retained after Smartinfo popup displayed

Resolved in Pega Version 7.2.1

Due to the way the date/time parameters were handed, the Smartinfo popup was overriding a currency icon and logo set into a custom header of Calendar events to show currency market closings (holiday, etc.). A check for custom values has now been added.

SR-A18100 · Issue 234215

BIX documentation updated for new "-J" timezone conversion option

Resolved in Pega Version 7.2.1

A -J option has been added to BIX to allow the specifying the timezone for datetime properties to be converted to when written to the XML output file. The documentation is as follows: A new command line option J is being added to take in a user specified time zone for e.g., UTC+05:00 format(s); If the specified timezone is not valid, it defaults to GMT example :How to specify this option: "-J" "UTC+5:30"

SR-A18230 · Issue 234568

Enabled SLA calculations for drag and drop reassignments

Resolved in Pega Version 7.2.1

SLA was not firing when an assignment was dragged and dropped from a workbasket to a work list and vice versa. This was due to a missing update to the assignment handle for the queue item, and has been fixed.

SR-A18261 · Issue 235785

CaseManager Following list properly updating work

Resolved in Pega Version 7.2.1

When there was at least one participant (workparty), clicking on the follow link in the Case Manager would only give the current status and would not update unless the workparty was unfollowed and followed again. This was required each time to get the updates. The issue was with the declare indexes not being generated correctly because of missing metadata between the workpage and workparty while doing a page copy. This has been fixed.

SR-A18481 · Issue 238244

Enabled SLA calculations for drag and drop reassignments

Resolved in Pega Version 7.2.1

SLA was not firing when an assignment was dragged and dropped from a workbasket to a work list and vice versa. This was due to a missing update to the assignment handle for the queue item, and has been fixed.

SR-A18656 · Issue 235214

Fixed typo in pyUpdateWorkPartiesBefore

Resolved in Pega Version 7.2.1

Activity pyUpdateWorkPartiesBefore was not functioning\ as expected due to a typo that indicated "Primay" instead of "Primary". This has been corrected.

SR-A18657 · Issue 239739

property-ref mapped table updated during optimization

Resolved in Pega Version 7.2.1

On optimizing any top level property after upgrade, the existing values present in the reference property columns were getting reset. This has been corrected.

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