CollaborationDetecting Changes in Diagrams During MergeYou can now specify in the Environment Options dialog whether to compare only the direct or all the changes in diagrams during the Project Merge and Project Comparison operations. By default, only the changes made by the user in loaded (open) diagrams are analyzed, leaving out unintentional diagram changes that occurred due to indirect changes in the model. This feature not only eases both merge and project comparison processes for the user, since the number of diagrams with changes is considerably reduced but also optimizes modeling tool performance. An Environment option to specify the changes to detect in diagrams.Learn more about diagram changes in model merge and project comparison >> Further Merge Usability ImprovementsThe model merge has undergone further usability improvements. From now on, changes from the Target and Equivalent Changes are automatically hidden by default; only the Source changes are shown. As a result, fewer changes need to be reviewed by the user. Additionally, the model merge has been extended by adding a capability to select which ancestor calculation algorithm to use. You now have the freedom to choose a Branch Point as an ancestor for your merges. This is especially useful when merge results become too complex to understand and analyze due to previously rejected changes. By default, the Lowest Common Parent ancestor calculation algorithm is used. Selecting the ancestor for future merges in the Merge Project dialog.Learn more about merge types in Teamwork Cloud >>
Back to Top |