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.
SR-A17175 · Issue 234726
Corrected results display for upgraded pysearchResultWork filters
Resolved in Pega Version 7.2.1
When applying the pysearchResultWork filter on the native work objects search bar, some results were not displayed as expected after upgrade. This was caused by an error in setting the property for ad hoc cases inside a child activity, and has been fixed.
SR-A17399 · Issue 233769
Cleared authentication requirement check box for PZINVOKECASETYPE
Resolved in Pega Version 7.2.1
SOAP clients were not able to execute authenticated activities (DATA-PARTY-PERSON VALIDATE , WORK-COVER- PZINVOKECASETYPE) due to the out-of-the-box final activity pzInvokeCaseType having 'Require authentication to run' default to checked. This default interfered with the ability to remove a covered case from a cover case, and has been changed.
SR-A17560 · Issue 234697
Added dynamic check to HarnessPurpose parameter
Resolved in Pega Version 7.2.1
If a main flow referenced a subflow with a parameter "HarnessPurpose" and value "Perform", accessing the subflow generated the error "Failed to find instance XXX-Work-Test.Param.HarnessPurpose of type Rule-HTML-Harness." This was an issue where the HarnessPurpose parameter caused a reset of the pxFormName property in the newassignPage, and this has been fixed by checking if the harnesspurpose is dynamic before setting the pxFormName.
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.