Klicken Sie auf den unteren Button, um den Inhalt von Hubspot zu laden.

Inhalt laden

Newsletter Subscription
Abonniere unseren kostenlosen MID Newsletter!
Wir informieren Dich gerne regelmäßig über alle Neuigkeiten der MID.

Subscribe to our MID newsletter for free!
We will be happy to inform you regularly about all the latest news on MID.

Klicken Sie auf den unteren Button, um den Inhalt von Hubspot zu laden.

Inhalt laden

Innovator 16.0 Release Notes

June 19, 2023

UPGRADE NOW

You can find all detailed information about the June 19, 2023 Innovator 16.0 release and all Innovator 16.0 hotfixes here.

Version Number Product Description Date
Version 16.0.1.30130 Innovator 16.0.1 Hotfix January 31, 2024
Version 16.0.1.21011 Innovator 16.0.1 Hotfix October 12, 2023
Version 16.0.1.20718 Innovator 16.0.1 Hotfix July 20, 2023
Version 16.0.1.20614 Innovator 16.0 Release June 19, 2023

Notes on Version Consistency:

Please note that we highly recommend having the same versions for both model server and clients when updating your Innovator installations to ensure reliable operation of Innovator. It is mandatory that both the model server and clients have the same release number (XX.X.X). The 16.0.1.30130 hotfix is compatible with the 16.0.1.2XXXX previous versions. The 16.0.1.30130 hotfix is not compatible with the 16.0.1.11130 Innovator release. The server and client components for this release must be used in the same version. The 16.0.1.30130 hotfix has limited compatibility with older versions (16.0.1.20507). It is possible to use the server components in this release with older client components in the 16.0.1 version. However, clients in the 16.0.1.30130 version require servers in the same version. Repositories which have been updated through transformation or start with the current server can no longer be used in older program versions. 

Notes on API Documentation:

The API changes are continuously documented in the online help.

Innovator 16.0.130130

The hotfix 16.0.1.30130 fixes the CVE-2024-0056 (NVD) security vulnerability and fixes model server crashes when merging.

New Features

Administration: New Filter for Active Model Versions

The Administration program now has the new “Active Model Versions” display filter for managed models. Deselecting this filter can reduce the node sets if e.g. searching for models marked for deletion. 

Advanced Search for Versionable Elements

A sub select’s result set for contained elements can be narrowed to versionable elements. 

Examples: 

SELECT FROM #Package# COLLECT “Contained Elements (Transitive)” : #Versionable Element# 

or 

