Bug 521996 - Associated elements are not matched by preconditions
Summary: Associated elements are not matched by preconditions
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Properties (show other bugs)
Version: 4.1.1   Edit
Hardware: PC Windows NT
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2017-09-07 09:40 EDT by William Piers CLA
Modified: 2017-10-17 09:20 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description William Piers CLA 2017-09-07 09:40:37 EDT
Context: 
* a diagram mapping (on a target A) also refers to associated elements (B)
* a property page/section P1 is declared for A, with a precondition matching A's type (by checking its features for instance)
* a property page/section P2 is declared for B, with a precondition matching B's type

When clicking on a representation element which refers to A & B, in the property view two pages are added : 
* one for A with P1.title, and showing P1.section
* one for B with P2.title but showing nothing instead of P2.section

Two workarounds are possible:
* use Domain Classes instead of preconditions in pages/sections. This can be verbose as preconditions are useful to factorize the properties declarations
* if P1 & P2 have the same intent, declare only P with no precondition to separate As from Bs  but a dynamic mapping to generate the fields as needed
Comment 1 Maxime Porhel CLA 2017-10-17 09:19:35 EDT
William, could you provide a sample VSM to directly show your point. 

And could your expected result/correction/behavior ?
Comment 2 Maxime Porhel CLA 2017-10-17 09:20:05 EDT
And could give more hints about your expected result/correction/behavior ?