I'll try to answer your questions, however, not in order. First off, with the way each app handles this situation MAY be different. In the specific case of Rypple, they offer a free version of the app so that it will showcase some of their capability. They chose to map users via email address. It's been awhile since I've done this, but I believe, when you give a "thanks", they actually build up a graph of connections based on this. So, if I give you a thanks in the Jive Community, and you go into canvas mode of the app, you should see it there. Those recognitions will feed into Rypple's system and will be available from their web app.
1. Are there some circumstances where because of how the data is mapped, multiple instances cannot be integrated and therefore an App should not be made available to a Jive deployment?
In the case of Rypple, I can't think of a situation like this off the top of my head.
Does this help?
Director, Platform & Ecosystem, Jive Software
President, OpenSocial Foundation
Hmmm. I think this is going to be very interesting for us to try and manage. In the specific case of Rypple, the division I work for isn't part of the Rypple contract, so I guess I'll need a demo account to work with and see how the integration works.
I'm also a little concerned based on feedback I got that we could end up with one division who wants their Rypple content to surface in Jive, and another who doesn't. All sorts of cases I hadn't anticipated.
I'll let you know how it goes as we try to move forward. We are making some initial headway with Inxpo, so maybe we'll have a very limited edition of Apps in production soon.
So here's a screen shot of what my canvas view looks like for Rypple:
Each thanks I receive shows up regardless of the instance of Jive that it was "awarded" to me in. This is because I've got the same email address in multiple instances of Jive AND because it's pulling my awards from Rypple's home server.
In your case, you have only one instance of Jive, however, the way that the app works is that each time a person is recognized, it will flow onto the activity stream and be visible by the entire instance. That is, it's not scoped to a specific group/department, etc.
How about we do this...
Let's get Tracy setup with the demo account. (Tracy, is this a Jive demo account or a Rypple demo account?) Next, let's try to simulate the scenario that you have so we can document it accurately. At that point, we can decide our next steps, e.g. should we pull in the Rypple team and run this by them etc.
Does this sound workable?
We aren't talking about multiple instances of Jive, but multiple instances of Rypple (or Salesforce, etc.). And from what Ted understands, Rypple actually has more than one configuration that can be purchased (perhaps only the Thanks is currently integrated into the App?).
I think we've actually come up with a plan for how to move forward with this. I'm still working to get Apps launched in production first, so continuing through the process of understanding how Inxpo will work for us and getting it documented so users get it. Once we've got that live, I'll be working to get other Apps live and/or at least document the process for how we'll move forward with them. I'll let you know what we come up with.
And BTW, we have another company that other parts of the business work with that does something similar to Rypple. I have suggested they consider creating an App, both to help us as well as to get themselves move exposure. They have a company board meeting coming up where they'll be discussing this as a possibility. Wanted you to be aware in case it comes to fruition. I didn't give them contact info yet. Will let you know if/when they ask for it.
Not sure how unorthodox UBM is in this area, but here is my example use case:
- Rypple has a free Jive App
- We have at least two different divisions who have (separate) agreements with Rypple. In other words, it is not a single contract with Rypple, but rather two different contracts.
- How would the information stored in Rypple get integrated into the App?
- Will this same process apply to all App vendors, or will it vary?
- Are there some circumstances where because of how the data is mapped, multiple instances cannot be integrated and therefore an App should not be made available to a Jive deployment?
Thanks for your feedback, Mark Weitzel!