Community release 17.8 provides:

• New Features
• API Changes
• Bug Fixes

New Features

Updates to Lithium Case Portal

We have made several updates to Lithium Case Portal:

• Users who have permission to View or Create a case can now edit cases in the community, as well as edit custom and non-custom case fields. Previously, cases were read-only and could not be edited. Contact Lithium Services to perform this kind of customization.
• We have expanded the column-wise sorting functionality of results in the Case Portal. Previously, you could only sort results according to options configured for static columns such as “Created Date” and “Last Modified Date”. You can now configure sorting for all columns. In other words, you can now sort or list the results in the Case Portal based on options that you configure for any column. Contact Lithium Services to perform this kind of customization.
• You can now apply additional filters to Case Portal results. Previously, the Case Portal could filter results only based on their origin. You now have more control over filter configuration so that you can customize the results displayed in the Case Portal to your needs.

API Changes

Community V2 - Additional reason codes added to /allowed endpoint responses

The /allowed endpoint is used to verify whether the current user has the correct permissions to make a Community API v2 call. The response includes a reason_code field, as described in Verifying permissions. We have added the following reason codes:

• 100 – Ok or Unknown
• 106 – Entity not found
• 107 – Entity does not support action
• 108 – Constraint check failed

You Found It. We Fixed It.

• Using the id field as a constraint on the outbox_notes resource (SELECT subject FROM outbox_notes WHERE id = '35') now works correctly in a LiQL query in order to filter private messages in a user's outbox by user ID.
• Queries to the messages collection filtered by conversation.last_post_time (SELECT id, board, conversation.last_post_time, post_time FROM messages WHERE conversation.last_post_time < 2015-07-01T22:29:11-07:00 AND depth = 0 ORDER BY conversation.last_post_time DESC limit 10) now correctly returns topic messages where the last post in the topic thread is within the range specified in the WHERE clause.
• We fixed an issue where community users were receiving duplicate notification emails.
• Links in Groups components that take the user to the Pending Requests tab in the Group Members Page now take you to the correct location.
• The Pending Requests tab in the Group Members Page now shows the invite date/time.
• Sitemaps for nested TKBs now display properly.
• CSS formatting  of <p> tags in private messages has been fixed to remove the unnecessary whitespace.
• We fixed an issue seen in 17.6 where images uploaded with a message post and resized using the rich text editor caused an error if the images did not have HTML width and height attributes set. No action is required by customers. Existing images will render even if the height or width have incorrect values. If there is incorrect height or width specified for an image when posting new messages or editing existing messages, the message will not be posted and an error message will be displayed in the form.
• The query returned for the messages.query field in LiQL queries like SELECT * FROM tags WHERE messages.id = '233' now returns the correct LiQL statement. Previously the query would return a value like SELECT * FROM messages WHERE tag.id = '57', which is not valid because we do no support tag.id in the WHERE clause. Now the value returns a statement with a valid query syntax using tags.text. For example: SELECT * FROM messages WHERE tags.text = 'test'