This program corrects the following problems/limitations so that you can use the application with more stable quality.

Fixed Issues and Constraints

Model Editing

• Fixed a problem in which the project could not be opened if a manual shape representing the same model was under another shape, the manual shape directly under the diagram was moved (re-parented) to another shape, and then undone, saved, and closed.
• Issue where images copied from a Web browser could not be pasted into a shape has been resolved.
• Fixed a problem in PowerPoint where copying a text shape and pasting it into a shape would cause the shape to become transparent.
• When duplicating a reference source model with the tree grid displaying the reference destination model in the editor, a problem was resolved where two reference destination models were displayed below the duplicated model.
• When only models in an inverse reference relationship can be added as child nodes in the tree grid, the [+] button on the operation panel is enabled when a child node is selected, and a system error occurs when the button is pressed.
• When a shape is defined in a tree diagram with the target field as the source and the data type as the target itself, adding a child element with the [Insert] key solves the problem of selecting a metaclass for which no view definition exists.
• The order of multiple elements cut and pasted in a tree grid or form grid was sometimes reversed.
• When multiple elements are selected and moved or resized in a sequence diagram, the undo operation cannot be undone in a single undo operation.
• Fixed a problem in which some style information (e.g., title text style for simple shapes) was not maintained when diagram shapes were copied.

Model editing (rich text)

• The problem of equal alignment in rich text when justification is specified has been resolved.
• When a Word table is copied and pasted into rich text, the table width expands to the entire width of the rich text.
• Solved a problem in which, if the column headers of a rich text table are cell-joined, changing the column width would not result in the changed column width after the edit is finalized.
• FIXED A PROBLEM IN WHICH CERTAIN OPERATIONS ON RICH TEXT COULD RESULT IN UNDERLINED LINE FORMATTING, WHICH COULD CAUSE A SYSTEM ERROR OR FORCE ND TO TERMINATE IF EDITING WAS PERFORMED IN THIS STATE.
• WHEN A SUPERSCRIPT IS ENTERED IN RICH TEXT AND THEN OUTPUT AS AN HTML DOCUMENT, THE SUPERSCRIPT OVERLAPS WITH THE PREVIOUS LINE AND THE BOTTOM OF THE PREVIOUS LINE IS HIDDEN FROM VIEW.
• In rich text in the document form grid, a problem has been resolved where the height of a line would be displayed two lines high if only one line of text was entered and the view was switched.
• In rich text on the document form, a problem was resolved where a single-byte space would be entered when all characters entered were deleted and the edit was immediately confirmed by pressing the Enter key.
• In rich text on document forms, when editing is started with nothing entered and the [Esc] key is pressed to cancel editing while text is being entered, a single-byte space is entered.
• Fixed a problem that caused the "(Unset)" status when all contents in the rich text box of a document form were deleted and the [Esc] key was pressed.
• Fixed a problem in which the paragraph settings (left-align, center-align, right-align) for tables in rich text were not reflected in the output of document output and were displayed as left-aligned.
• Fixed a problem in which selecting and deleting a table and the text line above one of the tables would delete the text line that was not selected when there were two or more text lines (line breaks) above the table and the table in the rich text by pressing [Shift]+[Enter].
• When scrolling with the mouse wheel so that rich text fits within the screen, the mouse wheel would sometimes scroll up a little and then back down, preventing the text from scrolling up.
• When using Microsoft IME in Rich Text, the issue where Japanese input could not be performed correctly depending on the version of Windows 10 has been resolved.
• Solved a problem in which the bullet symbols displayed in Word were different from those displayed in NextDesign when rich text containing bullets was pasted into Word.
• When using GoogleIME with rich text, problems such as underlines being set and text not being inputted have been resolved.
• Fixed a problem with rich text that caused the display to collapse when bullets were set to reverse indentation.
• A problem with nested tables overflowing cells within rich text table cells has been resolved.
• Fixed a problem in rich text where justification would not work unless [Shift]+[Enter] was pressed to break a line.
• When a hyperlink is inserted into a rich text paragraph, an unintended character is added to the beginning of the hyperlink text.
• Problem solved where tables inserted in rich text could not be moved to the end.
• When inserting a hyperlink to rich text, the problem of selected images or tables disappearing when they are selected has been resolved.
• When inserting images into rich text, the problem of being able to select non-image files has been resolved.
• Fixed a problem with garbled characters when changing to a specific font in rich text.
• Fixed a problem in which the second line would not be displayed in the document form grid when two lines of rich text were entered.
• Fixed a problem in which the " " would sometimes disappear when converted after Japanese input in Rich Text and then converted after Japanese input again after entering " ".
• When editing rich text with a large amount of input, a problem with poor response to keystrokes and input delays has been resolved.
• A problem has been resolved where underlining formatting would remain set after certain operations in rich text.
• When rich text with superscripts created in NextDesign V3 or earlier is output as an HTML document, the bottom of the immediately preceding line is no longer hidden.

