Content

Enhancements

• Encryption of Zoom apiKey
  
• Salesforce Connector 4.3 (Early Access)

Bug Fixes

Enhancements

Encryption of Zoom apiKey 

Earlier, Community Admins shared their organization’s Zoom apiKey and apiSecret values with the Khoros Support team to integrate the Zoom application with Community Events.

With this release, Community Admins can now manually enter, update, and delete the Zoom API ID and secret key values in the Community Admin panel. These values are encrypted and stored in Khoros’ database. Since they are encrypted, external parties cannot access the API ID and secret key values.

To add API keys:

1. Go to Community Admin > Discussion Styles > Events.
2. Specify the Zoom Authentication application ID and Zoom Authentication secret key fields.
   

    

3. Click Save.

Learn more on Integrate Zoom with Community Events

Salesforce Connector v4.3 (Early Access)

This version includes enhancements and addresses issues of the previous versions to improve overall Salesforce-Community integration experience. 

This version provides the following enhancements:

• Better controls over triggers and case-related emails
• Ability to use custom fields to map community and Salesforce contact objects
• SDFC API upgrades to the latest versions, and few other enhancements

NOTE: If you want to be considered for the Early Access (EA) program, contact your CSM. If selected, CSM works with the Support and product teams to upgrade the Community Connector for the Salesforce version.

Learn more on Connector for Salesforce package versions and upgrades

Learn more about the issue fixes and enhancements on all Salesforce Connector Versions

You found it! We fixed it!

General fixes

• Earlier, there was an issue in some communities where digest notification messages were not sent out. This was due to the limit on the value of the unique identifier of messages specified in the database table. The issue is fixed. The digest notification tables are now independent of the unique identifier. Communities can now send as many digest notification messages as needed. 
  
  
• When community admins or moderators added a comment to a post, a Moderator flag was added to the post. The issue is fixed. Now, comments from admins and moderators do not display the Moderator flag. 
  
  
• When a community member other than an admin, moderator, or the owner of a post ran the API query to retrieve the details of a cover_image, they received a permission denied message. The issue is fixed. Now, members with appropriate permissions can successfully run this API call.
  
  
• Previously, when you removed a community member from a community, the database tables did not delete the subscription details. This led to failures when the community restarted or when a backup was done. This issue is fixed. Now, after removing a member, the community restarts successfully.
  
  
• Previously, when community admins sent Group Hub invites to users via email, users received invitations from the email ID of the community admin who sent the email instead of the community email ID. The issue is fixed. Now, users receive invitations from community email ID.
  
  
• When community admins sent Group Hub invites via Private Message and the community’s preferred language was not English, the Private Message received by the members used to have invalid group hub invitation link and creation date values. The issue is fixed. Now, members receive Group Hub invitations with a valid invitation link and creation date values.
  
  
• When community admins sent Group Hub invites to more than 1000 users, many users did not receive the invitations. The issue is fixed. Now, users receive the Group Hub invitations.
  
  
• Event invites used to display the time of an event in the timezone of the member who sent the invite. This issue is fixed. Now, the event’s timezone displays according to that of the receiver.
  
  
• When you used the Advanced search option in Private Messages, the search text field used to display invalid text instead of the specified text or blank text. This issue is fixed. Now, the search text field displays the specified search keyword or is empty.
  
  
• When you assigned editor and publisher roles for a board in Blog v3 and TKB V4 (or any later versions of Blogs and TKB), members used to be assigned to these roles for all the boards in that node. The issue is fixed. Now, members are editors and publishers only for the assigned boards and receive notifications for these boards only.
  
  
• 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.
  
  
• 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.

Accessibility Fixes

• The View Link link on the community page did not have a description other than the name of the link. Members who use screen readers had difficulty understanding the purpose of the link since it did not have enough text to read out. This issue is fixed. Now, the screen reader reads out a detailed description for the link.