Update Configuration Dialog

Purpose

When migrating a full model into the current Innovator version, you must update basic configuration profiles at the very least so that you can use the new options in the model. New configuration options are not automatically added to the migrated models. You can also update application configurations when a full migration is carried out.

You can only use migration files in $INODIR/config/ when updating the model configuration and application configurations.

The dialog contains information about the application configurations, the model's imported profiles and migration files available through the transformation.

The applicable migration files are marked when an application configuration or profile are selected. You many need to install on-demand packages to update profiles which do not mark a file.

Prerequisites

You require model administrator rights.

Call

This dialog appears in the model editor when you run the Model>Administrative Tasks>Update Configuration command.

Structure

Important information about interpretation of the display can be found at the top.

Three sections are shown in the middle.

• Profiles and Application Configurations of the Model

  The left-hand list shows the state of the profiles with regard to the possible update.

  Icons differentiate profiles and application configurations:

  Profiles

  Application Configurations

  When a profile is selected, the migration files which contain it are marked. The first migration file containing the profile is expanded. You many need to install on-demand packages to update profiles which do not mark a file.

  Configuration states:

   Migrateable
  Profiles marked orange can be updated without any problems.

   Modified
  Profiles marked red contain changes which would be lost upon the update.

   Problematic
  The profile needs to be repaired and should be checked.

   Up to date,  Own,  Obsolete
  Updates do not exist for profiles marked in different colors. When migration files are imported, profiles which can be migrated may no longer be required as their content was distributed to other profiles. They are marked as Out-of-date.

• Migration Files

  Migration files are sorted according to relevance. Import conflict-free migration files from top to bottom. Migration files towards the bottom are often no longer required as they have already been covered by a migration file at the top.

  No conflict

  This file contains updates for your profiles. It can be imported with no issues.

  Conflictive

  Changes you have made have been deleted in this file's import. Move your changes to a customization profile so that you can import this update with no issues.

  Up to date

  The content of this file corresponds to the state in your model. Import would not make any changes.

  Not required

  This file contains updates for profiles which are not available in the model. Therefore, it cannot be imported. If you want to use these profiles, please load the respective add-on.

• Details

  Selected migration file, its type and status.

The bottom contains the Delete Obsolete Profiles and Import Migration File buttons and the Close default button.

• Delete Obsolete Profiles

  When migration files are imported, profiles which can be migrated may no longer be required as their content was distributed to other profiles. These and their dependencies can be cleaned up using this button. It is very difficult to delete profiles in the configuration editor due to existing profile imports.

• Import Migration File

  The selected migration file is imported. The file and the profiles and application configurations contained are then marked as up-to-date. Other migration files may also be marked as up-to-date if the profiles modified by the current import only had one difference in them.

How to Proceed

The left-hand list shows the state of your profiles and application conigurations with regard to the possible update.

First, import the conflict-free migration files step-by-step from top to bottom.

Importing migration files may change the state of other profiles due to updates which may occur.

Special measures may be necessary in two exceptional cases.

1. Profiles marked red

   These profiles were included within the scope of delivery by MID and have been modified by you. These changes would be lost upon update.

   To update these profiles, you need to check-out these changes into customer-specific extension profiles (customization profiles). You can import the customization profile into the MID profile so that your changes will be available. You can then update the fixed MID profile.

   To identify your changes, it may be helpful to e.g. compare model configurations of a model with the modified profile and a model with the profile from the current installation in the Align Models editor. You can compare the profiles to identify your own changes if you have the Configure privilege and are in the Compare mode in this editor.

2. Problematic profiles

   These profiles are in an unexpected state and need to be checked. Search for placeholders in the configuration editor and use the verifications available in the configuration editor.

Then delete the obsolete profiles.