Skip to end of metadata
Go to start of metadata

The release notes show the new features and enhancements that have been included in Enterprise Studio, HoriZZon and the HoriZZon Server, and the issues that have been fixed.

For each new release, you need to migrate your model packages with metamodels embedded (.xmam), or stored in your personal storage or on the HoriZZon Server  to materialize the changes and fixes in the release.

Customers with a cloud solution will be updated first. For the update scheme, please refer to Maintenance windows for the cloud solution. The installer files for the on-premise solution will be updated later. Not sure which solution you have? Check out Which BiZZdesign software solution am I using?

On this page:

Expand/Collapse All

Release 24 September 2021

Availability: Cloud hosted only

New features and enhancements

Team Platform

TP-10913, TP-12381

The model package and project invitation pages in Enterprise Studio and in HoriZZon now better reflect who can be invited: users and groups (instead of only users).

Bug fixes

Data integration

In some specific cases, the BiZZdesign Open API call getObjects could return too many associated data blocks.


Enterprise Portfolio Management

Refreshing portfolio charts would sometimes cause a "does not evaluate to an object" script error to occur.



Some icons in models were not rendered correctly in HoriZZon, for example, icons used in meta-object attributes in a Connection model.


Using search operators ? * and " " in the HoriZZon search did not work anymore.TP-12364
The format for dates used in the user export to CSV was not readable for other tools and has changed to the ISO 8601 standard. Example of the new format: "2021-08-28T23:45:12Z", where the time is presented in UTC.TP-12404
Using one of the characters \  +  ,  !  (  )  :  ^  [  ]  \"  {  }  ~  /  in the HoriZZon search would cause an error.TP-12405

Release 23 September 2021

Availability: Cloud hosted only

Please take note that this release is a fix on the 23 August 2021 release, not on the 13 September 2021 release, which is a limited release. The 23 September 2021 release, therefore, does not include the features and bug fixes of the 13 September 2021 release. The 24 September 2021 does include these features and fixes.

Bug fixes

Team Platform

The SCIM user provisioning for Azure AD was failing, making it impossible to provision new users.


Release 13 September 2021

Availability: Cloud hosted only, for limited amount of customers

New features and enhancements



Dates in HoriZZon are now shown in the formatting of the selected application language. Before, English formatting was always used. Example:


From now on, when a user has been inactive during a HoriZZon session but leaves the browser window with HoriZZon open, a message will appear asking the user whether he or she wants to continue or sign out. The session will be ended due to inactivity and the user will automatically be signed out. If the user does not respond to the message he or she will automatically be signed out.


The sharing function now has the option to share embedded views via a direct link. This option is suitable for embedding views in Confluence using the Iframe macro, but can also be used on other platforms where embedding via a direct link is desired, for example, Microsoft Teams. To share a view via a direct link, use the Embed URL option.


In addition to the user overview page and the user export file, the user's last activity date is now also shown on the individual user page.

Team Platform


A user's Personal Storage in Enterprise Studio no longer becomes inaccessible for the user after changing the username (e-mail address or Windows login name) to connect to HoriZZon. 

Bug fixes


Creating a Data association or Compensation association relation using the Create panel did not work.



Dashboards with time dimension filters were displaying issues due to the hardcoded time filter.TP-12094

When a generated tooltip view was pinned, the push-pin did not correctly indicate it. It had the wrong color.


Release 23 August 2021

Availability: Cloud hosted only

New features and enhancements

Team Platform


It is now possible to enforce 2-step verification for all users when signing in to HoriZZon. To require the use of 2-step verification, select the Require 2-step verification for all users option at the General settings in HoriZZon. When set, all native HoriZZon users must set up 2-step verification. If they have not yet set up 2-step verification, they must register a device for authentication after signing in before they can continue.

As indicated, 2-step verification is only available for native HoriZZon users, it is not available for users signing in using an organizational account.

The setting for 2-step verification is only accessible for System Administrator users. If you are working with the hosted or hybrid solution and wish to have the setting activated for you, please contact BiZZdesign Support.

For more information, please refer to Enforcing 2-step verification for signing in to HoriZZon.

Bug fixes


The allowed number of characters for e-mail addresses in HoriZZon was limited to 50.


The Explore button on the inspect page for an object was not shown for Consumer users.TP-12327


The validation checks in the Metamodeler did not check on empty enumerations and struct types. They were accepted.TP-10081

The validation checks in the Metamodeler did not check that custom viewpoint names are sufficiently different from any other viewpoint and concept when names only differed in case (for example, "abc.mmd" and "Abc.mmd").



When a UML class containing typed parameters was copied to another model package without copying the type classes too, the copied class resisted changes, causing various script errors.


Release 16 August 2021

Availability: Cloud hosted only

New features and enhancements

Team Platform


Before, when authentication with SAML failed when a user tried to sign in to HoriZZon, an "Internal server error" message was shown. From now on, a clearer error will be shown on the sign-in page if authentication fails.


In addition to viewing the history of a single object, relation, view, or diagram, it is now also possible to view the history of multiple objects, relations, views, and diagrams in a model package at once. Scripts are available to retrieve the desired information, one for viewing the history of objects and relations and one for viewing the history of views and diagrams. In the script, you specify the metamodel in which you want to search and the type of object, relation, view, or diagram. It is also possible to search all types of objects, relations, views, and diagrams in the metamodel. Example:

The results can be used for, for reporting goals, for example export to Excel. 

Please take note that the model packages and projects in which you want to perform the search need to be on the latest tool configuration. If they are not yet, you first need to migrate them.

For more information, please refer to Viewing the history of multiple objects, relations, views, and diagrams at once.

Bug fixes

Enterprise Portfolio Management

There was a problem with the aggregation of portfolios, which resulted in incorrectly calculated chart percentages.


Team Platform

When sending a test e-mail for the HoriZZon configuration failed, the user interface did not show the details received from the server in the notification message.


View filters and viewpoints

In the window for generating a color, label, or tooltip view, when clicking on an endpoint to activate the color/label/tooltip, Enterprise Studio would navigate to another view where the endpoint object was drawn.


Release 13 August 2021

Availability: Cloud hosted + On premise

Bug fixes

The PATCH command in the BiZZdesign Open API to update an existing document for an existing object was failing with a generic 500 response.


Release 11 August 2021

Availability: Cloud hosted only

Bug fixes

Team Platform

When configuring a storage place for a SAML-enabled environment using a local installation of Enterprise Studio, a JavaScript error was thrown.


Release 2 August 2021

Availability: Cloud hosted only

New features and enhancements

Data integration


When exporting a Kibana connection, the index name is now checked for validity. If the index name does not meet the requirements, it will be clearly communicated in a message. Requirements for a valid Kibana index name are:

  • Lowercase only
  • Cannot include the following: \ / * ? " < > | , # or the space character
  • Cannot start with a - _ or +
  • Cannot be . or ..
  • Cannot be longer than 255 characters

Indices prior to Kibana version 7.0 could contain a colon (:), but that has been deprecated and will not be supported in versions newer than 7.0. Current Kibana version in HoriZZon is 7.7.

TP-12213, TP-12239

When working with Connection models, any collections (with entities and links) in the model package can be included when performing an export. It means that externally managed data can now be used in, for example, Excel or Kibana. When creating a Connection, a model context needs to be set that should act as the root for looking up and creating objects in the context of the connection. To use collections for the export, they can be set as the model context of a Connection.  As mentioned before, the use of collections is only suitable for export purposes; when performing an import, externally managed objects are excluded. Example of an Excel connection:


Performance improvements have been made for selecting objects in Enterprise Studio that have many data blocks.



In addition to English and Dutch, HoriZZon is now also available in French and German. To switch application language, click the profile icon at the top, and under Application language, select the desired language.


The functionality for zooming in and out on HoriZZon views using the mouse wheel or the  +  and  -  key of the keyboard, has been removed due to inconvenience reasons. It still remains possible to zoom in and out on views using the zoom buttons that are available in each view and using the  +  and  -  keys of the keyboard.

Team Platform


From now on, the default attributes (e-mail, first name, last name, member of) for user synchronization and authentication with an external identity provider using the SAML 2.0 standard can be configured to a custom name to match the attributes used by the identity provider.

In addition, it is now possible to change the SAML service provider's maximum authentication lifetime value in HoriZZon. This setting controls the service provider's session timeout value (default value 1 hour). Some identity providers have higher session timeout values, so it may be necessary to change this setting's value to align with your identity provider's session timeout value. This setting was already available for customers with the hybrid or hosted solution.

If you are working with the on-premise solution, the attributes and authentication lifetime can be set by a HoriZZon System Administrator on the SAML authentication settings page in HoriZZon. If you have the hybrid or hosted solution, please contact BiZZdesign Support if you wish to have settings configured for you.


For safety reasons, restoring a model package or project to a previous state (via the timeline) will from now on only be possible for users with the Lead Designer role. Before, also users with the Designer role were able to do this. Viewing a previous state remains possible for Designer users.

Bug fixes


Setting metric values in the Scenario analysis view would raise error messages.



Navigation in a HoriZZon view from a BPMN Call activity to its called process (via the plus sign on the object) did not work anymore.



Sometimes the scope of a site was broken after changing it by setting a different default view. Setting the scope of a site now works similar to making a selection for edit permissions when inviting people to a model package or project.


Relations stored directly under a model were always out of scope in a site.


In some cases, references to other objects were shown twice at the object properties in a HoriZZon view.


Users without any role in HoriZZon could access Kibana. From now on, the Consumer role is needed.TP-12257
Color views based on data block values or enumeration attributes were not always working. TP-12277


Simultaneously left and right-clicking an object's Properties form would make Enterprise Studio crash.


Team Platform

When running an LDAP import, it would incorrectly check for licenses.



It was not possible to copy UML classes from one model package to another. When trying to, error messages would appear.


In some cases, inviting a user to a model package or project via HoriZZon could result in an error.


A session of a user in HoriZZon would be extended automatically when the web browser kept HoriZZon open, which made the session infinite. This is no longer possible. Additionally, the new default session time (configurable on the General settings page of HoriZZon) will be 12 hours (43200 seconds) from now on (before, it was 30 minutes). All existing environments that are using the old default value of 1800 seconds as the timeout, will see this increased to a 43200 (12 hour) timeout. If you want to start using a different session timeout than the new default 12 hours, you will need to explicitly set a new value.

If you are working with the hybrid or hosted solution, please contact BiZZdesign Support if you wish to have your session timeout changed.

TP-11909, TP-12300
Changing the roles of a group could make the server unresponsive.TP-12151

Release 5 July 2021

Availability: Cloud hosted only

As of January 2023, BiZZdesign no longer supports Windows 8.1 as environment for local Enterprise Studio installations. With this, BiZZdesign is following the Windows lifecycle policy.

New features and enhancements



The HoriZZon user export now also shows the date a user has last committed data and the total number of commits the user has made. Example:

(for the example above, a number of the intermediate columns have been hidden)



The warning message that appears when deleting objects in the model browser that have references to other objects, has improved, making it more clear which objects the user will be deleting.


Changes have been made that improve performance when saving changes or refreshing diagrams and views in Enterprise Studio.

Bug fixes


Clicking on a background image in a HoriZZon view would show the error message "Error loading object".TP-11062
When clicking on a hyperlink in HoriZZon that links to a view that is out of scope, nothing happened and no message was shown.TP-11729

Cache settings allowed for temporary browser-side caching of certain potentially private content.



In some situations, copying and pasting data between model packages would make Enterprise Studio crash.


Team Platform

When a prepared working copy was downloaded and claims were revoked, the creation of a backup of the model package was failing when not all commits were available.



An incorrect message was shown when deleting a workflow from HoriZZon.


Release 24 June 2021

Availability: Cloud hosted only, for limited amount of customers

Bug fixes

View filters and viewpoints

Various issues with color views in HoriZZon have been resolved.

TP-12202, TP-12207

Release 21 June 2021

Availability: Cloud hosted only, for limited amount of customers

New features and enhancements



The Metro map is a new view type for ArchiMate modeling. It can be used to visualize (data) flows and processes in a business-friendly manner as a metro (underground/subway) map. The Metro map can be added via New > Presentation > Metro map in the ArchiMate model context menu in the model browser.

Metro maps can be used to visualize existing objects and relations (only Flow and Triggering). It is not possible to create new elements. The Metro map has a canvas menu that includes showing/hiding the legend, laying out the entire view, or only the relations and coloring options.


The Strategy motivation view now supports using the Serving, Flow and Triggering relation to model relationships between courses of action.

Data integration


The beta3 version of the BiZZdesign Open API is available, introducing endpoints for managing data policies.  This includes the possibility to assign editors to data blocks and to set up data update schedules for data blocks.

For more information and the latest open API documentation, please refer to   BiZZdesign Open API .



Various improvements have been made for HoriZZon session handling, including an option for additional session validation. The HoriZZon session settings now have an option for IP address session validation as an additional security measure. The session settings are only accessible for System Administrator users. If you are working with the hosted or hybrid solution and wish to have the new setting activated, please contact BiZZdesign Support.

For more information, please refer to Configuring HoriZZon session settings.


When the list view (instead of grid view) is used on the Views page or on the model browse page of a site, the views on the page are now presented with their icon instead of a general icon. (This was already available for objects.) Example of the model browse page in list view:


The user invitation e-mails that are sent by HoriZZon have been updated to make them more uniform and more recognizable. References to HoriZZon in these e-mails, now use the name "BiZZdesign HoriZZon" followed by the name given to your HoriZZon portal. (In the example below, the portal name is "BiZZdesign".)



The title of the first (leftmost) column "Object" of a script-generated table chart, representing the objects in the table, can now be renamed via the chart's metadata. Replacing the default metadata value with the value objectHeading, enables renaming the title of the object column. Example:

s = Structure();
s.add("metadata", "objectHeading");
s.add("property1", "Asset value");
output s;

The chart needs to be put in edit mode to rename column headers.

For more information, please refer to Renaming the object column title of a scripted table chart.

Bug fixes


The icon used for the Implementation and Migration view was not rendered correctly in HoriZZon.

