Skip to end of metadata
Go to start of metadata

Expand/Collapse All

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 20 December 2019

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


 Windows Client application available for hosted Enterprise Studio

Enterprise Studio Online can now be used through an advanced small Windows Client application instead of a web browser. This allows for usage of multiple screens, direct printer access and more.

If you prefer to use this application instead of your web browser, BiZZdesign can enable the Windows Client for you. After that, the Windows Client needs to be downloaded and installed on the user computers, and  use of the Windows Client needs to be activated in the Team Server for each user who is going to use the Windows Client.

For more information, please refer to Using a Windows Client application for running Enterprise Studio Online.


 Allowed ArchiMate relations conform to ArchiMate 3.1

Permitted relations in ArchiMate are now conforming to the ArchiMate 3.1 standard. Relations that are no longer permitted according to the standard have been deprecated.

 ArchiMate exchange format import and export conform to ArchiMate 3.1

The ArchiMate exchange format import and export have been extended to accommodate for the changes in version 3.1 of the ArchiMate standard. Main changes in 3.1 are:

  • Introduction of the Value Stream element
  • Introduction of an optional direction for the association relationship

 Influence and Realization relation available in Stakeholder view

The Realization relation and Influence relation have been added as allowed relations in the ArchiMate Stakeholder view.


 Sharing views with other users
TP-10186, TP-10188, TP-10267, TP-10370

It is now possible to share views from sites through hyperlinks.  Hyperlinks can be shared with other people who have access to HoriZZon and to the sites where the shared views are located. The recipient of the link only needs to click the link and sign in to HoriZZon to view the shared view. For more information, please refer to Sharing HoriZZon views with other users.

 Various interface improvements on pages

Following improvements have been made to HoriZZon pages:

  • New pagination, sorting, and search function (replaces the former filter options) for overview pages and lists of favorites, sites, and dashboards. The sorting function consists of two separate controls, one for selecting the data to sort on and one for sorting ascending/descending. Example:

  • Toggle grid/list view for overview pages and lists of favorites, sites, dashboards, and workflows. Example:

  • Changed and relocated Add button for overview pages of sites and dashboards, and Share button for dashboards overview page. Example:


 Web session function no longer active

The function in the Brainstorm section (Measure phase) of a Lean model to start a web session has been disabled.

Online editing

 Self-defined properties and associated values available in Enterprise Studio
TP-10116, TP-10249

Property fields that have been defined in document definitions and their associated values entered in HoriZZon, are now also available in the shared model package in Enterprise Studio in which the property fields have been defined. The external properties and their values are available in the Properties window of the element once the element is selected in the model browser or in the view. The properties and their values are read-only. They can, for example, be used for generating color views and other analysis goals.

If values have changed in HoriZZon, you can press Ctrl+F5 in the model package to clear all current values and retrieve the latest values from HoriZZon. The latest values will be retrieved once you select an element with external properties. For more information, please refer to Using data block values from HoriZZon in model packages.

Team Platform

 New Consumer role
TP-10103, TP-10104, TP-10106, TP-10107, TP-10108, TP-10134, TP-10139

The roles for defining users' access to HoriZZon functionality and the Team Server administration pages in HoriZZon have been extended with the Consumer role.  The Consumer role can be used for users and groups who only need to be able to view the content of HoriZZon sites and dashboards. They can browse the content of sites and dashboards that have been shared with them. Users with the Consumer role can also start workflow requests based on the default workflow.

Whether existing users and groups in your Team Server will automatically be assigned the new Consumer role when upgrading to the new release depends on their current roles:

  • Users and groups that currently have the Lead Designer, Designer, and/or the Contributor role will automatically be assigned the Consumer role.
  • Users and groups that only have the System Administrator and/or Administrator role will not be assigned the Consumer role. If they need to have that role, you will need to manually assign the role.
  • Users and groups that do not have a role at all will also not be assigned the Consumer role. If they need to have that role, you will need to manually assign the role.

Consumer role takes one license Consume seat.

For more information about the Consumer role, please refer to User roles and permissions.

 Toggle for grid/list view on Team Server administration pages

The Team Server administration pages in HoriZZon containing overviews or lists of users, groups, packages, and projects now have toggle controls for switching between a grid view (tiles) and a list view. Example:

 Contributor cannot add and share dashboards

As of this release, users who solely have the Contributor role (Consumer role included) can no longer add and share dashboards in HoriZZon.

 Improved sorting function on overview pages of Team Server administration

The sorting function at the top of the overview pages of packages, users, groups and API clients has been split into two separate controls, one for selecting the data to sort on and one for sorting ascending/descending. For more information, please refer to Sorting on HoriZZon and Team Server list pages.

Bug fixes


Thumbnails in the Coach view could not deal with removed views.



After upgrading a shared model package's embedded configuration to the latest tool configuration, any special characters in the translations of custom profile attributes were no longer encoded correctly, leading to malformed texts.


Data integration

The Technopedia connection in Enterprise Studio would not work due to an API change on the Technopedia side.



The content of generated table views would disappear in some situations.TP-9876
Clicking on collapsed graphical shapes in HoriZZon brought up an empty page instead of navigating to the proper destination.TP-9945
Workflow form fields were misaligned.TP-10203
On occasion redirecting after sign-in could take the user to the Sites page instead of the correct page.TP-10276

Language and translation

When generating a color view or label view in a Team Server model package, the label of an attribute was shown untranslated in the view's legend. In addition, the name of the view in the viewpoints pane also contained untranslated parts.



When drawing a duplicate relation between two objects, letting the new relation reference refer to the existing relation would not keep its intended position. Also, when this is a relation that ends on another relation, the application would crash.


Online editing

When opening the Metamodeler, a message would appear regarding registering schemas.


Team Platform

The background of a view and the background of objects (of a shared model package) in the model browser would turn to gray periodically, for a short period of about 15 seconds. After that, it would turn to white again.TP-10127
The Activity Console sometimes dropped the token needed for authentication when the connection with the Team Server was lost. This resulted in users having to authenticate again.TP-10234

Team Server model packages originally created by making a copy of the "Archisurance TOGAF" example model in some cases refused to commit changes while (incorrectly) reporting that an "uncommitted migration is still active". The example model has been repaired.

This incorrect error message would occur when certain parts of the original example model still existed when the model package was added to the Team Server, but need to be deleted or changed afterward. If you have a Team Server model package based on the "Archisurance TOGAF" example model and experience this problem, please contact BiZZdesign Support.



Workflow task notification e-mails were not sent.


Release 5 November 2019

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.

As of 01-01-2021 BiZZdesign no longer supports Internet Explorer 11. This will impact your use of Enterprise Studio Online, the Team Server, HoriZZon, and InSite Lite.

New features and enhancements


 Tool configuration management improvements

Management of the Enterprise Studio tool configuration has improved. In the Backstage view, on the Manage Package tab, is a new tab Manage Configuration, on which the embedded configuration of the current model package can be inspected and managed. This includes the ability to open and customize individual metamodels, and a new function to upgrade the entire configuration to the latest tool version. Upon opening, the new tab lists all available metamodels, their usage, and their versions. Clicking a metamodel in the list will open the Metamodeler.

The new configuration management means that metamodels can no longer be opened and customized via the Metamodel command in the View ribbon tab. This command is no longer available.

The Manage Configuration tab is only available for tracked and shared model packages, not for file-based packages. Configuration management is only available to users with the Lead Designer role.

The new configuration management will simplify the configuration upgrade procedure for most users. Please take note that advanced customizations to the configuration made outside the Metamodeler, such as customized concepts, symbols, and script libraries cannot be handled. For more information, please refer to Updating to a new Enterprise Studio release.

Bug fixes

Enterprise Analytics

In model packages containing models for two or more metamodels, adding an attribute or profile filter to a chart would produce a script error.



HoriZZon did not display images when running in Internet Explorer.


The search button in HoriZZon would not work properly when searching multiple times.TP-10248


When generating a view, clicking the Relation Types tab would invoke a crash.TP-10232

Translations in the profiles shown in the profiles cross-reference table were missing.


Language and translation

Attribute translations were lost during a configuration upgrade using the MetaModeler.TP-10196

Profile attribute translations were not shown in property forms.



Generating RTF reports would crash the application.


When generating an InSite Lite report, the Profile attributes tab of the reporting window would not show the attribute tree.TP-10223

Release 23 October 2019

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


 New installer for on-premise installation Enterprise Studio

This release of Enterprise Studio comes with a new installer for on-premise installations. Main features are:

  • If there is a previous installation of Enterprise Studio using the new installer, it will upgrade Enterprise Studio to the newer version. It will remove the complete old Enterprise Studio installation and replace it with the new version. In case of a major release (e.g., from ES 4 to ES 5), you can change the installation location at the start of the installation wizard if the old installation should not be replaced (default location is 'C:\Program Files\BiZZdesign').
  • If you try to install an older version of Enterprise Studio than what is currently installed, the installer will show a message declaring a newer version already exists. This prevents you downgrading unless you uninstall your current installation of Enterprise Studio and reinstall using the older version of the installer. You can select which directory Enterprise Studio will be installed into.
  • The installer for a specific installed version of Enterprise Studio can be used to uninstall the application or to  repair it. Repairing means it will re-add all the files that should be in the installation directory and can be used if you have removed a file from the installation directory.

The new installer has no effect on installations using the old installer. However, it would be advisable to uninstall the old version of Enterprise Studio before installing this release using the new installer. Make sure to stop Enterprise Studio and the Activity Console before uninstalling.

If you are performing Enterprise Studio installations using a script, please make the necessary adjustments to the script.

For more information, please refer to Enterprise Studio and HoriZZon Server installation.

 Removal of file extension check dialog

Following the introduction of the new Enterprise Studio installer, the File extensions dialog and its associated functionality has been removed. This window would appear during the installation of Enterprise Studio, asking whether you want to associate your files with the tool version you are currently installing.  Additionally, the application setting for checking file associations upon startup has been removed from the Advanced tab of the Enterprise Studio Options.


 Tool configuration accessible for scripts without open model package

Previously, scripts executed outside of the context of an open model package, such as command-line scripts, would not have access to metamodel script libraries, as these are part of the configuration embedded in a model package. Now such a script will automatically fall back to the libraries contained in the tool ("disk") configuration.

Enterprise Analytics

 Set time interval of x-axis line chart

It is now possible to manually set the time interval of the x-axis in a line chart, ranging from x seconds to x years. The interval is a minimum interval; if the available space in the chart does not allow showing the interval, the chart will automatically display a larger time interval.


 Improved navigation for view strategy blocks

Clicking a view strategy block (from a Strategy on a Page view) in HoriZZon now navigates directly to the view, showing the same behavior as in Enterprise Studio.

 Navigation for BPMN call activities

It is now possible to navigate BPMN call activity elements in HoriZZon. Clicking the plus control in a call activity will open the called element.

 Cross-model navigation for BPMN resources and resource roles

Cross-model navigation is now also supported for BPMN resources and resource roles.


 New licensing system available for on-premise installations

In this release, the new licensing system is also available for on-premise installations. The licensing system requires the availability of a Team Server, which acts as the licensing server. It replaces the CodeMeter Runtime licensing mechanism.

The installer files for this release are available at request. If you wish to update your software, please contact BiZZdesign Support, and request the new software release. BiZZdesign will send you the release files, including a new license key that you need to register when updating your software to the new release.

Customers running Enterprise Studio with a Team Server:

Perform your regular update procedure, but after installing the new Team Server and new Enterprise Studio, register your new license key before upgrading any custom configurations and migrating model packages. For instructions, please refer to Enterprise Studio release-specific required actions.

Customers running Enterprise Studio without a Team Server:

Do not perform your regular update procedure. Instead, perform the procedure for installing a new Enterprise Studio with a Team Server. This includes registering your license key. For instructions, please refer to Enterprise Studio and HoriZZon Server installation.

 Grace period in case of seat shortage

A grace period has been added if license seats are exceeded before shutting down the Team Server. The grace period is visible to System administrator users, on the License page of the Team Server settings.

Team Platform

 New Java version required for Team Server

As of this release the Team Server requires Java 11 instead of 8 or 1.8, which requires updating your Java version if you are not on this version. For more information, please refer to Enterprise Studio release-specific required actions.

 Proxy settings storage place connection no longer needed

The storage place (Team Server) connection does not need proxy settings anymore, meaning that they do not need to be configured anymore in the wizard for configuring a storage place connection. Instead, the proxy settings from Windows will be used automatically. However, it remains possible to manually set the proxy settings in case they cannot be detected automatically.


 New UML state diagram

The UML metamodel has been extended with the UML state diagram. State machines can be used to model discrete behavior of a part of a designed system through finite state transitions or to express the usage protocol of part of a system. To create state diagrams, a new diagram type "State diagram" is available in the UML model.

Example of a state diagram:

Bug fixes


It was not possible to draw relations between objects on the Lifecycle view.TP-9650
A Landscape map with an empty x population was broken, showing too many elements in the cell.TP-9851

Selecting a view as the z population for a Landscape map or a matrix chart no longer worked.


Changing the lifetime of an object to indefinite would result in a crash.TP-9933
Custom metrics did not work in a Customer Journey Map.TP-10083


Copying nested BPMN objects into a BPMN sub-process would crash Enterprise Studio.


Data integration

After moving a connection in a Connection model, or a meta-element in a mapping, a rectangle was visible around the members (mappings, attributes, metrics, etc.) of the moved element.


The export of elements without a name to the ArchiMate Exchange format resulted in a file that was not accepted by all tools supporting this format. To fix this, empty names are now exported.TP-7227

Setting NumberFormat when exporting dates to Excel using an Excel connection model would lead to errors in some Excel versions.


Exporting an ArchiMate model without relationships to the ArchiMate Exchange format led to an invalid export.TP-8151

Enterprise Analytics

It was no longer possible to create a bar chart with a script.


Aggregate metrics of type money were not properly supported for timed values. In the case of line charts, they did not show.TP-9971


The pushpin for saving generated views (like color views) and viewpoints in HoriZZon did not always work.


Lists and sets were not visible in object properties.TP-9842

Searching for a specific period in HoriZZon did not work.


Sometimes online edited documents could not be savedTP-10032


After selecting a relation and just one of its end objects in a view, and then copying an pasting those, only the end object would be copied, which is correct, but when running Check and Repair afterward, the results would list a relation reference "without a referred object" and a reference "without a graphical object".


Team Platform

From the moment a model package was saved in the Team Server, Enterprise Studio no longer remembered which views were open at the last save (to open in the next session), but instead kept opening the views that were open at the initial save.TP-5716
A filter on a group containing more than one word did not work properly when provisioning users with Azure AD, resulting in users not being added to the proper group automatically.TP-9507

It was not possible to add users with an e-mail address containing a single character domain name.



After moving a UML element (class, enumeration, etc.) on a diagram, a rectangle was visible around the members (attributes, operations, literals) of the moved element.



The wrong date format was submitted in workflow forms when running HoriZZon in Safari.


Trying to upload a custom workflow with long names could break the workflow functionality.


Release 5 September 2019

This release is only available for the hosted solution Enterprise Studio Online. The release is not available if you are working with an on-premise installation of Enterprise Studio or Team Server.

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.

Bug fixes


It was not possible to migrate model packages created with an Enterprise Studio version prior to 4 [2019-08-13].


Release 13 August 2019

This release is only available for the hosted solution Enterprise Studio Online. The release is not available if you are working with an on-premise installation of Enterprise Studio or Team Server.

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


 Updated currency symbol for Swiss Franc

The default currency symbol for displaying Swiss Franc money values has been changed from SFr to CHF.

 Limitation of available font sets

The set of available fonts in Enterprise Studio has been reduced, and now contains only fonts that are also supported by HoriZZon. This ensures that views in HoriZZon always look identical to their presentation in Enterprise Studio.


 Improved autolayout

The auto layout function for ArchiMate views has been improved. Most notable change is that the default layout direction of Access, Aggregation, Composition, Flow, and Triggering relations is now from top to bottom (which was bottom to top).

Data integration

 BiZZdesign open API available

A data enrichment open API has been added to the HoriZZon server. With this data enrichment API external attributes can be added to existing structural data created by Enterprise Studio. In order to use the open API a named "API Client" must be created in HoriZZon. For more information and instructions, please refer to BiZZdesign Open API.

Team Platform

 Alternative token authentication available for Azure AD

The current Azure AD configuration for the Team Server uses Azure AD tokens for user provisioning. If you prefer to use a secret token for authentication instead of Azure AD tokens, there is now the possibility to generate a SCIM token and use this for authentication in your Azure AD configuration. Both authentication options are equally save.  It is always possible to return to using Azure AD tokens for authenticationThe SCIM token can be requested (and deleted) via the Team Server authentication settings. After that the token needs to be registered in your Azure AD configuration for user provisioning.

For customers with a hosted Team Server, please contact BiZZdesign support for requesting a SCIM token if you want to use a secret token.  For instructions about including the secret token in the Azure AD configuration, please refer to  Configuring Azure AD for hosted Team Server and HoriZZon.

Please take note that the alternative token authentication option is not yet available for on-premise installations, since this release is only available for the hosted solution Enterprise Studio Online.


 E-mail notification for workflow tasks

It is now possible to enable e-mail notifications for tasks in a custom workflow. When activated, an e-mail message will be sent to individual users upon assignment of tasks.

 Scope of custom workflow optional

Setting the scope of a custom workflow is now optional, making it possible that a workflow can be started on any type of object in HoriZZon. Not using a scope means that it is no longer mandatory to define workflow data in the Metadata diagram. Additionally it is no longer needed to set the subject on the start event of the workflow definition.

When not defining a workflow scope, make sure to only use fields in the workflow forms that are not object-related, like a username or registration date. Do not use fields with object properties.

 Option for setting visibility all users

If your custom workflows include fields of category "User", tasks can be assigned to other users with this field. By default, any user working on this task can see all users from the Team Server when selecting a user to assign the task. If users with only the Contributor role should not have access to all other users' name and e-mail address (for privacy or security reasons), the workflow should ideally be designed in a way that the user field is not available to these users.

In addition, there is now the option Always show all users in the general Team Server settings, enabling you to prevent Contributors from having access to other users' names via a user field.  It is activated by default, deactivate it if access should be prevented. The setting is only accessible to users with the System administrator role.

The Team Server settings are not available when working with a hosted Team Server. In that case, please contact BiZZdesign Support if you want the option to be deactivated.

Bug fixes


If the Enterprise Studio application experienced a crash, the crash reporting functionality would sometimes include a desktop screenshot that not only showed windows of Enterprise Studio, but also of other applications.TP-9429

A number of fonts that were available in Enterprise Studio were not supported by HoriZZon, making views look very differently in HoriZZon. Because of this t he set of available fonts in Enterprise Studio has been reduced, and now contains only fonts that are also supported by HoriZZon. This ensures that views in HoriZZon look identical to their presentation in Enterprise Studio.


Enterprise Studio would hang during startup when its custom configuration contains a specific kind of error.



Changes in the transparency of row or column header elements in a Landscape map were lost when refreshing or modifying the Landscape map.



When clicking the link in a workflow e-mail notification, the user was redirected to the sites overview page instead of the specific task.TP-9323

After changing a preferred cross-model relation in Enterprise Studio, the control for navigating this cross-model relation in HoriZZon would still use the old preferred relation, linking to the wrong target.


When selecting a user in a workflow field, the autocomplete list with names would not be filtered when typing the name.TP-9799


The Enterprise Studio trial version did not display the proper explanation text on Backstage pages for actions that are not allowed under a trial license.


The Enterprise Studio trial version did not display its expiry date in the About Enterprise Studio window (File > About).TP-9720

The license expiry date on the license settings page in HoriZZon was shown as an invalid date in Internet Explorer and Safari.



Dragging and dropping an object from the model browser onto a view made the view scroll back to the top. Also, the dropped object was no longer highlighted afterward.


Online editing

Uploading identical document definitions from different model packages from Enterprise Studio could cause loss of data.



Scripts were allowed to add values to a profile collection attribute that it should not be able to contain according to its definition.


Team Platform

It was not possible to move the end objects of a relation when that relation was located in a read-only model.TP-5714
Enterprise Studio would hang in scenarios involving the copying of a large number of objects from a shared model package to a different model package.TP-6386

The icon of a regular model package was not correctly updated to the icon for a shared model package after saving the package on the Team Server using Save as.


Sometimes the Activity Console would disconnect multiple times a day, making the user need to sign in again.TP-9811


When clicking the link in a workflow e-mail notification, the user was redirected to the sites overview page instead of the specific task.TP-9323

A custom workflow would appear on any object or view in HoriZZon and could be started there despite of the defined scope.

If you have custom workflows that you use on any object or view, you will notice that this is no longer possible because of the defined scope. In order to continue using this workflow on any object and view, you need to remove the scope of the workflow, and re-upload it (defining the scope of a custom workflow is now optional).
When a workflow request was started via the properties panel, long form field labels took up too much vertical space (because of the wrapping), which ruined the form's layout.TP-9750
When selecting a user in a workflow field, the autocomplete list with names would not be filtered when typing the name.TP-9799

Release 2 August 2019

This release is only available for the hosted solution Enterprise Studio Online. The release is not available if you are working with an on-premise installation of Enterprise Studio or Team Server.

Bug fixes


The layout of views in HoriZZon was inconsistent with Enterprise Studio due to font interpretation differences. Furthermore, line height in texts in Enterprise Studio was too large which caused some text to spill outside of the shape, where they used to be within the shape.

Any view in HoriZZon showing such discrepancies will automatically be corrected as soon as the view is committed again in Enterprise Studio.


Release 18 July 2019

This release is only available for the hosted solution Enterprise Studio Online. The release is not available if you are working with an on-premise installation of Enterprise Studio or Team Server.

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

Enterprise Analytics

 Support for population filtering on date

Populations of charts and portfolios can now be filtered on attributes of type "date". Example in a Landscape map:

Bug fixes


The list of Team Servers on the Open page of the Backstage view could be cut off if it contained more items than the page's height allowed.TP-9645

The icons on the Open tab of the Backstage view for deleting a model package and removing a local copy of the package were shown cut off.



For custom workflows, it was not possible to use data form fields based on custom enumeration metrics.


When an invited user clicked the link in an invitation mail to register with the Team Server, he or she would sometimes be redirected to the login page.TP-9744


When the Messages window exceeded 99999 messages, rows would be displayed in reverse order.



The addNewReference script method would inadvertently refuse to add a relation reference when this relation connects nested objects.


Release 11 July 2019

This release comes with a new licensing system and is only available for the hosted solution Enterprise Studio Online. The release is not available if you are working with an on-premise installation of Enterprise Studio or Team Server.

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


 Icon quality improvements
TP-8312, TP-9527

Following improvements have been made to icons used in the Enterprise Studio interface:

  • The icons in the Backstage view tabs have been updated to scalable images, so they also appear in correct sizes when working on high screen resolutions.

  • Various icons in the Import and Export sections on metamodel ribbon tabs (ArchiMate, BPMN, Amber) are now using scalable SVG-based icons, so that they now scale well to high DPI resolutions.

 Extension Check and Repair function

The Check and Repair function has been extended to repair more types of inconsistencies that are causing committed data to fail with the message "An error occurred during the creation of the contribution file".


 Possibility to call Sub-process from Call object

The Call object control to set a called element, now also supports calling a Sub-process. Previously, only processes could be set as called element. Selecting a Sub-process is only possible in case a custom profile with attribute "calledSubProcess" is assigned to the Call object. This custom profile definition can be created using the Metamodeler.


 Direction for association relation

The option to set the direction of the association relation has been added, as specified in version 3.1 of the ArchiMate standard. The direction is denoted by a half-arrow at the end of the line.


 Word wrap for entity names

It is now possible to wrap names of ERD entities in the Crows Foot logical view and conceptual view, using the  control on an entity. Click it before entering a name.


 Color view improvements

The values for a color view generated in HoriZZon are now sorted correctly, for example numbers low to high, enumeration values according to the literals. In addition, there is a control available for reverting the color scheme.

 Support for navigating cross-model relations

Navigating cross-model relations is now supported in HoriZZon. Objects with cross-model relations are marked with a  in HoriZZon. Clicking this control will  open the properties panel of the linked object, or  open the linked diagram or view.  In case an element has multiple cross-model relations (defined in Enterprise Studio), clicking the control will open the linked element that has been set in Enterprise Studio as the preferred relation. Example: 

 Improvements workflow requests overview
TP-9458, TP-9491

Following improvements have been made to the workflow functionality:

  • Deleting own requests in the requests overview page is now called terminate requests. In addition, the control for terminating a request has changed acccordingly.

  • Previously when deleting (now terminating) a request, the request would immediately be removed. From now on a confirmation dialog is first shown to ask if the user is sure to terminate the request, preventing that it could be terminated by accident.

  • The look and feel for "Group tasks" in the requests overview page now has the same look and feel as "My tasks" "My requests".

 HoriZZon logo is Home button

Clicking the HoriZZon logo will now take the user to the HoriZZon homepage, just like the home button does.


 New software licensing system for BiZZdesign tooling
TP-9051, TP-9372, TP-9523

This release of the BiZZdesign software comes with a new licensing system. In this licensing system the Team Server acts as licensing server. It replaces the CodeMeter Runtime licensing mechanism. Customers with the hosted solution can continue working with the release.


 Attribute date format in accordance with application language

Before, if a date attribute was defined in the Properties window, it would always be shown in the fixed format "dd-mm-yyyy". From now on, the Properties window uses the default short date format of the selected application language.

 Navigation improvements cross-model relations

Before, it was only possible to navigate cross-model relations via the model browser. Now, objects with cross-model relations are marked with a  in the diagram or view. If an object has only one cross-model relation, clicking this control will navigate the user to the linked object. In case of multiple cross-model relations, clicking the control will open a menu showing the relations. Clicking one will navigate the user to that object.  On behalf of navigating this object in HoriZZon, a preferred relation can be set by adding a checkmark next to one of the cross-model relations in the menu. 


 Word wrap for UML element names

It is now possible to wrap names of the following UML elements: Class and Use case in a Use case diagram, and Class, Data type, Enumeration and Interface in a Class diagram. To activate wrapping, click the  control before entering a name.

Bug fixes


The sorting order "Unsorted" of an ERD entity would revert to the default "Ascending" after closing and reopening the model.*



There were various alignment differences in views between HoriZZon and Enterprise Studio.


When using a color view in HoriZZon,  nested objects in a parent object were not very well distinguishable when they had the same color as their parent, especially when the child objects did not have a visible outline.


Team Platform

When a new user was provisioned through SAML SSO, or when a group membership changed, this change could take some time (up to 5 seconds) to be visible in HoriZZon.


Release 29 May 2019

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


 Improvements Check and Repair function

The Check and Repair function has been improved. Before, when some of the repairs caused claiming conflicts, all repairs were rolled back. Now only those that caused the conflicts are undone, the other repairs will still be applied. Also, the checking speed has increased significantly, and a progress indication has been added to the status bar.

 Additional changes for implementation new versioning system

As follow-up of the new versioning system of Enterprise Studio, several message boxes and dialogs in the application that displayed a detailed tool version in their caption or title, now show the new version of number plus date instead of the three numbers displayed previously.

 End of life 32-bit version Enterprise Studio

The 32-bit version of BiZZdesign software has reached end of life. This release is the last version for which a 32-bit version is available. This version is only available at request. If you are still using a 32-bit version of Enterprise Studio, you need to switch to the 64-bit version.


 Improvements in updating landscape map data

The performance of the creation of a landscape map has been improved.

  • For large populations for the relationships or Z-population elements (e.g., the whole model package), the set of elements actually appearing on the map is determined more efficiently.

  • Previously, data in a landscape map was automatically updated, which could lead to performance issues in case of large model packages. As of this release, real-time updating a landscape map is deactivated by default. The map is no longer automatically recalculated every time something is changed in the population. Only after explicitly clicking the map control for creating the map, real-time updating is activated again. Real-time updating can be deactivated again via the "real-time update" property in the map's Properties window.

Data integration

 Timeline start and end date available for import/export using Connection model

To enable import and export of start and end dates of ArchiMate objects from a Roadmap or Lifecycle view via a Connection model, the visibility of the corresponding attributes has changed from hidden to read-only.


 Changes in default workflows
TP-7767, TP-9088

Following changes have been made to the default workflows in HoriZZon:

  • The default worfklow "Review request" has been removed, the "Change request" is the remaining default workflow. Tasks in these workflows can be performed by any user regardless of their role. If needed, a review request workflow can be added again by creating a custom workflow.

  • Task assignment for the change request has changed. When starting a request, it is no longer directly assigned to a user. Instead, the request will become available to all Designer users who have been invited to the model package the request is related to, and have access to the site in which the request has been started.

  • These users will see the request appear in the Group tasks section on their workflow tasks overview. The user who is going to complete the request, can assign the task to him or her self.


 Online editing of self-defined information in sites

HoriZZon now supports adding and editing of self-defined model information in sites. To enable adding and editing own model information in a site, property fields can be defined in the model package the site is based on in Enterprise Studio, and published to a central database , resulting in editable element property fields in HoriZZon sites based on that model package. The property fields are defined in document schemas in a Connection model.

Each model package in which you want to have self-defined information available for its sites, needs to have a Connection model with document schemas. A model package can have its own document schemas, but you can also import existing schemas (from other model packages) from the central database.

Like any other regular property information, the self-defined information can be used for analysis goals.  The self-defined information and associated values will only be available in the sites, and not stored in the actual models on the Team Server. Users who need to be able to add and edit self-defined information in sites, must have the new Contributor role.

 Creation of custom workflows
TP-9245, TP-9299, TP-9363

As of now custom workflows can be made by creating workflow definitions in Enterprise Studio, and then uploading them to HoriZZon for use. A new BPMN model template "Empty model with workflow diagram"  is available specifically for developing custom workflows. When working with this template, four diagram types are available in the model to specify the different aspects for a custom workflow: Process diagram, Forms diagram, Metadata diagram, and Resources diagram.

Custom workflows can be created by any Designer or Lead Designer user, but can only be uploaded to HoriZZon by users who have the Lead Designer role.

Take note that model packages with workflow diagrams need to be stored on the Team Server, otherwise the workflows cannot be uploaded to Horizzon.

Workflow requests based on custom workflows can only be started by users who have the Designer or new Contributor role. The same applies to performing the tasks of these workflows. For more information about the new Contributor role, see item "New Contributor role" on this page.

Team Platform

 New Contributor role

The user roles in the Team Platform functionality have been extended with the Contributor role. Currently, the Contributor role can be used for users and groups who need to be able to start custom workflow-based workflow requests and to perform tasks from these workflows, but should not have Designer permissions.  The Contributor role stands in its own, there is no dependency towards the Designer and Lead Designer role, meaning that a Lead Designer or Designer user does not automatically have Contributor permissions.  The Contributor role will have more functions in near future functionality.

 Old Team Server environment no longer available

The Team Server has now been fully integrated into HoriZZon, the old Team Server pages have been removed permanently, meaning that the old environment is no longer available.

Bug fixes


The Check and Repair function would incorrectly list objects placed on top of a 'view legend' drawing shape as "not matching their place in the graphical hierarchy". After repairing it insisted it had deleted these objects, when in fact they were still intact and would be listed again at the next run.TP-8577

The Check and Repair function would keep mentioning that a view has "multiple graphical modules" run after run, meanwhile insisting it has repaired the defect.


In the uncommon situation where the same release of Enterprise Studio had been run before from a different installation folder, the application would unnecessarily display messages at startup about the "currencies.txt" and "exchangerates.txt" files not being found at the original location.


Enterprise Studio would crash when started for a second time, while the trial license dialog was still being shown.



Selecting one of the color view options in the Amber Quantitative Simulation results dialog would crash Enterprise Studio.


Data integration

Overwriting an existing Excel file was not possible when performing an export to Excel using a Connection model.


Technopedia® content was not updated anymore in Enterprise Studio.TP-9329

Enterprise analytics

Negative values of type "Money" were shown with a double minus sign in a score chart.


Enterprise Studio Online

In some cases Enterprise Studio Online would trigger the pop-up blocker installed at the browser and would not start.



When a color view was generated in HoriZZon, the relations were not properly colored.


Various object icons were no longer shown in HoriZZon, like the type icon of view references in a diagram, and model package objects in the site browser tree.


Workflow comments were not shown for finished requests, only for running requests .TP-9284
HoriZZon showed the text "Processing sign in" after authenticating successfully.TP-9551


The New (or New multiple) command in the context menu would be incomplete when the number of object types or views defined in the metamodel approached 100, resulting in menus getting cut off. To fix any incomplete context menus, the allowed number has been increased.TP-8031

The automatic relation layout Layout with bends no longer worked.


Reporting and printing

From Enterprise Studio 3.3.0 and onward, InSite Lite reports would often incorrectly resolve object (or view) hyperlinks in documentation fields, resulting in "page not found" errors when clicked.


Team Platform

Long running operations in Enterprise Studio would exceed the maximum authentication token validity.


When managing access of a group in the Team Server, an empty page would be shown.


It would not be possible to invite a user when the user's name contained a comma.TP-9489
In the Team Server settings page the e-mail configuration always required a username, but it should be optional.TP-9513

Release 18 April 2019

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


 Improved autosave operation

The autosave operation in Enterprise Studio blocks the GUI until it is done. To better inform the user about the progress, the autosave feature now announces in the status bar that it is running, and an indication is given of its progress.

 New names for application settings files

The files in which Enterprise Studio stores its application settings (*.ini, *.xml) have been renamed. They now reflect the new Enterprise Studio versioning scheme, where a version is identified by a major version number and a release date.

 Renamed installation folder and desktop shortcut

The name of the installation folder and the text in the desktop shortcut of Enterprise Studio have been adapted to show "Enterprise Studio" again instead of "EnterpriseStudio" (a space was added in between).


 Support for drawing second association relation between objects

To fully support the bi-directional nature of the ArchiMate  association relationship, drawing a second association between two objects will be detected by Enterprise Studio, regardless of the direction in which both associations were drawn, and the user will be asked whether he or she wants to refer to the existing relation or create the second one.

This is an improvement over the old situation, where the duplicate would only be detected if drawn in the same direction as the existing association.

 Quality checks for ArchiMate models

It is now possible to perform quality checks for ArchiMate models. The new feature allows you to specify modeling conventions in one or more convention views that can be linked to a model. Then views or models can be validated on compliance to these conventions. The results can be presented as a color view or in a workset.

Data integration

 Preselection of current object in form field when edited

In a Connection model, many form fields that allow selecting a model object or script viewpoint now preselect the current object when edited, thus making it easier to inspect its location.

Enterprise Studio Online

 Dedicated browser tab for Enterprise Studio Online

When starting Enterprise Studio from HoriZZon multiple times, the application will now appear in one dedicated tab, and will not create a new tab for each new invocation, as it did before. This new behavior only applies when using web browser Chrome, Firefox or Safari. Edge and Internet Explorer still have the old behavior.

Enterprise Analytics

 Population type and location info for charts and Landscape view

A tooltip will now show the type and location of populations in landscape views and charts. By clicking the population the user can navigate to the population object in the model browser.


 Improved look and feel workflow pages

The workflow pages have an improved look and feel. The following has changed:

  • Workflows on the overview page can now be sorted.
  • Workflows can now directly be managed via the  control that is available in each workflow on the overview page. There is also a manage entry in the sidebar menu on the workflow page. Managing workflows is only accessible for Administrator and System administrator users.
  • Each workflow type now has its own overview of open tasks and requests. When clicking a workflow on the overview page, a list of open tasks and requests is shown to the user:

  • Users can delete their own requests.

 Workflow tasks assignable to any user

