AutomationML Editor 6.3.11

Version 6.3.11.2

New Features

• If an extension is selected in the add reference dialog, the original document version is marked with a map marker.

Changes

• Increment minor version always sets the patch version to 0.
• The version upgrade assistent has been modified. If the current file has unsafed modifications it can be saved before the upgrade. The upgraded file can be saved to a new file.
• Extenal referenced files which are local files are no longer copied to the _AMLExternalLibraries folder.
• Alias names are editable in the upgrade version dialog.
• When a new version or extension of a document is created the referenced documents in the new version are checked for updates. If old versions are referenced the upgrade dialog is showed.
• Generated Aliasnames for extensions will contain the extension text.
• An informational message in the dialog to transfer server data has been modified.

BugFixes

• Fixed a bug, where a SupportedRoleClass gets an invalid path reference when created from an external RoleClass
• Fixed a bug, where a Path to an external AttributeType was not marked as invalid, when it could not be resolved to an external AttributeType.
• Fixed a bug, where invalid alias names were not listed in the validation report.
• Fixed a bug, where the switch of the signature validation from off to on could raise an exception.
• Fixed a bug, where an internal link, defined in a class was not copied to a class instance.
• Fixed some issues related to instance creation, where ID references wer not updated to there corresponding instance elements.

AutomationML Editor 6.3.10

New Features

• The Service Configuration Dialog provides a new command button to open the profiles folder of the editor.

Changes

• The menu items to open external files and collection have been moved from the File->Open menu item to a new File->Load menu item.
• Increment minor version and patch version options for classes, used in the version creation dialog, also change the document and library version numbers.

Bug Fixes

• Fixed an issue where a modified class name was not propagated to the class children, when the children were derived from the changed class.
• Fixed an issue where the creation of an instance of an external class failed to create valid class references.
• Fixed an issue where a valid name of an attribute, shown in the header editor, was marked as invalid.
• Fixed an issue where the close button in the outsource dialog has no effect.
• Fixed an issue where the preview window for external documents could raise an exception when internal links are expanded.
• Fixed an issue where the resizing of the server administration dialog left blank spaces in its window.
• Fixed some issues with bad text colours when the dark mode is used.
• Fixed an issue, where the settings icon in the right window command button was invisible in some themes.
• Fixed an issue, where references to document versions could defined with an not unique alias name.
• Fixed an issue, where the selected dependency relation was not updated in the dependency diagram.

AutomationML Editor 6.3.3

Version 6.3.3

New Features

• Newly created libraries are automatically assigned an ID.
• If a class is selected in the library view of an external document, the relation view also shows the classes derived from it, including the derived classes of the main document.
• ExternalReferences, classified as version references also contain a Version element, defining if the reference links to a new Version (forward) or old Version (backward).
• If three consecutive unauthorized login attempts have been made to an AutomationML file provisioning service, no further attempts will be made by the editor. Otherwise there is a risk that the IP address will be blocked by the server. The editor informs the user that the number of unauthorized login attempts has been exceeded. The login block remains in place even after the Editor is restarted. The editor will not attempt to log in again until the user releases the lock. This is possible when executing the connection check in the configuration dialog of the service. However, this should only be done if the login information is correct.

Changes

• If a new document version is published that contains versioned classes or libraries, but these classes or libraries are not contained in the published previous version, the version references of these classes are deleted in the new version. This can happen if intermediate versions are involved.

Bug Fixes

• Fixed an issue where a new version document, created from a local copy of a published version, did not create a forward version reference in the published version.
• Fixed an issue where the merge service failed to correctly classify an imported external reference as a version reference.
• The problem that publishing a new document version to a local file system did not create a version reference has been fixed.

AutomationML Editor 6.3.2

New Features

• The servicename of the selected active external AutomationML file server is shown in the top right main window header. The displayed name can be clicked to open the service configuration dialog.
• The verification icon for signed libraries provides the service name of the verification source in its tool tip.
• Server addministration allows to update key files used for library signing.
• Adding an AutomationML ID as a semantic reference to attributes is an additional paste option when pasting external attribute type references.

Changes

