Author Topic: Outputing Linked Word docs using the RTF Generator (Read 8385 times)

John T. · « **on:** October 02, 2006, 11:25:33 am »

I have a need to include documents (e.g. a Word document), that have been linked to an element (e.g. an use case) using the "files" tab in the properties of the element, when generating a RTF document using the RTF generator.

If anyone knows whether this is achievable or not or better still has a template example, I would me most grateful.

Thanks

John

Jan ´Bary´ Glas · « **Reply #1 on:** October 02, 2006, 11:20:38 pm »

Sorry, I don't know about a way doing it. The file is not in the repository as far as I know.
Other option is not to use Files tab but Linked document (RTF only).

Weedman · « **Reply #2 on:** October 31, 2006, 01:55:53 pm »

We have this need as well. It would be of great benefit to us.

Jeff Weedman

louis · « **Reply #3 on:** November 17, 2006, 03:42:53 am »

Hi,

I have the same problem.

I would be grateful too, when someone can help.

The problem is that linked objects do not apear in export (rtf,XMI) and also not in HTML documentation.

Regards,
Louis

«Midnight» · « **Reply #4 on:** November 17, 2006, 05:28:04 am »

The files are stored in zipped form (somewhere) in the repository. This - the format and the fact that the content is not available from Windows - has been a source of confusion before (search the forum and you'll see). I don't remember seeing an easy solution. Nor does there seem to be an API function from within EA to handle this.

You could probably drag the information out somehow, and then use Windows API functions (or a third-party) package to get at the content. It sounds like a bit of work, but you could probably handle everything with a bit of VBA from within MS Word.

peter.zrnko · « **Reply #5 on:** November 17, 2006, 12:44:16 pm »

I think the last answer

Quote

The files are stored in zipped form (somewhere) in the repository.

is about linked documents, that are stored internaly in EA repository.
While the rest of this thread is about files (files tab of element properties).

Linked documents could be a part of rtf or html export, but it is a problem to access them from outside of EA project.

Files (files tab) cann't be part of rtf and hrml export. It is no problem to access them from outside of EA project.

«Midnight» · « **Reply #6 on:** November 21, 2006, 05:00:25 am »

Oops, I stand corrected!

louis · « **Reply #7 on:** November 29, 2006, 08:30:24 am »

Does someone know how I can make or become a program what export/import embedded linked documents.

I tried something with odbc and I indeed found out that the format a linked document is stored in EA is a kind of ZIP. After unzipping it was a bit readeble.

alesliehughes · « **Reply #8 on:** November 30, 2006, 02:50:05 pm »

In the next build (801), the Automation Interface has been extended so you can get the Linked Document of an Element.

Alistair

louis · « **Reply #9 on:** November 30, 2006, 11:45:20 pm »

I 'm sorry but I don't know what an Automation Interface is.

Is the linked document also a part of the xmi-export in the next build(801)?

Eve · « **Reply #10 on:** December 03, 2006, 01:12:54 pm »

Quote

Is the linked document also a part of the xmi-export in the next build(801)?

Yes it will, but it already is.

Look for '<modelDocument xmlns:dt="urn:schemas-microsoft-com:datatypes" dt:dt="bin.base64">' in XMI 2.1 and '<UML:TaggedValue tag="modeldocument" xmlns:dt="urn:schemas-microsoft-com:datatypes" dt:dt="bin.base64">' in XMI 1.1.

louis · « **Reply #11 on:** December 04, 2006, 01:05:25 am »

Thanx.

You help me very wel.

Another question. In a project I want to offer all the linked documents to a "translate-factory". After translating I want to restore the documents in EA.

Now I do it as follows:
- I make an RTF - report including al the linked documents.
- The document is translated
- All the parts of the translated document I cut and paste to the right place in the project.

I think someone has a better suggestion for this. For example when I can create a readeble document from the linked-document-part of an xmi-export, and after translating put it back in xml then I am very happy.

louis · « **Reply #12 on:** December 15, 2006, 02:51:24 am »

I have another problem with linked documents in combination with odbc. I use a odbc connection to a progress 100b database. When I want to change a linked document and press save I get next message:

Microsoft OLE DB Provider for ODBC Drivers [-2147467259]
[DataDirect][ODBC OPENEDGE driver][OPENEDGE]Invalid date value (7496) Error in parameter 1.

Has anyone an idea?

«Midnight» · « **Reply #13 on:** December 15, 2006, 05:52:40 am »

Have you selected the Jet 4.0 engine option on the Tools | Options main page? If not, try changing it.

Please let us know if the problem persists.

louis · « **Reply #14 on:** December 15, 2006, 06:15:56 am »

At this moment it is not possible. When you use linked documents, in fact they are embedded, they are represented in the genereted documentation. HTML as wel as RTF

Sparx Systems Forum

News: