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

Pages: 1 [2] 3 4 ... 9
Excellent suggestion. Thanks for the link to that other thread. Lots for me to think about.

Has anyone found a way to create a document template that exports a relationship template to Word? I can get EA to print out a JPEG of the matrix easily enough but this is totally useless because it is so tiny as to be completely illegible. Does this require some kind of Ninja SQL skills?

Obviously there's the CSV export option from the Relationship Matrix itself but this has its own problems because it only outputs the names of the elements and none of their detailed attributes such as their notes.

I am performing requirements traceability and am amazed that this functionality seems to be so lacking!

Can you add tagged values to custom diagram types using an MDG Technology?

I have successfully added tagged values to model elements by creating attributes on the stereotype in the profile. When I try the same trick with a diagram it doesn't seem to work.

Has anyone managed to do this?

Uml Process / Re: Satisfy Dependency Stereotype behaviour
« on: January 16, 2017, 09:09:41 pm »
Geert - you are, as always, awesome 8)

There was a random stereotype defined for a note link. Once removed all is well.

Thanks - that was driving me mad!!!

Uml Process / Satisfy Dependency Stereotype behaviour
« on: January 16, 2017, 07:36:17 pm »
When I create a satisfy relationship between a block (as the source) and requirement (as the target), using the SysML 1.3 toolbox, EA applies the following stereotype: «sysML1.3::satisfy»

This seems to be the only relationship from the Requirements Toolbox that has this behaviour. All other relationships are rendered with they stereotype name only (no mention of the version of SysML they are taken from. Does anyone know why this happens and how it can be turned off?

If I turn off the SysML 1.3 MDG and enable SysML 1.4 then the problem seems to disappear but I don't want to change to SysML 1.4 if I can avoid it as we are mid-way through a project.

Automation Interface, Add-Ins and Tools / Re: Headers and Footers
« on: January 04, 2017, 02:54:36 am »
Additional info: when viewed in Word, the document that is created seems to have different headers defined for the first page, left page and right page. I don't want to vary anything - I just want every page header/footer to look identical

Automation Interface, Add-Ins and Tools / Headers and Footers
« on: January 04, 2017, 02:51:03 am »
In which RTF Template(s) should I create my headers and footers when generating documents?

Presently, I have created them in my Cover Page only. When I generate the document, the cover page contains them, but none of the subsequent pages do... what am I doing wrong?

Using EA13 but still constructing documents using the Master Document (rather than Report Package) element

Automation Interface, Add-Ins and Tools / Re: Nesting Master Documents?
« on: December 27, 2016, 03:24:20 am »
There's a bug in ea 12.1 that means the report package doesn't work. Sparx advised me not to use it

Uml Process / Find and Replace
« on: December 23, 2016, 12:03:03 am »
Is there any way to perform a find and replace for a text string within the "Notes" of an element?

Any of you scripting gurus got any suggestions if not?


Shame - thanks!

Does anyone know how diagram fragments can be used to display diagrams in a a virtual document?

I can create an SQL query to find the package that contains the diagram easily enough... but I then need to display the diagram image for the diagram that is located inside the package.

Do I need to return a specific field from a table in the database? If so, which database table actually stores the image?

Automation Interface, Add-Ins and Tools / Nesting Master Documents?
« on: December 02, 2016, 12:29:01 am »
I am creating a virtual document using a «master document» package containing a series of «model document» elements. I'd like to be able to group these model documents to allow me to control the structure of the document more easily. Is it possible to nest, or combine two separate «master document» packages into a larger document?


Excellent - that worked a treat!

Can anyone suggest an SQL query that would be able to link a message on a sequence diagram to the actual operation on the block which classifies the lifeline.

The connector that represents the message the diagram has the same name as the operation, but... It also has parenthesis after the name. This means that trying to do an SQL JOIN statement doesn't work, since the name of the actual operation excludes the parentheses.

I'm no SQL guru so there might be a clever way to construct the query... Or perhaps there is another table with the info...?

Let's say I have two diagrams and want to export them to a document.

Diagram 1 has blocks A and B
Diagram 2 has blocks A and C

I want to construct a template that outputs the "notes" from each block underneath each diagram. But, ideally, I only want to export those notes once.

So, when the exporter gets to Diagram 2, it only outputs the notes from block C (because it previously exported block A)

Does anyone know of any sneaky ways to get EA to do this? Some kind of script that keeps track of the number of times an element has been found during the export process before?!?

Pages: 1 [2] 3 4 ... 9