This content has been marked as final. Show 1 reply
I would say there are two ways to do this:
- The webhook you mentioned. Based on criteria, the webhook would be initiated and perform an action, in this case pushing a new configuration to the tile when a new project question is asked. Note, the webhook would have to run somewhere, but you can run this in your own environment and the webhook would be registered to run at that location. There aren't any out of the box mechanisms in Jive for Webhooks, so they have to be custom developed. The benefit is that the tile would get updated in as close to real-time as possible. One minor drawback is that you have to account for if the Webhook fails to run. See the 2nd option for that
- Create a standalone middleware application that periodically retrieves data from Jive (newly posted questions) and then remotely pushes a new configuration to the tile. You can optimize this API call for performance reasons or even maintain a "last run" date so that you're only retrieving recently created content. This has the benefit of running on a schedule (~15m, ~30m, etc), putting monitoring around it's execution, and knowing that you're getting the latest state of the information. You could say the delay in tile update (depending on the schedule) is a negative, but it seems that as long as the tile is updated in a timely manner, it would be ok.