LocalEnvironment.Wildcard.WildcardMatch contains the value of a wildcard that you can set in the File name property on the FileInput node. The sample uses the value from LocalEnvironment.Wildcard.WildcardMatch to set the values for the output file name and directory in the FileOutput node. The sample demonstrates the following tasks:
The sample is based on a scenario where a file based e-mail system uses file nodes to forward file based e-mails. Users send e-mails by creating a file in an e-mail directory. The file name follows the convention To_<receiver>@<branchname>.txt The e-mail system collects the files in the output directory and transfers them to the input directory of the receiver office.
Note: The sample does not use the EmailOutput node.
The scenario is implemented by using a single message flow called FileWildcardMatchSampleFlow. The FileWildcardMatchSampleFlow message flow uses a FileInput node and a FileOutput node. The FileInput node is configured to monitor an input directory for files named To_*.txt where the asterisk (*) is a wildcard character that can be made up of zero or more characters.
A Compute node takes the value set in LocalEnvironment.Wildcard.WildcardMatch, which is in the form <receiver>@<branchname>, and assigns the value <receiver> to the destination file name in the local environment. The Compute node also assigns the value <branchname> to the destination directory in the local environment. The FileOutput node uses the values set in the local environment to create an output file.
The following diagram shows the FileWildcardMatchSampleFlow message flow:
