Messages

1

Bugs and Issues / Re: Cannot add parameters to class operations anymore

« on: November 07, 2016, 05:52:17 pm »

No, but I also cannot find it. With the ribbons I really don't find anything anymore, tbh. Tried using "find command", which usually works fine, but didn't find anything like that. The closest I found to "consistency check" was "Project Integrity Check".
I ran that and it found several problems.
Made a backup and let it do its job.
Now everything is working again - thanks a lot!

Guess it is just the function you suggested, it has just been renamed, correct?

2

Bugs and Issues / Cannot add parameters to class operations anymore

« on: November 05, 2016, 01:48:16 am »

Hi all,

I have a strange problem which seems to be based somewhere within my project file: I cannot add any attributes to any class operations anymore. It just doesn't save what I enter. It doesn't matter which stereotypes, languages or anything else I choose (EA 12.1 as well as 13).

I tried with a new project and it works perfectly fine. But within my project (and several other projects with the same file base) it doesn't work (anymore).
Does anyone have an idea about how this could have been broken? Is there any setting which prevents attributes from being added?

I have asked a lot of people over the past days, and no one believed me until they saw this behaviour themselves. And no one has any idea about how we could have broken the project so badly.

Unfortunately, the whole company uses a  project file as a base for their projects, where this problem also happens, which means more and more projects in my company are encountering this.

Thanks in advance.

3

General Board / Re: Can you easily hide / show one exact element type in a diagram?

« on: July 19, 2016, 05:43:31 pm »

Auto layout doesn't work for me. Tried that, didn't really look anything like I wanted it to be. I guess it's simply not indended to be used for complex process diagrams.

4

General Board / Re: Can you easily hide / show one exact element type in a diagram?

« on: July 19, 2016, 05:22:33 pm »

Thanks.
I guess it is what I was searching for, but I can't get it to work.

I created a filter on elements: "Object Type" one of "Requirement" and when "hide" is the selected option, it hides everything BUT the requirements. I would've expected it the other way round. But anyway, if I change the filter to "Object Type" not equals "Requirement", the filter won't do anything at all.

I don't understand how to create a filter where my exact object type is hidden.

Edit: stupid me. Selecting "all" in "one of" and simply unchecking "Requirement" works, of course.

Thank you!

5

General Board / Can you easily hide / show one exact element type in a diagram?

« on: July 19, 2016, 12:01:03 am »

Hey folks. Didn't find anything neither here nor via google. Tbh, I don't really think there is a way, but I decided to try and ask.

I have a diagram which is pretty stuffed with information, but still okay to read. But for some people, I need a view which is even more crowded (e.g. with requirements & their dependency links on the diagram), but for others, I don't, and it really gets confusing having all that information on one diagram.

My current workaround is to copy & paste the complete diagram into a new one (without creating new elements) and simply delete the element types I don't want to see in this view.
But maybe there is a smarter solution than this?

Edit: Build 1230, btw.

6

Bugs and Issues / Re: Columns in upper case, not setting column stereotype.

« on: June 21, 2016, 11:37:42 pm »

What I do in my project is just adding columns to some of the already existing tables, which are already stored as oracle tables in my base EA project, there's nothing I can change about that.

Oracle stores everything in upper case since forever, as far as I know, but until EA version 11, I was happy to at least being able to easily read my table column names in my design file. We unfortunately have column names consisting of several words. In upper case, this really is hard to read. And I simply don't think there is a need to override how a user wants to store a column name in this tool, no matter what Oracle will do later on.

7

Bugs and Issues / Re: Columns in upper case, not setting column stereotype.

« on: June 21, 2016, 10:23:47 pm »

Same problem here.. anyone having found a proper solution yet?
The sterotypes <blank> workaround really is just annoying and a lot of overhead, I really don't want to do this whenever I change a column name or add a column to a table.

I get that a lot of people might think "so what", but it really bothers me and I don't get why this behavior in the tool has been changed at all and still think it is a bug.

Maybe you specify the problem you are experiencing. There were a few listed in the thread.

Geert

Sorry, totally skipped the other problems in my head automatically.

I am talking about adding a new column to a class of type table / Oracle (or changing an existing columns name) will always convert the column name to upper case automatically.

EA build 1230 btw.

8

Bugs and Issues / Baselines - error message when trying to show differences

« on: June 21, 2016, 10:19:30 pm »

After two years of refusing to use baselines, because I thought the comparison was much too slow, I wanted to try once again today.

I just created a baseline on a very high level in the project, which I knew would be slow, but I wanted to see how bad it really is.
In fact, it does not work at all. Even after just creating a baseline, no matter whether I make any changes at all, "show differences" will always give me an error "An error occurred during the compare process." and no more information.

I am using EA build 1230 and my project is (still) stored in a *.eap file.

On package level, it works well, but with ~ 1000 packages in my project with a lifetime of only some months, I really don't want to go down to this level, it produces way too much overhead.

At the moment, we still use a simple file copy as a backup. But as we want to go for a cloud solution with future projects, we will need a working version control solution soon.

9

Bugs and Issues / Re: Columns in upper case, not setting column stereotype.

« on: June 21, 2016, 09:55:16 pm »

Same problem here.. anyone having found a proper solution yet?
The sterotypes <blank> workaround really is just annoying and a lot of overhead, I really don't want to do this whenever I change a column name or add a column to a table.

I get that a lot of people might think "so what", but it really bothers me and I don't get why this behavior in the tool has been changed at all and still think it is a bug.

10

General Board / Re: Can't re-connect keystore manager to keystore

« on: February 05, 2015, 06:12:44 pm »

Hi there.

We're having this very problem (file empty) every now and then, around twice a year. The sskeys.dat is suddenly empty.
As we have experienced this so many times, we now have several copies of the original file and just replace the empty one with the working copy. That works every time.

We think, that this problem might occur, when a user's EA is crashing while it tries to access/write to the file, but we aren't sure. Anyway, it's our best guess, and having a copy of the working file is the best solution we could come up with so far.

Edit: we're using the Corporate Edition, and I guess we normally have around 50 users at the same time.

11

Bugs and Issues / Re: Compare utility error - "The query is too comp

« on: October 31, 2012, 10:55:26 pm »

Thanks for your answer. I created a bug report using the topic header and its description. Let's see what happens.

12

Bugs and Issues / Re: Compare utility error - "The query is too comp

« on: October 31, 2012, 09:27:49 pm »

I still haven't found a solution. At the moment I am working in a way, that I instantly copy changes from the root document to the child document, after they have taken place. But this costs a lot of time and will not work anymore, as soon as others are using the root document as well.

No suggestion, anybody?

13

Bugs and Issues / Compare utility error - "The query is too complex"

« on: October 22, 2012, 07:39:36 pm »

Hi all,

when trying to view differences between my model version and a baseline, I always get the error "DAO.Database [3360] Query is too complex."
Is there any way to solve that?
As I still have a base version copy, I already thought of creating baselines for smaller packages - would that work?

Thanks in advance
Infyrana