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 ... 7
The traceability window is still ignoring MDG icons and this is confusing end users.

One generic way to solve it and to allow extensions at the same time is to provide an addin event that we can use to provide the icon that we need.
The icon could then also reflect the state of any element property or tagged value.

Thank you Paolo

Users are asking for a way to enter tagged values for a set of recurrent of a very long list of tagged values (longer than the window height).
As far as EA 14.1 is concerned, the specification manager is still very cumbersome for data entry.
It is also limited to the content of a package.

If I were you, I would rather simplify by changing my root packages into sub-packages.
Here is an example of a complex root package published to HTML:

It is easy to do. Here is something I did some time ago. You will need to tune it for your specific case.

1. Create a new single target package where you want your root packages to be moved to.

2. Using SQL Server Management Studio or equivalent, run some SQL to
a) change the package type for the root packages to be moved
UPDATE t_package set PackageFlags = NULL
WHERE t_package.Package_ID in (
   SELECT  Package_ID FROM t_package
   WHERE PackageFlags like 'isModel=1%'
   AND NOT (Name = 'XXXTRANSFER' or Name = 'XXXProjects')

b) move the selected root packages into the new single target package.
UPDATE t_package set Parent_ID =  {ID OF MY SINGLE PACKAGE}
WHERE t_package.Package_ID in (
   SELECT Package_ID FROM t_package
   WHERE Parent_ID = 0

Try first on a test database :-)

For some obscure reasons, some stereotypes defined in our MDG are mysteriously added to the list of UML Stereotypes in our shared repository.

As a result, when a new element or connector of that stereotype is created, Sparx uses the one defined in the repository instead of the one defined in the MDG.
Since the signature of these 2 stereotypes are different this has various impacts on the behavior of Sparx (execution of shapescripts, model validation...).

This situation happens notably when we change the type and/or stereotype of an element or connector in our MDG and then in the model repository. In that case, Sparx sometimes adds a new duplicate stereotype in the repository.

The architecture discipline requires frequent and dynamic updates to the metamodel.
Therefore having to rebuild and redeploy the mdg for each little change (as currently implemented by Sparx) is inadequate.

Therefore we are using a language metamodel, stored in the production repository, as language constraints.
When Sparx starts, an addin loads this metamodel and dynamically builds the language constraints in memory. These prevent users from creating the wrong connectors.
The exact same language metamodel is also used as documentation.

When the metamodel is changed in the repository, the validation rules are changed instantly.

Quicklinks are also generated automatically from this metamodel.
The same validation rules can also be loaded from the quicklinks.

There is an additional issue with Build 1427 (already reported to Sparx) which make it unusable to me at least.

As soon as I save my workspace layout with a name and then reload it, then I can no longer save a UML profile without loosing the default stereotype colors.

If I delete the registry keys EA400/EA1405Workspace then it works again. But I loose my workspace.

Automation Interface, Add-Ins and Tools / Re: Stripped-down model view
« on: September 19, 2018, 12:00:01 am »
The Text Element stereotype is a good idea.

However we need this to be dynamic, like a model view.
And I would not add such behavior in our add-in.

I will issue a feature request.

Thank you.

Automation Interface, Add-Ins and Tools / Stripped-down model view
« on: September 12, 2018, 01:08:55 am »
Is there any way to have the equivalent of a model view as a text box, without any window around it.
Ideally there should be an optional text on the left.

Example: "Number of issues: " {text box containing the result of some SQL query}

In v14 there is now more than ar multiple ribbons in the RibbonSets.xml
In v13 there was a single ribbon in UserRibbon.xml

When deploying RibbonSets.xml to end users' computers, how can we make sure that the right ribbon is activated.
I could not find the currently selected ribbon set in the registry.


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:

Pages: [1] 2 3 ... 7