Messages

1

Bugs and Issues / Re: Import/Export XMI file

« on: May 16, 2009, 10:48:44 am »

i'm running into an issue with importing and exporting from XMI as well.  I have a package with a master document, and model documents i'd like to export from one model and then import into another.  pretty basic stuff.  i read the instructions and used default settings and it looked like the export succeeded.  

seemed so easy.  so then i tried to import.

i get the following message:
error:
code = 0xc00ce00e
The attribute 'xmi.idref' with namespace "...." which is not define anywhere in the document.

what does this mean?

even importing into the same model in a different package i get this error.

2

Automation Interface, Add-Ins and Tools / Re: query for specific tagged value

« on: May 16, 2009, 07:34:49 am »

kris,
good idea, that would work too.  i only tried it this way because i thought it would let me be a little more flexible on some filtering i wanted to do.  

i was hoping there was some way to do filtering on requirement type from within the external requirements tag.  but this doesn't seem possible

3

Automation Interface, Add-Ins and Tools / Re: query for specific tagged value

« on: May 13, 2009, 12:33:19 pm »

thanks dermot.

using your suggestion for reply #7 was very helpful, i was able to only ask for the target elements by setting the direction to source->target.  when would you ever have target->source?

4

Automation Interface, Add-Ins and Tools / Re: query for specific tagged value

« on: May 12, 2009, 09:20:47 am »

i've also observed the following:

use case is connected to (points to)  requirement A.
requirement A is connected to another requirement B.

when printing connector->target->element->name for requirement A,
you get:
Requirement A
Requirement B

Requirement B is the only REAL target for requirement A.  But Requirement A is the target of the Use Case.  Why does EA not distinguish between these two cases?  Does it simply look at all Connectors involving Requirement A and publish the targets without first checking to see if Requirement A is the source?

5

Automation Interface, Add-Ins and Tools / Re: query for specific tagged value

« on: May 12, 2009, 06:26:24 am »

i tried generated from the model directly and the exclude Connector options seem to apply.  However, using virtual documents F8 | Options seem to be ignored.  How can we have model documents exclude connector types?

6

Automation Interface, Add-Ins and Tools / Re: query for specific tagged value

« on: May 09, 2009, 10:49:57 am »

so far that doesn't seem to have any effect.  I excluded all connectors and i still get the same result.

on another note, here's an interesting result: i created a dummy requirement in a use case. i trace it to another requirement. via Relationship matrix.  when i print the dummy requirement out, i am printing its connector->target->element->name.  I get the right dummy requirement parent.  But I also get the dummy requirement itself.  what's the meaning of this?

7

Automation Interface, Add-Ins and Tools / Re: query for specific tagged value

« on: May 08, 2009, 09:32:20 am »

also, this is being generated in a model document.  this model document already has a filter set on it to return all use cases.  what i need now is a way to filter parts of the template or do some conditional expression while the template 'iterates'.

is this possible??

8

Automation Interface, Add-Ins and Tools / Re: query for specific tagged value

« on: May 08, 2009, 09:30:03 am »

sorry i should have been more clear.

for example, i have a use case.  it has connectors to the requirements it realizes, and one connector to the actor of the use case.

i only want to print the requirements associated with the use case.  but the template only allows me to get all the connector->target->elements, not just some of them.

how would i only print the requirement targets for this use case?

9

Automation Interface, Add-Ins and Tools / query for specific tagged value

« on: May 06, 2009, 04:59:06 am »

is there a way to ask an element for a specific tagged value? can we do such things as conditional statements in the RTF template? such as

if(element == usecase) ...

otherwise, how to separate use cases from other elements? i would like to do something like

Usecase
Requirements from this UseCase

Thanks

10

Automation Interface, Add-Ins and Tools / filtering connected elements

« on: May 13, 2009, 12:29:56 pm »

hi,

is there a good way to filter connected elements?

in a template for a model document, let's say we are accessing the target element of several connectors.  the target elements are requirements, but they could be of
different types, such as system or derived.

I have a Search on this model document returning UseCases.  Within these UseCases are the connected requirements I would like to filter on requirement type.  I've tried creating filters on requirement type via Document options but this doesn't seem to apply to those elements.

Any ideas?

Thanks

11

Automation Interface, Add-Ins and Tools / not printing blank values

« on: May 12, 2009, 03:08:17 am »

Hi,

Is there any way to specify not to print if the value queried is empty?  Such as if I am trying to print the Alias field for an element and it's empty, is there any way to print nothing for that?

Thanks

12

Automation Interface, Add-Ins and Tools / template flexibility

« on: May 08, 2009, 11:37:28 am »

hi

does the template allow for us to specify what fields we want for which elements?

if i want to show the connectors for use cases but not actors, is this possible?  it seems we define what we want to see for all elements.  this does not seem to be very flexible in what we're allowed to generate.

if I were to use virtual documents, this would only allow me to do the following format:

all use cases
all actors

instead of what I would like:

usecase
actor
usecase
actor

is there a way around this? why are all elements treated the same?

13

Automation Interface, Add-Ins and Tools / Re: duplicate table headers

« on: May 07, 2009, 04:14:43 am »

that's the thing, i have no extra blank lines anywhere, my template is

package>
element>
Table header
content
<element

but the header is still repeated in each row.  the whitepaper only mentions that leaving an extra blank line below the table will cause a 'space' between rows, not repeated headers

14

Automation Interface, Add-Ins and Tools / duplicate table headers

« on: May 06, 2009, 08:56:30 am »

i'm trying to generate a table listing all use cases.  in the template, the table has a row for headers, and one for the fields. however the table headers get repeated for each element.  i did the same thing listing the scenarios and the table headers don't get repeated.  why is it different?

15

Automation Interface, Add-Ins and Tools / Re: list numbering styles

« on: May 07, 2009, 10:12:38 am »

Thanks

I was able to get it to work