OS4X Directory Scanner - Revision history

Admin: /* 2DO file OS4X Enterprise send job */

2026-05-21T09:33:11Z

2DO file OS4X Enterprise send job

2026-05-21T09:26:04Z

2DO file OS4X Core enqueueing

2026-05-21T06:48:41Z

2DO file format support

2026-05-20T17:28:01Z

Recursive search path depth

2026-05-20T17:22:14Z

2DO file OS4X Core enqueueing

2026-05-20T17:18:07Z

Type selection

2026-05-20T17:14:12Z

Type selection

2025-01-21T12:49:50Z

2024-03-07T14:12:58Z

Ignore files with suffix ".part"

2024-03-07T14:12:28Z

Regular expression

← Older revision		Revision as of 09:33, 21 May 2026
Line 188:		Line 188:

	==== 2DO file OS4X Enterprise send job ====		==== 2DO file OS4X Enterprise send job ====
		+	[[File:Bildschirmfoto 2026-05-21 um 11.31.33.png]]
		+
	If your ERP system can provide a 2DO file, the referenced file can be extracted from this meta information file, also the recipient of the job. The additional configuration options are as follows. The value of the field "<code>SID</code>" will be used to search for the recipient of the job according to the rules documented in [[OS4X_Directory_Scanner#Person_regular_expression\|Person regular expression]].		If your ERP system can provide a 2DO file, the referenced file can be extracted from this meta information file, also the recipient of the job. The additional configuration options are as follows. The value of the field "<code>SID</code>" will be used to search for the recipient of the job according to the rules documented in [[OS4X_Directory_Scanner#Person_regular_expression\|Person regular expression]].

← Older revision		Revision as of 09:26, 21 May 2026
Line 171:		Line 171:

	==== 2DO file OS4X Core enqueueing ====		==== 2DO file OS4X Core enqueueing ====
		+	[[File:Bildschirmfoto 2026-05-21 um 11.25.25.png]]
		+
	If your ERP system can provide a 2DO file, most parameters can be extracted from this file. The additional configuration options are as follows.		If your ERP system can provide a 2DO file, most parameters can be extracted from this file. The additional configuration options are as follows.

@@ Line 47: / Line 47: @@
 === 2DO file format support ===
-The 2DO file will be used for information extraction. It doesn't care about newlines. All elements are separated by spaces, so virtual and absolute filenames with whitespaces are not support, also for all other values. The following list of variables are taken into account:
+The 2DO file will be used for information extraction. It doesn't care about newlines. All elements are separated by spaces, so virtual and absolute filenames with whitespaces are not supported, also for all other values. The following list of variables are taken into account:
 *<code>DSN</code>: The absolute path of the file to be transmitted.
 *<code>DSNNEW</code>: The virtual filename for OS4X Core enqueueing.

@@ Line 45: / Line 45: @@
 === Recursive search path depth ===
 You can influence, how "deep" the directory scanner scans for valid entries. By default, the directory scanner scans for objects only in the configured directory (depth: 0). If you want to dig deeper, you can give a valid depth value.
 === Type selection ===

@@ Line 174: / Line 174: @@
 The preset is:
 *"OS4X Core enqueueing" (<code>dirscanner_os4xeq.sh</code>): This script parses all parameters correctly to enqueue the found file to the OS4X send queue with the given parameters.
 === Person regular expression ===

@@ Line 159: / Line 159: @@
 ===== Job comment =====
 An optional job comment can be added to the send job.
 === Person regular expression ===

@@ Line 47: / Line 47: @@
 === Type selection ===
-If you configured and licensed to [[OS4X_Core_configuration#is_OS4X_Enterprise_installed.3F|use OS4X Enterprise]], you have the option to
+For OS4X Core, the following type of directory scanners are available:
-*Scan for files, handled for OS4X Core enqueueing
+*OS4X Core
-*Scan for directories or files to be used for OS4X Enterprise job creation
+*2DO file OS4X Core enqueueing
 Depending on your choice, you're getting a different configuration view:

@@ Line 89: / Line 89: @@
 ====== Fixed record length transfer mode selection ======
-If the default transfer mode should be overridden and "fixed record length" files should be transfered, a non-empty return value activates this functionality.
+If the default transfer mode should be overridden and "fixed record length" files should be transferred, a non-empty return value activates this functionality.
 ====== Variable record length transfer mode selection ======
-If the default transfer mode should be overridden and "variable record length" files should be transfered, a non-empty return value activates this functionality.
+If the default transfer mode should be overridden and "variable record length" files should be transferred, a non-empty return value activates this functionality.
 ====== record length selection ======

@@ Line 38: / Line 38: @@
 === Ignore files with suffix ".part" ===
-Many upload tools append a filename suffix "<code>.part</code>" during the transmission and remove it afterwards. These files can be ignored by enabling this checkbox. This is also a handy feature if [[OS4X_Core_configuration#Serialize_incoming_files|serialized OFTP2]] files is enabled.
+Many upload tools append a filename suffix "<code>.part</code>" during the transmission and remove it afterwards. These files can be ignored by enabling this checkbox. This is also a handy feature if [[OS4X_Core_configuration#Serialize_incoming_files|serialization of incoming OFTP2 files]] is enabled.
 === Age of entry ===

← Older revision		Revision as of 14:12, 7 March 2024
Line 36:		Line 36:

	Since OS4X version 2018-10-25, you can choose the engine for the regular expression (before that point, POSIX was the default engine). Offering the PCRE engine, regular expression can become much more complex, offering a huge benefit of selecting the correct file or directory.		Since OS4X version 2018-10-25, you can choose the engine for the regular expression (before that point, POSIX was the default engine). Offering the PCRE engine, regular expression can become much more complex, offering a huge benefit of selecting the correct file or directory.
		+
		+	=== Ignore files with suffix ".part" ===
		+	Many upload tools append a filename suffix "<code>.part</code>" during the transmission and remove it afterwards. These files can be ignored by enabling this checkbox. This is also a handy feature if [[OS4X_Core_configuration#Serialize_incoming_files\|serialized OFTP2]] files is enabled.

	=== Age of entry ===		=== Age of entry ===