The release notes show the latest new features and enhancements in the Bizzdesign Horizzon platform, 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 Bizzdesign cloud solution. Installer files for the on-premise solution will be updated periodically. Not sure which solution you have? Check out Which Bizzdesign Horizzon software solution am I using?

On this page:

Expand/Collapse All

Release 31 January 2023

Availability: On premise only
Horizzon Server (2023-01-31), Enterprise Studio (2023-01-12)

Bug fixes

Data integration

Data blocks with a certain date format could not be processed.


Release 27 January 2023

Availability: On premise only
Horizzon Server (2023-01-27), Enterprise Studio (2023-01-12)

This release only supports PostgreSQL 14 or higher. If you are still on a Microsoft SQL Server database, please migrate using the 3 November 2022 release. For more information and instructions, please refer to  Migrating the Horizzon Server database from Microsoft SQL Server to PostgreSQL .

If you already run the database on PostgreSQL but on a version before Postgres 14, you must upgrade to PostgreSQL 14, otherwise the server will not start.

If you have a PostgreSQL version newer than 14, and want to continue using it, you must allow the use of this newer version via the configuration file. But please be aware that 14 is the only officially supported version. For more information and instructions, please refer to Bizzdesign Horizzon release-specific required actions , Releases 2022, 3 November 2022 release.

End-of-support and end-of-life announcements

Bizzdesign no longer supports Windows 8.1 as environment for local Enterprise Studio installations. With this, Bizzdesign is following the Windows  lifecycle policy.

End-of-support and end-of-life announcements

Bug fixes


Accessing Horizzon dashboards using an Nginx server would raise a 502 gateway error.


Release 23 January 2023

Availability: Cloud hosted only
Horizzon Server (2023-01-23), Enterprise Studio (2023-01-12)

New features and enhancements


TP-13162, TP-14240

The ArchiMate metamodel has been updated to version 3.2 of the ArchiMate Specification. The main changes are:

  • A derivation rule has been added for the Grouping element (following section B.3.5 of the specification).

  • The restrictions on the derivation rules have been improved (section B.4 of the specification).

  • The icon notation of the Meaning element has changed, and an icon notation has been added to the Work package element.

  • The default color of the Plateau, Gap, and Location elements has changed.

  • All concept icons in the model browser now match the colors used in the ArchiMate 3.2 Specification. The following concepts have been updated:
    • Composite elements container
    • Location
    • Gap
    • Work package
    • Meaning
    • Outcome

  • Composition and Aggregation relations can now be added between Plateau and Outcome elements, and Realization relations can be added between Material and Equipment elements.

  • Relations no longer allowed following the ArchiMate 3.2 Specification have been deprecated. Models with those relations can still be read, but new relations can no longer be created.

  • Although the ArchiMate 3.2 Specification changed the Technology Layer metamodel, making Device, System Software, Facility, and Equipment no longer subtypes of the Node element but of the technology internal active structure element, these are still subtypes of the Node element in Enterprise Studio. If you are querying your model for Nodes, the results will potentially include Devices, etc. Therefore, you should consider adding an additional type filter to those queries to exclude those subtypes.

  • As of this release, Enterprise Studio no longer supports the specific role names for relations. The role names were never part of the standard and have now been completely removed.

    If you use scripts that use specific role names, you will need to update them. For more information, please refer to the item under Scripting in these release notes.

Data integration and contribution


Data block fields (of all available types) and their values are now available in the standard indexes in OpenSearch. When creating an index pattern for dashboards, the data block fields can be recognized by the prefix datablocks.<namespace>:.

Update 1 February 2023: Including data block fields in the standard indexes has been temporarily disabled until further notice. Data from your data blocks is already available in the standard indexes, but the data may be outdated.


Limited functionality to edit data blocks in Enterprise Studio is now available at request. The following places in Enterprise Studio now allow setting data block values directly:

Properties pane:

Properties form:

Properties table:

Please note the following:

  • The objects with data blocks in Enterprise Studio are checked for data policies. If a data block does not have a policy with assigned editors, it cannot be edited in Enterprise Studio.
  • Only one object at a time can be edited. The data blocks cannot be edited in bulk or via script.
  • Editing data blocks is only possible on objects created in Enterprise Studio. Data blocks on external objects (entities) and objects created in Horizzon remain read-only.
  • Calculated fields are not updated automatically. Use the Refresh external objects option to update the values.

If you would like to have the edit functionality activated for your environment, please contact Bizzdesign Support.



Few styling changes have been made to Horizzon, including a number of updated icons in the Horizzon sidebar and icons for user manage permissions in packages.


TP-14055, TP-14187

A published BPMN diagram now displays a thumbnail showing the diagram's contents instead of a general image. The thumbnail is available in the Properties slide panel of the object and also on the object's inspect page. Also, a BPMN diagram can no longer be set as a favorite, since this can already be done for the object it belongs to. Example:


Create space

It is now possible to move elements aside to make room for new elements or add space to the diagram. It can also be used to create space within an element. This function is similar to the Make room function in Enterprise Studio.

To use the function, right-click on a space (or on an element) in the modeling canvas and drag toward the direction where you want to create space. Any elements positioned next to where you start dragging will be moved aside into the dragging direction. Example:

Select elements

Elements in the BPMN diagram can be selected by dragging a rectangle around them using the mouse. For an element to be included in the selection area, it now needs to be fully contained by it. Partially contained elements are not included. To select elements within another element using a selection area, hold down Shift and drag a rectangle around them. After selecting the elements, they can easily be moved together by dragging the group.

TP-14186, TP-14253

Select similar elements

It is now possible to select a specific set of elements in the diagram. Select one element and then press Ctrl+E. All other elements of the same type will also be selected. This function is similar to the Select similar  function in Enterprise Studio.

Set the direction of data association relation

It is now possible to set the direction of an association relation by hovering the relation line and clicking . The direction(s) that can be set depends on the used data type (Data input, Data output, or Data object). Also, the positioning of elements connected with a data association has improved.

Connect message flows to pools

Connecting a message flow to a pool has been made easier. Drag the flow to the first border of the pool until it turns green and release the mouse button.


The sidebar of the Horizzon Design page containing the modeling canvas has changed. It now contains the menu items belonging to the model instead of the model package, which is the appropriate context for the diagram. The new context is also visible in the breadcrumb at the top of the page.


Few terminology changes have been made in the context of process modeling, they include:

  • The title of the Horizzon page containing the model canvas has changed from "Refinement of..." to "BPMN diagram of ...".
  • Modeling tasks are now called Diagram update tasks.



One of the changes in the implementation of ArchiMate Specification version 2.3 is that Enterprise Studio no longer supports the specific role names for relations. The role names were never part of the standard and have now been completely removed.

If you use scripts that use specific role names, you will need to update them. The scripts will not fail, but return unintended or incorrect results and this might go unnoticed. You need to replace specific role names with general role names and optionally add a type filter for the target object. Depending on the contents of your script, other adaptations to the script may be needed to restore its original behavior.

An example is shown below. In the figure, the specific role names are shown on the left, and the general role names are on the right.

The following script is used to find the processes that are triggered by the actor:

forall obj in actor.objectsWithRole("triggers process") {
	output obj;

Following the example figure above, the result would be only the process. Now, if the general role name is used:

forall obj in actor.objectsWithRole("triggers") {
	output obj;

the result would be the process as well as the service. Since this is not the desired outcome, you need to make another adjustment to the script to get the correct result by adding a type filter "ArchiMate:BusinessProcess":

forall "ArchiMate:BusinessProcess" obj in actor.objectsWithRole("triggers") {
	output obj;


The script method getTaggedValues now has an optional boolean parameter "persistent". When "true", only tags are returned that were added as being persistent. When "false", nonpersistent tags are returned. When the parameter is omitted, getTaggedValues returns all tags, as before.

For more information, please refer to getTaggedValue(s), hasTaggedValue, removeTaggedValue, setTaggedValue method.

Team Platform


Performance improvements have been made for opening model packages in Enterprise Studio. Opening a model package will now take less time. The modification also affects ordering the contributions in the model package timeline. The order will now be based on the order of the contributions as they are retrieved from the server instead of when they have been added (committed).

View filters and viewpoints


By default, the text labels of a label view in Enterprise Studio are presented as one-line labels. In the case of labels with a long text, it can be useful to have the label text wrapped for readability. It is now possible to wrap the text in the labels of label views generated on objects and relations. To activate text wrapping for label views in Enterprise Studio, select the new option Wrap label view text on the General tab of the Enterprise Studio Options. When activated, the labels are adjusted to the with of their objects (but with a minimum width).

For more information, please refer to Enterprise Studio general options.

Bug fixes

Data integration and contribution

Having empty data blocks on an object could sometimes lead to extended periods of unavailability when this object was selected (the wait cursor is shown for several seconds).


Enterprise Portfolio Management

Exporting Portfolio view recommendations to PowerPoint® could fail due to a script error and result in an incomplete PowerPoint deck.



It was impossible to access the Horizzon dashboards using an Nginx server.


It was impossible to sort models and objects on the Design tab of the Horizzon homepage by "Last updated".


Clicking a link from the weekly tasks summary e-mail would trigger a redirect loop in some customer environments. 


The horizontal space for presenting a view in a site was limited, causing a view to quickly get cut off when moving it to the left or right.



In certain scenarios, deleting an object would not automatically delete all of its connected relations, leaving behind incomplete relations that are subsequently flagged by the Check and Repair function as defects.


When a modeling task's assignee in Horizzon had become invalid (due to, for example, the removal of this user), the "Claimed by" text below diagram's preview would show "Invalid user" instead of the assignee's name.


Team Platform

When a user was removed, the server would return an error when retrieving any running task still assigned to that user.


Setting a persistent tagged value containing an internal object value in a script would corrupt a subsequent commit.


After removing SAML-provisioned users from Horizzon, these users would still be shown when searching for them by their full name.


Release notes 2022

For more information, see Release notes archive 2022.

ArchiMate is a registered trademark of The Open Group.

BPMN is a trademark of Object Management Group, Inc. in the United States and/or other countries.

PowerPoint is a registered trademark of the Microsoft group of companies.