Lithium Community 18.5 Release Notes

New Features 

• GDPR updates 
• Revised email templates: Subscription Search and Subscription Search Blogs 
• Salesforce Connector 
  • GA release of Salesforce Lightning connector 
  • Ability to configure the number of search results for Salesforce federated search  

GDPR updates 

Rank and Role personal information 

Starting with the 18.5 Release, member Rank and Role information is now treated as personal data. As such, when members close their account or their accounts are deleted, rank and role information associated with the member's account is also removed.   

Private messages information 

Starting with the 18.5 Release, the contents of private messages a member has sent via the community is included in their community content download file. Learn more about a member's ability to download community content information. 

Revised email templates: Subscription Search and Subscription Search Blogs 

We have fixed the Subscription Search and Subscription Search Blogs email notification templates to use more secure template objects. Specifically: 

•  "community" template object changed from ICommunity to community template model object 
• "message" template object was changed from IMessage to message template model object  
• "board" object changed from IBoard to board template model object 

If you are making any calls to these templates that reference the old template objects, you must update those calls. If you have customized these templates, you need to apply your customizations to the new templates. 

Note: If you have not customized these email templates (most customers) and are still using the out-of-the-box versions, you don’t need to do anything. 

To apply your customizations to the updated email templates: 

1. Go to Studio > Text Editor > Email Text. 
2. Open the Select Email Template menu and choose the Subscription Search or Subscription Search Blogs email template, as needed. 
3. Click View. 
4. In the Editable Email Text pane, make changes to the template as needed. 
5. Click Save. 

Learn more about editing email templates. 

GA release of Salesforce Lightning connector 

We are happy to announce the GA release of the Salesforce Lightning connector.  

You can check out the Salesforce Connector integration documentation and how to migrate knowledge articles to support the Lightning connector. 

Set the maximum number of results for the Salesforce federated search component  

Previously, the Salesforce federated search component could not be configured to set the number of search results returned. The component was hard-coded to return up to 100 results, which proved difficult to use.  

To fix this display issue, we have added a setting so you can configure the number of search results to display. 

To set the maximum number of search results to display in the Salesforce federated search component: 

1. Sign in to Salesforce as a Admin. 
2. Go to Custom Settings > Feature Settings. 
3. Click Edit. 
4. In the No of Federated Search field, set the maximum number of results to return. 
   
   
5. Click Save. 

You Found It. We Fixed It. 

• Handling post-back messages from Salesforce for Private Support non-community cases is not supported. Previously, our component allowed agents to send messages to these types of cases, but the messages were never delivered, confusing agents. We have fixed this issue and now agents can post back only to Community Cases. Additionally, the agent is notified that they cannot post back to these types of cases. 
• Previously, when a Salesforce agent published a new version of an existing article, the Community user could still view the older version, since Salesforce maintains both versions. We have fixed this behavior and now the community user is redirected to the most current version of the article. 
• We have fixed the issue where attempting to navigate a community using keyboard controls (for example, Tab, Enter) via the mobile menu resulted in losing focus and subsequent navigation attempts failed.  
• We have fixed the issue where some community skins disappeared from time to time. Previously, you needed to restart the community to restore the skins; this workaround is no longer needed. 
• Previously, when using Studio self-publish, not all nodes were getting updated with the changes. This issue has been fixed. 
• We have fixed the issue where TKB article content created before TKB version 2.4 was being displayed as raw HTML in the Rich Text tab view. The previous workaround was to copy the HTML and paste it into the HTML tab; then the Rich Text view displayed probably. This display issue has been fixed, and the workaround is no longer needed. 
• We have fixed the issue where querying for the number of users who have been deleted from the community returned inaccurate (usually zero) results. 
• Previously, if a member was removed from a group, the member group count was not getting decremented to reflect the new value. This issue has been fixed. 
• We have fixed the issue where moving large threads was not honoring the "Do not notify Subscribers" option, resulting in email notifications to be sent out to these members. Now, this option is adhered to and notification emails are not sent out. 
• We have fixed the issue where scheduled LSI reports were being delayed for up to 12 hours.