Previously, a task could only be assigned to a user that had been invited for the site from which the task originated. As of now a task can be assigned to any user from the Team Server.

 Changes in dashboard creation, sharing and management

Dashboards can now be created and shared from the dashboard overview page.

Management of a dashboard can now be done from the dashboard page. Dashboards can only be managed by Administrator and System administrator users.

 Clearer error message when uploading incorrect workflow

When uploading a new workflow in HoriZZon, a more precise error message is shown when the workflow that is being uploaded is not correct.

Team Platform

 Changed session timeout settings

The setting for remember me cookies has been removed. Instead, three timeout settings for authentication tokens have been added.  The settings are located at the General settings in the new Team Server environment, and they are only accessible for a System administrator user.

Take note that the old Team Server page for general settings is no longer compatible and cannot be used anymore.

Bug fixes


The behavior of metrics of a numeric type on which scaling is applied, had changed; as of Enterprise Studio 4 the scaling factor was applied to the user value. As a consequence, reports showing the user value looked different in version 4. This has been reverted.



Some object properties of the basic profile were not visible in HoriZZon.


Data integration

During an Excel export with a connection model, relationships were incorrectly placed at the highest level in a model, rather than in the appropriate scheme.



The license expiry text on the About dialog in Enterprise Studio (on-premise installations only) would display the word "expires" twice.



The quick-create object controls (on the sides of an object) were missing for any object inside a collapsed container, for example a collapsed BPMN sub-process or ArchiMate business actor.


Two specific types of model data inconsistency ("objects without a parent" and "objects that can no longer be loaded") could lead to the inability to save or commit changes in a shared model package. They can now be detected and repaired using the Check and Repair function.


When an expanded Navigator tree shows a relationship of which one of its end objects has just been deleted from the model, collapsing and/or expanding this part of the tree would crash Enterprise Studio.


Reporting and printing

Enterprise Studio would crash when trying to print the contents of the Messages window.


Team Platform

It was not possible for an Administrator user to delete a model package in the Team Server integrated in HoriZZon (It was possible in the old Team Server).


Sometimes after updating a shared model package, restoring to an earlier point in the time was no longer allowed, and would result in an incorrect error message (citing conflicting changes as the cause).


The Team Server could exhaust all available database connections, resulting in a crash. Properties  maxTotal and maxWaitSeconds  are available in the Team Server database configuration file to enlarge the number of connections that must be available, and the waiting time for a connection to be returned.


Release 11 March 2019

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


 Navigation buttons in portfolio dashboard clickable for navigating to portfolio views

From now on the navigation buttons at the top of a portfolio dashboard can now be clicked to navigate between the different views of the portfolio.

 Direct access to manage workflows

Each workflow on the Workflow overview page now has a manage icon for direct access to the manage workflow page. The manage icon is only available to users who have the Administrator or System Administrator role.


 Assign profiles and documentation fields to diagrams and views

It is now also possible to assign custom profiles and documentation fields to viewpoint definitions, which makes it possible to add custom properties and documentation field to diagrams and views. Below is an example of a custom documentation field assigned to the Actor cooperation view:

Bug fixes


When prompted to refer an ArchiMate object to another ArchiMate object with an identical name after changing the name, the object in question would sometimes refer to an object of a different type, e.g. a Business object to a Business contract.


The performance of a Landscape map was poor when used in a large model package.


Specializations of the concept Technology node could get both the Technology and Default Life Cycle profile assigned. This also applied to the concept of Application component and the Application Life Cycle profile.


Enterprise Analytics

When a script was used to populate a matrix chart, the values "relationProperty" and "objectProperty" for attribute "matrixType" were not accepted because they were converted to lowercase.


In a table chart, for currency symbols with more than one character only the first character was displayed.



When creating multiple new attributes in an ER diagram at the same time, the attributes would be sorted incorrectly. From now on they will be sorted in the order they are specified in the New Multiple dialog.



When opening a metamodel in the Metamodeler, certain profile assignments would get lost. Now, previously made assignments to viewpoints, object references, collections, specialized relations and all concepts from the Component metamodel are preserved.



Creating objects using the New multiple command did not properly create references to already existing objects outside of the current model, but instead created duplicate objects.


In rare cases, saving a model package stored in the Team Server as an XMA or XMAM file would produce a file that Enterprise Studio would refuse to open.


Creating one-on-one typed objects (like BPMN and Amber objects) using the New multiple command, and selecting the Match names with existing objects option, would result in corrupted views, due to having references to these objects.


Right-clicking in a Cross-reference Table and the Property Table would cause a crash.


Team Platform

A user was not always removed from the corresponding groups when originally provisioned through a SAML connection.


View filters and viewpoints

When a viewpoint that applies to all diagrams was used in a standard report, any diagrams not open at the moment the report was generated, would not have the viewpoint applied.


Release 8 February 2019

Bug fixes


The Enterprise Studio application logging would log unnecessarily many warning and errors.


Release 6 February 2019

Bug fixes


The Attachment and Alignment toolbars were always visible on a new install of Enterprise Studio.


Release 1 February 2019

Bug fixes

Team Platform

Upgrading the Activity Console would fail if the data being upgraded was last "touched" by a pre 3.3 version of Enterprise Studio.


Release 29 January 2019

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.

Enterprise Studio versions older than 3.3 are not compatible with the Team Server of the current release. For more information, please refer to the release-specific information.

New features and enhancements


 Enterprise Studio application logging and crash reporting
TP-8356, TP-8475, TP-8506

As of now, application logging is always enabled in Enterprise Studio. It is used to collect information regarding operations and events in Enterprise Studio. It is also possible to set the level of logging, which determines the amount of detail in the information that will be collected.

In case of a crash, information about the crash is automatically collected in a crash report, which can be stored if needed, for example to send to BiZZdesign for analysis. If custom application logging is activated, the files from the logging will automatically be included in the crash report.


 Resource roles allowed on a lane set

In a BPMN diagram, a resource role can now be dropped onto a lane set, and selected as the primary resource role for a lane set.

 Hierarchy for resources and resource roles

