This Specification Flow Task reads in multiline, two column data from a named sheet in an Excel file, and passes them into the specification for driving into constants or controls.
Microsoft Office and DriveWorks Live running as a service through IIS
Services (IIS) do not have access to many applications, especially COM programs such as Microsoft Word and Excel.
When using DriveWorks Live and IIS please read the following articles for information on where to place this Task.
|Title||Changes the Title (not the name) of the task.|
|File Name||File Name of the Excel File Including Extension.|
|Sheet Name||Sheet to pull the data from.|
|Show Excel||Workbook will be visible if set to True.|
|Return Constant||The name of the Constant that the named pairs will be posted to for reference.|
When this Task is added the properties are static. To be able to build rules on a static property see How To: Change A Static Property To A Dynamic Property.
|Property Name||Example Rule||Example Result||Meaning|
|FileName||"C:\MyDocuments\ExcelFiles\ExcelData.xlsx"||C:\MyDocuments\ExcelFiles\ExcelData.xlsx||This is the Full File Path for the Excel document to use.|
|Sheet Name||"DataToUse"||DataToUse||This is the name of the Sheet in Excel|
|Show Excel||TRUE||TRUE||TRUE to show the Excel Application when the Task is run.|
|Return Constant||"DWConstantReport"||DWConstantReport||This is the name of the Constant that the Task will report to with|
The Excel sheet used for the import needs to have two columns:
The Table containing the names and values should be positioned with the Name header in cell A1.
If a Constant is found with the same name (Not case sensitive) then the value from the second column will be passed into it.
If no Constant is found with that name, then DriveWorks will look for a Form Control with that name to pass the value to.
If no Control is found, then no action will be taken with that rows data.
If a Constant and Control exist with the same name the Constant will take priority.
Here is an example table showing how the data should be laid out.
This task supports Status Outputs. These can be used to perform different actions depending on what the status outcome of the task is. For more information see Status Outputs in the Task Node Outputs section of Specification Macros Task Node.
The status output navigation is as follows:
Success with Warnings
Failed (one of the following occurred).