Another situation occurs if users have saved their models as model files for Java®. The change you made in the interface can then break that model file for Java, so the user cannot execute it. It is possible to define migration for this as well, so generated files can execute although they contain Java code in an old syntax. This procedure is referred to as compatibility for the Model Object API. Generally, API migration is more complex to handle, and there are situations when you cannot avoid breaking old model files for Java.

For the most common operations that do require migration, you automatically get the proper migration operation included under the last version. This only works if there is a version when you did the change. There can be occasions when you do not want to register a migration operation for every change you do. To turn off the automatic migration, click the Migration node and then clear the Add migration operations automatically check box in the Migration settings section.

The nodes for the migration operations appear in a Version under Building Blocks and under the following container nodes: Components, Properties, and Features.