•
|
You generally want to avoid saving a new version of the model opened in the COMSOL Desktop from the Model Manager workspace. Otherwise you will get Save Conflicts when trying to save a new version of the desktop model.
|
Creating a New Branch does not save new versions of the items included on the new branch — each item version on the new branch is initially the same as that on the parent branch.
|
1
|
Write the new title for the item in the Title field.
|
2
|
Write an optional comment in the Comments field.
|
3
|
Click OK to save the renamed item as a new version in the database.
|
1
|
Write an optional comment in the Comments field.
|
2
|
Click OK to perform the restore.
|
The target item when restoring a version in The Versions Window is given by the item whose version history is currently shown, which may not be the same item that the selected version belongs to. For example, restoring from a selected version of a regular model via the version history of a draft, with the draft created from that regular model, saves a new latest version of the draft.
|
•
|
You have created a draft from a model and then saved ten versions of that draft. By the tenth version, you realize that the modeling setup has gone wrong for the draft, and that things started to go bad by version four. Solved by restoring version three from The Versions Window such that a version eleven, identical to version three, is saved directly in the database.
|
•
|
You have decided to save what you, initially, think is a finished draft back to its original model. Such an action simultaneously saves a new version of the original model and deletes the draft. You then realize that you did this too soon — there were more things you wanted to first change in the draft. Solved by reverting the commit in which the draft was saved back to the original model from The Commits Window: the draft is added back to the branch and the model is updated to its previous version before it was overwritten by the draft.
|