Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - MaXyM

Pages: [1]
Automation Interface, Add-Ins and Tools / DiagramLink and Connectors
« on: December 05, 2017, 01:48:31 am »
Hello guys
I spent half a day searching for information but at the end I have to ask for it.
I need to change color of DiagramLink in relation to labels. But:

1. don't know how to get labels directly from DiagramLink
2. don't know how to find Connector which is represented by DiagramLink

BTW I found funny thing trying to set LineColor (attribute of DiagramLink). It seems to be BGR instead of RGB. So 255 is red (hex 00 00 FF), respectively blue is 16711680 (hex FF 00 00).

with regards

General Board / Dynamic list of dependencies
« on: September 21, 2017, 07:37:00 pm »
Let's say I have an application component which have to communicate with all (dozens) db servers in my network. Components which represent db servers are located in packages.
I would like to save manual work (which is error prone) of adding connections while adding new servers
On the other hand I need to maintain traceability between the component and servers.

I could imagine some element which generates list of elements based on SQL. Something like ModelView but it doesn't provide traceability. Could you please suggest me some way? Maybe I'm trying to manage it from wrong end?

Bugs and Issues / Values of attributes always truncated
« on: September 21, 2017, 01:32:29 am »
Hello guys.
Please look at image below.
You can see 2 elements. GenericServer Node element on the left side and it's instance on the right.
Both are node type elements without stereotype.

Attribute values are truncated. Doesn't matter it is a classifier or an instance.
Please note that settings available in Features and Compartment Visibility simply doesn't work in this case, whatever I set.

On the other hand, RunState values are not truncated. Unfortunately Feature and Compartment settings are not applied to this area also. Longer strings protrudes out of the shape.

Do you have any idea what happens and how to cope with that?
Worth to say I would like to see attributes not truncated, or truncated only if they really don't fit the shape.
Also since duplicated information is waste of space I would like to hide one or another data (RunState ones or inherited from classifier). I know I can hide RunState, but then I can see truncated values. I can hide Classifier attributes, and yes, this is how I'm doing it right now, but this way I cannot see datatypes as well as attributes which aren't set in RunState (incl attributes set in classifier only)


Recently I was trying to set aggregation connectors between elements using scripting. Durring the process I realized I cannot set direction as well as Subtype (weak vs strong). While debugging my code I separated behaviour I want to describe below. I'm curious it's a bug or I'm missing something down the road.

There is a test case.

1. Create simple diagram with 2 class elements: Class1 and Class2.
2. Create aggregation by dragging connector from Class2 to Class1 and selecting "Composition to Part". Name it whatever you want. The result should look like the picture:

3. Run following script, entering GUIDs of Class2 and the Diagram, before you run:
Code: [Select]
!INC Local Scripts.EAConstants-JScript

 * Script Name:
 * Author:
 * Purpose:
 * Date:
function main()
var el as EA.Element;
var diagram as EA.Diagram;

el =  Repository.GetElementByGuid('GUID of Clas2 element');
diagram = Repository.GetDiagramByGuid('GUID of diagram');

for (var i=0; i<el.Connectors.Count; i++)
Session.Output(el.Connectors.GetAt(i).Name );
el.Connectors.GetAt(i).Update(); // this line changes direction




4. The result on my end looks like on picture bellow. The direction of aggregation is changed from Source->Destination to Destination->Source. Debug console confirms it also

Also I don't understand why position of element Class2 has been changed by reloading diagram.
What am I doing wrong?

General Board / Communication Path not traceable
« on: August 19, 2017, 11:23:13 pm »
I was looking everywhere to solve my question but I haven't succeeded.
EA documentation says: Communication Path is a specialization of Association

Unfortunatelly Comunication Path seems not to be traceable: no relation shown in Traceability window.
After changing its type to Association it turns traceable.

Is it a feature or bug? Or I missed something?

EA 13.5.1351 Corp Edition

Thanx in advance

Bugs and Issues / Importing database schemas into subpackages
« on: June 15, 2017, 09:49:36 pm »
Hello everybody.
Recently while gathering new experience of importing database EA's feature, I found - I believe - a bug. I decided to ask for that on this forum before I report it to official support.

EA imports all db objects into packages named after object types. This way all tables are imported into Tables package. Until we have tables from single db schema and we are ok these are located in single package - everything works as expected. But our database contains hundreds of tables divided into few dozens of schemas. Imagine all those tables in Project browser tree, in single package sorted by table name... In fact impossible to manage.

Issue 1: In project browser, an item which represents database table is not prefixed by schema name (like available on diagram). This way it's very hard to find all tables of particular schema in Project browser. It affects user experience significantly. Maybe there is some feature/switch to enables db schema names in Browser. I haven't found one.

Issue 2: while already imported tables are moved to subpackages (for example Tables/MySchema/) and we proceeding with importing another tables, EA is not able to create relationship between new tables and already imported ones. I could had have even consider it as a feature (even if not handy, though) but I've found one thing which proves it must be a bug. In DatabaseBuilder, function "Show differences" shows missing relationships and moreover, it gives option to sync it with db. Unfortunately attempt of import does nothing at all. I checked out, that moving parent table (of relationship) from subpackage to Tables package, makes sync with db working again. So import/sync works but result depends on where table objects are located in project tree.

Do you have some experience with RE of databases? Can you confirm this issue appear to all DBMS (I found it while working with postgresql)?

With regards.

Pages: [1]