Please take note that in order to resolve an incorrectly rendered icon, you need to do the following: after having migrated the model package, make a change (any) to the view on which the icon is, and then commit the changes. After that, the icon will be rendered correctly in HoriZZon.


The Properties form (accessible via the control on ArchiMate objects and relations) was not available on the Composition and Specialization relation.



BPMN user tasks no longer displayed their icon.


Enterprise Portfolio Management

Scoring portfolios was hampered by delays when a model package contained changed default view settings.



The name of a viewpoint saved in an ERD model could not be adjusted.TP-8028

It was not possible to rename attributes in an ERD model via the model browser. Renaming an attribute raised a script error.



The color sorting in color views was not working correctly when applied to data block properties of type enumeration.

Please take note that this fix raised another issue. For more information, please refer to the known issues for this release.


When using more than one language in a model, in some cases, components in the model package tree, for instance, used when inviting users to a model package, were not translated correctly.


Special characters (like ë, ü or ß) in documentation fields were replaced by '?' in HoriZZon.TP-12117

Release 7 June 2021

Availability: Cloud hosted + On premise

Please take note that the HoriZZon Server in this release is dated 9 June 2021.

New features and enhancements

Data integration


In addition to objects and relations, data policies (and data entry) can now also be used on diagrams and views. When a data block definition is be linked to view and/or diagram types, the associated data block in HoriZZon will be available on all views and diagrams of the chosen types, and policies can be set for them on the policies page. Example of data policies for the ArchiMate Application behavior view:


Data policies now show information about when they were last updated and by whom. The information is available for the editors and for the data update schedules.

Bug fixes

Data integration

Object attribute values containing multiple values, like lists of object references, were no longer sorted vertically when shown at the object properties in HoriZZon.


Enterprise analytics

Table charts cells containing multiple text lines (for example, documentation), were not displayed correctly in HoriZZon, text lines would overlap. If you have charts that are affected, please do the following to restore your charts:

  1. In Enterprise Studio, select the table chart containing overlapping text.

  2. First click the Reset size button on the chart border, and then click Refresh .

  3. Open the chart settings window, and on the Representation tab, click Sort order. In the Column sort order window, click Reset .

  4. Perform steps 1 to 3 for each affected table chart in your model.

  5. Since Enterprise Studio does not consider these changes to be actual model changes, you cannot yet commit. Make a minor change to your model that is considered an actual change, for example, moving an object in a view. It will trigger the ability to commit.

  6. Commit the changes and when these have been synchronized, check the affected table charts in HoriZZon.



E-mail messages from HoriZZon were not always sent out properly, in particular the messages containing the license expiration reminder and grace period activation.


After switching to another model language, HoriZZon would not show one or more sections of properties for an object.TP-12156

Release 21 May 2021

Availability: Cloud hosted only

New features and enhancements



The ArchiMate Principles view is now located in the ArchiMate > Motivation submenu of the default context menu for creating new views in the model browser. This location is more in accordance with the ArchiMate 3.0 specifications. (Previous location was the Implementation and Migration submenu)


The following default attributes on ArchiMate objects have been deprecated and are therefore no longer available:

  • relatedGoals
  • relatedPrinciples
  • relatedGuidelines
  • related_deliverables
  • related_programs
  • objrepl (replication)
  • objrepls (replication number)

On Goals, Principles, and Guidelines, also the following attributes have been deprecated:

  • relSource
  • relOwner
  • relStatus

If you were relying on these attributes, please contact BiZZdesign Support for support on migrating to an alternative.

Data integration


Data blocks in HoriZZon sites now support the use of text fields. Fields of type "text" can be defined in the data block definition, resulting in text fields using Markdown format in the data blocks in HoriZZon. The field offers several formatting options for the text, like bold text, numbered lists, and including links.



In Enterprise Studio, it is possible to directly navigate from a decision in a Decision model view to the corresponding decision table to view the information. Now HoriZZon sites also support navigating from a decision to the corresponding decision table by clicking the control in the object.



Usually, when performing an auto-layout of type hierarchical layout on an ArchiMate view, the layout direction is top to bottom. If you prefer to use a different main direction for the hierarchical auto-layout, it can be configured by setting a tagged value on the view using the following script:

view = selection[1];
view.setTaggedValue("fullLayoutDirection", "LR");

The last section of the script is the variable value for the layout direction. Allowed values are:

  • TB (default): Top to bottom
  • LR: Left to right
  • RL: Right to left
  • BT: Bottom to top

For more information, please refer to Configuring the layout direction for the automatic layout of ArchiMate views.

Bug fixes


When setting the loop for a BPMN call activity, and also setting a called element for it, the controls for both settings are placed on top of each other, making the object information invisible to the user.


Data integration

When retrieved via the Open API, data blocks were not migrated to the latest version of the associated data block definition.TP-12018

