File Match Connector
File Match Connector
The File Match Connector adds a decision shape to the flow, capable of sending a message to one of two defined connectors based on the filename.
A File Match Connector functions as a fork in the flow. Files are sent along different paths in the flow depending on whether the filename matches a defined Filter. Files that match are sent along the solid blue flow path, and files that do not match are sent along the dotted gray flow path.
For example, when receiving X12 documents from a partner, it may be necessary to route the document to a specific flow depending on the document type. Promoting the document type to the filename and implementing a FileMatch Connector can ensure that X12 documents are routed and processed in the appropriate way.
FileMatch Connectors can be chained together in a ‘cascade.’ This allows for a multi-step conditional to sort files into the appropriate flows based on the filename.
This section contains all of the configurable connector properties.
Settings related to the core operation of the connector.
- Connector Id The static, unique identifier for the connector.
- Connector Type Displays the connector name and a description of what it does.
- Connector Description An optional field to provide a free-form description of the connector and its role in the flow.
- Filter The glob pattern filemask used to determine whether files ‘match.’ Files that match this pattern are sent along the ‘Match’ path, indicated by a solid blue line. Files that do not match this pattern are sent along the ‘Else’ path, indicated by a dotted gray line. This pattern supports wildcards (e.g. *.txt).
Settings not included in the previous categories.
- Log Subfolder Scheme Instructs the connector to group files in the Logs folder according to the selected interval. For example, the Weekly option instructs the connector to create a new subfolder each week and store all logs for the week in that folder. The blank setting tells the connector to save all logs directly in the Logs folder. For connectors that process many transactions, using subfolders helps keep logs organized and improves performance.
- Log Messages Whether the log entry for a processed file includes a copy of the file itself.
- Save to Sent Folder Whether files processed by the connector should be copied to the Sent folder for the connector.
Settings related to the automatic processing of files by the connector.
- Send Whether messages arriving at the connector will automatically be processed.
The following sections detail how to use negative filters and multiple filters at a time.
The Filter setting can be set to a negative filter, which operates as the inverse of a regular filter. Only files that do not match the ‘negative’ filter will be considered matches. Negative filters can be set by including a minus sign before the pattern:
In this example, all files without a ‘.tmp’ file extension will be passed along the solid blue path, and all ‘.tmp’ files will be sent along the dotted gray path.
Multiple filters can be specified in a comma-delimited list. Later filters will take priority, except for when a filter exactly matches a filename (no wildcards or other character replacements). Positive and negative filters can be combined, for example:
In this example, all text files will be considered matches except those that begin with ‘processed_’. A file called ‘processed_file.txt’ would not be considered a match and would be sent along the dotted gray path.