• The feature to automatically create an inheritance relation for child classes has been removed. It is recommended to model classes preferably in libraries as a flat list structure and not artificially reproduce the inheritance hierarchy.
• Due to an update in the modeling conventions for AutomationML libraries, classes and types are checked to contain a description.
• The dialog for moving an external AutomationML file distributor to another server has been modified. It is started via the configuration dialog of the new server.
• Library versionnumbers for exended versions of libraries or new editions do not require a higher version number for delta extensions.
• New document and library editions do not automatically increase the version number of classes.
• Dialogs for server administration have been redesigned for better feedback.
• The External Reference Assignment dialog has been modified and shows the already used references of the current document.

Bug Fixes

• Solved some issues regarding possible deadlocks when an external file sever could not be connected.
• Fixed an issue where undoing would leave an invalid document status and a subsequent check would cause a crash.
• Fixed an issue where copying a class with a base class reference from an external document creates an invalid base class reference in the copied object.

AutomationML Editor 6.3.0

Version 6.3.0

This version of the editor facilitates the creation and publication of AutomationML library and document versions. It supports collaboration in the development of new versions and their distribution. The editor offers new functions for managing content, hosted on an AutomationML file server, such as withdrawing documents that have been published erroneously or incorrectly. A valid editor license is required to use all functions in this context.

New Features

File Service Configuration

• It is now possible to configure multiple file service profiles for the same host. This allows to use a release configuration and a development configuration using the same hosting server. The different configurations are to be named with a unique service name.
• The file service configuration allows to define a new backup data profile. The backup profile is used to save documents, which are removed from the hosting file server. Backed up files may be restored.
• There is a new dialog for the administration of a configured file server. This makes it possible to withdraw published documents and renew the registration of classes and libraries. File transfer to a new server address with URL redirection can also be organized here. The dialog can be started via the server configuration dialog when authorized write access to a server is defined.
• Withdraw a published document: Published example and library collection documents can be removed from a publishing location at any time. Under certain circumstances, it is also possible to remove a published library document from the publication location. In this case, all entries made by the publication are reversed. If a backup data profile exists, the removed document is saved and can be restored.
• Restoration of backed up files: All backed up files may be restored to their original location. For backed up library documents the publication process is repeated. A backed up file can also be deleted permanently.
• Recalculation of library and class catalogs: If conflicts arise during the publication of documents, it may be necessary to recalculate the library and class catalogs. When recalculating the library catalog, all published libraries must be re-signed if the signature was contained in the library catalog.
• Server file transfer: All documents provided on a server can be transferred to a new provisioning location if a corresponding service profile is configured for the new location. If the transfer is successful, a redirection table is created, which can be used to redirect the now unreachable document addresses to the new addresses.
• The editor loads redirection tables from its local configuration folder or also from its public GitHub repository. If a redirection table is provided on GitHub, the URL redirection is set up for all users of the editor. If redirects are not to be used, the redirect files must be deleted manually.

Document Version Management

• When a new library version is created and not defined as an extension, all classes in the new library version are also versionized. The user selects whether the minor version or patch version of the previous version is incremented. An automatic increment of the major version for all classes is not supported.
• If a previous version does not have a version number, version 1.0.0 for the previous version is assumed.
• It is possible to create a new version of an already versioned document. This makes it possible to create different branches for versioning.
• It is now possible to create a new document version of the actual edited document by selecting the Create new version Menu in the main edit menu.
• It is now possible to create a new version for a higher AutomationML edition. A CAEX schema transformation is carried out for the new document and an attempt is made to swap external references for existing versions of the higher edition. Attributes of classes are extended with references to existing attribute types if possible. If no attribute type can be found for a class attribute, a new attribute type is created and referenced. With this procedure, it can happen that class references can no longer be resolved and manual reworking is required.
• If external documents are referenced, the user will be informed if new versions of the external document are available. The desired version can be selected and exchanged in a dialog that opens. This feature must be activated in the document preferences settings.

Document Publishing

• Recommendations for the naming of classes are checked, when a document is published. Names can be edited using the repair function.
• If the data type of an attribute is ‘xs:string’ or the attribute is a structure attribute such as a list attribute, the system checks whether the unit is empty.
• If the data type of an attribute is a numeric data type, the system checks whether an attribute unit is defined. As repair method is offered for missing units.

General

