Migrating from 11.1 to 11.2

Upgrade to 11.2 is only supported from an Axon Ivy Engine 8.0 and higher. If you have an Axon Ivy Engine older than version 8.0 you need first to migrate to a newer version.

Mail Notifications

The notification concept has been completely revised and standardized so that notifications can be sent via different channels. Read more about this here. Here are the most important changes:

Mail notifications can no longer be customized via custom mail standard processes. There is a templating concept for this. You may have used a custom mail process to suppress notifications. This can now be done directly in the process with Suppress Notification.
There is still a notification for a new task assignment. There is no longer a daily task summary mail.
In addition to the mail channel, there is also a web and Microsoft Teams channel.
If a user has manually enabled new task notification mails, this setting will be automatically migrated. However, the mail channel is disabled by default and needs to be enabled so that users get new task notification mails in the engine cockpit.

Application Path

With Axon Ivy 7.0 and earlier you were able to define the installation path of an application. The Admin UI allowed this input on the wizard to create a new application. This path was stored in the Axon Ivy System Database (IWA_Application.FileDirectory). Since Axon Ivy 8.0, new applications will be stored under the configurable path Data.AppDirectory in ivy.yaml which points by default to applications.

We now have removed the legacy support for IWA_Application.FilePath. If some applications were created with Axon 7.0 or earlier, you need to move them manually to the Data.AppDirectory location.

WebPage activity

The WebPage activity process element is no longer supported.

It will be automatically removed from existing processes where it has been present.

In most cases it can be replaced with normal HTML Dialogs.

Preference pages

The Email and SSL preference pages to set engine settings during development have been removed from the Designer. In older version they were accessible under the menu: Ẁindow > Preferences > Axon Ivy.

As a replacement, the Engine-Cockpit is now shipped with the Designer. The Engine-Cockpit can be reached by clicking on the ‘gear wheel’ icon on top of the included Web-Browser.

Within you can open the System Configuration and filter for Mail to inspect and set configurable values. Furthermore, there is a new view to define your SSL Settings.

Programed elements

Streamlined config access

Editable Program Start, Intermediate Wait and Program Activity bean implementors have to adjust code in order to keep the Editor inscription functional.

Namely we have deprecated the methods to read and write configuration within the Editor implementation. It is no longer the Editor implementors responsibility, to maintain the element configuration values. Therefore implementors can remove overwritten methods to read and write configurations, but must instead link their UI widgets, to the configuration field by passing its name as input. You can adapt this change from our Example Migration .

Furthermore, the bean runtime should be adapted, to use the new initialize(IProcessStartEventBeanRuntime runtime, ProgramConfig config) method. Configuration parameter values can then be consumed at runtime from the new getConfig(String) APIs.

Until your editable beans are migrated, the old configurations are still functional at runtime. Note though, that Inscription Editors won’t work correctly, until you migrated your API calls to the latest ExtensionUiBuilder.

AutoProcessStarterEventBean

The process start event bean ch.ivyteam.ivy.process.eventstart.beans.AutoProcessStarterEventBean has been deprecated. Instead use the new ch.ivyteam.ivy.process.eventstart.beans.TimerBean.

Tag Legend:

This migration is handled either by the Migration Wizard. The wizard will interact with you if you are affected by this change.

This migration will change something in the engine operation. If you are responsible for the operation of an engine, check if this change affects you.

This migration highlights behaviors or features that are deprecated. That functionality will be removed soon. If you are responsible for the operation of an engine, you should check if this change affects you.

This migration will remove a behavior or feature that has been available for the engine operation. If you are responsible for the operation of an engine, check if this change affects you.

This migration is handled by the Project Conversion automatically.

This migration will change a certain behavior in the projects. If you are a project developer, check if this change affects you.

This migration will mark features or APIs as deprecated in projects. That functionality will be removed soon. If you are a project developer, check if this change affects you.

This migration will remove a behavior or feature of a project. If you are a project developer, check if this change affects you.