Messages

1

General Board / Re: Package import : loss of links to other packag

« on: August 06, 2008, 07:17:26 pm »

Yes, you made yourself clear.  When stripping guids, the XMI file being imported must be fully self-contained because EA makes every guid in the file unique.

Hi, thanks for your reply.

However isn't it possible to include the GUIDs of referenced objects within the XMI file ? That would avoid redoing all the references by hand...

Is there another means to quickly restore the references once the package has been imported (within the same model as the export i remind you), aside from doing copy/paste as link and respecifying the instance classifiers ?

Thanks

2

General Board / Package import : loss of links to other packages

« on: August 05, 2008, 08:35:36 pm »

Hello,

Here is what I am trying to do.

I want to duplicate a package within the same model. For this, I first export my package using UML 2.1 or 1.3 (both won't work) and full EA tagged values.

Then I import the XMI file into the same model, while stripping GUID's so the elemnts from the XMI file will be created and EA won't issue an error (since the XMI files contains GUIDs that already exist in the model).

The problem is : when i'm doing this, any reference to elements that are outside of the package are lost (instance classifiers of objects, diagram links to elements that are outside the package...).

That is strange since these elements are still in the model, so if EA exported the package contents with references to those elements GUIDs, they should still be seen after importing.

Is my issue clear ? Did anyone else encounter the same issue and found a workaround ?

Thanks,

Thorkhas

3

General Board / Re: RTF numbering

« on: December 21, 2007, 06:49:55 am »

Hello,

I have more or less the same issue.

I have a package with the stereotype "model document" applied to it, to which i put several packages.

In my template I have :
1. Package

1.1 elemtn package

Both share the same list, so the numbering is correct.

However I get something like this :

I.1 Package1
 I.1.1 Element 1
   I.1.1.1 Sub element 11
   I.1.1.2 Sub element 12
 I.1.2 Element 2
   I.1.2.1 Sub element 21
 I.1.3 Element 3
I.2 Package2
 I.2.1 Element 21
   I.2.1.1 Sub element 211
   I.2.1.2 Sub element 212
 I.2.2 Element 22
   I.2.2.1 Sub element 221
 I.2.3 Element 23

This shows a consistent numbering. However I want the packages to start .. well, juste with ONE number :

I Package1
 I.1 Element 1
   I.1.1 Sub element 11
   I.1.2 Sub element 12
 I.2 Element 2
   I.2.1 Sub element 21
 I.3 Element 3
II Package2
 II.1 Element 21
   II.1.1 Sub element 211
   II.1.2 Sub element 212
 II.2 Element 22
   II.2.1 Sub element 221
 II.3 Element 23

And I don't really understand the white paper... it shows in itself a result like the one i'm having, and that is not correct numbering. Correct number should be something like "I. Pck1 // I.1 Elt 1" and not "I.1 Pck1 // I.1.1 Elt 1".

My packages have a number level of 1.

4

Automation Interface, Add-Ins and Tools / Re: RTF export : Classifier name in toc

« on: December 21, 2007, 12:58:23 am »

Looks like it only works for attributes in classes.

That is not a big problem.

I'm now trying to find how to include the little composite (infinite) sign on an element shape when they are indeed composite elements. I am using the shape editor, made me a nice shape but i no longer have those signs.

if (HasProperty("isComposite",true))
{
println("composite");
}

does work, as soon as i find how to include the little picture i'll be set

5

Automation Interface, Add-Ins and Tools / Re: RTF export : Classifier name in toc

« on: December 20, 2007, 08:16:37 am »

Alright, got it, the option is on the diagram properties. That does the job nicely.

Thanks a lot for your quick input !

Now I'll need to find out how to reorder elements within an activity, and it will be perfect so far, objects come first, then other activities, then decisions/mergenodes/activity initials and finals.

6

Automation Interface, Add-Ins and Tools / Re: RTF export : Classifier name in toc

« on: December 20, 2007, 07:42:52 am »

Thanks for replying.

Mhh i never thought of that. You think i should give a short alias to my classes so the objets show up as "Object Name : short class name" on diagrams and i can fully name objets ?

I can't seem to find out what alias are really used for in the doc though.

7

Automation Interface, Add-Ins and Tools / RTF export : Classifier name in toc

« on: December 20, 2007, 05:42:14 am »

Hello,

I am currently using EA in a reverse functional documentation project, mainly process documentation and how they relate to the IS.

There are many elements in the IS that have been modeled as classes, so we can easily find out which processes produce those elemnts. They are then instanced as objects in the process diagrams.

Since the name of those classes are pretty long, i don't give any name to the instanced objects.

I produced a RTF report on the processes; however they show up as anonymous and if I give them a short name, only the short name would display in the TOC of the export, making it ... not looking professional.

I wondered if I could tell EA to print the classifiers in the TOC. I tried to include {Element.Classifier} in the model, just after the {Element.Name} that is in the TOC. However that doesn't work, but i typed it so perhaps it comes from there; however i don't see how i can add template elements to the TOC.

I cannot simply create an object somewhere, and then use it on each diagram, because I used stereotypes to distinguis the fact they're created or used. So i need the objets on diagrams to be instanced.

Do you have any idea how I could include the classifiers' name in the TOC of an RTF export ? By the way i won't name the objets the same way as its classifiers, the diagrams would look messy - except if you can tell EA not to print the classifier of an objet in a diagram.

Thanks !