• Attributes can now also be added via the Add button in each window of an element tree if an element with attribute assignments is selected.
• In the drop-down menu of the ADD button, you can now either create a new element without a type reference (as before) or an instance of an external class or type. Necessary references to external documents are added automatically. The drop-down menu contains an additional button for this purpose.
• A new dialog is available which opens when the ADD from externals button in the drop-down menu of the Add button is clicked. The dialog allows to navigate all classes of all external documents shared by a file server. The classes are represented as the normal library order tree or alternativly as an inheritance tree.
• It is possible to capture an image of the dependency diagram for libraries and save it in the clipboard.
• The used UNECE code table defining units of measure has been updated to revision 17. A new selection dialog allows to filter and navigate listed quantities and units. It is also possible to select the unit common code or alternatively the unit symbol as an attribute unit. The preference can be selected in the attribute editor settings.

Changes

Document Publishing

• Fixed an issue where a forward version reference was not created when the name of the new version object has been changed.
• The publishing dialogue only shows the publishing locations for which write access is configured.
• Changing the publication target in the publishing dialogue will invalidate the conformance conventions that have already been positively validated.
• The standard file extension for key files for signing is ".key.json". However, existing files with the extension ".key" can also be read in.
• Fixed an issue where publishing a new document version to a target location that is different from the source location was rejected due to a local URI in a version reference.
• Version references between new version and previous version documents are automatically created when the new version is published.
• Forward Version references relating a previous version with a new version are not created, when no previous version is already published at the selected publishing location.
• Already published libraries are allowed to be published again when a different file server profile is selected.
• A SourceDocumentInformation, defined and inserted by the AMLEditor, is deleted when a document is published with a new Document Identification.

Document Version Management

• The creation of extensions in the Create Version dialog has been changed. Extensions may contain the classes of the previous version or may be defined as delta extensions without containing any previous library versions.
• When a new document version is created, document version forward references are not saved to the locally saved external source version. The version references are only generated when the new version is published.
• Names describing extended versions of documents are checked to contain only allowed characters.
• The numbering of extension versions can start from the beginning, if the extension is marked as delta.
• Description text of ExternalReference defining a version reference is changed to 'VersionRef'.

File Service Configuration

• Library Server configuration can be directly called from the Extras-Menu without showing all options.
• Additional folder profiles can not be added in the Library Service configuration dialogue, if all access opportunities are already defined.
• Adding multiple folder profiles for the same document type and AutomationML Edition is rejected in the service configuration dialogue.
• The configuration dialogue for the shared file service has been further revised. Validity checks and some other information have been added.

General

• The dependency diagram for libraries has been revised, filenames are shown in node displays and arrow directions are normalized.
• SaveAs for documents shows the filename of an existing file as the default name
• Adding a local file as an ExternalReference the reference path is set to a relative URI if the local file can be located in the same directory or any sub directory as the current file.
• When a new expandable item has been added to a collection in the side view, the new object is expanded by default.
• Fixed an issue where the computation of the string, used to calculate the signature, provides different results for the same caex element when called from different locations. This resulted in an unverified state for signed objects.
• An empty Attribute Datatype assignment is shown as "Null" in the sel...

AutomationML Editor 6.2.8

New Features

• A new check button is defined in the server configuration dialog to check the connections to all configured folder profiles.
• A new Algorithm to find classes or types in online repositories based on character comparison has been added to the FindOnline dialog.
• When a document is published, a task protocol window is displayed, showing the state of selected and possible publication steps.

Changes

• The SaveFile Dialog has been modified. It is recognized whether the selected directory is already used for local storage of external documents.
• The '_AMLExternalLibraries' folder is not created, when the saved document has no external references defined.
• The AutomationML file server selection button has been changed to a split button, allowing to change the active file server.
• The create version dialog has been modified to show extension texts and the new versioned document name.
• All newly created classes and attribute types automatically receive an ID.
• AutomationML document files which are saved on a file server are not listed, if the filename starts with a '.'.
• When a new versions of a document is created, source document informations of the previous version are updated in the new version.
• Adding references to external sources is enabled in offline mode, allowing referencing files from local hosts.
• Signaturekeyfile is saved with .key.json estension. Extension is required to be recognized when saved in the signdata folder of the file server.

Changes according to the publication of documents

• The usage of the prefix 'AutomationML' is not checked in the publication process, allowing to publish AutomationML owned libraries to temporary locations.
• ExternalReferences to local files are allowed when the document is published to a local server.
• Attributes which do not reference an attribute type are not marked as violations of modeling conventions, when any ancestor attribute references a type.
• Missing Attribute DataTypes are not marked as not recommended, when the attribute is structured.
• Missing version references from old to new version is not reported as an error when the new version is marked as an extension.
• Documentidentification in Publish Dialog of extension documents has extension comment included in the suggested filename.
• A precaution is taken to ensure that the publication of a document does not overwrite an existing file due to an already listed file name.

