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-A14403 · Issue 230497

Confirmation Message no longer appearing twice in confirm harness

Resolved in Pega Version 7.2.1

When the out-of-the-box pyWorkConfirmMessage section is included in an application and displayed in one of the steps while running the application, the pyWorkConfirmMessage section will display pyConfirmationNote property value of the work object present in pyWorkPage and will also display the pyConfirmationNote value defined at assignment level present in pxFlow page. This was traced to an additional call step in the function, and the handling has been modified to produce the expected results.

SR-A15013 · Issue 233710

Localization added to AddCoveredWork InsAudit

Resolved in Pega Version 7.2.1

Localization has been added to param.InsAudit in the Pega Final activity AddCoveredWork.

SR-A15491 · Issue 231066

Access control added for duplicate work baskets

Resolved in Pega Version 7.2.1

out-of-the-box functionality allows a user to add duplicate workbaskets to all users. An option has now been added to set restrictions on this ability: the 'when' rule "PYHAVEWORKBASKETSEDITACCESS" can be used to control access to the ability to add or modify the workbaskets as desired. In addition, a validation check will be performed on any duplicate entry of WorkBaskets for an operator.

SR-A15491 · Issue 231387

Access control added for duplicate work baskets

Resolved in Pega Version 7.2.1

out-of-the-box functionality allows a user to add duplicate workbaskets to all users. An option has now been added to set restrictions on this ability: the 'when' rule "PYHAVEWORKBASKETSEDITACCESS" can be used to control access to the ability to add or modify the workbaskets as desired. In addition, a validation check will be performed on any duplicate entry of WorkBaskets for an operator.

SR-A15495 · Issue 230541

Audit screen supports localization

Resolved in Pega Version 7.2.1

AddCoveredWork has been updated to localize the audit text.

SR-A15496 · Issue 230542

Audit screen supports localization

Resolved in Pega Version 7.2.1

AddCoveredWork has been updated to localize the audit text.

SR-A15593 · Issue 231998

Better date selection retention in Calendar view switching

Resolved in Pega Version 7.2.1

Switching to weekly view and then back to daily view in the calendar caused it to reset to the first day of the week and ignore a selected date. selected date is ignored. The container handling has been updated to better handle retaining the selection on different views.

SR-A16566 · Issue 232088

TrackAction and TrackAchievement no longer require authentication to run

Resolved in Pega Version 7.2.1

When an unauthenticated client called an external service (Service-HTTP, SOAP, etc.) that upon completion uses an activity that uses Requestor-Stop instead of allowing the requestor to time out, an error was generated. This was due to the new rule PXTRACKACTION defaulting to 'Require authentication to run', a conflict when an unauthenticated service invokes this activity. The 'Require authentication to run' setting has been unchecked for the pxTrackAction and pxTrackAchievement activities.

SR-A16598 · Issue 233879

Work party change refreshes existing harness

Resolved in Pega Version 7.2.1

If a work party was added to a case and the page was then refreshed at the browser level by hitting F5, a new harness appeared for the case type instead of the existing harness. The action order in the on-change action has been updated to correct this.

SR-A16899 · Issue 233288

ID Security enhanced for PostToSocialStream

Resolved in Pega Version 7.2.1

It was possible to to change the actor name with a runactionwrapper call to pzPostToSocialStream. This was a potential security issue where the parameter could be altered to post a message on some other's behalf. Since the actor is always the current operator, the parameter is not needed and a validation has been added in its place to check if the actor is indeed the current user. If this is true the message will be posted, and otherwise the activity will exit.

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