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

Pages: 1 [2] 3 4 5
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.

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.

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.

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.


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:

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)


We would like to DYNAMICALLY update the quicklinks in our model repository where our MDG is stored (without changing the MDG).
Does anybody know where these quicklinks are stored?

Why do we want to do this?
The model validation features of our addin dynamically adapts to metamodel changes without having to change anything in opur MDG.
Our formal metamodel is used 1) for model validation 2) for quicklinks generation 3) for documentation
See an example here:

The only thing missing to make it entirely dynamic is to update the quicklinks in the repostory when the metamodel gets changed.

We do *NOT* want to use a metamodel defined in the MDG as this is not dynamic.

In a template fragment I am selecting elements of a certain types in the current package using #PACKAGEID# (see select clause below).
I use that fragment only to be able to sort elements by a certain tagged value in a package.

The select clause collects notably the element Note.
The fragment also formats the resulting values in a table.

Problem: The generated Note field value, referred as {Note} in the document, shows the source HTML text including <LI> etc...

Any idea how to fix this problem?


Perspective = (select tv.value from t_objectproperties tv
where tv.Object_ID = t_object.Object_ID and = 'Perspective'),
Code = (select tv.value from t_objectproperties tv
where tv.Object_ID = t_object.Object_ID and = 'Code'),
t_object.Name as Name, t_object.Note,
Implications = (select tv.value from t_objectproperties tv
where tv.Object_ID = t_object.Object_ID and = 'Implications'),
Rationale = (select tv.value from t_objectproperties tv
where tv.Object_ID = t_object.Object_ID and = 'Rationale')
FROM t_object
where t_object.stereotype = 'NMBS_Principle'
and t_object.package_id = #PACKAGEID#
order by Code

Pages: 1 [2] 3 4 5