traceability

• The problem of time-consuming switching to the tracing page on large projects has been resolved.
• The problem of time-consuming element selection, expansion/compression, and scrolling in the trace tree on large projects has been resolved.
• The problem of time-consuming switching of trace settings on large projects has been eliminated.
• A problem that took a long time to add, delete, and move (reorder) tracing lanes in large projects has been resolved.
• Resizing the window while the trace view is displayed hides all trace lines.
• Solved a problem in which "Show in Editor" in the context menu of a cell was always disabled when the trace view was displayed in "Matrix" format and "Expand All" was executed from the context menu of a column or row.
• When a model that is a series in the trace tree is deleted and then the trace view is displayed, the deleted model remains visible.
• When a traceability report is output after deleting a model that is a series in the trace tree and then displaying the trace view, the problem of the deleted model also being output in the report has been resolved.
• Solved a problem that caused a system error when outputting a traceability report when the element that is the base of the trace series in the trace view is an "unknown element".
• The message "The displayed contents may not be up-to-date. message was displayed in the trace view, selecting the currently displayed trace setting would only clear the message and not update the displayed content.
• Fixed a problem in which after adding trace settings, the order of the added trace settings would change, even though the trace settings information was merged with a branch that had not been edited.

Profile Definition

• When a class defines two or more owning fields, a system error would occur if the owning field was deleted using "Delete Ownership" and then the owning field name in the same class was changed to the same name as the deleted owning field.
• When reopening a project after reordering metamodels in the Profile Navigator, the metamodel was reordered in the order of (1) class, (2) related class, and (3) enumerated type.
• Solved a problem in which reordering fields in the Profile Navigator and reopening the project would result in the sorting of (1) owned fields and (2) reference fields, in that order.
• If the parent of an entity on a class diagram is changed while the profile is changed, and the change is undone, when the project is saved and reopened, the parent of the entity on the class diagram is in the state it was in before the undo was done.
• The TopElementId of the exported profile file is now different when the profile is split or not.
• Solved a problem in which the class names of interaction element classes (lifelines, messages, etc.) were changed when a profile whose interaction class parent was changed was reimported.
• Fixed a problem in which changing the [Name] of an enumeration literal would cause the field with that value set to revert to its initial value.

Team Development

• After splitting a model into files for the first time, if the "Keep editing" checkbox was unchecked in the Configuration Management Navigator and a commit was performed, the model could be edited and could not be saved.

Document Output

• WHEN A RICH TEXT TABLE IS OUTPUT AS A DOCUMENT IN HTML FORMAT, THE LEFT AND RIGHT PADDINGS IN THE CELLS ARE NOW WIDER.
• Solved the problem of wide line spacing when rich text, including bullets, created with Next Design before V3.x is output as a Word document.
• Fixed a problem in which copying and pasting entire rows of an Excel file into a grid control field on a form and then outputting the document would result in a different font than the one displayed in Next Design.

Extensions

