|
Re: Subcontainer issue [message #1799895 is a reply to message #1799868] |
Mon, 17 December 2018 08:07 |
|
Hi,
I think you should add the participant mapping as extra-mapping as you will create the participant by click on the title area of the Protocol or on an other Participant element.
The, in the change contexte var:container, you should add a if() and check the type of the container: if it is a participant, change the context to the current protocol (aql:container.eContainer() I assume) .
For the name edition, the direct edit should work in the same way than other mappings.
It seems that you put 3 participants node mappings: I think you should have only one and use the semantic candidates expression to retrieve all candidates from your model. This could also explain why the elements you want to create do not appear on the diagram (if you do one mapping for each of the three first elements, then the other ones will not be displayed)
Regards,
Maxime Porhel - Obeo
Need training or professional services for Sirius?
http://www.obeodesigner.com/sirius
|
|
|
Re: Subcontainer issue [message #1799904 is a reply to message #1799895] |
Mon, 17 December 2018 09:10 |
PETROS SOURSOS Messages: 4 Registered: September 2018 |
Junior Member |
|
|
Thank you for your response.
It worked by adding to the Container Creation, Change Context feature: eContainer and then Change Context var: container ->set participants.
The 3 participants node mappings are used just to display the same Participant's, 3 attributes with Semantic Candidates Expression: var.self and no extra objects. It seems to work this way.
Best,
[Updated on: Mon, 17 December 2018 09:11] Report message to a moderator
|
|
|
Powered by
FUDForum. Page generated in 0.03062 seconds