Automated import tasks make it possible to carry out regular imports of data on a time-controlled basis. The easiest way to carry out such an import is via an individual plug-in from eTASK, in which the processing of the data is handled. In order for the import task to be executed, the corresponding timer job must also be active.
Identification
Information on the identification of the data record is stored in this info area.
| Property | Description |
| Description | A meaningful description helps so that even the uninitiated can understand exactly what this import task does. |
| Code | Enter an abbreviation for the import task here. For tasks that you have received from eTASK, this will often be the plug-in number. |
| Designation | The name for the import task can be entered here. |
| Active? | Decide here whether the import task should actually be executed. Please note that the corresponding timer job must also be active for the task to be triggered. |
Data source
This info area contains all the information required to identify and load the source file.
| Property | Description |
| Path | Enter the exact path where the source file is stored. You can use absolute paths as well as UNC paths as long as the path is accessible. |
| FTP connection | Here you can select the FTP connection to be used for the data import. This setting determines from which FTP server and with which access data the files to be imported are retrieved. Selecting the correct FTP connection is crucial for a successful data import. |
| File name pattern (Regular Expression) | You must specify the name of the source file here. You can either do this as an absolute specification (e.g. Import.csv), or you can describe the name pattern with a regular expression if it contains dates, for example. |
| Format | At this point, you select the format of the source file. This information is important so that the file can be processed correctly. For text files, pay particular attention to the encoding (UTF8) if you use special characters in the data. You can check the encoding of a file in a text editor. |
| Registration | Select a login here with which you can reach the path specified above. The login must be stored in the system beforehand. |
| Data from line no. | Specify here how many lines at the beginning of the source file contain no data and from which line the data should be processed. An entry of 2 skips the first line for the import and starts with the second. |
| File available via | Select here how you would like to obtain the source file. The selection values are limited to the technically implemented paths. |
Target table
This info area contains information about the import destination.
| Property | Description |
| table name | Here eTASK expects the technical name of the table into which this data is to be imported. For the "Rooms" table, this would be FL RAUM T, for example. |
Time control
All necessary information on the execution plan for the import task is stored in this info area.
| Property | Description |
| Interval | Enter the interval at which the import should be carried out in conjunction with the unit. |
| Next version | When starting the import task, specify here when the next (and first) import should take place. The value is updated automatically with each execution. |
| unit | Based on the interval, select the time unit that is to be used to trigger the import task. The selection values are predefined and cannot be changed. |
Action after import
This info area is used to specify what should happen to the data after import.
| Property | Description |
| Import Procedure | Enter the technical name of a database procedure with which the data is to be imported and processed. |
| Delete file | Specify here whether the source file should be deleted after processing in the source path. This is particularly recommended if the import task is carried out regularly but a new file is not expected with every run. This prevents the file from being processed multiple times. |
Logging
Here you define how the import task is to be logged.
| Property | Description |
| Save log [days] | With this setting, you specify after how many days entries in the logging of this import task, including the archived source files, should be automatically deleted. |
| Store import file? | If you check this box, the original version of every file you have imported will also be saved in the log. It is recommended to select this option, especially when importing important data or for a certain period of time after an import task has been started. This makes it easier to track unforeseen results of the import task. Please note that you are responsible for compliance with data protection regulations if you give people access to the logging of imports and thus possibly to the source data. |
Test Import
This function provides the "Run manually" button in the menu bar of the import task, which you can use to start the task manually if required or to test it during commissioning.
Import cycles
This info area contains all imports performed for this task, based on the logging settings.
See also: Import runs
