Jörg Witzel

[Jörg Witzel]

Hello,
we have the same “Ungültige Zeichen in einer Base-64-Zeichenfolge” Problem. However all our servers are virtual. The only physical machines are our Developer-Laptops. And i can’t install the LSA there naturally.

So i need a solutions without using a physical machine.

[Jörg Witzel]

In the EA there are two methods to model enumerations: a Class with stereotype “enumeration” and an entity Enumeration. Both look almost identical but only the entity Enumeration is translated correctly when generating java code. So we always use Enumeration.

[Jörg Witzel]

I found a workaround:
1.) You can not select Tagged Values for Attributes, but you can still ad an empty column (content-row contains “DTAG_”)
2.) Export the profile
3.) Find the Attribute description within the XML and change “DTAG_” to “DTAG_”
4.) Load the profile again

The generation of the document works now (with Tagged Values on Attribute Level).
Seems that only the GUI-mask is broken and not the generator 🙂

Best regards
Jörg

[Jörg Witzel]

Hello,
is there maybe an older version i could use, which still contains the “Tagged Values on Attribute Level” – Feature ?

I have a special document to deliver to my customer (only classes an diagrams – no complex eaDocx Features used) which should include tagged values for all attributes.

Best regards
Jörg

[Jörg Witzel]

Hello,

> We are keen to offer different options to output other information for elements, however one issue with Excel is that if
> we output information over more than 1 row we need to ensure there is a mechanism to ensure that we (internally)
> and you (the users) understand which element the attribute etc relates to. Hence the reason for including summary cells.

My suggestion is to handle Attributes and Operations the same way as nested objects. I.e. you already have a mechanism to handle for example Activitities within Activities. To use row-grouping for the hiearchy was a good idea. The same should be done for Attributes and Operations.

> It is all too easy to lose context as there is always the risk that a user does some manipulation on the rows and
> the context could be lost – is this a risk that would be acceptable?

Yes. I think the “check-for-changes” mechanism (forgor the correct name) you already have is good enough to prevent corruption of the modell.

> Other options we have considered is adding a column that displays the attribute(etc) owner?

Yes – that could also be an idea. However such a colum should be read only.

Best regards – keep up the good work !
Jörg
Comments/thoughts always welcome on what and how you would like to see the information.

[Author]

Posts