Model Versions

The Administration Program displays e.g. information about the status and log file for the model versions and enables the editing of some properties for model versions.

Purpose

If a model version with the same Innovator version as the administration program is selected in the Managed Models tab, information about the model version appears in the right-hand area or some of the properties are offered for editing. You can switch between these two views.

Prerequisites

You require a version rule when editing properties.

Structure

The information area consists of the following expandable sections and further elements for model versions, depending on the view.

* This information is only shown for active model versions.

Information View

This view displays properties of the selected model version.

  • Status

    The following information is shown as the status for the model version: name, directory, path, INOHOST*, host name*, IP address*, process ID*, port*, user* and purpose*.

  • Version

    The following information is shown as the version for the model version: version name, creation details, start details* and description.

  • Innovator Links*

    You can see the link name for the model version the Innovator link log can be accessed via.

    The link name used for creating links when copying and for generating documents in this model version is shown as default.

  • Update*

    The Innovator security concept consists of manual and automatic repository updates. The settings for the time interval and automatic update times are displayed here.

  • Inactivity*

    The settings for automatic logout if users are inactive are displayed.

    This function allows e.g. model elements that are locked for exclusive editing by inactive users to be released and model versions that are no longer being edited to be automatically closed.

  • Change Logging*

    Displays the change logging status.

    Change logging is configured in the Administrative Tasks backstage view.

  • Languages

    Display the model language and active display language.

  • Roles And Privileges*

    Display of roles and corresponding assigned privileges in the model.

    The roles and privileges are edited in the configuration program under Configuration>Model Administration>Manage Users....

  • Logins*

    Overview of the current logins to the model with the relevant user name, name in the system and computer name.

  • Resources

    Enter the RAM and hard disk space used.

  • Log File

    Displays the log file of the current model version and allows the saving of the file.

Properties View

This view allows the editing of some model version properties.

Properties can only be edited with a suitable version rule.

The backup's properties cannot be edited.

  • Version

    You can change the version name. This might be necessary, e.g. after moving in the hierarchy.

    You can change the version description.

  • Innovator Links

    If you want to use hyperlinks to Innovator elements in external documents or enable return to the model from HTML documentation, then these links lead to a concrete model. If you work with model versions, then you may wish to make these links lead to a different version than previously used. You can use link names to do this.

    You can see part of the link for the Innovator log you can replace in the Physical field; the link is made up repository name, model type and model name.

    You can enter link names which can be used to access model versions via the Innovator link log.

    The link name selected as default is used for copying elements and documentation generation when creating links.

    If there are multiple models with the same link name, then a selection dialog appears which lists the model names and version identification.

  • Languages

    Select the model language and active display language.

    Select the language which the model should be created in as model language. All model elements are assigned a name in the model language. Model templates are provided by Innovator in German and English.

    Attention

    Changing the model language is only appropriate when starting modeling, so that you can use language-specific word wrapping in diagrams and spell check in specification texts.

    Making changes at a later stage will mean that you will have to manually rename numerous model elements and may need to retranslate profile and metamodel content.

    It is also possible to use one of the active display languages for presentation and documentation purposes instead of the model language. Spell check in Specification texts and wraps in all the model's diagrams are made based on the model language or an alternative display language. The current respective display language is also used for language-specific exports.

    The Available languages list contains the languages that are not yet used in the model. You can use the Add » button to add languages to the Active languages list. Multiple selection is possible.

    The Active languages list contains the languages that are available in the model. You can sort this list using the arrow buttons or with the mouse. The same order is found in the drop-down listsfor the languages to be used. You can use the Remove button to remove languages from the model again. Multiple selection is possible.

    Attention

    If you remove an active alternative language, then all existing labels in this language are deleted.

    Display languages can also be activated in the Manage Languages backstage view.

  • Change Logging

    Make settings for change logging.

    • Activate change logging check box

      Activates or deactivates change logging.

    • Show backstage view 'Change Sets' check box

      If options are set, then changes are logged but change sets for users and the Change Sets backstage view are not displayed.

      Change logging without visible change sets is a good idea if you want to be able to trace model changes (e.g. for merging models) but the user does not want to use change logs for logging work orders.

    • Make change log anonymous check box

      When this option is set, the user name will not be visible in change sets. The history of elements shows change sets.

    • Maximum storage time input field

      Concerns all terminated change sets. 0 means unlimited. On reaching the specified age, a change set will be deleted, provided it is terminated.

  • Update

    You can enter a positive integer between 1 and 1440 (24 hours) into the Interval (min) field as the time interval for the automatic data update. Enter zero if you do not want to implement any regular updates.

    You can enter the times for the automatic data update in the format HHMM (hours and minutes) in the Times field. You can specify several different times by separating the entries using commas (e.g., 0900 1200, 1500, 1800). You can leave the field blank if you do not want to implement any updates at fixed times.

    Upon creation of an update, all changes to the repository are successively stored in a telegram model; this file and the stored repository enable a repository that has crashed to be restored.

    Note

    Make sure that not all repositories are backed-up at the same time in order not to overload the system as this can lead to drastically increased response times.

  • Inactivity

    Define the time criterion for the recognition of inactive users in order to release model elements locked for exclusive editing, for example.

    You can set a time limit in minutes for a user's inactivity where they have not been active in the model server. The time frame must be at least 10 minutes. 0 deactivates this mechanism.

    You can use the Automatically log out inactive users check box if you want such users to be logged-out. You can log-out inactive users at any time using the Log Off Inactive Users context command.

    You can set a time frame in hours in which users cannot cause any activity in the model in the Shutdown model after (h) field. The model version is then automatically closed. 0 deactivates this mechanism.

  • Logins

    You can prevent users logging-in so that you can carry out administrative tasks. You can inform them about the reason for login prevention. You can then permit the users to login again.

  • Apply button

    Modified properties only take effect when confirmed with the Apply button.

  • Discard button

    Modified properties are reset.