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

Pages: 1 ... 12 13 [14] 15 16 ... 20
Bugs and Issues / EA 11 RTF bork bork bork
« on: October 30, 2014, 01:54:52 am »
Hi all,

Having very serious issues with EA 11 and RTF document generation. There is an earlier thread on this, but there's no resolution.
  • EA crashes during generation. No error message, just terminates.
  • EA crashes during template editing - sometimes simply from selecting a bit of text and hitting Ctrl-C.
  • I've even observed bit rot, where a template that was working suddenly stops working, after making non-template changes to the MDG Technology and regenerating the XML file.
My templates were originally written in EA 10 (some in EA 9). Does anyone have any magic recipe for fixing these and making sure they don't break again?



Bugs and Issues / Apply Auto Naming and Security
« on: August 21, 2014, 06:55:37 pm »
Here's a weird one.

In a security-enabled repository, in order to apply auto names to elements the package must be locked - but the elements must be UNlocked. Yer what?

This is the behavior in 1009, and there's no mention of any changes in the version histories.

Is this really by design? If so, what's the reasoning behind it?


Bugs and Issues / "No current project" when project is open
« on: August 12, 2014, 07:36:33 pm »
Hi all,

If you open a project by entering a connection string in the Open Project dialog, and that connection string omits a project name so it looks like EAConnectString:--- DBType=etc etc, EA 10 opens the project but displays "No current project" in the window title.

Probably just cosmetic, but there's always the possibility that some flag is set incorrectly in a way which affects other stuff. Can someone check if this has been found and fixed in EA 11?



Bugs and Issues / Execution environment and stereotypes
« on: February 19, 2014, 02:01:38 am »
Hi there!

The presentation of stereotypes for execution environment seems a bit screwy.

If I set my own stereotype on an execution environment the element is presented in diagrams as «executionEnvironment,myStereotype». This also applies if I create my own stereotype extending executionEnvironment in a profile.

By contrast, if I set my own stereotype on an interface, it is presented simply as «myStereotype», which is what I want. The «interface» stereotype is displayed only if there is no other stereotype on the element.

In fact, if I tell the diagram not to show element stereotypes, «executionEnvironment» is still shown (but «myStereotype» is not).

Is there some obscure passage in the UML spec to warrant this? Is there some even more obscure EA option I can jiggle with to work around it?

I tried writing a shape script and print the Stereotype field (not StereotypeEx). This resulted in only «myStereotype» being displayed, but surely there must be a better way?



Bugs and Issues / Adding metatype
« on: January 20, 2014, 09:02:43 pm »
Hi there!

In a recent release of a profile, I added the _metatype attribute to one of my stereotypes. I deployed it in the same MDG Technology as always.

In my target project, I have now observed that some of the pre-existing classes with this stereotype are labelled Class (in dialogs etc) while others have the specified metatype. I would like them all to have the metatype.

Does this sound familiar to anyone? Is there a simple trick I can do to force the metatype onto these elements? And what's the underlying reason for this behaviour (so I can avoid it next time I go fiddling with metatypes)?



Bugs and Issues / Classifier as attribute type
« on: October 29, 2013, 06:09:38 pm »

If you select a classifier as the type of an attribute, EA does two things: it writes the classifier's name into the attribute's type (which is shown in diagrams), and it stores a reference to the classifier's object ID in t_attribute.Classifier.

If you then change the classifier's name, the attribute type is not updated to reflect this. Is there a reason for this? It would make more sense to me if the attribute type reflected the classifier's name.



Bugs and Issues / Profile diagram hacky hack hack
« on: October 24, 2013, 10:25:41 pm »
Hi all!

Does anyone know why the profile diagram isn't properly defined as its own diagram type?

There is a Profile toolbox, cool, no worries. But there is no corresponding diagram. What EA does, rather sneakily, is open the correct toolbox when a diagram is opened and the enclosing package has the «profile» stereotype -- regardless of the diagram type. So inside a «profile» package, you can create diagrams from UML, EA's core extensions, BPMN, whatever you like but they all open the Profile toolbox.

I call hack.

Now if you're working on some profiles in a project, you would like the option of creating a container package, with a single diagram which affords you the ability to create «profile» packages, wherein you construct your stereotypes, diagrams, toolbox pages, etc. But the only way to do that is to give the container package the «profile» stereotype, when it is in fact not a profile at all.

It's not the end of the world but it's wrong and it's bugging me.
Is there a reason for it?



Bugs and Issues / EA_OnPostNewPackage: stereotype missing
« on: July 16, 2013, 12:28:03 am »
Hi all,

