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

Pages: 1 ... 6 7 [8] 9 10 ... 12
Bugs and Issues / State Machine State Actions “burned in” Behavior
« on: September 29, 2016, 10:30:16 pm »
Once I entered a UML <behavior-type-label> or in EA wording added an "Operation" to a State and add a <behavior-expression> by selecting a Model Element on the Behavior Tab.

This behavior is “burned in”!
In other word to get rid of this behavior in my “Operation” I have to delete the whole Operation.

General Board / State Machine State Actions <behavior-type-label>
« on: September 29, 2016, 10:28:02 pm »
To allow defining of a <behavior-type-label> for state machine states, EA uses the "Operations" feature from Classes.

By doing so, is there any reason why I can define a return in the method signature of classes but not in the “method signature” of States?

When you have connected states with transitions and changed line style to Bezier and you add a new transition within the diagram all transitions switch back to Auto Routing.

This seems to happen for any line style changes from default (Auto Routing) to any other.

Observed in build 2015 and new V13 versions.

We have a EA SQL repository that is transferred to a eap file regularly.

Now we get the following error message:
„Database has reached maximum size [Select * from t_snapshot] Field:bincontent2”

As I know MS-Access DB’s are limited to 2GB. The last successful transfer resulted in ~800 MB. To verify that the data in the SQL DB is not exploded, we transferred the data to a feap, again resulting in ~ 800 MB.
So we are still far away from 2 GB.

Any idea on that?
Does anyone know if the transfer is done with one SQL select transaction?

Bugs and Issues / Create Linked Notes has strange behavior
« on: September 13, 2016, 06:31:30 pm »
I have classes with longer textual constraints.
To show this constraint text in several lines, I selected the constraint and pressed ”Create Linked Note”. This works fine in Build 1215. However when I change the constraint text, the note gets empty “{}”.
In current build for V13 the ”Create Linked Note” is even disabled.

I assume both kinds of behavior are a bugs.

When you define Tagged Values for Stereotypes with Profile Helpers and you add e.g. two Tag Groups, you can move the tags to those groups.
After closing and opening the Profile helper, tags defined e.g. under group A are now moved by EA under group B.
This behavior is in V12-V13.

I created a SQL search query. What I need from that query is a CSV file export.

Due to the fact that I need the notes of my elements, I defined “Note as Notes” to get rid of that “special treatment of the note field”. But there is another “special treatment of the note field” when it contains some text formatting stuff like Bold, List, … . In this case those parts of the note filed are not going in my notes column when exporting to CSV, but in one to many additional rows below the element.
Does anyone know a way to get rid of this “special treatment of the note field”?

Within my project I have security enabled with some groups and users.
Today I realized that some of the users are selectable in the Author field within the properties dialog and others are not.
By giving a missed user all permissions I verified that what is shown in the list has nothing to do with permissions at all.

Using V13 I find out that there is a new Checkbox “Add User to Authors” in the “Security Users” dialog. This Checkbox is checked for all users. I even unchecked and checked on again for a user not in the list (without success).
Any idea?

I defined a structured tagged values as shown here:

Instead of using a string I used an enum for each tag in the structure.

However the enum is treated as a string (The user cannot select the items of the enum).

In EA documentation is written that the tag must be simple (whatever simple is).
I assume not working enums is a bug.
(I used V12 .0.2015)

For some reasons I had to go back to our official company deployed EA version (V12).
However I also want to continue with V13. Is it possible to install both versions on one client without a VM?

(Maybe asked already, but I did not fined anything)

I want to show package baseline information in html reports. The easiest way I found was creating a “ModelView” element on a diagram having a SQL query doing the job.
The problem with that is that the diagram element does not auto-scale and so the html pages might not show all what is relevant.
Has anyone of you ideas how to achieve that, without doing too much EA and html scripting?

General Board / V13: Is context help box gone?
« on: June 28, 2016, 12:20:21 am »
In pre V13 versions when you moved the mouse to some kind of commands often a little box appeared (can’t remember the technical term) with some information about what this icon, menu item on screen is good for (e.g. you if you moved the mouse to something in the toolbox some informative text appeared).

In V13 Buid 1301 this is gone. Does it come back? ???

Suggestions and Requests / SQL Search macro #BranchGUIDorID= xyz#
« on: June 27, 2016, 10:47:37 pm »
Searching recursively children of a parent is not really simple in SQL. EA already provides the #Branch# macro which simplifies to find all children of a selected package.

However I have several use cases where this feature would be very useful if I could define the package without selecting it.

Example: a Kanban related to a higher level package could be updated by sql selecting elements under the higher level package.
Due to the fact that the feature is in principle already there, the implementation seems to me to be easy.

I have a stereotype with a tagged value of type date defined in my MDB.

When using that stereotype and trying to set the date in the Tagged Values view/window, it is not made persistent.
When doing the same in the properties dialog of my element all works fine.

Creating a package baseline leads to the following error message:
Microsoft OLE DB Provider for SQL Server [-21472179009]
Invalid column name ‘t-object’.

This message sound dramatic to me, but I do not see any negative effects (baseline is created and restoring from baseline seem to work as well)
Project Integrity Check does not repair that!
Any idea to get rid of that message?

Pages: 1 ... 6 7 [8] 9 10 ... 12