Migrating from 11.2 to 11.3

Upgrade to 11.3 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.

Primefaces 13

tag-project-changed tag-project-auto-convert

We have update the Primefaces JSF library from version 11 to version 13. For details have a look at the Primefaces Migration Notes

Primefaces 13 Project Conversion

There is a new Project Conversion available that updates projects from Primefaces 11 to 13. The following is automatically converted:

  • Rename p:repeat to ui:repeat because p:repeat was removed

  • Style classes from PrimeFlex 2 to PrimeFlex 3

  • Stylesheet primeflex-2.min.css to primeflex-3.min.css

  • Add missing attributes layout="tabular" and columns="0" for component p:panelGrid

  • Method contentLength of class DefaultStreamedContent.Builder takes a Long argument instead of an Integer argument

  • Convert value of attribute height of tag p:textEditor from type Integer to String (e.g., 200 to 200px)

Chart

The component p:chart was removed. You have to manually migrate to Chart.js.

Miscellaneous

Beyond what is documented in the Primefaces Migration Notes we faced the following additional problems when we migrated projects:

  • p:selectItems with a value attribute of type List<SelectItem> and attributes var="filter" and itemLabel=#{filter} displays wrong labels. You can remove the attributes itemLabels and also itemValue as the SelectItem object already defines the label and value of the items.

  • p:commandButton with an ajax="false" attribute sometimes does not work in p:confirmDialog. You can remove the ajax attribute since AJAX should work now in p:confirmDialog.

Removal of system database Conversion

tag-ops-changed

It is no longer possible to convert only the system database. Engine migrations must now always be carried out via the Engine Migration Wizard.

Therefore, the button to convert the system database from the Engine Cockpit was removed. Furthermore, the Engine Config CLI command to convert the system database is gone. As a replacement, you can trigger the Engine Migration command migrate-engine.

In addition, the autoConvert configuration from ivy.yaml no longer works. An engine migration must be carried out manually via the Migration Wizard or Engine Config CLI tool.

Legacy app.yaml in application zip

tag-ops-changed

With Axon Ivy 10.0 it is not only possible to deploy an app.yaml with an application zip, but an entire configuration folder called config. In this case the app.yaml should be placed in the config sub folder as part of the application zip. With Axon Ivy 10.0 we still support the old location of the app.yaml (with a warning message in the log), but with Axon Ivy 11.3 this is no longer possible. The app.yaml must now be placed in the config sub-folder of the application zip.

Data.WorkDirectory no longer configurable in ivy.yaml

tag-ops-changed

The Data.WorkDirectory is the temporary directory which Axon Ivy will use to create files. Data.WorkDirectory can no longer be configured in ivy.yaml. You need to configure it in jvm.options as ivy.Data.WorkDirectory. Or as operation system environment variable IVY_DATA_WORKDIRECTORY.

Tag Legend:

tag-ops-wizard

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

tag-ops-changed

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.

tag-ops-deprecated

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.

tag-ops-removed

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.

tag-project-auto-convert

This migration is handled by the Project Conversion automatically.

tag-project-changed

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

tag-project-deprecated

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.

tag-project-removed

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