TP-11975

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:

TP-9351

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)

TP-12009

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.

TP-11883

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.

TP-10239

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.

TP-11956

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.

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.

TP-11965

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.

TP-7133

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.

TP-11825

When defining a custom viewpoint definition, it is now possible to use own custom icon symbols for the concepts in the viewpoint definition. In order to 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:

TP-11640

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.

TP-10211

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

TP-11873

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:

TP-11651

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.

TP-11670

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.

TP-11670

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.

TP-11892

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.

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:
  
  

TP-11632

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.

Removed_shapes_icons.txt

TP-11508

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.

TP-11764

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.

TP-6990

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.

TP-10692

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  labelAlignment, setLabelAlignment, 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.

TP-11783

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 method, toInteger method, toReal method, profiles method, profile method.

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.

TP-11527

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.

TP-9872

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:

TP-11691

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.

TP-11706

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.

TP-10462, TP-11700

Graphical 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 graphical 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 graphical 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.

TP-10874

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.

TP-11141

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