Skip navigation

Hi Jive Dev's! I'm pretty excited to present the first in a series of developer tools to assist you in creating some great integrations for your Jive instances. The goal for these tools are to ensure that they save you development time, reduce the likelihood for errors, and simplify the creation of add-on's and apps.

 

The first of these tools is the Simple Stream Integration Builder. It simplifies the process of creating an add-on with one of the new features of Jive Cloud — Simple Stream Integrations — which allows you to have one-way external activity streams WITHOUT middleware. By subscribing to a third-party webhook, we can receive a one-way push FROM a third-party webhook TO Jive. In many circumstances, this take can an hour or two to package together. Now, with just a few lines of transform code and some assets, you can have a simple packaged Jive Add-on in less than 10 minutes.

 

Note: The Simple Stream Integration Builder only works with Jive Cloud (Jive 7 and 8 not supported).

 

Screen Shot 2015-07-17 at 7.58.29 PM.png

 

Some key benefits of this tool:

  • You can create a Jive Simple Stream Integration Add-on in mere minutes from start to zip!
  • No middleware needed.
  • After the add-on is installed, any group or project admin can add the stream to their group.
  • Tailor the activity to display relevant information for individual groups.

 

What you need to do to subscribe to a stream on Jive and build an add-on:

  1. Go to the Simple Stream Integration Builder page.
  2. Watch the demonstration video.
  3. Try it yourself by writing a bit of JavaScript to take the incoming webhook event info and make it speak Jive event info (reference Jive JSON Schema).
  4. Paste in a sample JSON input, test to make sure it’s error free.
  5. Give your add-on a title, description, and accompanying image (128px by 128px recommended).
  6. Install the downloaded zip to your Jive community.
  7. Profit?

 

easy_kitty.jpg

 

That’s it! What could have taken hours now only takes minutes, so you can go ahead and start doing what’s important—watching funny cat videos or “researching” on Reddit. Stay tuned for more tools like this one to get you developing some great integrations and apps for Jive in less time!

Every quarter, Jive releases its latest and most advanced cloud release, and with these releases comes a new bevy of integration features.  A few weeks ago, Jive released its Spring release (2015.2) and we'd like to share with you some of the platform improvements.  If you have any questions about any of the features, feel free to comment on the related documentation, or if you have a general question about this post, please use the comments below.

 

Here are some details about some of these latest features:

 

I'm extremely excited about the features we've put together in 2015.2, and more so about what's coming in the next release(s).  Stay tuned to the Developer Community for more details on some of these new features ... specifically Simple Stream Integrations!

 

Feel free to check out our last Developer update here: What's New in the Jive Developer Platform (2015.1)

 

Reminder

JiveWorld16 Developer Conference

Las Vegas - Aria Resort & Casino

March 14-16, 2016


We'll be doing a call for speakers relatively soon, so kick the tires on the latest integrations and start thinking about what you'd like to submit for consideration.  JiveWorld16 is going to be the cant miss Jive Developer event of the year, so we hope to see each of you there!

profile-image-display.jspa?imageID=28476&size=200

It's been a month now, and I think it's high time that we finally introduce our new Jive Developer Evangelist, Rashed Talukder. =)

 

Rashed comes to us by way of Plantronics where we worked in both their Technical Marketing and R&D Engineering organizations.  Thus far, I've been thoroughly impressed by his passion, skills and his desire to learn the intricacies of the Jive platform.  I'm confident that each of you will enjoy working with him in the Jive Developer Community, and strongly believe that he will be instrumental in taking our developer community to the next level!  Over the next few weeks/months, you should expect to see more engagement from him as he gets ramped up on the Jive Platform.  Until then ...  please join me in welcoming him to the Jive Developer Community!

 

What Does This Mean for Ryan in the Jive Developer Community?

It's simple.  In my new role as Director of Developer Evangelism & Partner Innovation, I'm working on increasing the potency of the Jive platform and this community, so I will still be intimately involved.  It mainly means that I will have more eyes and hands to help make this happen.  To say that I am excited, would be a gross understatement.  =)

 

Also, we are already hard at work planning the JiveWorld16 Developer Conference so stay tuned for more on that coming VERY soon! 


Make sure to share your thoughts on the developer keynote, if you haven't already:

Who Would You Like To See Keynote the JiveWorld16 Developer Conference?

Hi Jivers,


All the jive client developers who have been developing jive add-ons for a while certainly have used the jive rest apis.

 

We at ThoughtWorks have been using server side component for almost all of our jive add-ons with help of jive connects. Server component internally calls jive REST apis. In the past we have developed different add-ons and endup up duplicating the api client code at several places. So recently I thought of creating reusable node modulefor calling REST apis, which looks a bit simialr to the JS apis.


Some of you must have seenhttp://internally call jive REST apis/my previous blog which talked about using jive-sdk to make REST api calls. On the same theory I have developed a open source  node module on github


On client side we have an easy to use JS api which provides us method endpoints like this


osapi.jive.corev3.group.get(<group-url>)




On server side we have following method given by jive-sdk to make REST Calls.

 

jive.community.doRequest(<params>)

 

 

I thought it would be good to have something like the JS apis on server side which provides  easy to use end points for REST apis. An example for this nice jive-sdk method on server side would be something like this:


 

api.group.get(<group-url>)

 

So here's my attempt to add these friendly endpoints to jive-sdk. Its obviously not a complete solution. So I would appreciate if people can give feedback and also help add more wrapper methods to this.


How to use this wrapper?


Just add the github url in your add-on's package.json as follows:

 

Package.json

 

"dependencies": {
    "jive-api-client": "git+https://github.com/shilpakondawar/jive-api-client.git",
}







 

 

Code usage:

 

var jive= require('jive-api-client');
var api = jive("https://jive.example.com");

api.group.get("https://jive.example.com/api/core/v3/places/17257").
  then(function(groupData){
  console.log("groupData",groupData);},
  function(error){
  console.log("Something got wrong",error)});

api.request({url:"https://jive.example.com/api/core/v3/search/places?filter=search(%22test%22)", method:"GET"})
  .then(function (places) {
  console.log("Searched places:", places);},
  function (err) {
  console.log(err);});

 

 

I have added few wrappers and also examples for them in the library. In future I am planning to create npm module and add some more widely usable wrappers. For the time enjoy and use the github code.

Filter Blog