Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The Order ID of file orders for example is created like this: #<ISO date>#F<Seconds since Jan 1st 1970>-<ID of file order source>:<file name>
    • #<ISO date># is the date of appearance of the file, e.g. 2021-03-17., enclosed by #.The date is calculated for the time zone assigned the File Order Source.
    • F is a qualifier to indicate a File Order Source.
    • <Seconds since Jan 1st 1970>- is what is says and is appended a hyphen.
    • <File Order source ID>: is the unique identifier of the File Order Source configuration object followed by a colon.
    • <file name> is the name of the incoming file.
  • Such file orders can be considered triggers for workflow execution which implies that the workflow can be executed with the same Agent or with different Agents.

...

When an incoming file arrives in a directory then the file is might not be completely written at the point in time or of appearance.

  • In Windows environments files that are written by a process cannot be accessed by jobs.
  • In Unix environments parallel read and write operations to files by jobs and processes are possible - but not desired as results are unpredictable.

...

It is not considered good practice for a client application to make files with the same name appear and disappear in short sequence, however, the situation will be handled by creating the Agent that creates additional file orders.

Behavior with Outages

...

  • A job in a workflow can
    • move an incoming file to some archive location that is not under subject to file watching,
    • remove an incoming file.

...