Library PVMT and REC/RPL good/bad practices [message #1826441] |
Fri, 24 April 2020 17:21  |
Eclipse User |
|
|
|
First I share the bad practice:
In a library I have applied a PV Domain on Functions... Let's say function kind (datamodel/simulation/communication)...
I created REC.... and RPL in a project using the Lib.. The RPL has property values applied. But I could not manipulate the values of the properties applied.
First bad idea: I imported the Domain in the project to manipulate the properties but..... I guess the import mechanism recreated EObject of the corresponding property values when importing the Domain...
Second bad idea: for another reason, I removed the properties from the library by detaching model. WHen I tried to remove the properties from the elements in the project using the lib, it did not worked and showed invalid EReference (to the Domain in the Library, which was not existing anymore)..
COnclusion: It's a bad idea, when using REC/RPL from library in conjunction with PVMT to import the Domain in the project using the lib.
Questions: Is there a good practice ?
Question 2: in Capella user manual, it is said that property values are not handled properly by transition operations, is it confirmed ? How can I use property values at one level of analysis, and transition them to the others properly.
Thank you for any advice.
[Updated on: Sat, 25 April 2020 05:05] by Moderator
|
|
|
|
|
|
Re: Library PVMT and REC/RPL good/bad practices [message #1826643 is a reply to message #1826463] |
Tue, 28 April 2020 03:25  |
Eclipse User |
|
|
|
Hello Cedric,
PVMT does not yet support transition between perspectives (SA to LA for example), system to sub-system transition, or REC / RPL between library and project.
It's because even if the Property Values are transferred, the link with the PV definition is lost in the transfer.
This problem has already been identified and would need additional development in order to fully cover all use cases.
|
|
|
Powered by
FUDForum. Page generated in 0.04071 seconds