In the 16.1 Release, we’ve continued to make incremental improvements to some key feature areas, including LSI advanced filters, SEO, Studio components and messaging, APIv1, and the SDK.
New features
- Filter by Category and Board name in LSI
- SEO improvement: Solved indicator in search results
- Studio updates
- API changes
- SDK updates
Filter by Category and Board name in LSI
To make it easier to create LSI filters for specific categories or boards, we have added the ability to create category and board filters based on name instead of just ID.
To create an LSI filter based on a category or board name:
- Sign in to LSI.
- Go to the page where you want to view data and build your filter.
- (Optional)Set the date range for your report.
- Click Add a Filter.
- Select the type of filter you want (Category Name or Board Name), choose the equals or not equals operator, and select/enter the values.
Category Name filter:
Note: Category and board names are listed in alphabetical order. If your categories and/or boards use non-Romantic languages (Russian, Japanese, Arabic, Chinese, etc.), they are grouped by language and then alphabetized within those groups.
Board Name filter: - Click Apply when done.
Learn more about applying filters to LSI reports.
SEO improvement: Solved indicator in search results
Currently, when a post is marked as solved, the word "Solved" appears in the description in Google search results. However, sometimes Google creates its own description instead of defaulting to the SEO Description, depending on the terms the user typed into the search. When this happens, it’s not clear to the user if this post has been solved or not. With this release, search results for posts marked as solved now include “Solved:” in the returned SEO Title. For example:
Studio Updates
Error Messaging for Unknown components
Previously, if a community user opened a page that contained an unknown component (for example, a component that had been added to a quilt but no longer exists in Studio > Components or in the /res/components directory in the SDK plugin) the page would not render, and the user would be redirected to an error page with the message: “unknown component id: <component_id>”.
This error is usually caused by deleting a component from Studio or the SDK plugin without also removing the component from all quilts in which it was placed.
As of 16.1, a community page with an unknown component now renders as expected without the unknown component, and an error appears in the log file.
My Accepted Solutions Component
We’ve added a new My Accepted Solutions component that displays a user’s most recent accepted solutions. Use this component in the View Profile page. You’ll find this component in the User Profile section of the Components list in Studio > Page.
There are no configuration options for this component. Here’s an example of how it looks:
API Changes
We’ve added two new API v1 calls:
- User/notification/read – marks that a user has read their notification feed
- User/notification/unread/count – returns the count of unread notifications for a user
New field on the Community APIv2 Messages collection
Community API v2 LiQL queries on the Messages collection that filter on subject or body keywords, such as SELECT * FROM messages WHERE subject MATCHES ‘test’ OR body MATCHES ‘wireless’ now include the search_snippet field in the response.
The field includes an HTML snippet of text from message subject or body of the message with the matching text highlighted.
For example:
“search_snippet” : "This is the TKB article I wrote in order to <SPAN class=\”lai-search-match-lithium \”>test</SPAN> what is returned as a search snippet from a keyword filter",
SDK Updates
You can now contribute email template using the Lithium-Klout SDK.
Add email templates to your SDK plugin /res/lang/<language folder> and submit your plugin using the li submit-plugin command.
Example
For the American English version of the email_content.template.accept_as_solution_reminder.text email template, put the template in: res/lang/text.en
For the French version, put the template in: res/lang/text.fr.(UTF-8)
You Found It. We Fixed It.
- We have fixed the display issue where the word count was misaligned in the message editor.
- Previously, if you typed in double curly brackets (for example, “”) in the body of a message, the text was interpreted as angular code, resulted in an error, and blocked the user from editing the message. This issue is now resolved.
- We have fixed the issue where users could not upload .pbix files in Internet Explorer 11 or Microsoft Edge.
- Previously, if a user subscribed to a topic and another user replied to that topic and then closed their community account, the user who was subscribed to the topic would receive a notification in their feed that said “The person you requested has been deleted or does not exist.” We have fixed this error and now the notification feed shows the proper data and lists the reply as coming from an anonymous user.
- Previously, when you entered a search term and then clicked another tab (for example, going from the Posts tab to the Users tab), the term you entered in the search field would clear and you’d need to type it in again. Now, your search term persists as you navigate between tabs and is automatically submitted to the new search domain.
