When the plugin executes it creates the model and then stores it into Mauro. It would be helpful to check the parameters are valid to avoind creating a model which can't be stored e.g. the scenarios mentioned on the UI:
Should the Model/s be imported as new Branch Version/s. If selected then the latest finalised model with the same name will be chosen as the base. If not selected then the 'Model Name' field should be used to ensure the imported Model is uniquely named, otherwise you could get an error.
Should the Model/s be imported as new Documentation Version/s. If selected then any models with the same name will be superseded and the imported models will be given the latest documentation version of the existing Models. If not selected then the 'Model Name' field should be used to ensure the imported Model is uniquely named, otherwise you could get an error.
Name for the branch if importing as new branch model version. Default if not provided is "main". Each branch from a finalised model must have a unique name. If the branch name already exists then the model will not be imported.
In addition, the version number should be generated and populated / validated ahead of storing to avoid the error when a finalised version has no version number.
When the plugin executes it creates the model and then stores it into Mauro. It would be helpful to check the parameters are valid to avoind creating a model which can't be stored e.g. the scenarios mentioned on the UI:
In addition, the version number should be generated and populated / validated ahead of storing to avoid the error when a finalised version has no version number.