Released on: November 28, 2025


In the 2026x release, we implemented the UAF 1.3 standard, which includes key features for Mission Engineering Modeling. The UAF 1.3 Profile is fully supported in UAF, EA-BPMN, DoDAF, DoDAF 2.0, MODAF, NAF, and NAF 4.0 frameworks. Therefore, UAF 1.2 is no longer supported in this version. Moreover, the New DISR and UJTL library versions are now available.

General modeling capabilities introduce the Project History panel for Teamwork Cloud projects, providing quick access to commit messages and the project’s branch structure. For 3DEXPERIENCE platform projects, you can now create Collaborative Spaces specifically for standard profiles and libraries, ensuring they are always stored together in an accessible, shared location.

General modeling improvements include path-variable support in Excel/CSV Sync Options and Import dialogs, the deprecation of several legacy engineering sets, the introduction of a new Non-Profit Research license category, and expanded academic license options.

To download the latest version of the modeling tool, see Downloading installation files. For further information, check the product documentation.


UAF Features

Methods and Standards

Beginning with this version, the UAF 1.3 Plugin is available for production use. The UAF 1.3 Profile is fully supported in UAF, EA-BPMN, DoDAF, DoDAF 2.0, MODAF, NAF, and NAF 4.0 frameworks.

IMPORTANT! The UAF 1.2 Plugin is no longer supported starting with the 2026x version.


Projects created in earlier versions require the following migration before you can continue working with them:

UAF 1.3 Profile Support

Together with the UAF 1.3 Profile, the following changes are implemented to enable Mission Engineering modeling in the 2026x version:

Library Support

New DISR and UJTL library versions are now available:

  • UJTL (20250715)
  • DISR (20240606)

You can choose the library version when creating a new project. Learn more about using libraries >>>

UAF/UPDM Compliance Mode for BPMN2 projects

The “UPDM Profile for BPMN” is no longer available in this version. All of its stereotypes have been moved to the existing BPMN Customization Profile. In addition, a new UAF/UPDM compliance mode has been introduced for BPMN projects, allowing you to choose whether the compliant UAF/UPDM stereotypes (depending on the plugin) should be applied to BPMN elements.

Validation

  • The new correctness validation rules dedicated to checking if the client and supplier are correct have been introduced for the following relationships:
    • Opposes, Defines. New relationships, which were implemented with the UAF 1.3 Profile support.
    • Existing relationships: Phases, Compares To, Governed By, Maps To Goal, Owns Value, Creates, Enables, Evoked By, Presented By, Sequence
  • The new correctness validation rules were implemented to verify whether the classifiers are correct for the following elements:
    • Actual Mission Scenario. The classifier must be Mission Scenario or its specialization.
    • Actual Mission Vignette. The classifier must be Mission Vignette or its specialization.
  • The new correctness validation rule was implemented to verify whether the behavior is correct for the Mission Task Action. The behavior must be a Mission Task or its specialization.

Discontinued Products

The AutoStyler plugin is deprecated, with the intention of removing it with the next major version release, the 2028x version.

Other Enhancements

  • A new backwards compatibility feature allows UPDM 2.1 projects created in the 2026x version to be Saved As Older Version in 2024x compatible file format. This makes them directly compatible with the UPDM 2.1 plugin in 2024x, allowing you to open and work with these projects immediately in the 2024x version. This approach does not apply to the UAF 1.3 projects. Learn more >>>
  • The UAF Enterprise Architecture Framework is now renamed to EA-BPMN. The perspective and project creation template was already renamed in the 2024x version.
  • The «ActualDODAFProperties» stereotype will no longer be applied automatically after creating instances for «DODAFProperties». Moreover, the «DODAFProperties» stereotype is renamed to «UAFProperties».
  • In this version, the Strategic Actual Strategic Phase Taxonomy Table was renamed to the Strategic Actual Strategic Phase Table. Learn more >>>
  • A new UAF BoK Sample is now available. This sample is based on the UAF WOW! book.
  • This version includes new functionality that lets you select whether the Definition or Comment will serve as the Documentation for UAF elements.

Modeling and Infrastructure 

  • Path variables can now be used in the Excel/CSV Sync Options and Import dialogs. This feature provides greater sharing flexibility by allowing you to store file paths as named variables in your project, which can be easily adjusted on different machines, making it easier to collaborate across teams and environments. Learn more here >> and here >> 
  • Deprecated XML Schema, CORBA IDL, C++ and Java CE engineering sets. You can use the CATIA Software Producer plugin for code generation from Java and C++. 
  • Oracle DB and PostgreSQL drivers are no longer distributed with the modeling tool. Download and add the needed drivers according to the database type and version. Learn more >>
  • A new modeling tool license category, Non-Profit Research, has been introduced for Magic Systems of Systems Architect and Magic Cyber Systems Engineer modeling tools, as well as Magic Systems Cybersecurity Designer, Magic Model Analyst, Magic Systems EE Architect, and Magic Systems Safety Engineer plugins. Learn more >>
  • Academic licenses are now available for Magic Systems Cybersecurity Designer, Magic Systems EE Architect, and Magic Systems Safety Engineer plugins.

Back to top

Collaboration

Teamwork Cloud

The Project History Panel

In version 2026x, Teamwork Cloud introduces the Project History panel, which can be opened with just a few clicks. It saves time when reviewing commit messages or investigating the branch structure.


The Project History panel.

3DEXPERIENCE Platform

Collaborative Spaces for Standard Profiles

You can now create Collaborative Spaces specifically for standard profiles and libraries. This ensures profiles and libraries are always stored together in an accessible, shared space. It also prevents users from accidentally adding profiles to the spaces that others cannot access—for example, when creating a project, adding a project to the server, or migrating profiles.

Back to top

Documentation