Functional Chains can be assembled and reused in order to express more complex scenarios.

• Functional chains can be assembled through the means of a Functional Exchange. This implies that each Functional Chain contains an Involvement Function that can be used as source and target for an Involvement Link. The Involvement Functions are not necessarily required to be starting or ending in their Functional Chain to be connected by the Involvement Link.
• Functional chains can be assembled through the means of a common Function. This implies that each Functional Chain contains a Involvement Function that references the same Function.

A example of two Functional Chains assembled through the means of the Functional Exchange 2.

A example of two Functional Chains assembled through the means of the common System Function 3. Please note that the source and target of the connecting Involvement Link are two Involvement Functions that both reference System Function 3.

Involved Functional Chains can be folded in order to hide their involvements.

In order to do so, you must first select the the region of the Functional chain (this displays a button in the top left corner), and then the fold button must be pressed as illustrated bellow.

Once the Functional Chain is folded, all the displayed Involvement Links and Sequence Links having as source or target the now hidden involvements will be displayed directly on the container Functional Chain. Please note how the Functional Exchange 2 edge has now as source the Functional Chain 1 instead of the previous System Function 2.

Functional Chains can be involved in other Functional Chains, and thus producing Composite Functional Chains.

Please note how Functional Chain 1 and Functional Chain 2 are involved in Level2 which itself is involved in another Functional Chain.

Functional Chain Description diagrams can be combined with Sequence Links and Control nodes in order to enrich them with additional sequencing information.

• Sequence Links express precedence between the execution of represented Functions.
• A Sequence Link indicates that in the context of this Functional Chain, the source Function should operate before the target Function. More precisely, the target Function cannot produce its expected outputs before receiving the inputs produced by the source Function.
• A Sequence Link has an optional triggering condition and can be combined with Control Nodes (OR, AND, ITERATE).

The sequencing information can also be displayed in xAB diagrams. By default the associated elements are hidden, but they can be displayed by unchecking the Hide Sequencing Information filter.

"Show in Diagram Editor" (F10) manages:

• multiple selection and navigation to related multiple diagram elements
• selection the whole category model elements (ports, exchanges) in the diagram
• multiple diagram selection of the same mappying

New command Functional Chain/Operational Process to Functional Scenario/Operational Activity Scenario Initialization is available on Functional Chain/Operational Process.

Notes:

• management of referenced Functional chains and complex use cases (i.e assembled chains and multiple functional chain involvement of same Function/Exchange) is fixed too.
• order of sequence messages might be reordered based on FCD/OPCD sequencing information, no implemented yet.

New preference group in Transition/Generation page to control the creation of interaction during initialization (with or without return branch)

• Cut (Ctrl+x) is disabled for diagram model elements, only Copy/Paste is supported

• Copying diagram elements and pasting them is a different diagram kind is disabled (e.g. copy diagram model elements in CDB, pasted in xAB diagrams) :

• The contextual menu Edit/Copy/Paste on diagram only works on elements of type note/text

• A precondition is checked for the Capella Copy/Paste (Ctrl + C / Ctrl + V) command on diagram elements

• The Copy/Paste operation takes into account the zoom factor (in/out) of the diagram in order to set pasted elements at the right location.

1. **New live validation rule DWF_D_55** [Live], **disabled by default**, for cycle detection during model edition.
   1. The new rule **can be enabled** through Eclipse preferences "Model Validation"

      The new rule, if enabled, is smart enough to detect cycle coming from the current user edition and avoid it (e.g to avoid association creation through diagram CDB in case of a new cycle created, then the command is roll-backed)

2. Enhancement of legacy validation rule **I_34**: based on same **Tarjan algorithm as** **DWF_D_55 [Live]**, enabled **on "System Engineering"** to detect all Data pkg cycles, with a QuickFix to get involved model elements.

Optimized project renaming process and related Eclipse Help clarified:

• Renaming Capella project will rename also the Project and "System Engineering" model elements
• No need to close the session to rename a project
• When the renamed project contains images which are referenced in the diagrams, the paths to those images is updated during the rename of the projects. Both Capella model and images should reside under the same project.

• New section "Inherited Exchanged" section displays all the ExchangeItems of all Generalized Interfaces.
• Display in separate sections the ExchangeItems of the selected interface under the "Exchange Items".
• Display all the inherited interfaces under the "Generalized Elements" section & Display all the inheriting interfaces under the "Generalizing Elements" section.
• info: The "Generalized Elements" and "Generalizing Elements" sections are now available for similar Generalization links.

• "Roles" of selected association is displayed in Current Element Category.

• Display "Type" of ExchangeItemElement and Collection.

• Display "Related Function" or "Related State" on selection of State Fragment in Scenario Diagram.

• Display "Allocating" and "Allocated" information of FunctionPort, ComponentPort and PhysicalPort in semantic browser.

• Display "Included", "Extended", "Involved Actors", "Involving Actors", "Exploited Capabilities" and "Exploiting Missions" in semantic browser.

• Display computed Active Elements (Functions, Functional Chains, Capabilities) in all parent States/Modes hierarchy.

'Suffixed' feature updatable in property view:

In the property view of a REC's CatalogElementLink, it is now possible to make suffixable or not the target element without using the "update REC" window:

But only on REC's CatalogElementLink, it is grayed for RPL's CatalogElementLink and have an information tooltip to explain that you have to update the REC link:

"Naming differences on Suffixed Elements" filter:

The "Naming differences on Suffixed Elements" filter is now not active by default (Normal column):

So now, all naming updates of suffixed elements appear during a REC/RPL update if RPL elements don't have the name of the corresponding REC element + the suffix.