• SetRichTextField() to set html format values to rich text fields, the problem of displaying text strings that were approximately two lines high and leaned toward the top has been resolved.

• Solved a problem where, when pasting into Word by executing the context menu [Copy] with the rich text field set to a value in html format only with IModel.SetRichTextField(), the text was not pasted and the user did not notice the cause of the problem.

• If an assembly is registered in a shared library and an extension references a newer version of the same assembly, the problem of loading the version of the library registered in the shared library at runtime has been resolved.

• Solved a problem in which the assembly used by an extension depended on the loading status of the assembly of Next Design when the extension references the same assembly that is bundled with the main body of Next Design.

• Solved a problem in which continuous execution of the following APIs in a script would cause Next Design to forcefully terminate or display an out-of-memory dialog box, preventing the script from continuing operation.

  • IApplication.ExecuteScript()
  • IApplication.ExecuteScriptCode()

• A system error would occur when trying to add a model to a manual shape view definition in an ER diagram using D&D operations while the ModelCreationProvider of EditingCapability is registered.

• Fixed a problem that caused a system error when selecting a model in the Model Navigator if the ModelCreationProvider in EditingCapability returned the results of processing CapabilityResults.Fail.

• Fixed a problem that prevented the inspector from displaying the results of CapabilityResults.Fail when the ModelEditorSelectionProvider of EditingCapability returned the results of CapabilityResults.Fail.

• When displaying the Manage Extensions dialog without any extensions installed, the message "This version cannot be installed because it is not supported. is now displayed.

• Fixed the decision on whether or not the maxVer specified for a package can be installed. As an example, a package can be installed even if the maxVer of the package is 3.1 and the application version is 3.1.2.30616.

• Solved a problem in which an extension that did not specify a shared library could have an inconsistency with the version of the library expected by the extension when using a library specified as a shared library by another extension.

Applications in general

• Solved a problem in which continuous execution of scripts would cause Next Design to forcefully terminate or display an out-of-memory dialog box, preventing continued operation.
• The problem that the appearance of the dialog informing the user that he/she cannot edit a profile because he/she does not have the authority to do so was not consistent with other dialogs has been resolved.
• Solved a problem where an error message when a large project could not be opened due to lack of memory did not indicate that lack of memory was the cause.
• When multiple elements are selected in the Model Navigator and Product Line Navigator and the [alt+up][alt+down] keys are pressed, the order could not be moved between sibling nodes.
• Fixed a problem that caused the project to go into a dirty state if a field was placed in edit state in the inspector and the value was left unchanged and then confirmed or the edit was canceled.
• Fixed a problem in which pressing the [esc] key while displaying the read-only dialog or the Edit Feature Expression dialog would not close the dialog.
• The dialog that appears when splitting or merging model files has been fixed.
• Fixed a problem in which a separator line would appear at the beginning of a model when "Add Model" was selected from the Model Navigator context menu while no new model was available for creation.
• The offline license registration and de-registration dialog is now in Japanese, rather than English, making it difficult for English speakers to understand the procedure.

Extended Contents

UML/SysML Package

• In class diagrams of UML/SysML packages, when related connectors between classes were replaced, changes in the type of related ends displayed in the subeditor were not immediately reflected.

NDGit

• When selecting a modified file displayed in the Git Navigator and clicking the context menu [Show Changes], the mouse cursor does not turn into an hourglass and it is not clear whether the operation was accepted or not.
• When resolving conflicts in files with different major versions, an error occurred when trying to apply a file by specifying the direction to apply it in the conflict list, and the problem could not be solved.

EAIntegration

• When importing EA collaboration in some environments where Enterprise Architect is installed, an error message "The specified file cannot be found. error occurred when importing EA collaboration in some environments where Enterprise Architect is installed.

EnhancedErrorChecker

• In a project where a partially loaded model file had a model with no parent and inconsistencies occurred, a system error occurred when performing model validation.

ExtensionPoints Library

• Problem with ExtensionPoint not building ribbons correctly has been resolved.

That is all.