Skip to end of metadata
Go to start of metadata

Expand/Collapse All

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


On this page:


Release 4 - 20 November 2018

This release has a changed metamodel configuration. You need to migrate your model packages with metamodels embedded (.xmam), or stored in your personal storage or on the Team Server to materialize the changes and fixes in this release.

New features and enhancements

Modeling

 New shortcut for resetting zoom factor to 100%
TP-8077

If a diagram or view has been zoomed in or out, it is possible to reset the zoom factor to 100% using the Scale to 100% function in the status bar at the bottom of the application window. Now the zoom factor can also be reset using the key combination Ctrl+0. Make sure to use the 0 on the numerical keypad, because the shortcut Ctrl+0 with 0 from the alphanumeric keys can be used to complete a selection of layered objects in a diagram or view.


Team Platform

 Update - Team Server integration with HoriZZon
TP-7584, TP-8001, TP-8002, TP-8035, TP-8096, TP-8097

BiZZdesign is currently working towards one integrated environment for the Team Server and HoriZZon web portal (https://CustomerName.horizzon.cloud). The Team Server functionality offered in HoriZZon is still limited, so where needed links will be available to redirect you to your original Team Server environment, which is also still available (https://CustomerName.bizzdesign.cloud).

If you are working with only the Team Server, the new Team Server interface will not be visible yet.

This release includes the following changes:


  • Each site on the Sites page now has a manage icon . When clicked, the site creation page of the site opens in which the site can be edited. The manage icon is only available to users who have the Lead Designer role and have an invitation to the model package the site is based on.



  • A model package or project page now has a section Created sites, showing all sites that have been created based on that model package or project.



  • Individual user and user group pages with full information are now available.



  • Managing user groups is now possible. Groups can only be managed by users who have the Administrator role.



  • A user can now register a device for 2-step verification in HoriZZon. It can be done in the user manage page.



Bug fixes

General

Enterprise Studio would stop working when particular third-party tools were active, such as password managers or Windows Narrator.

TP-8190

ERD

The analysis "Show facts per entity type in table" on a NIAM view did not show the correct fact descriptions for entities that were defined on the "to"-side of the fact. In addition, the "participation" attribute was not interpreted correctly.

TP-8211

HoriZZon

Shapes were not displayed correctly in HoriZZon if they were not the default shapes for that object.

TP-7982

Special characters were not displayed correctly in workflow-related parts in HoriZZon.

TP-8118

Internet Explorer needed to authenticate every 5 minutes in HoriZZon.

TP-8670

Modeling

When a model package contained an invalid relation, the model browser would crash the application upon expanding the "from" or "to" side of this relation.

TP-8128

Scripting

The substring script method would raise an error when the size argument had value 0. As of now it returns an empty string.

TP-8078

View filters and viewpoints

Color view filters would only use three color palettes, resulting in reuse of the same color for incomparable values from different properties. The color palettes have also been improved.

TP-4793


Release 4 - 5 November 2018

Bug fixes

Team Platform

When using LDAP to connect to a Team Server and entering an incorrect password, the user would have to wait for about 10 minutes before being able to connect again.

TP-8235

The LDAP authentication disregarded the LDAP setting Follow referrals during sign-in in the Team Server.

TP-8271


Release 4 - 31 October 2018

Bug fixes

Team Platform

In situations where a user made changes that resulted in a collaboration conflict, Enterprise Studio would sometimes freeze or stop working.

TP-8257


Release 4 - 24 October 2018

Bug fixes

Modeling

When a second relation of the same type was created between two ArchiMate objects, Enterprise Studio would stop working.

TP-8216


Release 4 - 19 October 2018

This release has a changed metamodel configuration. You need to migrate your model packages with metamodels embedded (.xmam), or stored in your personal storage or on the Team Server to materialize the changes and fixes in this release.

New features and enhancements

General

 Modernized graphical user interface
TP-7655, TP-7937

The graphical user interface (GUI) of Enterprise Studio and Enterprise Studio Online has been updated. Changes include the following:

  • Renewed themes (Blue, Gray, Black, White), with White as the new default theme.
  • Updated icons in the ribbon tabs and the Backstage view.
  • New default configuration of window panes.



 Personal application settings persistent across software versions
TP-6304

As of Enterprise Studio 2.5, the application's and Activity Console settings set by the user are stored in files in the user's profile (or another user-defined location), making personal data persistent across modeling sessions. Application settings include changes in the Enterprise Studio Options and changes in the Enterprise Studio graphical user interface (GUI) like default shown window panes and changes in the ribbon layout.

As of now, new installations of Enterprise Studio automatically copy the application settings in the .ini file stored by the closest previous version (2.5.0 and higher), so the settings are persisted across software versions.

To reset the application settings to their original values (a "factory reset"), select the Reset all application settings option under Factory reset on the Advanced tab of the Enterprise Studio Options. The settings will be reset the next time Enterprise Studio is restarted.



In addition, the settings Enable auto context menu for graphic objects on the Graphics tab, and Use alternative diagram image format on the Advanced tab have been removed, as they do not have any purpose any more.


 Improved state indication for unsaved model package
TP-7778

In case of a new, unsaved model package, the status bar in Enterprise Studio would display "nil://". It now says "Not yet saved", better reflecting the actual state of the package.


ArchiMate

 New Landscape map view
TP-6679

A Landscape map has been added as a new view type in the ArchiMate model. It can be found in the category Overview in the New context menu. In this view, landscape maps can be generated that show the relationships between two or three sets of model elements in a matrix. A landscape map view can contain more than one landscape map.



In contrast to a matrix chart, the elements in landscape maps are references to actual model elements, which means that they can be used for navigation, color and label views, etc.


DMN

 Verification support in DMN decision tables
TP-7588

For a large class of DMN decision tables, the option has been added for static verification of the coverage of the rules, to detect, among others, overlapping rules and combinations of input values that are not covered by any of the rules. If certain prerequisites are met, a control will be present to verify the table.



Enterprise analytics

 Improved chart population filtering
TP-7653

When filtering the population of a chart based on an attribute that is a collection (a set or list), the comparison was previously done using a string representation. This was not very useful because it required listing all possible combinations of values.

It is now possible to check whether the collection contains a certain value. Similar to string values, "OR" can be used to check if the collection contains one of a number of options.

To check if the collection contains all of a number of options, multiple filters for the same attribute can be used.



Enterprise Studio Online

 Access Enterprise Studio Online from HoriZZon
TP-7801

Enterprise Studio Online can now be started from HoriZZon. A link to start Enterprise Studio Online has been added to the HoriZZon toolbar at the top of the window.



HoriZZon

 New name for HoriZZon settings
TP-7987

With the introduction of the Team Server settings following the Team Server integration with HoriZZon, and to better reflect the contents, the former HoriZZon Settings, in which the HoriZZon look and feel can be changed, have a new icon and are now called Personalize.



Language and translation

 Improved handling of special characters in Documentation window
TP-7758

The handling of certain special characters by the Documentation window has been improved for better support of languages such as Chinese.


Reporting and printing

 End of life HTML report and InSite Server
TP-7881

The HTML report and InSite Server have reached end of life and will no longer be available as of Enterprise Studio 4. You are advised to switch to HoriZZon. For more information, please ask your contact at BiZZdesign sales.

At specific request, the HTML report can be made available. Requests can be sent to the BiZZdesign service desk.


Team Platform

 Preview Team Server integration with HoriZZon
TP n.a.

BiZZdesign is currently working towards one integrated environment for the Team Server and HoriZZon web portal. In this release a sneak preview of an integrated Team Server will be available in your HoriZZon environment (https://CustomerName.horizzon.cloud).

The Team Server functionality offered in HoriZZon is still limited, so where needed links will be available to redirect you to your original Team Server environment, which is also still available (https://CustomerName.bizzdesign.cloud).

If you are working with only the Team Server, the new Team Server interface will not be visible yet.



 Object change history
TP-6097

It is now possible to view the change history of objects in a tracked or shared model package. For single objects the Show object history context menu function is available, showing when (and by whom) the selected object was created, and when it was last changed. For views there is the Show view history function, which does the same, but for the view's content as a whole. Example of an object history overview:



Bug fixes

General

Enterprise Studio would sometimes crash when opening a second model package.

TP-7708

After customizing the Quick Access toolbar by adding certain non-standard commands, next time the application was started, it would immediately stop working, either with or without an error message.

TP-7756

ArchiMate

According to table B.3 of the ArchiMate standard, aggregation and composition of relationships in a Location object should be allowed. Enterprise Studio only allowed association of those.

TP-7567

It was no longer possible to delete actors (or roles) from an Ecosystem view.

TP-7608

BPMN

Under some conditions, it was not possible to draw data association relations from or to a data store object.

TP-7760

Data integration

An ArchiMate export was incorrect when combinations of bold, italic, and/or underline was used for elements on a view.

TP-7021

If a model folder was selected as the context for the creation of a scheme in a Connection model import, this was ignored and the scheme was created at the top level in the model instead.

TP-7636

When validating an SQL mapping in a Connection model, an error was reported for a reference from an SQL table column to another table without a corresponding foreign key constraint in the table definition. This has been replaced with a warning, because imports and exports are still possible without constraint.

TP-7646

In a Connection model, column headers were no longer exported in an Excel export with an empty population.

TP-7752

Importing and exporting indefinite date ranges with an Excel connection was not supported well.

TP-7779

The Technopedia integration in Enterprise Studio was broken.

TP-7782

Enterprise analytics

The option Resize vertically did not work for the table chart.

TP-7723

The table chart showed behavior that should not have been shown in an Analysis definition view, such as showing resize controls and auto resizing.

TP-7864

HoriZZon

The link in the e-mail users received after they were assigned a workflow task, was not working correctly. The link now correctly navigates the user to the workflow task in HoriZZon.

TP-7668

Under certain conditions, search indexes used for retrieving data would not work correctly. Because of this data in HoriZZon would not be updated, which could lead to stale or missing data.

TP-7776

The redirect used during sign-in to HoriZZon did not validate the redirect destination.

TP-7940

Date values in HoriZZon were displaying an incorrect month.

TP-7965

Metamodeler

Validating a metamodel configuration with recursive definitions could lead to script errors.

TP-7543

Migrating a customized pre-3.3.0 configuration to a newer standard configuration (to fix a validation warning issued by the Metamodeler) would not work when the Metamodeler's export function was used to apply the customizations to the newer configuration.

TP-7682

Modeling

Dropping multiple objects from the model browser onto a view took considerably more time than what would be considered appropriate for this action. This was especially the case when working with Enterprise Studio Online.

TP-7867

When selecting the option Navigate via model in the Labels dialog or Color view dialog, the application would crash.

TP-8018

Scripting

Scripts comparing values of type "profile attribute" would sometimes produce unexpected results, marking unequal attributes as equal.

TP-3960

Team Platform

Opening a model package from the Team Server for the first time took a lot of time in case the model package had a large history (many commits).

TP-6687, TP-7097

In certain scenarios Enterprise Studio Online sessions would not show the proper user identity and would be unable to load storage places.

TP-7670

In model packages using model-level access, relation tables would sometimes not allow creating or removing relations, depending on the actual access granted and the current selection.

TP-7696

Signing in on a bookmarked Team Server sign-in page would result in an S_500 error message stating that the session has expired.

TP-7698

Follow referrals of the LDAP settings in the Team Server were not saved in the configuration. After restarting the Team Server these settings were lost.

TP-7699

When a proxy was configured in Enterprise Studio 3.3, it would not be used for all calls made by the Activity Console to the Team Server, leading to an interrupted connection.

TP-7720

User groups that had already been removed before TP-7615 was fixed (release 3.3.1) will now also be removed in HoriZZon.

TP-7753

Authentication errors from external identity providers were not handled properly.

TP-7757

The Team Server would output internal structure in error messages. This is now suppressed.

TP-7942

It was possible to enumerate usernames using specific calls in the Team Server.

TP-7943

Sometimes the Team Server would become unresponsive and required a restart.

TP-7997

When switching from LDAP with Kerberos to SAML authentication, Kerberos would not get disabled.

TP-8046

View filters and viewpoints

Color view filter legends did not show enum values in order. Values could be shown in a random order.

TP-5345

Release 3.3.1 - 10 August 2018

This release is particularly important for users of the Team Platform functionality.

Bug fixes

Team Platform

When a user with administrator or system administrator permissions had activated MFA (multi-factor authentication) in the Team Server, some functions requiring administrator or system administrator permissions were broken.

TP-7609

When a user group was deleted from the Team Server, it was still available in HoriZZon.

TP-7615

It was not possible to invite a user group to a model package or project without having an administrator role.

TP-7638

The user could get the error "Signing in to the storage place failed or was canceled by the user." when authenticating in the Activity Console with a Team Server having upper case characters in the URL.

TP-7642


Release 3.3 - 25 July 2018

This release is important for all users.This release has a changed metamodel configuration. You need to migrate your model packages with metamodels embedded (.xmam), or stored in your personal storage or on the Team Server to materialize the changes and fixes in this release.

If your organization is using Azure Active Directory for user authentication in the Team Server (and HoriZZon), please read the item "Changes in Azure AD configuration for user authentication" of this release notes. It contains important information.

If your organization is using Active Directory for user authentication, please read the item "Changes in Active Directory configuration for user authentication".

If you have recently used an earlier version of the Team Server before upgrading to 3.3, you may see the following info on the Team Server 3.3 page the first time you use it. To resolve this, drop the cache of your web browser and refresh the page. After signing in again, the Team Server page looks normal again.


New features and enhancements

General

 Changes in Enterprise Studio installation
TP-7590

As of this release, you will be prompted to close all open applications during the installation of Enterprise Studio. If you leave applications open, any unsaved data may be lost.


Amber

 Extended scope for model check "Duplicate objects"
TP-6696

The searching scope of the model check function Duplicate objects in the Count/Check group of the Amber ribbon tab now depends on the selection in the model browser. Allowed scopes are: the model package, one or more models, or one or more model package folders (folders directly located under the model package).

If the selection is empty, the entire model package is scanned (provided that at least one diagram or view from the model package is open). In case of an incorrect selection (anything else than a model package, one or more models or model package folders), the entire model package will be scanned.


ArchiMate

 Extended searching scope for model checks "Duplicate objects" and "Duplicate relations"*
TP-6696

The searching scope of the model check functions Duplicate objects and Duplicate relations in the Check group of the ArchiMate ribbon tab now depends on the selection in the model browser. Allowed scopes are: the model package, one or more models, or one or more model package folders.

If the selection is empty, the entire model package is scanned (provided that at least one view from the model package is open). In case of an incorrect selection (anything else than a model package, one or more models or model package folders), the entire model package will be scanned.


 Improvements to timeline views
TP-7096

Few improvements have been made to the roadmap and life cycle views. They are: 

  • Objects are no longer shown beyond the timeline. If their lifetime extends before the beginning or after the end of the time line, this is shown with an arrow-shaped border. Objects that fall completely outside the time line are shown with a transparent shape.



  • It is possible to use "indefinite" as a date for life cycle stages. It can be set for the first and the last life cycle stage date. To set the indefinite date, press Ctrl+Alt and click on a date in the life cycle properties form.



  • The pop-up window for setting the object's lifetime that is initially shown when the object is attached to the timeline, has been removed. Lifetime dates can easily be set on the selected object's corners. 


For existing models with these views, a one-time execution of the refresh function may be required.


BPMN

 Link data stores to ERD entities or UML classes
TP-7043

In BPMN models it is now possible to link data stores to an ERD entity or a UML class. It can be done in the same way as data objects are linked. A data store can only be linked to one ERD entity or UML class, not to both.



Data integration

 Excel connection support for import and export of timed attributes and metrics
TP-6138

The Excel connection has been extended to support the import and export of timed attributes and metrics.

For example, life cycle data can be imported by defining a date for each possible life cycle stage, or by defining a life cycle stage for a selection of dates. An example:



 Excel import and export for UML models
TP-4487

In addition to ArchiMate and ERD models, Excel import and export using a Connection model is now also possible for UML models.



DMN

 Empty lists or values as input and check on empty values in decision table
TP-6293

In a DMN decision table, the keyword "EMPTY" (or a translation of it) or "NULL" can now be used to explicitly check for empty input values or an empty list in a condition, in case of a list information item. Also, an "EMPTY" result can be specified in this way. An example:



Additionally, several small improvements have been made in the handling of list information items in DMN.


 Multi-line display of input data element name in listed mode
TP-6706

In a DMN Decision requirements diagram in listed input data mode, names of input data elements were always kept in a single line of text, which could lead to very wide decision elements in case of long names. This has been changed so that the names can be split over multiple lines. Also, each input data element is now preceded by an input data icon.



Enterprise analytics

 Various chart improvements and enhancements
TP-5251

The following overall improvements and enhancements have been made to the enterprise analytics functionality:

  • A uniform layout of the charts.

  • A cleaner and simpler visualization, including all chart controls located on one side of the chart.

  • One single pop-up window for chart display settings instead of various separate controls. Example:



  • A slider next to a legend or a table to handle values that do not fit the chart space.



  • The bottom line of a bar chart can be moved up and down for repositioning the chart.



  • Addition of time dimension and timed constraints (filters).



  • A new matrix chart that can be used for representing relationships among objects. The chart supports different matrix types: cross-relation, cross-relation property, intermediate object, and intermediate object property. All populations can be set separately.



  • Various table chart improvements.

    Changed resize behavior:
    • Resizing vertically, defined by the chart display setting Resize vertically (horizontal resizing per column is still possible). In case a large number of objects is added to the table, this setting is cleared by default. Can be selected if desired.
    • The font size no longer changes upon resizing a table. This may require a refresh of your old tables after migrating to the new functionality. 

    Filter functionality can be added via the chart display setting Show filter row . When selected, a filter bar is added to the table for filtering the table data, which supports the use of simple expressions.



Enterprise Studio Online

 Chrome support for easy copying and pasting
TP-7317

When using Enterprise Studio Online in Chrome, copying and pasting data between Enterprise Studio Online and your local device can be done just using Ctrl+C and Ctrl+V instead of using the Copy to local device and Paste to remote session commands in the remote session toolbar of Enterprise Studio Online.

In order to be able to use Ctrl+C and Ctrl+V, you first need to permit Chrome to do this. You may see a message pop up, or you can change the setting for the clipboard.



 Autosave improvements
TP-7151

Automatic saving of model packages is now postponed during lengthy operations, which will improve the efficiency of importing large data sets in large model packages.


ERSM

 Improved example model "ArchiSurance Health Risk & Security"
TP-5980

A number of small improvements have been made to the ArchiMate example model "ArchiSurance Health Risk & Security", to illustrate some new features that have recently been added to the ERSM functionality (release 3.1.1), and to solve some inconsistencies.


HoriZZon

 Increased zoom levels
TP-6716

The zoom levels in HoriZZon have been increased. Zooming in is no longer limited to 7x.


Metamodeler

 Versioning custom metamodel configuration
TP-5396, TP-7234

Metamodels now have two version identifiers: their "base version", which corresponds to the Enterprise Studio tool version with which they were created, and an optional "custom version". The custom version can be set when customizing the metamodel in the Metamodeler.



Depending on whether a metamodel configuration has customizations, one (base) or two (base and custom) versions are shown when opening the metamodel. Example:



 New properties pop-up window for viewpoint definition
TP-6430

A properties pop-up window is now available in viewpoint definitions in the Metamodeler. It can be accessed via the control in the canvas menu. The pop-up window also includes the viewpoint icon property, which replaces the former separate control for adding a view icon to the viewpoint.



 New properties pop-up window for elements and relations in viewpoint definition
TP-7027

A properties pop-up window is now available for elements and relations in a viewpoint definition in the Metamodeler. It can be accessed via the control on the element or relation in the definition. The pop-up window also includes the icon symbol, icon position, icon size, and arrow size properties, which replace the former separate controls for setting these properties.



Modeling

 Support for creating relations between read-only objects
TP-4841

It is now allowed to create relations between two read-only objects. The location in which a regular new relation is stored, is determined by the following steps:

  • By default, the relation is stored in the layer that contains the "from" object.
  • If this layer's model is read-only, the relation is stored in the layer that contains the "to" object.
  • When the "to" model is read-only also, the relation is now stored in the model of the view it was drawn on.
    As a result, relations are no longer relocated when their "from" object is moved: after creation, the relation stays in the same location until explicitly moved by the user.


Reporting and printing

 InSite Lite report performance improvements
TP-7035

Generation times and page loading times for the InSite Lite report have been improved.


Scripting

 objectsWithRole script method more robust against model package problems
TP-6392

The objectsWithRole script method no longer returns invalid (corrupted) objects. This will make scripts more robust against problems in the model package.


 Script methods for turning a string into a GUID
TP-7094

The following script methods have been added for string values that represent a GUID:

  • isGUIDFormat tests whether the string can be converted to a GUID value.
  • toGUID performs this conversion.
    For symmetry reasons a similar method isNumberFormat has been added that tests whether the toNumber method could convert a string to an integer or real value. The isNumberFormat method will replace the existing isNumber method, which will remain available, but is no longer supported.


 New default behavior for "setTaggedValue" script method
TP-7284

The default behavior of the optional fourth parameter (<undoable>) of the setTaggedValue script method has been changed: instead of defaulting to "true", it now defaults to the value specified for the third parameter (<persistent>). This simplifies setting non-persistent tags on read-only objects.


Team Platform

 Improved display of sign-in instruction text in Activity Console
TP-6491

When a user is asked to reenter Team Server credentials, and is referred to the Activity Console, the Activity Console shows a message indicating that signing in to the Team Server is not possible, followed by the instruction "Double-click to authenticate". This instruction could become (partly) invisible to the user, depending on the length of the Team Server name. As of now the instruction is always visible to the user.


 Changes in Azure AD configuration for user authentication
TP-7060

As of release 3.3 a client application secret needs to be registered at the Azure AD authentication settings in the Team Server. If there is no secret registered, the Team Server will not be able to authenticate with Azure AD, and users will not be able to sign in to the Team Server and HoriZZon (if applicable).



For more information and instructions, please refer to the release-specific required actions.


 Model-level access control
TP-7088, TP-3162, TP-7089, TP-7229

A new way to control access to models in the Team Platform functionality is available. Previously, you could use projects to control access to models. Working with projects will still be available, allowing project teams to work on parts of a model package in isolation. But if your main objective is to implement access control, new functionality is offered.

From Enterprise Studio 3.3, designers can share model packages and projects with other users and user groups, and at the same time assign access permissions. Edit permissions can be assigned per model or model folder. This provides a more flexible and easy to use way to control access for specific users.



Access permissions can be set in Enterprise Studio when sharing a model package or project, but can also be managed in the Team Server.



With the upgrade to Enterprise Studio 3.3, your existing projects and invitations will be converted and remain active.

For more information, see Model-level access control in Enterprise Studio.


 Replacement for stop contributing button
TP-7276

To allow use of the wider range of options offered by the new model-level access control feature, the list of model packages on the Open page of the Backstage view no longer has the button for stopping with contributing. Instead each model package has a button Manage access that links to the online Team Server page for managing the user's invitation to the model package.



 Single sign-on support for identity providers using SAML 2.0 protocol
TP-6993, TP-7183

Single sign-on access for the Team Server now also supports signing in with an organizational account based on an identity provider using the SAML 2.0 protocol, for example Okta and Ping.

If single sign-on via such an identity provider is configured, the user can sign in to the Team Server using the button available for this. The text on the button in the image below may differ from the one you see when signing in; the name is set during configuration.



For more information about configuring user authentication with a SAML 2.0 based identity provider, see Configuring user synchronization and authentication with a SAML 2.0 based identity provider.


 Changes in Active Directory configuration for user authentication
TP-7222

As of release 3.3 Kerberos (Windows Integrated Authentication) requires a keytab. Setting up Active Directory-based single sign on in the Team Server with just a password is no longer supported.

If there is no keytab registered, the Team Server will not be able to authenticate with Active Directory, and users will not be able to sign in to the Team Server and HoriZZon (if applicable).

Additionally, AES-256 encryption is now supported for Kerberos.

For more information and instructions, please refer to the release-specific required actions.


 Team Server user session management disabled
TP-6993

Due to compatibility issues arising from the changes in the authentication mechanisms, the user session management functionality in the Team Server is (temporarily) disabled.


 Refined proxy authentication
TP-7342

The proxy authentication has been refined regarding support of Kerberos, NTLM and negotiate-based authentication mechanisms.


View filters and viewpoints

 Automatic application of active view filters on newly opened diagrams and views
TP-4453

Before, when a view filter (for example a color or label view) was active, and another view was opened additionally, the view filter was not automatically applied to this view. To apply it, the view filter needed to be deactivated and activated again with this view open. This has changed. Active view filters are now always automatically applied to a diagram or view the moment the diagram or view is opened.

Bug fixes

General

In the Enterprise Studio Options the Reset button on the General tab, which should restore messages that were dismissed permanently by selecting the Apply the same answer every time without asking or Do not show this dialog again check box, no longer worked.
Also, the window of these messages was not high enough, clipping the check box.

TP-6519

On the Advanced search window, some texts were overlapping.

TP-6590

On the lower part of the Configuration tab in the Enterprise Studio Options, the single word "Protect" was displayed.

TP-6708

When multiple model packages were opened, the Enterprise Studio user interface would show some flickering effects on the icons in the ribbon.

TP-7169

ArchiMate

The «Stereotype» indicator was missing for ArchiMate relationships with a "stereotype" property.

TP-7104

BPMN

The BPMN process check would incorrectly claim that a linked Catch event and Throw event are not having a matching event.

TP-5734

When renaming a Global task in the model browser, none of the Call activities that refer to it would change their name accordingly.

TP-5889

Importing a BPMN 2.0 XML file into Enterprise Studio sometimes resulted in BPMN objects positioned outside the viewable area of a diagram.

TP-6460

Data integration

When importing a parent child relation from Excel using an Excel connection, an error could occur because the context of the import operation could not be established.

TP-7092

If certain relationships could not be created or matched when importing relationships from ServiceNow or an SQL database with a Connection model (e.g., because their end-points could not be uniquely identified), this sometimes had the side-effect that imported attribute values were assigned to the wrong relationships.

TP-7195

DMN

DMN information items linked to ERD entities and attributes or UML classes and attributes in the glossary would not be found when using the Where used function, because these links were stored in hidden attributes of the information item.

TP-5817

A DMN model that was created with the Dutch template "Leeg model met DRD en glossary" could not be removed from a model package.

TP-7202

Canceling the removal of an information item from a DMN glossary could result in a corrupt glossary with an empty row.

TP-7265

Enterprise Portfolio Management

Pasting a stakeholder to a goal in a Stakeholder Analysis View would result in a script error.

TP-1781

Portfolio scores may not have been updated when importing from an Excel worksheet. Object ID's stored in the worksheet could be interpreted as numbers by Excel, due to which a match with the actual object ID's would fail.

TP-7240

HoriZZon

The icons for the ArchiMate concepts Business interface, Application interface and Technology interface were not displayed correctly.

TP-6187

Clicking on objects in a Lifecycle view had no effect.

TP-7545

Language and translation

Changes in the name of BPMN or Amber process diagrams via the Translation table would not always propagate to (for example) HoriZZon.

TP-6445

Metamodeler

When applying metamodel customizations to a model package, the list of model packages in the Apply metamodel to a model package window would not fill out the full height of the window.

TP-7017

The deprecated metamodel TDM was still available for editing in the Metamodeler.

TP-7224

When applying or exporting metamodel customizations in the Metamodeler, viewpoint definitions were not marked as "deployed". Because of this, deployed viewpoint definitions could be deleted from a metamodel without warning, causing possible migration issues.

TP-7261

Modeling

It was not possible to copy the contents of a whole workset by using the Copy command from the workset's context menu.

TP-3724

The Property table incorrectly hid objects that could never be assigned one or more of the selected attributes.

TP-3783

When copying to another model package using matching objects by name, a relation that ends on a relation would sometimes be imported, while it should have been matched with a relation in the other model package.

TP-6030

Turning off the Snap to grid or Snap to object function lost its effect after the model package was reopened.

TP-6358

When deleting an object from the model (using Ctrl+D), references to this object on other, unloaded views could remain, but empty.

TP-7072

The Generate view for function would raise script errors when laying out a view containing references to named read-only relations.

TP-7079

The Delete from model command should delete a selected object reference, the referred object, and all of its other references from the model. When it was not able to delete the referred object, it would still proceed and delete only the selected reference.

TP-7095

Folders at model package level (that is outside models) were ignored in the calculation of chart and portfolio populations. Now these folders are handled in the same way as folders inside models.

TP-7200

Reporting and printing

Report runs on models containing out-of-date portfolio populations would sometimes stop halfway, displaying a pop-up message saying that the population is out of date.

TP-7118

Object values in table charts would no longer be clickable in an InSite Lite report.

TP-7159

InSite Lite, HTML and RTF reports would keep unused old files around when reporting to an existing report location.

TP-7174

Scripting

When a script traverses the characters of a string using the forall statement, the characters returned would be incorrect when one or more of them were multi-byte (e.g. Unicode).

TP-5910

The ternary operator raised a parse error when there was none. To alleviate the problem of script errors being incorrectly raised when using the ternary operator ("?:") in conjunction with a function call, the script engine no longer accepts whitespace alongside the colon (":") when calling a library function.

TP-6455

The default behavior of the optional second parameter "(undoable") of script method removeTaggedValue always defaulted to "true", as a result of which non-persistent tagged values could not be removed in a read-only context.
As of now the default behavior of the parameter defaults to "true" for persistent tagged values, and "false" for non-persistent tagged values. This simplifies removing non-persistent tags from read-only objects.

TP-7345

The script methods childrenInZOrder, canAddNewObject, canAddNewReference, canAddCopyObject, canAddCopyObjects, and canMoveTo incorrectly raised errors or warnings when called on read-only objects. Also, the methods canCollapse and canUncollapse incorrectly returned "true" when called on a read-only object.

TP-7348

The script method addRelationTo quietly failed when the relation would be created in a read-only model.

TP-7539

Team Platform

After opening a project or updating a project with commits from the model package, it would often happen that changes could be made in all the models of the model package, meaning that models outside of the scope of the project could be changed.

TP-4406

A model package that had been suspended while offline could not be opened again without having to reconnect to the Team Server.

TP-4676

When an existing object was dropped on a view, was not saved, was deleted from the model using Ctrl+D, and this failed because the existing object was claimed or had a reference on a read-only view, committing this change to a shared model would result in a corrupted view where the primary reference is missing.

TP-7016

In tracked and shared model packages, moving the end point of a relation to another object sometimes was not applied to all views where this relation was shown.

TP-7075

In rare, very specific cases of data inconsistency in a tracked or shared model package, Enterprise Studio would freeze when trying to delete the affected objects.

TP-7152

Using the object properties form (only available on ArchiMate objects) would make the model dirty and claim the associated object and view.

TP-7176

When the example model package "Archisurance & Portfolios" was used in a context that made its portfolio views read-only (for example when these were outside the scope of a project), clicking the buttons at the top of an open portfolio view (Dashboard, Population, Scores etc.) would raise a script error.

TP-7269

Interacting with controls on views in read-only models could lead to unexpected script errors.

TP-7271

The object properties form (only available on ArchiMate objects) suggested it was possible to edit properties of a read-only object, only to have the changes rolled back afterward, with a script error.

TP-7272


Release 3.2 - 8 June 2018

This release is important for all users.This release has a changed metamodel configuration. You need to migrate your model packages with metamodels embedded (.xmam), or stored in your personal storage or on the Team Server to materialize the changes and fixes in this release.

New features and enhancements

General

 Check for damaged relations in check and repair function
TP-3781

The Check and Repair function now also checks for damaged relations that are no longer connected to an object at both sides. These relations are removed during repair.


Configuration

 Display of full configuration location paths in configuration options
TP-6437

On the Configuration tab of the Enterprise Studio Options, in the Location section, previous configuration paths in the configuration location selection box, are no longer cut off when their length exceeds the standard width of the list.



 Replacement for resize properties
TP-6489

From now on, in the configuration, view definition files (.mmd) should use the "resizeStyle" property instead of "isResizable" or "resizeProportionally". The latter properties are deprecated and will be removed in a future release.

Possible values for the "resizeStyle" property are: resize (default), noresize, resize_horizontally, resize_vertically, and resize_proportionally.


Data integration

 More information in log file for periodic data exchange
TP-5784

The log file that is generated when performing periodic data exchange for an Excel, ServiceNow or SQL connection, has been extended. The file not only contains "output" statements and script errors, but now also logs all messages written to the Enterprise Studio messages window including, for example, collaboration conflict messages in shared model packages.


 Technopedia® data access limited to Designer users
TP-5829

Access to the Technopedia® data from Enterprise Studio is from now on only possible for users who have the Designer role in the Team Server.


 Formatting options for date and money values on Excel import
TP-6361

When working with Excel connections using ADOdb, ADOdb does not recognize date and money values; ADOdb exports dates as text and money as number values. As a result, when importing using ADOdb date and money values, their format is unknown. Also, when importing using Excel, date and money values may be strings and numbers instead.

In order to have date and money values in a known format after import, settings have been added to the properties of column objects that are linked to a date or money attribute, to set these formats. These settings are activated by default, and can be changed or deactivated if needed.



For more information, see Text to date and number to money conversion for Excel import.

DMN

 Control for changing input data into decision
TP-6073

An input data element can now be changed into a decision without losing the links to other elements, the properties in the glossary, and the use of these elements in decision logic. The new control on an input data element can be used for this.



 Evaluation decisions handle incomplete input data specification
TP-6075

The evaluation of decisions in DMN has been adapted so that it can also handle an incomplete specification of input data.


Enterprise Portfolio Management

 Configuration migration needed for using portfolio views
TP-6513

Due to changes in the scripts of the Enterprise Portfolio Management functionality in ArchiMate, embedded configurations in existing model packages (saved on the Team Server, in the personal storage, or saved as XMAM) need to be migrated to the new configuration provided with Enterprise Studio to avoid errors when using portfolio views.

Custom configurations need to be re-based on the new standard configuration.


Enterprise Studio Online

 Support for Safari on Mac
TP n.a.

Enterprise Studio Online now also supports Safari on Mac computers.


 Support for Microsoft Office
TP-6164

Enterprise Studio Online now supports the use of Microsoft Office.

If you want your BiZZdesign Connect Excel connections to use Excel instead of an ADOdb connection (the default), you can activate the use of Microsoft Office in Enterprise Studio Online. Also, reporting to Word, Excel and PowerPoint is possible if the use of Microsoft Office is activated.

To be able to activate Microsoft Office, an Office 365 Pro Plus license is required.

For more information about activating Microsoft Office in Enterprise Studio Online, see Use of Microsoft Office in Enterprise Studio Online.


HoriZZon

 Interface changes
TP n.a.

Few changes have been made to the HoriZZon interface:

  • There is a new sidebar on the left side with the sections Favorites, Sites, Dashboards, Workflow, and Manage.
  • The Manage functionality has moved from the settings (accessible via the control in the toolbar) to its own Manage section in the sidebar.
  • Favorite views now have their own page, accessible via the Favorites section in the sidebar.


 Dashboards in HoriZZon
TP-5476, TP-5477

HoriZZon now supports including and sharing dashboards. Dashboards can be included via the Manage section of HoriZZon, and will be available in the Dashboards section. Including dashboards can be performed by users with the Lead Designer role. Viewing the dashboards does not require any role.



For more information, see Adding and sharing dashboards in HoriZZon.


 New workflow section "My Requests"
TP-6281

The workflow functionality in HoriZZon now contains a section My Requests, allowing users to see the change requests and review requests they created, and follow their status. Each request shows the current state, and the active tasks for the request.



This feature is currently in a beta testing phase. You are welcome to try it out in your test environment, but be careful when using it in your production environment. If you are interested in the beta version of this feature, please contact the BiZZdesign service desk.

 Extended site scope selection
TP-6288

The model package structure in which the scope of a site can be specified, now also supports selecting folders and model-level folders for setting the scope. Previously, only models were selectable for scoping.



 Display of object views in object properties pane
TP-6289

When selecting an object in a view the object properties panel that slides in now also shows all the views the object appears on.



 Improved indication for applying changes in site management
TP-6313

The Apply button on the site management page now turns to green whenever changes are made that need to be applied. This will prevent that you leave the page without saving your changes.



 Improved object navigation
TP-6340

Object navigation with the relations explorer has improved. When navigating objects using the relations explorer, it is now possible to click a related object, which directly opens the object page.



 Support for custom workflows
TP-6346

HoriZZon now supports the use of custom workflows, in addition to the workflows predefined by BiZZdesign.

If your organization has its own workflows that you would like to use in HoriZZon in addition to or instead of the built-in workflows, BiZZdesign can be of service. If you are interested, please contact your CSO consultant at BiZZdesign.

This feature is currently in a beta testing phase. You are welcome to try it out in your test environment, but be careful when using it in your production environment.

 Security and back-end improvements
TP-6365, TP-6423, TP-6424, TP-6475

Security improvements have been made to HoriZZon by adding the following configuration possibilities:

  • CORS filter (Cross-Origin Resource Sharing)
  • HoriZZon session timeout
  • root directory for all the data used by HoriZZon
    In addition, the stability of the back-end of HoriZZon has been improved.


 Automatic removal HoriZZon session after signing out
TP-6425

From now on, when users sign out of HoriZZon, their HoriZZon sessions are also automatically removed for security reasons.


 Object selection in charts
TP-6470, TP-6478

It is now possible to select the individual objects in charts from Enterprise Studio to navigate them and view their properties.



 Setting scope and start view combined in site creation
TP-6946, TP-6965

Setting the scope and the start view of a site is now done on one page. As a result of this, selecting a start view is no longer optional. First you select the scope, and after that the start view. The currently selected start view is shown on the right of the site creation page.



Language and translation

 Support for UTF-8 with BOM encoding in configuration translation files
TP-6194

Translation files (.mps) in the tool configuration now may also use "UTF-8 with BOM" encoding, making them independent of having the right code page when editing translations.

If no UTF-8 Byte-Order-Mark (BOM) sequence is found at the start of the file, it is assumed, as before, that the file is encoded using the default code page for the language.


 Custom menu translations moved to MPS files
TP-6199

XML-based menu files (for example custom-menu.xml) in a (customized) configuration no longer contain the translations of their command labels and tooltips. Instead, each label defines a unique ID that can be assigned translations via the configuration's MPS files.

Existing customized menu files containing translations are still accepted by Enterprise Studio, but their translations should be moved to the MPS files (menus.mps) at the first opportunity to prepare for removal of this option in a future software release.


Metamodeler

 Removal of obsolete message upon opening Metamodeler
TP-5797

When opening the Metamodeler, Enterprise Studio no longer displays the message for a "potentially long running operation", as this message had become obsolete.


 Custom viewpoint definitions
TP-6119

The Metamodeler has been extended with the possibility to create custom viewpoint definitions for the ArchiMate metamodel in order to work with custom views in your ArchiMate model. The viewpoint editor allows you to add allowed concepts and relations, and set their default graphical appearance in a WYSIWYG manner.


If you already have custom viewpoint definitions, follow the release-specific instructions for 3.2 from the Enterprise Studio Update Guide to upgrade them to the new tool configuration.

For more information about creating custom viewpoint definitions, see Creating a custom viewpoint definition.

 Custom ArchiMate menu definition
TP-6170, TP-6266

In the Metamodeler, it is now possible to edit the New context menu for adding views to an ArchiMate model, in order to add, remove or move menu categories and views. In this way you can make custom views available and hide views that are not suitable for the modelers in your organization. The context menu can be customized in the Menu definition view within the Viewpoints folder of the ArchiMate metamodel.


If you already have customized menu definition files, follow the release-specific instructions for 3.2 from the Enterprise Studio Update Guide to upgrade them to the new tool configuration.

For more information about creating a custom menu definition, see Creating a custom menu definition.

Modeling

 Generate view option for laying out after generation
TP-5287

The Generate View for dialog now has the Lay out afterward check box on the View Type tab. When selected (the default), the option will do a full layout of the view after generating it. If deselected, a simple grid layout is used.



 Pagination in model browser and navigator
TP-6435, TP-6715, TP-6580, TP-6986

Pagination has been implemented for the model browser and the navigator, meaning that when an object has many underlying objects and/or relationships, only the first 200 are shown, followed by a "more" item displayed with three dots that displays the number of remaining items. Double-clicking it will retrieve the next 200 objects and/or relationships.



Initial issues with the Locate object command and the Jump to object feature in the Messages window (in case of layers containing more than 200 objects), and with selected items that were not shown if they were beyond the initial number of items shown, have been fixed.


Scripting

 New Query tool button for pausing script
TP-6095

The Break button has been added to the Query tool that, when clicked, pauses the run and allows the user to start debugging from that point (as if the user had put a break point at that location). To resume the execution, click Continue.



 New script methods for accessing relation arrow heads
TP-6214

The scripting language has been extended with methods that allow access to the shapes of relation arrow heads, much like the methods that already exist for the shape of a regular object. The new methods are fromShape, toShape, setFromShape, setToShape, fromShapeIsSet, toShapeIsSet, resetFromShape and resetToShape.For more information, see fromShape, toShape method and (re)setFromShape, (re)setToShape method.

Team Platform

 User invitation limitation on e-mail domain
TP-5749

To limit user invitations, a Team Server system administrator can now specify which e-mail domains are allowed for new users on the Team Server. For example, to allow only users with an e-mail address such as j.doe@bizzdesign.com , it is now possible to specify that "bizzdesign.com" is allowed. Users with a different domain will not be allowed.

The e-mail domain setting is available on the General settings page of the Team Server.



For more information, see Setting Team Server invitation limitations.



 Activity Console synchronization improvements
TP-5879

Changes have been made to the Activity Console synchronization process to improve the performance.


 Team Server user session management
TP-6049

For each user the session information regarding active Team Server sessions can now be viewed. The information includes the user agent, IP address, creation date, last access date, and the number of requests made.

Personal session information is available to each user on the user page, and an overall session overview of all users is available on the User sessions page in the Team Server settings. This page is only accessible to System Administrator users.


Any session that existed before the 3.2.0 release will only have its identifier listed, and will not have a creation date. Those sessions may represent invalid sessions.

The Team Server settings are not available when working with a hosted Team Server (used with Enterprise Studio Online or locally installed Enterprise Studio).

 User synchronization and authentication via Azure Active Directory out of beta
TP-66183

Team Server user synchronization and authentication via Azure AD, which was still in beta testing phase in release 3.1.1, is now fully functional. Additionally, now user group synchronization with Azure AD is supported.

For user groups synchronized with Azure AD, the following applies:

  • Only the permissions (roles) of these user groups can be changed in the Team Server. Other properties and the group's members must be updated in Azure AD.
  • All users in a user group will automatically have the permissions from that group.
    Please contact the BiZZdesign service desk for further instructions if you want to set up user synchronization and authentication via Azure Active Directory for your Team Server and HoriZZon portal.


 Protection against removal of model packages from the Team Server
TP-6256

It is now possible to protect model packages from being (accidentally) removed from the Team Server. Selecting the Protect from deletion check box on a model package page will make the Delete model package button unavailable, so that the model package cannot be deleted. The check box is only visible to Administrator and System Administrator users.



For more information, see Protecting model packages from deletion.

 Time before Azure AD users are removed from Team Server configurable
TP-6261

The Team Server now allows System Administrator users to configure the number of hours that users and user groups remain in the Team Server after being removed by Azure AD (via SCIM). After the configured time has elapsed the users will be removed from the Team Server. The duration can be set in Hours before removal on the Authentication settings page of the Team Server.


The Settings menu is not available in a hosted Team Server (used with Enterprise Studio Online or locally installed Enterprise Studio).


For more information, see Configuring user synchronization and authentication with Azure Active Directory.


 Default session timeout for Team Server
TP-6413

The Team Server will now default to a session timeout of 30 minutes if no valid value has been configured. Furthermore, infinite session timeouts are no longer allowed.


 Team Server security improvements
TP-6426 TP-6427, TP-6428

The following security improvements have been made to the Team Server:

  • The remember me cookie no longer includes sensitive data like the username.
  • The session cookies of the Team Server and repository-object-api have HTTPOnly and secure attributes enabled.
  • The XSRF cookies now have the HTTPOnly attribute enabled.
  • Headers to prevent caching by the browser have been added to the responses of the Team Server and repository-object-api. This prevents sensitive data being stored in the cache.


 Improved handling of slow Activity Console startup
TP-6436

When during the startup of Enterprise Studio the Activity Console needs more time to initialize (for example when it administers a large number of model packages), Enterprise Studio will no longer display a connection error, but instead wait for the Activity Console to finish its tasks.


 Simplified model package update in case of configuration changes
TP-7008

When another user has committed a configuration change to the model package you are working on and you want to update your copy of the model package, you no longer need to update this configuration change first, and then update the model package again to fetch all other changes. From now on one update will suffice. The same applies to updating a project with contributions from other users.

Take note that updating a project with contributions from the master model package still requires two steps.


 Improved opening time model packages
TP-7093

The initial opening time of a model package has been improved.

Bug fixes

General

The ribbon's collapsed state, the position of the Quick Access toolbar, and the possibly tailored entries of the Quick Access tool bar were not correctly stored when closing Enterprise Studio.

TP-4965

The tooltip displayed when hovering a model package in the model browser showed confusing and sometimes wrong information for some of the types of model packages. These tooltips have been improved.

TP-5499

Amber

It was not possible to create or edit Amber models in the 32-bit build of Enterprise Studio, except when using a custom configuration and selecting the Reload configuration at startup check box (in the Enterprise Studio configuration options).

TP-6442

ArchiMate

In the settings of the life cycle view, the Show Technopedia end of life option for showing Technopedia end-of-life data was visible.

TP-6223

The following concepts were missing in ArchiMate viewpoints, and have been added now:

  • Junction, Or-junction, Association relation and Influence relation to the Goal realization viewpoint.
  • Junction, Or-junction and Association relation to the Goal contribution viewpoint.
  • Association relation to the Principles viewpoint.

TP-6362

BPMN

When a BPMN collaboration diagram was deleted before it had been opened at least once in the session (for example when deleting a model containing the diagram), some objects on the process diagram this collaboration refers to would also be deleted.

TP-5442

In certain cases, inconsistencies in a BPMN model caused the BPMN export to fail with a scripting error.

TP-6286

Configuration

The icon of a custom view type would be omitted from the model browser after saving the model package to a personal or remote storage and detaching the custom disk configuration.

TP-4190

Data integration

After exporting portfolio scores to Excel, an import of this data could fail because the stored object IDs we no longer valid.

TP-6320

Connecting with BDNA Technopedia, sometimes failed due to authentication problems with the Activity Console.

TP-6472

If a query had been specified for a ServiceNow table in a Connection model, retrieving the table columns sometimes did not work. As a result, column properties could not be verified, and also the validation of the connection failed.

TP-6496

The report function of the Excel import (can be activated in a connection's settings) caused an error when deleting a relation.

TP-6504

DMN

The evaluation of DMN expressions sometimes gave inaccurate results because literal real numbers were rounded off to three decimal places.

TP-6225

Enterprise analytics

Highlighting a slice from a pie chart by clicking a legend item raised a script error in model packages created with earlier versions of Enterprise Studio.

TP-6658

HoriZZon

The feedback button was still present in HoriZZon.

TP-5384

If the "teamserver.url" configuration value of the repository API server contained a URL ending with a '/' and SSO was configured in the Team Server, HoriZZon did not show the button to sign in with a Windows account.

TP-6126

Replicated files could get corrupted under certain conditions. This could block any updates to HoriZZon.

TP-6216

Links in HoriZZon would not open the view but the object page for the view if the linked object was a view.

TP-6287

When views in HoriZZon got larger, the way of scaling did not work well, leaving a lot of white space above and below the view.

TP-6299

When reporting a Life cycle view that is using a color view to HoriZZon, the legend was always placed in the top left corner, and it was not possible to move the legend. In case of multiple legends, they would be displayed on top of each other.

TP-6301

The model browser in HoriZZon would show various types of meaningless objects, like view charts, view graphics and command definitions.

TP-6535

Processing of commits by the repository back end failed for some commits, which caused the whole replication process to stop, leading to an out-of-sync status between Enterprise Studio and HoriZZon.

TP-6684

Language and translation

When the application setting for model language was set to a language for which there are no model package templates available, and that has no comparable languages that do, the New tab in the Backstage view did not list any templates to create a new model package with.

TP-5862

Metamodeler

Line endings would show up as strange characters in serialized default values on the attribute forms in the Metamodeler.

TP-3216

The Metamodeler did not support UTF-8 encoding for translations, making non-ANSI characters in translations look distorted.

TP-4982

When the name property of an object is defined as read-only in its profile definition, the model browser still allowed editing the name.

TP-6212

Modeling

Performing auto-layout on a view with a name that exceeded ca. 140 characters would fail with a script error.

TP-4069

When an object having many custom documentation tabs was selected, many times the rightmost tab was activated instead of the leftmost.

TP-4214

When undoing a deletion of objects and relations on a view, some of the deleted relations would not reappear until the view was refreshed (for example with F5).

TP-4955

100% transparency on text was not really 100%.

TP-5441

Deleting a part of a model package could in some cases result in Enterprise Studio to hang.

TP-5443

After copy or pasting objects to another model package, object hyperlinks in documentation text would no longer show a single number (the referred object's local ID) as their address, but a longer expression, mostly containing "nil" or "rwc" (depending on type of model package).

TP-5668

When copying objects from one model package to another, including a cross-model relationship in the selection would often make it impossible to paste into the target model package.

TP-5706

When drawing an object reference for which there already exist multiple instances with the same name and type, Enterprise Studio offered the user to attach the new reference to one of those existing objects, but also allowed selecting an object with equal type but with a different name.

TP-5712

Collapsing branches in an existing Navigator after deleting relations of which roles are shown in the Navigator, could crash the application.

TP-6009

When deleting models or package folders from a model package, references to objects therein on views in another model were not deleted but became invalid (referring nothing) instead.

TP-6664

Reporting and printing

In InSite Lite reports, a view hyperlink object referring an Amber or BPMN diagram would open its properties page instead of the diagram's view page. Also, links to views within documentation did not open the view when clicked.

TP-1741

RTF reports no longer displayed correct page numbers in the footers of the reported document.

TP-5884

The HTML report would show "page not found" when clicking on a view reference.

TP-5945

Scripting

Searching in the Metamodel browser, which is part of the Query tool, could take very long, and lead to excessive memory use. Also, the browser would show object types multiple times at different locations, and would not jump through all results when the search button was clicked repeatedly.

TP-5972

When using too many (or too few) arguments with the exp script function, the resulting error message was incorrect.

TP-6303

Running a script from the command line would crash Enterprise Studio when the script's log file was locked by another application.

TP-6331

Team Platform

When a shared model package was closed, any claims belonging to changes that were undone before they were saved would cause claiming conflicts. From now on, these changes are automatically discarded. Please note that claims for changes that were (auto)saved before being undone still remain: these have to be discarded manually as before, in the Backstage view, via Timeline > Undo changes.

TP-3845

After trying (in vain) to delete a claimed object together with its connected relations, the object would return, but some of the deleted relations would not reappear until the view was refreshed (for example with F5).

TP-4811

The generic error message "File '...' cannot be opened. It is valid, but the model is still empty" was very confusing to the user. The message now has been improved to show more details about the underlying problem (mostly the connection with the Team Server was lost).

TP-4927

In some situations the audit log page would not show any information, for example when specific characters like a backslash or double quote were entered in a username on the login page with an invalid password.

TP-5024

Synchronizing large amounts of LDAP users in the Team Server could fail with a generic error.

TP-5719

The LDAP user import in the Team Server was limited to importing 1000 users. To solve the issue, options have been added to the Team Server Authentication settings page that can be activated for a trouble-free import.


For more information, see Configuring user synchronization and authentication with Active Directory.

The Settings menu is not available in a hosted Team Server (used with Enterprise Studio Online or locally installed Enterprise Studio).

TP-6096, TP-6682

An internal error occurred on the Team Server when updating the authentication settings.

TP-6124

When running the Team Server, the SQL database increasingly took more memory, eventually causing problems.

TP-6228

If the Activity Console was not able to synchronize with a storage place, it was not possible anymore to perform the needed re-authentication via the storage place in the Enterprise Studio Options.

TP-6309

When working in a shared model package, the icons in the Create pane could periodically turn into a gray, disabled state.

TP-6311

The Activity Console was not able to connect to the Team Server and HoriZZon when security protocol TLSv1 was disabled for the Team Server and HoriZZon.

TP-6324

Team Server user sessions started before the 3.2.1 release did not have a last accessed date set if they were never used by the user anymore. The sessions would expire, however automated clean up would not happen due to the missing last accessed date.

TP-6412

Using a Team Server JSSC file a second time would result in the unnecessary creation of a second, fully identical storage place in Enterprise Studio.

TP-6419

The Team Server would create a PID file, which could sometimes cause issues when the server would be rebooted. A PID file is no longer created.

TP-6446

When deleting all user sessions for a specific user or deleting all sessions for all users (including users' active sessions), the page would not properly reload, and the users whose active session had been deleted, would not be directed back to the sign-in page of the Team Server.

TP-6559

When synchronizing with LDAP in the Team Server, changed LDAP users were not shown on the synchronization preview page.

TP-6645

When a user who had not responded to an invitation e-mail, was removed after two weeks, the person who invited that user would get a notification e-mail of that removal every hour.

TP-6947

User provisioning in Azure AD did not always work correctly.

TP-7098

UML

In a UML model, UML class attributes and operations could not be assigned the "report feedback" profile, as is the case in an Amber model.

TP-6233


Release 3.1.7 - 27 March 2018

This release is important for all users.

New features and enhancements

Enterprise Studio Online

 New corporate design look & feel
TP n.a.

The Enterprise Studio Online environment has a new look & feel matching the BiZZdesign corporate design, including colors and logos, an updated feedback form, and a new landing page when a session ends.

Bug fixes

Team Platform

In very specific circumstances Enterprise Studio would not allow editing a newly opened model package, giving a warning there was an inability to check for collaboration conflicts.

TP-6454


Release 3.1.6 - 16 March 2018

This release is useful for users who work with Enterprise Studio Online, and/or with the BiZZdesign Connect Excel import (without Excel application).

New features and enhancements

Enterprise Studio Online

 Performance improvements
TP-6359

Performance improvements have been made to reduce slowdown when working with Enterprise Studio Online.

HoriZZon

 Improved scaling site browse page
TP-6350

The browse function on the site browse page now contains a horizontal scroll bar so deeper nested models can be properly viewed as well.

Bug fixes

Data integration

When importing from Excel using an ADOdb connection, the import of properties for some objects was skipped.

TP-6389

HoriZZon

Browsing a site using the model browser caused HoriZZon to hang in case of large model packages.

TP-6353

When an object has many relations (several hundreds or larger), and was explored in HoriZZon with the object inspect or explore function, HoriZZon would likely crash, or run very slowly. The number of relations that can be shown in the object explore or inspect function is now restrained to a maximum of 50 relations per object. When relations are being skipped, the user is informed, and the number of skipped relations is also shown on each object, when applicable. Also, the total numbers of elements in the view is restrained to 500 elements.

TP-6355

Team Platform

Enterprise Studio would sometimes freeze up or raise errors after copying a view containing a view reference from a shared model package to another package.

TP-6093


Release 3.1.5 - 16 February 2018

This release is useful for users who work with HoriZZon and/or with the BiZZdesign Connect Excel import.

Bug fixes

Data integration

Performance improvements have been made for the Excel import when used in Enterprise Studio Online, or locally without Excel being installed.

TP-6265

HoriZZon

The lookup of fonts used by HoriZZon was not platform independent.

TP-6061

Sometimes new commits or model packages would not be replicated from the Team Server to HoriZZon.

TP-6248


Release 3.1.1 - 5 January 2018

This release is useful for all users.This release has a changed metamodel configuration. You need to migrate your model packages with metamodels embedded (.xmam), or stored in your personal storage or on the Team Server to materialize the changes and fixes in this release.

New features and enhancements

General

 Login options renamed to "sign in"
TP n.a.

For consistency reasons, all login options in the Team Server, Enterprise Studio and HoriZZon that require your credentials to access, have been renamed from "log in" to "sign in". Example:



ArchiMate

 Updated ArchiMate example models
TP-4073

The ArchiMate example models in Enterprise Studio have been updated:

  • The "ArchiSurance" example has been replaced by a new "ArchiSurance TOGAF" example, which also includes examples of the use of the new concepts added in ArchiMate 3.0.
  • The "ArchiSurance and Portfolios" example is still based on the existing example model, but some model errors have been fixed.
  • The "ArchiSurance and Profit with Canvas" example has been removed.


 Extended Coach view
TP-4633

The coach view, which can be used in ArchiMate models for defining cyclic methods for modeling, has been extended with the possibility to define a sequential method and a method that resembles the Architecture Development Method (ADM) of TOGAF{^}®^TOGAF is a registered trademark of The Open Group.

In addition to the existing components (coach, view browser and help box), the following components can now be added to the Coach view:

  • A description box
  • A thumbnail box that may contain views as thumbnails


For more information, see Components of the Coach view.

 Reorganization of ArchiMate views in context menu
TP-5707

The context menu for adding new views to an ArchiMate model has been reorganized in order to have a better separation between the views that are based on ArchiMate 3.0, and other views that offer extra functionality. All of the ArchiMate views are now grouped under the category ArchiMate. This also includes the Value stream views that are not officially part of the standard, but are similar in function and type to the ArchiMate views.

The following new categories have been created that contain views with additional functionality, both existing and new views, which are using ArchiMate elements and relationships:

Strategy

  • SWOT analysis (new)
  • PESTEL analysis (new)
  • Porter's Five Forces (new)
  • Balanced Scorecard (new)
  • Scenario analysis (new)
  • Strategy on a Page (new)

Business model

  • Business Model Canvas® (new)
  • Customer Journey Map
  • Business Outcome Journey Map (new)
  • Ecosystem view (new)

Planning

  • Roadmap view
  • Life cycle view



The Portfolio and Risk and Security categories of views have remained unchanged.

The icons for the existing views in the different categories have been updated in order to match to the style of the new views.


 New strategy views
TP-4625, TP-4628, TP-4631, TP-5494

Several new strategy views have been added, and make use of ArchiMate elements and relationships. All views are available in the new Strategy category of views. They are:

SWOT analysis

The SWOT analysis view offers the possibility for organizations to evaluate their internal strengths and weaknesses (resources and capabilities that enable or hinder the design and implementation of strategies), as well as its external opportunities and threats (areas which enable or hinder organizational performance).

In the TOWS matrix mode of the SWOT view, users can design strategies aimed at exploiting their organization's opportunities (O) and strengths (S), while neutralizing their threats (T) and improving their weaknesses (W).



For more information about SWOT analysis online, see SWOT analysis (Wikipedia), and SWOT Analysis - Do It Properly (Strategic Management Insight).

PESTEL analysis

The PESTEL analysis view offers the possibility for organizations to monitor and analyze their macro-environment in order to identify potential opportunities and threats, based on several categories. The PESTEL analysis has several variations, based on the kinds of categories which are used to assess the environment.



For more information about PESTEL analysis online, see PEST analysis (Wikipedia), and PEST & PESTEL Analysis (Strategic Management Insight).

Porter's Five Forces analysis

The Porter's Five Forces view offers the possibility for organizations to monitor and analyze their industry in order to determine the intensity of industry competition and its profitability. This is done by investigating the following five forces in their industry:

  • Bargaining power of suppliers
  • Bargaining power of customers
  • Threat of new entrants
  • Threat of substitutes
  • Industry rivalry


For more information about Porter's Five Forces analysis online, see Porter's Five Forces analysis (https://en.wikipedia.org/wiki/Porter's_five_forces_analysis) (Wikipedia), and Porter's Five Forces (Strategic Management Insight).

Balanced Scorecard

The Balanced Scorecard view combines the functionality of two popular and interlinked strategy techniques: Strategy map and Balanced Scorecard. The Balanced Scorecard view offers the possibility for organizations to plan and manage their performance in terms of measures, targets, and initiatives which are defined for several strategic objectives, based on four perspectives: financial, customer, internal process, and learning and growth.



For more information about the balanced scorecard online, see Balanced scorecard and Strategy map (both Wikipedia), and Balanced Scorecard Basics (Balanced Scorecard Institute).

Scenario analysis

The Scenario analysis view offers the possibility for organizations to define and analyze what kind of impact certain strategic themes/factors/drivers can have in the future, from the perspective of the possible scenarios associated with them. As an example, Internet of Things, Blockchain, etc. are themes which can be used for a Scenario analysis view.

When combined with the Business Model Canvas®, the Scenario analysis view can be used to perform a business model stress test.



For more information about scenario analysis online, see Scenario planning (Wikipedia) and Business model stress testing: A practical approach to test the robustness of a business model (ScienceDirect).

This feature is currently in a beta testing phase. You are welcome to try it out in your test environment, but be careful when using it in your production environment.

Strategy on a Page

The Strategy on a Page view can be used to support storytelling by offering the possibility to combine different types of information (strategic, tactical, operational) in a way that can be used to communicate with both technical and non-technical stakeholders.


For more information, see Strategy and business modeling in Enterprise Studio.

 New business model views
TP-4629, TP-5288, TP-5600

Several new business model views have been added, and make use of ArchiMate elements and relationships. All views are available in the new Business model category of views. They are:

Business Model Canvas®

The Business Model Canvas view offers the possibility for organizations to design, assess and visualize their business model. In this view, the business model can be designed with the help of nine blocks: key partners, key activities, key resources, value proposition, customer relationships, channels, customer segments, cost structure, and revenue streams.

The view should not be confused with the existing Business Model Canvas from the BMC metamodel.



For more information about Business Model Canvas online, please refer to Strategyzer.com.

Business outcome journey map

The Business outcome journey map view has been added to the ArchiMate metamodel. The view is similar to the Customer journey map. It can help model the business outcomes of an organization in relation to the value streams that are realizing it, to the value propositions they can offer to their customers, and to the analysis of the capabilities, which are making all of this possible.



For more information about business outcome journey maps, please refer to the BiZZdesign blog Why Business Outcome Journey Maps are a useful technique for business architects.

Ecosystem view

The Ecosystem view offers the possibility for organizations to model and analyze the economic community in which they interact with other stakeholders, such as organizations, groups and individuals. These stakeholders can be categorized, based on how closely their interact with the organization, as being part of the Core business, Extended enterprise, or Business ecosystem. The result of the interactions between stakeholders is the production and exchange of value.



For more information about business ecosystems online, see Business ecosytem (Wikipedia), Mapping Business Ecosystems (Partnering Resources), and Introduction: Business ecosystems come of age (Deloitte Insights).For more information, see Strategy and business modeling in Enterprise Studio.

 Change in automatic layout for Roadmap and Life cycle view
TP-5620

The automatic layout, which could be performed on the Roadmap view and Life cycle view using the layout control in the canvas menu, has changed.

From now on the automatic layout can be performed via the regular auto layout function, accessible via the ribbon Home > Automatic Layout, or by pressing F6. Because of this change, the layout control is no longer available in the canvas menu.


Data integration

 Data integration with Technopedia®
TP-4323

Integration with Technopedia® (from Flexera + BDNA) is now supported. The functionality allows for the integration of base product information and selected content packs from Technopedia®. This information is described in predefined, separate profiles; one for all base information and one for each content pack.

The Technopedia® functionality is only available within model packages that are stored on the Team Server. It also requires HoriZZon.

This feature is currently in a beta testing phase. You are welcome to try it out in your test environment, but be careful when using it in your production environment. If you are interested in the beta version of this feature, please contact the BiZZdesign service desk.

 Import/export of data structures
TP-4409

Adding an attribute as property for a meta-element in an Excel connection mapping table now supports attributes of category "struct" to enable importing and exporting data structures. Upon selection of the attribute, the user is asked to select a member from the structure. This member will then be treated as an attribute for the import or export.



 Making imported tagged values non-persistent
TP-5834

Imported tagged values in a Connection model were persistent by definition, until now. From now on tags in a meta-element can be defined as non-persistent, resulting in non-persistent imported tagged values. To define a tag as non-persistent, hold down Shift while clicking the tag icon, and make your choice.



For more information, see Making imported tagged values non-persistent.

ERSM

 Several improvements in the ERSM functionality
TP-4800

The following improvements have been made in the ERSM functionality:

  • In the settings of a risk and security view, controls have been added to show and hide all the traffic lights on the view at once: .



  • A warning icon has been added for a manually overridden control strength value of a control measure, in case the value is derived from one or more control services. 



  • The probable loss magnitude of a loss event can now be linked to the value of associated assets, creating a dependency. If the value of the asset changes, the probable loss magnitude changes with it. A warning icon has been added for a manually overridden probable loss magnitude in case the value is derived from one or more assets. 

     

HoriZZon

 Generate table views
TP-5188

It is now possible to create viewpoints of data tables with selected properties and/or metrics from the objects and relations in a diagram or view. The table view can be generated via the More options menu of a property of a selected object.



The generated table view is shown on the page, below the diagram or view. The contents of the table can be filtered, overall and per column.



For more information, see Working with viewpoints in a site.


 Creating and processing review requests for model views and objects
TP-5563

This new feature provides a collaborative modeling experience. Users can request and process reviews and changes on model views and objects in HoriZZon.



A task list in HoriZZon provides a workflow-driven view on the models and allows commenting and responding to tasks.


This feature is currently in a beta testing phase. You are welcome to try it out in your test environment, but be careful when using it in your production environment. If you are interested in the beta version of this feature, please contact the BiZZdesign service desk.

 Single sign-on for HoriZZon
TP-5740, TP-5676

Users can now sign in to HoriZZon using their Windows account (Active Directory) or their organizational account (Azure Active Directory) if single sign-on for Active Directory or for Azure Active Directory has been configured in the Team Server.

This feature is currently in a beta testing phase. You are welcome to try it out in your test environment, but be careful when using it in your production environment. If you are interested in the beta version of this feature, please contact the BiZZdesign service desk.

 Better insight for site scope selection
TP-5870

The tree structure with model package components (site management) for setting the scope of a site now provides better insight in the selection of the scope, showing a correct indeterminate check status, and the number of selected models for each tree level.



 Site browser only shows folders with content
TP-5896

The Browse function of a site shows the contents of a site in a tree structure, including all the folders in the site. Because of the scope of a site, folders could turn out to be empty, which could be confusing.

From now on, only folders with content (models) are shown in the browser.



Modeling

 Generate view for read-only objects
TP-5725

The Generate view for function is now allowed also for read-only objects, when these objects are on a diagram or view that is not read-only. Objects can be read-only when working together on projects (Team Platform).


Scripting

 Improvements to scripted auto layout
TP-5620

The script method autoLayoutDiagram is now able to also perform the layout of relations (equivalent with the F7 commands in Enterprise Studio). To determine if auto layout is supported on a view, a new method canAutoLayoutDiagram has been added.For more information, see autoLayoutDiagram, canAutoLayoutDiagram method.

Team Platform

 Team Server session timeout and "remember me" cookies configurable
TP-4618

The maximum duration of the session timeout and the "Remember Me" cookies can now be configured in the Team Server by users with the System Administrator role. The cookies settings are available on the General settings page of the Team Server.


The Settings menu is not available in a hosted Team Server (used with Enterprise Studio Online or locally installed Enterprise Studio).

For more information, see Configuring the Team Server cookies settings.

 Team Server log rotation configurable
TP-4703

The Team Server has logs containing technical information about events when running the Team Server. By default the logs will be rolled over based on the size of the log file, but it is also possible to configure the log rotation by date.

For more information, see Configuring Team Server log rotation.

Configuration should only be performed by users who are familiar with installing and configuring software and databases.

Configuring log rotation is not possible when working with a hosted Team Server (used with Enterprise Studio Online or locally installed Enterprise Studio).

 Support for PostgreSQL database
TP-5410

In addition to SQL Server, PostgreSQL 9.6.5 or higher is now a supported database management system for the Team Server.

For more information, see Team Server installation and setup.


 Team Server account lockout policy
TP-5413, TP-5452

It is now possible for Team Server System Administrator users to specify the number of consecutive failed sign-in attempts after which a user is locked out, as well as the duration the lockout will last. The account lockout settings can be configured on the General settings page of the Team Server.

The default lockout time is 30 seconds after 5 unsuccessful login attempts.


The Settings menu is not available in a hosted Team Server (used with Enterprise Studio Online or locally installed Enterprise Studio).


For more information, see Configuring the Team Server lockout policy.


 Additional security for cookies
TP-5454

Cookies in transit have had their security re-enforced by adding the secure header, without which it would be potentially vulnerable to MitM attacks, as it could accidentally be sent over an unencrypted connection. Please take note that all BiZZdesign online solutions are deployed over secure connections, therefore this problem could not occur.


 Use of secure headers
TP-5455

The Team Server now uses X-Frame Options, X-Content-Type Options, and X-XSS Protection headers. These are headers that prevent cross-site scripting (data injections) from being used.


 Nginx version number hidden in HTTP header
TP-5456

All cloud-hosted BiZZdesign server products no longer advertise the version of nginx (web server) being used, to enhance security.


 Validations on e-mail server side
TP-5457

The Team Server now implements checks on the e-mail also server side to prevent malicious use of the Team Server API.


 Team Server password policy extended with username length
TP-5458

The Team Server now allows System Administrator users to set the minimum length of a username. The username length can be set on the General settings page of the Team Server.


The Settings menu is not available in a hosted Team Server (used with Enterprise Studio Online or locally installed Enterprise Studio).


For more information, see Configuring the Team Server password policy.


 No additional information on failed login to Team Server
TP-5459

To enhance security, the Team Server no longer provides information when users fail to log in, to warn them they are about to be blocked.


 Team Server password expiration configurable
TP-5460

Team Server users with the System Administrator role can now enable automatic password expiration for users. Users will be forced to change their password when they attempt to log in to the Team Server and their password has expired.

The password expiration settings are available on the General settings page of the Team Server.


The Settings menu is not available in a hosted Team Server (used with Enterprise Studio Online or locally installed Enterprise Studio).


For more information, see Configuring the Team Server password policy.


 Multi-factor authentication (MFA) for Team Server login
TP-5461, TP-5462, TP-5463

Users can now enable multi-factor authentication (MFA) for their own Team Server user account.

On the user's page in the Team Server, a button is available to add an MFA device and associate it with the user. Any TOTP-compliant (Time-based One-Time Password) MFA device/application can be used.

Multi-factor authentication is not applicable to users signing in using Azure Active Directory.



Once users have an MFA device associated with their Team Server user account, they can only sign in when they provide a valid MFA code. The Team Server sign-in window has been adapted for this.

An associated MFA device can be removed by the user self, or another user with the Administrator role. It can be done by clicking the new Remove button next to MFA device on the user page.For more information, see Setting up 2-step verification for signing in to the Team Server.

 Team Server user synchronization and authentication via Azure Active Directory
TP-5672, TP-5739, TP-5745

In addition to the possibility of user synchronization and authentication with Active Directory (via LDAP), the Team Server now also supports user synchronization and authentication with Azure Active Directory, which can be configured by users with the System Administrator role.

User synchronization and authentication with Azure Active Directory allows users to sign in to the Team Server and the HoriZZon web portal using their organizational account via single sign-on.



The Authentication settings page can be accessed via Settings > Authentication (previously Settings > Data Integration).


The Settings menu is not available in a hosted Team Server (used with Enterprise Studio Online or locally installed Enterprise Studio).

This feature is currently in a beta testing phase. You are welcome to try it out in your test environment, but be careful when using it in your production environment. If you are interested in the beta version of this feature, please contact the BiZZdesign service desk.


For more information, see Configuring user synchronization and authentication with Azure Active Directory.


 User authentication for adding storage places handled by Activity Console
TP-5759

Adding a storage place requires the user to authenticate. The authentication part is now being handled by the Activity Console. Depending on the way the Team Server that is referred to is configured, the Activity Console presents different ways to authenticate: by means of username and password, with Integrated Windows Authentication, or with Azure Active Directory. An example:



 New icons for Activity Console
TP-5830

The look and feel of the Activity Console has been updated to align better with the rest of the BiZZdesign product family. It means that the Activity Console icon and its statuses have changed. The former icon (visible in the system tray) has changed to . In the open Activity Console window, additional indicators have been added to messages:



For more information, see Possible statuses and messages from the Activity Console.

 Failed user sign-in attempts included in audit log
TP-5833

Failed sign-in attempts for users that do not exist are now logged in the Team Server audit log.

The audit log can be accessed via the Settings menu in the Team Server by System Administrator users.

The Settings menu is not available in a hosted Team Server (used with Enterprise Studio Online or locally installed Enterprise Studio).

 Possibility to resend user invitation e-mail
TP-5849

It is now possible for Team Server Administrator and System Administrator users to resend the invitation e-mail to users that have not registered yet to the Team Server. The Resend invitation button is available for this on the user page of the unregistered user.



For more information, see Resending a user invitation mail.

 Adding new users using comma-separated list for e-mail addresses
TP-5850

It is now also possible to add new users to the Team Server by entering their e-mail addresses in a comma-separated list, instead of entering the e-mail addresses in separate boxes.



For more information, see Manually adding users to the Team Server.

Bug fixes

General

The error message that appears when a migration cannot be started due to open changes, was confusing, and has been further clarified .

TP-5448

Enterprise Studio would show a crash report, when it was started a second time, while another instance of Enterprise Studio was already running.

TP-6027

ArchiMate

When changing the graphical shape of an ArchiMate Contract or Representation element, an additional horizontal line was shown.

TP-3274

The pie chart showing direct versus derived relations in the ArchiMate Model analysis function did not work any more, it always showed 100% direct relations.

TP-3655

When selecting a faulty ArchiMate exchange file on the ArchiMate import, no message appeared addressing this, leaving the user in the dark.

TP-4158

Moving a relationship end point to an object that is not creatable on a view crashed Enterprise Studio.

TP-5605

Changing a relationship's type crashed Enterprise Studio.

TP-5658

Auto layout commands could be performed on the Coach view, which could damage the layout of the view. It is no longer possible to perform auto layout on the Coach view.

TP-5940

Configuration

When a custom configuration contained any files of which the file name (including extension) was less than 7 characters long, these files would sometimes trigger warnings at startup about them not being UTF-8 encoded.

TP-5875

Data integration

In Excel, ServiceNow® and SQL imports, relations were created at the highest level specified by the model or create context of a connection or mapping. However, Enterprise Studio expected a relation to be in the same scheme as either its source or target element. This has been fixed. The context is now only used if it specifies the scheme where the source or target element are located.

TP-5370

Clicking the Import column headings control in an Excel table in a Connection model resulted in a script error.

TP-5521

The ArchiMate Exchange Format export function also exported some non-ArchiMate (Enterprise Studio-specific) concepts, resulting in import errors in third-party tools.

TP-5633

DMN

Selecting or entering an information item domain in a DMN glossary did not work for the German model language.

TP-5030

Graphic shapes on a DMN decision table view lost their text labels.

TP-5297

In a DMN glossary, changing the height of a row in the glossary did not work correctly: the rows below did not move.

TP-5297

In many cases, after adding a condition to a DMN decision table (or using a new information item in an expression in the table), the automatically created Information Requirement relation was added twice to the relevant views.

TP-5440

DMN expressions did not correctly handle currencies with their own currency symbol, with the exception of euro (€), US dollar ($), GB pound (£) and yen (¥). The currency symbols for Swiss franc (Sfr), Canadian dollar (Can$), Australian dollar (A$) and Indian rupee (Rs) are now also handled correctly.

TP-5467

Entering a numeric parameter value in a DMN boxed invocation resulted in an error message when trying to evaluate the corresponding decision.

TP-5478

When navigating the relations in a DMN Decision Requirements Diagram, the role names ("requires" and "is required by") were reversed.

TP-5814

Enterprise analytics

For the specification of filters for the population of a chart, exclusion of elements without a certain profile did not work.

TP-5609

Enterprise Studio Online

In some places in Enterprise Studio Online where access to the file system is needed, like creating HTML and InSite Lite reports, non-existing paths were shown, like the default locations for the reports.

TP-5170, TP-5603

ERSM

ERSM risk values did not propagate correctly when elements from multiple models in the same model package were combined.

TP-5300

The heatmap "asset value versus vulnerability" did not show strategy elements (Resource, Capability, Course of Action) with an "Asset" profile.

TP-5591

HoriZZon

When exploring the relations for an object in the Relations section of the object's properties panel, the text "Loading..." would stay shown for too long, even after the actual loading had finished.

TP-5360

Documentation texts with special diacritical characters such as ï were not displayed correctly in HoriZZon.

TP-5583

Loading sites and model packages when creating a site would take a lot of time to complete.

TP-5721

When a new unregistered user was added to a user group, and the user group was invited to a site in HoriZZon, the user was not able to access the site after registration.

TP-5806

The tree structure with model package components (site management) for setting the scope of a (large) site would become increasingly slower when the tree got expanded.

TP-5810

Modeling

On rare occasions, an Amber model package would refuse to open again, displaying an XML error.

TP-3826

When using the Generate view for function to create a view with a depth larger than 1 and using "graphical composition" for relationships, some related objects in this view still would not be graphically nested.

TP-4750

When an object (for example, of the ArchiMate plateau type) is referenced by many other objects, this would slow down Enterprise Studio.

TP-4862

The context menu of the Worksets window was missing several menu items, like Generate view for, Execute viewpoint, Locate, and Navigate.

TP-5010

Model packages could contain inconsistencies in one or more (no longer visible) relationships that would crash Enterprise Studio when the object these relationships started from was moved or cut and pasted.

TP-5524

In particular conditions, Enterprise Studio could deadlock during the loading of objects.

TP-5652

The items in the Profiles tab of the Properties window would overlap, when running Enterprise Studio in a scaled high resolution mode.

TP-5576

Doing multiple selections in the model browser was very slow, especially when using the Shift and/or Ctrl key.

TP-5974

Reporting and printing

Generated InSite Lite reports would display cross-model relation roles as "<unknown role>".

TP-3594

When creating an InSite Lite report of a model package containing an Amber Process call object that once called a later deleted process diagram, the report completed but raised script error messages.

TP-5484

In some places in Enterprise Studio where access to the file system is needed for shared model packages, like creating HTML and InSite Lite reports, non-existing paths were shown, like the default locations for the reports. The standard HTML report for example no longer proposes to create the report in the current directory, but instead defaults to the user's "My Documents" folder.

TP-5931

Scripting

In the scripting language, the session statement for "continue on external error" did not work when it was followed by a pipe statement.

TP-5801

Using big integer values in the scripting language was not supported well; values would either end up as 0 or a negative number.

TP-5869

Team Platform

Importing XML files directly to a shared model package caused an endless loop in Enterprise Studio. This has been fixed, and the performance of commands that create many objects in tracked and shared model packages has been significantly improved. An example of such a command is the import of large ArchiMate Exchange files.

TP-4461

Team Server 3.0.0 could not be installed if Internet Explorer was used; it was not possible to complete the setup page.

TP-5444

The Team Server did not support SSL-encrypted LDAP (LDAPS).

TP-5492

Previous versions of a model package, opened from the timeline, incorrectly offered the option to update. After doing so, the original model package remained in an out-of-date state and was vulnerable to damage in subsequent commits. Also, previous versions opened from the "recent" list would no longer be read-only, seemingly (although not actually) allowing edits.

TP-5497

Using certain special characters (&, <, >, ") in a commit message sometimes caused the model package timeline in the Backstage view to misbehave and show raw XAML.

TP-5523

In cases where a user was ever invited to multiple projects and/or the master model package, and removed one of the invitations (or suspended contribution), it would result in the deletion of an empty, but necessary file. This would lead to the message 'It is valid, but the model is still empty'.

TP-5735

The Forgot password page of the Team Server allowed the user to guess usernames/e-mail addresses by typing an address. The page no longer indicates if the e-mail provided actually belongs to a user or not.

TP-5800

Use of Integrated Windows Authentication for Single Sign-On could cause "414 Request-URI too Large" errors. The default maximum header size has been increased to 16 KB to support larger request headers used for Single Sign-On.

TP-5809

The Update and Apply buttons on the backstage tabs Update, Apply Contributions, and Update Project could become invisible when a large number of commits was shown on the page.

TP-5866

When making changes to a model package, while the Activity Console was synchronizing changes, the user would have to wait until synchronization was completed.

TP-6050

UML

In a UML model, a script error could occur when adding an attribute to a class, which also appears on a use case or package diagram.

TP-5812

Release notes 2017 and 2016

For more information, see Release notes archive 2017 and 2016


ArchiMate®  is a registered trademark of The Open Group.