Khoros Communities 21.10 Release
Content New Features Bulk content archive (Early Access) Enhancements Granular permissions to edit published blog articles Allow Co-Authors to edit published Blogs and TKB articles Userid field added to Bulk Download Member Data report Security Announcement API Updates Bulk Data API v2.0 Bulk content archive (EA) Allow co-authors to edit published articles Contributor types accessible through LiQL Attachments in Private Message You Found It. We Fixed It. New Features Bulk content archive (Early Access) We are happy to announce that we’ve extended the Content Archive feature to include support for archiving content in bulk. With the initial Content Archive release, you could archive only one article at a time. With bulk archive, you can archive multiple articles at once, making it easier to keep your content organized and up-to-date. With bulk archive, you can: Specify criteria to search for specific community content. Review the matching content and select all matching results or select one or more specific articles from the list. Archive the selected posts in bulk. Enablement To be considered for the Early Access (EA) program, contact your CSM. If selected, your CSM will work with the Support team to enable the feature. Once enabled, you can turn on/off the feature from the Admin panel. Go to ADMIN > Mod Tools > Content Archive > Turn on content archive. Note: If the Bulk Content Archive has not been enabled for your instance and the admin setting Mod Tools > Content Archive> Turn on content archive is turned on, you can archive only one content at a time. You can only restore or unarchive posts one at a time from the Archives page. There is no option to unarchive posts in bulk. All bulk archived content is moved to your community’s Archive Page. Check out this video to get an overview of the Bulk Archive feature. The video shows how you can bulk archive content from a TKB board with articles created at least one month ago, with no more than two views and no replies in the past one month. Bulk content archive 1. Click the Archives link under the Community dashboard on your community home page 2. Hover the Options menu 3. Click Bulk Archive 4. You will land on the Bulk Archive tool page. Choose from where you want to archive content. 5. In this example we choose Hi-Fi Products 6. Select the type of posts you want to archive. 7. In this example we choose TKB 8. Select how old the posts that you want to archive are. 9. In our example, we select posts that were created at least 1 month ago. 10. Enter a valid number for Maximum Views for the posts that you want to archive. This will enable the In the Past dropdown. 11. In this example, we enter 2 12. Select a timeframe for the views. 13. In this example, we select 1 month, which means that the posts must have had a maximum of only two views in the past one month. 14. Select a timeframe for which the posts have not had any replies within the time frame selected in the Created At Least and In the Past dropdowns. 15. in this example, we select 1 month, which means that the posts have had no replies in the past 1 month. 16. In our example we leave the Author filter empty Click Search. 17. A row is added to the Job table as shown. The STATUS column shows that the job is currently searching the community for the filters submitted. 18. You must refresh the Bulk Archive page to check the STATUS change of the job. The STATUS changes to Ready to archive when the search completes and has fetched results. Click Ready to archive. 19. You will land on the Search Results page, which displays the posts retrieved for the job submitted. From here, you can either archive a few or all posts retrieved. 20. If you want to archive only a few posts, select only those posts. The number of posts you select are displayed. 21. Click Archive Selected. 22. Click Next. 23. Click Archive. 24. The selected post is queued for archival. 25. If you want to archive all posts in one go, click Archive All. 26. Click Next. 27. Click Archive. 28. All posts are queued for archival. 29. Scroll up and click Bulk Archive. 30. The STATUS column for this job now shows that all posts are archived to the community's Archive page. Here's an interactive tutorial Click the icon in the top right corner before you begin, for best experienced in Full Screen. Bulk Content Archive 1. On your community page, select the discussion board from where you want to bulk archive. In our example we select a TKB board. 2. You will land on the selected board page. 3. Hover over the Options menu. 4. Click Bulk Archive 5. Since you landed on this page from the TKB board, the values for Location and the Type of Post are pre-selected. However, you can always choose a different Location and Type of Post from here. 6. Select how old the posts that you want to archive are. 7. In our example, we select posts that were created at least 1 month ago. 8. Enter a valid number for Maximum Views for the posts that you want to archive. This will enable the In the Past dropdown. In this example, we enter 2 9. Select a timeframe for the views. 10. In this example, we select 1 month, which means that the posts must have had a maximum of only two views in the past one month. 11. Select a timeframe for which the posts have not had any replies for. 12. In this example, we select 1 month, which means that the posts have had no replies in the past 1 month. 13. In our example we leave the Author filter empty 14. Click Search 15. A row is added to the Job table as shown. The STATUS column shows that the job is currently searching the community for the filters submitted. 16. You must refresh the Bulk Archive page to check the STATUS change of the job. The STATUS changes to Ready to archive when the search completes and has fetched results. Click Ready to archive. 17. You will land on the Search Results page, which displays the posts retrieved for the job submitted. From here, you can either archive a few or all posts retrieved. 18. If you want to archive only a few posts, select only those posts. The number of posts you select are displayed. 19. Click Archive Selected 20. Optionally, enter the URL of the related content. When you attempt to view archived content (via a permalink or bookmark) you will be directed to this content. In our example, we will leave this field empty. Click Next 21. Click Archive 22. The selected post is queued for archival. 23. If you want to archive all posts in one go, click Archive All. 24. Click Next 25. Click Archive 26. All posts are queued for archival. 27. Scroll up and click Bulk Archive. 28. The STATUS column for this job now shows that all posts are archived to the community's Archive page. Here's an interactive tutorial https://www.iorad.com/player/1877100/Bulk-content-archive https://www.iorad.com/player/1868612/Bulk-content-archive Related articles: Learn more about the Bulk Content Archive feature Here’s an example of how the feature works Learn more about enabling the feature. Enhancements Granular permissions to edit published blog articles Prior to this release, there was no way to restrict members to only edit published blogs. Members had to be granted the “Manage own article” or “Manage all articles” permission to edit blogs after they are published. This enabled members with these permissions to perform other content actions (delete, move and so on). With this release, we introduce two new permissions that enable members to only edit published blogs, and then take them through the publishing workflow process. Edit my published blog posts: This permission is tied to the BlogAuthor role. Members with the BlogAuthor role can edit their published blogs and send the edited version for review. Edit all published blog posts: Members with this permission and the Start new articles permission can edit their blogs and those published by other members and send the edited version for review. Note: You must be on Blogs version 3.1 to use these new permissions. Go to Studio > Features and select 3.1 for the Blog version. Once you have updated to Blogs v3.1, you must deny Manage own articles permission in the BlogAuthor role. BlogAuthors will have Edit my published blog posts permission by default. Related articles: Learn more on blog permissions Learn more on Editing published blogs in Blogs v3 and above Allow Co-Authors to edit published Blogs and TKB articles Co-Authors of Blogs and TKB articles can now edit published articles. To do this, Co-Authors of blogs must have the Edit my published blog posts permission. Co-Authors of TKBs must have the Edit my published TKB posts permission. Note: For Blogs, you must be on Blogs version 3.1 to use these new permissions. Go to Studio > Features and select 3.1 for the Blog version. For TKBs, you must be on TKB version 4.1 to use these new permissions. Go to Studio > Features and select 4.1 for the TKB version. Userid field added to Bulk Download Member Data report With this release, we are adding the "Userid" field to the "Bulk Download Member Data" report. This field retrieves members' community userid and helps community managers identify the partially registered users who registered without a username. Learn more about community member metrics Security Announcement As part of our efforts to continuously improve the security of our applications, Khoros will be upgrading our Web Application Firewalls (WAFs) for all customers over the next few months. These advanced WAFs provide enhanced capabilities that will enable us to better prevent bad requests from hitting applications earlier in the process, thereby improving the stability, reliability, and security of your communities. While the rules and filters have been vetted and tested, due to the nature and customizability of the Community platform, there is a small risk that there could be some level of unexpected impact. Issues caused by the WAF could result in end-users receiving a 403 forbidden response to an operation. Contact Support if you see this behavior and provide as much detail as possible about the action you were taking and the timing of that action (including timezone information). The change will first be rolled out to all stage instances and after a few weeks, we will roll out changes to production instances in batches. API Updates Bulk Data API v2.0 We are happy to announce the launch of Bulk Data API v2.0 with this release. The Bulk Data API v2.0 brings more user-actions and associated fields along with the existing actions and fields. Note: This new version will be available on November 8, 2021. Bulk Data API now includes this information: Subscriptions Private messaging Idea status change Event discussion style Group hub interactions 'Me too' user action Product associations Search metric enhancements TKB helpfulness rating Archival action User Rank changes The earlier version, v1.0, is still available. We will announce the deprecation of v1.0 in a future Community Release Notes. There are schema changes associated with Bulk Data API v2.0, and fields have also undergone re-ordering. We recommend updating the data store according to the schema changes before querying Bulk Data API V 2.0. The new version supports exporting data belonging to past time ranges. Note that, these newly added action keys and associated fields will be fully available for date ranges post Nov 8, 2021. Which means that, when data for a past time range is pulled using Bulk Data API v2.0, all the currently available action keys and corresponding fields will be present. However, the newly added action keys and associated fields may not be fully available for past date ranges. For detailed information on Bulk Data API v2.0 action keys and fields, refer to the Bulk Data API v2. Bulk content archive (EA) With the introduction of the Bulk Content Archive feature, we also provide Bulk Content Archive APIs to archive content in bulk. Use these APIs to: Create bulk archive processes Retrieve details on currently running archiving processes Get the number of posts retrieved for the search filters applied Retrieve all results Delete and cancel a bulk archive process To learn more, see bulk content archive and the archive bulk content use case. Allow co-authors to edit published articles As mentioned earlier, Co-Authors of Blogs and TKB articles can now edit published articles. We also introduce APIs to achieve the same. All permissions and versions changes are applicable to use APIs, as mentioned in this section. To learn more about these APIs, see Edit blog and KB articles after publication Contributor types accessible through LiQL The current API to retrieve the contributors for TKBs and blogs returns both the co-authors and contributors together. With this release, we introduce a new constraint to list the co-authors and contributors separately. This new constraint, called messages_contributed.contributor_type, is added to the user object with two acceptable values: co-author contributor Learn more about the messages_contributed.contributor_type. Attachments in Private Message We have updated the threaded private message POST/notes_threads with the attachments field. You Found it. We Fixed it! General Fixes We have fixed the issue where the RSVP links to No and Maybe were missing for languages other than English in Events version 1.2. This issue has been fixed on both the main page of the event and in private messages. Earlier, comments or replies in Blogs v3 made via Khoros Care or API v1 did not appear on the community page. We have fixed this issue. We have fixed the issue where the search page displayed a misleading message saying “No search results found” even before entering a search keyword. Earlier, the thumbnails for all videos uploaded before the migration from Ooyala to Brightcove were missing. This issue is now fixed. All videos uploaded before the migration are accessible. The issue that the comment box for comment syndication did not load on the external website is now rectified. The issue that topics from the community were not automatically escalated to salesforce is resolved. In communities where the Search Subscription and Email Metrics is enabled, the “change and discontinue your search” link in the Search Subscription emails were redirected to an error page. This issue is now fixed. The issue that, when Admins changed the "Any edits & comments on knowledge bases articles I subscribe to" settings under the Admin > Users > Notification defaults, they were not updated, is now fixed. Earlier, in an SSO-enabled community that uses dual authentication where users can register using a non-SSO method or an SSO method, non-SSO users could register using an e-mail address associated with another account. Even though the system recognized that the e-mail was already associated with another profile, it still accepted registration. This issue is now fixed. Now, when non-SSO users register, they will continue to be informed that the e-mail they selected is already in use and registration is rejected. Earlier, when users with appropriate permissions tried to fetch a post or a reply to a post marked as spam using APIs, they received a "Permission Denied" error message, which was misleading. This is fixed. Now, when they fetch such posts and replies, they will see a success message without the content. Accessibility Fixes Earlier, the community pages that used the “BoardBrowserListTaplet” and “NodeListTaplet” components had a clickable icon and an adjacent message subject link next to it which both led to the same page. Some customers didn’t want two different UI elements that served the same purpose. We have addressed this issue by introducing a Studio parameter called "disableIconLink" to enable/disable links on the icons for the "BoardBrowserListTaplet" and "NodeListTaplet" components. By default, links on icons for these components are enabled. To disable the links on icons from Studio: 1. Go to Studio. 2. Choose the community page where you want to make these changes. 3.Click Switch to XML View on the top-right section. 4.Add the parameter disableIconLink="true" to the component with id="forums.widget.board-browser-list" for BoardBrowserListTaplet and id="nodes.widget.child-node-list" for NodeListTaplet component as below: <component id="nodes.widget.child-node-list" disableIconLink="true"/> <component id="forums.widget.board-browser-list" disableIconLink="true"/> The issue where the screen reader did not read out the information about the pagination controls when users entered, left, or navigated within a pagination component is now resolved. Previously, when community breadcrumb links were too long to fit on the page and the links were truncated with an ellipsis (for example, Community Name> TKB page name >name of the TKB arti…), the screen reader read out only the visible characters. This did not provide complete information to users. We have fixed this issue, and now the entire breadcrumb link is read. A NVDA-specific screen reader issue where it announced incomplete information for the search filter buttons on the search edit field for Private Messages is now fixed. On the Private Messenger page, the screen reader used to read out the "Inbox" and “Sent” buttons as "Show option button", which was misleading. This issue is now resolved. The screen reader now announces that they are drop-down menus with proper labels. We have fixed the issue where the focus moved to multiple non-interactive elements on the page while navigating with the keyboard Tab key. We have fixed the issue where the screen reader did not read out if the Additional Options or Teaser or SEO Options in the Post form were collapsed or expanded. The issue where the screen reader read out the name of the file instead of the alternate caption provided for an image is now fixed. Now, when you upload an image with an alternate caption, the screen reader reads out the alternate caption. Earlier, screen readers were unable to identify if a table on the community page was a “data” table or a “presentation” table. This was because the roles for both table types were set to "presentation". To fix this issue, we have introduced the “isTableRolePresentation” parameter that enables you to remove the role="presentation" attribute for the table from Studio. For example, on the “Move Messages Page”, for the “move-messages-form” component, pass isTableRolePresentation="false", to remove the role="presentation" attribute. This means that the role is “table” for this component. <component id="move-messages-form" isTableRolePresentation="false"/> Note: The default value of “isTableRolePresentation” is “true”. The default role is “presentation”. This parameter is available for these components: File Name Page Name Component Name AllDrafts.tml Blog Console Page BlogConsolePage RecentBlogArticlesTaplet.tml View Profile Page blogs.widget.recent-blog-articles MoveMessagesForm.tml Move Messages Page move-messages-form ThreadList.tml forums.widget.thread-list TaggedMessagesTaplet.tml Tag View Page tags.widget.leaderboard-messages tags.widget.leaderboard-messages-title tags.widget.leaderboard-messages-community-title tags.widget.my-recent-tagged-messages tags.widget.frequent-tagged-messages tags.widget.recently-tagged-messages ForumPage.tml Forum Page message-list MessageHistoryPage.tml Message History Page content MessageTrackerPage.tml Message Tracker Page MessageTrackerPage RecentPostsPage.tml Recent Posts Page post-list TagDetailPage.tml Tag Detail Page tag-list UnansweredTopicsPage.tml Unanswered Topic Page unanswered-list UnreadPostsPage.tml Unread Posts Page unread-list ForumsFilteredByLabelPage.tml Forum Filter by Label Page post-list GroupPage.tml (common) Group Page message-list TopMessagesLeaderBoard.tml Kudos Leaderboard Page tabs KudosUserPage.tml Kudos User Page KudosUserPage ProductMessageList.tml Product Page products.widget.product-message-list RecentQuestionsPage.tml Recent Questions Page question-list TkbHistoryViewList.tml TKB Article History Page history TkbPage.tml TKB Page message-list We have fixed the issue where the color contrast between the “Close” button and the background was insufficient for low-vision users to see the icon clearly. Now, the contrast between foreground and background colors meets the WCAG 2 AA contrast ratio thresholds.2.9KViewsSign in to react to this post30CommentsKhoros Communities 20.8 Release Notes
Community 20.8 delivers self-service for many Community page URL redirects, a sneak peek at improvements to Community in-app user guidance and help, as well as enhancements to several existing features and APIs. New Features API Updates Bug Fixes New Features and enhancement Coming Soon: Improved User Guidance and Help in Community URL redirect rules for Community pages Addition of new columns to Bulk Download of member data in Community Analytics Cookie Banner enhancements Coming Soon: Improved User Guidance and Help for Community In the coming months, we will be rolling out a new User Guidance/Help solution for Community and Community Analytics. First up will be in-app guides. These guides will provide you with a helpful information, including: New feature announcements Product alerts and notifications Tips to help you get the most out of community features Don’t be surprised if you start seeing guides like this in the coming weeks: And don’t worry, we won’t be spamming you with lots of pop-ups. These guides are intended to help you get the most out of the product and get out of your way fast. Next, we’ll be rolling out our new Resource Center, which you can open by clicking the question mark icon at the top-right corner of the application window. Use the Resource Center to get product help, access Release Notes, and learn about available Product Coaching sessions and community best practices. Note: Later this year, we plan to remove the existing Help drawer that appears at the bottom of the Admin and Studio apps. This feature-level help content will all be available within the Help section of the new Resource Center. Guides and Resource Center will be available in: Community Admin Studio App Creator Toolbox Moderation Community Analytics URL redirect rules for Community pages Over time, content on your community changes, moves, is deleted/archived, or replaced. When this happens, you want to make sure that Internet searches don’t show results that go to obsolete/missing pages. Or, sometimes, you might want to point people to newer or more relevant content. To help optimize these search results and make sure that people get to the right content, you can create redirects rules. Redirects enable you to keep page and link authority of your website when a website’s URL is redirected to another URL (for any reason). Basically, redirects help you keep the SEO of your website healthy and keep visitors engaged on your site. Properly defined redirects help keep your search rankings. The most common types of redirects are 301 (permanent) redirect and 302 (temporary) redirect. Previously, you needed to open a Support ticket to get these search redirect rules created. As of the 20.8 Release, you can create these search redirect rules yourself from Community Admin. Note: To create redirect rules other than 301 or 302 redirects, you must still open a Support ticket. The ability to create, edit, or delete redirect rules is granted through the Manager redirects permission, located under Admin > Users > Defaults > SEO Redirects. This permission is denied by default. We recommend enabling this permission for Admins or other trusted community members. Members with this permission have access to the Redirect Rules tab under Admin > System > SEO. Learn more about setting up members to create redirect rules and how to manage these rules from Community Admin . Addition of new columns to Bulk Download of member data in Community Analytics Bulk Download Members Data provides a snapshot of member activity and community influence. With the 20.8 release, this report will include Registration Start Date, Registration Completion Date, and Registration Status columns. Registration Start Date is the timestamp (UTC) when the member initiates the registration process. The Registration Completion Date is the timestamp (UTC) when the Registration Status changes from “Partially Registered” to “Registered". If the registration was completed more than two years ago, the Registration Date will be empty in the Bulk Download Members Data report. With the addition of these columns, you can now filter the list of members who completed their registration within the time frame selected for the report. Learn more on download community member metrics. Cookie Banner enhancements Currently, when users visit the community the cookie banner appears and prompts them for consent to use site cookies. The Click Here link opens the webpage that describes your cookie policy, but it does not dismiss the banner. As of today, clicking OK or continuing to use the site is considered as user consent to add or set all community cookies. With the 20.8 release, we have changed this behavior. Users must now click OK in the cookie banner and explicitly confirm their consent to activate the community cookies. Continuing to use the site will not be considered as a user consent anymore. If users do not provide their explicit consent, only the Type 1 cookies(“Strictly Necessary”) are set, and all other cookies are held back. With this release, we also re-classified the LithiumVisitor and VISITOR_BEACON cookies into Type 1. Learn more about cookies found in Khoros communities. API Updates api.mark_read view count update The Community API v2 api.mark_read query parameter now increments the view count for messages for anonymous as well as signed-in users. See Mark a message as 'read' for more information about the api.mark_read query parameter. Constrain message queries by messages posted or edited in the past n days We have added new fields, constraints, and sorts to enable you to constrain queries to the messages, reviews, and review_comments collections by posts that have been posted or edited in the past n days. In this context, the term posts refers to topics, replies, and comments for all conversation styles (forum, idea, TKB, QandA, group, blog, contest) including reviews and review comments. See Get messages posted or edited in a specified range of time for more information and examples. Developer Documentation improvements We've given our Community API v2 endpoint and LiQL documentation a refresh in order to improve usability and the search experience. See our announcement in the Community Blog. Here's a quick look. You'll now find the endpoint documentation in the API Reference section, organized by HTTP method type. You'll find LiQL reference information in the Guides section with our LiQL guides and examples. API v2 and LiQL reference now appear in Search results. Our legacy API v2 experience will remain in place for two weeks to ease the transition. We hope that you find these changes helpful. You Found It. We Fixed it We have fixed the issue where images that were uploaded when sending a private message from a mobile device were placed in the sender’s public image album instead of their hidden album. We have fixed the issue where users were not appearing in the @mentions pop-up menu, despite typing in their entire user name. Previously, when you sorted the list of Group Hubs by different criteria, the number of group hubs was returned each time. This display issue has been fixed. Previously, the Net Accepted Solutions metric key worked only in Studio and not the SDK. This issue has been fixed, and the key is now available via the SDK. We have fixed the issue where the Real-time Virus Scanner took a very long time to complete attachment scans or in some cases, never completed the scan.ViewsSign in to react to this postCommentsKhoros Communities 21.5 Release Notes
21.5 Release delivers self-serve SAML SSO as an out of the box core product feature, instead of a plugin-based approach. This release also includes enhancements around Events, Group Hubs and Community Analytics, and API updates. Content Features Self-serve SAML SSO Enhancements Remove the restriction on the number of Events node within a category Increase in the date range limit in Community Analytics reports Specify the default sort order for Group Hub List component Set the avatar size in a Group Hub card API Updates New FreeMarker sequence builder method Get node IDs of nodes displayed in the Group Hubs Listing Page You Found It. We Fixed It! Features Self-serve SAML SSO With this release, we’ve redesigned our existing SAML 2.0 integration to enable Community Admins to configure authentication for their Communities and integrate with their SAML IDP by themselves. SAML SSO is now available out of the box as a core product feature, instead of a plugin-based approach used earlier. This simplifies setting up SAML SSO in Communities and helps reduce the total cost of ownership. The key features in Self- serve SAML SSO include: Dynamic metadata: Supports up to three identity providers. Admins can integrate a maximum of three IDPs (that are XML strings) in the Admin panel instead of maintaining it in a config file. Dynamic entity identification: Admins can add the attribute name for the SSOID for their community. If this value changes, Admins can change the value and save it without restarting the Community. Dynamic assertion mapping: Admins can add all the attribute names in the SAML assertion in the Assertion Mapping tab in the Community Admin panel. This eliminates the need for maintaining a config file for Assertion mapping. Note: Communities launching post Community version 21.5 can opt to configure Self-serve SAML SSO while launching. Existing customers who want to switch to using self-serve SAML SSO must contact their Customer Success Manager or Account Executive. This process involves Professional Services (PS) engagement for user/SSO ID migration and may need to address other customisations such as user authentication workflows, custom user profile fields, and other customisations or integrations relying on user data. You can find the settings for Self-serve SAML SSO under Community Admin > Admin > SYSTEM > SAML SSO. Learn more about SAML SSO Learn more on how you can configure SAML SSO from the Admin panel Learn more about the SAML SSO tabs and settings in the Admin panel In the 21.4 release, we introduced the Feature Logs framework. This framework helps generate and view feature specific logs in components and endpoints. Developers and administrators can use these logs to monitor and debug during Community customisation. We are happy to announce that we are now explicitly providing you with status and error logs to help with monitoring and debugging issues when you configure Self-serve SAML SSO for your community. Learn more about Feature Logging in the Developer Documentation Portal. Note: Along with enabling Self serve SAML SSO, the PS/Support team can also enable Feature Logs in your Community so that you can access the logs from the ToolBox while setting up SAML SSO. Enhancements Remove the restriction on the number of Events node within a category With this release, we have removed the limit on the number of Event nodes/boards you can create within a category or Community. Removing this limit allows you to host events specific to a product or exclusive to a particular set of members at the community level or within the same category instead of creating another category to create a new event board. However, you can have only one Event board within a Group Hub. Learn more about Events Increase in the date range limit in Community Analytics reports Earlier Community Managers had to stitch together multiple reports to build Year to date(YTD) reports since the maximum time range for Community Analytics reports was six months. With this release, the date range is increased to one year making it possible to easily view and download YTD reports. Note: You might experience a slight delay when the system fetches or downloads a year’s worth of data. There are no other changes to the way the Community Analytics report works. The look-back period remains two years, and 2000 is still the maximum number of rows available in all CSV exports(except the Bulk Download Member Data Report). Specify the default sort order for Group Hub List component You can now specify the default sort order for the grouphubs.widget.grid component, which displays Group Hub cards in the Group Hub Listing Page. You define the default sort order using a new initialSort parameter in the quilt XML. If the initialSort parameter is not included in the quilt XML for the component, the component is sorted by Member Count. Example: <component id="grouphubs.widget.grid" initialSort="alpha" /> Learn more about setting the initialSort parameter. Set the avatar size in a Group Hub card You can now control the image size of the group hub avatar displayed in a group hub card displayed in the Group Hub Listing Page. Set the default avatar size using the size XML parameter for the node.widget.avatar-limurs component in the Group Hub Card quilt. Supported options are tiny (the default), small, medium, and large. Example: <component id="nodes.widget.avatar-limuirs" size="small" /> Learn more about setting the avatar size in a group hub card. API Updates New FreeMarker sequence builder method We have added the utils.sequence.builder() method to the utils FreeMarker context object to create a sequence builder and build a sequence using a large number of items. Using a builder instead of concatenation improves performance and stability. Get node IDs of nodes displayed in the Group Hubs Listing Page We have exposed a new node subobject on env.context in the FreeMarker API. Returns a node context object. Chain calls from the node context object to get the node ID of the node in context. env.context.node has a single method, .displayId. and is supported only on the GroupHubCard (GroupHubCard.quilt.xml), which is used to format the grouphubs.widget.grid component on the Group Hub Listing Page. You found it! We fixed it! We have fixed the issue in Forums v5 where the HTML option was not available to members with the Allow user to use advanced HTML in posts and signatures permission grant and the Use full HTML in posts and signatures permission denied. We have fixed the issue where the solution count on the leaderboard did not match the user's actual number of solutions. We have fixed the issue that the preview of the avatar did not match the cropped image. We have fixed the issue where deleting the labels of a TKB article via API deletes the list of contributors along with the labels. Now, the list of contributors stays intact after deleting the labels. We have fixed the issue when members with periods or spaces in their usernames receive an error message while uploading or copy/pasting images. We have fixed the issue where the toolbar options in the message editor did not support keyboard shortcuts. Now, you can also access these options without the mouse and only with the keyboard keys. We have fixed the issue where the + sign to open the Community’s Tree Structure in the Admin panel was not available. We have fixed the issue where the Community structure in the Admin panel breaks after the Communities that use the Accessibility feature restart their Community. We have fixed the issue in Forum v5 where opening any post marked as spam did not display that post is marked as spam. We have fixed an SEO issue where the Open Graph URL did not match the Canonical URL. Now, they will be same, thus benefiting SEO.ViewsSign in to react to this postCommentsAurora Analytics Metric Definitions
This article provides definitions for all the metrics available in Aurora Analytics. Aurora Analytics approximates user behavior and therefore these metrics exclude almost all nonhuman requests (Web crawlers, robots, RSS feeds, REST API calls). About how Community visit metrics are calculated When viewing visits metrics, you might see small variants in the reported numbers. This is expected when you compare visits metric for a period within a month versus a sum of months in that period. The main reasons for these differences include: Overlapping visits across months "Visits" are defined as the number of unique user sessions. A session is defined as a group of interactions one user takes within a given time frame. Sessions time out in the case of 30-minute inactivity. Assume someone browsed through a community during the last hour of a month (Month-1) and continued browsing through the first hour of next month (Month-2). In this scenario: When we measure visits for Month 1, this session is counted as 1 visit. When we measure visits for Month 2, this session is counted as 1 visit. So, when you sum up visits for Month 1 and Month 2, you see 2 total visits, whereas, if you measure visits over the 2-month period, this session is counted as a single visit. Algorithm approximation "Visits" and "visitors" metrics are an approximation algorithm in their calculations. As such, there might be a 1-2% variance in the calculations. Elastic search documentation mentions that sometimes the variance could be up to 6%. Aurora Analytics metrics and definitions Widget/Metrics Definition Page Views A page view is counted each time a browser requests a page regardless of the device type or whether the page is cached. Page Views approximate user behavior and therefore exclude non-human requests (web crawlers, bots, RSS feeds, REST API calls). Page Views (Trend graph) Page Views trend graph is a line graph that shows how the Page Views are trending for the selected time frame. Visits A visit is one or more page views over time by a uniquely identified visitor. A cookie set in the browser identifies visitors (anonymous or registered), so if a visitor has cookies turned off, each page view counts as a new visit. The visit counter increments as soon as the visitor views any community page; the visit ends after 30 minutes of inactivity. After the 30-minute timeout, the next page view counts as a new visit. The Mobile Visits metric is a subset of the Visits metric and includes requests from mobile web browsers only. Unique Visitors The number of unique visitors over the specified time interval. When a visitor (registered or anonymous) views a page, the application looks for a visitor cookie. If no cookie is found, a new cookie is created, and the visitor counts as a new unique visitor. If a visitor cookie is found, the Unique Visitor counter is not incremented. If cookies are cleared after a visit, the next visit sets a new cookie and counts a new unique visitor. Since cookies are browser dependent, so are unique visitors. Users who access the community from different browsers count as a unique visitor. The Mobile Unique Visitors metric is a subset of the Unique Visitors metric and includes visitors who used mobile web browsers only over the specified time interval. Page Views/Visit The average number of Page Views per Visit for the time frame selected. Visits vs. Unique Visitors The trend of the number of visits to the community site against the number of unique visitors for the selected time frame. Visits by User Type The number of visits made by anonymous users and signed-in users. Anonymous users also refer to community members who have not logged in. Learn more about Visits by User Type. Visit Referrals The number of community visits that originated from specific URL domains. This metric helps you understand how much traffic is coming in from different search engines, social networks, or links on your company website. Completed Registrations The number of member registrations completed during the selected time period (excludes partial/abandoned registrations). A registration is considered complete when the visitor finishes the sign-up flow and is given a unique user ID. If the visitor leaves the sign-up flow before being granted their unique user ID, the registration is considered to be abandoned, and the completed registration counter is not incremented. If the community uses Single Sign On (SSO), Khoros increments the completed registration count the first time it receives an authentication token that contains a unique User ID. Partial Registrations The number of user registrations abandoned during the selected time period. Completed and Partial Registrations The line graph shows how the completed and partial registrations are trending over the selected time frame. DAU/MAU DAU (Daily Active Users) is the number of unique members who engage (at least one page view) with the community in a one-day window. MAU (Monthly Active Users) is the number of unique members who engage (at least one page view) with the community over a month or 30-day window. The ratio of DAU to MAU is the proportion of monthly active members who engage with the community in a single day window. Member Time on Site The Member Time metric indicates the total number of minutes from first page request to last page request for each visit of all registered members in your community during the date range of the report. Member time does not capture the time of actions, such as likes, unless the member requests a new page after the action. Nor does it include the last 30 minutes after the last page request before the session times out. Member time is calculated from the time of the first page request, such that a session that started at 11:50pm on day 1 and ending at 12:15am on day 2 is counted as member time for day 1. New vs. Returning Members New members are members who have never visited the community and are visiting for the first time. Returning members are members who have visited the community before. This line graph shows the trend of new and returning members over the selected time frame. Note that this widget will show data for the last 30 days only, irrespective of the selected date range. Depending on the time range you choose in the dashboard settings, you may get partial data or no data. New vs. Returning Anonymous Users When a user views the community without signing in, the community looks for cookies saved on their device. If there is no cookie present, then the user is treated as a New Anonymous User. If cookies are present, then the user is treated as a Returning Anonymous User. Since members can also view the community without signing in, they are also considered Anonymous. Note that this widget will show data for the last 30 days only, irrespective of the selected date range. Depending on the time range you choose in the dashboard settings, you may get partial data or no data. Forum This widget shows the engagement on the selected Place for the date range selected. Shows the number and trend line of the number of discussions created, number of likes received, number of replies for the time frame and selected Place. Click View Details for further insights. Blog This widget shows the engagement on the selected Blog for the date range selected. Shows the number and trend line of the number of posts created, number of likes received, and the number of comments for the time frame and selected Place. Click View Details for further insights. Knowledge Base This widget shows the engagement on the selected Knowledge Base for the date range selected. Shows the number and trend line of the number of articles created, number of likes received, and the number of comments for the time frame and selected Place. Click View Details for further insights. Places - Follows The total number of followers for the selected Place. Topics - Follows The total number of followers for the selected Content. Observing vs. Participating vs. Contributing This widget shows the engagement between members who are observing, participating and contributing in the community for the place and time frame selected. Observing members are those who have signed into the community and their engagement is limited only to viewing the contents. Participating members are those who reply or like posts in the community. Contributing members are those who create content or provide solutions in the community. Private Messages This widget shows the number of private messages sent, its trend line and the messages per conversation in the community for the time frame selected. Messages sent The number of private messages sent from the inbox by all the community members during the selected time frame. Messages sent (trend graph) The trend line graph showing the number of private messages sent from the inbox by all the community members during the selected time period. Discussions The number of Discussions in the selected Place during the selected time frame. Likes The number of likes received for the Discussions and replies in the selected Place during the selected time frame. Replies The number of replies received for the Discussions in the selected Place during the selected time frame. Engagement Shows the trend line for number of Discussions, likes, and replies in the Place during the selected time period in Forums Details. Shows the trend line for number of Blog posts, likes, and comments in the Place during the selected time period in Blogs Details. Shows the trend line for number of articles, likes, and replies in the Place during the selected time period in Knowledge Base Details. Shows the trend line for number of ideas, votes, and comments in the Place during the selected time period in Ideas Board Details. Time to First Reply The time taken (average) for Discussions in the selected Place to receive its first reply after it has been initially submitted. It is typically measured from the moment the Discussion is published to the moment someone replies to it. First Replies The total number of first comments on all the Discussions in the selected Place during the selected time frame. If for the selected time frame there are 10 Discussions in the selected Place, and only 4 have received a reply, then the total number of first replies is 4. If for the selected time frame there are 10 Discussions in the selected Place and only 1 Discussion has replies, even if that one Discussion has 5 total replies, the First Replies is 1. Marked As Solved The number of Discussion replies that are marked as an accepted solution for the selected Place and for the selected time frame. There is only 1 solution per Discussion. Marked As Solved Trend Shows the trend line for the number of replies that are marked as an accepted solution for the forums in the selected Place and for the selected time frame. Solutions Authored The number of solutions the member provided for a discussion Time to Solution The average time taken for the replies in Discussions for the selected Place to be marked as an accepted solution. It is measured from the moment the Discussion is posted until one of its replies is marked as an accepted solution. Solution Views A count of page views of Discussions with an accepted solution after the Discussion has had a reply marked as an accepted solution. Forum - Follows The total number of followers for the selected Forum during the time frame selected. Discussions - Follows The total number of followers for the Discussions in the selected Place during the time frame selected. New and Trending Discussions The total number of new Discussions and trending Discussions in the Forum selected during the selected time frame. The metric values for Trending Discussions depends on the minimum number of views set in the Engagement dashboard settings. Posts The number of blog posts in the selected Place during the selected time frame. Comments (for Blogs and Ideas) The number of comments the blog posts or Ideas in the selected Place received during the selected time frame. Articles The number of Knowledge Base articles in the selected Place during the selected time frame. Blog - Follows The total number of followers for the Blog in the selected Place during the time frame selected. Posts - Follows The total number of followers for the Blog posts in the selected Place during the time frame selected. Knowledge Base - Follows The total number of followers for the Knowledge Bases in the selected Place during the time frame selected. Article - Follows The total number of followers for the Knowledge Bases articles in the selected Place during the time frame selected. TTFR Time to First Reply TTFS Time to First Solution Helpful Votes The number of votes the Knowledge Base board or article received stating that they were helpful. Unhelpful Votes The number of votes the Knowledge Base board or article received stating that they were unhelpful. Members Joined The number of members who joined the Group. Members Left The number of members who left the Group. Invitations Sent The number of invitations sent to members to join the Group. Invitations Accepted The number of invitations that were accepted by members to join the Group. Ideas Snapshot (widget) This widget contains the metrics related to Ideas Board. The metrics are number of ideas, number of comments received, number of votes received during the selected time period for the Place selected. Ideas (Groups, Events and Members reports) Total number of ideas created during the selected time period for the selected Place. Votes Total number of votes received during the selected time period for the selected Place. Idea Votes (Members report) Total number of votes given by members during the selected time period for the selected Place. Idea Votes Given (Members report) Total number of votes given by members during the selected time period for the selected Place. Idea Votes Received (Members report) Total number of votes given to the member's ideas during the selected time period for the selected Place. Closed Total number of ideas closed during the selected time period for the selected Place. Completed Total number of ideas completed during the selected time period for the selected Place. Events (Groups, Events, and Members reports) The number of events in the selected Place during the selected time frame. RSVP-Attending (Groups, Events and Members reports) The number of members who RSVP'd 'yes' to the events in the selected Place during the selected time frame. RSVP-Interested (Groups, Events, and Members reports) The number of members who RSVP'd 'Interested' to the events in the selected Place during the selected time frame. Attended The number of members who attended the events in the selected Place during the selected time frame. Events Attendance (Members report) The number of members who attended the events in Groups for selected Place during the selected time frame. Events Attended (Members report) The number of events the member attended during the selected time frame. Events by type (widget) This widget shows engagement on events based on the event type (In-person, Online, and Hybrid). Lead-up to the Event (widget) This widget shows metrics on all the activities that occurred on the event before it started. Note: In Classic Analytics, a summation of all posts in the community (root topics and replies across discussion styles) is presented as the Posts metric in the Categories report. However, in Aurora Analytics, the root topics and replies across content types (Forums, KB, Blog, Ideas, and Events) are presented as specific/independent metrics, instead of adding them together and presenting as the Posts metric. Related topics: About Aurora Analytics Dashboard Settings Aurora Analytics ReportsViewsSign in to react to this postCommentsKhoros Communities 22.8 Release
Content Enhancements Support for additional content types for Content archive Salesforce Connector v4.3 (General Availability) E-mail notification status information in the Bulk Download Member Data Enable Moderators to access Group Hubs in Community URLs to the Group Hubs .csv File Export API Fetch users subscribed to a label Support additional content type for content archival Bug Fixes General Fixes Accessibility Fixes Enhancements Support for additional content types for Content archive Previously, you could individually or bulk archive only KB articles, blog posts, and forum discussions. With this release, you can now archive Events, Ideas, and Q&A discussions. You can also unarchive (one-at-a-time) any archived ideas, events, and Q&A posts from the Archives page. The screenshot below displays the Bulk Archive page, now with the ability to archive all the above-mentioned discussion styles: You can also archive Ideas, Events, and Q&A posts from the post level menu options. Learn more about content archival and bulk content archival. Salesforce Connector v4.3 (General Availability) In community version 22.6, we released early access to SFDC v4.3. With this release, we are happy to announce the General Availability of this feature. Learn more on Connector for Salesforce package versions and upgrades Learn more about the issue fixes and enhancements on all Salesforce Connector Versions E-mail notification status information in the Bulk Download Member Data With this release we have introduced a new field - Email Notifications Allowed to the Bulk Download Member Data Report. For members who have opted not to receive email notifications, this field shows “No”. Otherwise, it shows “Yes”. To set whether or not to receive email notifications, click your profile image and go to My Subscriptions > SUBSCRIPTION & NOTIFICATIONS > Notification Settings. The screenshot below shows that the member has opted to receive email notifications. For this member, the Email Notifications Allowed column in the Bulk Download Member Data Report displays “Yes”. Bulk Download Member Data Report for the above example: Learn more about Bulk Download Member Data Report Enable Moderators to access Closed and Hidden Group Hubs in Community With this release, Moderators (who have permissions such as Mark posts as moderated, Bypass content filters, Bypass automatic spam rejection, and Approve, recall, or reject topics and posts) can access closed and hidden group hubs. When granted these permissions, moderators can moderate content within those group hubs without being a group hub member. This is controlled by a config, which is enabled by default (to disable it, contact Support). Note: To enable Moderators to access and moderate Group Hub content (Closed or Hidden) without being Group Hub members, you must explicitly grant (not granted by default) the “See discussion style boards ” and “See Group Hubs” permissions to Moderators. Learn more about Group Hub roles and permissions URLs to the Group Hubs .csv File Export Earlier, links to the community’s Group Hubs page from the Group Hub reports’ .csv files were not provided. With this release, we have included links to the community's Group Hubs in the downloaded .csv files. To download the Group Hubs report, go to Content > Group Hubs and click the Group Hubs tab. Then, open the gear menu and click Export (CSV). The screenshot below shows the downloaded file with the URL to redirect you to that Group Hub in your community. API Updates Fetch users subscribed to a label Previously, querying a label subscription provided the results of the label subscription specific to the logged-in user. With this release, we have updated the subscription collection to fetch all the community users subscribed to a particular label. Learn more about target.type and target.id constraint. Support additional content type for content archival Previously, you could archive the content only for blogs, forums, and KBs. With this release, we have extended the content archival and bulk content archival APIs to support the archival of Ideas, Events, and Q&A. You found it! We fixed it! General Fixes There was an issue where the contents of notification emails were displayed in a table even though the Remove HTML from mail option under My profile > Subscriptions & Notifications > Email Format was enabled. This is now fixed. Previously, when members with permission to bypass the read-only setting on the community submitted a post with a label, notifications were sent to the subscribers of the label. This post was lost during a migration process and was uploaded with an image instead of a message. When users clicked on the notification feed, the page errored out since the post was missing. This eventually led to page errors in the community. This issue is now fixed. Now the notification page loads successfully and any corrupt data for that notification is not displayed. The issue where the daily digest emails are intermittently not sent from the community is now fixed. The issue where KB authors were not auto-subscribed to their own articles is now fixed. Previously, when topics were merged from one forum board to another, the notification email and notification feed text for merge messages were incorrect. This issue is now fixed. Previously, when admins ran catalog sync by enabling product catalog sync, product catalog sync failed on manual sync. This issue is fixed. Now, product catalog sync runs successfully on manual sync. Users must have the administrator role to run the auto and manual sync from community versions 22.6 and 22.8 onwards respectively. The relevant integrate your product catalog guide is updated with the fixed issue information. Previously, when members replied to a thread for any topic and tried to preview the message they had entered in the message editor, the message editor preview failed to load and an error message was displayed indicating that the requested action was unable to complete. This issue is fixed. Now, members can preview the message they have entered in the message editor. Previously, when members mentioned any registered users with their usernames using the “@” symbol while replying to a post via smartphone and if there was any space in the username that they mentioned, the system failed to list the appropriate username in the dropdown. This issue is fixed. Now, the system lists the appropriate usernames based on the specified mentions. Previously, when members tried to attach an ICB file (.icb) to a draft post in the community, the file failed to upload and an error message was displayed indicating that the .icb content type does not match its file extension and the file has been removed. This issue is fixed. Now, members can successfully attach ICB files while creating a new post or replying to a post in the community. Previously, when members tried to attach a .pbit file to a draft post in the community, the file failed to upload due to MIME type errors. This issue is fixed. Now, members can successfully attach .pbit files while creating a new post or replying to a post in the community. Previously, signed-in users were able to retrieve the draft history of blogs or KBs of any authors via API even if they did not have any specific permissions. This issue is fixed. Now, users cannot view the draft history of other authors without appropriate permissions. Previously , the ‘See discussion style boards’ permission was not exposed in the UI for Hidden Group Hub roles . This prevented a cloned role of hidden group hub from managing Group Hub membership. This issue is fixed. Now, the permission is visible for Group Hub roles (OOTB and cloned group hub roles) of hidden group hubs and admins can grant this permission. The Hidden Group Hubs continue to be not available for non-group hub members as the permission is not available at Group Hub node level defaults. Accessibility Fixes The issue where the screen reader did not announce the list item count for the “Options” menu on the Gallery page is fixed. The accessibility issue where duplicate-id errors were thrown while running the Accessibility Insights Tool on the forum page is fixed. Previously, when you selected tab items under the ‘Ideas’ pane on the community page, the screen reader focus moved to the top of the page. Members who use screen readers had difficulty interacting with the tab items. This issue is fixed. Now, the screen reader focus remains on the selected tab items on the community page. To implement this fix, your community must be on v22.8 or above, and Ideas v3.1ViewsSign in to react to this postCommentsCommunity Classic 24.05
Member Experience Consent for third-party cookies usage in Events Removed limits on number of recipients for Private messages Member Experience Consent for third-party cookies usage in Events In Communities v23.10, we introduced an enhancement requiring users to explicitly consent for using cookies while uploading or viewing external videos in the posts. In this release, we have extended this enhancement to the Events. Now, members must explicitly consent to the usage of cookies when they use external videos to host Events on the Community. Below is an example of the consent banner on an events page: Removed limits on number of recipients for Private messages For communities in version 20.6 and later, messaging was limited to 10,000 users per message by default, with the option to configure this limit. With this release, we have removed these limitations altogether. You can now send messages to an unlimited number of users without any restrictions.ViewsSign in to react to this postCommentsKhoros Communities 21.6 Release
21.6 is a minor release. As communicated earlier, minor releases contain defect fixes and minor enhancements. Minor releases are not made available in production by default. To request an on-demand upgrade, contact Support. Content Enhancements Changes to the community cookie banner Bulk Download Member Data metrics to consider Events discussion style API Updates Moving events between boards using the Move API You found it. We fixed it! Enhancements Changes to the community cookie banner The community cookie banner now shows Accept instead of OK and includes a Reject button. The banner is displayed on your community site for each visitor until that visitor clicks the Accept or Reject button. Clicking the Learn more link opens the webpage that describes your cookie policy but does not dismiss the banner. Users must click Accept in the cookie banner and explicitly confirm their consent to activate the community cookies. Once accepted, the cookie banner will not appear in subsequent logins. If users click Reject, only the Type 1 cookies (“Strictly Necessary”) are set, and all other cookies are held back. Once rejected, the cookie banner will not appear in subsequent signins. If users do not Accept or Reject and browse the community, only the Type 1 cookies (“Strictly Necessary”) are set, and all other cookies are held back. The banner will continue to show in the subsequent signins. The table below shows the expected combinations when cookies need to be dropped Cookie Banner LithiumCookieAccepted Value User Action Drop Type 2/3/4 Cookies Disabled 0 N/A Yes Enabled 0 No action taken No Enabled 1 Click "Accept" Yes Enabled 2 Click "Reject" No Learn more on how to enable site-wide cookie notification banner. Bulk Download Member Data metrics to consider Events discussion style The metrics in the Bulk Download Member Data report will now consider Events discussion style along with the existing discussion styles. Henceforth, when you request the Bulk Download Member Data report for a particular time period(for example, March 2021), the Events discussion style will also be considered for computing the metrics. This enhancement is already available to all communities using Events and hence a support ticket is not needed. Learn more about metrics in Bulk Download Member Data. API Updates Moving events between boards using the Move API We have enhanced the existing Move API to now support the moving of events. You may want to move an event from one Events board to another when you find it more relevant to another Events board. With this release, using the Community v1 Move API, you can move an event along with its comments, RSVP information and invite data to another board. After a successful move, the destination board's permissions govern the event's access. Note: You can move only the event (which equates to a topic message). However, it is required to move the comments along with the event. Hence, always set the move_message.include_replies parameter to true. You found it. We fixed it! Earlier, users without relevant HTML privileges trying to reply with invalid HTML on Forums v5 received errors, and the errors were not being removed automatically. Then resubmitting the post resulted in post-flooding warnings, and the post never got published. With this fix, users will still receive the error message when they submit a post with HTML errors, but the errors will be auto-corrected, and they can successfully submit the post. The issue with the events not displaying in the calendar component in the Firefox browser is now fixed. We have fixed the Mobile View issues for Events Calendars, where after closing a tab with the details of a particular event, all events in the Calendar disappear. There was a dependency on the TKB discussion style to add or remove the list of co-authors in the Blogs discussion. This prevented the list of 'Co-Authors' from being displayed in the Blogs especially in those communities which did not have the TKB discussion style. With this release, we have removed this dependency. The performance issue with the media page load time is fixed. Previously, using the "message-list" component in Forums v5 and changing the display format for posts from Linear to Threaded displayed the list of articles TKB Page with a broken layout. Also, the avatars shifted to the right. With this release, we have fixed this issue. Now when you use this component, the TKB Page displays an undistorted list of articles. We have fixed the issue for communities with the email metrics feature enabled, where opening the invite URL in the email for a topic throws an error. Now, clicking the URL redirects you to the topic. We have fixed the issue where the 'Mark all content as spam' option did not work for messages beyond the first 2000 messages authored by a user. We have fixed the issue where the ‘Top Kudoed Posts’ widget displayed archived content. Accessibility fixes The issue with using the "tab" key on the keyboard to move focus from left to right between the options on the community page header is now resolved. Earlier the role attribute of the help icon “i” was read out as a link instead of a button. This issue is now resolved and will now be recognised as a button. The Microsoft Windows-specific issue with the state of a link selected on the Help page not being announced by a screen reader is resolved.ViewsSign in to react to this postCommentsKhoros Communities 22.2 Release
Content Features Bulk content archive (GA) OAuth 2.0 Client Credentials Flow Enhancement Group Hubs roles hierarchy (GA) Search for products on community Syndicate Comments List along with Product information Group Hub Name filter in Community Analytics API Updates CWA API Updates Bug Fixes Features Bulk content archive (GA) In the 21.10 release, we announced the EA of bulk content archive, which enabled you to search for outdated community content and archive multiple articles at once. Bulk Archive is now released as GA in Community release 22.2. Note: To enable this feature, contact Support. Learn more about Bulk content archive. Watch our Bulk content archive coaching video. Learn more about the bulk content archive APIs, Also see, Bulk Archive Content guide. OAuth 2.0 Client Credentials Flow Note: To enable this authorization, contact Support. In this release, we have added OAuth 2.0 Client Credentials Grant flow that reduces the usage of user name and password in the backend system. The client credentials flow enables server-to-server authorization which grants access to read data from the community, based on the access provided by the assigned role for the client app without the need of any user credentials. Learn more about, see OAuth 2.0 Client Credentials Grant flow. Enhancement Group Hubs roles hierarchy (GA) Currently, Membership Roles for Group Hubs exist only at the Group Hub level. To change permissions for these roles, you needed to go to each group hub to make the changes. For communities with several group hubs, this could be a time-consuming task. In this release, we’ve introduced a roles hierarchy for Group Hubs, enabling global management of group hub role permissions. Now, you can change the membership role permissions either at the community level or at the category level. The permissions for the roles cascade down to all the group hubs within the community or the category, respectively. Note: This feature is enabled for all customers by default. When you update your community to this feature, The OOTB permissions of existing group hubs will be set to default. These permissions will then be derived from the community level group hub roles. Any permissions that were previously changed explicitly for a group hub, will remain as is. You can change the permissions of any of these roles at the group hub level or category level. The permissions at the group hub level takes precedence over the roles defined at the category level, followed by the roles defined at the community level. When this feature is enabled, you can manage all group hub related roles (Curator, Inviter, Member, and Owner) from the Admin > Users > Group Hub Roles tab. These roles are now available at the community and category levels. What this means for existing group hubs: If you were using the out-of-the-box group hub permissions and had not made explicit changes to the individual group hubs, you will not experience any behavior change. However, you will have the additional capability to manage these roles' permissions globally. If you had changed permissions for individual group hub roles earlier, those changes would persist. So you will not experience any behavior change. If you want to change such permissions back to the default, you must set the permission value to 'default' in the required group hubs. Learn more about Group Hub roles hierarchy and how Group Hub role permissions are determined. Search for products on community With this release, we’ve added PRODUCT search in the ‘Search Results’ page to increase the findability of products in the community. Users can search information on the community’s ‘Search Results’ page and see the list of products that match the search query. They can then click the product they are interested in to get authentic information around it. Note: This feature is enabled for all customers by default. To use this feature you must be on Search v3.4 and Product v2.0. Goto Admin > Studio > Features to update to these versions. As shown in the image below, you can search for a product on the community’s ‘Search Results’ page. Click the PRODUCTS tab. Select from the Category and/or the Manufacturer dropdowns, to get the list of products. Assume that you select ‘Tents’ from the Category drop-down menu and “Quecha” from Manufacturer. As shown below, all products that are tagged with these two selections are listed. From here, you can click the product and view the product details. There can be cases where you do not want to use any of these dropdowns because some of the products are not categorized. In such cases, you can opt to disable the Category and Manufacturer dropdowns using the XML in the Studio. Useful links: Add a product to a product category using Community Admin Update to Search v3.4 and Product v2.0 Enable or disable Product Search and Filter using XML Syndicate Comments List along with Product information As mentioned above, you can now search for products in the community. Finding products makes it easier for customers to discuss them within the community. With this release, you can syndicate user-generated content or conversations around a product to external pages (for example external marketing or support pages) along with the product's information. By syndicating comments along with the product’s information on an external website, You can use community to cross sell and drive revenue Users always see or have access to authentic information about the product from the community. You can display product information in appropriate external websites, offering tips and tricks to increase sales on a marketing page or reduce calls to agents on a support page. Below screenshot shows the Product dropdown added to Community Syndication under ADMIN panel. Below screenshot shows product-id added to the code which you can add to the external website. This enables the product information to be syndicated along with the comments. Learn more about setting up comment syndication with product information Useful links: Comments-List-development-and-testing Comments-List-Syndication-FAQ Group Hub Name filter in Community Analytics We have added a filter for Group Hub Name. You can specify a Group Hub name to retrieve the metrics for Group Hub, Conversations, Members, and Membership for that Group hub. NOTE: This option is available to all customers, by default. As shown in the below screenshot, go to CONTENT > Group Hubs. Click Add a filter. Select Group Hub Name from the Filter by dropdown. API Updates CWA API Updates We have added count(*) support to fetch the count of draft articles for the content workflow feature. You can now combine the author.id or conversation.style constraints with the visibility_scope constraint to retrieve drafts filtered by conversation style or author ID. Learn more aboutLiQL reference for the messages collection, You found it! We fixed it! General fixes Earlier, TKBs and Blogs having “&” in their titles were saved as draft or submitted for review or publication, the title displayed “& amp;” instead of “&”. This issue is fixed. Earlier email notifications having “&” in their subjects displayed “& amp;” instead of “&”. This issue is fixed. Earlier, when you created or updated an API from Admin > System > API apps page, you received an error message. This issue is fixed. Earlier, when a post on the community that was escalated to Salesforce was moved to another board, the changes did not update in Salesforce. This issue is fixed. Now, when you move an escalated post to another board, the board details in the Salesforce also updates with the new board details. Earlier, there was a delay with the navigation slide-out menu. After a member joined a hidden group hub, it did not appear in the menu. This issue is fixed. There was an issue with the Kudo and Solution counts which were getting reduced in leaderboards when content was archived. Similar issue was observed with the APIs to get the kudo counts for a user. This is now fixed. Earlier the pagination in the spam quarantine page showed inconsistent behavior due to user access privileges and spam content was not displayed uniformly across pages. We have now fixed this. There was an issue with roles based badge creation , wherein once a badge was created (but not activated), the system did not show the correct count for the number of community users who would receive the badge on activation. This is now fixed. Scheduling of reports was not working for GroupHubs Membership under GroupHubs Overview in Community Analytics. This issue has been fixed now.ViewsSign in to react to this postCommentsAurora: Filter the Analytics Dashboard
Aurora Analytics enables you to filter data for more granular insights. You can filter based on: Roles Ranks New Topics Username Thread ID To add filters to your dashboard: Open the Account menu and select Analytics. On the dashboard page, select + Filter. Select a filter. Enter relevant values to filter. Select Add. The dashboard displays data for the selected filter. Let's look at an example of filtering data for specific roles. Assume that you want to view metrics and activities by Administrators for the "Products" category in your community for the last 30 days. To filter for this data: Change the scope to Products. Set the date range to Last 30 days. Select +Filter. Select Roles. Select Administrator from the menu. Select Add. The Dashboard displays metrics and activities by Administrators for the "Products" category for the last 30 days. Thread ID You can use this filter to view the metrics related to a particular thread or topic in your community. The Thread ID is the ID found at the end of the community URL. For example, in the below URL, "236502" is the Thread ID for a topic in the community: https://community.khoros.com/kb/supportinformation/khoros-cookies-datasheet-community-care-marketing-khoros-bot/236502 You can add this filter under Dashboard and Reports by selecting the Filter option. You can add more than one Thread ID to the filter. After you select Add, the dashboard displays the metrics for the added Thread IDs or, in other words, the topics with those Thread IDs. Related topics: About Dashboard Settings Scope Analytics data to specific place in the community Set date ranges and data comparison time frame for Aurora Analytics Dashboard Set the Trending Discussions options for Aurora Dashboard View metrics by content type Aurora Analytics Metric DefinitionsViewsSign in to react to this postCommentsKhoros Communities 22.1 Release
22.1 is a minor release. As communicated earlier, minor releases contain defect fixes and minor enhancements. Minor releases are not made available in production by default. To request an on-demand upgrade, contact Support. Content Enhancement Value Analytics survey export Filter anonymous user traffic in Community Analytics Announcement You Found it! We Fixed it! Enhancement Value Analytics survey export The Value Analytics survey questions and the corresponding answers from users were previously mapped to IDs and made available in the survey export. With this enhancement, if you so choose, the text of the questions and answers can be exported, instead of the IDs. Enablement Contact Support to have this enabled for your community. Filter anonymous user traffic in Community Analytics Community analytics users can now filter out anonymous user traffic from the community traffic metrics. Just set the User Name filter to Anonymous to filter out anonymous traffic. Announcement As part of our work at Khoros to continuously improve the security of our applications, we will be rolling out 'Shield Advanced & Additional Rate Limiting' for all of our customers soon. In addition to the network and transport layer protections that come with AWS Shield Standard, AWS Shield Advanced provides detection and mitigation against large and sophisticated DDoS(distributed denial-of-service) attacks near real-time visibility into attack and integration with AWS WAF Rate limiting protects your community and makes it more reliable when there is a spike in requests from a bad actor or a legitimate user who is intentionally or unintentionally trying to overwhelm the servers. You found it! We fixed it! General Fixes You can remove columns in analytics reports using Settings > Manage Columns. However, users were then not able to add the removed columns back to the reports. This issue has been resolved now. The issue where the ‘from/to’ fields in Private Messages were not searched for the entered username is now resolved. After creating an event, if the global language setting was changed, the Featured Guest component was not getting translated. This issue has been resolved. Anonymous users were able to open the unpublished Blog and TKB drafts through URLs. This issue has been fixed. When anonymous users tried to submit a post and were prompted to sign in, an exception error occurred during the sign-in process, and the post was not submitted. This issue has been fixed, and the error no longer appears.. When trying to add a Featured Guest to an Event, if the auto-suggest drop-down box didn’t show the username of the guest, users were unable to add the guest to the event. This issue has been fixed. Previously, authors and admins were not able to view the original image in a post if the image was pending moderation. We have fixed this issue. While managing the role-restricted custom avatar collections via the SDK, a validation error used to occur. This is now fixed, and the user is successfully able to push new role-based avatars via SDK plugin without any errors. Previously, image metadata was stripped from any resized version of an image uploaded in a post . We have fixed this issue, and metadata is now retained after the image is resized. There was an issue with the video metrics being displayed in the admin metrics and in the video details page for a member. This issue is now fixed, and the correct metric values are displayed. Previously, while running a catalog sync(via XML file) with one or more of its products deleted, it threw errors. This issue is now fixed. The catalog sync runs successfully and restores the deleted products. Accessibility fixes Previously, list items present in the Show user options menu button were not accessible by Up-Down arrow key even though they were defined under "List" as "List items". We have fixed this issue. Color contrast accessibility specifications are now met for disabled menu items and disabled state of pagination. Images present on a page are now accessible through a keyboard. Certain accessibility-related attributes for pagination were not defined in a way that would enable a screen reader to announce the current page information. This issue is now fixed. The Compose button on the Private Messages page is now visible in high contrast white mode. Previously, the information announced by a screen reader when the focus was on the number of kudos was not descriptive enough. This issue is now fixed..ViewsSign in to react to this postComments
2.9KViews
30Comments
