Innovator 16.2 Release Notes

The Innovator release 16.2.1.30204 is packed full of new features and improvements; including ORDBMS and UDF for Information Architects.
Access options to Innovator models have also been further developed.
In addition, new functions have been introduced to enhance the platform.
Innovator contains an integrated AI so that you can search models using natural language.
The update also contains plenty of improvements to detail, enhancing the overall performance and usability of the system.

Administration Program: Drag-and-Drop for Managed Models View

Drag-and-Drop can be used when moving and assigning models in the administration program’s “Managed Models” view.

The agent works asynchronously; this means that the display has a delayed update of two seconds. This time can be customized using the INOAGENT_DROP_WAITTIME environment variable. Specification in seconds.

As well as moving model versions within the version model (its own subtree), the following is now also possible:

• Versions can also be moved into other models (other subtrees)
• Models can be assigned to another agent
• Models and versions can be moved to the new folders

The “Move” dialog is no longer available for model versions.

There are two new commands for assignment not possible with drag-and-drop:

• “Provide as New Model” for model versions (ribbon and context menu)
• “Move to Root Layer” for model folder and models (context menu)

Structural changes to model versions require the version right. Environment right is required for version models.

Administration Program: Grouping Managed Models into Folders

Managed models can be grouped into folders. There are two types of folders:

• Model folders are always above the model level and can be used for grouping version models.
• Version folders are always in a model and can be used for grouping model versions and back-up within the model.

Assign and arrange nested folders using drag-and-drop.

You require the environment right for all operations to model folders. Version folders require the version right for the surrounding version model.

Administration Program: Moving a Managed Model to Another Agent

The “Switch Agent” command in the administration program’s context menu can be used to move a managed model and all its versions to another agent.

Drag-and-drop can also be used to move the model. For more information about this, see; “Administration Program: Drag-and-Drop Managed Models Tree”.

Administration Program: Options Dialog Available in Application Menu

The Options dialog can also be accessed directly via the administration program’s Application menu.

ArchiMate: Derived Relationships

Derived relationships are supported in ArchiMate diagrams. The carousel has an icon for creating derived relationships. The created relationship is automatically marked as derived.

“Direct” and “Derived” are used for differentiating grouped headers in the dialog when using the magic wand.

There are three options in the display options so that derived relationships can be easily recognized as such:

• The “is derived” property can be shown as an icon property
• Use “Color Of The Derived Concept Connection” to define a font color element which stores the methodical color under the “Normal” entry
• The line thickness of the derived relationship can be changed using “Line Thickness Of The Derived Concept Connection”

These display options are supported in concept diagrams and in the whiteboard.

The derived relationship is based on one or more paths. Evaluation is limited to a path length of 11 so as not to affect performance. The path consists of 1 start element, 4 intermediate elements, 1 target element and 5 concept connections between these elements.

The path is automatically calculated when the server is backed-up. It is also possible to manually start this using the “Maintain Derivation” command in the context menu. The “Missing Derivation” smart icon can be shown for derived relationships in the diagram.

The paths to derived relationships can be shown in the Details area. The relationships derived from the path components (selected relationship or concept) can be shown in the Details area.

The model template has a new profile “ArchiMate 3 Relationship Derivation”; it contains the rules, constraints and strengths required for calculating derived relationships in accordance with the specification.  “/” is also shown as an icon for derived relationships. Various “Derived <color>” color elements are available.

There are various new verify options for derived relationships. These are also taken into consideration in the general verify routines.

ArchiMate Export and Import support derived relationships. An “IsDerived” property is also created upon export. If a file exported using Innovator is reimported into Innovator, then derived relationships are recognized by this property. Paths are already created upon import; this means they are visible if an imported diagram is opened.

ArchiMate: Nested Relationships for Concept Connections

Nested nodes in ArchiMate diagrams can express a relationship. Use the diagram content configuration to determine which relationship should be represented by a nesting. If two nodes are in the same container and there is a concept connection between them, then a relationship from the container to the concept connection can express the nesting. If more than one relationship is possible, these are displayed in a dialog and you can select the one you wish to create or add. If a concept connection is dragged between two concepts within the container, then nesting can also be selected. The relationship edge is automatically hidden when the nodes involved are moved into the linked container. The relationship edge reappears when one or both of the nodes are dragged out of the container.

