StreamOnce breaks down information silos by bringing communication from a wide range of enterprise systems directly into your Jive community, where you can interact with it all in one place.
StreamOnce for Jive feeds information from various applications into a Jive group where group members can see it and interact with it.
This article provides the table with the supported StreamOnce integrations and it's working mechanism.
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 the Jive Sales team.
NOTE: StreamOnce is licensed on a per-user basis. Before you start using it in production, you should talk to your account manager about your plans for using StreamOnce.
|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.||
|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.||
|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.||
|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.||
|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.||
|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.||
|Sales, Marketing and Support teams who want to monitor and discuss tweets from people or authors of interest.||
|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 question is posted in Yammer, members of a connected Jive Group can also see the question and provide answers.||
|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.||
|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.||
|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.||