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.

Messages - adepreter

Pages: 1 2 [3] 4 5 ... 9
Thank you Nizam. But in the present scenario
- the MDG is stored and must be stored in the add-in
- the metamodel is stored in the repository

So I really need an API to load the MDG after the repository is already open (not OnInitializeTechnologies)



Loading my MDG on EA_OnInitializeTechnologies is not appropriate for my needs. It is too early.
I need to first read configuration data (including a metamodel) from a repository, then update my MDG dynamically and then finally load the MDG.

How can I load an MDG at any time?
Would it be possible to make this API public please? This API should already exist since it is used by Sparx in the UI.



When a tag is added to a stereotype in an MDG using "Edit with profile helper", the features/attributes window does no synchronize properly
=> the new tag does not show in the list of attributes.


Bugs and Issues / Tag description no longer visible in Sparx 14
« on: June 11, 2018, 09:31:55 pm »
The numerous tag descriptions that I provided with my MDG are no longer visible in Sparx 14.

Please bring them back as it was before or better (e.g. when user is hovering over a tag).


Adding perspectives in Sparx 14 was a good idea though it still doesn't tell how the many different languages integrate.

I would like to take advantage of this feature in my MDG which provides all perspectives needed for Enterprise Architecture in one single language.
However I couldn't find any documentation to achieve this.

The problem:
- In my MDG, how can I assign each diagram type to a specific perspective?

The story:
- As an Enterprise Architect
- I want to create, from a selected architecture perspective, a view that belongs to a single integrated language that is the standard in my company
- So that all stakeholders can easily collaborate using a same and single terminology and notation

The references:
- What I mean by architecture perspective:
- What I mean by view:

What I could figure out is that the problem comes from legacy content in the ...AppData/Roaming/Sparx Systems folder.
Now the problem is in the hands of the Sparx team.

Thank you! Very useful.

That is anyway very useful information Geert. Thank you  :)

Since it is working with your MDG, I will try to figure out what makes mine invisible in the Resources window (Though it might be hard to find out because the MDG is quite large)

No, I don't have any reference to an MDG file.

Even if I remove the MDG, regenerate the MDG using Sparx 14 and import it, I still can't see the MDG in the resources window.

Using the "Technologies / Manage" option, there is a button '"Remove" that is activated for our technology.
And from Resources Window I can still import the MDG => It gets imported and activated, but it is still not visible in the Resources window.
For checking the existence of the MDG in the database: SELECT * FROM t_document where DocType = 'TECHNOLOGY' and DocName ='TechnologyName'

All users have 13.5 installed and our MDG is stored in our shared repository.
The MDG includes our architecture workspace layout which is critical since the default layout in Sparx is focusing on analysis, design and development.

The problem is that we cannot deploy Sparx 14 on users machines (there are many) without having tested on our own machines.

So we need both to coexist for some time.

Our MDG that was built and deployed with version 13.5 was deployed in our shared SQL Server repository.

After upgrading to Sparx 14 and opening that repository, the MDG is not visible in the resources window though it is activated.
Same problem with all of our other test repositories in Access and in SQL Server.

I implemented the _MeaningForwards and _MeaningBackwards in a connector metaclass of type Transition.
The initial values of _MeaningForwards and _MeaningBackwards  are set to a description of the meaning of the connector in each direction exactly as described ion the documentation:

But when I look in the traceability window, I still get the default verbs defined for the UML Transition.

NB: It does work for metaclasses of type association and dependency

I know this is a weird situation but...

If an MDG XYZ is stored in a repository
and an AddIn is installed that loads the same MDG (or another version of it)

then  the MDG that is activated is the one from AddIn (as expected)
and the quicklinks defined in the MDG loaded from the AddIn are ignored (BUG)


Thank you very much to all.
It works :-)

I didn't know I would start such passionate discussion :-)

How can we wrap/unwrap the zipbin MDG content (to/from the t_document table)?


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