The new release presents significant Licensing, Installation, and Other Changes. Additionally, it adds improvements to the Project Statistics tool.
Users can now handle conflicts by Resolving Conflicting Changes Automatically in Merge in Collaborative modeling, and major Memory Consumption Improvements in Merge have been made.
Last but not least, a number of key issues detected in earlier versions, including those affecting modeling tool performance, have been fixed.
Download the newest MagicDraw version at nomagic.com or contact your sales representative. Don't forget to give us your feedback on LinkedIn, Twitter, or Facebook. For further information, please check the latest documentation and additional resources.
You can now contribute to improving the performance of the modeling tool and modeling experience. Simply export the Project Statistics report that is based on the quantitative data collected from your project and then share it with us.
Locking elements prior to modifying them is now a thing of the past with the introduction of the Lock-free model editing mode (a.k.a an optimistic locking). You can continue using locks if that is what suits your team’s needs best; however, the Lock-Free editing mode is a simple yet effective way to boost modeling productivity.
To start using the Lock-free editing mode, first enable it in the project, after which you can work on model elements freely, without locking them. Consequently, there is no need to wait until locks are released by other users to work on the same or related parts of the model. If conflicting changes occur, you can handle them in the Conflicting Changes panel to prevent data loss.
Image Removed
Handling conflicting changes in the Lock-free Editing mode
The Disconnected team collaboration UI has been rebuilt from the ground up. The improved feature usability allows distributed teams working on the same server project to update it with the changes from the locally exported .mdzip file more conveniently and with a significantly reduced amount of manual steps.
Not only can you now update projects without having the target ones open in the modeling tool, you can also manage used project changes more easily. Additionally, the newly-implemented smart branch selection algorithm ensures configuration-aware update of server projects and smoother project merging in the future.
Image Removed
Updating a server project from a local .mdzip file
Along with improved Merge usability and bug fixes, the 19.0 SP3 release adds adjustments to common ancestor calculation algorithm rules. As a consequence, subsequent project merging iterations can be carried out more effectively without the need to repeat previously made merge decisions.
For your convenience, we have moved an environment option Support Mount Points of Usages in Teamwork Cloud from Save/Load to the Collaboration node. Image Removed
When working with change sets, you can now discard both suspended and all local changes in an active change set. Image Removed
The Maintain Mount Points of Used Projects option can now be accessed even more conveniently. It has been added to the Update from Local Project and Add Project to the Server dialogs. Image Removed
Indirectly used projects can now be hidden or unhidden automatically together with directly used projects when their status changes, such as upon the used project update, remove, or merge.
Resolving Conflicting Changes Automatically in Merge
Handle Merge conflicts more efficiently by tailoring the Merge behavior to your needs! From now on, in the Environment options dialog, you can specify either the Source or Target to be the default resolution when dealing with conflicting changes.
Image Added
Automatically choosing Source as the default resolution during merge
The latest release brings significant improvements to the Project Merge memory consumption. Specifically, with multiple optimizations in place, we reduced the memory footprint by 25%-40%, compared to version 19.0 SP3. The effect may vary from model to model, depending on the model's size, as well as the number and type of changes themselves.
Image Added
Comparing memory consumption between different versions
The -leaveprojectopen parameter helps reduce memory when loading or closing any large-size project for property files by leaving the project open per property file after generating reports. Learn more how to deploy this command for multiple report generation >>
The new template.docx.ignorechildstyle report property for the DOCX template is now available for ignoring template styles to be included into generated reports and applying matching styles in the main template instead. Learn more about this report property >>
The following key issues have been fixed with this version:
No error occurs when uploading generated report files to the server through FTP and SSL in Report Wizard.
The problem of the Dependency Matrix template displaying incomplete allocated dependencies in Report Wizard has now been solved.
TWC projects that automatically used a system/standard profile while being used by a non-system/standard usage can now be exported into .mdzip.
The direction of Item Flow can now be changed.
Diagram validation is now faster in larger projects.
The Transformation Wizard performance problems have been fixed.
A new nested Instance is no longer created instead of being reused during the data import from Excel.
Dialog overlapping no longer occurs when several dialogs are opened on MAC.
An empty PDF was printed even though the diagram was fully filled
The GanttChart diagram became empty after model obfuscation
The SVG export did not export IDs for elements in a diagram preview
The comments panel did not appear when the HTTP Protocol was used
When it was impossible to create the symbol for DurationConstraint using API
Project loading from TWC
The Lost Message could not be created using Open API
The MBPLE variant overwrite protection did not work on TWC
Some expressions were not recalculated after reloading the project
Documentation in the Properties tab could be updated only after the project reload
There was a delay when the element was renamed in the diagram
The error message (java.lang.IllegalStateException: No UUID map object after save) no longer appears after cloning the project
Content block
id
94973651
Info
You can check the list of publicly available issues or your own reported issues fixed in MagicDraw 19.0 SP3SP4. Note: You will be required to login. Use the same username and password as for www.nomagic.com.
