This document type is used to export data directly in to a Microsoft Word document from the DriveWorks project.
DriveWorks can attach to and extract bookmarks in a word document which can then be driven using rules.
DriveWorks can use .doc, .docx and .docm files.
Files saved as an .docx are the quickest to generate as DriveWorks does not need to open Word.
In DriveWorks Administrator open the project the document is to be applied and go to Stage4: Output Rules> Documents
If the Document Path is not set then the file will be created in the specification folder.
Data arrays can be driven into tables in Microsoft Word documents.
When a bookmark exists in a cell of a table (in Word), and the rule applied to the captured bookmark results in a data array, DriveWorks will drive each cell in the table to the corresponding value in the array.
If a bookmark is outside of a table, but has an array value applied, then this bookmark will be not be driven.
If a bookmark is within a table, but does not have an array value applied, then this value will be driven as normal into one cell.
Bookmarks in table cells will be driven slightly differently, depending on whether the bookmark is in a single cell, or if it spans multiple cells.
If a bookmark is placed in a single cell then DriveWorks will:
Bookmarks that span multiple cells can be created in Word. If this is the case then we will:
To preserve any formatting applied to a table it is important to understand the Document Generation Types that DriveWorks uses.
There are two methods of driving Word documents:
This also applies to:
Table formatting is preserved when documents are generated using the OpenXML method only.
Macro enabled documents (.docm files) are driven using OpenXML and then opened in the application to run the macro. This is to maintain as much table cell formatting as possible.
The legacy .doc file format contains very little formatting information. This means that if there is more data in the array than there are rows in the table, those rows may not maintain the formatting that is expected. For example, adding rows into a table that has alternating row colors will cause a new row to be added with the same row color as the previous one.
Previewing a .docx file, which uses the same document generation type as a .doc file, maintains alternate row colors. This is due to the .docx file format containing the required formatting information.
To have the best chance of preserving formatting it is recommended to either use a .docx or .docm file, or make sure there are enough rows for your data in the table in Word.
Overlapping bookmarks can be created in Word documents. Although they will still be driven, it is not a supported scenario in DriveWorks and therefore the result may differ between the two document generation types.
An entry into the specification report will be added if an overlapping bookmark is encountered when generating the document through the Word application.
The scenario can arise where an overlapping bookmark is being found but there are no visibly overlapping bookmarks in the document. This is a known issue with Word documents reporting intersecting bookmarks incorrectly.
If this is the case, the entry in the report will detail the bookmarks that overlap. The recommended solution is to ensure that just the text that is to be replaced has been highlighted when creating the bookmark and not the whole line.
DriveWorks will automatically execute a macro called CreateReports, after driving all the captured cells and prior to the new document being saved.
The Word document is triggered in the specification flow by the Release Documents task.