Architect Release 2.1 has been released. It follows the succesful 2.0 release and fixes various bugs, while adding a few minor new functionalities.
In the Architect 2.1 release, the following features are new or improved.
- The command "More than one relation of the same type between objects" under the menu "Checks" (available in Architect Professional) now outputs its results to a workset instead of a table, making it easier to perform actions on those results. Its results have been improved. (TNG-1948)
- Double clicking on an item in the selector dialog for colour and label view selects the item clicked on and now directly closes the dialog.
- The performance of the application when opening views or moving and resizing of objects within a large model containing many collapsed levels has been improved significantly. (TNG-1936)
- The new viewfilter command 'Show relation roles' has been added. When active, this filter shows the role names of relations in the view. (TNG-1923)
- A 'link to views' attribute has been added to the basic profile, which allows each object to link to various other views. (TNG-1951)
- The HTML Help manuals now contain the complete texts of the Appendices.
The following bugs have been fixed.
- In the ArchiMate metamodel, types 'Deliverable', 'Goal', and 'Effect' were translated as 'Compound'. (TNG-1907)
- On some PCs Architect Professional would not show the menus 'Analysis', 'Checks', and 'Roadmap'. Also, the command 'transform xml' would not function on such a machine. (TNG-1909)
- The Query tool's metamodel browser has been renamed from 'profile browser' to 'metamodel browser'. (TNG-1902)
- In Architect Professional, the command 'Domain dependencies via profiles' from the 'Analysis' menu produced dependencies via relations, not via profiles. (TNG-1900)
- In HTML reports a script error would occur when using the index in its popup state. (TNG-1910)
- In Architect Professional (with Roadmapping add-on) the Roadmap command "Show roadmap in browser" gave incorrect output in case of parallel periods. (TNG-1919)
- After creating a HTML report with such settings that initially a specific view diagram should open itself, and also that the summary window of this view should open, the summary would open but close again immediately. (TNG-1913)
- In a HTML report, unrelated viewpoints or folders would typically be reported nested, and in some cases more than once. (TNG-1917)
- When reporting viewpoints to HTML, included viewpoints inside folders that themselves were not included were not reported. They are now: only when a viewpoint itself is unchecked, it is not reported. (TNG-1926)
- The "User x Group" and the "Roles and rights" tables of a repository were not editable anymore. (TNG-1933)
- During import of a XMI file some relational types could not be created, although they were allowed by the metamodel. (TNG-1929)
- The object values in the legend of a colour view are now correctly sorted on their name. (TNG-1921)
- Users that checked out objects in a repository model could not edit this model after logging on to Windows with a name that differed from the name used in the previous session only by upper/lowercase. The upper/lowercase character distribution is not relevant anymore for the repository. (TNG-1941)
- 'Generate view' should not take unchecked types into account. (TNG-1924)
- Graphical changes as a result of the assignment of a profile only worked in the first view they were applied in. (TNG-1934)
- Architect allowed drawing a relation starting from a relation, with unpredictable results. (TNG-1957)
- Translations of the ArchiMate view types were not stored within the ArchiMate metamodel folder, but within the Architect installation folder. They have been moved to the correct place. (TNG-1958)
- Architect Professional would sometimes crash when reporting a model containing collapsed objects and two or more viewfilter viewpoints. (TNG-1942)
- Under Windows Vista, the model and view browsers would not correctly handle multiple selection using Ctrl and Shift. (TNG-1950)
- Copying a viewpoint (query) to another model did not work when the application option (advanced) "match objects when copying between models" was switched on. (TNG-1914)
|