Skip Navigation

Search

Setting an Intelligent Advisor project to run in compatibility mode (downgrade a deployment)
Answer ID 8561   |   Last Review Date 07/10/2026

What can be done if a customer's Intelligent Advisor project isn't compatible with an upgraded Intelligent Advisor hub?

Environment:

Intelligent Advisor

Resolution:

Compatibility mode can be used to run particular deployments in the previous quarterly release version. This provides time to resolve any layout or behavior differences between versions, in other words, it runs the deployment on the previous runtime version so that customers have time to remediate any differences introduced by the current release.

Compatibility mode can be useful if:

  • you are experiencing issues with deployed interviews or web services after upgrade, or
  • you know that the next upgrade will break the deployment.

 

For deployments in compatibility mode in the Intelligent Advisor 8C release only, both the Web services - Assess option and the Web services - Interview option do the same thing. That is, selecting either option will deploy the policy model to all appropriate services in the Determination Server. To un-deploy from the Determinations Server you must uncheck both options. For later releases, the options will work as expected.

Note that it is recommended that deployments always use the latest product release unless warranted. Compatibility mode is only temporary, and either a patch must be deployed or the customer's policy models must be made compatible with the latest version of the runtime prior to the rollout of the next quarterly release.

Also note: Only policy models that have NOT yet been modified in any way by the latest version of Oracle Policy Modeling can be put into compatibility mode.

As described above, compatibility mode is intended as a temporary bridge after an upgrade, not as a long-term operating model, with this in mind be aware that compatibility mode will be automatically turned off when:

  • the next upgrade occurs
  • you activate a deployment version that requires the latest product release

 

Staying in compatibility mode permanently does not reduce upgrade risk. In practice, it can increase risk, because the deployment remains dependent on an older runtime path. If an issue occurs only while running in compatibility mode, Oracle's ability to fix it is more limited because that runtime represents the previous release rather than the current release line. The expected remediation path is normally to move the deployment forward to the current runtime, not to keep extending compatibility mode. For that reason compatibilty mode should not be treated as a way to remain one release behind indefinitely.


See:

 

 

 

 

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