creating connector using script

[MV]

Hi guys,

Is it possible to create connector using scripts. An example will help ....

TIA

[KP]

You need to call AddNew() on an element's Connectors collection. So something like:

Code: [Select]

dim conn as EA.Connector
set conn = source.Connectors.AddNew("Association","")
conn.Start_Object_ID = source.Object_ID
conn.End_Object_ID = target.Object_ID
conn.Update()
source.Connectors.Refresh()
My morning caffeine hasn't kicked in yet, so this could well be rubbish: Debugging is left as an exercise for the reader

[Aaron B]

Some corrections to KP's code  

Code: [Select]

dim source as EA.Element
dim target as EA.Element
dim conn as EA.Connector

' set source and target to reference valid Elements in your repository

' ClientID = source end, SupplierID = target end
' source end is already set based on the element that owns the Connectors collection.  Only need to set SupplierID.

set conn = source.Connectors.AddNew("", "Association")
conn.SupplierID = target.ElementID
conn.Update
source.Connectors.Refresh
target.Connectors.Refresh

[KP]

Some corrections to KP's code  

Wow, only 3 mistakes! Thanks

[MV]

Thank you guys...

[motivatedgorilla]

Is there a way to achieve the same result using JScript and SQL query especially when you have a single element that has a relationship with a 1000 others?

[qwerty]

Why would you want to use SQL? Creating a new connector is independent from the number of already existing connectors.

And yes: JScript will do analogously.

q.

[peigee]

The replies so far only mentioned the source and target elements (client and supplier id) for the new connector. How to specify the source and target role (attribute sourcerole and destrole in the repository table t_connect) for linking the operation FK and PK, if I want to add a connector for a new FK via java script? I could not find such properties available for the connector object. Here are the sample script I have been experimenting and found out SourceRole and DeskRole are invalid property for the connector:

--after added a new method for the FK operation record (and its parameters) and located the existing source and target element and the target PK operation name:

var Connectors as EA.Collection;
Connectors = theElement.Connectors;
var newConnector as EA.Connector;
newConnector=Connectors.AddNew("","Association");
newConnector.SupplierID=r_element.ElementID;
*newConnector.SourceRole=newMethod.Name;
*newConnector.DeskRole=c_r_pk;
newConnector.Update();
Connectors.Refresh();
target.Connectors.Refresh();

What are the correct properties I shall use to complete an FK constraint addition via Jscript?

[Geert Bellekens]

Check https://www.sparxsystems.com/enterprise_architect_user_guide/15.2/automation/connector2_2.html

Each connector has a ClientEnd and a SupplierEnd

Geert

[peigee]

Thank you Geert. I have tried your suggested two properties before by assigning the FK and PK method.name values (perhaps I should have used method.MethodID?). Anyhow after seeing another post suggesting property StyleEx, I got it working, as follows:

--after added a new method for the FK operation record (and its parameters) and located the existing source and target element and the target PK operation name:

         var Connectors as EA.Collection;
         Connectors = theElement.Connectors;
         var newConnector as EA.Connector;
         newConnector=Connectors.AddNew("","Association");
         newConnector.SupplierID=r_element.ElementID;
         newConnector.StyleEx = "FKINFO=SRC=" + newMethod.Name + ":DST=" + c_r_pkname + ":;";
         newConnector.Update();
         Connectors.Refresh();
         r_element.Connectors.Refresh();

[steen.jensen]

Wy all those refresh statement??

[qwerty]

Because the explanation in EAs help is sub-optimal and people just don't know why to use them. Doing no harm they plaster their code with refesh calls.

q.

[peigee]

The second refresh statement indeed isn't necessary. The first one is for the newly added connector to be navigated to by my subsequent code not listed here.

[qwerty]

Why navigating in the collection if you have the created connector right at hand? You just created it. Ah, well. Never mind.

q.

[peigee]

Geerty, a good reminder! Just realised while setting StyleEx had created the visual connector in a diagram, it hadn't actually populated values in SourceRole and DestRole of t_connector table, therefore, the FK (Association) connector is still not created correctly.
However your suggested ClientEnd and SuppliedEnd are two readonly properties and wouldn't accept newMethod.MethodID or anything else related to the FK/PK operation records at all.
I am now back to square one!