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 2 3 [4] 5 6 ... 21
Hi all,

I'm trying to create a stereotype which extends datastore. I've tried this both with in-project UML types and with a profile. I'm on 11.1.

The problem I bump into is that the shape script I've created isn't run. When I create an element of my stereotyped type, it looks like an Object. It is presented with the datastore keyword and my stereotype, and it has the Object colour, not the datastore one.

If I redefine my stereotype to extend Object instead of datastore, it works: the script runs.

Why is this? And does it still work the same in 13?


Bugs and Issues / User guide API documentation not navigable
« on: January 31, 2018, 03:17:17 am »
Hi all,

The API documentation in the user guide cannot be navigated to find what you need.

Starting from the first page, I can navigate to Automation, then to Object Model, then to Reference, which has links to pages for the different packages.
Then what? Well, let's see.

Repository Package => "Learn more" => Repository Class. Well, OK -- but what about all the other classes? Fail.
Element Package => Just a class diagram, no links. Fail.
Element Features Package => Just a class diagram, no links. Fail.
Connector Package => Just a class diagram, no links. Fail.
Diagram Package => Just a class diagram, no links. Fail.
Project Interface Package => Just a class diagram, no links. Fail.
Document Generator Interface Package => "Learn more" => DocumentGenerator Class. Alright. And look, there's the Project class!
Mail Interface Package => "Learn more" => MailInterface Class. OK.

And if I'm looking for the Simulation Package I'm poop out of luck, 'cos that's not even listed on the Reference page. Are there other packages missing? Who knows?

Prev/Next buttons, you say? These packages have got dozens of classes in them. Left-to-right navigation is -- no. Just no.

Look, I understand the desire to move from the installed help file to an on-line web format but you can't just take a tree-structured bunch of help pages, flatten them out and call it good. You've got to make sure the new structure can actually be navigated, and that means every class has to be linked from its parent package's page.

It's time to fix this.


General Board / Visibility levels: users or groups
« on: January 29, 2018, 09:09:25 pm »

From the user guide: "In additional to their normal permissions, database users are granted access to one or more visibility levels."

In anything but tiny-scale deployments, database (and everything else) access is administered not by user, but by group. In terms of SQL Server, users are created based on group, rather than user, principals.

Will EA's visibility levels work correctly when applied to group-based database users?


Hi all,

Element constraints aren't listed on the shape script Display Element/Connector Properties help page.
Is there a way to access them? Like a call to HasProperty("#CONSTRAINT:xyz#"), something like that?


Bugs and Issues / User security: AD groups
« on: January 23, 2018, 09:00:14 pm »

Looking at the post-12.1 user security, it seems that I can specify a permissions group and link it to an AD group, but I cannot specify that all users belonging to an AD group should have access to the project. Nor can I tell EA to import all users belonging to a specific AD group.

Am I right?


Suggestions and Requests / Watermarks. Discuss.
« on: December 12, 2017, 09:14:52 pm »
Hi all,

This is a discussion post regarding watermarks.

There are two instances of watermarks in EA: document and diagram watermarks. A document watermark consists of an image which can be specified in the document generation dialog and which is then superimposed on each page of the generated document, while a diagram watermark consists of a single line of text which is superimposed on copied, printed and generated diagrams. The text is repeated diagonally lower-left-to-upper-right with a fixed typeface, size and line separation.

I'm OK with how the document watermarks work, except they're not in the API. So I think there needs to be an addition to the DocumentGenerator() class which allows you to set an image file for the document watermark.

Diagram watermarks are a different story.

First off, there's a bug which causes the watermark to appear in front of the diagram label (eg "class My Class Diagram"). The watermark should be behind everything else, including frames and labels.

More importantly, however, these watermarks are specified per workspace. That is to say, they're stored in the user's registry and not in the project. Meaning a modeller puts the same watermarks on diagrams from every project they access, while at the same time two modellers can print the same diagram at the same time with different watermarks.

This doesn't make sense to me. It would be more natural for a watermark to be dependent on some aspect of the diagram or the model of which it is a part, not on the user account that's exporting the diagram.

I therefore propose that the diagram watermark functionality is reworked as follows:
  • Diagram watermarks to be stored in the project, not in the user's registry. (If necessary, split them into "user (or workspace) watermark" and "project watermark".)
  • [Project] watermark content to be selectable: either the diagram's version; or its parent element's Status, specified tagged value or other property common to all elements; or a fixed string; or an image file (like a document watermark).
  • Watermark layout to be selectable: typeface, size, direction and line separation.



Hi all,

