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 - Simon M

Pages: 1 2 [3] 4 5 ... 415
I think an XMI import includes references (GUID) to out-of-scope elements, so that they can be resolved if the referenced elements are present in the target project, but I think the import ignores those that cannot be resolved. I may be wrong on this.
There is an option to create placeholders for external references. If you use this and then later import the package containing those elements, it will restore the links to those elements by the packages imported earlier.

General Board / Re: Repository security
« on: November 28, 2017, 08:16:57 am »
Was hoping to have time to look into it with the recent offer Free: Pro Cloud Server Express but alas other urgent things keep drawing my attention away from it.
The express version doesn't offer that capability. However, you can contact sales to organize a trial.

The problem isn't that a profile has been used to define the language. It's how to display, edit and report on user defined fields that EA has no knowledge of. Ultimately, regardless of how the language is defined, you are going to end up with a list of properties. ie. It's going to look like our tagged value list. As for the stereotype display, there's probably no reason why we couldn't display to the user no stereotype if the stereotype defines a metatype.

Defining validation rules for connectors and properties isn't something that is in the current profile language. (Although we have been doing a bit in that direction in version 14 if you look at the recent webinar)  But that doesn't have anything to do with how the language is defined. If it was added into existing profiles, it provides exactly the same advantage to users.

The only "extra" work defining profile for a language requires is extending a base UML metaclass. If you want to ignore UML, I'd choose 'Class' and 'Dependency'. Because of the database schema you're working with, you would still need to make that decision if you weren't creating a profile)

Bugs and Issues / Re: EA 11 and Windows 10
« on: November 23, 2017, 08:47:09 am »
As far as I am aware there is no way to make them co-exist.

Bugs and Issues / Re: Diagram View Crashes App
« on: November 22, 2017, 09:43:10 am »
I'd recommend contacting Sparx Systems support directly.

I then tried deleting the diagram, creating a new one, and dragging the package elements onto it; but that also caused the app to crash.

This is what I see as the key point. One (or more) of the elements being added to a diagram are causing the crash. It's likely that our support team will need a sample of your model to reproduce the problem. Depending on how much time you want to invest vs concerns with sharing your model with us you can attempt to cut down the problem by adding only a subset of the elements to the diagram and checking if it crashes.

The latter, which effectively changes the condition from contains to equals.
Equals is a completely ineffective as a description for the behavior you are after.

Regardless, what you are after doesn't exist.

You mean set the condition to 'Equal To' instead of 'Contains'?

Or do you mean that you want whole word only?

General Board / Re: Is this possible host Web EA in a linux server?
« on: November 15, 2017, 08:23:55 am »
WebEA is tested under Apache for Linux as well as Windows.

You still need to run the Pro Cloud Server on Windows (although I have successfully run it under Wine)

Code: [Select]
%list="Attribute" @separator="\n" @indent="\t" attStereotype == "Stereotype_A")%

In the EA API and database schema, all tagged values are a string. The different types determine what editor the gui uses and how they are displayed in the gui.

I just checked the format that EA uses to save the date... And it's pretty much the worst possible case. It depends on the locale settings for the machine where the date is saved. I'm not sure that can be practically changed now.

Standard Windows functions are being used to read the dates, which is why the behavior changes when the string isn't a valid date in the current locale.

General Board / Re: how to document EA model in two languages
« on: November 09, 2017, 04:03:14 pm »
I didn't forget that.

I'd rather have the translations missing formatting and have a clear distinction between them with each one in a logical place.

I recently saw a scenario where someone was doing the same thing with constraints to keep formatting, unfortunately that's not a strategy that works. You could use scenarios as a field with formatted text. It's not my personal preference because it's just a manual thing to create a scenario of the right name/type, the metadata is separated (or not there) and it's not obvious to a reader what is happening.

Bugs and Issues / Re: EA Trial on MacOS / wine / Core Dump!
« on: November 09, 2017, 02:35:21 pm »
Hi sailkrish,

I'm personally far from an expert at anything MacOS related.

I'd recommend contacting our support team directly using the 'Report a Bug' link at the bottom of this page.

The link provided shows the setup steps, although I'm not sure of the variation between the brew instructions on that page and the steps on our page. I'm not sure what other information our support team would require to determine why it's failing on your system.

General Board / Re: how to document EA model in two languages
« on: November 09, 2017, 08:52:43 am »
If I had to support a model in multiple translations my starting point would be to create a stereotype extending Element for each translation.

In each one I would add tagged values for Name and Notes. Depending on requirements I would also add TranslationDate, Translator.

That would at least make it possible to manage the translations. With the way the specification manager handles memo tagged values and grouping in the tagged value window it wouldn't even be too ugly.

Sorry, I haven't been able to determine that either.

Using the Query Builder, is it possible to create searches that can use more than one tagged value?
Unfortunately, no. It can only build queries using a single record for each table used.

Adding for example the Element Name more than once will make the query not work (I guess it will create a AND in the SQL, but of course you'd expect an OR here; except when using wildcards you might want an AND).

That depends on whether you have marked both entries as required or not.

Pages: 1 2 [3] 4 5 ... 415