Winter 2015 Cloud Release: Upgrade and Onboarding Guide

Version 3

    This short guide explains the new features and known changes to Jive Cloud with the Winter 2015 Cloud Release (planned for late February). We hope it will help you get ready for this release and explain it to your users.

     

     

    What changes will upgraded users see?

     

    News

     

    The Winter 2015 release has one major component, News, that comes along with significant changes to the information architecture of Jive. (You may know News as "auto-follow," or "subscription streams"--it allows community managers to choose what activity users should automatically follow.) The News feature and all its associated UI changes are turned OFF, until you enable News or until the next Cloud release comes out, whichever is first. Because these changes are so significant, they have their own guide including end user FAQ and a sample upgrade plan, which you can find here: All About the News Feature.

     

    This release also contains the following, more minor features, which will be live at release time.

     

    Subscribers Toggle in Impact Metrics

     

    Impact metrics now include a Subscribers toggle, so you can segment the statistics according to whether viewers are subscribed to the content in a News stream. (You probably want to make sure the people who are auto-subscribed are actually reading, for example.) You'll see the button above the graph when you click View more from an item's impact metrics.

     

    New Community Manager Reports

     

    A new Community Manager report, the Community Health report, provides a great view of change over time, showing statistics about registered user numbers and anonymous users, about content creation, views, reactions, and value (including changes in answered and unanswered questions), and about searches.

     

    Another new report, the Top Successful Search Queries report, tracks searches that ended in a clickthrough to a result. You can see what content people are most interested in. This report can also help you identify searches that might benefit from targeted content via the Promoted Results feature.

     

    Promoted Results

     

    (This is a NEW setting in the admin console. The topic below will also appear in the documentation.)

     

    Community managers can now create rulesets to ensure that particular keywords always return specific content results, even when that keyword does not occur in the content.

     

    Admin Console: System > Settings > Search > Content Search > Promoted Results

     

    Promoting a result ensures that when you type certain keywords, a content item you select will always be at the top of the results. You can associate multiple keywords or key phrases with a single content item by entering the terms separated by commas. You can also associate different content items with the same keyword, so that several content items show up when a user queries that keyword. Use the Priority field to detemine which promoted results for a keyword appear first. For example, if you wanted the European, American, and Asian holiday schedules in your organization to be promoted for the keyword “holidays”, you could create a rule for each document linking it to the keyword “holidays.” Then you could rank these schedules 1, 2, and 3 in the results by assigning the rules priorities 0, 1, and 2.

    Keep in mind the following limitations when promoting results:

     

    • Keywords must be at least three characters long.
    • Single keywords can function as wildcards in spotlight search, but when you specify a key phrase, the query must be an exact match for the key phrase. (Standard searches typed in the search page, or entered by typing in the search field and pressingEnter, do not support wildcards unless you explicitly type*as part of the string.) For example, if you specify "quarter" as a keyword, your selected content will be returned for spotlight search queries on "quart" as well as "quarter." But if you specify "quarterly sales," your selected content will not be returned for queries on "quarter," "quarter sales," "quarterly," or "sales," only for queries on "quarterly sales."
    • No two rules can have the same priority number, so multiple rules for the same keyword or keyword combination must be in sequential order.

     

    To create rules and rulesets for promoting results:

     

    1. In the Keyword(s) field, add one or more keywords separated by commas.
    2. In the Content Link field, type the full URL of a content item, for examplehttps://yourcommunity.com/docs/DOC-4669
    3. Click Add.
    4. If you want more results to be returned for the same keyword(s), add more rules with the same keyword(s) and different content. Then assign a priority to each rule within the group of rules. You can do this automatically by creating the rules in order of document priority, but you can also edit the Priority field after a rule is created. Moving a rule to a higher priority will move other rules down in priority, affecting the numbering of all rules below it. Priority applies only within a group multiple rules with the same keyword or keywords. Note that when you change the priority of an existing rule, the rules above and below it will be renumbered to create a sequential list.

      Because the rules will appear in one sequential list, you might end up with a sequence like this one, which represents two rulesets:

             24. keyword1 document g
             25. keyword1 document a
             26. keyword1 document q
             27. keyword2, keyword3 document x
             28. keyword2, keyword3 document r
             29. keyword2, keyword3 document n

     

            The first ruleset says that when keyword 1 appears in a query, the first three results will be documents g, a, and q. The second ruleset says that when either keyword 2 or keyword 3 appears in a query, the first three results will be documents x, r, and n.

     

         5. When the rules are ordered the way you want them, click Save Settings.

     

    Google Docs Leaves Beta

     

    Google docs is no longer in beta and you'll see the following behavior changes:

     

    • Google docs and files can be instantly synchronized to Jive via WebHooks: no more waiting.
    • You can also move folder hierarchies into a Google Drive folder and expect them to be synchronized into Jive. Note that until you edit a moved document on the Google Docs side, you won't be able to see it in Jive.
    • Google docs now have impact metrics like Jive native documents, so you can track who is viewing, sharing, and responding to them. And they can now be found in community search.

     

    Upgrading Google Docs groups and content you created during the beta may have some complexity. You can expect ongoing communication around how this will work.

     

    Custom Stream Activity Indications are Off

     

    To improve performance, indicators of new activity in custom streams have been removed.

    Third-Party Google and Marketo Analytics

     

    Third-party web analytics tracking has been available in Jive for a long time in an implementation that allowed JavaScript input, but this has caused some security problems. The settings have been modified in this release to support Google and Marketo tracking code out of the box simply by cutting and pasting a tracking ID.

     

    If you have already been using JavaScript input in the System > Settings > Third-Party Analytics screen, you can continue using that setting, or you can reconfigure your setup using the new Google and Marketo tabs. If you need to implement a new analytics solution that isn't Google or Marketo, please reach out to Support.

     

    Apps in Tiles for Developers

     

    Developers planning to build integrations with Jive can now implement an HTML view within a tile. This capability provides flexible control of layout. This custom view can run as a Jive-hosted tile, or can be hosted by your own integration service. Information about how to do this will be published soon in the Developers area of Jive Community.