Release Notes 5.1.0
All fixed issues can be retrieved here : Fixed issues
Physical links and functional exchanges are colored as black if there are multiple physical paths or functional chains passing through. To help users better distinguish which physical paths or functional chains are involving in a physical link or a functional exchange, a pie icon with colors of physical paths/functional chains is displayed by default on the beginning and on the end of the physical link/functional exchange as shown in the following image.
Users can also choose to display the name of involving physical paths/functional chains next to the pie icon
Besides, filters are also provided to hide the pie icon or the label of involving physical paths/functional chains according to user's need
By default, only pies are displayed on new created diagrams (not labels).
Note: model migration of existing diagrams hides pies and related labels.
Physical paths can be composed in a way that there are many branches in the same physical path. For example, in the below image, if the physical path begins with PL 1, at PC 2 it is separated into 2 branches, either it can go to PC 3 via PL 2 or it can go to PC 4 via PL 3.
There is no orientation in physical path, in other words, depending on which physical component the physical path begins with that we have a different way to interpret the physical path. For example, for the above image, we can also understand that the path begins with PC 3, via PL 2 it reaches PC 2 and then dispatches into PC 1 and PC 4 via PL 1 and PL 3 accordingly. Therefore, when displaying a physical path in diagrams, in case of having different ways to track a physical path, we illustrate all of them.
For example, in the above image, inside PC 2 there are 3 internal links that form the physical path. They allow the continuity of the physical path regardless of whatever way the physical path is interpreted.
Internal link filters
Two filters are provided to hide physical path internal links and functional chain internal links. For the same above example, if the "Hide Physical Path Internal Links" filter is applied, internal links related to the physical path "Physical Path 1" will be hidden in the diagram.
By default, these Physical Path internal links are displayed.
Note: model migration of existing diagrams does not hide this internal links too.
Contextual menus ("Delete", "Copy As", Diagram access) available in Semantic Browser, even in Interpreter view for better data exploitation
New group "Copy As" menu gathering customized copy facilities ("Copy Qualified Name", "Copy as Description Link" and "Copy as Text").
Add menu on Semantic Browser and Interpreter views
Some Capella contextual menus ("Delete", "Copy As", Diagram access, Show In) available in Semantic Browser, even in Interpreter view for better data exploration and navigation.
Semantic Browser:
- you can analyze, validate and delete some model elements, etc...
- You can also create new diagrams or existing one too.
Interpreter View
- You can run a query, and then, clean or analyse/navigate into your model
Example
DWF_SM_16 (new , severity: error): This rule ensures that State Machines always have regions without mixed States/Modes.
DWF_SM_06 (modified + quickfix, severity: error): This rule ensures that in the same hierarchy do not exist mixed States/Modes.
Two new validation rules were introduced, in order to achieve a more consistent behavior when working with constraints. Each rule has a corresponding
quickfix as a way to fix the models containing constraints not properly assigned or located. There is no need to migrate the projects from previous versions,
as these validation rules and quickfixes help with correcting the existing constraint assignment and location issues.
DWF_D_58 (new + quickfix, severity: warning): In monopart mode, this rule ensures that ConstrainedElements Value is not Part/PartDeploymentLink.
DWF_D_59 (new + quickfix, severity: warning):
In monopart mode : This rule ensures that a constraint is not stored under and doesn't have ConstrainedElements values as a Part/PartDeploymentLink. Exception : In EPBS Layer constraint's can be stored under Part
In multipart mode : This rule ensures that a constraint is not stored under PartDeploymentlink. Exception : If first ConstraintElements value is container PartDeploymentlink or empty ConstraintElements value
_Diagram palette tools managing Constraints are also improved to better locate new constraints for components. _
When transition triggers are made with catching functional exchanges or exchange items they shall be transited in the next Capella layer.
When a function is inserted inside entry/exit/do on the n Capella layer it shall be transited in the n+1 layer.
Transition of StateMachine will transite Triggers, Effects from layer N to N+1.
Transition of StateMachine will transite Entry, Do activity and Exit from layer N to N+1.
Preference updated with tooltip
Added new validation rule to detect mixing of deployment and containment.
DWF_DC_44 (new + quickfix, severity: warning): This rule ensures that a Physical Component of nature NODE or BEHAVIOUR is not contained and deployed inside the same parent Component..
If a component Node is deployed and also contained, it will not be displayed as 'rounded/deployed' if there is no other Node component deployed.
If a component Behavior is deployed and also contained, it will not be displayed as 'rounded/deployed' if there is no other Behavior component deployed.
In any case, the session must be closed before the conflict resolving step. This is because during this step, the model contains elements in conflict state, further actions on the session would make the model become completely corrupted. There are two new mechanisms implemented in Capella to make sure that the session is closed during this step:
- When a model is in conflict state, the session cannot be opened, a popup is displayed to inform users about resources being in conflict.
- An already opened session will automatically be closed if a concerning resource enters the conflict state (e.g. following a Git action).
- Changelog
- Metamodel changes
- API changes (Capella - Sirius - Diffmerge)
- Official Website
- Download
- Release-Notes 7.0.0 (upcoming version)
- Release-Notes-6.1.0 (current version)
- Release-Notes-6.0.0