We are currently working on adding Event Subscriptions to Workfront. What that means is that you will be able to subscribe to pre-defined Workfront events that will send a response to a defined endpoint of your choosing. This means that you will be able to interact with the Workfront API in real time. No more queries on an interval searching for changes! What we want to focus on is deploying a minimum viable product quickly, which means there will be some limitations you need to be aware of. Here are some that we know of:
It will not include events tied to the hours object (changes to the hours object, or new hours)
It will not include group based subscriptions (the ability to limit which events send a JSON response to an endpoint based on the group that triggered the event)
It will not include customizable events (the ability to define an event by a filter)
It will not include c ustomizable JSON responses (the ability to define which fields are sent when an event occurs)
It will not include UI based subscriptions (you will have to subscribe through the API or a middleware tool).
It might not include session based events (we are still researching whether we can support allowing users with a session id subscribe to events; it may be that we have to limit this to only apiKey authentication. This would mean that you would not be able to differentiate between which user made the change potentially.)
So, what we need to know from you is whether this represent a minimum viable product. Assuming all of the items above were not available in version 1, would Event Subscriptions be useful? If so, which of these items are the most important to build into version 2. Let me know what questions you have. Thanks!
