Updating an Axon Ivy Engine on the LTS 10 line almost always works (example 10.0.13 > 10.0.14) without any manual adjustments both in the Axon Ivy Projects and in the configuration of the Axon Ivy Engine 😎. We invest a lot of time to be backward compatible so that you can always be on the latest update release, which always fixes bugs, improves performance and closes security gaps.
It is important that you regularly update your engines to the latest version! If you discover any incompatibilities, please let us know!
P.S: If you are running your engine in a container environment such as Docker, all you have to do is increase the version number and restart the engine 🐳.
But be careful if you are using the Axon Ivy Portal. The portal version should always correspond to the version of the Axon Ivy Engine. Usually, the portal also works with newer versions of the engine, but this does not necessarily have to be the case (e.g. there is a minor issue when using this combination Engine 10.0.13 x Portal 10.0.11).
When upgrading the portal, you must take the migration notes of the portal on the 10.0 line into account:
Especially 10.0.11 to 10.0.12 can be a tricky one. The extension mechanism of some features has been changed and are no longer supported as overrides, you need to implement this as sub processes.