¶ Introduction
In Transpas, many things require an exchange of data.
This can be done via an HTTP request or via a file.
If this is done via a file, the data from this file must be read into Transpas.
The Filesystem watcher was created for this purpose.
The Filesystem watcher monitors a file folder, so to speak, and will process all files placed in it via the action set on that line.
¶ Set up
It is possible to set a number of things on the Filesystem watcher.
Below is an explanation of the different settings.
¶ Description
A description of this filesystem watcher.
It is customary to enter the name of the service for which the files are read.
For example Transporeon, Import customer X or something similar.
¶ Active
Turn the filesystem watcher on or off.
¶ Company
Enter the company to which the Filesystem watcher belongs.
This allows filtering by company using the selector at the top of the screen.
¶ Directory
The folder where the files that need to be read are located.
Preferably enter a UNC path here. This is more reliable.
So: \SRV-SQL01\AS\Transpas\
And not: D:\AS\Transpas
¶ Filter
The filter can be used to indicate that only certain files may be read.
By default, the value in this field is *.*. This will read all files.
To only read XML files, this can be changed to *.xml, for example.
It is not recommended to use the *.* filter here.
This can ensure that temporary files are also read.
¶ Action
The action that must be performed to import the read file into Transpas.
For example, the standard order import action: 2244 - Import transport bookings xml (tpent)
¶ EDI Provider
Orders are imported using an EDI Provider. All kinds of settings can be made here for the import.
Consider automatically accepting imported orders, translating unit codes and products or sending a notification when new orders have been read and much more.
¶ Import definition
The import definition to be used for the import of the imported files.
¶ Continue on error
Default: 'No'
If set to 'No', the filesystem watcher action will not process any more files after encountering an error file. The error file is moved to the error folder and the action stops after this.
Only the next time the filesystem watcher action is performed will it process more files.
If 'Yes', the action will not be stopped after an error file and will process subsequent files without having to re-execute the action.
¶ Wrong
Error folder: The full or relative path of the folder where the error files should be saved.
Error folder method: Should subfolders be created in the error folder? If so, in what format? For example, subfolders per year and within that per month.
¶ Backup
Backup folder: The full or relative path of the folder in which the processed files should be saved.
Backup folder method: Should subfolders be created in the backup folder? If so, in what format? For example, subfolders per year and within that per month.
¶ Maximum # of log lines
The number of log lines to keep before purging the oldest ones.
¶ App server instance
If many files are read, it can be useful to create multiple application services for the filesystem watcher. In this option you can select under which service this filesystem watcher runs.
¶ Example
When everything has been filled in, it will look like the image below:
