The Batch,
Batch Sweep,
Cluster Computing, and
Cluster Sweep study nodes can now be configured to use models and data stored in a Model Manager database. You enable database storage for a study node by selecting
Database in the
Model storage and
Data storage lists in the
Settings window.
New methods have been added to DatabaseApi for accessing the corresponding database, repository, branch, and latest version given a model or file location URI for a specific model or file version. For example,
You can test for the existence of items and item versions in a database via new exists methods added to, for example,
ModelItem,
ModelItemVersion, and
BranchModelItem. This is useful when, for example, you want to test if the version corresponding to a model location URI has been permanently deleted in the database before proceeding with other logic:
A new input parameter type, TargetFileResourceParam, has been added, enabling you to perform a partial update of file resources belonging to a fileset version of a file item. Two examples of updates you might make and the methods you would use include:
A new SAVED_IN enumeration value for sorting on the COMSOL Multiphysics version that a model was saved in has been added to
ItemSortField.
The target item may now be absent from the database when providing an item key via SaveItemParam.targetItemKey(). Instead, a new item is created as long as necessary source data for field values and item contents is available via other input parameters. The same holds true when invoking
BranchModelItem.update(...) when the model item is absent (as well as for file items and tag items).
The COMPUTEDDATA constant in
ItemSortField and the
INPUTFILE,
OUTPUTFILE, and
GEOMETRYPART constants in
ItemVersionReferenceType have been deprecated. Their replacement constants are found in the same enum types.