When multiple data blocks are defined for a single object type, they should be sorted in alphabetical order (based on Namespace+Name) in HoriZZon but instead, they were appearing in random order.


Enterprise analytics

Charts could get broken due to invalid (deleted) metrics.TP-11907

Matrix charts sometimes were not rendered correctly in HoriZZon, with cell contents shifted horizontally and/or vertically, overlapping row and column boundaries.



The model tree of the site browser would show diagrams of 1-on-1 models (e.g. BPMN, UML models) in duplicate.



When adding a value to a custom ArchiMate object property that refers to an object of the same type (for example, a related business function), an error message would appear if this was done using the properties form on the canvas.



Generating a view for a Roadmap view with the Lay out afterward option selected would raise an AutoLayout error.TP-11239

Using the Show View History function on a newly created, not yet committed view would crash Enterprise Studio.



When a script calls method removedTaggedValue with more than 2 arguments, Enterprise Studio was likely to crash.


The scripting method findObject sometimes would not find an object.TP-11936

Team Platform

In some situations, Administrator users were able to perform reflected XSS.

TP-11835, TP-11974


In some cases, optional workflow fields would behave like required fields.


Release 14 April 2021

Availability: Cloud hosted + On premise

New features and enhancements

Data integration

Availability of the ArchiMate CSV import and export functions in Enterprise Studio will end in April 2022 . Until that time, the functionality will enter the "Extended Support" state, during which BiZZdesign will limit support to priority 1 and 2 issues. For importing CSV files in your ArchiMate model and exporting to CSV, please use an Excel connection. For more information, see  Data integration with Excel .



Following the earlier announcement in the 29 March 2021 release regarding the end of life for LeanCoach models in March 2022, it is from now on no longer possible to create new LeanCoach models in Enterprise Studio. Existing models can still be opened and edited.



When defining a custom viewpoint, it is now possible to also add profiles, next to concepts and relations, and specify graphical properties for these profiles (for example, changing the graphic shape). When assigning such a profile to an object during modeling, the specified graphical properties for the profile will override the standard graphical properties of the concept.


When defining a custom viewpoint definition, it is now possible to use own custom icon symbols for the concepts in the viewpoint definition. To do this, the custom icons need to be added to the Symboldefinitions folder of the tool configuration. When creating a concept in the viewpoint definition, the custom icon can be selected by entering its name (or a part of the name) in the search box at the top of the icon selection window:

Please make sure to add your custom icons only to a custom tool configuration, NOT to the standard tool configuration.



A selection of the most used AWS architecture icons has been added to Enterprise Studio to support cloud architecture modeling. They can be selected using the Change Graphic Shape function via an object's context menu.

Strategy and business modeling (BMC)


The Value stream concept can now be added to the Activities section of the Business Model Canvas.

Bug fixes

Data integration

Links between entities (from external data) sometimes could not be navigated in Enterprise Studio, causing scripts and the Navigator to fail to discover these relationships.TP-19222

Editing money values above 10.000.000 in a data block would prevent editing any other value within the data block.



HoriZZon would reload every 5 minutes, which could result in losing unsaved changes or a blinking HoriZZon window every 5 minutes.


Team Platform

The web browser did not automatically authenticate in HoriZZon by redirecting to the authentication every 5 minutes. An error was displayed when a request failed due to authentication.TP-12008

In some situations, users could access user and group information that was not required for their role.


Release 7 April 2021

Availability: Cloud hosted + On premise

Please take note that Enterprise Studio in this release is dated 29 March 2021.

Bug fixes

Team Platform

The user export to CSV was not working anymore.


Release 1 April 2021

Availability: Cloud hosted only

Bug fixes

Team Platform

Group membership access to sites was not updated.


Release 29 March 2021

Availability: Cloud hosted only

New features and enhancements



The Landscape map now supports defining a hierarchy in the X- and/or Y-population, enabling the user to show the chart for only population elements that are defined at a certain hierarchy level.

By specifying the populations that must use hierarchy at the Hierarchy settings () and the used relation (aggregation/composition), adding the right filters, hierarchy can be included in the chart. Example:

For more information, please refer to Using hierarchy in an ArchiMate Landscape map.

Data integration


The following changes have been made to data block editing to make editing go quicker and more efficient. These changes apply to editing data blocks in the Properties panel as well as the Data entry page of a model package.

  • Click on a data block field to directly edit it.
  • Go through the data block fields and buttons using the Tab key.
  • When leaving a field after editing it, any changes to the field will automatically be saved.
  • When editing a field, press Enter to save the changes and exit the field edit mode.
  • When editing a field, press the Escape key to exit the field edit mode. Any changes in the field will be discarded.

Enterprise analytics


The following features have been added to the matrix chart. To be able to use them, the Advanced options setting needs to be activated on the Definition tab of the chart settings.

Directly creating and deleting relations, editing relation properties

