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

Any date about when we shall have a solution for this? (besides the weird and buggy “virtual connectors”).,39241.msg242691.html#msg242691

Users complain they cannot create SIPOcs because of this.

Does anybody know whether it is possible to deploy an add-in using ClickOnce Security and Deployment?

The goal is to
- enable users to install an add-in without admin rights
- update the add-in automatically when it has changed


Automation Interface, Add-Ins and Tools / MDGs and strict connector syntax
« on: February 27, 2018, 07:10:15 pm »
We have a connector validation implemented for our MDG.

How can we make sure that...
Step 1: when the strict connector syntax in ON, this only applies to UML and not to stereotypes derived from UML
Step 2: when the strict connector syntax is switched ON/OFF, our MDG-specific connectors are validated/not validated (same as for BPMN)



Suggestions and Requests / Enable tooltips on HTML reports
« on: February 21, 2018, 11:54:48 pm »
We would like to see element notes when hovering on elements in generated HTML reports.


Related post:,29540.0.html

End users sometimes want to create several views of the same element on the same diagram.
They also want to tell which connector needs to be visible for each view on the element (diagram object).
They don't want to create a "virtual connector". How could they think about such terminology when searching the documentation?

1) Bug: The documentation provides documentation on the implementation i.e. "virtual connector"
It should instead on the end user's feature i.e. getting several views on the same element on the same diagram.

2) Questioning the implementation
Why not creating virtual diagram objects instead of "virtual connectors". These virtual diagram objects would not visible in the project browser (like text, boundary etc...)??
Users would then explicitly hide the connectors they don't what to see for the virtual object.
So it would be also more flexible for the end-user.
And it would be a direct implementation of the requirement.

So that we can
- Export only changed elements (and import in other tools)
- Create reports on last changes

If we could also have the author that would be even better

Pages: 1 [2] 3 4 5