| Jive StreamOnce | |
StreamOnce can integrate with many applications. Some integrations feed application data into Jive where you can collaborate around it: some integrations support bidirectional information streaming and comment updating. If you need a different integration, please alert Jive Sales.
| Integration | Who Benefits? | How it Works | Bidirectional Streaming? |
|---|---|---|---|
| Microsoft Exchange | Any team currently using distribution lists for collaboration. Instead of being isolated in email inboxes and possibly deleted, all messages remain in the group. | Messages sent to the email DL stream into a connected Jive group. Members of the Jive Group can reply within Jive, and the reply will go back out to the DL. | Yes |
| Google Groups (through Google Apps) | Any team currently using Google Groups for collaboration. Instead of being isolated in email inboxes and possibly deleted, all messages remain in the group. | Messages sent to the Google group stream into a connected Jive group. Members of the Jive Group can reply within Jive, and the reply will go back out to the Google group. | Yes |
| Dropbox | Teams that share files with partners or each other through Dropbox. For example, a partner can upload a deliverable into Dropbox. The internal team can then review and discuss the file from within a Jive group. | Files uploaded to a Dropbox Folder will show up in the Jive group the folder is connected to, where community users can collaborate and comment on them. Comments created in Jive do not go back to Dropbox. | No |
| Evernote | Sales and Business Development teams that are on the road and use Evernote to take meeting notes. When they take notes on a mobile device or laptop, their notes will be available within Jive for the rest of their team to collaborate around. | Notes saved to an Evernote notebook will show up in the Jive group the notebook is connected to. Comments within Jive do not go back to Evernote. | No |
| Chatter | Sales teams can leverage Chatter to talk with each other, while other teams who help them to close deals can collaborate in Jive, chiming in as needed. Keeping the conversation in Jive can reduce the number of Salesforce licenses required for non-Sales teams. |
Discussions created in a Chatter group stream into a connected Jive group. Members of the Jive group can reply to the discussion, and the replies will go back to the Chatter group. |
Yes |
| Marketing and Support teams who want to monitor and discuss their Fan Pages. Centralizing the conversation lets them react immediately when needed without leaving Jive, or choose to discuss Facebook posts in context before replying. |
Posts to a Facebook Fan Page stream into a connected Jive group. Members of the Jive group can reply to the Facebook post, and the replies will go back to the Facebook fan page. |
Yes | |
| Sales, Marketing and Support teams who want to monitor and discuss tweets from people or authors of interest. |
Tweets from a connected Twitter handle stream into a connected Jive group. Replies and group discussions won't ever be tweeted. |
No | |
| RSS | Any teams who currently rely on critical information from an RSS Feed as part of their workflow. | RSS feeds stream into a connected Jive group. | No |
| Yammer | Teams that have already adopted Yammer can connect effectively with teams that have adopted Jive for collaboration. For example, when a questions is posted in Yammer, members of a connected Jive Group can also see the question and provide answers. | Discussions created in a Yammer Group stream into a connected Jive group. Members of the Jive group can reply to the discussion, and the replies will go back to the Yammer group. | Yes |
| Bugzilla | Engineering teams who use Bugzilla for defect tracking can encourage richer interactions around issue resolution and draw in other teams who may not use Bugzilla, enhancing cross-team solution-building. | Any new bug created in Bugzilla that exceeds a set priority and severity is streamed into a connected Jive Group as a discussion, and updates to these bugs are also synced to Jive. When members of the Jive group reply to the discussion, the reply is synced to the Bugzilla page for that bug. However, new discussions created on the Jive side are not synced into Bugzilla. | Yes |
| Jive2Jive | Bridges two Jive communities by streaming discussions from group to group. For example, bring discussions from your external community right into your internal one where you can collaborate internally around solutions. | Stream activity from a group in one Jive community into a group in another Jive Community. This functionality is only available for Open and Members Only groups. | Yes |
| Jira | Engineering teams who use Jira for defect tracking can encourage richer interactions around issue resolution and draw in other teams who may not use Jira, enhancing cross-team solution-building. | Based on a "favorite filter" defined in JIRA, streams in all newly created issues that meet the filter conditions, as well as any updates and comments on new and existing issues included in the filter. Even better, any Jive comments posted in response to JIRA activity will be synced as comments to the appropriate JIRA issue. Note, however, that updates to existing comments on either side are not synced, in either direction. | Yes |