The matrix chart now supports directly creating and removing relations and edating relation properties for the "Cross-relation" and "Cross-relation property" matrix types. In order to do this, the chart needs to be put in edit mode (Representation tab). After that, existing relations in the chart can be removed and new relations can be added ("cross-relation" matrix) or existing relation properties can be edited ("cross-relation property" matrix).

Cross-relation matrix:

Cross-relation property matrix:

For more information, please refer to Directly editing relations in a matrix chart.

Including hierarchy in X- and Y-population

The matrix chart now supports defining a hierarchy in the X- and Y-population. It enables the user to show the chart for only population elements that are defined at a certain hierarchy level. Use of hierarchy is supported for each matrix type. By specifying the populations that must use hierarchy (Representation tab) and the used relation (aggregation/composition) in the hierarchy (Definition tab), and adding the right filters (see next item), a hierarchy can be included in the chart. Example:

For more information, please refer to Using hierarchy in a matrix chart.


Filtering on chart populations now also supports using OR filters and filtering on related attribute, profile, or metric. The options are available in all chart types. Only in the matrix chart, the chart setting Advanced options needs to be activated (Definitions tab) to enable using these options.

OR filtering

Until now, filters in a charts only supported AND filtering. Now they can also be used as OR filters. To switch from AND to OR filtering, click  in the chart population window and click  in the filter section title. To switch back to AND filtering, click .

Filtering on related attribute, profile or metric

Filtering the population of a chart is now also possible on related attribute, profile, and metric. These are filters on attribute values, profiles, and metric values of objects that are accessed via a relation. An example is shown below. The table chart shows the devices that (via application components) serve three business processes.

For more information, please refer to Filtering the population of a chart.


Availability of LeanCoach models in Enterprise Studio will end in March 2022. Until that time, the functionality will enter the "Extended Support" state, during which BiZZdesign will limit support to priority 1 and 2 issues.



The text of the slightly misleading "Could not parse license key according to new format" entry in the EnterpriseStudio.log (Team Data folder) has been changed to better reflect what is happening, namely that the license is being verified.

Bug fixes


It was not possible to move a BPMN data store to another Items collection in the model browser.



It was not possible to rename new custom viewpoint definitions in the model browser or Properties pane and to use the translation table on them.



In large model packages, the first model browser search action would take considerably more time than subsequent searches.


Team Platform

Users that are provisioned by an identity provider were not allowed to edit properties on their user page that are not managed by this identity provider.


Access tokens could have been abused in HoriZZonTP-11832
Migration of data in the Activity Console took too long, which resulted in the message "Unable to establish a connection to the Activity Console." in Enterprise Studio.TP-11933

View filters and viewpoints

A color view that displays object values and has customized colors could crash Enterprise Studio if one of those objects has since been deleted from the model.


Release 15 March 2021

Availability: Cloud hosted only

This release only includes a new HoriZZon and HoriZZon Server version.

New features and enhancements


TP-7120, TP-11950

The following features have been added to optimize the process of creating sites:

  • When creating a site, first a table with all available model packages and projects is shown from which one can be selected. The table is searchable and can be sorted and also shows when each model package and project has been last updated. This makes searching for the desired model package or project easier, especially in the case of large numbers of packages and projects.

  • Creating sites is now also possible from the model package and project overview page. The title bar of the Sites section on the page has a plus control to add new sites. Example:

Bug fixes

Data integration

Adding a money value to a data block field, removing the value, and then adding it again would result in an error, preventing the user from saving the latest money value.


The validation of Open API access tokens needed improvement.TP-11944

Team Platform

There was a security issue in the group and client management pages for users with the (System) Administrator role.TP-11831

Insufficient input validation was performed on certain model package management operations.


Release 1 March 2021

Availability: Cloud hosted only, for limited amount of customers

New features and enhancements



The set of available shapes and icons in Enterprise Studio has been cleaned up. About 100 deprecated and unused symbols were removed from the Enterprise Studio configuration and will no longer be shown in the Change Graphic Shape dialog for new model packages. For backward compatibility reasons, the old shapes and icons will remain available in existing model packages. For a list of the removed shapes and icons, download the file below.


Bug fixes

Team Platform

Sites remained accessible to users after revoking their invitation for the model package or project a site is based on.


Release 26 February 2021

Availability: Cloud hosted + On premise

Please take note that the HoriZZon Server in this release is dated 19 February 2021.

Bug fixes

Data integration

Removing a container (external data) using the Open API did not work and returned an error.


Team Platform

Updating a project could fail when the prepared working copy is enabled and commits for the update could be missing.


Release 17 February 2021

Availability: Cloud hosted only

New features and enhancements

Data integration


Access to the BiZZdesign Open API can now be restricted by configuring an allowlist. You can request allowlisting for the Open API by submitting a ticket to BiZZdesign Support, including the IP addresses that need to be allowlisted.


