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.
For each new release, 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 the release.
Customers with a hosted solution will be updated first. For the update scheme, please refer to Maintenance windows for hosted 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:
Release 7 September 2020
New features and enhancements
|Availability: Cloud hosted +On premise|
To facilitate navigating cross-model relations from and to BPMN processes via the canvas, a navigation control has been made available for BPMN diagrams. The control will become visible in the diagram once a cross-model relation has been created from an element in a model of a different metamodel to the BPMN diagram (process, collaboration, or choreography), or the other way around (via the model browser).
When importing data using a ServiceNow connection, both the display values and actual values for the entire data set are fetched, but only the actual values were imported into the model in Enterprise Studio. As of now, the display values can also be imported. To enable this, the Import display value option needs to be activated at the import options for a mapping relation. See also Creating a ServiceNow connection.
The current version (date) of HoriZZon is now shown in HoriZZon. To view it, click the user profile icon, and then click About.
Performance improvements have been made to processing model packages with many views to HoriZZon.
A custom navigation control can be defined for some object using the Metamodeler, to link one or more other objects and to navigate to these linked objects. A custom navigation control can be used between objects in models of different metamodels, but also within the same metamodel. Multiple navigation controls can be created for one object. Custom navigation controls can be created in any metamodel. Example of a custom navigation control for BPMN tasks, referring to ArchiMate application components:
For more information, please refer to Creating a custom navigation control.
The Properties pop-up window would no longer appear for objects on a Lifecycle view.
Model packages having an embedded configuration that does not contain all standard metamodels could not be upgraded to a new tool configuration without crashing the application.
Charts showing the values of a metric with a profile attribute as values would become empty after switching active language.
Deleted association relations would still be visible in HoriZZon after being deleted in Enterprise Studio
|Availability: Cloud hosted + On premise|
It is now possible to configure the default roles (Lead Designer, Designer, Contributor, or Consumer) for users being provisioned using identity provider Azure AD. If you do not use group authentication or are not able to upon user provisioning, you can specify one or more default roles for all users to provide them access.
Defining the default roles can be done on the Team Server authentication settings page for Azure AD. This page is only accessible to users who have the System Administrator role. Please take note that the settings are only available in an on-premise installation of the Team Server. If you are working with a hosted Team Server, please provide the roles that you want to assign when contacting BiZZdesign Support for configuring the Team Server.
Detailed application logging would crash Enterprise Studio when performing changes in batch (like when importing a large set of objects).
The Check and Repair function sometimes removed cached chart data that should have been preserved.
The Open API beta "GET" "collaborations" endpoint that returns a list of collaborations would also return collaborations that were already deleted.
Charts in model packages with embedded configurations created with Enterprise Studio 4 - 24 Jan 2020, were not rendered correctly in later versions of Enterprise Studio and HoriZZon, even when the embedded configuration was not upgraded to their current tool version.
Matrix charts would sometimes not be rendered in both Enterprise Studio and HoriZZon.
|It was no longer possible to set the dimensions for a matrix chart of type "cross-relation property".||TP-11056|
Portfolio archives could be refreshed.
Under some circumstances, table charts would not show up properly in HoriZZon
Pie charts that are set to "count mode" would display in HoriZZon with this mode turned off.
Model packages with invalid data would sometimes crash the component that synchronizes the data between Enterprise Studio and HoriZZon. As a result, data would not be available in HoriZZon.
When using a previous version of the Activity Console, checking the model package history in the timeline of a storage place was not possible. An error message would appear saying 'Error loading the history from the server'.
|Availability: Cloud hosted only|
The error messages that may appear when using ADOdb for importing Excel files have been improved to better indicate errors due to ADOdb limits.
When creating a new object on a diagram or view, Enterprise Studio checks if the object matches existing objects in the model package, and if so, the new object can be matched to an existing one. Previously the entire model package was checked for matching objects. This is still the case, however, it is now possible to exclude parts of a model package from matching by configuring the scope for matching. Models and top-level folders can be excluded from matching.
Models and folders can be excluded from matching by deactivating the allow matching property on the Properties tab of the model or folder. When new objects are created on a diagram or view, the excluded parts of the model packages are not checked for matching objects.
For more information, please refer to Excluding models and folders from object matching.
When drawing an object reference and immediately renaming it to let it refer to an existing object, the unused new object created with the reference was not removed.
|Availability: Cloud hosted + On premise|
|Charts in model packages with embedded configurations created with Enterprise Studio version 24 Jan 2020, were not rendered correctly in later versions of Enterprise Studio and HoriZZon, even when the embedded configuration was not upgraded to their current tool version.||TP-10988|
A table chart that uses (or has used) "selection mode" would remain blank when viewed in HoriZZon.
|Availability: Cloud hosted + On premise|
If you are working with an on-premise installation of the Team Server, using MSSQL, and using integrated security for the Team Server, you need to download a new JDBC driver for the Team Server before updating it to the new version. For more information and instructions, please refer to Enterprise Studio release-specific required actions.
TP-10666, TP-10749, TP-10879
HoriZZon now has a new homepage for welcoming the user. The new homepage includes the following sections with favorite, popular, and last updated views. Additionally, the views show to which site they belong. The design of the HoriZZon pages has also been updated, including a new header, style of titles and breadcrumbs located in the header. In addition, on the right in the header is a separate entrance for notifications and one for the user profile, language settings, and configuration download.
For more information and a demo, see also the BiZZdesign blog: https://bizzdesign.com/blog/a-new-home-for-horizzon/.
On behalf of consistency and better visibility of several site functions, the following changes have been made:
It is now possible to configure the default roles (Lead Designer, Designer, Contributor, and Consumer) for users being provisioned using a SAML2 enabled identity provider. If you do not use group authentication or are not able to upon user provisioning, you can specify one or more default roles for all users to provide them access.
Defining the default roles can be done on the Team Server authentication settings page for SAML 2.0. This page is only accessible to users who have the System Administrator role. Please take note that the settings are only available in an on-premise installation of the Team Server. If you are working with a hosted Team Server, please provide the roles that you want to assign when contacting BiZZdesign Support for configuring the Team Server.
When a shared model package or project is closed or when Enterprise Studio exits and there is work that has not been committed yet, Enterprise Studio will now inform the user about this. The user has the option to close the model package or project without committing (the default), not closing and checking these changes, or just cancel the operation. If the user does not react to the question, the model package or project is automatically closed without committing the changes after 30 seconds.
For more information, please refer to Committing changes to a model package or project.
To be able to delegate administrative tasks in the Team Server further, it is now possible to grant users group manage permissions. It can be given to members of a group and can be done by users who have the Administrator role or have manage permissions for that group. A user with group manage permissions can perform the following actions:
Please take note that adding and removing members and changing the group name and description can ONLY be done for native Team Server groups. These are groups that have been created in the Team Server. It is not possible for groups that have been added to the Team Server through provisioning via an external identity provider (Azure AD, SAML, etc.).
A user can be granted group manage permissions via the group page or the new group members page:
There can be multiple users with group manage permissions in one group. Once a user who is granted manage permissions for a group is no longer a member of that group, he or she will automatically lose his or her manage permissions for that group.
For more information about group manage permissions for users, please refer to Granting users group manage permissions.
When a shared model package or project is opened in Enterprise Studio and there are contributions from other users available that have not yet been applied to the model package or project, Enterprise Studio will now ask the user if they want to update the model package or project with these contributions upon opening.
To be able to delegate administrative tasks in the Team Server further, it is now possible to grant users manage permissions for collaborations (i.e., model packages and projects). It can be given to individual users who are directly invited to a model package or project (so not group invitations). Granting the permissions can be done by users who have the Administrator role or have manage permissions for that model package or project. A user with manage permissions for a model package or project can perform the following actions (in addition to permissions that are implied by being invited):
A user can be granted collaboration manage permissions via the model package or project overview page. Example:
Users who create a model package or project automatically receive the manage permissions for that model package or project. There can be multiple users with manage permissions for a specific model package or project. Once a user who is granted manage permissions for a model package or project is no longer invited to that model package or project, he or she will automatically lose his or her manage permissions for that collaboration.
For more information about collaboration manage permissions for users, please refer to Granting users manage permissions for a model package or project.
List pages in the Team Server administration pages, like the user list page and model package list page, have a search box for searching/filtering items in these lists. It can be done by entering a search term. Now you can also use query-based search on these pages: Users, Groups, Members, Model packages, and Projects. With query-based search, you can combine a specific filter name and value in the search box, making searching and filtering more powerful.
An example: When entering only a search term on the Users page, the names and e-mail addresses are scanned for this value. To limit the results, a filter name can be included in the search box. By entering name: followed by the value, only the users' names are scanned for the value, not the e-mail addresses. Also, searching for a specific role that users have is not possible by only using a search term. It is possible using a query-based search. By entering role: followed by the role name, the list is scanned for users with that role. Entering role:designer will show all users who have that role.
Following filter names can be used:
Users, groups, members: name:, description:, role:
Model packages, projects: name: and description:
The Check and Repair function would incorrectly claim to have repaired some defects in a model package, again listing these defects in the next run.
|Some windows versions before Windows 10 gave an error when booting the Activity Console due to a Microsoft update.||TP-10689|
|In a model package containing charts, the Check and Repair function kept producing "chart with hidden legacy property values that are no longer used" messages, even after a presumably successful repair.||TP-10735|
In some situations, it could happen that the Technopedia connection did not work correctly.
Some table charts would remain blank when their view was first opened. Refreshing the chart would not always solve the problem.
|Charts based on a viewpoint script that uses the built-in function "query" (to execute another script and relay its results) would not render correctly in HorriZZon, resulting in an incomplete view.||TP-10731|
Collapsed objects were not shown in HoriZZon.
Upon opening a model package, the legends (graphic shape) added to views did not show properly.
It was possible for invalid objects to be matched when drawing new objects, causing invalid references.
|When a proxy was configured for connecting to the Team Server, the proxy settings were not used for connecting to the documents service API (used for document definitions and Technopedia).||TP-10871|
When there were more than fifty objects on a view, the color view would not set a color for all objects on the view.
When workflow links sent by e-mail were clicked using Outlook, the Outlook Safelinks protection would redirect the workflow links and make them unusable.
|Availability: Cloud hosted + On premise|
When running Enterprise Studio Online in the Windows Client application, there is now support for native application mode. Functionally, the native application mode has no additional value to the Windows Client application, it is mainly a visual change: Enterprise Studio Online opens in its own window and functions in the same way as a locallly installed application. Also, the Activity Console, and integrated file explorer and web browser open in their own application windows and look as if they were running locally. The native application mode is not supported on resolutions higher than 2560x1440. Make sure that you are using the latest version of the Windows Client application.
The native application mode can be activated via the session toolbar by clicking Settings > Switch to native application mode.
The Appstream Windows Client application, available since the 20 December 2019 release, for running Enterprise Studio Online, can now also be used when running HoriZZon in Mozilla Firefox.
If the preference is set to using the Windows Client application for running Enterprise Studio Online but the Windows Client application is not installed yet, clicking the Enterprise Studio Online button in HoriZZon will generate an error message with a link to the support page about the Windows Client application, or a default message informing that no app is installed.
The following improvements and changes have been made to the Enterprise Studio user interface.
Relocations and rearrangements
The automatically derived line color of ArchiMate objects has been refreshed. The way the line color is derived from the background color has been improved, in Enterprise Studio as well as HoriZZon. Also, the color of the icon in an object now follows the color of the font in the object.
A new ArchiMate Total view has been introduced which uses a new fresher color scheme. The new view, called Total view new style, is available next to the old Total view, now called Total view classic.
The old Total view and the rest of the view types keep their original color scheme. Existing views will keep their original or customized colors. Some of the ArchiMate example models and template models have been updated to fit the new color scheme. The standard template "Empty model with total view" now includes the classic and new style Total view.
For more information, please refer to Creating ArchiMate models using the new style color scheme.
To show a more complete overview of the features Enterprise Studio offers for ArchiMate modeling, the ArchiSurance TOGAF example model has been extended with the following:
As of this release, views of a site are by default sorted by popularity ("Number of hits"). Previously, the default sorting was by name. Sorting options "Name" and "Last modified" are also still available.
As of this release, a new feature for sharing view is available at request to try out. In addition to the existing feature of sharing views via hyperlinks (since the 20 December release), there is a possibility to include views in SharePoint and Confluence pages by embedding the views. Embedded views can be viewed by anyone who has access to the respective SharePoint or Confluence page. Accessing a view in HoriZZon from the SharePoint or Confluence page is only allowed for HoriZZon users who have the Consumer role. Security of the sharing feature can be enhanced by specifying a list or range of allowed IP addresses (IP allowlisting).
Example of a view embedded in a SharePoint page:
The sharing by embedding feature including allowlisting is currently only available at request. If you are interested, please
BiZZdesign Support. If you prefer to use allowlisting, please also provide the IP addresses.
For more information about the sharing functionality, please refer to the support page Embedding HoriZZon content outside HoriZZon and BiZZdesign blog Unleash the power of HoriZZon on SharePoint & Confluence.
The model packages overview page in the Team Server administration pages now shows for each model package the date it was last updated instead of the creation date. Also, it is now possible to sort the model packages and projects by their last updated date.
Before, setting a specific or persistent color palette for a color view in Enterprise Studio required using a script. From now on, w hen selecting different colors in a generated color view, these colors will be persisted and applied the next time the (saved) color viewpoint is reactivated for a view. In addition, controls have been added to the color view legend to reset the changed colors, and to deactivate the color (or label) view from there. For more information, please refer to Customizing the colors of a color view.
Example of a color view with default colors (left) and customized colors (right):
It was not possible to migrate model packages created with Enterprise Studio 4 (2019-08-13) to a later version.
It was not possible to change the duration of the value stage of a value stream in a Business Outcome Journey Map.
When exporting data using an Excel connection, dates would be exported as strings instead of actual dates.
|Charts that were defined using a document-based attribute (for online editing) were broken after reopening the model package.||TP-10494|
Analytic charts in currently open views and diagrams were refreshed upon loading these views and diagrams, and when saving them. This resulted in undesired waiting times. From now, analytic charts can only be refreshed manually. In addition, some performance optimizations have been made to reduce the time needed to refresh charts.
|Aggregate metrics were not visible in HoriZZon.||TP-5785|
|HoriZZon sometimes showed the wrong languages on charts.||TP-6066|
Managing external groups was not possible in Internet Explorer. After applying changes, an S_400 error was returned.
When activating a license, the license expiration date on the Team Server license settings page would show the text "invalid date" instead of the date when viewing the information using Internet Explorer.
The Metamodeler would not preserve the font color upon opening a metamodel.
Enterprise Studio would crash when navigating to View > Derive relations > Via Profile Attributes to open a derived relations table.
|The column headers in the Property table did not show the correct translated attribute name for customer-defined profile attributes.||TP-10455|
|Deleting a workset would crash Enterprise Studio.||TP-10482|
|The personal storage for saving model packages would not be available for users when they are in an AzureAD domain.||TP-10176|
|Sometimes configured team servers would not show up on the Open backstage page, while visible on the Save As page.||TP-10396|
After copying a relation reference without copying both its attached object references, and undoing this action, committing any remaining changes would fail with the message "An error occurred during the creation of the contribution file". The Check and Repair function has been extended to detect such a situation in the working copy and repair it.
|Some special characters in the e-mail address were not supported when inviting a user.||TP-10511|
|Availability: Cloud hosted + On premise|
A warning about registering document definitions would appear when opening a model package in Enterprise Studio installations without HoriZZon.
For more information, see Release notes archive 2019.
ArchiMate® is a registered trademark of The Open Group.