DriveWorks has the ability to create Data Documents (no physical file is created) such as writing data to a DriveWorks table or external database.
The Documents - Data Task provides you with the ability to add Data Documents to your Project.
The Documents list can be filtered by using the filter at the top of the list.
Please see the topic How To Use Filters for more advanced filtering information.
Open the project and go to Stage4: Output Rules.
Please refer to the Document Types section below for information specific to the Document being added.
Please refer to the Document Types section below for information specific to the Document being edited.
The name of the document is displayed at the top of the edit window.
The Notification Area also displays the name of the document, its status and how many elements the document contains.
When performing a Task that saves the Project you are notified if an item within another Task is currently being edited.
Tasks that will cause the notification to appear include:
The message displays the name of the item under edit and the Task it can be found in.
All items currently in edit mode will be listed.
When changes made to a document are cancelled the following prompt will appear:
This gives the option to commit the changes if Cancel was mistakenly selected.
The options available on the Cancel dialog are:
This selection is reset when DriveWorks is closed and reopened.
Alternatively, double click the Document name to begin editing.
The types of Document - Files that can be driven are listed in the table below:
|Export to Calculation Table||Exports rows to an existing Calculation Table in the Project.|
|Export To Group Table||Exports data to a Group Table.|
|Export To Simple Table||Exports data to a Simple Table that will be available for the existing Specification only.|
|ODBC Data Export|
DriveWorks has the ability to export data to an external database (using a Microsoft Windows ODBC connection) as part of running a DriveWorks Project.
|SQL Server Data Export|
DriveWorks has the ability to export data directly to a SQL Server database as part of running a DriveWorks Project.
|Triggered Action||A Triggered Action allows a Specification to Transition to a State once a specified file has been created.|
The order Documents are created for a new Specification can be controlled by modifying the Default Specification Flow, see example of this here How To: Change Document Generation Order.
The generation of Documents in the Specification Flow is triggered by the Release Documents Task.
See How To: Modify Specification Flow for information on adding a Task sequence to a State.
Multiple Documents are added to the Task sequence by using a pipebar delimited list (DocName1|DocName2|etc..).
The order the Documents appear in the string is the order they will be generated.
Alternatively the order each Task sequence appears in the list of Task sequences for a given State is the order that Task will be performed.
ODBC Data Export Document
DriveWorks treats any ODBC Data Export as a Document, but the timing of this taking place is set independently of the Document generation timing. The Time to Export setting applied in the ODBC Data Export wizard is the time the export is done.
Take care the Time to Export setting for the data export does not conflict with any settings applied to a customized Specification Flow.