The limit of the number of links that can be created using the BiZZdesign Open API to and from an entity has been increased to 500.



Before, when dropping a nested object from the model browser onto a view, the object could only be placed including all its child objects. Now, it is also possible to drop a nested object without its child objects by keeping the Ctrl key pressed while dragging and dropping the nested object.



The BiZZdesign scripting language now offers the option to change the label text alignment property (left, center, or right-aligned) of an object on a view using the new  labelAlignmentsetLabelAlignment, and resetLabelAlignment methods. The existing method "property"IsSet method has been extended to support label text alignment (labelAlignmentIsSet).

For more information, please refer to: labelAlignment method (re)setLabelAlignment method "property"IsSet method.


The BiZZdesign scripting language has been extended in several places. Few new methods have been added:

  • reverse() for string values. It returns the string with its characters in reverse order.
  • element() for set values. When this set contains exactly one element, this method returns it.
  • toInteger() for real number values. It returns the number as an integer value, truncated to 0 decimals without rounding.
  • toReal() for integer number values. It returns the number as a real value.
  • profiles() for object values. It returns the set of profiles that is assigned to the object. Like the profile() method on attributes, the optional "expand" parameter tells it whether or not to return "basic profile" when a profile is defined as "hidden".

The following extension has been made to an existing method:

  • The profile() method for attribute values was extended with an optional "expand" parameter. When true, the method will not return "basic profile" when the attribute is defined in a "hidden" profile, but instead, return that hidden profile.

For more information, please refer to: reverse method (strings)element methodtoInteger methodtoReal methodprofiles methodprofile method.

Team Platform

TP-11781, TP-11782

The new HoriZZon Server name (former Team Server) is now everywhere visible in the Enterprise Studio and HoriZZon interface. Please take note that the BiZZdesign Support pages are still being updated with the new name, so the old name may still be visible in topics.

Bug fixes

Enterprise analytics

Dates in the table chart were not properly sorted in date-value order.



If the graphical setting Derive line color from fill color is active, the lines were not correctly visualized in HoriZZon.TP-11731
In some situations, the processing of commits to HoriZZon was delayed, causing delays in showing model changes in HoriZZon.TP-11844

Signing out of HoriZZon failed if the Kibana dashboards feature was disabled.


Hyperlinks to views were not working anymore in Horizzon.TP-11872

Release 4 February 2021

Availability: Cloud hosted + On premise

Bug fixes

Team Platform

Certain group memberships would not be removed for already removed users as part of the sync with external authentication services like Azure AD.


When performing LDAP operations, the error "LDAP support is not enabled" could occur even when LDAP was enabled.


Syncing with LDAP would throw an error, despite the fact that the synchronization worked.TP-11848

Release 28 January 2021

Availability: Cloud hosted only

From this release on, Team Server is called HoriZZon Server. While the new name is being implemented in the software and on the Support pages, the old name may still be visible in places until the process is completed. See also Team Server is now HoriZZon Server.

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

New features and enhancements



The following improvements have been made to the Landscape map:

  • The height of individual rows can be manually adjusted by selecting an element in the map's left column and then vertically resize it.
  • By default, the text of elements in the map cells is automatically resized with the available space. If desired, automatic label scaling can be disabled in the properties of the Landscape map.
  • A minimum and maximum font size can be set for automatic label scaling.
  • Landscape maps are now more robust against model changes.



HoriZZon can now show relations to relations. When clicking a relation in a view or inspecting a relation, its related relations are shown.

Showing relations to relations in view:

Relation inspection:


Zooming in and out on a HoriZZon view was already possible using the zoom buttons that are present in each view. Now it is also possible to zoom in and out on a view using the mouse wheel or the + and - key of the keyboard.


In this release, the following closely related features are introduced in HoriZZon, enabling users to set up access to and maintenance of data blocks. Data blocks are sets of additional object attributes that can be used for data enrichment and can be edited by Contributor users in an object's properties panel in a HoriZZon view. Example:

Data policies

This feature enables Lead Designer users to set up data policies for data blocks and data update schedules (see Data maintenance). Editing data blocks in the properties panel requires Contributor users to have access to the site the data blocks are in. Data policies allow Lead Designer users to choose who is able to edit particular data blocks without needing access to the site. Editor permissions enable a Contributor user to edit data blocks on a separate model package data entry page (see Data entry). 

Currently, data policies can be set at either the particular data block level or at the object level, which will set editorship for all data blocks defined for that object. In addition to setting up data policies, data block editing via the properties panel can be further limited if additional control is needed.

Data entry

In addition to the Properties panel of an object, data blocks can now also be edited on a separate model package data entry page, provided that data policies have been set up for them. The data entry page provides users an overview of all the data blocks they are able to edit, represented via a model tree. Contributor users can use this page to update multiple data blocks without needing to access them via the context of a site. The Data tasks page (see Data maintenance) also redirects users to this page when they click on a specific data task.