Resources and resource roles can now be nested in a BPMN resources diagram. Example of nested resource roles:

 Improved BPMN import and export
TP-5015, TP-5489, TP-5733, TP-7761

The import and export function of BPMN has been re-implemented to resolve several issues that were raised in the past.

In addition, a function has been added to import process maps from a Lean model into a BPMN model. If defined, the process map and improved process map are imported as separate BPMN processes in the BPMN model.

 Ability to move message icon on message flow

The position of the message icon on a message flow can now be changed by dragging it to the desired location.


 Hints for form fields in custom workflow

In custom workflows, hints can be defined for form fields for a workflow to make a form entry more intuitive.

Team Platform

 Completion Team Server integration with HoriZZon
TP-7796, TP-7800, TP-7820, TP-8099, TP-8102, TP-8247, TP-8249, TP-8328, TP-8348, TP-8389, TP-8390, TP-8804

The integration of the Team Server in HoriZZon is complete. The new Team Server interface is now available to everyone, also for users who only work with the Team Server. Opening the Team Server will initially show the old interface, but there is an entry to access the new interface. The completion includes the following:

  • Users and groups can now be filtered and sorted. They can be filtered on name (for users first name or last name), display name or e-mail address, and sorted by name (for users first name or last name), display name or create date.

  • Model packages and projects can now be filtered and sorted. They can be filtered on name or description, and sorted by name, description or create date.

  • User access for model packages and projects can now be managed when inviting users and groups, and also after they have been invited.

  • The Manage access links next to the shared model packages and projects on the Open page of the Backstage view now refer to the new integrated Team Server.

  • The complete Team Server settings are now available, including general, e-mail, database, license, and authentication settings, and audit log.

  • Newly invited users can now register in the new environment.

Bug fixes


Executing Enterprise Studio from the command line with a script that specifies a log file in a non-existing folder would crash the application. Instead, Enterprise Studio now shows an error message.


The Check and Repair function was unable to delete a faulty object when (part of) its data was missing (message "Modules failed to load module ...").


When a custom configuration is located in a folder with a name containing an "é", the application would crash.


The pages in the Backstage view contained various visual glitches, such as wrong colors, unreadable texts, wrongly sized items.



In Amber models, attribute values from the Responsibility and Task profiles of actions in collapsed blocks would not be shown when generating a label or color view.



When modeling a Landscape map, a script error would appear when trying to define a relation population (ZX or YZ) after having transposed the map before that.


It was possible to perform an auto layout on landscape maps, which would scramble the layout.


The influence relation was missing in the definition of the Requirements Realization view in ArchiMate. It is now an allowed relationship on the view.



It was not possible to set loop characteristics for call activities.


A participant in the BPMN example model Pizza Collaboration had the wrong name.


Enterprise Studio Online

When a username or e-mail address of a user had changed, the Team Server would be shown twice.


In Enterprise Studio Online, application settings of older versions were not preserved when the application was upgraded.



The control for opening the security profile of a Security Domain or Control Objective in an ArchiMate or ERSM model was no longer visible.



If, for a custom workflow, a membership creation event was consumed before the corresponding group creation had been processed, the workflow API produced errors.


The wrong routing was used when navigating to the project page via a user page.


The score chart and pie chart could show the wrong currency in case of aggregated money metrics.


Workflow validation failed for user group candidates.


Processing a sign-in failed in Internet Explorer when using an external identity provider.



The Metamodeler would sometimes export a custom menu structure if nothing had been changed, thus unexpectedly overwriting the default menu structure resulting in a missing entry for the Landscape map view. From now on, the menu structure will only be exported if it has been customized.



In the uncommon situation where a custom configuration would define an "onEndLabelEdit" handler script for a concept that deleted the reference of which the user is editing the label, Enterprise Studio would crash when editing such a concept.


Clicking on a hyperlink to another view in the documentation window of Enterprise Studio would sometimes lead to a crash.


Enterprise Studio would sometimes crash when logging was enabled and a specific text was present in a documentation field.


A number of symbol definitions were no longer accepted, and would show nothing when selected using the Change Graphic Shape command.


Scrolling down in a custom metric value list containing more than ten items would cause a script error.


Aggregate metrics could show the wrong value in charts in case their type was numeric (integer, real, money) and a value mapping had been defined.


Reporting and printing

For models in which some diagrams were located directly under the model (i.e. not directly or indirectly, inside a model folder), the Print dialog would allow printing of only one of those diagrams per session. Also, the active diagram would not be preselected when the Print dialog opened.


An RTF report of an Amber model no longer contained "Items" sections, and were therefore not reported.



Scripts that (inadvertently) add a collection (List, Set, Index) to itself would crash Enterprise Studio when this collection was displayed or traversed.


Team Platform

When pushing a commit and updating a working copy would happen at the same time, it could lead to a corrupt state in the Activity Console database.


The presence of a username attribute in the SAML 2.0 responses caused issues during SAML 2.0-based Single Sign On.


The Team Server would sometimes not be reachable from Enterprise Studio.


The Activity Console would crash when dealing with a large number of commits.


Links on the user overview page in the new Team Server interface referring to the old Team Server did not work correctly.


The filter field on the Groups page showed the wrong filter text (filter users).


Users with special characters in their name (and in their Windows user folder) had issues with their team data folder.


After disabling SAML a user could still authenticate with SAML until the server was restarted.


An empty commit was saved when downloading a commit failed.


The button for uninviting a group was not working.


An Administrator or System Administrator user could not revoke a model package or project invitation on the group page.


On the user overview page the way of collecting sites for an unregistered user was not correct.


A specific collaboration error scenario, potentially leading to loss of elements recently added to a view, was fixed. It involved updating a local model package with changes from others, right after attempted changes were rolled back because of conflicting claims.


View filters and viewpoints

Viewpoints generated with the Generate view for function that were saved with a version of Enterprise Studio older than 3.2.0 would 'forget' part of their settings when opened again using Enterprise Studio 3.2.0 or later.


Color view scripts that output reference objects instead of referred objects did no longer assign a color to these references.


Release notes 2018

For more information, see Release notes archive 2018

ArchiMate® is a registered trademark of The Open Group.