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.
SR-D48246 · Issue 518689
TextAnalyzerClass will be populated during upgrade if not present
Resolved in Pega Version 8.3.2
After upgrading, the email channels were failing to process the emails and the error "Unable to load data page D_pyEntityClassMapping. Required parameters : ClassName cannot be blank" was seen in the tracer log. Analysis showed the email channels were failing to process the emails due to the pzUpgradeVersion property in Data-Channel-Email instances being inconsistent post-upgrade. To resolve this, the system has been updated so if the TextAnalyzerClass or name property is not present in old email channels (created in 7.4), it will populate that property in the upgrade activity with the default classname.
SR-D49782 · Issue 518047
Extension point added for ClearInteraction to support custom interactions
Resolved in Pega Version 8.3.2
In order to support clearing a custom interaction page after clicking the "Reset" button on preview console, an extension point has been added to pyClearInteraction.
SR-D54120 · Issue 541351
Improved handling for attachments not using UTF-8 encoding
Resolved in Pega Version 8.3.2
When an email was received that used a charset encoding other than UTF-8, special characters in the HTML body were not displayed and instead the replacement character was shown. To resolve this, the system will read the encoding from the email rather than use the meta tag, and will add the attachment's HTML encoding information in Data-WorkAttach-File so that the same can be used to process and display the original HTML properly.
SR-D57865 · Issue 520962
Added property check for outbound templated email reply
Resolved in Pega Version 8.3.2
When a template was used for the first time for outbound correspondence, email was generated correctly. If the same template was used as the content for reply, the generated email skipped all styles. This was traced to a missing property check, and has been resolved.