Blog Post

Release Notes
6 MIN READ

Lithium Community 17.12 Release Notes

SuzieH's avatar
SuzieH
Khoros Alumni (Retired)
7 years ago

Happy New Year! We hope that 2018 brings all kinds of good your way.

Community release 17.12 includes all features and bug fixes since release 17.10 in order to accommodate our Holiday Production Freeze

New Features

Case Portal Search

We have expanded the functionality of the Case Portal search feature. You can now filter case portal search results based on text strings that you enter in the column-wise search fields. The columns in the Case Portal Search Results page now support search. You can configure the following columns as searchable:

  • Id
  • Title
  • Status
  • Author
  • Origin
  • createdDate
  • Priority
  • lastModifiedDate
  • closedDate

To configure column-wise search for your case portal columns, contact Lithium Services.

Updates to Product Questions events

As described in Register Product Questions event listeners, the Product Questions ActiveCast component generates events in JavaScript that correspond to the state of the component and actions made on messages within it. We have added message depth and message details to the action context for the LITHIUM:messages.post event.

Note: The Product Questions component is currently in open beta.

The action context will now look something like this for the LITHIUM:messages.post event:

{
message: {
author: // author ID and login
body: string // body of the message
depth: inst // position of the message in the thread. 0 = topic, 1 = first-level reply
subject: string // subject of the message
uid: int
}
}

Add Previous and Next links in the TKB Article Page

We have enabled the article-navigator page-level component, which adds Previous and Next links, to work on the TKB Article Page. The links enable a user to move through articles in a knowledge base by post date (most recently posted articles displayed first). This component does not respect ordering defined in Community Admin.

Note: The article-navigator component can be used only on the Blog Article Page and the TKB Article Page. 

The article-navigator component adds the Back To Knowledge Base, Previous, and Next links shown in the screenshot below.

 


You must add this component in XML view in Studio or by editing the TkbArticlePage.quilt.xml in the Community Plugin SDK.

 

This example XML includes the article-navigator component. If you are using the latest version of the TKB feature, your quilt XML should look something like this:

<?xml version="1.0" encoding="UTF-8"?>
<quilt extends="Common" layout="one-column">
<add to="common-header">
<component id="helpfulness-display" wrapper="lia-page-header"/>
</add>
<add to="main-content">
<component id="article-navigator" />
<component id="article" />
<component id="rating-feedback-list" />
<component id="comments" />
</add>
</quilt>

Coming Soon! Lithium Community iOS SDK

In May of 2017, we announced GA of our Community Android SDK. That made a lot of folks happy and also made a lot of folks say, "That's great! What about iOS?" Our team has been working hard on a Community iOS SDK since the release of the Android SDK. Watch our Online Communities blog for the announcement of our Lithium Community iOS SDK beta program toward the end of January.

API Changes

We have added new methods to the utils, coreNode, and message context objects.

New utils methods for sequences

You can now remove items from a sequence and remove duplicate items from a sequence.

  • utils.sequence.remove(sequence,itemToRemove) removes all occurrences of the given item.
<#assign input = ["a", "a a a", "aa a", "A", "a"] />
<#assign res = utils.sequence.remove(input, "a") />
<#-- resulting sequence is ["a a a", "aa a", "A"] -->
  • utils.sequence.unique(sequence) removes duplicate items from a given sequence
<#assign input = ["131", "135", "251", "131", "135"] />
<#assign uniqueInput = utils.sequence.unique(input) />
<#-- resulting sequence is ["131", "135", "251"] -->

Get the description from coreNode

We added the coreNode.description method to the coreNode context object. To display the description of the node in context as defined in Community Admin, for example, you would use an interpolation like this:

${coreNode.description}

Retrieve views metrics from the message context object

We added the metrics.views method to the message context object. To retrieve and display the number of views for the message in context, for example, you would use an interpolation like this: ${env.context.message.metrics.views}

You Found It. We Fixed It.

  • We have improved the error validation workflow of the New Case Page in the Case Portal. If validation fails, the page now retains the entered data and indicates the fields in which the error occurred.
  • We have improved the notifications workflow for Case Portal users. You can add contacts to the “Additional CC” field in the Email Notification region to copy these contacts on case-related notifications. To enable this feature, contact Lithium account team or Services.
  • We have fixed an issue that displayed an Invalid Authorization Response error message while publishing video files with Knowledge Base articles. Videos uploaded to Knowledge Base articles now play after the articles are published. 
  • We fixed an issue that logged a user out of their session while trying to post a product question using the Product Questions ActiveCast component.
  • We have improved the workflow of the Password Reset token to increase security while using the password reset option.
  • We fixed a migration issue that moved message replies to the wrong message thread on the destination board. We also improved our migration workflow to detect and repair database inconsistencies more efficiently.
  • Answers posted to a Q&A Board now appear without requiring a page refresh.
  • We have fixed a URL-related error where the “jump-to/first-unread-message" string was being displayed in the URL for Knowledge Base articles when the Jump to first unread post in a topic option was selected in My Settings > Preferences > Linear Layout.
  • Matching search terms in search results are now highlighted in both the title and body text in the Community search results for Responsive sites.
  • We have improved the download management workflow for private attachments when the Make all attachments public option is not selected in Community Admin > System > File attachments. Previously, if the user who uploaded the private attachment logged out and then tried to access the file, Community displayed an error message. With this fix, the attachment is either downloaded if the user has the necessary permissions or an “Access Denied” error message is displayed.
  • You can now disable the Accepted Solutions feature for group posts on Responsive communities.
  • In Forum and Group boards,  the UI no longer incorrectly navigates to the first unread post in the thread when a user clicks or taps the Reply button. This issue occurred only when the Jump to first unread post in a topic option was selected in My Settings > Preferences > Linear Layout
  • The Jump to first unread post in a topic option in My Settings > Preferences > Linear Layout no longer affects what happens when a user clicks or taps the New column in the Community UI. Now when a user clicks or taps the New column, the user is always taken to the first unread post in a topic  (as expected) regardless of the how Jump to first unread post in a topic is configured.
  • The “Powered by Lithium” logo now redirects to the correct URL.
  • We have improved how Lithium Social Intelligence (LSI) reports information for the Minutes to First Solution column in the Forums category. Previously, if the timestamp of an accepted solution preceded the timestamp of the forum or thread itself, LSI recorded a negative integer value in the Minutes to First Solution column. (This event occurred only when an older thread with an accepted solution was merged with a newer thread.) For these types of events, LSI now records a value of "0" instead of recording a negative value.
  • Quotes used in message replies now display @mentions correctly. Note that there is still an outstanding issue where an @mention in quoted text triggers a duplicate notification email.
Updated 5 months ago
Version 11.0