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 - PeterHeintz

Pages: 1 2 [3] 4 5 ... 9
When defining queries of diagrams with the Query Builder, each row of the returned results shows the right diagram type icon and double click to a row opens the diagram.

When you do the same with SQL and using t_diagram.ea_guid as CLASSGUID and t_diagram.Diagram_type as CLASSTYPE the wrong icon is shown and double click does not work. Double click starts opening the right diagram after a “Find in Project Browser” is done row per row.

Further information:,39165.0.html

General Board / Another question about SQL queries of diagrams
« on: January 26, 2018, 01:46:46 am »
I want to have my query result clickable so that I can easy move to the diagram.

This works for queries created with the query builder. But what fields I have to alias with CLASSGUID and CLASSTYP when I do pure SQL on t_diagram?

General Board / EA Repository Table; How to get diagram types?
« on: January 25, 2018, 11:20:21 pm »
Up to now my diagram queries had been simple enough to use the query builder.

But now I need sql and I want to filter to concrete diagram types like BDD or IBD.

The t_diagram table has a Diagram_Type field but only containing abstract types like Logical, Package,… but not the concrete once.

T_diagramtypes is also not helpful, so I tried to use the magic “description” field in t_xref. This field contains some diagram field information but I do not know how to connect to.

Does anyone know in which field and table the concrete diagram types are stored and how this table is connected to t_diagram.
Is it t_diagram->t_object->t_xref?

I have created some search queries (located in My Searches) and I have some Views in a View Folder (let’s say MyViews) pointing to searches in My Searches.
Once I published and import a MDG which contains My Searches and MyViews in another project, I find the punished searches under a search container with name let’s say is “My MDG” and the "views" whithin a top level Model Views folder “My MDG”.

However the search folders within my imported "Model Views" still point to “My Searches” rather than to “My MDG” searches.

Trying out the trick to import the MDG to the source repository of the MDG to point to “My MDG” searches before publishing (what I do with success in some other scenarios) does not work here for whatever reason.

Any idea how to solve that with MDG?

Bugs and Issues / RTF Template Selectors based on package stereotypes
« on: October 24, 2017, 09:14:55 pm »
Does anyone know if this should/is work.

Package:review session:KB-SfS ESC ReviewSessionPackages
Package::KB-SfS ESC Packages

Currently I assume that this is just another issue, where package elements are constraint without reasons.

Bugs and Issues / Case Sensitive Problem with Searches
« on: October 19, 2017, 10:54:29 pm »
I realized the problem by doing the following:

I had a search let say with name My_search and I wanted to have MY_search
So I copied My_search and named the copy MY_search
However afterwards I found only MY_search in the list when trying to delete My_search.
When trying to assign a search to a Model View I found both
After returning to Model Search, selecting MY_search and pressing delete, My_search was deleted but MY_search was still there.

Well finally what I wanted to achieve at the end, but not what I sad EA to do.

Bugs and Issues / Test, Issue, Defect,… Requirement dependencies
« on: October 18, 2017, 09:29:06 pm »
Test, Issue, Defect, Requirement are some EA build in elements.

The major difference in comparison to other stuff like classes is that you can set a Type rather than a Stereotype when opening the property dialog. However the type is somehow a stereotype.  :-\  So far so good.

However there is some stereotype dependency looking strange to me.
In my MDG I have define some stereotyped requirements and when I create a requirement I can select one of those stereotypes as type of my requirement. Apart of thinking why it is called type and not stereotype it is good for me.

However, when I create other stuff like Defect, Issue I see the same Types/Stereotypes I have created for requirements only.

So it seems to me that Test, Issue, Defect is regarded as a kind of Requirement by EA.
What is the sense of that? Any idea?
From my perspective it is just nonsense!

When you define a model search you are able to return an alias ‘name’ which could be a ‘concat’ of several strings. Especially for unnamed elements, one can add e.g. type/classifiers to that name to provide some context.
Unfortunately the relationship matrix uses the real name of the elements and not was is returned by the model search. This makes the relationship matrix for unnamed elements useless.
So please provide a way that rows and columns can use data returned from the model search to be displayed.

Referring to,36071.msg232266.html#msg232266

I think that the Matrix Specification Artifact not allowing to use Model Search is just a kind of inconsistency.
However to have those feature for the Matrix Specification Artifact would be helpful.

According user documentation Step 6 here:

It should be possible to set a swimlane to horizontal by this: Orientation=Horizontal
But EA ignores at least in build 1310.

If have stereotypes define in my MDG technology profile having some tags. Most of those are just text, enums or structures. I also use Date as defined here:
what works fine for me.

To do that, I add to my stereotype definition in the profile an attribute and type in as Type of that attribute “Date”.

By doing so, an element using that stereotype get a tag that shows a calendar to select a date. All fine!

However when I try the same e.g. with Memo or Time my tag is just a pure String (neither a memo, nor a time).

Is it a bug that Memo, Time, … does not work?
Or is it a bug that Date works?
What is the right way to do such thing within UML Profiles (not Reference Data )?

Currently I am investigation, if the new formal review feature is suitable for our “formal reviews.

However I realized that it is implemented more as a chat or discussion. From our needs it is quiet unhandy to not be able to correct a topic once it was left be the editor.

Personally I think the edit blocking of discussion topics or posts is also not helpful but unhandy.

Can anyone illuminate me, why not allow later editing of that stuff is helpful/needed?

I published a style sheet with MDG, but when having a User Template and trying to use Update Style, the shown list does not contain the MDG published style sheet.

Bugs and Issues / Kanban Element Inconsistency
« on: August 01, 2017, 08:51:12 pm »
When you use a Kanban diagram you can drag and drop probably any element from the project browser to the diagram and particularly packages as well.

The cool thing about Kanbans is that you can specify queries, defining what elements to show on the Kanban to get a more or less self-maintained Kanban diagram.
However packages delivered by the queries are filtered out when the diagram is updated.

In other words, manually dragged you can have packages on the Kanban diagram but when using a SQL query you cannot. This is just inconsistency and from my point of view packages delivered by a SQL query should not be filtered out by the diagram "updater" at all.

When you look in the EA DB scheme you see that a package is “more” than the other stuff (t_object + t_package). When you are using EA, packages are “less” than other stuff (see this issue or e.g. the Specification Manager).
I ask myself why you Sparxians spend all this effort the reduce Package features where there is no need to, or where we users would have some benefits just if you would do nothing.

Pages: 1 2 [3] 4 5 ... 9