Skip to main content

V2.3

The package has been updated with the upgrade to Next Design V4.0.

Fixed issues and restrictions​

  • Fixed an issue where the change in the type of the association end displayed in the sub-editor was not immediately reflected when changing the association connector between classes in the class diagram of the UmlSysml package.
  • The new extension does not support operation with project data of the old package (UML/SysML Sample).
    If you want to operate with the new extension, please migrate the old version using the old extension once.
  • The old version profile in the current package does not support operation in reference format. If you want to operate in reference format, please perform the conversion according to the following procedure.
  • Conversion procedure
  • Use the update function to convert the V2.0 profile included in the copy format in the currently used project to the V2.1 profile.
  • Use the profile included in this version to convert to the reference format.
  • From the profile change list, undo the changes to "Trigger related" and "Trigger related bend position" under the class diagram "StateMachines" at the position of "UML/SysML.UML.Behaviors.StateMachines".
  • This step is necessary because the update function from V2.0 to V2.1 does not incorporate the changes on the class diagram included in the V2.1 profile, and they are treated as differences from the base profile when converting to the V2.1 profile.
  • If you convert the V2.0 profile to the reference format, you cannot use the update function of the UmlSysml package, and it will be mistakenly assumed that you are using the latest version.
  • In addition, the procedure for updating to the profile included in this version using the profile update function of the main unit is not guaranteed to work.
  • If some classes and fields are disabled for UML/SysML profile references, it may not function as intended.
  • For example, Next Design itself treats a class/field as invalid, but the UmlSysml package may display invalid information.
  • When multiple UML/SysML profiles are added, the Model Navigator will display a set of classes that can be placed directly under the project, for the number of profiles added.
  • We recommend that you customize the "Allow placement directly under project" setting or change the display name to make it easier to distinguish between options.
  • In the UmlSysml package, the connector shape definition for tree diagrams is now displayed in the profile navigator.
  • The name and display name of the connector shape definition for tree diagrams have been changed.
  • In the English version of the UmlSysml package, the display name of the related class for the connector shape of tree diagrams has been changed.
  • In the English version of the UmlSysml package, the display name of "Requirement ID" has been unified to "Requirement ID".
  • The column width has been adjusted because the column headers of forms and tree grids became cut off due to the change in the display name.
Last updated on