SR-C4046 · Issue 351373
JAWS reads group layout tab headers
Resolved in Pega Version 7.4
When using JAWS for 508 testing, the screen reader was reading group layouts with tab numbers rather than the field value provided for the header. This was due to missing aria-labels, which have now been added.
SR-C4784 · Issue 347888
Tooltips display fixed for Google Chrome hover
Resolved in Pega Version 7.4
When launching an interaction for the first time using Google Chrome, tooltips for the link were not displayed correctly on hover. Refreshing or reloading the frame displayed the tooltips as expected. This was due to an issue with focus in Google Chrome, and has been corrected.
SR-C4784 · Issue 346817
Tooltips display fixed for Google Chrome hover
Resolved in Pega Version 7.4
When launching an interaction for the first time using Google Chrome, tooltips for the link were not displayed correctly on hover. Refreshing or reloading the frame displayed the tooltips as expected. This was due to an issue with focus in Google Chrome, and has been corrected.
SR-C4784 · Issue 344824
Tooltips display fixed for Google Chrome hover
Resolved in Pega Version 7.4
When launching an interaction for the first time using Google Chrome, tooltips for the link were not displayed correctly on hover. Refreshing or reloading the frame displayed the tooltips as expected. This was due to an issue with focus in Google Chrome, and has been corrected.
SR-C928 · Issue 343908
True/false values localized in report filters
Resolved in Pega Version 7.4
Localization has been added to the labels of grid Section pzAvailableValues.
SR-B69751 · Issue 325146
Resolved button select error in PegaSurvey
Resolved in Pega Version 7.4
In Pega Survey, the 'Simple Question' with 'Answer mode' of 'RadioButtons' was not working properly: selecting one radio option via mouse click caused another radio option to be selected after the buttons were clicked multiple times. This was traced to legacy code which required an extra refresh in SurveyScripts for a Survey smart shape. This code has now been removed as it is not required in QuestionScripts.
SR-B14783 · Issue 291708
Added image retrieval support to correspondence rule
Resolved in Pega Version 7.4
If images were present in the correspondence rule used to send emails, no images were visible in the emails sent out from Pega after restart. This was traced to 'SendEmailNotification' using the 'StaticContentUtilsImpl.getResolvedFile(String)' engine API to fetch the Image bytes, which did not have the necessary support to fetch 'Data-Content-Image' content. This has been added.
SR-B74711 · Issue 328307
Added image retrieval support to correspondence rule
Resolved in Pega Version 7.4
If images were present in the correspondence rule used to send emails, no images were visible in the emails sent out from Pega after restart. This was traced to 'SendEmailNotification' using the 'StaticContentUtilsImpl.getResolvedFile(String)' engine API to fetch the Image bytes, which did not have the necessary support to fetch 'Data-Content-Image' content. This has been added.
SR-B84855 · Issue 339079
Clarification on DSN Thread Topic parsing
Resolved in Pega Version 7.4
The PDN article regarding parsing DSN emails incorrectly stated that "If the message triggers a DSN, the Thread-Topic value is still intact. You can map the value from this header to a utility named parseThreadTopicHeader in the Message Header section on the Request tab. Be sure to specify the pyInboundEmail page property in the Map To Key field." In actuality, the Thread topic is not intact for all domains; it depends on the email provider. If the thread topic is not present in the DSN mail header, custom logic will need to be added in the email service activity rule to get it from the mail content.
SR-B96972 · Issue 343423
Specification rule save-as loads requirements
Resolved in Pega Version 7.4
While doing 'Save As' of a Specification rule from a locked ruleset version to a higher unlocked version of the ruleset, the linked Requirements were not shown in the Requirements section under the Details tab. Sometimes a refresh would show the requirements, but intermittently an exception would be generated. This was traced to the system not auto-populating the requirements list on 'save as' of the specification, and code has been added to PostActionSaveAs of the 'Rule-Application-UseCase' class to populate the Requirements link on 'save as' of this rule.