Bug Fixes

• The size of the signature dialog window is set to with and height of the displayed content.
• The create version menu item is always available for classes in versioned libraries.
• If a local file is referenced as an external, it is copied to the external libraries folder of the edited document.
• Access to undefined folder profiles does not trigger any exceptions.
• Fixed some issues where publishing of Containers as examples and loading published containers throw exceptions.
• Fixed an issue, where the activation of the CAEXOject Header editor via context menu (i.e. Revision or RefSemantic) did not allow editing.
• Fixed an issue, where the verification shield of a signed library was not shown, when the library was published on a local folder.
• When a new version of a signed library is created the new versioned library does not keep the signature.

AutomationML Editor 6.2.3

Version 6.2.3

New Features

• The 'Find class online dialog' contains a new option to define an inheritance relation between the selected class and the class found.
• The 'Find class online dialog' contains a new option to define a semantic reference when the dialog is called from a selected attribute type.
• The 'Add Reference ... dialog' contains a new option to create new versions for all libraries contained in the referenced document.
• A Semantic reference to an AutomationML attribute provides a new button/ method to lookup the attribute definition.
• It is now possible to create versions for classes and attribute types without a drag/drop operation if the containing library is already modeled as a new library version.

Bug-Fixes

• Fixed an issue where online search of existing classes throw an exception.
• Fixed an issue where excluded instance hierarchies are still be included in the outsource dialog.
• ExternalReference Path editor allows selection of files from local storage.
• Fixed a bug in the outsourcing dialog
• Fixed a bug in publishing dialog
• Fixed a bug in undo/redo methods when a transaction includes multiple documents
• The error that the help pages were no longer offered has been fixed.
• ExternalReferences which are no more used after outsource was successfull will be deleted.
• It is no more possible to add references to multiple versions of the same library to the same document.

Changes

• Attribute Types in published libraries must have a unique ID assigned
• Library dependency view needs to be activated by clicking a button to show the dependency graph.
• ExternalReferences used for version relations are distinguished from ExternalReferences used to access external model objects.
• ExternalReferences which are no more used after outsource was successfull will be deleted.

AutomationML Editor 6.2.1

AutomationML Editor Release Notes

Version 6.2.1

With version 6.2, the AutomationML Editor offers more support for the management and creation of AutomationML class libraries according to Conventions for the modelling of AutomationML libraries in addition to continuous bug fixing. The new functions are activated by default, but they can be deactivated via the options dialog.

The most important improvement in version 6.2 is the distribution of AutomationML libraries via a publicly accessible file server and the integration of the libraries via external references. The editor contains a preconfigured access to the AutomationML NextCloud as a file server. However, it is also possible to use a company-owned or privately used file server as long as it is accessible via the WebDAV/Https network protocol. All configured servers can also be used in parallel.

As the AutomationML NextCloud server could be replaced in the future, the URLs of the integrated external references for accessing the libraries would have to be changed in this case. However, when a new server is introduced, the editor will provide a feature, to redirect and update the external addresses automatically.

You can find detailed instructions on how to use the new features in the wiki on the following topics:

• Using external Sources

• External Source Windows

• Preview Windows

• Publishing

Version 6.2.1 is published for the .NET 8 Desktop Runtime.

Options to activate library management

• Select the Access External AutomationML Files in the options dialog or from the editors main tool bar to get access to external AutomationML files from the AutomationML file server (currently the NextCloud; Internet access is required). Please note that by enabling this feature, the former provided import function from the AutomationML website will be disabled.
• Select the Save Externals in the options dialog to enable the local storage of referenced external libraries when saving the document. This means that all referenced external libraries, as well as their dependencies are stored to the documents relative folder '_AMLExternalLibraries' and are available offline for the current document.
• Edit or configure access profiles for file servers from the options dialog.

New functions for library management