Propagation of 'suffixed' feature from a REC to its RPL elements:

In previous version, if a REC have a RPL element, if you changed the 'suffixed' feature of the REC and update the RPL from this REC, the corresponding 'suffixed' feature of the RPL was also updated.

Now, updates on 'suffixed' feature is not propagated from a REC to its RPL elements.

invalid Diagram in gray in Project Explorer to show descriptors with no target diagram or diagram with no root model element ##

Lost diagrams (i.e descriptors/diagram references with no target diagram or diagram with no root model element) are displayed in Capella Project Explorer as invalid and in gray.

You can also remove these invalid representations using the "delete" command through Project Explorer.

• DWF_DF_05 (updated): check that all the functions involved in Functional Chain are also active in modes and states as Function Chain.
• DWF_DC_35 (new): function is not available in at least one Mode/State allocated to a functional chain in which the function is involved.

* DWF_CA_07 (new + quick fix, severity: warning): Capability check that all the involved actors are present in at least one operational process or functional chain or scenario related to the capabilities it participates. * DWF_CA_08 (new + quick fix, severity: warning): Capability check if the current Capability has actors that are not involved but are present in at least one operational process or functional chain or scenario related to the capability. * DWF_CA_09 (new + quick fix, severity: warning): Capability check if the current capability has related operational processes or functional chains that are not involved with the capability. * DCOV_08 (updated): when validating the involved actors the actors, show all the capabilities to which the actor is not involved (not only the first matched capability as it was before). * DCOM_05 (updated + quick fix, severity: warning): add Function Scenario validation and added quick fix to create actor-capability involvements.

• DWF_D_55 (new + quick fix, severity: error): check that Enumeration Literal element is typed by its parent and quick fix to fix it.

• I_40 and I_26 (new + quick fix, severity: warning): detects duplicate Involvement links / relationships (links of the same type and with the same Source and Target elements). The quick fix will delete all duplicate links and will leave one link.

• DCON_04 (new + quickfix, severity: warning): check if a RPL/REC_RPL has no more REC.
• DCON_05 (new + quickfix, severity: warning): check if a REC has no RPL (is not used in a RPL).
• DCON_06 (new + quickfix, severity: warning): check if a REC_RPL has no RPL(is not used in a RPL).

• DWF_DF_15 (new, severity: warning): check if SequenceLinks between the referenced Involvement Functions/OperationalActivities have no Involvement Links referencing them.
• DWF_DF_16 (new + quickfix, severity: warning): check if a SequenceLink has empty condition.
• DWF_DF_17 (new, severity: warning): check if a SequenceLink between two addiacent Control Nodes has no FunctionalChainInvolvementFunction.
• DWF_DF_18 (new + quickfix, severity: warning): check if a SequenceLink has no associated FunctionalChainInvolvementLinks.
• DWF_DF_19 (new + quickfix, severity: error): check if a SequenceLink has inconsistent associated FunctionalChainInvolvementLinks.
• DWF_DF_20 (new + quickfix, severity: error): check if a SequenceLink between the referenced Involvement Functions/OperationalActivities is in opposite direction to Involvement Links referencing them.
• DWF_DF_21 (new, severity: warning): check if a ControlNode is used having 2 IN links and 1 OUT link or 2 OUT links and 1 IN link.

Added Tools for Contextual Capability Realization Involvement ([CRI]) Diagrams:

• Create: Actor, Component, Capability Realization, Actor Involvement, Component Involvement
• Insert: Actor, Component, Capability Realization, Relationships

Added Relationships ToolUpgrade on Contextual (Detailed, External, Internal) Interface Diagrams ([CDI], [CEI], [CII])

The goal is to provide a safe way to transfer model elements from one project/library to another referenced library through a dedicated Capella view "Transfer View".

See related embedded documentation in Help Content Capella Guide\User Manual\User Interface\Transfer View.

It detects **illegal backreferences and assistance to include mandatory model elements to move too. **

** **

It provide Semantic Validation of the destination model for model consistency (no backreferences or invalid Arcadia references):

• New validation rule I_38 to enable manually through preferences to detect any referencing problems (semantic rules implemented by Capella Properties): such problems should be resolved before trying to execute a move.
• In case of issues, User can :

1. 1. either "Force move" and do the correction in library with the help of validation rules (recommend to use I_38 Validation rule)..
   2. or "Cancel move" and correct the semantic element move move before applying move action.

Note: Orchestra URI migration is still out-of-scope for the moment: you might have some lost Orchestra URI for model elements moved if you are in an Orchestra context

Related delegations of a displayed category are displayed as belonging to this category (only the first level).

In the scenario diagrams, it is possible to hold the key strokes CTRL + SHIFT and drag the mouse from bottom to top in order to remove useless vertical blank spaces.

Note: the opposite (from top to bottom) add vertical blank spaces, feature already available from 1.3.0.

With 1.3.1, it is also possible to add or remove space through this shortcut not only on the scenario background, for instance on diagram element (e.g big fragment). It does not work a non Sirius graphical elements (e.g. Note, Text elements etc...) * *

• In xAB diagram, the refresh operation is about 60% faster
• In xDFB diagram, the Switching to category tool is improved
• In Capella Wizards/Dialogs, the displaying model elements in tree is improved
• In xAB diagram, Select all elements tool is about 25% faster
• In Semantic Browser view, queries are computed only when the view is focused
• In Properties View view, if many model elements are modified the refresh operation happens only once
• In Console view, technical logs are disabled by default
• On model deletion, there is now no multiple focus selection in Project Explorer