CATIA Magic / No Magic Modeling Tools

Released on: July 17, 2026


2024x Refresh3 Hot Fix 3 is now available for CATIA Magic and No Magic portfolios. It includes a number of improvements, bug fixes, and vulnerability fixes in our modeling tools and server products.

Hot Fix version compatibility

The version and Hot Fix number of a modeling tool and its plugins must be the same. After installing the Hot Fix version of a modeling tool, select the same Hot Fix version when downloading its plugins. The modeling tool will not work correctly if you install plugins of a different version and/or Hot Fix number.


Magic Software Architect / MagicDraw

Collaboration in Teamwork Cloud

  • Used projects containing elements with duplicate local IDs can now be removed successfully.
  • The issue causing indirectly used profiles, such as the Data Markings Profile, to become directly used after project migration has been resolved.
  • The issue causing an error when updating project usages to their latest versions has been resolved.
  • The issue causing an error when clearing unresolved proxies has been fixed.

Collaboration powered by the 3DEXPERIENCE platform

  • The issue preventing a project from opening after committing a merge with rejected changes has been resolved.
  • The issue causing Requirement Derivation Maps to require a manual refresh after requirements were created or deleted has been resolved.
  • The issue causing matrices to require a manual refresh after relationships were created or deleted has been resolved.
  • The issue causing a corrupted local cache to be created after a network error while loading a project has been resolved.
  • The issue preventing a 3DEXPERIENCE platform project from opening after the required security certificate was added has been resolved.
  • The issue causing unresolved references to remain after committing merged changes has been resolved.

Magic Model Analyst / Cameo Simulation Toolkit

  • The issue causing logging configuration errors during simulation deployment has been resolved.
  • The issue preventing FMUs exported from Dymola 2025x Refresh1 and later from initializing correctly has been resolved.

Magic Collaboration Studio / Teamwork Cloud / Cameo Collaborator

  • Fixed a bug in RBAC where category move could unexpectedly grant access to originally restricted resources under the new category.

Cameo DataHub

