Topics

1

Automation Interface, Add-Ins and Tools / Adding built-in XSDcomplexType to my toolbox

« on: June 04, 2025, 10:35:01 pm »

My client uses the built in XML schema toolbox to manage and generate XSD's.

Now I wanted to create a custom toolbox in our MDG and add the XSD... stereotypes, but I can't seem to be able to.
I tried
- XSDcomplexType(UML::Class)
- EAUML::XSDcomplexType(UML::Class)

But none seems to work. I always get an error when I try to use the toolbox item on a diagram.
Unlike the «table» stereotype, these stereotypes are not considered part of the EAUML profile, and I guess that is why the EAUML:: one doesn't work.

Does anyone know a solution to this? As a workaround, I could add the "UML Profile for XSD Schema" that can be downloaded from the resources section to my MDG, but I'd rather not.

Geert

2

Bugs and Issues / Stereotype is not shown in the correct toolbox page

« on: May 26, 2025, 11:33:32 pm »

Details:

I have defined my own diagram type and toolbox.
Then I defined a view specification extending my diagram, that exposes certain stereotypes.
For the most part this works fine, except for one connector stereotype: ArchiMate3::ArchiMate_Realization
All stereotypes show up in the toolbox page I had defined for them, except for the Realization. That comes up in the toolbox page with the name of my view specifications (as if I didn't add it to a toolbox page)

Steps to reproduce
- Import the attached MDG technology file
- Create a new diagram of type Architecture::Solution Context Viewpoint
- Notice the Realization in the toolbox page Solution Context Viewpoint (instead of the toolbox page Structural Relationships"

Reported

Did anyone encounter this issues and know a solution?

Geert

3

Automation Interface, Add-Ins and Tools / How to define the default Language for my stereotype?

« on: May 19, 2025, 07:35:45 pm »

I'm building an MDG for modelling Data Contracts

So I have a stereotype DC_Model based on a class.
Attributes (steretoype DC_Field) have a datatype that is limited to this list: https://datacontract.com/#data-types

So I added a new "Product" for Data Contract, and added all of those datatypes ad code engineering datatypes.
That works well, if I set the language to "Data Contract" I can select the datatype for the attributes from my list of datatypes.

The thing I'm looking for is how to set the default language of my steretoype to my language.
I don't see any property that I can use to fill in the language.

I suspect it must be possible in an MDG since ArcGIS seems to be able to do it. Unfortunately that MDG is one of the "internal technologies" and not in plain xml format, so I can't check how they did it.

One thing I was thinking was to use a pattern instead of a simple stereotype in the toolbox, but I hope there is an easier solution.

Geert

4

PCS Bugs and Issues / Prolaborate custom connector properties for non stereotyped connectors

« on: April 04, 2025, 08:36:56 pm »

In my model I have defined «trace» relations between BPMN Activities and Applications.

That seemed like a perfect candidate for a custom connector property,
I'm trying to create one according to the manual: https://prolaborate.sparxsystems.com/resources/v5-documentation/create-connectors-in-prolaborate#target-selection--using-designer-configuration
but for some reason I can't create such a property without selecting a connector stereotype?

Is it really not possible to create a connector property for say a trace,  association, generalization, dependency,.. etc...?

Seems like a major oversight, or am I missing something?

Geert

5

PCS Bugs and Issues / Prolaborate custom icons not working?

« on: April 04, 2025, 07:51:10 pm »

I'm trying to set custom icons for my stereotypes in Prolaborate according to the help: https://prolaborate.sparxsystems.com/resources/v5-documentation/customize-visual-elements-in-prolaborate

The first hurdle was the size of the image file. Prolaborate asks for a .png file, so I converted my 16x16 .bmp files used in the MDG to a .pgn file.
The problem is that the filesize of such a image file is only about 400 bytes, for unknown reasons Prolaborate only accepts files larger then 1 KB.

So I then resized the images to 32*32, which allows me to upload the image. So now it looks OK in the configuration panel, but it doesn't work in my actual models. I still see the default icon in both the project browser as the detailed element page.

Did anyone here succeed in setting their own icons for stereotypes? What's the secret sauce?

Geert

6

Bugs and Issues / Tagged value "format" is changed to "Format"

« on: February 28, 2025, 09:59:19 pm »

Details:
I have an MDG that defined a tagge values as follows:
<Tag name="format" type="enumeration" description="" unit="" values="email,uri,uuid" default=""/>
This tag is defined on a stereotype that applies to Attribute

<Stereotype name="DC_Field" metatype="Field" notes="" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
<AppliesTo>
<Apply type="Attribute"/>
</AppliesTo>

When I create such an attribute, all the other tagged values remain lowercase, but only "format" is changed to "Format".


Steps to Reproduce:
- Define a tagged value on a stereotype extending attribute, with name format
- Import the MDG in the model
- Create an instance of the stereotype
- Notice that the tagged value "format" is created as "Format" (with uppercase F)

Reported

Geert

7

Bugs and Issues / Schema composer forgets inheritance selection on redefined types

« on: February 12, 2025, 06:21:33 pm »

Details:
When building a schema you can select whether or not to include the generalizations on a redefined type.
This information however is not stored in the database and lost upon reloading the schema


Steps to Reproduce:
- create a schema with the schema composer
- add an element that has a generalization to another class
- create a redefined type for that element in the schema composer
- select the inheritance checkbox on the redefined type.
- save the schema
- reload the schema
- notice that the inheritance checkbox for the redefined type is now unchecked.

Reported with ID: 25029064

Geert

8

Bugs and Issues / XSD generation inconsistent with quotes

« on: December 11, 2024, 06:38:05 pm »

When generating an XML schema, the xml header uses single quotes, whereas the rest of the schema uses double quotes.
This was not the case in version 15.2
In v17 this is

<?xml version='1.0' encoding='utf-8' ?>

in v 15.2 this was

<?xml version="1.0" encoding="utf-8"?>

Reported. I already got a response that this is a known bug and logged to be fixed.

Geert

9

Bugs and Issues / Error when copying package

« on: August 02, 2024, 06:41:53 pm »

I recieved the following error after copy/pasting a package

---------------------------
Enterprise Architect
---------------------------
Enterprise Architect (Build: 1701 - 64 bit)

ADODB.Field [0x800a0bcd]

Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record.
---------------------------
[ OK ]
---------------------------

Steps to Reproduce:
- copy package (full structure for duplication)
- paste package
- notice error

Had the same error on v16 as well.
Reported.

Geert

10

Bugs and Issues / Translations for operations cannot be added using the API

« on: June 03, 2024, 05:14:57 pm »

Details:
In the API there are methods to set the translations for EA.Method, but they simply don't work.
The translation is not added (that, or the GetTX... methods don't work, that is possible as well)

There is unfortunately no way to view or update translations for operations using the GUI

Seriously, who tested this feature? Was this tested at all?


Steps to Reproduce:

Code: [Select]

function main
    dim language
    language = "nl"
    dim operation
    set operation = Repository.GetMethodByGuid("{1880D1F3-8CC0-4291-AC6F-2432AB636921}")
    Session.Output "Start: " & operation.GetTXName(language,0)
    operation.SetTXName lcase(language), UCase(language) & " TXName"
    operation.update
    Session.Output "txName: " & operation.GetTXName(language,0)
end function
Reported

Geert

11

Bugs and Issues / Translations for connectors and operations (and methods) are not copied when cop

« on: June 03, 2024, 05:13:37 pm »

Details:
When I copy a package and paste it again, then the translations for attributes and connectors are not copied.
Only the translations for elements are copied.

Reported

Geert

12

Bugs and Issues / Translations for attributes and operations name and alias cannot be entered in t

« on: May 20, 2024, 06:54:55 pm »

Summary:
Translations for attributes and operations name and alias cannot be entered in the GUI


Details:
I've setup the translations module, and added a number of languages.
I can now add translations for the name and alias of elements, but not for the name and alias of attributes and operations.

For attributes the translations tab is not visible, and for operations the translation tab shows the translations for an element.


Steps to Reproduce:
- setup translation and add a few languages
- select an attribute/operation in the project browser
- note that you can't edit the name and alias translation for the attribute/operation

Reported

Geert

13

Bugs and Issues / Translation for connectors name and alias can not be added in the GUI

« on: May 20, 2024, 06:53:58 pm »

Details:
The user interfaces doesn't offer a possibliity to enter translation for connectors name and alias. Only the notes can be translated.

reported

Geert

14

Bugs and Issues / Connector.SetTXAlias sets TXName instead

« on: May 20, 2024, 06:52:44 pm »

Details:
The method connector.SetTXAlias sets the translated name, and not the alias


Steps to Reproduce:
Execute this script, and notice that the translated name contains "NL TXAlias" and the translated alias is empty

Code: [Select]

function main
    dim language
    language = "nl"
    dim connector
    set connector = Repository.GetConnectorByGuid("{908CBA1C-F31B-42a3-99B6-CC42040426BC}")

    connector.SetTXName lcase(language), UCase(language) & " TXName"
    connector.SetTXAlias lcase(language), UCase(language) & " TXAlias"
    connector.update
    Session.Output "txName: " & connector.GetTXName(language,0) & " txAlias: " & connector.GetTXAlias(language,0)
end function
Reported

Geert

15

General Board / Translation facilities in EA: is it usable?

« on: April 26, 2024, 10:02:58 pm »

I just had a new request from a user that needed process documentation in three languages. (Compliance requirement)

From what I figured out:

- Translations can be added to names, alias and notes
- Diagrams are not translatable
- Translations are not found in the HTML export
- Translations are not found in WebEA
- Translations are not found in Prolaborate?

So how useful is this translation feature anyway? Did I miss something? This doesn't look like a finished feature at all.

Was anyone successful in using translations in EA?

I'm currently thinking for our use case to create multiple duplicates of our model, and then with a script copy the translated names and descriptions for a specific language to the main name/description
This way we can publish our models in different languages in Prolaborate.

It feels this should standard behavior, and not something I should be scripting at all.

Geert