• The File menu contains the new Add Reference function. This allows the content of an AutomationML file from an external source, either from the AutomationML server or a company's own source, to be integrated into an existing document as an ExternalReference. All libraries from the external AutomationML file are displayed in separate windows ('External Views'). This function is only available if the Access External AutomationML Files option is selected.
• The File menu contains a new method Outsource Libraries. This function can be used to outsource the libraries contained directly in the document. Libraries that are published on the AutomationML library server are integrated as external sources, other libraries are outsourced to locally saved documents.
• The File menu contains the new Publish function. This function displays a dialog for publishing the currently edited AutomationML document to the activated library server. In order for a document to be published, the libraries it contains must fulfill the published conventions. When a library document is published to the AutomationML file server, all libraries are automatically signed. For user defined libraries, published to different target locations, the signing is optional.
• When library modelling conventions are reviewed the result is visualized. Specific repair dialogs are offered to repair failures to comply with mandatory conventions.
• The Open menu provides the new External Collections function to load AutomationML defined library collections from the AutomationML file server or any other configured server. A collection contains preselected external references supporting specific modeling aspects. This function is only available if the Access External AutomationML Files option is selected.
• The Open menu provides the new External Examples function to load AutomationML defined examples from the AutomationML file server or any other configured server. Example models can contain class libraries which are not published and may contain InstanceHierarchies. AutomationML published class libraries are included using external references. This function is only available if the Access External AutomationML Files option is selected.
• The View menu provides the new View Externals function to open external referenced files and display the contained libraries in extra windows.
• A new dialog has been added to browse the AutomationML file server to select libraries, models or example files. It is possible to enter filter criteria and to preview selected files. The dialog is viewed, when one of the mentioned referencing functions is called.
• A new dialog has been added to add and edit access profiles for a file server to provide libraries, models or example files. If write access rights are defined, a server can also used to publish documents.
• A library dependency graph is shown as a new relation window. Library dependencies are defined by versioning relations between libraries and class to class relations.
• All external referenced files and their dependencies are automatically saved to a local folder, named '_AMLExternalLibraries' when a document is saved. The locally saved libraries enable the usage of the contained classed when the editor is used in offline mode. This behavior is activated if the Save Externals option is selected.

New Features

• Support to dragg libraries and to paste them into the library container is added.
• "Create Version" is added as a new paste option for dragged libraries. Library versions can be marked as extensions.
• "Create Version" - dialog supports to edit a version number.
• Version information is shown behind the library name in tree views.
• Revision links are updated with alias references if the related version is external.
• Problem report dialog contains a new button to open the folder, containing the error log.
• New method to naviagte to all referenced role classes from systemUnit classes and InternalElements

Changes

• The function to create new documents initialized with AutomationML standard libraries has been removed. Standard libraries can only be used by referencing the external sources.
• The function to import AutomationML files from the AutomationML website has been removed. If the Access External AutomationML Files option is not selected, the import from AutomationML is still available.
• The menu item Tools has been renamed Extras.
• The menu item Settings has been removed. Settings can now be made in a new dialog, accessible under Extras->Options.... Options are grouped in categories.
• Backup file restoration dialog window can now be closed without restoring the file. Selected files are only restored, when the OK button is pressed.
• The naming for backup files has been changed. The current file name is included.
• Document version headers are not inserted into a document when no document versions are defined.
• AutomationML editor does not automatically adds a SourceDocumentInformation object to a modified document if a SourceDocumentInformation already exists.
• Split always creates an external reference into the remaining document, also when no classes of the splitted libraries are referenced.
• External reference path are created as relative paths when the location of the external document is relative to the edited document.
• Allowing references to external sources from documents, contained in an AutomationML container.
• Facet-Names of sibling facet-elements are checked to be unique.

Bug-Fixes

• Fixed an issue where opening settings threw an exception.
• Fixed an issue where the expansion state of properties was not maintained when the view changed.
• In the file-name attribute of a CAEX-Document no longer the complete file path is stored but only the filename.
• Fixed an issue where the name of the backup file was shown as the file-name attribute instead of the document filename.
• Fixed an issue where documents in the document version collection of an AML File were deleted.
• Fixed an issue where expanded collection in views could not be closed.

AutomationML Editor Version 5.6.11

Version 5.6.11

Issues Addressed in this Release

• Runtime version changed to .NET Framework 4.8
• Update to last version of Aml.Engine

Version 5.6 will be the last version which does not require a license. Service releases will be available providing bug fixes. New features are only added to version 6.0 and beyond.

You should exchange the AMLEditor.exe.config after installation using the attached file. It is needed to load the OCLEditor plugin.