2 people found this helpful
What you are talking about sounds very similar to a Simple Stream Integration with an App View.
Check out the following resources and hopefully that will get you straightened out:
- Simple Stream Integration Builder - Jive Developers
- Dev Tool: Using the Simple Stream Integration Builder with StatusPage.io (1 of 3)
- Dev Tool: Build an App w/ the Simple Stream Integration Builder (2 of 3) <= This is the one you need to look at.
- Dev Tool: Simple Stream App with Bi-Directional Communication (3 of 3)
See also, Introducing the JiveDev QuickStart App for other ideas =)
Thanks for the links! I've gone ahead and gone through those and I was also viewing this article earlier (How to embed an app within an external stream object ) and this line struck me as bit counterintuitive to what I'm attempting to achieve: "if you want to provide an external stream that, when clicked, opens a rich app view". I'm wondering if it's at all possible to insert content similar to what you would get from going into Jive and composing a blog with the WYSIWYG editor? My end goal is to have the content be indistinguishable from a normal blog (except, of course, for the fact that it was written by a bot).
Thanks again for your help!
1 person found this helpful
So there are 2 manners in which you can go here.
If you want to create a Blog Post with the API, you can do that ... at which point it will be exactly a blog post with all the native functionality. The issue here is that you will need to do some mapping logic and credential sharing specific to this use-case. (i.e. get credentials to create blog posts in Space ABC for User DEF, GHI, etc..). Once you have this, you can call the API every time an activity happens in your source system...and map that information into a blog post via the Contents API (see: Jive REST API v3.14 → Content service )
The SSI pattern that I shared above simplifies this pattern as it gives you an easy to manage credential sharing mechanism and with an embedded App, allows you full fidelity control of the content body to render whatever you want inside the content frame.
If you want the most parity for blog posts, then I would recommend the Contents API approach ... and then just insulate your business rules into a middleware agent to connect the two systems.
Hope that helps clarify the initial direction.