Place Under Version Management Wizard
The wizard supports you when transferring a standalone model to the version management.
Purpose
Version management in the Administration Program always starts for a model with the provision of an initial model version. Multiple initial model versions can be created for a model, whereby versions can be provided for branches, for example.
Prerequisites
- A model in a repository with single sign-on must be selected in the Standalone Servers tab.
- A model rule for the selected model's repository needs to exist for the user.
- An agent must be running in the repository's INOPRJ directory.
- A version rule that enables the resulting model version to start must exist for the user.
Call
Select (Nicht definierte Variable:UIVar_AdmMenuCascades.MenuTabModelGrpNameVersionManagementVersionInit).
At the top, you can see the current step. As of the second step, a "Back" button (
) is active. You can use this to return to the previous step.
The middle shows the selection and input options.
The bottom contains the Next or Finish buttons and always Abort.
Step 1 of 4: Specify Position in the Hierarchy
How to proceed
-
In the Create as new model field, enter a name for the version, e.g. a version number.
The model name stays the same.
-
Activate the Add as model version radio button to insert the selected model into an existing version hierarchy as a model version.
- Select a model in the hierarchy to create a new model version at the topmost level.
- Select the new model version in the hierarchy to integrate it below a model version.
- The model name is changed to suit the selected model's name when creating the model version if this is different.
-
Click on Next to go to step 2.
Step 2 of 4: Version Name and Display Format
Context
It is possible to extend or replace the model name for the version name in managed models. You can use the $(model) and $(version) placeholders for the display; these will be resolved at runtime.
How to proceed
-
Enter a name for the version in the Version Name field.
Restriction
You can set name rules for a model version name of a managed model. The name must comply with the current name rule.
The version name can be changed later on.
-
Enter the $(model) and $(version) placeholders in the Display Format field to determine the display in the model editor.
Click on Next to go to step 3.
Step 3 of 4: Description
How to proceed
-
Enter a description for the version in the Description field.
The description can be changed later on.
Click on Next to go to step 4.
Step 4 of 4: Ready to Create the Model Version
How to proceed
-
Check the settings for creating the new model version.
- If you want to start the new model version straight away, then activate the Start the New Model Version check box.
- If you have converted the last model of a repository after several cycles, you can use the Stop the Original Model Server check box to automatically end the model server of the repository if necessary.
-
If everything is correct, click on Finish.
The model is created. This may take some time.
The tab jumps to Managed Models and the model version is selected.
