Migrate to the latest package

Version V1.1 (hereinafter referred to as V1.1) of the old package (UML/SysML Sample) and the latest version from the previous version of the current package We will explain how to migrate to this package in the following order.

• Prepare for package migration
• Migrate to the latest package

Prepare for package migration

If you modify and use the profile provided in the package, the following events may occur.

• Data migration function does not run
• Information on modified profiles will be lost.
• Some of the functionality provided by the package does not work
• The set value is updated with the default value

Before starting package migration, please check the following and perform the appropriate migration preparations. from V1.1 for migration from V1.1 or from V2.0 for migration from V2.0 Please check.

If you are deleting the imported "Modeling" package from V1.1

• Operation example
  • Have you ever deleted the package "Display name: Modeling, Name: Modeling"
    • Even if you add it again with the same name, it cannot be migrated because the internal management information is different.
• Phenomenon that occurs
  
  • Data migration function is not executed.
• How to deal with it
  
  • Please contact support.

When moving the imported "Modeling" package on the profile navigator from V1.1

• Operation example
  • The package "Display name: Modeling, Name: Modeling" has been moved from directly under the root package.
  • The package name of "Display name: Modeling, Name: Modeling" has been changed.
• Phenomenon that occurs
  
  • Data migration function is not executed.
• How to deal with it
  
  • Add the package "Display name: Modeling, Name: Modeling" directly under the root package.

If you are changing the view definition (form/shape etc.) from V1.1

• Operation example
  • Changed shape color
  • Added shape definition to diagram
  • Added existing fields to display on the form
• Phenomenon that occurs after migration
  
  • If you change the view definition defined in the UML/SysML profile, the information on the changed view definition will be lost.
• How to deal with it
  
  • If you need the changed information, please back it up and restore it manually after updating.
    

If you are adding attributes to the stereotype from V1.1

• Phenomenon that occurs after migration
  • If you are adding attributes to a stereotype class, the information about the added attributes will be lost.
• Workaround
  • If you need the added attribute information, please save it and restore it manually after updating.
    Note that if you have added attributes to classes other than stereotypes, the information will not be lost during the update.

If you are changing attributes such as class, field, or enum name/display name from V1.1

• Phenomenon that occurs after migration
  • If you have changed attributes such as class, field, or enumerated type name/display name defined in the UML/SysML profile, the changed information will be returned to the state before the change.
• Workaround
  • If you need attribute information such as the changed name/display name, please save it and restore it manually after updating.

Target attribute details

• class attributes
  • display name
  • name
  • Abstract class?
  • Inherited from
  • icon
  • Allow placement directly under the project
  • Allow model file splitting
  • field
  • View in model navigator
  • Display on trace page
  • Show differences when comparing differences
  • Exclude from search
  • Exclude from replacement
  • Constraints
  • Tagged value
• Field attributes
  • display name
  • Field name
  • Category
  • Show in finder
  • Show in inspector
  • Show differences when comparing differences
  • Tagged value
• Attributes specific to primitive type fields
  • initial value
  • Exclude from search
  • Exclude from replacement
• Attributes specific to class type fields
  • The number of data
  • Structure and save
• Enum attributes
  • display name
  • enumeration name
  • enumeration values
• Enumeration value attributes
  • display name
  • name
  • icon

If you are editing a class diagram for editing a metamodel from V1.1

• Operation example
  • Place notes and your own classes on the class diagram to edit the metamodel.
• Phenomenon that occurs after migration
  • Comments included in the class diagram for editing the metamodel and metamodel placement information will be lost, and the class diagram of the UML/SysML profile will return to its initial state.
• Workaround
  • If you need the edited information, please back it up and restore it manually after updating.

If you are deleting the imported "UML/SysML" package from V2.0

• Operation example
  • Have you ever deleted a package with "Display name: UML/SysML, Name: UMLSysML"
    • Even if you add it again with the same name, it cannot be migrated because the internal management information is different.
• Phenomenon that occurs
  
  • Data migration function is not executed.
• How to deal with it
  
  • Please contact support.

When moving the imported "UML/SysML" package on the profile navigator from V2.0

• Operation example
  • The package "Display name: UML/SysML, Name: UMLSysML" is moved from directly under the root package.
  • The package name of "Display name: UML/SysML, Name: UMLSysML" has been changed.
• Phenomenon that occurs
  
  • Data migration function is not executed.
• How to deal with it
  
  • Add the package "Display name: Modeling, Name: UML/SysML" directly under the root package.

If you have added a definition with the same name as a class or field added in the package after migrationfrom V1.1from V2.0

• Phenomenon that occurs after migration
  • Some of the features provided by the package may not work.
• Workaround
  • Also check the migration preparation for from V1.1. If applicable, take the corrective action before and after importing the profile.
  • After migrating to the latest package, please import the profile included in the package using the following steps.
    • [Next Design User's Manual > Profile Definition Guide > Profile Operation > Profile Update > Import Profile](../../../docs/profile-definition-guide/profile-operation/profile-update.md #Import profile)

If you have added a definition with the same name as the tagged value added in the package after migrationfrom V1.1from V2.0

• Phenomenon that occurs after migration
  • The value of the tagged value with the same name as the added tagged value is overwritten with True.
• Workaround
  • Please save the configured values ​​and restore them manually after updating.

If you are deleting a class, fieldfrom V1.1from V2.0

• Phenomenon that occurs after migration
  • If classes or fields are deleted [^1], some of the functionality provided by the package may not work.
• Workaround
  • Also check the migration preparation for from V1.1. If applicable, take the corrective action before and after importing the profile.
  • After migrating to the latest package, please import the profile included in the package using the following steps.
    • [Next Design User's Manual > Profile Definition Guide > Profile Operation > Profile Update > Import Profile](../../../docs/profile-definition-guide/profile-operation/profile-update.md #Import profile)

[^1] This phenomenon occurs because even if a deleted package, class, or field is added again with the same name, it is treated as a different package, class, or field.

If you are adding a definition with the same name as the view definition added in the package after migration from V1.1from V2.0

• Phenomenon that occurs after migration
  • A view definition with the same name is added, making it difficult to tell them apart.
• Workaround
  • Rename the view definition.
    Please note that if you rename the view definitions added in the migrated package, some functionality provided by the package may not work.

Migrate to the latest package

Migration from older packages and older versions of packages uses the update functionality provided by the latest packages.

Caution

• Some data will be reorganized during migration. Please back up your files in advance.

To use the update function, follow the steps below.

How to operate

1. Open the project in which the profile of the old package or version of the package was imported.
2. The Migrate Data to Latest Format dialog will appear. Press the [Yes] button in the dialog.
   
3. After a successful update, you can use the functions of this package by overwriting and saving the project and reopening it.
4. If you have taken any of the measures in Prepare for package migration, please perform the restoration work.

info

• The following prerequisites must be met to perform the update:
  
  • The license type must be one that allows profile editing.
  • If you are using Subversion integration, you must have permission to edit all files.

tip

• Updates can also be performed by pressing the [UML] > [Data] > [Migrate data to latest format] button from the ribbon.
  

tip

• For those who wish to continue using older packages or older versions of packages, it is possible to set the [Migrate data to latest format] dialog box not to be displayed when opening a project.
  • You can hide the Migrate Data to Latest Format dialog by going to the ribbon and unchecking the UML > Data > Ask for migration on every open checkbox.