I'd like to stamp "draft" (or whatever) watermarks on certain generated documents. RTF doesn't actually support those, but according to this MSDN article you can achieve the same effect using a \shp.

I tried creating a watermark in a Word document and saving that as RTF (which works, Word can render it correctly when reopening the file), then importing that into a linked document in EA (by creating the linked document, then in the RTF editor selecting File - Import), the idea being that I could use that document in a call to DocumentGenerator.InsertLinkedDocument() to get the watermark to show up on all pages.

The EA RTF editor did not display the watermark, but not to worry, the RTF specification says you're allowed to ignore content you can't handle, but if I export the document, the \shp is gone. I'm not sure the spec says you can do that, but anyway, that means this approach doesn't work.

But is there another way to create a watermark like this?

I can script it, sure. But I was looking for a way to have it incorporated into the template.


Automation Interface, Add-Ins and Tools / Doc template: generalization set
« on: December 08, 2017, 10:36:57 pm »
Hey all,

I can't find anything that looks like a generalization set field in the connector section of an RTF template.
Is it available somewhere, or do I need to write a fragment?


General Board / Project MDG Technology options storage
« on: December 07, 2017, 02:57:08 am »
Hi all,

Anyone know where the project set of required / disabled MDG Technologies is stored?
Can't find an obvious candidate table.


General Board / Audit: document generation
« on: December 06, 2017, 02:43:58 am »
Hey all,

Auditing can audit XMI import/export. Can it also audit document generation? Who, what, when?
No, right?


Bugs and Issues / ActionPin property type not set when created
« on: November 08, 2017, 03:19:16 am »

When I create an action from an activity, EA offers to create the action pins (structural elements). They're given the right names, and their argument properties (behavior, parameter) are correct. But the type is not set.

Is there a reason for this?

I would expect the kind (direction) to be set as well: input for input activity parameters, output for output and return activity parameters.

Am I being unreasonable?

(Inout activity parameters are less straightforward; ideally two pins should be created in this case but I can let that slide.)



Excluding WebEA and OSLC, is there anything the old non-pro cloud server can do that the Pro Cloud Server Express can't?


Hi all,

Well, clue's in the title really.

Apparently, the Pro Cloud Server includes a license server which supports IPv6.
Is that included in the Pro Cloud Server Express?


General Board / Re: Free: Pro Cloud Server Express (with WebEA)
« on: October 30, 2017, 08:23:43 pm »
Hi all,

This is in reference to the offer posted in the Latest News thread. No speculation please, I'm after an official reply.

Quote from: Sparx
For registered users of Enterprise Architect Corporate (and above) with more than 5 current licenses, Sparx Systems will provide a license of Pro Cloud Server Express with WebEA.
  • Your licenses of Enterprise Architect must be current
  • The Pro Cloud Server Express licenses will match the Enterprise Architect license expiry date

I'm a little confused. Since this is described as an "offer", that implies that the offer won't be valid for ever (although there's no end date listed).

So my question is:
If I qualify and take this offer up, then subsequently renew my 5+ Corporate+ licenses, will the Pro Cloud Server Express license expire? In other words, is this a one-time offer?

Or should it be read to mean that the Pro Cloud Server Express comes free of charge for customers with 5+ Corporate+ licenses? Meaning that as long as I pay for 5+ yearly client renewals, my Pro Cloud Server Express will keep on keepin' on?

If so, how do I renew my Pro Cloud Server Express license?


General Board / Updating 11.1 to 13.5 -- any gotchas?
« on: October 25, 2017, 07:57:59 pm »
Hi all,

Well they put it off for longer than humanly possible, but my big client is finally gearing up to update EA from 11.1 to 13.5.
So are there any gotchas, ifs, buts or bear traps I should be aware of?

The GUI is completely reorganized. Got that. Anything else?

The main features we're using would be
  • Corporate edition on Windows 7 (moving to Windows 10)
  • Custom MDG Technologies with a lot of document templates
  • No extensive use of third-party standards (BPMN, TOGAF, etc)
  • SQL Server repositories
  • User Security with Windows authentication
  • Cloud Server for RAS (backed by SQL Server)
  • The old Visio importer

We were using the license server as well, but we're abandoning that due to the lack of IPv6 support and reverting to the user-friendly and easily circumvented license file.

  • Are there any changes to the EA database schema, and are there update scripts available?
  • Are there any breaking changes to user management?
  • Are there any breaking changes changes in the cloud server?
  • Is the new Visio importer included in the Corporate edition, or is it only sold as part of the Office integration?
  • If the latter, will the old importer work with 13.5?

Anything else anyone can think of would of course also be appreciated.


Pages: 1 2 3 [4] 5 6 ... 21