ArchiMate: Stereotype can be Selected when Importing Packages

Select “Create Packages from Organization” for ArchiMate import to select a stereotype for packages.

Bpanda Connector: Stored SVG Files Used

If the “Apply the Innovator look” option is activated when exporting processes, then SVG files are created and transferred to Bpanda. If the “Provide SVG in the model” property is set in the model, then the SVG files stored there are used.

Stored SVG files are also used when exporting process maps.

BPMN Import: Option for Scaling Task Nodes

The new “Scale Task Nodes” option is now available when importing BPMN diagrams. This is a Boolean setting which is deactivated by default.

If the option is activated, then the import adjusts the size of the task node to the scaling factor used.

BPMN: Task Displays Decisions Used

Decisions can be assigned to tasks using the “Used Decisions” property. This property is also available as text property in the display options’ configuration.

Concept Diagram: Customizable Display of Owners of Concepts

It is possible to control how owners of concepts/junctions are displayed in concept diagrams using two display options:

• The “Owner Display Kind” options allows you to set whether nothing, only the user or a namespace should be displayed.
• The “Display Differing Owners Only” option suppresses the owner display if the container matches the logical owner.

Concept Diagram: New “Group” Layout and Extended Container Support in Static and Dynamic Concept Diagrams

There is a new “Group” layout in static and dynamic concept diagrams. As with the layer display, this display is suitable for displaying interactions between various abstract layers of the model and uses the same configured layers. The nodes from the same layer are arranged close together. Nodes at the same height have the same layer.

Dynamic concept diagrams support arranging of containers in both the new “Group” layout and in the “Layer” layout.

Container assignment to a layer is ignored to enable a clear and structure-focused display.

Configuration Editor: Type Systems can be Localized

If the “is Model Default” property is activated for a type system, then localization is possible. Localization is possible for the type system, data types in the type system, type classes and default values.

Dashboards: Dashboards Integrated

Dashboards are fully-integrated within Innovator. Dashboards and data definitions are model elements which can be stored anywhere in the model. Stereotype properties, labels and text definitions can be used and access and read rights can be assigned.

There is now an improved view for dashboards in the Model Content; this contains both depictions you already know from the Diagram view.

Dashboards are document windows with their own ribbon.

Data definitions define how a widget is structured. Data definitions also have a document window for easily creating definitions. IntelliSense is used for the search terms.

If you used the Dashboard plug-in in Version 16.1, then transforming models converts existing application configurations into the new elements. These can be found in a new system model.

DataBridge

DataBridge is a synchronization service which enables bi-directional data integration between Innovator and external tools. It acts as a central interface for automating synchronization of model content in various target systems, such as Neo4J (graph database), PostgreSQL (relational database), OpenSearch (for dashboards) and Collibra (Data Governance).

DataBridge transforms complex Innovator metamodels (business objects, applications, processes etc.) into target-specific data structures and keeps them consistently synchronized. Flexible mapping allows stereotypes, properties, relationships and labels/texts to be seamlessly transferred to the respective target format. Integrated conflict management, detailed logging and status tracking all ensure a reliable and traceable data exchange.

DataBridge runs as a standalone Windows service or Linux Daemon and supports both time-controlled and event-based synchronization.

The DataBridge plug-in enables administrators to centrally configure and control all synchronization processes directly on the Innovator interface. Simply use the ribbon button to start synchronizations for single or all linked target systems. You can monitor the current status and manage extensive mapping configuration in the plug-in’s configuration interface. The configuration can be edited directly in the application configuration.

Diagrams: Callouts support Concept Connections and Resources

Callouts can be used in all diagram types to display target or source elements from dependency relationships. Concept connections are now also supported in concept diagrams.

Concepts can also be used as a resource of an activity in the BPMN diagram and displayed as a resource node. You can show the reversed direction in the callout using the “Referencing Resource Role” and “Container for Resource Roles” in the concept diagram.

Showing what the resource is being used for is possible in all diagram types where resources can be displayed as nodes.

