Skip Navigation
Expand
Cookies (And Integrations) - Everyone Loves Them, Right?
Answer ID 8931   |   Last Review Date 09/12/2016

I like cookies (chocolate chip).  When I want to bake cookies, I put the cookie dough on the cookie sheet and shove it into the oven. Luckily, when I replace that oven, I don't have to buy a new cookie sheet!  You just start baking another round of fresh cookies again! Sure, you can always get another cookie sheet (twice as many cookies at once) but since nothing is wrong with the old one, you get to keep using it as long as your cookie dough holds out.

This is related to a question customers ask me all the time: Do we have to rewrite an integration every time we upgrade?  The short answer is: No. So how do we ensure that integrations work across releases?  The answer is 'Managed Frameworks'.   Managed Frameworks are similar to cookie molds. They ensure that integrations work across ovens…um, releases.

Oracle Service Cloud's managed frameworks are developed and subsequently versioned to allow integrations to be written once and forgotten at least until you need to make modifications to it due to your business process changes or want to take advantage of new capabilities, of course.  We can do this because we take advantage of the nature of underlying technologies while also nurturing a policy of backward compatibility amongst our development teams.

How can you make use of Managed Frameworks?  You probably already do.  Managed frameworks are available to use through the Connect API's. In a nutshell, Connect API's are product release 'agnostic' and this ensures backward compatibility so that your integrations will continue to work on new product releases. So zero maintenance...really.  (And you can read more about Managed Frameworks here: https://cx.rightnow.com/app/answers/detail/a_id/5169/.)

How do we support Managed Frameworks?  The Connect API's are versioned.  We periodically release new Connect versions that introduce new features and capabilities to the framework.  When integrations are written against a specific Connect version, it will continue to work between upgrades as long as the integration stays on the same connect version. .  And, finally, speaking of versions, we also have a formal policy for shutting down older Connect versions that you can read about here (https://cx.rightnow.com/app/blog/detail/a_id/8718).

We have sites that have upgraded to the latest product release and have integrations written in Connect version 1.0 that are still working.  Considering that Connect 1.0 was released in May 2010, that's quite a few cookies!  What has your experience been with the Connect API's?  (And what kind of cookies do you like?)

I like cookies (chocolate chip).  When I want to bake cookies, I put the cookie dough on the cookie sheet and shove it into the oven. Luckily, when I replace that oven, I don't have to buy a new cookie sheet!  You just start baking another round of fresh cookies again! Sure, you can always get another cookie sheet (twice as many cookies at once) but since nothing is wrong with the old one, you get to keep using it as long as your cookie dough holds out.

.This is related to a question customers ask me all the time: Do we have to rewrite an integration every time we upgrade?  The short answer is: No. So how do we ensure that integrations work across releases?  The answer is 'Managed Frameworks'.   Managed Frameworks are similar to cookie molds. They ensure that integrations work across ovens…um, releases.

Oracle Service Cloud's managed frameworks are developed and subsequently versioned to allow integrations to be written once and forgotten at least until you need to make modifications to it due to your business process changes or want to take advantage of new capabilities, of course.  We can do this because we take advantage of the nature of underlying technologies while also nurturing a policy of backward compatibility amongst our development teams.

How can you make use of Managed Frameworks?  You probably already do.  Managed frameworks are available to use through the Connect APIs. In a nutshell, Connect APIs are product release 'agnostic' and this ensures backward compatibility so that your integrations will continue to work on new product releases. So zero maintenance...really!  (And you can read more about Managed Frameworks here: Answer ID 5169

How do we support Managed Frameworks?  The Connect APIs are versioned.  We periodically release new Connect versions that introduce new features and capabilities to the framework.  When integrations are written against a specific Connect version, they will continue to work between upgrades as long as the integration stays on the same connect version. And, finally, speaking of versions, we also have a formal policy for shutting down older Connect versions that you can read about here (Answer ID 8718).

We have sites that have upgraded to the latest product release and have integrations written in Connect version 1.0 that are still working.  Considering that Connect 1.0 was released in May 2010, that's quite a few cookies!  

What has your experience been with the Connect APIs?  (And what kind of cookies do you like?)

Available Languages for this Answer:

Notify Me
The page will refresh upon submission. Any pending input will be lost.