Unit processing

To do this, it has its own database allowing to:

• Store the different settings of the folder.
• Store so-called “intermediate” data to allow visualization of the data conveyed before their integration into the recipient system, thus allowing the implementation of consistency checks or the entry, or even the automatic generation of new information not carried by the source system.
• Carry out any processing outside the perimeter of the connected information systems.
• Guarantee traceability of the treatments performed, especially in the event of an error to facilitate the diagnosis of the problem encountered. Through this own database, Open Flux makes it possible to configure a certain number of unit processes, then to organise them within a group of processes whose whole constitutes a flow. The different flows thus defined can then be categorized to group them according to the “theme” with which they are associated. There is no limit to the number of unit treatments or to the number of flows (groups of treatments) or their categorization.

Through this own database, Open Flux makes it possible to configure a certain number of unit processes, then to organise them within a group of processes whose whole constitutes a flow. The different flows thus defined can then be categorized to group them according to the “theme” with which they are associated. There is no limit to the number of unit treatments or to the number of flows (groups of treatments) or their categorization.

The different types of unit treatments are as follows:

• Access to the data of an information system by reading directly from a database or via an ODBC driver when the interfaced solution requires it (for example for Sage Line 100 in proprietary database).
• Sequential reading of data from one of the connected information systems to feed the Open Flux database, or vice versa of Open Flux data to feed an information system.
• Execution of an SQL query on data from the Open Flux database or on those of connected information systems.
• Import of external files (csv, xml, json, …) either into Open Flux or directly into one of the connected information systems.
• Export of data in files (csv, xml, json,…) either by reading Open Flux, or by reading one of the connected information systems.
• File transfer via FTP protocol up or down.
• Execution of a Web script by http protocol, with parameters passed in Post or Get mode.
  Invocation of a Web Service by Soap protocol.
• Running a local program with execution parameters.
• Various other processes such as deleting a file, zip/unzip files, etc.