DeenaP
Lithium Alumni (Retired)
Joined 9 years ago
User Profile
User Widgets
Contributions
GDPR Enhancements for Online Communities
On the 25th of May 2018, the General Data Protection Regulation (GDPR) will go into effect. This is a regulation by which the European Parliament, the Council of the European Union, and the European Commission intends to strengthen data protection for all individuals in the European Union. Lithium has been receiving questions about the plans that Online Communities has for GDPR support, and in this regard, the following is a quick update: A few weeks ago, we began working on the different aspects of our product portfolio that relate to the handling of personal data (Personally Identifiable Information (PII)). We have also had the opportunity to have discussions with some of our customers to understand the expectations and requirements around GDPR and to validate our plans. Based on these discussions, we are now working on three areas for GDPR support: PII retrieval PII deletion Demonstrating Compliance These enhancements are currently in development. Our first release for GDPR support is planned in March (previously January) 2018, and we target completion before the May 2018 GDPR deadline. We will also have a limited beta-program in December 2017 that we will invite you to be a part of. To help with some of the most common questions we have heard in the discussions so far, we now have a GDPR FAQ for your reference. Hope you find this useful. Write to us if there are any questions or if any additional information is needed about our plans for GDPR support.16KViewsSign in to react to this post10Comments17.9 Release Notes
Community release 17.9 provides: Updates to Lithium Case Portal Improvements to community private message flood controls API Changes You Found It. We Fixed It. New Features Updates to Lithium Case Portal This release includes the following updates to the Lithium Case Portal: Support for attachments when creating or commenting on cases Support for the rich text format during case creation Support for customization of knowledge articles Support for attachments when creating or commenting on cases You can now attach one or more files to a new case via the Case Portal or adding comments to an existing case. Simply click the Choose Files button located at the bottom of the New Case page and select the file you want to attach. Note: The allowed file types are dictated by the settings in Admin > System > File Attachments and should correspond with the file types allowed by your Salesforce org. At this time, you cannot attach video files. Support for the rich text format during case creation Previously, the text editor on the New Case page in the Case Portal supported rich text format during case creation, but the formatting was removed and replaced with plain text while the case was being viewed on the Case Details page in Salesforce and in your community. Now, the rich text format is retained and is displayed in the Description RTE field in the Salesforce Case page and the Case Details page in the community. Support for customization of knowledge articles You can now choose which Salesforce knowledge article fields are displayed when viewing the knowledge article in your community. Knowledge articles can now be customized to include any fields from the corresponding article type in Salesforce. To customize knowledge article pages in the community to include your custom fields, contact Lithium Services. Improvements to community private message flood controls With Lithium, you can control how often people are allowed to send private messages before triggering flood controls. Flood controls are in place to help combat potential spam. To modify the flood control settings for your community, open a Support ticket and provide the following information: A user can't make more than 1 post in X seconds. A user can't make more than 5 posts in X seconds A user can't make more than 20 posts in X seconds The default flood rate settings are: A user can't make more than 1 post in 30 seconds. A user can't make more than 5 posts in 600 seconds (10 minutes) A user can't make more than 20 posts in 3600 seconds (1 hour) Note: Admin and Moderators are exempt from flood controls; these thresholds only affect regular users. Learn more about combating spam. API Changes This release includes several updates to the Community API v2: Return Featured Threads in the order defined in Community Admin Community Plugin SDK node.js support Access recipient data from the outbox_notes collection LiQL pagination OFFSET no longer needs to be a multiple of LIMIT Maximum value for LIMIT in LiQL queries Return Featured Threads in the order defined in Community Admin In 16.2 we added the ability to set a display order for Featured Threads in Community Admin (by kudo count, date, or a manually configured order). You can now order LiQL queries to the messages collection by the order set in Community Admin > Content > Featured Threads > Ordering. Here is an example query that orders the results based on the Community Admin configuration: SELECT topic.subject, kudos FROM messages WHERE conversation.featured = true AND depth=0 Order By conversation.featured ASC Community Plugin SDK node.js support The latest version of the Community Plugin SDK now supports node.js versions 4, 6, and 8 on Mac OSX and versions 4 and 6 on CentOS. See the Community Plugin SDK documentation for instructions for updating the SDK. Access recipient data from the outbox_notes collection In previous versions, LiQL queries like the following would return a recipients collection: SELECT * FROM outbox_notes WHERE user.id = '186' LIMIT 1 However, trying to access 'recipients' data in a query (for example, SELECT recipients.user.avatar.message FROM outbox_notes) would return an error. You can now access recipient data from the outbox_notes collection. LiQL queries like the following are now supported: SELECT recipients FROM outbox_notes SELECT recipients.user.avatar.message FROM outbox_notes SELECT recipients FROM outbox_notes WHERE user.id = '3' limit 10 LiQL pagination OFFSET no longer needs to be a multiple of LIMIT Previously the OFFSET in a LiQL query had to be a multiple of the LIMIT. For example, LIMIT 5 OFFSET 15 was allowed, but LIMIT 5 OFFSET 13 was not. With 17.9, LIMIT and OFFSET can be any combination. For example, SELECT * FROM users LIMIT 3 OFFSET 2 returns the 3rd, 4th, and 5th result returned by the query SELECT * FROM users. Maximum value for LIMIT in LiQL queries We have added a configuration which sets the maximum value allowed for LIMIT in LiQL queries to 1000. This is to help performance and protect against malicious attacks. If you need to raise this limit, contact Lithium Support. You Found It. We Fixed It. We have fixed the issue where the component messages.form.replyinline was causing a JS error when included on the ForumTopicPage quilt, which had the additional effect of breaking some other page components, such as Quick Reply and Add Tags. We have fixed the issue where label subscriptions were not triggering an email notification to members who were subscribed to those labels. Previously, tapping the Kudos button on a Mobile V1 community page did not increment the kudos counter until you refreshed the page. This issue has been fixed. We have fixed the issue where draft blog articles were being returned in the list of published articles for the specified tag. Now, articles in a draft state do not appear in the article list. We have fixed the issue where adding the Tabs component to the ContestEntriesTab or ContestHomeTab quilts causes the page to reload repeatedly, which in rare cases, could have caused the community to run out of memory. We have fixed the issue where videos could not be uploaded or deleted from a user's profile. Previously, if you tried to add additional spacing or line breaks in the HTML tab of the message editor when using the IE11 or Firefox browser, the extra spaces/line breaks were not being added. This issue has been fixed. We have fixed the issue the "Answered" and "Unanswered" filters were not filtering topics in forum boards properly. Now, these filters are processed properly. We have fixed the issue where sending a test email to yourself in Studio (under Text Editor > Email Text), did not work for some email templates. Now, sending test emails to yourself works for all email templates. Previously, robot.txt changes were not getting pushed when publishing via Studio Publish. This issue has been resolved. We have fixed the display issue where sending a group private message on a responsive community to enough users to make the username list flow to a second line in the Send To field resulted in the user name bleeding outside the boundaries of the send to margins. Previously, inserting a long image caused the message editor view to always force the scroll bar down, making it impossible to get to the top of the post without using keyboard shortcuts (up and down arrow keys) or by expanding the editor size by dragging the edge. This issue has been fixed, and you can now scroll down within the message editor.ViewsSign in to react to this postCommentsLithium Community 18.2 Release Notes
Community release 18.2 brings the limited release of GDPR features, migration to full HTTPS encryption for all communities, and bug fixes. New Features API Changes You Found It. We Fixed It. New Features Limited Release: GDPR for Community Migration to full HTTPs Encryption for all Customers Search Filter in the Product Editor tab Limited Release: GDPR for Community GDPR (General Data Protection Regulation) is a privacy-related regulation standard introduced by the European Parliament, the Council of the European Union, and the European Commission. This regulation is intended to strengthen data protection for all individuals in the European Union. GDPR enables individual users (data subjects) to view, edit, export, and delete the Personally Identifiable Information (PII), that they may have provided to data controllers (brands) and data processors (online communities). This regulation will come into effect from the 25th of May 2018. GDPR-related capabilities from Lithium will be available in phases. For those customers interested in using some of the initial features, please contact Lithium Support to discuss your needs. In the 18.2 release, Lithium supports a few features such as PII retrieval and PII deletion. Additional GDPR-related features will be available as part of upcoming releases and are planned to be delivered by early May 2018. Enabling GDPR Please contact Lithium Support to discuss your needs. The Support team will enable the limited features as needed. For more information see: GDPR for Online Communities FAQs GDPR Enhancements for Online Communities Migration to full HTTPs Encryption for all Customers Lithium is moving all customer communities to full HTTPS encryption. This change protects your organization and your end-users, while paving the way for performance improvements and great, new features. With the 18.2 Release, Lithium is deprecating support for the following community configurations: HTTP-only community mode "Mixed mode" HTTPS support These configurations will remain available through Community release 18.7 (August 2018). After 18.7, support for these configurations will be removed. For details about the migration path, see Full HTTPS Encryption for all Communities. Search Filter in the Product Editor Tab We added a search field to the Community Admin > Features > Products > Product Editor tab. API Changes FreeMarker: Clear the top-level category with FreeMarker Community API v2: Pass the API Session Key in the Header FreeMarker: Clear the top-level category with FreeMarker We've added the top.clear() method to the FreeMarker nodes context object to clear the top-level category set for a community. Use this method if you need to reset the top-level category. After you have cleared the top-level category, you can set a new top-level category using nodes.top.setCategoryDisplayId. Community API v2: Pass the API Session Key in the Header As of Community 18.2, you can pass the API session key as the value of the Li-Api-Session-Key header when using the Community API instead of passing the session key in the URL. Passing the session key in the header is now the recommended way of passing the session key. See API session key authentication for details. The Li-Api-Session-Key header is supported by both Community API v1 and v2. You Found It. We Fixed It. We have fixed an issue where Admin Metrics were not visible to Admins or other users with the similar permissions while using the 18.1 version of Community. We have fixed an issue where a question could not be posted for a product if the product category did not have a board attached to it. We have fixed an issue where the Forgot Password link would redirect to the wrong page. We have fixed an issue where skins created in SDK were not marked as created in SDK and could not be edited in Studio. This issue occurred only when using Community release version 17.12 and later. Previously, when the Use Search Before Post "similar articles" workflow feature was enabled, clicking the View More Results link after search would display an error. This error would occur only for the TKB discussion style. This issue has now been fixed, and the View More Results workflow now works as expected. We have fixed an issue where the Insert Video button remained enabled even after the video had been uploaded. Clicking this button again would upload the same video a second time. This issue has now been fixed. We have fixed an issue where the Sync History tab under Community Admin > Features > Products would fail to work as expected and display an exception. We have fixed an issue where CSV files of badges could not be downloaded if the badge name contained commas. This issue occurred only while using the Chrome browser.ViewsSign in to react to this postComments
16KViews
10Comments
You’ve seen all recent content