Diagrams: Modifying Element Type for Dependencies and Concept Connections

The element type of dependencies and concept connections in diagrams can be modified. The available create templates are made up of the menu items configured in the diagram. Menu items cannot be configured for dependencies and concept connections in the model structure. Available create templates are determined using the execution rights of the current role.

Documentation/Detail Trees: Transitive Owners in Details

The “Owner (transitive)” and “Contained Elements (transitive)” chapters are available in the documentation structure, meaning they are also available in the detail configurations.

Show the elements relevant to the context by constraining to one stereotype.

Entity Relationship Diagram: Display Read Direction of Entity Relationships

A “Display Order of Reading” display option is available for displaying the read direction for relationship edges of entity relationships. If this is set and the edge has a display text in the diagram, then the read direction is shown with a black triangle, as is the case in the class diagram. The read direction can be reversed in the relationship’s properties.

Excel Import: Importing Create Defaults

A create default exported as an Excel file can be imported using Excel Import to create a new create default or modify an existing one.

General: Navigating Between Last Selected Elements in Model Editor

Two new commands have been added to the quick access toolbar: “Navigate Backward” and “Navigate Forward”. Use these to jump between the last selected elements in the model.

Simple selections in the model structure, model element lists, diagrams and tables for classifiers, detail area and results region are recognized. If a previously selected element is jumped to again using one of the commands, then the respective editor is automatically opened and the element focused on.

The “Navigate Backward” command also has a list which shows all selections made. Simply click on the entry in the list to jump to it directly.

General: Relationship Properties Available as Text Property in Display Options

It is possible to configure the extended use as a property on the source/target side and activate the display on the source/target side for dependencies and similar relationships. These relationship features can be selected as a value for the text property in the display options for the affected source and target elements.

Impact Analysis: Edge Direction can be Set

Set whether an edge in Impact Analysis should be displayed in the same direction as the graph, in the opposite direction or independently from the graph direction. This setting can be made in the “Set conditions for display configuration” dialog.

Impact Analysis: Extended Configuration Options

The “Content” and “Display” tool windows in Impact Analysis now have an extra tab called “Paths” for defining complex conditions for various elements. Paths can be directly selected in the diagram and configured individually based on evaluation, display and coloring. It is also possible to merge nodes or edges.

Impact Analysis: Graphic Grouping Possible

Nodes can be grouped according to criteria in Impact Analysis. Nodes which belong together are grouped into invisible rectangles (groups) which do not overlap.

If the “Smooth graph” option is activated, then groups appear as layers and nodes are evenly arranged. These layers start in the graph with the initial node layer.

Possible grouping criteria include:

• Package directly above
• Model directly above
• System model directly above
• Stereotype

Model Content: Create New Application Configurations

You can create new application configurations in the model content’s “Administrative Content” view.

Powershell: Innovator PowerShell Library can be Used with Linux

The Linux installation has an Innovator PowerShell library which can run on the Linux environment.

The script library for Linux systems has a reduced range of functions with no Windows-specific commands.

PowerShell Version 7.6 or higher is required.

Properties: Extending Stereotypes Available

The new “Extension” element type can be used to define any number of stereotypes with stereotype properties, type system options, labels and texts.

The “Extending Stereotype” relationship role enables these stereotypes to be used by any number of element types so that the additional properties are available. The “Extending Stereotypes” property is also available for the element. The respective properties are then added for the selected stereotypes. The affected entries are marked as extensions in the info display (Shift + F1).

Properties: Parameter Values Available as Property

Message parameter values in interactions can be accessed as properties in the Properties editor. The parameters are displayed in rows in the editor with direction, name, type and modifiable value. Only the values are listed in the Properties editor, separated by commas; these can also be edited in this syntax. The “Edit Parameter” command is no longer available. The parameter values are also shown as properties in the table editor and can be modified directly or in the editor.

Tables: Slot Values Displayed

Content tables now have an extra column for displaying slot values. This column is read only. Slot values can be modified in the Properties area.

Administration Program: Improved Performance as Models with no Version Rule no Longer need to be Identified

