Details
-
Feature
-
Status: Dismissed (View Workflow)
-
Minor
-
Resolution: Won't Do
-
None
-
None
-
None
Description
Current Situation
- When watching directories for incoming files then JobScheduler would create the Order ID from the full path.
- With an extended hierarchy of folders or with long file names the length of the Order ID is growing. This might interfere with the max. length of 255 bytes for an Order ID.
- Hint: when using relative paths for the configuration of the directory to be watched then the relative path will be used to precede the file name and therefore might reduce the length of the Order ID.
- Using characters in file paths that require multiple bytes, as e.g. with Japanese characters, makes the situation worse as fewer characters are allowed that fit into the 255 bytes column size.
- In addition, when using the splitter JITL Job then child orders are created that extend their Order ID by a number of bytes in addition to the length of the parent Order ID.
Desired Behavior
- The JobScheduler should not use the file path as the Order ID but instead use a running number as for any Ad Hoc order.
- The file path instead should be copied to the Order Title attribute and should be left truncated if it does not fit into the column size.
- The Order Title should may have a length of 512 byte
- The effective file path is available from the scheduler_file_path parameter that can have any length.