The new release presents significant Licensing, Installation, and Other Changes. What is more, it brings improvements to the Project Statistics tool.
As for Collaborative modeling, users can now handle conflicts by Resolving Conflicting Changes Automatically in Merge. Additionally, 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, has been fixed.
You can now contribute to improving the performance of the modeling tool and modeling experience. All you need to do is to export the Project Statistics report that is based on the quantitative data collected from your project and then share it with us.
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.
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%, as compared to version 19.0 SP3. The effect may vary from model to model and depend on its size as well as the number and type of changes themselves.
Comparing memory consumption between different versions
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 and, at the same time, were used by a non-system/standard usage could no be exported into .mdzip.
The Excel Import plugin could not be installed since it was not compatible with the 19.0 SP4 version of the modeling tool.
The direction of Item Flow could not be changed.
The exception was thrown in a .log file when obtaining element names from the elements that did not have names.
The validation of diagrams was time-consuming in larger projects.
The Transformation Wizard performance problems.
A new nested Instance was created instead of being reused during the data import from Excel.
Dialog overlapping occurred when several dialogs were opened on MAC.
