The release notes show the new features and enhancements that have been included in Enterprise Studio, HoriZZon and the Team Server, and the issues that have been fixed.
On this page:
Release 3.0.4 - 30 October 2017
This release is particularly important for users who work with the BiZZdesign Connect functionality for Excel import and export.
The manual import of empty Excel worksheets resulted in a script error.
Release 3.0.2 - 11 October 2017
This release is important for users that have updated from Enterprise Studio version 2.5.0 or lower to version 3.0.0, or migrated from Architect or BiZZdesigner to Enterprise Studio version 2.6.0 or 3.0.0. You are advised to update to version 3.0.2. as soon as possible.This release has a changed metamodel configuration. You need to migrate your model packages with metamodels embedded (.xmam), or stored in your personal storage or on the Team Server to materialize the changes and fixes in this release.
New features and enhancements
Export to ArchiMate Exchange File Format is available again in Enterprise Studio, and now supports exporting ArchiMate 3.0 models, enabling opening these ArchiMate models in other third-party tools like Archi and Sparx Enterprise Architect.
The ArchiMate export function can be found in the ArchiMate ribbon tab, in Export.
The ArchiMate export functionality is available in the tool packages "Advanced" and "Enterprise", not in "Pro EA".
Opening a legacy Architect or BiZZdesigner model package that contains BPMN or Amber models in combination with one or more ArchiMate models, would result in the BPMN and Amber models being damaged by the automatic conversion from ArchiMate 2 to ArchiMate 3.
When a 2.5.0 or older working copy with uncommitted changes was opened with a newer version of Enterprise Studio, the uncommitted changes were invisible.
Release 3.0.0 - 18 September 2017
This release is useful for all users.This release has a changed metamodel configuration. You need to migrate your model packages with metamodels embedded (.xmam), or stored in your personal storage or on the Team Server to materialize the changes and fixes in this release.
If you are updating from Enterprise Studio version 2.5.0 or lower to version 3.0.0, commit all outstanding changes in your Team Server model packages before updating to Enterprise Studio 3.0.0.
This is not needed if you are updating from version 2.6.0 to 3.0.0.
New features and enhancements
The new web portal HoriZZon allows EA teams and business stakeholders to exchange real-time and tailored insights via a personalized, self-service portal that's accessible from any place and at any time. It is simple, fast and always up to date.
For more info, please contact BiZZdesign InSide Sales via telephone number +31 33 7600280.
Enterprise Studio Online is the new zero-footprint solution of Enterprise Studio (In the 2.6.0 release notes still referred to as "Enterprise Studio On Demand").
Future new features, enhancements and bug fixes regarding Enterprise Studio Online will be included in the section Enterprise Studio Online of the release notes.
The metamodel for the ArchiMate language has been adapted to conform to version 3.0.1 (Technical Corrigendum) of the ArchiMate standard. This mainly affects the relationships that are allowed between elements. Relationships that are no longer allowed in ArchiMate have been removed from the metamodel and will be marked as deprecated in existing models.
To check ArchiMate models for relations that are now deprecated, use the Deprecated relations check.
Any deprecated relations will be shown in the Worksets window. Double-clicking a relation in the list will open the view with the selected relation. The deprecated relation type can be changed into a valid type by right-clicking it and then clicking Change Relation Type.
The life cycle view now supports modeling capability life cycles. The capability life cycle is a useful addition which facilitates the creation of capability development roadmaps based on the Capability Maturity Model. These kinds of roadmaps are a core part of Capability-based planning and can be used to plan and monitor the development of a capability over a certain period. The capability life cycle has a number of fixed stages.
For more information about the capability life cycle, see Life cycle management.
The mapping of BMC elements to ArchiMate concepts has been improved, including support for the Capability and Resource concepts. The default mapping from BMC to ArchiMate is shown below:
Value + associated core element
Customer segment, Key partner
Value + associated core element
Product + Value
The Excel import can now deal with Excel worksheets with merged cells.
In addition, objects and relations can now be imported in case multiple types are defined for a meta-object or metarelation. Before, a warning was generated in this case. Now, an object or relation will be created, matching the first possible type from the list.
You can now add multiple attributes at the same time when defining a meta-element in a connection mapping. You can use the Up and Down arrow buttons in the selection window to put the attributes in the desired order.
The output for the Show databases and Show tables controls in a SQL Connection model is now sorted.
In the overview of the available columns in a table in a SQL Connection model, an additional column has been added that shows if the column is a primary key, an auto-increment identity column, or a foreign key that refers to another table.
The generated scripts for scheduled Excel, ServiceNow® and SQL imports and exports now add a summary of the results to the script log file.
When importing an object via an Excel connection that is identified by other properties than its name, there was no way to define whether its name should be updated or not. It always did, because this was the default setting.
To make this optional, the Replace option has been available in the properties of a mapping relation when attached to a meta-object (it was already available when attached to a property). The option is activated by default. When deactivated, the name of the object will not be updated.
Excel worksheets can now be imported and exported without the Excel application being installed. If not installed, an ADOdb connection is used to read from and write to a worksheet. As a prerequisite the ODBC driver Microsoft Access Database Engine 2016 Redistributable needs to be installed.For more information, see Import and export of Excel worksheets using an ADOdb connection.
The quick-create object controls for fast addition of objects and relations in a diagram or view are now also available in the DMN diagrams. They are the small triangles at the sides of objects in the diagram.
When opening a model package, Enterprise Studio now provides more feedback during the process, both in terms of which steps are being performed, and their progress.
The Query tool script editor now supports the keyboard shortcut key Ctrl+F3 to quickly search for the currently selected text.
Shortcut Ctrl+Shift+F3 will search in the opposite direction.
It is now possible for system administrator users to define a custom password policy for the Team Server. The password policy can be found under the General settings in the Team Server. It will be used to validate the passwords set by a user. The password policy supports the following:
- Minimum and maximum password length
- Minimum uppercase and lowercase characters, digits and special characters
- Combination of character types
Does the new policy affect existing passwords?
The policy is only enforced when passwords are changed. Once a policy has been set, there is no way to detect whether or not existing passwords satisfy the policy. Users will need to be forced to change their password in order to comply with a new policy. Users can change their password by clicking the Forgot password on the Team Server login page.
Because of the introduction of the password policy, the password strength check on the Team Server registration page and the set password page has been removed.
The Settings menu is not available in a hosted Team Server (used with Enterprise Studio Online or locally installed Enterprise Studio).
For more information about the password policy, see Configuring the Team Server password policy.
The user overview in the Team Server has been extended with a column for showing the last activity date for each user. This date is the date on which the user performed any activity on the Team Server.
All Team Server pages that show lists of model packages, users and user groups can now be sorted on the different columns in the lists.
The link to the page with information about Enterprise Studio software updates was not working correctly.
The minimal height of the main application window of Enterprise Studio was set too high, resulting in a bad fit on low-resolution screens.
The buttons on the Open tab of the Backstage view were sometimes shown with incorrect positions and incorrect order.
The shortcut key for opening the Properties pane had accidentally been changed from Alt+Enter to Ctrl+Enter. It can now be opened again using Alt+Enter.
When installed on the same machine, variants of the same version of Enterprise Studio (like a regular and an Academic release) inadvertently shared the files they store their application settings in. These variants were not able to keep settings that differ from those of the others.
Sometimes, when opening a legacy Architect or BiZZdesigner model package in Enterprise Studio, the automatic conversion of its ArchiMate content failed, and the model package could not be saved as an XMAM file or as a tracked or shared file.
When adding a moment to a customer journey, the serving relation was not added from the moment to the customer.
In case custom life cycle management profiles or life cycle types were used, the corresponding legend was not (properly) shown on the Life cycle view.
In a ServiceNow Connection model, empty dates were not exported correctly.
When importing new objects with an Excel connection, the values of attributes of assignable profiles were not imported, because the profile was not assigned dynamically.
Evaluation of DMN decision tables no longer worked, due to an error in the way the Enterprise Studio scripting engine handled access to structure fields.
DMN decision tables with hit policy "first" or "rule order" were not evaluated correctly for tables with more than 9 rules.
Enterprise Portfolio Management
In case a custom metric was scored automatically (by script), its possible values were not visible in the metric definition form.
The aggregation mode of a chart (except for pie charts) could not be set in the analysis definition view. As a consequence, the setting used in a portfolio could differ from the default setting (as assumed by the analysis definition view), resulting in the display of a warning icon.
If a metric value was added to an object when the property form was not in edit mode, deleting the value in edit mode would also delete the metric.
The use of custom metrics in combination with automated scoring could produce error messages in the score view.
Enterprise Studio Online
Sometimes a "Database is locked" error occurred when using Enterprise Studio Online.
After defining an "alias" type using the Metamodeler, a script error would pop up when applying the changes.
Generating a view using the Generate view command would take a long time in case of large models.
After copying objects from one model package to a model package in another window, and then deleting the copied items in the Worksets window, Enterprise Studio would go into an infinite loop.
It was not possible to navigate relations in a model using the Navigator.
The Worksets window displaying imported/matched objects when copying objects from one model package to another would also appear when copying objects within the same model package.
The use of the Elaborate Relation function could crash Enterprise Studio when working on relations associated with the Risk element.
Enterprise Studio could turn into an unstable state after copying large amounts of objects between two model packages.
After copying objects between model packages, closing the last model package would sometimes crash the application.
TP-5045, TP-5062, TP-5179
The Unused objects dialog would keep displaying objects as "not used" after clearing and again selecting a filter check box (which then should have produced no objects).
Copying or creating layer objects took much more time than it should.
During editing of a view's background images, the view background would turn to white again, while it should stay red during editing.
Reporting and printing
If the Enterprise Studio tool language was set to English, the Page Setup dialog for generating an HTML or RTF report still had some defaults in Dutch.
Scripts with large amounts of statements or if conditions could crash the application.
Opening or reporting large numbers of views, or executing many scripts would consume significant amounts of memory that would not be freed until application exit.
The scripting function ask would ignore its second parameter (caption) when the third parameter (initial value) was specified.
Some script methods associated with the discontinued reuse functionality (isReuse, getReusedObject, reuseIdentifier, setReuseIdentifier, resetReuseIdentifier) were not removed from the scripting language.
The script generated for a view filter (color view, label view, etc.) would sometimes issue a script warning when executed via the Query tool.
A vulnerability to Cross-Site Request Forgery (CSRF) in the Team Server has been fixed.
The layout of the Commit tab in the Backstage view was ruined if the application window was minimized and maximized again (while showing the Commit tab).
In warnings about collaboration conflicts the names of the objects would sometimes be displayed as "??" when the objects were not yet loaded.
The warning message issued when objects in a project are out-of-date and the project needs to be updated would unnecessarily display the names of those objects as "??" when the objects were not yet loaded.
A model could disappear from the project in the Team Server after deleting the model and then restoring to a commit in the timeline in Enterprise Studio which restored the model.
When a user has the "Lead Designer" role and was invited for more than 20 model packages or projects, the Manage models button on the project page of the Team Server was not always enabled.
View filters and viewpoints
After editing a saved viewpoint created with the Generate view for command, its name would be reset to its original name (the name of the selected view type).
The attribute selection tree in the Color view and Label view dialog was not displayed in the active model package language when the Navigate via model check box was selected.
Color or label viewpoints that were created or edited by the Query tool, dropped on a view, and then executed by double-clicking their reference, would not be applied to the active model, but instead to the model containing the viewpoint.
Release 2.6.0 - 8 August 2017 and older
Enterprise Studio 2.6.0 release notes and older are only available as PDF.
ArchiMate® is a registered trademark of The Open Group.