...
The form provides the standard form icons.
Extra buttons:
 | HELPDEVTODO: not yet added If a valid location has been configured in the file collector to locate an existing CSV file, the user can click on a button at the top of the grid to automatically create the file column descriptions in this form. The column names are taken from the first row of the file. To construct the name all invalid characters are stripped out of the value found in each cell and the result is assumed to be the name of the column. The remaining rows are examined to try to determine the type and length for each column definition based on the values found in the file. If a type cannot be determined then the column is defined as a string. The length of the field is set to be the length of the longest value found. |
...
| Field | Type | Description | ||||||
|---|---|---|---|---|---|---|---|---|
| Name | Text | The name of the file collector. | ||||||
| Enabled | Checkbox | Tick when the configuration is complete and the file collector is ready for use. | ||||||
| Source Type | Dropdown | This field can have any of the following values:
| ||||||
| Number of Header Lines | Text | The number of lines in the header of the file. These are ignored when reading the file. (This option is not available for Binary File, XML and HTML file types). | ||||||
| File Type | Dropdown | Can have values:
| ||||||
| Allow Non-Scheduled Collection | Checkbox | If this is turned on, then the collector will run as part of any ad-hoc Analysis Engine run which requires this data. If not, it will only run as part of a scheduled task under the Analysis Engine. | ||||||
| FTP Site | The FTP Site on which the import file is stored. If no site is specified then the file is assumed to be on the local machine. If a site is specified then all directory paths specified on this form should be the full path to the file since the base directory specified in system configuration is ignored (since the base directory is specific to the local machine). | |||||||
File Location Strategy | Drop-down | Can have values:
| ||||||
| Tag | Text Expression (special case: only string literals allowed, no PhixFlow variables) | This field is only available if the Source Type field is set to Managed File. When files are uploaded by PhixFlow they are placed into a directory whose full path is a combination of the root File Upload Directory (specified in System Configuration on the System Directories tab), the tag value specified here and the Input Directory specified below (hard coded to 'in' for Managed files). If you are creating a file collector to load email messages and/ or attached files, you can specify a tag here if one has been provided in the subject line of the incoming emails. See How To: Read data from an email account for further details. | ||||||
Ignore Base Directory | Checkbox | This field is only available if Source Type = Specified Directory. Normally the base directory, specified in the "System Directories" tab of the "System Configuration" screen, is prepended to all directories specified on this form. However, if this flag is ticked then this does not happen and the directories specified on this form alone are used as the full path specifications for the import file. | ||||||
| Input Directory Expression | Text Expression | Source Type = Specified DirectoryIf the Source Type is Specified Directory, files will be ready from the directory specified in Input Directory Expression. Unless the flag Ignore Base Directory is ticked, the path specified in this field will be added to the default input directory root - this is specified in the System Configuration File Upload Location. If the flag Ignore Base Directory is ticked, the full path for the input directory must be specified. In fact, this field is an expression. This must evaluate to a plain text string. In the simple case, this will be text surrounded by quotes, e.g.
Also, because this is an expression, you must always use / rather than \, even on windows platforms. You can include PhixFlow variables in this expression, e.g.:
If you need to include wildcards or some other variable element in the resulting path, you must use the Directory Pattern Expression. If File Location Strategy = All Files in Folder PhixFlow will look in this directory to find files matching the pattern specified in File Pattern Expression. If File Location Strategy = Read Names this is added to the start of the file location read from the file name attribute. Source Type = Managed FileIf the Source Type is Managed file, this will contain a non editable value of "in" | ||||||
| Directory Pattern Expression | Regular Expression | This field is used to identify valid sub-directories of the input directory. If a Directory Pattern Expression is provided then PhixFlow will not only check the Input Directory for files but will also check all sub-directories of the Input Directory. Each file found will then not only have its name checked against the File Pattern Expression but will also have the relative path from the Input Directory to the file (referred to as the sub-directory path) checked against the Directory Pattern Expression. For example, suppose the Input Directory has the sub-directories: 'region1/teamA'; 'region1/teamB'; 'region2/teamA'. If you want all the files across all regions for teamA, but not teamB, then you could use the following Directory Pattern Expression to pick out just the files for teamA: ".*/teamA/" Alternatively, if you wanted all the files for all teams in region 1 only, you could use the following Directory Pattern Expression: "region1/.*" Regular expression rules are used to perform this match rather than the sort of pattern matching rules you might be used to when listing files. For example:
A number of internal variables are available in these expressions:
Note that there are also a number of predefined compressed file expressions that will always be checked to determine if a file within a valid sub directory is actually a compressed file. If so then this file will assumed to be a valid compressed file and hence will be recursed into as if it was a standard matching directory. Please see Compressed Files for a list of valid compressed file expressions. | ||||||
| Exclude Dir. Pattern Expr. | Regular Expression | This field can be used to exclude certain sub-directories found by the Directory Pattern Expression. For example, suppose the Input Directory has the sub-directories: 'region1/teamA'; 'region1/teamB'; 'region2/teamA'. If you want all the files across all regions for teamA, but not teamB, then you could use the following Directory Pattern Expression to find all files: ".*" combined with the following Exclude Dir. Pattern Expr to exclude those for teamB: ".*/teamB/" Regular expression rules are used to perform this match rather than the sort of pattern matching rules you might be used to when listing files. For example:
A number of internal variables are available in these expressions: | ||||||
| File Pattern Expression | Text Expression | This field is only available if File Location Strategy = All Files in Folder. An expression used to generate a list of files to be read. This expression must itself resolve to a Regular Expression, used to match files in the input directory. Note that regular expression rules are used to perform this match, not the shell replacement style rules used in many file systems. E.g. to match all files, you must use ".*" and not "*". A number of internal variables are available in these expressions:
Examples: "inputRecords.txt" will read files called "inputRecords.txt" from the input directories. ".*" will read all files in the input directories. ".*\\.txt" will read all files in the input directories with the extension ".txt" "teamA.*" will read all files in the input directories starting with "teamA." "record_" + toString(now(),"yyyy-MM-dd") + "\\.txt" will read files in the input directories with the format "record_yyyy-MM-dd.txt", where yyyy-MM-dd is the current date. E.g. "record_2013-03-26.txt". "("+listToString(_context.f,"|")+")" will read files with name contained in the list of files uploaded by the Stream Action which caused the File Collector to run, but only if a Context Value called 'f' is set in the Action and its value expression is '_files' | ||||||
| Archive Directory Expression | Regular Expression | If set, processed files will be written to this directory. This field is an expression that must resolve to a Regular Expression. Note that because this is an expression field, if you supply a simple directory definition in plain text it must be surrounded by quotes. Also, directory separators must be / and not \, even if the file is being moved to a directory on a Windows platform. E.g. "C:/data/address/archive/". | ||||||
| Error Directory Expression | Regular Expression | If set, files that error during processing will be written to this directory. This field is an expression that must resolve to a Regular Expression. Note that because this is an expression field, if you supply a simple directory definition in plain text it must be surrounded by quotes. Also, directory separators must be / and not \, even if the file is being moved to a directory on a Windows platform. E.g. "C:/data/address/error/". | ||||||
| Local Archive Directory | Checkbox | For files retrieved via FTP, whether the archive directory is on the PhixFlow server (local) or on the original server. | ||||||
| Local Error Directory | Checkbox | For files retrieved via FTP, whether the error directory is on the PhixFlow server (local) or on the original server. | ||||||
| Advanced | ||||||||
| Maximum Files | Text | Specifies the maximum number of files that will be processed whenever the collector runs. | ||||||
| Minimum Files | Text | Specifies the minimum number of files that are expected to be found whenever the collector runs. If fewer files are found then this is treated as an error. | ||||||
| Max Records Per File | Text | Specifies the maximum number of records that will be read from each file processed. | ||||||
| Text | The maximum number of errors PhixFlow will permit during the processing of a file before. Once this number has been exceeded, PhixFlow will abandon the attempted file load. See error handling summary below. | ||||||
| Parallel Readers | Text | The number of files to process in parallel. If blank, this defaults to 1.If the collector is configured to read files in sequence, this field is ignored and a single file reader is used. | ||||||
| Next Sequence | The next sequence number expected to be found within the name of the file being imported. This field is only available if File Location Strategy = All Files in Folder. | |||||||
| Unreadable Directories | Drop-down | The action to take on finding an unreadable directory when searching a directory hierarchy for files to import.
| ||||||
| XPath Expression | XPath | This field is only available if File Type = XML File or HTML File This field should be populated according to valid XPath syntax. Please see XPath Examples for how to use XPath expressions and how the returned data can be used and evaluated in the corresponding stream attribute expressions. | ||||||
| Character Set | Text/ Dropdown | The character encoding to be used. Select a value from the drop down list. If Other if selected, a new box opens and a new character set can be entered. Full list of available character sets can be found here (Canonical Names from both columns can be used). | ||||||
| Column Separator | Text/ Dropdown | Select a value from the drop down list. If Other is selected, a new box opens and a new column separator can be entered. | ||||||
| Separator Character | Text | This field is only available if Column Separator = Other. Allows a custom column separator to be entered. | ||||||
| Quote Style | Text/ Dropdown | Select a value from the drop down list. If Other if selected, a new box opens and a new quote character can be entered. | ||||||
| Quote Character | Text | This field is only available if Quote Style = Other. Allows a custom quote style character to be entered. | ||||||
| Checkbox | This field is only available if File Type = Comma Separated Values. If this flag is set then PhixFlow will not throw an error if the record being read contains more columns than expected. If this flag is not set then an error will be reported if there are too many columns. See error handling summary below. | ||||||
| Checkbox | This field is only available if File Type = Comma Separated Values. If this flag is set then PhixFlow will not throw an error if the record being read contains fewer columns than expected. If this flag is not set then an error will be reported if there are too few columns. See error handling summary below. | ||||||
| Import Rows Matching | Regular Expression | PhixFlow will attempt to match each line in the file against the expression, and only those that match will be imported. | ||||||
| Replace Text Matching | Regular Expression | In each imported line, replace all occurrences of the text matched with Replace Text Matching with With. | ||||||
| With | Regular Expression | See description of Replace Text Matching above. | ||||||
| Excel Data Expression | Expression: List | This field is only available if File Type = Excel Spreadsheet. This field is an expression that must evaluate to a list of ranges with the format "WorksheetName!TopLeftCell:BottomRightCell" If this field is left blank, PhixFlow will read the first worksheet it finds in the excel file (even if this is a hidden sheet) with a range covering the whole sheet. E.g. if just a single range is needed: "DailyCallsSheet!A1:G100" E.g. if a list of ranges is required: ["DailyCallsSheet!A1:G100", "A1:B20", "Calls!A1:C100"] Remember that in all cases PhixFlow will only read the columns that have been defined in the File Columns tab. Because this field is an expression, the resulting list can be generated with any valid PhixFlow expression. You can also use the internal variable _worksheets which gives you the list of worksheets that PhixFlow found in the file. See the example below for how you might use this. Examples
do ( $rangeList = [], forEach($sheet, _worksheets, if ( listContains(["sheetA", "sheetB"], $sheet), addElement($rangeList, $sheet + "!A1:B10") ) ), $rangeList ) This expression will evaluate to the list of a maximum of two ranges, if both worksheets sheetA and sheetB exist - in this case, this is equivalent to ["sheetA!A1:B10", "sheetB!A1:B10"]. Crucially, if a sheet is not found, the range will not be included. This is important for error handling. If you specify a range that is not in the excel file PhixFlow will error. So if you are not sure that a worksheet will always be included, write an expression like this to check, and only specify the range when the sheet is found. Related internal variables See notes for the internal variables _worksheet and _range below. These can be used in stream attribute expressions to record the source worksheet and range for data you have loaded into PhixFlow. Constraints Note that if a worksheet is specified, then the full cell range must also be specified. Hence it is not possible to select a 'worksheet only' or 'columns only for a specified worksheet'. e.g DailyCallsSheet or DailyCallsSheet!A:C are not supported. | ||||||
| Ignore Undefined Values | Checkbox | This checkbox is only available if File Type = Excel Spreadsheet. This checkbox should be ticked if all unsupported excel values such as #N/A, #REF! #DIV/0 etc should be ignored and replaced with null values during processing. In this case a single warning message will be displayed to the user once processing has completed stating the number of unsupported cell values found during the processing and a detailed message about the first unsupported cell value. | ||||||
| File Password | Text | This checkbox is only available if File Type = Excel Spreadsheet. If you are reading a spreadsheet which is password protected, enter the password here so that the file can be unlocked. | ||||||
| Confirm Password | Text | This checkbox is only available if File Type = Excel Spreadsheet. If you are reading a spreadsheet which is password protected, confirm the password here so that the file can be unlocked. | ||||||
| Name | Text | The name of the column. The attribute will be referred by this name elsewhere in PhixFlow. This can contain any combination of letters and numbers, and the characters: '_'. | ||||||
Order | Number | The order in which the attributes are placed. This must match the order of the fields in the files that will be read by this file collector. | ||||||
| Type | Drop-down | This can be one of:
| ||||||
| Length | Number | For a String, the maximum length of the String. For an Integer, the maximum number of digits. Note that for a comma-separated file it is not necessary to set field sizes; only the field sizes of the fields in the stream that this collector will write to are important. Of course, for a file with fixed length records it is crucial to set the fields lengths correctly. | ||||||
Xml Namespaces Xml Namespaces are used for providing uniquely named elements and attributes in an XML document. An XML instance may contain element or attribute names from more than one XML vocabulary. If each vocabulary is given a namespace, the ambiguity between identically named elements or attributes can be resolved. Note : this tab is only available for XML File Collectors. | ||||||||
| Name | Text | Name of the XML namespace. However, this is not mandatory - you can give any namespace any name - all that matters is that the names defined here match those you use in XPath expressions to extract data from the XML response. In particular, default namespaces, e.g. xmlns="urn:xmlns:company-com:message" can be given any name, providing that you use this name in XPath expressions. | ||||||
| Value | Text | Value of the XML namespace. E.g. http://schemas.xmlsoap.org/soap/envelope/ | ||||||
File Format Description This tab is only available for Binary File Collectors. | ||||||||
| Validate File Format | Checkbox | Validate that the file matches the XML description. | ||||||
| Stream Item Node | Expression: list of strings | A list of target node names - that is, the names of nodes that will generate an output record. Example of a single target: "DATA_RECORD" Example of a list of targets: ["DATA_RECORD1","DATA_RECORD2","DATA_RECORD3"] | ||||||
| File Format Description | A Binary File Grammar, in XML, describing the format of data in the file. | |||||||
Description | ||||||||
| Description | Text | Description of the file collector. | ||||||
...