Backward Compatibility for Model Manager

When COMSOL Multiphysics connects to a local Model Manager database created using an older COMSOL Multiphysics version, the database will be automatically upgraded to support any functionality added in the newer version. This upgrade does not modify the storage format of models and data files, however, so older versions of COMSOL Multiphysics will still be able to load models and data files from the database even after this upgrade — an important use case when you, for example, need to recompute a database-stored model using the exact same version of COMSOL Multiphysics the model was initially solved in.

Models saved in a Model Manager database have the same version requirement constraint as models stored as MPH-files on the file system: a model saved to a Model Manager database from a newer version of COMSOL Multiphysics cannot be opened from an older version of COMSOL Multiphysics.

When you connect from a newer version of COMSOL Multiphysics to a server database hosted by an older version of Model Manager server, the Model Manager server will not be aware of any newer functionality supported by COMSOL Multiphysics. In this case, such functionality will either be hidden or disabled in the COMSOL Desktop environment.

The opposite case is similar: When you connect from an older version of COMSOL Multiphysics to a server database hosted by a newer version of Model Manager server, you will not have access to all functionality supported by the newer server from the COMSOL Desktop environment. Same as for local databases, you will still be able to load older models and data files from the server database though.