Orchestration now also supports MTP files that do not fully conform to Manifest 1.1.0.

Previously, it was not possible to use MTP files in Orchestration Studio that differed from Manifest 1.1.0. Files that differed were recognized as errors during validation. Being detected as errors meant that these files were not available for orchestration in Orchestration Studio.

• In the current version, any differing content that is negligible for orchestration is now only treated as a warning. The current Aspect.Profile concept of the Standard is supported and it is also possible, for example, to use files based on Manifest 2.0.0 in Orchestration Studio for configuration.
• The most recent AutomationML libraries (v2.10) are supported.
• MTP files that do not have origin information are automatically given a placeholder when loading the file in the Template Editor task, which is substituted with COPA-DATA origin information with the current LastWritingDateTime on saving.
• MTP files created with relative AutomationML Paths can be read.
  Example: AutomationML Path of AnaMon can be MTPDataObjectSUCLib/DataAssembly/IndicatorElement/AnaView or AnaView .
• The MTP file is checked for duplicates and normalized when it is loaded. The names of data assemblies, services including all contained objects, HMI pictures, visual objects and server assemblies are checked.