TRM Integration

  • The issue where the Create Sync operation could fail after removing DHLinks from a specification has been fixed.
  • The issue where synchronization from the modeling tool to TRM could fail when updating certain requirement attributes has been fixed.
  • The issue where relationships could be missing from the Mapping window during the Copy Data with Sync operation after changes were made to a requirement specification has been fixed.
  • The issue where Widget List attribute values were not displayed in the DataHub properties of a Specification Folder has been fixed.
  • The issue where synchronization could fail when the TRM Name attribute was mapped to the appropriate attribute in the modeling tool has been fixed.
  • The issue where creating a Requirement Specification under a Specification Folder from the DataHub Explorer could fail has been fixed.
  • The issue where creating a new requirement could fail when a mapped attribute value contained spaces has been fixed.
  • The issue where synchronization from the modeling tool to TRM could fail in migrated projects containing multi-value specialized type attributes has been fixed.
  • The issue where certain custom attribute values could not be updated in the DataHub properties has been fixed.
  • The issue where multi-value widget enumeration attribute values were not copied from TRM to the modeling tool during the Copy Data with Sync operation has been fixed.
  • The issue where the Copy Data with Sync operation could fail when copying requirements from the modeling tool to TRM has been fixed.
  • The issue where TRM widget attribute values could not be updated from the modeling tool or through DataHub properties has been fixed.
  • The issue where requirement attributes could not be edited in the DataHub Explorer when the -Ddatahub.bulk.data.operation=false option was used has been fixed.
  • The issue where certain attributes could not be edited in the DataHub Explorer has been fixed.
  • The issue where synchronization from TRM to upgraded Teamwork Cloud projects could fail with a "No value present" error after using the Check Changes Recursively operation has been fixed.
  • The issue where adding a TRM data source from the 3DEXPERIENCE platform could fail has been fixed.
  • The issue where an unexpected OSLC link could be created when copying synchronized data from TRM to the modeling tool has been fixed.
  • The issue where the DataHub Explorer did not open when the ENOVIA Requirements command was selected after reconnecting to TRM has been fixed.
  • The issue where the ENOVIA Requirements command could fail to add the TRM data source in a new Teamwork Cloud project has been fixed.
  • The issue where the Copy Data with Sync operation did not transfer all attribute values from TRM to the modeling tool has been fixed.
  • The issue where the data source name could change after using the Show IP Configuration command has been fixed.
  • The issue where duplicate widget attributes were displayed in the properties of the default requirement type has been fixed.
  • The issue where synchronization could fail after importing a model version in a 3DEXPERIENCE platform project has been fixed.
  • The issue where schema mappings for custom attributes were not saved has been fixed.
  • The issue where the Check Changes operation did not detect updates to mapped multi-value widget enumeration attributes has been fixed.
  • The issue where searching for "&" in the DataHub search bar caused nodes with Turkish characters to be displayed incorrectly has been fixed.
  • The issue where Turkish characters in synchronized TRM element names were displayed incorrectly in the DataHub Explorer and Containment tree after synchronization has been fixed.
  • The issue where requirement attributes could not be edited in the DataHub Explorer when a custom attribute had an empty default value has been fixed.
  • The issue where Type-Ahead search in the DataHub Explorer did not find requirement objects whose names contained spaces has been fixed.
  • The issue where synchronized nodes could be incorrectly marked as excluded for certain attribute mappings has been fixed.
  • The issue where synchronization icons were missing from revised objects in the DataHub Explorer has been fixed.
  • The issue where connecting to TRM could take significantly longer after reopening a previously synchronized 3DEXPERIENCE platform project has been fixed.
  • The issue where synchronization from the modeling tool to TRM could be cancelled for requirements with mapped enumeration attributes has been fixed.
  • The issue where synchronizing large numbers of requirements from the modeling tool to TRM could take an excessive amount of time or fail to complete has been fixed.
  • The issue where custom attribute names displayed in the DataHub properties did not match those shown in TRM has been fixed.
  • The issue where custom requirement type names displayed in the Copy Data with Sync mapping dialog did not match those shown in TRM has been fixed.
  • The issue where synchronization icons were missing from synchronized requirement specifications added to the DataHub Explorer has been fixed.
  • The issue where opening the properties of the first element under a large data source node could take significantly longer has been fixed.
  • The issue where the DataHub Explorer could not be reopened through the ENOVIA Requirements command after reconnecting to TRM has been fixed.
  • The issue causing slow performance when transferring DHLinks between requirement specification revisions has been fixed.

IBM DOORS Integration

  • The issue where the Open Module in New Window command did not open DNG modules in a separate window has been fixed.
  • The issue where folders could not be created under DOORS Next Generation projects from the DataHub Explorer has been fixed.
  • The issue causing reduced UI performance when a DataHub data source was connected has been resolved.
  • The issue where the Check Changes operation incorrectly detected changes for synchronized requirements with mapped Boolean attributes has been fixed.
  • The issue where the Select in Application command did not navigate to synchronized DOORS folders and modules has been fixed.
  • The issue where single-valued enumeration attribute values were displayed in brackets in the Conflict Dashboard has been fixed.
  • The issue where configuring DOORS Next Generation backlink support required a manual Java startup argument has been fixed.
  • The issue where multiple DOORS Next Generation server data sources could not be added has been fixed.
  • The issue where custom DOORS Next Generation enumeration attributes could not be imported via DataHub has been fixed.

JAMA Integration

  • The issue where an internal error could occur when right-clicking a synchronized JAMA folder has been fixed.
  • The issue where sets could not be created in JAMA projects from the DataHub Explorer has been fixed.
  • The issue where the Check Changes operation did not detect updates to diagrams and images in synchronized sub-requirements has been fixed.
  • The issue where connecting to JAMA using Basic authentication could fail has been fixed.
  • The issue where moved JAMA items were incorrectly identified as new and their synchronization links could be reported as deleted has been fixed.
  • The issue where the Check Changes operation incorrectly detected changes for synchronized requirements with mapped Boolean attributes has been fixed.
  • The issue where the Check Changes operation did not detect updates to mapped Boolean attributes has been fixed.
  • The issue where the JAMA Single Project Selection dialog could occasionally appear blank has been fixed.

Other

  • The issue where links could not be excluded from synchronization in the mapping window has been fixed.
  • The issue where the Create Sync operation could be blocked by links to unloaded elements has been fixed.
  • The issue where attribute names could appear blank in the DataHub UI has been fixed.