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 ... 20
16
Bugs and Issues / MDG Technology wizard: wrong back link
« on: March 27, 2018, 10:02:06 pm »
If in 1352 you start the MDG Technology wizard, select not to use an MTS file and click Next, and from the next wizard page click Back, you arrive at the MTS file selection page.

Instead, you should arrive at the wizard's first page.

Reported.


/Uffe

17
Bugs and Issues / Custom Script fragments not working in 13.5.1352
« on: March 27, 2018, 03:07:36 am »
Hi all,


We recently upgraded from 11.1 to 13.5.

I have a document generation script which worked fine for three years before the upgrade, and now doesn't.

In the project (SQL Server repository), there is a simple project browser script that calls the main document generation script which resides in an MDG Technology. The generation script makes a number of calls to DocumentGenerator.DocumentElement(), specifying various elements and a few dozen different templates. The templates reside in the same MDG Technology.

Some templates include fragments. Custom SQL fragments work as expected every time. Custom Script fragments, however, do not.
(Note: these are the only two types of fragment I'm using. There are no Template Selector fragments or Document Script fragments. If you are unaware of the difference between these, please refrain from posting "helpful" suggestions.)

The first time I run the document generation script, all custom script fragments produce the desired result.
On subsequent runs, the custom script fragments produce nothing.
After a restart of the client, the document generation again works once, then I have to restart again, etc.

When testing, I am changing nothing between runs. The behaviour is consistent: all custom script fragments fail after the first run, none of them fail on the first run, and custom SQL fragments never fail.

If I select the same element in the project browser and hit F8 to invoke the regular document generator, and specify the "parent" template which contains the references to the fragments, this partial generation works every time. But it does not clear the error: when going through the document generation script, custom script fragments fail consistently every time after the very first.

I have tried regenerating the MDG Technology: no effect.

What the hell is going on?


/Uffe

18
Bugs and Issues / Behaviour of action pins
« on: March 22, 2018, 11:06:41 pm »
Hey all,


I'm bumping into some things I don't like with action pins. Am I the only one?

Let's say I create an activity with some parameters, and specify classes for their types.
Let's then say I create a call behavior action from the activity, with an action pin for each parameter.
Each pin thus created is correctly linked to the correct behavior (the activity) and parameter.

However, each pin is of "input" kind -- regardless of the corresponding parameter's direction.

Shouldn't the pin kind follow the parameter direction?


Furthermore, the pins do not have any types set.

Shouldn't they?


Finally, if an activity parameter's type (class) has tagged values, those tagged values are included in the parameter's extended tagged values.
A pin does not -- even after setting the type to match the corresponding parameter's, the pin has no extended tagged values.

Shouldn't tagged values be "extended-inherited" from types to pins, just as from types to parameters?


The first two I can script my way around if necessary. But there's magic behind the extended tagged values, so I'd need that to be fixed in the tool.

Or am I unreasonable -- or plain wrong -- in how I expect action pins to work?


/Uffe

19
Bugs and Issues / DB2 import: FK constraint connector target role
« on: March 21, 2018, 03:02:41 am »
Hi all,


Using 13.5.1352 on Windows 7x64, importing from a z/OS DB2 12 database through IBM DB2 Connect.

After import, some but not all foreign key constraint connectors are out of whack. The Involved Columns list is empty (as is the Join on Constraint field), and the target role is set to some random string of garbage.

The same garbage string gets reused in several broken connectors, but from one import there may be more than one such garbage string.
The behaviour is not consistent; the garbage strings and which connectors get them vary from import to import (of the same database).

Has anyone else seen this? If so, what's going on?

I can go through and set the Join on Constraint property manually. The dropdown is properly populated.
But does anyone know if this indicates that something else is broken in the model?


Secondly, EA crashes after import. Far as I can tell, this is an unrelated error.
The crash occurs even if I tell EA not to import any constraints or foreign keys at all, and it occurs whether or not I tell it to draw diagrams.

The Windows log shows a fault somewhere in or near ntdll.dll.

Anyone else see this?

Cheers,


/Uffe

20
Hi all,


EA does not allow structural elements (ports, activity parameters, etc) to be placed in a diagram unless their parent element is in the diagram as well.
This makes sense in most situations, but when the diagram is the composite diagram for the parent element it does not.

I would like to propose, therefore, a relaxation of the parent element restriction to allow structural elements to be placed in a diagram without their parent element if the diagram is the composite diagram of the parent element.

A composite diagram typically depicts the inner structure of a parent element -- a structural breakdown in the case of classes and components, or a behavioral breakdown in the case of activities -- with the structural elements representing parts of that breakdown.
In these cases, the presence of the parent element in the diagram serves no semantic purpose: if the diagram's context is a breakdown of an element, that element is unnecessary. All it does is cause layout problems.
However, if you want to show the structural elements, you have to include the parent. There's no other way to get them in there.

So EA should allow structural elements to be placed freely within the composite diagram of their parent element.

If the user chooses to place the parent element in its own composite diagram, the old rules should apply and the layout of the structural elements should be locked to the parent element.

You can almost see what I'm after by creating a diagram filter which hides the parent element's type, and applying it in a composite diagram. This causes the structural elements to appear to be free-floating, although they are in fact still constrained by the hidden parent element.


/Uffe

21
Hi all,

Activity parameters and action pins do not honour the diagram's Show Parameter Detail setting (in Features).

Shouldn't they?


/Uffe

22
Hey all,


How nicely do in-project defined requirement types play with profile-defined stereotypes?

Let's say I want to define a requirement type 'MyReqType'. I want it to show up in the Type dropdown in the properties dialog (project type), and I also want it to have a mandatory tagged value (stereotype).

If I define the requirement type both ways, how will EA behave?

If I create a «MyReqType» element from the toolbox, will EA recognize it as being of the 'MyReqType' requirement type, or will it see it as something different because the fully-qualified stereotype name is MyProfile::MyReqType?

If I create a regular requirement from the Common toolbox and set its type to 'MyReqType' in the property dialog during creation, will the tagged value be created?


Cheers,


/Uffe

23
Automation Interface, Add-Ins and Tools / WebEA user authentication
« on: February 17, 2018, 12:05:54 am »
Hi all,


I'm evaluating WebEA for a client. According to the WebEA Login help page, in addition to some "access code" I cannot see any point of, WebEA supports "standard Enterprise Architect model security." However, the page then states that login credentials can include
  • An access code, or
  • A user ID and password, or
  • Possibly all three
Ignoring the fact that "all three" makes no sense since you can't provide just a password with no user ID, what about Windows domain authentication? It's part of standard EA model security, but it's not in the list.

Can you authenticate WebEA users against a domain, or not?

What happens if you configure a project for windows authentication, and configure WebEA to prompt user ID and password?
Should users provide a blank password?
Is the password ignored?
Or will users be unable to log in?

What happens if you configure a project for windows authentication, and configure WebEA to prompt for an access code, or no authentication at all?
Are users correctly identified in the project (in Author fields etc)?


/Uffe

24
General Board / Security permission missing from user guide
« on: February 10, 2018, 02:50:52 am »
Hi all,

The recently added security permission Configure Project Requisites is not listed on either the 13.0 permission list or the 13.5 permission list pages.

/Uffe

25
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?


/Uffe

26
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.


/Uffe

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


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?


/Uffe

28
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?


/Uffe

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

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?


/Uffe

30
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.

Thoughts?


/Uffe

Pages: 1 [2] 3 4 ... 20