SR-D71475 · Issue 538720
Check added to apply values of newAssignPage.pxFormName
Resolved in Pega Version 8.3.2
After upgrade, trying to open existing assignments resulted in a different harness being opened. This was traced to changes in how the property newAssignPage.pxFormName was used, and has been resolved by checking whether the harnesspurpose is dynamic before setting the pxFormName. If formname is already present, the system will proceed with picking the harness from the shape.
SR-D72672 · Issue 536386
Security updated for CreateOperator
Resolved in Pega Version 8.3.2
In order to improve security, CreateOperator in Pega-ProCom will require authentication to run with pxCanManageUsers privilege.
SR-D75469 · Issue 538119
Resolved null-pointer exception in Expression Builder launch from activity rule
Resolved in Pega Version 8.3.2
A NullPointerException occurred in SafeURL when trying to launch the Expression Builder from an activity rule. This was trasced to a failure to get a value property in a target field due to the target element and its parent element containing the same value for name attribute. This caused the parent element to be considered instead of the target element. To resolve this, the search for the target element in parent tag will use '$p' along with 'target element name' in query selector.
SR-D75835 · Issue 539301
Added handling for Google Chrome drag and drop of Outlook email
Resolved in Pega Version 8.3.2
Attempting to drag and drop an email from Outlook to a case opened in Google Chrome resulted in the email being moved to the Outlook deleted folder. This was traced to Google Chrome defaulting to defining the "dropEffect" attribute as "none" when the expectation is it should be "copy". To resolve this, the recommended handling from Microsoft has been added as an event to make a copy (and not a move) an email from Outlook when dragged and dropped with Google Chrome.