ProxyConnectors - where to store?

[Paolo F Cantoni]

We have grouped all our elements by metatype into specific branches of our repository.  We have automation to move elements around between folders when EA or our users don't put them where we need them.

EA now has t_object entries of type ProxyConnector (actually ConnectorProxy).  These are related to the end of a relationship that is NOT an element.  That is for relationships from relationships to elements and relationships between relationships.

We have folders for those items that don't end up in the browser and we manage those in a similar way behind the scenes.

My question is, where should we place these Connector Proxies.  They are placed somewhat arbitrarily as far as we can make out.  We suspect we run the risk that if we purge a folder that doesn't appear to have any objects within it we will inadvertently purge any ProxyConnectors.

Should we place them in the same folder branch as the origin object of the relationship or with the destination object of the applicable relationship?  Does it matter?

Paolo

[Mauricio Moya (Arquesoft)]

I guess, as it happens always, these proxy elements are located in the same package of the diagram they are created in. Every time you create a new element (a new row in t_object table) in a diagram, its parent package is the same as the diagram parent package.

So, my suggestion is: create a locked package (in order to avoid user deletion), and via your automation relocate the proxy elements as children of this package. If you don't delete the package, the elements will remain in the model.

[Paolo F Cantoni]

I guess, as it happens always, these proxy elements are located in the same package of the diagram they are created in. Every time you create a new element (a new row in t_object table) in a diagram, its parent package is the same as the diagram parent package.

So, my suggestion is: create a locked package (in order to avoid user deletion) and via your automation relocate the proxy elements as children of this package. If you don't delete the package, the elements will remain in the model.

That does seem to be the case (where EA seems to create them).  Are you suggesting we have ONE package for the entire repository?  That could work. 

Paolo