SR-D51535 · Issue 519474
Enhanced discrimination for tasks in MyPega spaces
Resolved in Pega Version 8.3.2
When using My Pega for spaces and tasks, using drag and drop to move many cases around quickly resulted in tasks intermittently ending up in a state where they could not be updated further and became unusable. Analysis showed that because the milliseconds part of the update time was rounded, the logic of comparing for value between 0 and 1000 failed when the comparison returned -ve value. To resolve this, the comparison has been modified to !=0 and the 'when' rule pyContinueTaskProcessing has been added as an extension along with the appropriate usage guide to restrict processing. By default, the system will consider task name, description, due date, assignee, and rank properties; if more properties are needed to evaluate, this when rule can help.
SR-D54200 · Issue 516775
Custom attachment category parameter passed to dropdown
Resolved in Pega Version 8.3.2
Attempting to use the out-of-the-box “Attachments control” which was configured at design time to use a custom category where both the custom category and the section class were in the same work class resulted in the attachment category dropdown defaulting to “File” instead of the custom category. Investigation showed that the custom attachment category name configured on the control was missing in one of the pre-processing activities sequence. To resolve this, the activity Work-.pzInitAttachContent and the initAttachmentPage activity have been updated to pass the custom attachment category parameter.
SR-D59504 · Issue 524640
Attachment drag drop searches only current Ajax context
Resolved in Pega Version 8.3.2
When the Interaction for customer service was open and more than 1 task from the sidebar was open, the drag and drop zone was missing on any subsequent Task/Cases past the first. In an Ajax container scenario, getElementByID js was searching in all the containers because they were present in DOM, and it was losing context. To resolve this, the code has been updated to only search in the current context when using an Ajax container.
SR-D63976 · Issue 524220
Double decompression of Attachment BLOBs corrected
Resolved in Pega Version 8.3.2
Attachment streams were being double-decompressed on download. This was traced to the GetAttachmentReference activity in which the file was opened then performing a show-html of DisplayAttachment HTML. This internally called the DisplayAttachFile activity which attempted to open the file again, resulting in a double de-compression of the attachment BLOB. This has been corrected.
SR-D64506 · Issue 529333
Improved accessibility around page landmarks
Resolved in Pega Version 8.3.2
Accessibility testing revealed an issue with pages where the main landmark was contained in another landmark. This has been resolved by removing the main role in the FlowActionHTML rule.
SR-D65513 · Issue 530181
URL encryption modified for ShowAllOperators
Resolved in Pega Version 8.3.2
In the control ShowAllOperators the call to pzEncryptURLActionString was introduced to encrypt URLs to avoid hijacking. The content of the URL relied on the pxRequestor.pxWorkGroup property which was resolved using pega:reference tags. This approach worked in versions below 8.x, but in higher versions the tags were not resolved at runtime and results were not displayed. To resolve this, the requestorWorkGroup will be treated as string and passed as parameter instead of using pega:reference tags.
SR-D67323 · Issue 529946
Cross-site scripting filtering added for CreateMergedWordDoc
Resolved in Pega Version 8.3.2
Cross-site scripting filtering has been added for the TemplateName parameter value in the CreateMergedWordDoc section.
SR-D79113 · Issue 543721
Updated DisplayAttachment to handle SIngleClick download from Case Worker portal
Resolved in Pega Version 8.3.2
On using the script "pega.ui.HarnessActions.doAttachmentSingleClick" in the Worker portal to download attachments displayed within a screen flow, the entire application was hanging and no action was invoked even on clicking the Continue or Finish buttons of the screen flow. Whenever an attachment is downloaded using the script function pega.ui.HarnessActions.doAttachmentSingleClick() , an iframe is used and changetracker is called to communicate data between different iframes. However, the case worker portal is a single thread model while the manager and admin portals are multi threaded, which resulted in changetracker freezing on the worker portal. To resolve this, the DisplayAttachment HTML rule has been updated to build the necessary changeTrackerMap for the worker portal.
SR-D80120 · Issue 544213
Custom attachment category parameter passed to dropdown
Resolved in Pega Version 8.3.2
Attempting to use the out-of-the-box “Attachments control” which was configured at design time to use a custom category where both the custom category and the section class were in the same work class resulted in the attachment category dropdown defaulting to “File” instead of the custom category. Investigation showed that the custom attachment category name configured on the control was missing in one of the pre-processing activities sequence. To resolve this, the activity Work-.pzInitAttachContent and the initAttachmentPage activity have been updated to pass the custom attachment category parameter.
SR-D47795 · Issue 524674
Fallback to Pulse notification added for empty incoming account in CallEmailAutomation
Resolved in Pega Version 8.3.2
After upgrade, issues were seen with the sender receiving email notifications for sent messages when alias addresses were used for incoming emails. To resolve this, a fallback mechanism to use a Pulse notification has been added in cases where an incoming email account is not found in the pyCallEmailAutomation activity.