Version rules no longer have an influence on starting and stopping model version; this means that tree nodes no longer need to be shown in italics. The tree can therefore be displayed more quickly in the administration program.

Information is still displayed when a model or a version with no version rule is selected.

Administration Program: Preventing User Logins

The model administrator can permit or prevent user and guest logins at the model level for standalone and managed models.

It is only possible to fully lock the repository level for standalone repositories.

The Innovator Powershell library also has this function for models.

Align Models: Improved Comparison of Directed Relationships

The evaluation logic for directed relationships has been improved for model comparison. Directed relationships can exist with or without a name:

• With name: If the owner is a namespace, then the relationship must have a unique name (e.g. for dependencies or concept connections).
• Without name or namespace: A unique name is formed by combining owner and target (e.g. for generalizations or import relationships).

Assigning primarily occurs for comparison using the UUID. If UUIDs differ, then a check is carried out to see whether owner, target and, if applicable, name (only for namespaces as owner) are the same.

Align Models: Model Configuration can be Temporarily Ignored

Use the “Ignore Configuration” command in the ribbon to temporarily ignore the model configuration when merging. This makes it possible to create model states which differ from the model configuration requirements.

The option is automatically reset once merge has been completed. Verify routines can be set as a final check to identify possible deviations from the model configuration.

Please note: This function should only be used by experienced users.

Align Models: Selection via Application Configuration Packages Extended

Application configurations are always created for a specific purpose. An application configuration package exists for each purpose; this package bundles all application configurations with the same purpose together.

You can select which models should be compared via the application configuration packages instead of individual application configurations. The comparison then automatically considers all application configurations with the same purpose.

ArchiMate: Relationships between Risk Elements and Business Resources are Dependencies

The “Change Element Type” command is also available for concept realizations. They can be changed to dependencies or their specializations as long as these are permitted between the elements involved.

For more information about this, see; “Diagrams: Modifying Element Type for Dependencies and Concept Connections”.

If profiles provided by MID within the scope of delivery are used, then elements of the risk extension are linked with business resources or actors via concept realizations of the “recognizes” and “is responsible” stereotypes.

Once the migration files have been installed, then these concept realizations become dependencies.

Read how to customize your model in the Migration Manual.

BPMN Diagram: Modified Drop Behaviors of Classifiers and Concepts

When a classifier or concept is dropped in a BPMN diagram, a check is now carried out first to see whether these can be used as a data object of a business object. If this is possible, then the respective data object is created (this is also possible within a lane).

If no data object can be created, then evaluation is carried out as a resource of an activity, lane or process.

This resolves a previous limitation where, despite correct configuration, no data object could be created within a lane.

BPMN: Concepts can be Used as Data Structure

Classifiers and concepts can be used as data structure for business objects. Both information objects in process maps and the business object, data object and artifact from ArchiMate are permissible in model templates. Install the migration profiles to use this feature.

Change Sets: How Active Change Sets are Treated upon Inactive or Missing Login

If the change log is activated, then participation is automatically created for a new or existing change set when user login occurs.

The change set is then shown as active with an empty timestamp in the “Finished at” column. The timestamp in the participation is entered as “Finished at” when the user logs-out (even if this is done indirectly by the model administrator). If all participations to a change set are terminated, then the latest timestamp is shown in the “Finished at” column.

If inactive users are automatically logged-out or the model server is closed, then the login is indirectly deleted; this does not remove the participation to a change set. The affected change set is still shown as active even though no user is active within it. The affected participations are also removed when the model server is closed. If change sets are merged, participations with no active login are also removed.

Concept Diagram: Improvements made to Copy-and-Paste

When copying nodes in the concept diagram, pasting adds both nodes and edges between these nodes. Only edges which existed in the output diagram are taken into consideration for this.

The access rights for the active role are automatically added to for the copied nodes.

Confluence Integration: Displaying Diagram Properties

Diagram properties can be displayed in Confluence.

Creating a Relationship using the Carousel enables Selection of Existing Relationships

If there are already one or more relationships between the elements when using the carousel or magic wand in the concept diagram, then a dialog appears where you have the option to add these relationships or create new ones.

