SR-B31818 · Issue 292373
Security update for URL string queries
Resolved in Pega Version 7.3
To ensure sensitive information is not exposed in transit between the client and server via URL query string parameters, pyCaseManager Menu and pzGetUserProfile activity have been updated to avoid passing the user ID as a parameter.
SR-B31818 · Issue 292752
Security update for URL string queries
Resolved in Pega Version 7.3
To ensure sensitive information is not exposed in transit between the client and server via URL query string parameters, pyCaseManager Menu and pzGetUserProfile activity have been updated to avoid passing the user ID as a parameter.
SR-B31876 · Issue 290136
Correspondence logic corrected for party ID
Resolved in Pega Version 7.3
When using the Send Email smart shape to send correspondence to work party, party Roles containing the string "Owner" (such as "AAOwner") caused the correspondence to be sent to the email address of the "Owner" party instead of the "AAOwner" party. This was caused by a logic error in the party list iteration that used 'contains' instead of 'equals', and has been fixed.
SR-B33088 · Issue 293375
pyGetAttachmentContent modified to access class for new properties
Resolved in Pega Version 7.3
The out-of-the-box properties IsDataPageRefreshed and PxAttachName were generating errors indicating the page contains undefined properties. The issue was with the activity pyGetAttachmentContent. As the properties pxAttachName and pyURL etc. are present in their respective classes and the data page class is Data- the errors were not visible. To correct this, pyGetAttachmentContent has been modified to use Page-Change-Class in the activity to change to the correct class so that properties can be accessed. pzRemoveAttachments and pzRefreshAttachmentList have also been updated to use pyIsDataPageRefreshed (new property created).
SR-B33387 · Issue 298483
Incorporated synchronized timestamp function for addWarning
Resolved in Pega Version 7.3
When the pxWarningCreatedDateTime was the same for two warnings with the same pxWarningName, one of the warnings was not getting justified. To fix this, the addWarning function will use the synchronized timestamp function getCurrentDateTimeUnique() to generate the created time.
SR-B33678 · Issue 292086
Bulk process with only 'case type any' properly assigns all processes
Resolved in Pega Version 7.3
When using Bulk Process with "Bulk Process in Background" checked and only the filter 'Case type is any', only the first process was getting assigned to the operator. This was due to the agent name not being properly set while populating the queue with this filter, and has been corrected.
SR-B33678 · Issue 292524
Bulk process with only 'case type any' properly assigns all processes
Resolved in Pega Version 7.3
When using Bulk Process with "Bulk Process in Background" checked and only the filter 'Case type is any', only the first process was getting assigned to the operator. This was due to the agent name not being properly set while populating the queue with this filter, and has been corrected.
SR-B33962 · Issue 291929
Overview rendering enhanced for multiple subcases
Resolved in Pega Version 7.3
When a case was created with two subcases, assignment of one of the subcases was not getting rendered in the overview section. This was caused by the pzLoadNestedCasesForClass checking contains on pyID and has been resolved by changing the function to check on pzInsKey. Also in step 5.4, the appending of pyID has been changed to pzInsKey.
SR-B34248 · Issue 293070
Performance improvements for Work-Cover-.pyLoadMyCases
Resolved in Pega Version 7.3
Performance issues in Work-Cover-.pyLoadMyCases were traced to code in pyLoadMyCasesNested that made an unnecessary page copy and triggered several data page loads. To improve response time, the page copy activity has been removed and the system will instead use a Boolean value to determine whether to read data from the DB or from the clipboard page.
SR-B35117 · Issue 292760
Split-for shape "open flow" works as expected
Resolved in Pega Version 7.3
When working with a flow that contains a Split-for each shape which loops pyWorkParty and executes a flow on Data-Party class, an error was generated if there was a right-click on the sub-flow shape and "Open flow" was chosen. The sub-flow opened properly if there was a right-click on the sub-flow shape, "View Properties" was chosen, then a click on the "Open" icon right of the flow name. This was traced to the Top Class being passed for opening the flow rule in the Navigation rule "pyMenu" of "Data-MO-Activity-SubProcess-SplitForEach" class. To fix this, the class has been changed from Top to ".pyPageClass" in the Navigation rule "pyMenu" of "Data-MO-Activity-SubProcess-SplitForEach" to open the flow rule