This has probably been asked here before, but my search within the forum didn't turn it up... well, not within the many non-related results, anyways.
Is there a way to have "Export to Word" append an attribute column instead of putting it on a new line?
e.g.: current:
Object Text Here
AttrName: AttrValue
I want:
ObjectTextHere AttrName: AttrValue
I am aware I could set up a WORD macro to fix this, but we would rather set it up so DOORS gets it right the first time, to reduce the possibility of user error.
Thanks.
evandy - Tue Aug 31 14:35:16 EDT 2010 |
|
Re: Append attributes during export
SystemAdmin - Wed Sep 01 14:29:58 EDT 2010
You can do one of two things, depending on what you are asking. If you want an actual column, you can create a view with the attribute column after the object text and then use the Table option when exporting to Word. If you just want to append the attribute to the end of the object text, like appending the Object ID to the end of an Object Text requirement, then you can find word.dxl (located at a path similar to this: \lib\dxl\standard\export\office) and create an enhanced Word export by modifying the file to append the attribute.
|
|
Re: Append attributes during export
evandy - Thu Sep 02 08:42:58 EDT 2010 SystemAdmin - Wed Sep 01 14:29:58 EDT 2010
You can do one of two things, depending on what you are asking. If you want an actual column, you can create a view with the attribute column after the object text and then use the Table option when exporting to Word. If you just want to append the attribute to the end of the object text, like appending the Object ID to the end of an Object Text requirement, then you can find word.dxl (located at a path similar to this: \lib\dxl\standard\export\office) and create an enhanced Word export by modifying the file to append the attribute.
Since applyStyleLockPasteInvoke seems to automatically include the \par RTF tag, ere's what I've done so far:
1) Modified wordDumpBodyVBA and wordDumpColumnValueVBA to return the text they gather, instead of passing it directly to applyStlyeLockPasteInvoke. Each method filters the output string through richTextFragment() before returning it.
2) wordDumpObjectVBA concatenates all the strings for an object returned by the 2 modified methods in step 1. (It still handles headings in the original manner. No reason to muck with that, I think)
3) The concatenated strings are passed through a method which calls applyStyleLockPasteInvoke with all the original error handling.
This works just fine for anything that doesn't have an embedded OLE object, but OLE objects are not included in the output, so I'm obviously missing something here. Any guidance?
Attachments
attachment_14527751_word-export.dxl
|
|
Re: Append attributes during export
SystemAdmin - Thu Sep 02 10:12:40 EDT 2010 evandy - Thu Sep 02 08:42:58 EDT 2010
Well, I have a partially-working word.dxl that does what I want. However, it doesn't seem to handle OLE objects well (in fact, it drops them entirely).
Since applyStyleLockPasteInvoke seems to automatically include the \par RTF tag, ere's what I've done so far:
1) Modified wordDumpBodyVBA and wordDumpColumnValueVBA to return the text they gather, instead of passing it directly to applyStlyeLockPasteInvoke. Each method filters the output string through richTextFragment() before returning it.
2) wordDumpObjectVBA concatenates all the strings for an object returned by the 2 modified methods in step 1. (It still handles headings in the original manner. No reason to muck with that, I think)
3) The concatenated strings are passed through a method which calls applyStyleLockPasteInvoke with all the original error handling.
This works just fine for anything that doesn't have an embedded OLE object, but OLE objects are not included in the output, so I'm obviously missing something here. Any guidance?
Attachments
attachment_14527799_exportwordIDs.dxl
|
|