In addition to the Next Design installation folder, there is now a new folder where extensions can be placed with user rights to add files. For details, please refer to the next page of the Extension Development Manual.
Extension Development Manual > Development Guide > Common > Extension Distribution
IN ORDER TO USE A PROJECT CREATED WITH V1.0 WITH V1.1, THE MEASURES DESCRIBED IN THE FOLLOWING NOTES ARE REQUIRED.
Sequence diagrams are preview versions and are subject to the following functional limitations
The following elements cannot be described in a sequence diagram
The following functions are not available for sequence diagrams
IN A COMPOSITE FRAGMENT OF A SEQUENCE DIAGRAM, STYLE SETTINGS OTHER THAN TEXT COLOR CANNOT BE CHANGED. (THE INSPECTOR DISPLAYS A UI FOR THE STYLE SETTINGS, BUT YOU CANNOT CHANGE THEM.)
If you nest compound fragments in a sequence diagram and the child compound fragment contains a message, the error checker will display a multiplicity violation warning for the message in question in the error list. Please skip this warning as it does not affect the model, or eliminate the nesting of the composite fragments.
In the tree format of the trace page, some of the compressed and expanded nodes may not be highlighted during the highlighting process when a node is selected.
To highlight it correctly, re-select the node.
In the matrix format of the trace page, derivation associations can be added without the limitation of multiplicity limits.
The model's error-checking function can detect multiplicity constraint violations, so please check for errors before editing.
If you try to add a trace series in the "Trace Tree Settings" dialog by clicking the "Edit" button > "Add" button from the "Manage Trace Settings" dialog with no lanes on the currently displayed trace page, you can only select the root model of the project.
To add a trace series to the trace configuration information, select "All Elements" under "Display in" on the Trace page, for example, to display one or more lanes on the Trace page before performing the operation.
If a table or image is inserted into a rich text cell in a form's grid, generating a Word or PDF format document may result in output with some of the table or image in the cell missing.
If this is the case, manually resize the tables and images.
Files generated in XPS format may not be opened with the standard Windows XPS viewer.
If an image generated in XPS format exceeds 69,000 x 69,000 pixels, the standard Windows XPS viewer will not open it with the message "This page cannot be displayed. If this is the case, you can use a different XPS-enabled application. In this case, please use another XPS-enabled application to open the file (e.g. Sumatra PDF). (Example: Sumatra PDF)
When generating documents, field values of true/false type are output as strings of "True" and "False" instead of in a checkbox format. In the document form, the field display name is output to the right of the string representing the field value, resulting in an unnatural order of notation for the document.
In contrast, the unnaturalness of document output can be alleviated by changing the "Title Direction" setting for Boolean fields to "Left" in the document form's view definition.
Product line model files created in different projects are not available. Therefore, product line model files cannot be imported, exported, registered for reference, or unregistered.
In the product line function, if a product is applied and "Hide Invalid Elements" is unchecked, models that are not assigned a product should be toned down, but in the case of model reference controls, they are hidden instead of toned down.
Although it is possible to edit some of the profiles built into the application system, such as the product line, from the inspector, do not edit them. Doing so may prevent the project file from opening properly.
DELETING A CONNECTOR IN THE ER DIAGRAM THAT HAS AN OFF-SCREEN CONNECTION DESTINATION MAY CAUSE THE SELECTION TO MOVE TO THE DESTINATION SHAPE AND CHANGE THE DISPLAY POSITION SO THAT THE SHAPE FITS WITHIN THE SCREEN.
IN THE ER DIAGRAM, CHANGING A SHAPE DEFINITION OR UNDOING MODEL EDITS (RE-PARENTING, DELETING, CUTTING) MAY CHANGE THE ORDER IN WHICH THE FRONT/BACK VIEWS OF THE TARGET SHAPE ARE DISPLAYED.
In that case, please modify the display order manually.
YOU CAN ADD A CONNECTOR AND A SHAPE AT THE SAME TIME BY DRAGGING AND DROPPING THE SHAPE TRIANGLE ON THE ER DIAGRAM. AT THIS TIME, YOU CAN CREATE A MODEL WITHOUT BEING CONSTRAINED EVEN IF THE UPPER LIMIT OF MULTIPLICITY DEFINED IN THE METAMODEL IS EXCEEDED.
You can detect that the multiplicity limit has been exceeded by going to the ribbon [Home]-[Model]-[Error Check].
YOU CANNOT ADD A SHAPE DEFINED BY SPECIFYING A "CLASS" IF THE ER DIAGRAM HAS "SHOW ITSELF AS A SHAPE".
IF YOU DEFINE A SHAPE ON AN ER DIAGRAM THAT SPECIFIES A [CLASS], PLEASE CLEAR THE [SHOW ITSELF AS SHAPE] CHECKBOX WHEN YOU ADD THE ER DIAGRAM.
If you are using Google IME when editing rich text fields, you may not be able to enter text correctly.
Use Microsoft IME to edit rich text fields.
If you save the project without finalizing edits in the text box, the text in the process of being edited will not be saved.
To save successfully, you must finalize your edits in the text box before saving.
Simply changing the tree layout (e.g. Home > Arrangement > Layout > Downward) in a tree diagram does not enable the Save Project operation and will not save the layout changes.
To save layout changes in the tree diagram, perform any other change operation before saving.
IF YOU PASTE TEXT IN TSV FORMAT AGAINST A GRID OR TREE GRID THAT HAS A MODEL REFERENCE CONTROL COLUMN, THE MODEL REFERENCE CONTROL COLUMN WILL ALSO BE PASTED, BUT IF THERE ARE MULTIPLE MODELS WITH THE SAME NAME THAT CAN BE REFERENCED, THE FIRST MODEL FOUND AMONG THE MODELS WITH THE SAME NAME WILL BE PASTED AS THE REFERENCED MODEL. THE PASTED REFERENCE MODEL IS THEREFORE THE FIRST MODEL FOUND AMONG THE MODELS WITH THE SAME NAME. THEREFORE, THE PASTED REFERENCE MODEL MAY DIFFER FROM THE INTENDED MODEL.
To ensure that the exact reference model is pasted, make sure that the name of the referenceable model is unique.
Interaction-type models can only be copied in text format.
When "related classes that cannot be added because they violate only path constraints" and "related classes that cannot be added because they violate only multiplicity constraints" are defined in the same model, the message displayed when adding a derivation relation between the main editor and subeditors and when adding a connector shape on a diagram will be different. The message is different when adding a connector shape on a diagram.
Add derivation relation between editors: display message that multiplicity constraint is violated
Add connector on diagram: display message that path constraint is violated
If a "relation that cannot be added because it violates a path constraint" is defined between the same models, any message specified for the constraint will not be displayed when adding a connector shape on the diagram. (An optional message will be displayed when adding a derived association between editors.)
The display may be disrupted when using a remote desktop connection.
In this case, close Next Design, reconnect Remote Desktop, and then restart Next Design.
The following changes are not shown as differences when comparing differences.
WHEN COMPARING DIFFERENCES, THE MODEL OF THE RELATED SOURCE IS NOT DIFFERENTIATED DUE TO A CHANGE IN THE RELATED DESTINATION IN THE CONNECTOR OF THE ER DIAGRAM.
TO CHECK THE DIFFERENCE, DISPLAY THE RELEVANT ER DIAGRAM AND CHECK THE CONNECTOR'S DIFFERENCE DISPLAY, OR EXTRACT THE RELEVANT DIFFERENCE INFORMATION WITH AN EXTENSION.
Cannot rename a model file after splitting it.
To rename a model file, merge the model file, then re-split and rename it.
When splitting into model files, if the imdl of another model is specified with the same name as a model file that does not exist (deleted by Explorer, etc.), when the project file is reloaded, the error message "Model:yyyy with duplicate internal ID with model:xxx cannot be loaded." error message appears.
In this case, right-click the model file with the duplicate name in the Project Navigator and execute "Unregister Model File" from the context menu.
When working with configuration management systems, files must be given the Needlock attribute to prevent file modification conflicts when operated from other SVN clients (such as TortoiseSVN).
Failure to do so may result in Next Design's team development features not working properly.
WHEN WORKING WITH SVN, PLEASE PLACE ONLY ONE PROJECT IN ONE FOLDER. (DO NOT PLACE MORE THAN ONE PROJECT IN A SINGLE FOLDER.)
When a project is retrieved by "Open from Repository" - "Select from Folder", the first project is always opened, even if more than one project is registered in the folder.
When "Get and Open from Repository" is executed, it searches for project files registered in the repository. At that time, a connection error may occur if the number of folders in the repository is large.
Specifically, it begins issuing http requests to automatically search for project files. Depending on the target server, a limit may be set on the number of http requests per minute, and if this limit is exceeded, a connection error will result.
IN THIS CASE, PLEASE SWITCH THE METHOD OF SELECTING THE PROJECT FILE TO BE RETRIEVED TO "SELECT FROM FOLDER" OR CHANGE THE SVN SERVER SETTINGS.
Do not replace a profile by splitting it into files and overwriting the corresponding file. You may not be able to open the project file properly.
If you wish to update your profile, please use the Import Profile function.
IF YOU HAVE TURNED ON "SHOW ITSELF AS A SHAPE" IN THE VIEW DEFINITION OF AN ER DIAGRAM, DO NOT CHANGE THE TYPE OF ITS OWN SHAPE DISPLAYED ON THE DIAGRAM TO A COMPARTMENT SHAPE. YOU MAY NOT BE ABLE TO EDIT THE CORRESPONDING DIAGRAM.
If you have changed to a compartment shape, undo or delete the view definition and redefine it.
Do not add "Use of Interaction," "State Invariant Expression," "Duration Constraint," and "Interaction Note" in the view definition of the sequence diagram (interaction class).
If added, the project file may not be available for future updates.
Do not define owned fields in related classes.
Performing a file cleanup from Manage Project Files will delete all models set in the Model Ownership field of the related class.
Do not add fields to product line features and products. Once you add them and save the project, you will not be able to delete the fields.
If you accidentally add a field, undo or discard the project without saving it.
For product line features and product metamodels, changes to field categories and display attributes are not reflected or saved.
You can freely rearrange the order in which the metamodel is displayed in the Profile Navigator, but if you reopen the project, it will be rearranged according to the following rules
Model types: (1) entities and interactions, (2) related classes, and (3) enumerated types are sorted in group order. Note that the order within the same group is maintained.
If you try to add an existing field with the same name as the field displayed in the grid in the document form, it may not be added below the grid.
If this is the case, select the document form title, then add the existing field, and move the position of the existing field added at the end of the form up.
You can select two models in the editor to add associations, but note that the type of association added depends on the type of view.
ER Diagram: Reference Related
Document Form or Tree Grid: Derivation Related
If a field currently displayed in the tree grid has a model corresponding to the derived class of the field's data type, changing the icon for that class will not immediately update the icon displayed in the name column.
If this happens, switch views or scroll to redisplay the tree grid.
If you add a reference field to a class in a model that is displayed in the Related Inspectors, the added reference field will not appear immediately in the Related Inspectors.
In that case, please switch the tabs or show/hide of the inspector to redisplay the related inspector.
The name of a group created in a document form view definition cannot be changed. If you wish to change the name of a group, you must cancel the group and set it up again.
The scripting method of extensions and script execution in the script editor is intended for the following uses
MAIN APPLICATIONS: AUTOMATED PROCESSING WITH SIMPLE PROCESSING LOGIC, SEMI-AUTOMATED PROCESSING WITH PARTIAL MODIFICATION AND REUSE, API OPERATION CHECK
FOR FULL-SCALE EXTENSIONS THAT REQUIRE EVENT PROCESSING, WE RECOMMEND USING THE DLL METHOD. IF YOU DEVELOP EXTENSIONS USING THE SCRIPTING METHOD, PLEASE ALSO REFER TO THE RESTRICTIONS DESCRIBED BELOW.
Scripted extensions will not raise an exception.
For example, if you try to delete data of an enumerated type during a foreach iteration, an exception is raised in C#, but in scripting extensions, no exception is raised and the iteration continues.
Do not implement scripting extensions that expect an exception to be raised.
Implementing event handlers with script-based extensions may cause a delay of several seconds in the timing of event processing.
IF EVENT PROCESSING IS TO BE REALIZED BY AN EXTENSION, DEVELOP IT USING THE DLL METHOD.
The extension does not support asynchronous processing.
If asynchronous processing is performed by extensions, data may not be updated or referenced correctly and cannot be processed as expected. Do not implement asynchronous processing in extensions.
In a DLL-style extension with a lifecycle of application, the Deactivate method is not executed when the extension exits.
If you need to implement processing at the end of an extension, process it in the application before closing event (application/onBeforeQuit) or the project after closing event (project/onAfterClose).
When a model is copied by pressing Ctrl+C on the diagram, an event before the command is executed (commands/onBeforeExecute) and an event after the command is executed (commands/onAfterExecute) are issued twice each.
Please be careful when using applicable events in extensions.
When a selection element is changed in the product line navigator, the model selection event in the navigator (navigators/onSelectionChanged) is fired three times when it should be fired only once.
Please be careful when using applicable events in extensions.
When a parent is reassigned on a tree grid or tree diagram with reference fields defined as parents and children, a model parent change event (models/onBeforeChangeOwner) and a model parent change event (models/onAfterChangeOwner) are unnecessarily issued to indicate that the ownership-related parent has changed, even though the ownership-related parent has not changed. AfterChangeOwner event (models/onAfterChangeOwner) is unnecessarily issued to indicate that the model parent has changed even though the ownership-related parent has not changed.
Please be careful when processing events for tree grids and tree diagrams.
Multiple undo operations may be required to undo model changes processed by extensions.
If multiple API calls with model changes are made in a single handler process, multiple undo operations are required to undo the model changes made by the handler process. To be able to undo this with a single undo operation, it is necessary to implement your own undo processing in the event handler of the Undo command.