Team for Capella - Releases

Team for Capella 7.0.1 (2025-04-07)

Compatibility: Capella 7.0.1

What's new

• Compatibility with Capella 7.0.1
• UX enhancements
  • The Semantic Criteria category has been added in the Filters and Customization dialog opened from the Diff/Merge editor when comparing two models with Compare with > Compare Each others.
  • The Semantic Browser now retrieves the impacted diagrams for newly created semantic objects, ie. the model elements created in a connected project which has not been saved since their creation (those objects are not known yet for the server nor for the other users).
  • The Semantic Browser refresh computation of referenced elements has been reworked for elements of connected projects. Computation is now done in less than 1s for some projects which used to encounter a 1min freeze on selection change.
  • The refresh of frozen diagram, ie. diagrams which were _locked by other_ before reception of remote changes, has been reworked to avoid interfaces freezes occurring in some situations on xAB, xDFB diagrams having functional chains, physical paths or physical links.
• Packaging, installation and deployment
  
  • The default repository's data source is now named repoCapella instead of capella to match its repository name, ensure naming consistency and ease readability.
  • In multi-user configuration with shared Capella installation folder, it is now possible to keep the registered repositories list in the shared capella/configuration folder.
  • Scheduler
    • The Database - Restore job is now able to restore dynamic repositories and/or a single repository at a time.
    • A new option has been added to the Repository - Start  job to allow the reinitalization of a repository without having to restart the server nor to access the files.
    • URLs of Jenkins plugins have been replaced in installation scripts in order to avoid redirect errors during installation on Linux.
• Server changes
  • A new option has been added to the Start repository REST API to allow the reinitalization of a repository without having to restart the server nor to access the files.
  • Two new OSGI commands revisionCacheInfo and revisionCacheCleanup are available to manage the internal revisions cache. They can be called on the OSGI console or from the REST API.
  • Loggers have been added to log actions that are processed such as users opening/closing a session, committing changes or actions on repositories through the REST API (creating/deleting users/projects/repositories...).
  • The OpenID Connect authentication is now officially compatible with Keycloak.
  • The OpenID Connect authenticator has been reworked to improve the token validation and allow the customization of the authentication request sent to the identity provider and the user registration capabilities.
  • Embedded Swagger UI has been updated from 5.11.2 (2024-01-29) to 5.20.1 (2025-03-10).
• Tools
• A new CLI application is available to create a connected projects. connect.bat/connect.sh scripts have been added to the TeamForCapella/tools folder.

More details can be found in the documentation.

Fixed Issues

This version also introduces several fixes:

• Import wizard now correctly sets the Library nature if the imported project is a Library.
• Export wizard now better handles several use cases mixing multi-selection, project names containing whitespaces, libraries. Better guards and error messages have been added to report Merge Strategy known unsupported cases.
• Import/export wizard usage no more forbid later activation of durable locks for a given Capella workspace.
• The activation of the Next button of Import/Export/Connect wizards is now based on the result of the Test Connection button.
  • OpendID Connect logout and authentication cancel after a first successful authentication no more lead to project opening.
• License Server - Run job console is no more spammed by Jetty debug logs.
• Exporter/Importer/Connect/Credentials CLI application better handle the -help, httpHost, -connectionType arguments.
• ...

 Note: Windows 10 users: Windows 10 Defender significantly slows down Eclipse, reason being Windows 10 Defender scanning the JAR files. The problem has been reported to Microsoft here. Until then, a workaround to this problem is to add Eclipse root directory to Windows 10 Defender's exclusion list, detailed steps are shared here. This is not just an Eclipse issue on Windows 10.