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.

Messages - Uffe

Pages: 1 ... 52 53 [54] 55 56 ... 72
Bugs and Issues / Re: Document Generator
« on: December 02, 2013, 11:38:53 pm »
Maybe you don't have a template named "ElementName"???

Bugs and Issues / Re: Classifier as attribute type
« on: October 30, 2013, 05:45:59 pm »
Thanks guys. A timing issue? Ouchie...

Would you like me to file it as a bug report?


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 / Re: Profile diagram hacky hack hack
« on: October 25, 2013, 07:28:20 pm »
Yeah, it's the Ravenous Backward Compatibility Beast of Traal rearing its ugly head. Makes sense, and as I say it's no biggie.



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 / Re: Apply/ Release User Lock is not available..
« on: October 17, 2013, 11:57:22 pm »
Sounds like the user has selected a Command Set which doesn't include Security. I've had several new users trip up on this.

The very first time they start EA, they are presented with a choice of command sets and they want to keep it simple so they select something like Essential UML rather than Complete, which sounds big and complicated and dangerous.

Problem is, only the Complete and Project Management command sets actually include the Security commands.

So ask the user to check View -- Workspaces and Commands -- Commands, and make sure they've got Complete selected.

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.



This has been verified as an Issue - the Issue Number is: 13055290.

Oh, and by the way: headers aren't generated either. Same result: no header generated when called from the automation interface, header generated when invoked through F8 (same template, same element).

I haven't tried footers, because somehow it doesn't quite feel as if performing basic functional testing on EA is my job.  >:(

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 / Re: Note rendering in RTF reports
« on: April 26, 2013, 06:40:16 pm »
OK, thanks.

For reference, I wrote a JScript to retrieve the information, based on the sample script in the help file.

I did not use GetFieldFromFormat() or GetFormatFromField(); instead I used formatted="1" in the tags.

XML DOM CreateElement balks at creating a tag whose name contains spaces, so I had to do a replace on the completed XML string.

If anyone has a neater way of doing it, I'm listening. :)


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 / Re: Text diagram objects behaving badly
« on: March 27, 2013, 11:39:28 pm »
OK, thanks for that.

Any ETA on that fix? People are kinda champing at the bit over here...

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.



Pages: 1 ... 52 53 [54] 55 56 ... 72