SELECT FROM ELEMENTS WHERE ( SELECT FROM “Contained Elements (Transitive)” :#Versionable Element#)  

ArchiMate® Import: Unformatted Texts

When importing files in ArchiMate® format, unformatted texts are also recognized for elements of the “property” type if these are configured in the model. 

Automatic Translation in Specification Editor

The new “Translation>Translate Automatically” command in the “Text” ribbon enables automatic translation of the text from the model into the display language selected, using web services. The function has the same effect as the command of the same name in the the tool window for translations. 
*  The text structure (e.g. paragraphs, lists, tables) remains unchanged upon translation.
*  Images will be retained.
*  The text is translated paragraph by paragraph. Character formatting at the start of the paragraph is adopted for the whole paragraph. Character formatting which deviates from this formatting within the paragraph is not adopted.It is possible to add this formatting manually after translation has been carried out using the “Font>Format Painter” command.
*  Hyperlinks to elements of the same model will be retained. The hyperlink is given a placeholder as text immediately upon translation. Once saved, the translation of the element name in the display language is used instead.
*  The following applies for all other types of hyperlink: If the entire paragraph is one single hyperlink, then this remains upon translation. Otherwise, this is not the case; not even at the start of the paragraph.

Bpanda Connector: Composite Properties from Various Model Elements

In the application configuration in Bpanda Connector, the name or description for a risk or control measure in Bpanda can be made up of properties from various model elements in Innovator. To do this, enter the “concatenates” element in the application configuration and the “relationship” element below the appropriate property to specify the model element relative to the risk’s model element.  

Bpanda Connector: Header for Properties

A header can be entered for each property in the application configuration in the Bpanda Connector. If the property’s value is empty, then the header is not displayed. The header can be added in the “header” attribute. A multi-language header can be added in the “nlsHeaders” list. To do this, use one element per language with the “language” and “value” attributes below “nlsHeaders”. The values for “language” correspond to the two letter language abbreviations from ISO 639-1. 

Bpanda Connector: Properties-Based Filtering

A model element can be filtered based on its properties in the application configuration in the Bpanda Connector. The “filterType” element along with the “attribute”, “stereotypeProperty” or “text” attributes and a “value” attribute is required in the application configuration. If the value of the respective property, stereotype property or text for a model element does not correspond to the given value, then this is ignored. It is also possible to enter these attributes below the entries in the “types” list.

Bpanda Connector: Translatable Constants

Constants which depend on the display language can be entered in the application configuration in Bpanda Connector. To do this, use the “nlsConstants” in the application configuration instead of the “constant” attribute and enter one element per language below it with the “language” and “value” attributes. The values for “language” correspond to the two letter language abbreviations from ISO 639-1.  

Excel Export Supports Properties for Dependencies

If you have configured properties for dependencies in such a way that the source elements or target elements are shown in the Properties area, then these properties are also exported when exporting to an Excel file. The same applies when exporting in JSON, XML and CSV formats. The properties for dependencies are not automatically recognized when importing an Excel file. The column needs to be manually assigned the relationship or incoming relationship.

Full Screen Mode

Use the “View>Document Views>Full Screen” (F11) command to only show document windows and to hide tool windows. The ribbon is minimized. Repeating the command restores the previous state. 

Translations also Adopted with Names

The name is automatically adapted for some elements if a referenced element is exchanged. If the referencing element already has a modified name, then the name can be reset to the default value. All translations of the referenced element are adopted for the referencing element.  

User Defined Functions from SAP HANA

A user defined function referenced by a From clause is modeled as a view of the “User Defined Function” stereotype. Its columns form the Return table and its expressions form the Return select. The function’s parameters are modeled in a table of the “Function Parameter Table” stereotype; this is linked with the function via a sub-select clause of the “Used Parameter” stereotype. A function such as this is used via a From clause of the “From Function Clause” stereotype. The concrete values of the parameter are added to its property separated by commas, just as they are added within the function brackets. This function is also possible within the Entity Relationship model.  

Feature Updates

``Change Element Type`` Narrows Relationship Templates

The “Design>Model Elements>Refactor>Change Element Type” command displays the available create templates in a dialog. This list is narrowed via the configuration for specializations of dependencies and concept connections. A create template is only permissible if it changes the element type or stereotype and if both the source and target element can be linked. 

ArchiMate® Import: Large Empty Labels Become Frames

ArchiMate® Import maps elements of the Label xsi type to comments by default. However, if the height of the node is at least twice as high as the text, then a frame is created instead. This improves the layout in many cases.

Changing Document Names

If a document window represents an element, e.g. diagrams or specification texts, then you can double-click on the tab or press F2 to open a dialog for renaming the element.

Collapsed Participants also Enlarged when Increasing Size

Moving using Shift+Ctrl+right mouse button also modifies the size of collapsed participants.

DB Import: Import Primary Key via SQLStatement

If a database does not return a primary key via Standard-JDBC, then the primary key query can be carried out using an SQL Statement.

DB/ER Diagrams: Edit Declaration (Ctrl+F2) Omitted

The “Edit Declaration (Ctrl+F2)” context menu command is omitted in DB and ER diagrams for attributes and columns; this is because IntelliSense cannot be provided for data types from the configuration.  

Diagram Occurrences in Tables Extended

Whiteboard diagrams are now listed as diagram occurrences in the “Contents as Table” and “Process Table” table views. 

Diagram: Aligning Multi-Line Frame Titles

Multi-line frame titles are aligned according to the frame title setting (Left Justified, Centered, Right Justified).

Diagrams: Optimizing Size and Header Size in the Context Menu

You can also access the “Optimize Size” and “Optimize Header Size” menu commands via the context menu in diagrams.  

ER-DB Mapping Does Not Map Irrelevant Packages

Standard mapping of the conceptual model to the database schema only maps packages if the package is selected or if the package contains an entity, a view or a diagram. 

Expand Participants to Show Content Revised

The function for expanding participants to show content has been reworked so that the diagram layout is not affected. 

Impact Analysis Differentiates between Owner and Source

In impact analysis, the “Owner” relationship property is referred to as the source for a directed relationship. A dependency, concept connection or generalization are all examples of a directed relationship. The “Source” relationship property is followed as an edge in both directions by default. This means that a directed relationship’s source is shown in an existing impact analysis, even if another user-defined behavior has been specified for the “Owner” relationship property.  

Lane Creation Revised

The function for creating lanes has been reworked so that the diagram layout is not affected.

Moving with Right Mouse Button Revised

The function for moving using the right mouse button has been reworked so that the diagram layout is not affected.

Own Icons Automatically Updated when Administration Program is Started

Your own icons in a central icon directory are also automatically updated when the administration program is started. 

This occurs when the following environment variables are set:  

 *  ICON_PATH   

 *  ICON_DEPLOYMENT_PATH  

Performance Improvement with Icon Comparison for Network Path Cache

Runtime has been considerably improved when comparing icons to see whether they have been modified.  

This effect occurs when the following environment variables are set: 

 *  ICON_PATH   

 *  ICON_DEPLOYMENT_PATH  

Time-Out when Creating a Model Version

A model server is started in the background when using a wizard to create a new model version. The new model version should be created in this model server. If there is a poor network connection, then the command for starting the model server may terminate with a time-out. If an error occurs, then the wizard closes and deletes this model server. The time-out means that the wizard does not have the information required to delete the model server. The model server will therefore continue to exist after the command is terminated. The time-out for this command has now been increased from 2 seconds to 30 seconds to avoid this issue arising.

Bug Fixes

Security Vulnerability CVE-2024-0056 (NVD) Fixed

The security vulnerability CVE-2024-0056 has been fixed by using System.Data.SqlClient 4.8.6.

Align Models: Right Singles when Comparing within a Model

When comparing elements from the same model, elements which only exist in the right-hand branches are also shown.  

Bpanda Connector: Rights from All Roles Taken into Consideration

The “Bpanda Connector>Import>Import from Bpanda” command produces an error message in the following circumstances: 
*  The user is not model administrator.
*  The user’s role is not defined as permissible in the application configuration.
*  If the “Rights from All Roles” toggle command is set, then none of the user’s roles are defined as permissible in the application configuration. 

Bpanda Connector: Translation of Concatenated Values

In the application configuration in Bpanda Connector, the name or description for a risk or control measure in Bpanda can be created by combining various properties from Innovator. Simply enter the “concatenates” element in the application configuration. The properties’ values are then also transferred to all display languages in Bpanda in addition to the model language. This also applies to boolean terms and enumeration values. 

BPMN Diagram: Display Between Events and Event Definitions Fixed

Display options can be used in the BPMN diagram to control whether an event’s own name and/or an assigned event definition’s name should be displayed. If you wish to display the event’s own name but the name is empty, then the display shows an empty row. This row can then be used for e.g. renaming using F2. 

Checking Rights when Creating a Managed Model

You only require a model administrator rule for managed models when creating a managed model. You do not require further rules.

Container Assignment in Diagram Saves Modified Coordinates

If a container assignment is modified in the diagram, then the previously-modified coordinates are saved.

Defective Text Alignment Fixed

Text alignment now works perfectly. All rows are aligned on the selected side.

Diagrams: Break in Text Nodes with Special Characters

If a text node contains a special character (e.g. ‘&’) followed by an empty space and if a break occurs before the special character, then the empty space is displayed correctly.

Dimension Maintenance: Type Class for Floating-Point Numbers

The “Deutsch” type system has the new “Float” type class for Dezimalzahl, Dezimalzahl($1,$2), Geld, Geld($1,$2) and Reelle Zahl ($1 Byte). It is possible to enter decimal numbers with decimal places for these types of columns in the table for dimension maintenance in Business Intelligence models. 

Docu Wizard: Replacing Placeholders in Names in the Output File

If placeholders are used in output file names in the configuration editor, then the wizard removes characters which are not permissible in these paths and replaces these with an underscore in the name suggestion on the “Finish” page. 

Drag & Drop Possible within a Grouping

If elements can be dragged from the gallery in the ribbon and dropped in a diagram, then it is also possible to create these elements within a grouping. It is also possible to type elements within a grouping using drag&drop. 

Excel Import Ignores Incorrect UUID Values

UUIDs which no model element was found for but an element was found for due to its name column value are ignored when importing an Excel file. Both cells are marked with an error if no element is found.  

Excel Import sets Access Rights as in Create Templates

If access rights are not entered for a model element or if the column is ignored when importing an Excel file to the file, then the access rights from the create template are used.

Excel Import: Refresh Preview

Changes to the “Maximum number of displayed rows per sheet” input field in the “Check Data for Excel Import” dialog affect the content shown. You do not need to reload the file.

Exporting Formatted Texts to Bpanda

No superfluous blank lines appear in lists when exporting formatted texts from Innovator to Bpanda.

Impact Analysis Context Menu has Default References

The “Go to” command in the impact analysis context menu contains default references, as is the case with all other windows.

Impact Analysis Displays Concept Connection as Node

A concept connection modeled between a concept and a concept connection is displayed as a node in the impact analysis. This makes it possible for impact analysis to display three concepts linked with each other and two concept connections. This is the case if one of the two concepts connected using a concept connection is selected as start element. Display is also possible if another concept is used as start element. This concept needs to display a concept connection which shows the concept connection between both original concepts. In this case, the three concepts and two concept connections are also displayed by the impact analysis.

Impact Analysis uses Selected Content Configuration

Impact analysis uses the selected content configuration and display configuration, even if the diagram was only opened in read-only mode. 

Mapping Ignores Multiple Entities

FROM clauses from database views which link to database tables with more than one entity in the conceptual model are ignored when mapping the database model to the conceptual model. These FROM clauses are not mapped. The database table is mapped to all entities. The database view is mapped to a view. 

Merging BPMN Diagrams

Additional checks are carried out when merging BPMN diagrams to ensure that the graphic displayed corresponds to the logical element. Notably, that the process definitions always remain complete.

Model Comparison Possible with Non-Unique Searches

Model comparison can be started with multiple searches. The comparison also works if subsets of different searches match.

Order of Properties Retained when Modifications Made to Superstereotypes

If superstereotypes are modified, then the visibility and order of properties needs to be maintained. This also includes properties of redefined superstereotypes.

PDF Graphics Export Revised

PDF graphics export do not have a thick white edge in the bottom and right-hand areas.

Progress Display when Importing an Excel File

The elapsed time and progress is shown in a dialog during import of the Excel file.

Repeated Creation Using Drop-Down List Works

Repeated creation in the diagram works using the “New from Template” drop-down list.

Saved Query in Submodel and Maintaining the Find Menu

The set search scope is taken into consideration when running a saved query in the Find menu. The Find menu is maintained when saving a query under a new or different name in the dialog.

Selecting Text Boxes On Closed Participants

Text boxes can also be selected if they are completely on top of closed participants.

Text Alignment in Diagrams

Text alignment works perfectly in all diagrams.

Text Correctly Displayed after its Size has been Changed

Once the size of a text has been changed, the text is shown in the size that it could be read when its size was changed.

Text Modification when Formatting in Specification Texts

Changing character and paragraph formatting in specification texts is recognized as a text modification; this makes it possible to save such changes.

Innovator 16.0.1.21011

The hotfix 16.0.1.21011 prevents the possible blocking of the server under Linux during the evaluation of a customizable search (inoref) or the “Configuration Violations” verify routine.

New Features

Advanced Search with ``Path`` Property

The advanced search can use the “Path” property. This property returns the same string as in the Result Region.

Beamer: Display of Elements without Access

The display of elements without access is optional in the Beamer and can be switched on by means of a checkbox.

CSV Export for Authorized Users

In the “Authorized Users” dialog from the “Administrative Tasks” backstage view of the model editor and in the administration program in the context menu on standalone and managed models, the users who can log in to the model can be exported with their roles as CSV.

Database and DDL Import: Elements under the Database Model Root

When importing database tables and database views, referenced elements in the model structure can be organized in different schemas or database object groups. For this purpose, there is a toggle command “Consider Database Model of the Target” in the menu ribbon of the database connection.
If it is activated, then all elements that are located in the subtree of the database model of the target schema are displayed in the right-hand list of the database manager. If it is not activated, then only the elements of the target schema are displayed there.

Drag-and-Drop of Model Elements on Notification Schedules

Model elements can be assigned to a notification schedule in the Notifications tool window view using drag-and-drop.

PowerShell: Export Users of a Model as a CSV File

In the PowerShell, the command “Export-InnoModelUsers” is provided, which exports the list of allowed users of a standalone or managed model as a CSV file.

Feature Updates

Aligning Nodes in Different Containers

Nodes in different containers can be aligned if they can be moved accordingly.

ArchiMate Import: Improvements

Multilingual import is supported. Elements that have multiple values for the name due to different language attributes are supplied for the respective display languages if these are set in the model. This also applies to the names of stereotype properties if they are added to the customization profile. The “time” type is imported correctly.

Bpanda Connector: Transfer of Specification Texts to Bpanda

When transferring specification texts to Bpanda, empty paragraphs and empty lines at the end of paragraphs are ignored.

Color Scheme Silver

The silver color scheme has been dropped due to significant contrast problems of font and background.

Concept Diagrams: Multiple Junctions Allowed

A junction represents the interruption of a direct concept connection between source and target. Multiple consecutive junctions are allowed in a path of concept connections.

DDL Import Assigns *-Expressions to View Columns

When importing a DDL file that contains a view with a * expression for view columns, this expression is assigned to exactly one view column.

Examples:

CREATE VIEW v1 AS SELECT * FROM t1; results in a view column * with the expression *.

CREATE VIEW v2 (a,b,c) AS SELECT * FROM t2; results in three view columns a, b and c, where a has the expression *.

Demo Example 'Business Intelligence Bike Share'

The demo example “Business Intelligence Bike Share” has been extended.

Dependency Editor: Performance Improvement

The performance of loading the server data for the dependency editor has been significantly improved.

Excel Export Supports Display Languages

Even if a display language is set, model elements can be exported to Excel. The language used for the export is stored in the Excel document under “Information>Properties>Tags”. When importing an Excel file, it is checked if the export language is the same as the model language. If this is not the case, then a warning appears and the user must confirm this for the import.

LDAP: Determination of the Group Assignment of Users

During LDAP synchronization, the user assignment to groups is queried via the “MemberOf” field on the user itself. If no users are found here, then an attempt is made to determine the members of a group via the “UniqueMember” field on the group.

MySQL column option

The column option ‘ON UPDATE’ is included in the MySQL template.

Search in the Whole Model Ignores Nodes and Edges in Diagrams

Searching in the whole model or in a selected area ignores nodes and edges in diagrams. This can lead to reduced search results.

Smart Icons on Fully Transparent Elements

Smart icons are not displayed on elements whose transparency is 99 %.

State Diagrams: Deleting a Trigger Does Not Delete Every Last Use of an Event

If you delete a trigger with a call event or signal event, then the event is automatically deleted if there is no further use by another trigger. If a change event or a time event is referenced by the trigger, then these events are not automatically deleted even if the last usage is deleted. These events are created explicitly and must therefore also be deleted explicitly.

Translation Revised

In the “Translation” tool window, keyboard navigation also works across multi-line text input fields. To exit these with Enter (down) or Shift+Enter (up), the Ctrl key must also be held down. When using a web service for automatic translation, in addition to several terms for all displayed languages, a single table cell can also be translated automatically, then also only for the language of the column.

Translation: File Name for Individual Selection

If you export an individual section of the model when exporting translations, then the name of the first selected package is suggested as the name of the translation file.

UML: Use Case in Details of an Extension Point

For extension points, the use case can be displayed as owner in the Details tool window.

Bug Fixes

ArchiMate: Creating Concept Realizations and Relationship Properties

If you open the selection dialog for the “Realizations” property or a relationship property, you can also create new elements in this dialog. The create templates required for this are determined from the perspective of the future owner of this new element.

Boxed Expression Editor: Insert FEEL Functions via Context Menu

In the Boxed Expression Editor, inserting FEEL functions into literal expressions using the context menu works reliably.

BPMN Import Supports Message Flows from and to Participants

Importing a BPMN file also creates a message flow even when it runs to or from a participant.

Deleting On Automatically Copying Plug-ins

If the local Innovator variable “PLUGINS_DELETE_WHEN_COPYING” is set to the value 1 when automatically copying plug-ins from a central directory, then files and directories which do not exist in the source directory are deleted in the target directory.

DDL Import Supports CURRENT_TIMESTAMP() Function

When importing a database table with a column that has an ON UPDATE option with the value CURRENT_TIMESTAMP(), the value is set as the option value if the ON UPDATE type system option is present on the table column.

Diagrams: Hide and Show Callouts

Callouts can be hidden and shown again.

Diagrams: Relationships Do Not Fully Overlap

It is prevented in diagrams that one relation (edge) completely covers another relation (edge).

Diagrams: Resize for Groupings and Frames as for Containers

Moving elements with the mouse while holding down the right mouse button will enlarge or reduce besides the surrounding (with Ctrl) or additionally the cut (with Ctrl+Shift) containers also groupings (BPMN diagrams) and frames.

DMN: Export and Import Type References

Type references (TypeRefs) are transferred by DMN 1.3 export and import as strings and no longer as qualified namespace paths.

Dynamic Viewpoints: Ignored Nodes

In the dynamic viewpoint, elements are successfully ignored in the “Add Elements” dialog even if their checkboxes were not activated in the dialog before ignoring. The “Ignored Nodes” property in the Properties area is correctly updated.

Excel Export Supports Data Type Definition

With Excel export it is possible to export an entity attribute with a data type definition.

Impact Analysis Displays Edges with Square Brackets

The impact analysis shows edges even if they have a square bracket in the displayed name.

Server: Blocking under Linux is prevented

The possible blocking of the server under Linux during the evaluation of a customizable search (inoref) or the “Configuration Violations” verify routine is prevented.

Visibility and Sorting of Type System Options

For stereotypes of database tables and similar elements, the visibility in the dialog and the order of type system options can be specified in the configuration. If options from different type systems are involved, then the names are supplemented by the type systems for distinction.

Innovator 16.0.1.20718

The hotfix 16.0.1.20718 fixes the CVE-2023-32697 (NVD) vulnerability in Java drivers. In InoAgent and InoHub, the SQLite Java Database Connectivity driver has been updated to version 3.42.0.0.

New Features

Database Snowflake: WITH Clause

DDL import and export support the WITH clause before a SELECT. During import, a view with stereotype “Select in From clause” is then created for the SELECT. This Select-in-From clause is generated by the DDL generator for Snowflake in a WITH clause. For all other databases, the Select-in-From clause is still generated directly in the FROM clause.

Database Views Support Lateral Join

In a Snowflake model, a lateral join is modeled by creating a From clause with the same target as the predecessor From clause. The expression of the From clause then starts with the keyword LATERAL.

Database Views: Select-DDL for Snowflake Extended

The on-demand template for “Information Architect for Snowflake” contains the type system options DUPLICATES (with the values ‘-‘ , ALL, DISTINCT) and TOP (Integer) for the Select-DDL of database views.

Demo Model Contains Perspectives

In the demo model “Enterprise Modeling Car Rental”, in the menu “View>Windows>Arrange Windows” there are some example perspectives that demonstrate the usage of perspectives.

Deployment Diagram Displays Deployment Specification with Connecting Edge

In the deployment diagram, a deployment specification can be created on a deployment relationship. The connection between the deployment specification and the deployment relationship is indicated by a connecting edge.

Find: Current User as Value in Advanced Search

In the advanced search, the placeholder “CURRENT_USER” can be specified as a value for string-valued properties of properties, stereotype properties and labels as well as specification texts. This placeholder will be replaced by the name of the current user when the search is executed. The value can also be inserted into the search using IntelliSense.

Impact Analysis: Edges into the Result Region

The edges of an opened impact analysis can be added to the result region using the context menu command “Result Region>Add All Graph Edges”. The model elements represented by the edges appear in the result region. For edges representing a property, nothing is added to the result region.

Logging-In Selects the Last Selected Element

If the “Model Structure” tool window view was visible when the model editor was closed, then the last selected element will be selected again after reopening.

PowerShell: New HostName Property for Managed Models

For managed models, the HostName property is provided. It contains the host on which the model is running. It is empty if the model is not started.

Tables Show Diagram Occurrences

In the “Contents as Table” and “Process Table” tables, the diagram occurrences are displayed as a column for the individual rows.

Feature Updates

Administrative Contents: Clearer Expansion Behavior

The view “Administrative Contents” in the tool window “Model Contents” shows the tree for application configurations initially completely collapsed, you can see all purposes directly below each other. In the context menu of the purpose nodes there are commands to expand or collapse all nodes. When changing the view, the expanded state is retained as in the other views.

ArchiMate Export: Performance Improved

The ArchiMate export is significantly faster, especially for “Export Extended Selection”.

BPMN: Adjust Process View to Definition Takes Over Comment Positions

When adjusting a process view to the definition, all missing contents of the process are added and, if necessary, adjusted to the position of the definition view. If comments are associated with the contents of the process, these are also added or, if necessary, adjusted to the position. It should be noted that a comment can also be located outside the process view. The position is adopted relative to the process view.

BPMN: Edge Type of Message Flows Changed

If a message flow is connected to a participant on at least one side, then the edge type rectangular is used. Only if a message flow is connected to a process content on source and target side, then a polygon is used as edge type. During migration, the edge types are adopted according to these specifications. If the previous edge type does not fit these defaults, it is adopted as a user-defined edge type. The representation of the message flows is not changed by this.

DDL View Import: View Expressions without Hyperlinks

When importing database views, the expressions are taken over as text if a target element was not found in the model. Tracing by hyperlinks is thus not possible for these elements, but the expression is complete.

Distribution of Plug-ins with Deletion

By using the two Innovator variables “PLUGINS_PATH” and “PLUGINS_DEPLOYMENT_PATH”, plug-ins can be copied from a provided source directory to the plug-in directory used when the model editor is started. If the “PLUGINS_DELETE_WHEN_COPYING” Innovator variable is set (e.g. to the value 1), then the copying process is not only additive and updating, but plug-ins in the target directory which are not present in the source directory are deleted. Thus a complete alignment of source and target directory takes place.

Dynamic Viewpoints: No Automatic Nesting in the ``Layer`` Layout

When creating a new dynamic viewpoint, starting from a start element, the reachable nodes in the diagram are added. If nesting can be expressed with the automatically displayed concept links, this nesting is performed automatically. For viewpoints with the “Layer” layout as display option, automatic nesting is omitted because this would influence the layer-wise display too much. Nesting can be done explicitly for content if required.

Find: Change Saved Search

A loaded search activates the tab stored in it (e.g. “Find Label”) and the settings it contains. If the tab is changed, then the search remains loaded and is changed.

In this way, for example, a saved search can be replaced by an extended search with the same name, without the need to delete and recreate.

Changes are marked by an asterisk after the name of the loaded search and can be saved directly. Discarding changes will restore the loaded search and switch to the corresponding tab with the saved settings.

History Table: Summary With Content History

The history table integrates the content history table. In addition to property changes, it also displays content changes (adding, removing, and moving sub-elements).The “History” ribbon provides the functions of the history table. The commands of the “Contents” group control the scope of the entries displayed in the table.

  • Entries about the history of the initial selection are always displayed
  • With the toggle command “Content” activated, entries for the content history of the initial set are additionally displayed
  • With activated toggle command “Recursive” the initial set is extended by its sub-elements (recursively)
  • The two date fields allow the restriction of the displayed entries regarding the modification date

Changes to the listed settings do not immediately affect the table, but must first be applied with the “Apply” button. The “Cancel Changes” button sets the settings in the ribbon to the state that is currently displayed in the table.

Impact Analysis: Presentation of From Clauses Changed

For From clauses, the display in the impact analysis has changed. Instead of an edge between view and connected classifier, a node is displayed. This allows the analysis starting from a used feature. The previous representation can be achieved by a summarized sub-path of owner, from-clause and connected classifier.

Set Correspondence Language for Multiple Users

In the user administration, the command “Users>Edit>Properties” can also be executed on multiple selection. In contrast to single selection, only the correspondence language for change notifications of the selected users can be changed in case of multiple selection.

Specification Editor: Horizontal Scroll Bar

If a page width for the specification editor is not explicitly defined in the options for the model editor, the text is wrapped according to the window width. Tables may be cut off horizontally in the process. To avoid this effect, the horizontal scroll bar is displayed in these cases, which enables a complete display of all tables in the text.

Bug Fixes

Java Vulnerability Fixed

The CVE-2023-32697 (NVD) vulnerability in Java drivers has been fixed. In InoAgent and InoHub, the SQLite Java Database Connectivity driver has been updated to version 3.42.0.0.

BPMN Export Considers Position and Size of a Text

When exporting a diagram to BPMN, the position and size of a text is exported. Thus, for example, the label of an event or a sequence flow receives the same position and size in other BPMN tools or in Bpanda. During import, the text position and size are also adopted. Font size and font type, on the other hand, are not exported and not imported.

Changesets: Closing a Diagram

Closing a diagram only creates an entry in the change history if changes were actually made to the diagram.

Concept Diagrams: Automatic Nesting of New Concept Nodes

For concept diagrams, it is possible to specify in the configuration whether concept connections can be expressed by nesting. When adding concepts to the diagram, the new nodes are automatically nested depending on this configuration. The nesting is only done if container and content are added to the diagram together. Existing nodes are not changed.

DDL Import Recognizes Outer Join Syntax Variants

The import of a DDL file recognizes all outer joins in a database view even without the optional keyword OUTER.

DDL Import Supports Comment for Table Column

When importing a database table from a DDL, the comment for a table column is also supported if it is set within the row.

Example: CREATE TABLE table_name (column_name DATE COMMENT ‘column comment’);

Diagrams: Saving Graphical Changes with Active Display Language

Graphical changes in the diagram are saved even when a display language is active.

PowerShell Command Retrieves Managed Models Correctly

The PowerShell command “Get-InnoManagedModelVersion” retrieves model versions correctly when multiple InoAgent instances operate on a common INOPRJ.

Specification Texts: Hyperlinks in Enumerations

In specification texts, text at the beginning of an enumerated entry can be converted to a hyperlink.

Innovator 16.0 (Innovator 16.0.1.20614)

New Features

Application Configurations: Handling Improved

The handling of application configurations has been improved:

  • Model-wide application configurations can be edited and saved directly in the inline and ribbon controls provided for this purpose as well as in the Manage dialog using the “Edit Model-Wide Configurations” privilege, without the detour via user-specific configurations./li>
  • In addition to saving, the “Save As” command is available.
  • Changes in an edited configuration can be discarded.

BPMN: Resource Assignments for Additional Process Elements

Resource assignments are also supported for data object, event and gateway.

Configuration Extensions in the Properties Tool Window

In the “Properties” tool window, new stereotype properties, labels and text definitions can be created with the necessary privilege and access rights. For a role with the privilege “Configure”, a green plus icon appears in the expanded category, which opens a wizard. This offers the same possibilities as the configuration editor, but in a much more compact way, and it ensures that the stereotype property (or label or text definition) is available at the selected model element. The created configuration property appears in the “Properties” tool window when completed.

In case of multilingual operation, existing web service for translation and with the privilege “Translate model elements”, the localizable terms can be automatically translated into the display languages in the wizard.

Content History of Elements

Similar to the history of elements, you can open a table where changes concerning the contents of elements are logged. Such changes are adding, removing and moving contents (recursively if needed). Set up notifications will inform you about such changes. The table is opened with the “Start>Open>Content History” command.

Copy Relationship Combinations

The relationship combinations of concept connections and concepts can be copied via “Engineering>Copy Relationship Combinations …”. The procedure is largely the same as copying relationships.

DB Import: Name Constraint

A new input field "Filter" can optionally be used for tables and database views during DB import as follows:
  • A comma-separated list "Name1[,Name2,...,NameN]" imports named objects only
  • "Name%" imports all objects starting with "Name"
  • Further constraints, like "Name%<anything>" or "Name%[%...%]", are not supported and lead to an error message

DMN 1.3 - Import/Export

XML import and export is possible according to DMN 1.3.

DMN 1.3: Additional FEEL Functions

The FEEL functions newly added in DMN 1.3 are available in the IntelliSense menu with corresponding labeling (1.3).

DMN: Decision Diagram Supports Grouping

Groupings are supported in the decision diagram. A grouping frame can be used to express a relationship between the grouped elements.

Dynamic Viewpoints: Tracking Direction of Concept Connections

Dynamic Viewpoints diagrams can be built using start elements and path length over connected concept connections. The concept connections followed must be specified. Only concept connections that are allowed as diagram content are available. For the tracked concept connections, the tracking direction can be restricted to incoming or outgoing relationship. With “Default”, both directions are tracked. If a concept connection is only allowed as diagram content and not as a tracked concept connection, it will be displayed in the diagram if necessary, but will not be evaluated for the calculation of the required content.

As part of the migration, all configured diagram contents are also automatically adopted as a tracked concept connection without restriction of the direction.

Dynamic Viewpoints: Ignore Nodes

In dynamic viewpoints, all nodes are offered for adding that are necessary to complete the paths according to path length. Such nodes can be marked as ignored and thus excluded from the calculation of paths. This can be used to prevent tracking of relationships that are outside the diagram focus.

Excel Export and Import Support UUID Specifications

If the option “With UUID of references” is activated during Excel export, then for each property that references model elements, a column with the UUID of the referenced model elements is created in addition to the column with the name of the referenced model elements. The same applies to the Stereotype, Access Rights and Imported Profiles properties. The name of the additional column is the name of the property extended with the string “UUID”.

When importing an Excel file with UUID columns, the referenced element is primarily searched for using the UUID. Thus, a renamed or moved model element can be found again. If no element is found via UUID, then names are searched for. In this way, a model element that has been deleted and newly created with the same name can be found again.

Excel Export Offers Options

For exporting model elements to Excel, two options are offered in the ribbon. By default, one worksheet is created per stereotype, otherwise one worksheet is created with all stereotypes. For references, in deviation from the standard, a minimum unique namespace can be specified, the determination of which increases the execution time and may increase the response time for other users. Export to CSV is done without grouping by stereotype. Export to JSON and XML is always done grouped by stereotype.

Excel Import Can Ignore Empty Cells

During the Excel import, empty cells are imported in such a way that the corresponding property values are emptied. This leads to problems with some properties, e.g. with certain element types at the name. To ensure that empty cells are ignored and the existing value is not changed, set the “Ignore empty cells” option in the “Check the file to import” dialog.

Managed Models: Display of the Version Name

In managed models it is possible to display the version name at the model root. The wizards for creating versions provide the option to specify the appearance. The placeholders $(model) and $(version) can be used, which are resolved at runtime. The model administrator can change the display in the model editor on the model root along with the placeholders. This way the display of the version can be achieved for already existing versions.

Model Content: Context Menus Extended

In the “Bookmarks” and “Diagrams (Tree View)” views of the “Model Contents” tool window, diagrams can be created using the context menu. Depending on the selection, the same menus are available as in the “Model Structure” view. The context menu also contains the “Paste” command.

Notifications

In single sign-on models, model users can be notified about changes in the model by e-mail. For this purpose, the notification service must be configured (especially e-mail server, SMTP port, sender address of the notifications). The language of the notification can be set per user in the user management.

The notifications can be set up on the whole model, on packages for their content, but also on individual model elements. It is defined whether the notification should be sent timely, daily, weekly or monthly. Notification occurs when the element itself or an element from its (transitive) content has been changed.

In the Model Content tool window, there is a new view for managing notifications. Here, notifications can be disabled in general or for a specific notification interval (e.g. “daily” due to vacation).

Notifications: Manage and Export

With administration rights, you can manage the user notifications in an Innovator model and control the behavior when exporting the model. There are three properties for the Innovator model for this purpose, which are displayed in the “Properties” tool window. For details, see help (F1) on the tool window.

OpenAPI: Integral Part of 'Innovator for Software Architects'

The OpenAPI plug-in is part of the “Innovator for Software Architects” product and thus of the “Enterprise Modeling Suite”.

Options: Show Backstage View 'Change Sets'

When working in the same changeset for a longer time, the by default showing of the backstage view “Change Sets” at program start was disturbing. In the “Display” tab, each user can use the “Display backstage view ‘Change Sets'” option to control whether they want to see this backstage view after logging in. By default, the option is disabled. Even if the option is deactivated, the backstage view “Change Sets” is available via the “Model” application menu.

Sort Documentation and Details with Structuring Chapters

In additional structuring chapters a sorting type can be set. Sorting is possible according to the displayed name or heading, label or stereotype property in each case alphabetically and for label and stereotype property also numerically. The evaluated label or stereotype property must be defined via a corresponding filter entry. In addition, it is also possible to reverse the sorting type.

The sorting always only has a direct effect on the next level. This level must not already be sorted via a model element enumeration chapter or another structuring chapter. In tables, it is possible to sort by a column in this way. Sorting is done only by the first column with a set sort type. The enumeration column of the table must not be sorted in this case.

Specification Texts: Find and Replace

The “Find & Replace in Specifications” tool window is provided by the “SpecTextReplacer” plug-in. It enables model-wide find and replace in specification texts. The tool window is opened in the “Tool Windows>View” menu group and provides the following options:

  • Find and replace text in specifications
  • Convert text in specifications to hyperlinks
  • Find and replace text in hyperlink addresses in specifications

Translation for Multiple Languages

In the “Translation” tool window, translations can be made for several languages at the same time. Display languages can be added and removed as a column. For checking the translations, e.g. in diagrams, it is possible to easily switch between the model language and the respective display language.

Updating Configuration

On the “Administrative Tasks” backstage, the “Update Profiles” button for model administrators opens a dialog that informs about the update options of the model’s profiles at the end of the migration. The dialog indicates which migration files you can easily import directly in the dialog. You can also see which migration files may cause problems during import due to existing changes in the model’s configuration. Even outside of the migration, the dialog shows which of your profiles are updateable and in which you can make changes without affecting the updateability.

User Roles Receive 'Edit Hyphenation' Privilege

As part of the transformation of repositories, “Edit Hyphenation” is automatically added to the privileges for all user roles. This does not apply to those user roles that previously had no privilege or the “Edit Annotations” privilege only.

Feature Updates

.NET 6

The Innovator client runs under Microsoft .NET 6. Innovator is delivered and installed for Windows with the required runtime environment.

Advanced Search Finds Innovator Model

In the advanced search, the Innovator model can be found. Its properties and labels that have been configured in any profile – including customizing profiles – can be used. From any model element type there is a possibility to use a subselect on #Innovator Model#. With the help of such a search query, editing in PowerShell can be controlled in a more targeted way.

Align Models: Selection List Extended

In the “Align Models” editor, additional nodes are available for selecting the comparison roots to make their contents more selectable and easier to compare. Displaying a node requires a specific privilege or model administrator rights:

Innovator and synchronization profiles (privilege “Configure”)

  • Application configurations (display name “: “, privilege “Edit Model-Wide Configuration”)
  • Database connections (privilege “Configure Database Connections”)
  • Model user and user role (model administrator)

If one of the additional nodes is selected, then all corresponding contents are compared in the model comparison. Likewise, individual contents of the next levels can be used directly for the comparison. Application configurations are considered as model content. Thus, these elements are also available during the merge. Profiles, database connections, model users and user roles are considered as configuration content and are only available for the model comparison.

Application Configuration Handling

In the “Find” dialog, the saved searches area is hidden by default. It can be shown and hidden with a checkbox. In the dialogs “Find”, “Manage Table Views” and “Configure Mappings” (for the Beamer) there is no difference between the loaded and the selected configuration, the selected configuration is loaded. The “Load” button is omitted, the “Discard Changes” button is newly added.

Application configurations cannot be loaded or saved in the “Manage” dialog, which can be opened from various context menu ribbons that use application configurations. The configuration marked as loaded is always the configuration loaded in the associated application. The functions are limited to operations on the configurations themselves.

Application Configurations for Business Intelligence Plug-ins

The configurations of Business Intelligence plug-ins are read from application configurations. After transforming Business Intelligence models from previous versions and before importing the migration profiles, the “SystemModelManagement” model, which previously contained the configurations, should be deleted.

BPMN: Arrangement of Resource Nodes

In order to be able to position resource nodes freely, they are displayed in a separate node below a task or subprocess. The following applies to resource nodes:

  • If they are not positioned by default, then they are connected to the task or subprocess via an edge
  • They can overlap with other nodes and are displayed in the background by default, but can be brought to the foreground
  • They can be located outside the process

BPMN: Export of Lanes to BPMN

When exporting a lane to BPMN, the lane gets its name and, if there is a resource, separated with space, colon and another space, the name of the resource.

If there are multiple resources, then their names are separated with comma and space.
If the lane has no name and there is no resource, then “” is output.
If the lane has no name, then only the name of the resource is output.
If no resource is present, then only the name of the lane is output.
If lane and resource have the same name, then only the name of the lane is output.

BPMN Import with Improved Stereotype Selection

When importing a BPMN file, suitable values of the configuration are suggested for stereotype selection. For a user task, for example, a create template with the task type “Untyped” is suggested if there is no create template with the task type “User”.

BPMN: Predecessor/Successor Nodes for Displaying Processes

The predecessor/successor processes of an event node are displayed in a separate predecessor/successor node. The node can be moved independently of the event and its name. A position outside the process frame is also permissible.

The configuration of the display options required for this has been moved from the event node to the predecessor/successor node. The display option “Show predecessor/successor process” has been moved from the event node to the diagram. During migration, the additional nodes are automatically created and displayed at the previous position. The display options are automatically adopted.

Concept Diagram Supports Display Options for Layout and Layer

For concept diagrams, the Layout and Layer display options are supported as for dynamic concept diagrams.

Concept Diagram: Edge Course Changeable for Edges to Edges

For edges that have an edge as a target, the connection type can be set via the context menu:

  • Direct connection
  • Rectangular connection
  • Polyline

After creating such an edge, the connection type “Direct connection” is set. For the other connection types, the edge course can be changed.

Concept Diagram: Layout Circle Renamed to Star

In concept diagrams, the Circle layout has been renamed to Star. This name fits better with the representation used, where elements with many relationships between them are moved closer together.

DB Diagram: Splitting Merged Tables

When splitting a merged table, the name of the included table is used for the new table, unless the tables are maintained by automatic mapping, in which case the name is derived from the linked entity.

Diagrams: Edge Type Adjustable in All Diagrams

In all diagrams (except sequence diagrams) the course of edges can be set via the context menu:

  • Restore Default (diagram-specific)
  • Direct (straight line, representation without edge points)
  • Right-angled (display with one or more edge points)
  • Polygon (display with freely positionable edge points)

Diagrams: Incomplete Representation of Constraints

In diagrams, a constraint is displayed even if not all elements constrained by it are visible in the diagram. Its connections are then displayed accordingly incomplete. To be able to ensure the completeness of the representation if necessary, there is the new verify option “Constraint ‘Name’ is incomplete. [VFY574]” as part of the migration profiles. This verify option is included in the “Notation Violations” verification routine for use case, class, component, composite structure and distribution diagrams.

Diagrams: Moving an Edge at the Node

The position of the edge at the source or target node can be moved, provided that the edge is displayed with movable points or rectangular.

Diagrams: Optimize Header Size

The following applies to all containers (concepts, collaborations, processes, lanes, participants, structured classifiers, etc. represented as containers) with content: If the header of the container node would increase beyond the previous size (e.g. due to a name change or icon), then the naming is shortened and ended with “…”. This prevents unintentional moving of nodes in the container.

To display the naming completely, the command “Design>Arrange>Optimize>Optimize Header Size” is available. The naming will be multiline and the header size will be adjusted accordingly. The content of the container is not moved if possible. The command is executed on all selected containers or without selection on all containers. The command “Design>Arrange>Optimize Size” is located under “…>Arrange>Optimize”.

DMN: Performance Improvement for Export

The performance of the DMN export has been improved.

DMN: Simulation Uses Drools 7.73

The DMN simulation uses Drools (www.drools.org) version 7.73.0.Final, which closed security holes.

Documentation: Avoiding Repetitions

The recursive chapter evaluations have been rearranged to avoid repeating information in a document. The recursion of a chapter evaluation is aborted if an element in the evaluation path is already evaluated for exactly this chapter. This abort criterion has been rearranged so that an element contained in multiple sub-paths is only evaluated completely for the first occurrence at the highest level. This avoids the repetition of identical information. For each evaluation on a lower level only the heading of the element chapter is output. All contained chapters (including the recursion) are not evaluated.

ER Diagram: Automatic Layout

In the ER diagram, the command “Standard Layout>Arrange Diagram” is available in all notations.

Excel Import Considers Create Defaults

If a model, a system model or a package has been selected as target for the import of an Excel file and no owner is defined for a model element in the file and the model element cannot have the selected target as owner, then the create defaults for the creation of a new model element are evaluated and the imported model element uses the target of the create default as owner.

Excel Import Shows Owner for New Elements

The Excel import shows which model element will be the owner for new model elements in the preview dialog in the tool tip. If a create default was used to determine the owner, this is also displayed.

Excel Import and Export: Messages

Excel export and import provide all messages that have occurred at the end of the export or import in a dialog. If there are numerous messages, then they are stored in a file named Excel_.log in the temporary directory. The messages are grouped and sorted by line numbers within the groups.

Hyphenation

To change the standard hyphenation you need:

  • in the model editor the “Edit Hyphenation” privilege
  • in the administration program the environment right or the login as administrator

The dialog for changing the hyphenation can be opened on a selected diagram node with the context menu command “Hyphenation”. In this dialog, all separable words (> 3 characters) of the selected node are displayed in the set display language and can be changed. The button “Standard” is activated if the hyphenation does not correspond to the standard. In the dialog, words for hyphenation can also be entered that are not contained in the selected node.

In the administration program, a dialog for editing the hyphenation is opened on the backstage with “Hyphenation”, which contains all words from all models that do not correspond to the standard hyphenation.

Impact Analysis: Use of Application Configurations

When opening an impact analysis, the model-wide application configurations for content and display last set for the diagram are used by default, provided that the user himself has not most recently used any user-specific configurations for the diagram. In this case, his content and/or display configurations are used.

Users are informed when opening the diagram which user, if any, has most recently set a user-defined configuration.

Logging in Again without Closing the Model Editor

If a user is automatically logged out of a model, e.g. by the inactivity setting (in the administration program), then the user receives a note about this. He can log in again without having to exit and restart the model editor.

Migration of the Agent Database

When migrating managed models, an attempt is made to correctly update the agent database directory name. For more details, see the Migration Manual.

Naming Convention for Names of Model Servers

The naming convention for model servers (repositories) allows digits as the first character in addition to letters.
[A-Za-z0-9][A-Za-z0-9_]{0,254} (representation as a regular expression; so e.g. also no umlauts)

Options for Relationship Wizard Extended

The relationship wizard (magic wand icon) is now available in all diagram types. In the options, the following alternatives regarding the relationship wizard are available in the “Mouse” tab under “Creating a Relationship Using the Carousel”:

  • Do not display relationship wizard in carousel
  • Display relationship wizard in carousel additionally
  • Display relationship wizard in carousel only

Output Smart-Icons at Graphic Export, Hardcopy and Documentation

Smart icons can be used in the diagram, e.g. to recognize existing specification texts on diagram elements. The active smart icons are applied when printing, copying to the clipboard and exporting the diagram. If the “Show Active Smart Icons in Graphic” property is activated in the documentation command, then the active smart icons are also adopted for the documentation.

Privileges Renamed

The names of the procedural rights have been revised.

Result Region: CSV Export Contains UUID

The command “Export CSV File” in the result region additionally exports the UUID in the second column.

Slots are Commentable and Constrainable

Slots are elements that can be commented and constrained. This allows comments and constraints to be associated with slots. For constraints, the property “Constrained elements” must allow slots in the configuration.

Specifications: Opening Specification Texts of Connected Elements

In some specifications, the texts of linked elements are displayed read-only. Examples are the texts of synchronized elements or called elements of tasks. In the active tab of such a read-only text, the specification text of the connected element can be opened for editing with the context menu command “Open Specification” or with “Start>Open>Specification”.

Tables for Content and Process Tables: Showing and Hiding Columns

In process tables and tables for content you can open a dialog with the command “Design>Table View>Show Columns” which allows showing and hiding columns. The made setting is saved and loaded along with the table configuration (e.g. column widths, sorting, grouping). The dialog replaces the context menu on the table header for showing and hiding columns. The advantage consists of an increased performance for large tables.

Transformation as of Version 14.1

The transformer can only transform repositories and model versions from version 14.1 or higher. If your source version is older, you have to make an intermediate stop in an older version (14.1–15.2) and install it for this if necessary.

Bug Fixes

Align Models: Consistency Message is Prevented

During model aligning, the server is prevented from terminating with the consistency message “Diagram ” contains more than one presentation of process ” nested into the same node, which is not allowed. Only on the top diagram level more than one representation of the same process is allowed.” For the process, it is ensured that there are no duplicate views of a process in the participant node. In case of error, the message “” of type ‘participant node’ cannot be assigned to ” of type ‘process view node’ as ‘owner’.” is provided.

Align Models: Merge of Lane Representations

During model alignment of BPMN diagrams, it is ensured for the removal of a lane representation that the lane is empty. The lane is considered empty even if all remaining content is also removed or moved to the process view during model alignment. The shutdown of the model server is prevented.

Automapping from Attribute Change Null to Primary

When a null attribute is changed to primary in an entity, the automatic mapping sets the null property of the column correctly to Not Null. The model server repairs table columns that are primary and incorrectly null.