Data Modeling: “USING INDEX” Oracle Type System Option Type Changed

The “USING INDEX” Oracle type system option has been changed from ‘Boolean term’ to ‘String’ when entering an index name. This change cannot be executed for profile migration. The option therefore needs to be deleted from the configuration beforehand.

Data Modeling: Conceptual Type System Localized in Default Profiles

The type system used in the entity relationship model is now localized (‘English’ and ‘Deutsch’). The names of the type system and data types are localized in the default profiles for German and English; these are then shown in the interface depending on which display language is set.

When using within an API application, please ensure that the previous “Deutsch Type System” profile name has been changed to “Conceptual Type System”. The type system’s logical name has also been changed accordingly. These localizations are taken into consideration upon profile migration.

Data Modeling: Uniform Namespace for Entity Attributes

Entity attributes and attributes within an entity relationship view both make up a namespace. The transformer gives elements contained (e.g. dependencies) a unique name.

Data Modeling: User Defined Function Parameter

The parameters for a user-defined function are modeled as content elements of a view. It is possible to configure entity attributes as content elements in a view of an entity relationship model or table columns in a database view.

These are provided by IntelliSense and can be found at the top of the suggestion list.

Data Modeling: User Defined Functions Supported for SAP HANA

User Defined Functions (UDF) for SAP HANA can now be modeled. In the entity relationship model, these are views which can contain parameters in the form of attributes. In the SAP HANA model, these UDFs correspond to views where table columns can be used as parameters.

The “Parameter Values” property is available in FROM clauses which reference these UDFs. The values can be added as a list separated by commas.

Diagram: Improved Readability of Floating Labels

The font color is automatically adjusted for floating labels (e.g. edge labels) if these texts become illegible due to the underlying container having an unfavorable color. The adjusted color is not stored; it is only displayed in this way to make it legible.

If the text is moved to another background, clicking on refresh (F5) changes the color back to its original color or the text color is changed again to suit the new background. The color is not changed if the text is above a normal node, frame or header.

Diagrams: Mapping Dependencies Permitted in Further Diagram Types

The requirements, entity relationship and database diagrams permit mapping dependencies as menu items.

Diagrams: New Color Behavior

The color behavior has been revised at various points within diagrams to make labels more legible:

• Compartments in compartment nodes (e.g. classes) are no longer shown in color.
• Only the frame is now shown in color for user input tasks.
• Table headers are only shown in color for color labels or individual colors; no longer for methodical colors.
• Only the header is now shown in color for views.
• Separator lines now adopt the frame color.
• Stereotypable relationship edges are colored in the methodical color if no individual colors were assigned to relationship edges for individual color representation.
• Owner relationships and edges from association classes are given the frame color of the respective node.

Diagrams: Relationship Wizard Supports Creation of Incoming Connections

Nodes which only permit incoming connections exist in certain modeling methods. The relationship wizard can be used on these final nodes to create connections starting from a suitable source element in the opposite direction.

If more than one connection type is possible, then the respective selection dialog is shown.

Activate the relationship wizard in Options if you wish to use it.

Diagrams: Tool Tips for Smart Icons Revised

The smart icon tool tips are now even more descriptive.

Markers for realizations and synchronized elements at the node now also have tool tips in the concept diagram.

General: Deletion Dialog shows Number of Affected References

The deletion dialog shows the number of diagram occurrences and typed elements in the table of elements to delete which would also be deleted or modified if the deletion is carried out.

General: Dependency Editor Supports Concept Connections and Other Directed Relationships

Concept connections and other directed relationships are now also supported alongside dependencies for dependent and required elements in the dependency editor. The supported relationship types depend on the element types selected and respective configuration.

General: Limit when Copying Large Volumes of Data

Copying large volumes of data requires the “Use Bulk Commands” privilege in the target model. This privilege is not required in the source model. If the copy volume exceeds 1,000 instances, then an error message appears indicating the missing privilege.

General: Modifying Element Types Optimized and Extended

General: Modifying Element Types Optimized and Extended

The “Refactor>Change Element Type” command has been extended and optimized in many areas:

• UUID retained: An element’s UUID remains unchanged when an element is converted. This means that e.g. existing hyperlinks linking to this UUID are still valid after the element type has been changed. The element can also still be found in the bookmarks.
• Default adoption of properties: All properties of the original element (including the owner) are adopted upon conversion.
• Optional evaluation of create defaults: Create default evaluation can be activated in the second tab in the dialog. If activated, then a suitable default is searched for and the new element is also stored in the owner defined there, if one is given. This setting also determines what information is displayed about modified or affected elements.
• Adding to the results region: Automatically adding new elements to the results region can also be activated in the second tab. This option replaces jumping the element to its new storage location. Content and selection made in the results region remain.
• Support for bookmarks: It is also possible to convert elements by directly selecting them in the bookmark view. The converted elements are still retained as bookmarks.

Java 25

The minimum requirement for Java is changing from version 21 to version 25.
Its own OpenJDK runtime environment (version 25) is included and installed within the scope of delivery of Innovator for Windows.
You do not need to install any further Java runtime environments on the server or client to run Innovator for Windows.

Model Content: Views in Model Content

The order of the navigation tabs in the Model Content is shown in a more intuitive order.

Model Login: Improved Open & Login for Large Numbers of Models

A very large numbers of models in the “Model Servers in the Network” view in the “Open & Login” backstage page may result in some model servers not being able to be accessed in the first few seconds after program start.

This meant that the “Open” button was deactivated if access to the respective model server was not immediately possible after startup. The “Server not reachable” message then used to be displayed in the info field.

The “Open” button is now also activated even if the model server cannot be reached at that point in time.

Tables: Multiplicity Added to Display

Parameters for operations are displayed in a column in tables. The name, type and now also multiplicity are displayed. The same applies for properties which are displayed in the access function column.

User Management: Rights Inherited from Groups are Shown for Users

The “Manage Users” and “Manage Environment” rights are shown for the user in the “Assigned to Groups” table in the Administration program’s user management.

Administration Program: Change Log Transferred

The change log and notifications are also transferred if the “Place Under Version Management” command is executed, as long as this is set in the model.

If a managed model is converted using “Convert to Model File”, then an active change log is retained and converted along with it.

Administration Program: INOHOST for Project License Servers in NAT Scenario

The configured INOHOST setting is retained when changing project license server properties in the administration program; it is not replaced by the NAT value. This ensures that the functionality of the project license server is not compromised, even in NAT scenarios.

Agent: New Storage Structure for Agent Database and Log Files

The storage location of the agent’s database and log files has been changed.

It is possible to set the directory for log files using the “-Dde.mid.innovator.inoagent.logdir” Java option.

The log files were previously stored in the “$INOPRJ/ivm/logs/inoagent-Host.Port” directory. This directory also used to contain the InoAgent’s database.

The new structure now stores log files in “$INOPRJ/ivm/agent/Host.Port/logs”. The respective database can now be found in the parent directory: “$INOPRJ/ivm/agent/Host.Port/agent.sqlite”.

Use the “-Dde.mid.innovator.inoagent.dbpath” Java option to choose another directory where the database should be stored. The path must end with the “agent.sqlite” file name.

ArchiMate Import: Improved Performance

The file selection dialog now opens much more quickly when import is started.

Beamer: Creation Dialog Recognizes Execution Rights

The dialog for creating relationships using drop only shows create templates which the current role has execution rights for.

All create templates can be shown using the “Rights from All Roles” setting.

BPMN Import: Create Event Definition

If a definition already exists for an event, then another definition is not created if the “Create Event Definition” option is set.

Business Intelligence: Consistent Display of Cube Dimension Edges

The cube dimension edge is no longer displayed as dashed; not even if it is rectangular.

Diagrams: Diagram Opened for Read-Only Also Refreshed

A diagram opened for read-only is now also refreshed if brought to the foreground.

DMN: Deleting Rules in Decision Tables Fixed

The respective value is also deleted when rules are deleted from decision tables if these are no longer used by other rules.

Values which are used more than once are still only created once and collectively used.

Documentation: Impact Analyses Supported with Reduced Rights

Documentation generation can create impact analyses even if the user does not have write rights in the program directory.