Data maintenance

Data maintenance enables Lead Designer users to configure update schedules for data blocks. An update schedule describes how often editors (Contributor users) should be prompted to update a certain data block. Currently, update schedules can only be set at the data block level. The frequency that can be set for updating a data block ranges from one time only to yearly.

When a data schedule is defined, data tasks will be generated. They represent an action for editors of a data block to update the data block. Data tasks can be viewed and picked up via the Data tasks page, showing the user all open and closed data tasks he or she is responsible for. When picking up a data task, the user is redirected to the model package data entry page to update the data block.

For more information, please refer to Model data enrichment using data blocks.

The introduction of the new features comes with an updated terminology in existing features to align with the new features. The new terminology is used in the documentation on BiZZdesign Support, but the user interface of Enterprise Studio and HoriZZon do not yet use the new terminology. It will be available in the next release. As a result, there may be a discrepancy between the terminology used in the documentation and what you see in the user interface of your BiZZdesign applications.

Old nameNew name

Online editing

document definition

document store


datablock definition

data block store

data block

Connection with Kibana

document connection

document mapping

document definition

document store

Kibana connection

Kibana mapping

document definition (not changed)

document store (not changed)


TP-10462, TP-11700

Graphics options, such as the grid size, whether or not line colors should be derived from the fill color, line jump behavior, etc., can now be configured separately for each view or diagram. It is also possible to set default view settings for all views in the model package. Some graphic settings are only available at the default settings; they cannot be set per view. Any view settings that are set individually will override these default settings. The view settings are now stored with the model package and are therefore shared among all users.

The graphics options have been removed from the Enterprise Studio Options Graphics tab because of these changes. Also, grid and guide settings that could previously be accessed via Snap to Grid in the Home ribbon tab have been relocated to the new View Settings window. The view settings for an individual view or diagram can now be set via  View Settings in the Home ribbon tab. First, open a diagram or view, and then you can set the graphics options for it. 

The model package's default view settings can be accessed by right-clicking the model package in the model browser and selecting Default View Settings. The default view settings have few more options (for color views and collapsed objects) than the view settings for the individual view or diagram.

Few outdated graphical settings associated with fill gradients and shadows have been removed from the options.

For more information, please refer to Graphics options for diagrams and views.

Team Platform


Changes have been made to HoriZZon Server group management to make it easier to handle many members. Adding and removing members can now be done for multiple users at the same time. Selecting users for a group can be done per batch of users on one page. With two clicks, all users on the first page can be selected, and after navigating to the next page, one mouse click will add the next batch of users, and so on until all users are selected.

From now on, the Members page will be the only location to manage a group's members. The "Group members" section on the group manage page is no longer used for this. You will be directed to the Members page.



It is now possible to use line breaks in the labels of messages in a UML communication diagram.

Bug fixes

Data integration

It was possible to score metrics for an entity manually. A metric for an entity can only get its value from a data block attribute.


The Collections folder (containing read-only externally managed objects) could be moved under a regular model package folder, possibly resulting in inconsistencies in the model package.


The Open API allowed entities to be added to containers that are incompatible with the entity's type.TP-11614
Entities deleted using the Open API were not deleted from Elastic. This could potentially affect search results in HoriZZon.TP-11624

The Technopedia integration would cause problems searching for data or updating data, depending on the combination of Enterprise Studio and server versions.


Enterprise analytics

The matrix chart would show association relations incorrectly, only showing the related object if the association relation was drawn from a specific direction.



Links to model objects in documentation fields did not work when the documentation field was used as a property.


When creating a HoriZZon site from a BPMN model or another 1-on-1 relation-related metamodel like Amber or UML, diagrams were are always shown in duplicate in the site browser.


Values in "generated" profile attributes (i.e. collections that combine the values of the same attribute on child objects, as long as they do not have a value themselves) would not be displayed in HoriZZon. The same would happen for "inherited" profile attributes when these contained object references.TP-11409
The e-mail sender name was no longer showing the customer environment name, but instead always showing "HoriZZon".TP-11477
In some cases, a pinned table view was not restored properly.TP-11637

Graphical elements on a view with vertical text were rendered incorrectly in HoriZZon.



When a script wrote an invalid object reference to a workset that already had one or more rows containing an object, Enterprise Studio would crash.


Team Platform

Group members that had been removed from Azure AD were not removed from the HoriZZon Server.


After changing permissions from a group, this group's members would still have the previous permissions inherited from the group.


View filters and viewpoints

When using sets of attributes of type RTF on elements, a generated viewpoint in HoriZZon like the label view or tooltip view would not properly show the attribute values in the labels and tooltips.


Release notes 2020

For more information, see Release notes archive 2020

ArchiMate® is a registered trademark of The Open Group.