Publication for Capella 2023.3.0 (2023-03-03)
The main novelty of this version is the capability to manage traceability links directly within Capella, while keeping these links synchronized with the Publication server and the connected third-party repositories.
Managing Traceability in Capella
This new capability makes it possible for System Engineers to easily create traceability links between their model elements and third-party artifacts such as requirements, tests cases, or change requests.
The System Engineer can create such links simply by dragging and dropping URLs of artifacts from their website into Capella.
The drag and drop can take place in a diagram, or in the model tree. A link gets created between the dropped artifact and the model element on which it was dropped.
It is possible to configure different types of links to be created between different types of model elements and different types of artifacts. If several types of link are configured as being allowed between the dropped artifact and the model element, then the user must chose the one they want to create.
These links are available within the Capella model, but they also get to the Publication server each time the model is published. These links can also be created or deleted on the Publication for Capella website, and System Engineers can synchronize their Capella models to retrieve these link changes in the Capella model.
Please refer to the User Guide for a complete description of this novelty and the related features.
Other Changes
- Models must be saved before publishing.
- A pop-up will be displayed if the user tries to publish an unsaved model to make it possible to save the model and proceed, or cancel the publish.
- Models are automatically saved after publishing.
- Publishing a model will modify some technical information in the model. For this reason, the model is saved automatically after publishing, whereas it appeared as dirty in previous releases.
Bug Fixes
- The display of the rich text documentation is now correct.
- There was a bug in previous versions that caused the rich text to be incorrectly formatted after the 1st link in the documentation.
- The version number displayed in the home page footer is now correct;
- In version 2022.11.0, the footer was incorrect and stated 2022.9.0.