I've got an Add-In which is supposed to do some magic when certain packages are created.
However, when I get EA_OnPostNewPackage the package I retrieve from the repository has no stereotype: neither Package.StereotypeEx nor Package.Element.Stereotype is set. So the magic fizzles.

Curiouser and curiouser, I'm pretty sure I've actually seen the post event work, albeit intermittently. I'm using 10.0.1007 against a SQL Server 2008 repository if that means anything.

It would appear there's a timing issue in the sending of this event, where the event is fired before the package creation has completed.
Has anyone else seen this?

Btw, I tried retrieving the package in my event handler, then immediately calling Update(). EA did not like that one little bit.
The EA_OnPreNewPackage event which is fired just before does include the stereotype so I suppose there's always that ugly brute of a workaround, But Still.



Bugs and Issues / RTF script fragment not called from automation
« on: May 06, 2013, 11:51:55 pm »

It seems that when you're creating an RTF document through the automation interface, any template fragments which themselves invoke scripts are not called. SQL fragments are called just fine.

I have also verified that the exact same "top" template calls the fragments correctly when invoked through F8 on the exact same element.

As previously documented (, I can't use SQL fragments because they mangle the formatting.

Am I missing something here?


Bugs and Issues / Note rendering in RTF reports
« on: April 18, 2013, 02:26:15 am »
Hi all!

I'm working on some RTF templates in 10.0.1006 and am bumping into an issue: Element Notes are generated with the formatting codes (<ul>, <li>, etc) as part of the text.

This occurs when I output the notes to a table column using a template fragment with an SQL query.

The same element notes are rendered correctly when output to regular text in the calling (non-fragment) template.

Is there an option I need to set?
Alternatively, is this a known problem?



Bugs and Issues / Text diagram objects behaving badly
« on: March 27, 2013, 12:32:59 am »
Hi all,

Wondering if anyone else has seen this.

After upgrading to EA10 (1006), text diagram objects have started getting seriously confused.
What happens is this: (just about) all "Text" objects in the entire project have their name fields set to the name of some completely unrelated element somewhere in the project, breaking Hyperlinks and causing general havoc.

Opening the Properties dialog on one of these objects reveals that that, too, is confused and contains an additional, unlabeled drop-down box in the middle of the Address field. The Type field has been blanked.

When I fix these objects, it doesn't take long (a day or so) until they break again. I've even deleted and recreated some of them, to no avail. Only Diagram Hyperlinks seem to be immune.

What the hell is going on? This is a production project with 140 users. For that to suddenly break is not an option.


Bugs and Issues / "Author" field retained when copying elements
« on: March 16, 2013, 02:17:00 am »
Hi all,

If you copy an element or a package structure, the elements, diagrams etc retain the original "Author" field.

This is very annoying in a team environment where one person (me) sets up the structures for the different teams to use.

Can we agree this is a bug, or should I log it as a feature request?

I would also like an option to specify that the "Author" field reflect the identity of the last updater, rather than remaining fixed until explicitly modified.
But I wouldn't call the current behavior a bug in this case.



Bugs and Issues / Truncated attribute initial values
« on: June 20, 2012, 01:12:03 am »
OK, racking my brains here.

I've got some Nodes with Attributes representing domain names, with the name stored in the Initial Value of a typeless attribute named "dns_a".

When shown in a diagram, the initial values get truncated after 15 characters, which is a bit short for most domain names.

Seems like a simple option needs to be set somewhere - but I cannot find a setting for this. Where the blinking flip is it?



Bugs and Issues / Include reference data in MDG Technology
« on: June 21, 2012, 04:13:52 pm »

I would like to define some project roles and make them available in several projects. These fall into the "reference data" category, and the MDG Technology Creation Wizard does not include an option for them.

Is there a way to include project roles or other reference data in an MDG Technology XML file?



Bugs and Issues / SQL search macros not working?
« on: June 19, 2012, 12:00:25 am »
Hey guys,

This seems weird, but...
I can't get the SQL search macros #WC# or #Author# to work.

I've tested on 9.2.921 against a SQL Server repository, and with 9.3.934 on an .EAP file.
In both cases, the construction
Code: [Select]
WHERE Name like '#WC#lass#WC#' fails to return anything, but using the correct wildcard characters (% and *, respectively) returns all "Class1" elements.

Similarly, the construction
Code: [Select]
WHERE Author like '#Author#' returns nothing, but if I substitute the text from the relevant option it works.

I tried using the #Author# macro in a non-SQL search filter - and that works.

Clearly I must be doing something wrong, but I can't see what.
Anyone else spot it?



Pages: 1 ... 12 13 [14] 15 16 ... 20