Implementing "Typed By" Assignment in SysON Custom Creation Tools

[nlorit]

I want to know how a tool for creating an actor, for example, can be implemented inside SysON using the view model.

I followed the Obeo blog post on extending SysON for Arcadia. I successfully created a tool that generates a new PartUsage, but I haven't been able to figure out how to modify the 'typed by' field programmatically.

[AxelRICHARD]

Hello,
Thank you for using SysON.

If I understand correctly your need, you succeeded in creating a new PartUsage programmatically, and now you wonder how to type it with a PartDefinition right?

Lets say you want to produce the following model:

package MyPkg {
   part def A;
   part def B {
      part p1 : A;
   }
}

So you probably created your PartUsage with:

var p1 = SysmlFactory.eInstance().createPartUsage();

To type it with the PartDefinition A, you have to create a FeatureTyping element and then set the type and typedFeature properties of this FeatureTyping.

var featureTyping = SysmlFactory.eInstance().createFeatureTyping();
p1.getOwnedRelationship().add(featureTyping);
featureTyping.setType($PART_DEFINITION_A);
featureTyping.setTypedFeature(p1);

Best regards,

[nlorit]

Thanks for the reply, I want to know if this can be done inside the Sirius Web View Studio Low-Code approach ?

[AxelRICHARD]

Yes, with the low code approach, you can do the same, with "CreateInstance" (to create the FeatureTyping) and "SetValue" (to set the type and typedFeature properties of the FeatureTyping) elements inside your tool.

[nlorit]

OK i see so somthing like this :

with set type : Mylib::A or aql:Mylib::A ? (with your model example)
and set typedFeature : aql:newPartUsage

[AxelRICHARD]

set typedFeature : aql:newPartUsage

yes

set type : Mylib::A or aql:Mylib::A ? (with your model example)

no, you have to use the existing instance of a PartDefinition or any other compatible type. Either you have to use a SelectionDialogDescription to be able to select and existing element and then use this selected element in your "SetValue" or you must be able to navigate to the PartDefinition or any other compatible type from an accessible element in your context (self or newPartUsage), but it won't be easy because the sysml metamodel is complex (in my example if you start your navigation from newPartUsage you will have to navigate to its parent B then the parent of B, MyPkg and then from MyPkg get the member corresponding to A) and it will only work for this specific model construction. For the second approach you can use the "Query" view (on the right side of a project page on a small sysml example to build the query that will work in your case).

By the way, for the creation of the FeatureTyping in the CreateInstance don't forget to use ownedRelationship for the Reference Name property.

[nlorit]

Thanks a lot for your time and your help !!