22.7 is a minor release. As communicated earlier, minor releases contain defect fixes and minor enhancements. Minor releases are not made available in production by default. To request an on-demand upgrade, contact Support.

Content

• Announcement
• Bug Fixes

Announcement

Virus Scanner Enablement

We are happy to announce that we will be enabling Virus Scanner by default on communities. 

While this feature has been available and turned on currently for a number of communities, it was not enabled by default. Over the coming releases, it will be enabled by default across communities. This enablement is planned in a phased manner, starting version 22.8.

Learn more about Real-time virus scanner

Bulk Archive enabled for all communities 

With this release, the bulk archive feature is enabled by default for all communities. You no longer need to contact the Support team to have it enabled.

Learn more about the Bulk Archive feature

You found it! We fixed it!

General fixes

• Previously, when community admins sent Event invitations to more than 2000 members via Private Message, the Private Message was not delivered to members and displayed an error message. This issue is fixed. Now, members receive Event invitations via Private Message successfully.
  
  
• Previously, when community admins sent Group Hub or Event invitations to users via email or Private Message and the maximum number of users per invite exceeded the defined limit, the system did not display an error message. This issue is fixed. Now, the system displays an error message that indicates that the number of recipients per invite has exceeded the limit.

• Previously, when users accepted a post with an image as a solution, and the image was in an album they did not have access to, the EntityUpdated event was not triggered, and nothing was written to the event log. This issue is fixed. Now, the events for accepted solutions with images are triggered and logged in the event log.
  
  
• Previously, when members executed an API v2 call to create posts and the maximum number of attachments per post exceeded the defined limit, the API response did not return a proper error message that indicated the respective limit. The issue is fixed. Now, the API response returns a proper error message.
  
  
• Previously, when community admins or moderators added a comment to a post, a Moderator flag was added to the post. This issue is fixed. Now, comments from admins and moderators do not display the Moderator flag.
  
  
• Previously, members received an incorrect notification count from the notification cache. This issue is fixed. Now, the notification cache returns valid values in the notification count.
  
  
• Previously, members could not find the Knowledge Base articles they had edited in the Salesforce platform. This issue is fixed. Now, the Salesforce platform displays all the Knowledge Base articles created or edited in the community.
  
  
• Previously, community admins or moderators who approved threaded comments added to a blog post did not find the pagination for pre-moderated comments. This issue is fixed. Now, the pagination is available for the pre-moderated comments. Community admins/moderators can review and approve these comments.
  
  
• Previously, when community admins sent Group Hub invitations to members via email and user-preferred language was different from the Group Hub node language, members received invitations in Group Hub node language instead of user-preferred language. This issue is fixed. Now, members receive Group Hub invitations in their preferred language.
  
  
• Previously, when community admins sent invitations to users via Private Message and user-preferred language was different from the preferred language of the sender who sent the invitations, users received invitations in sender’s preferred language instead of user-preferred language. This issue is fixed. Now, members receive Group Hub invitations in their preferred language.
  
  
• Previously, the Group Hub email invitations sent to members included the sender's email address, which raised security issues. This issue is fixed. Now, invitations sent to members do not include the sender's email address.

• Previously, the draft articles (Blogs or KBs) of any authors displayed on My Contributions page were visible to all the signed-in users (when My Contributions URL was edited) even if they did not have any specific permissions. The issue is fixed. Now, users cannot view the draft articles of other authors without appropriate permissions. This fix is available in community version 22.6.
  
  
• Previously, when admins ran catalog sync to restore the deleted products, the deleted products were not restored after the sync and error messages were logged in the system. The issue is fixed. Now, the catalog sync restores the deleted products. This fix is available in community version 22.6.

Accessibility Fixes

• Previously, tables on the community pages (Forum, KBs, and All Topics) did not have defined table headers. Members who used screen readers had difficulty understanding the purpose of the data. This issue is fixed. Now, table headers are defined and the screen reader reads out a detailed description of the table.
  
  
• Previously, members who used screen readers could not navigate between the tabs on the screen using arrow keys and were instead using the Tab key to do so. This issue is fixed. Now, members can use arrow keys to navigate between the tabs on the screen.
  
  
• Previously, the screen reader focus moved twice on any element on the community page while members navigated via down arrow key in SCAN mode. Members who used screen readers had difficulty understanding the context of the respective element. This issue is fixed. Now, the screen reader focus moves only once on the element of the community page.