There are various ways to import Files into the application in order to store them there in a structured manner. Depending on how your company works, this can be done in different ways.

The storage of Data is organized according to very different structures in different companies. The application can easily accommodate these individual requirements in this regard.

Companies organize their Data in very different ways. The Data is stored on Servers and arranged in Directories according to various criteria such as date, customer name, customer order number, or Production Order number. The nesting of Directories can vary in depth. However, each structure always has a Directory in which the customer's original Data, consisting of the print File, order information, and CSV data for variable orders, is stored. Each structure also has a Directory where the approved Print Data is located. The name of the File is also part of the work organization.

The aim of the Workflow is to provide options for mapping all market requirements in terms of Data Storage, Structure and Working Methods. In addition, it should be possible to automatically create Structures, Storage Locations, and orders. The Workflow requires few conventions:

• Hierarchical Directory Structure – data is not necessarily stored in a Hierarchical Directory Structure by the Workflow. Data is stored in a database with the corresponding meta information.
• File Names – file names do not have to follow any convention, since Print Data can be quickly located along with higher-level structures such as collections, groupings, or orders.
• File Versions – the Workflow always displays the current version for processing. If it is necessary to revert to an earlier version, this can be done at any time.
• Log – whenever Print Data is processed within the Workflow, each activity is automatically logged. Users can therefore always view the history of the Print File.
• Release of Directories – access to external File systems is managed by the Workflow. Usernames and passwords are stored within the Workflow and therefore do not need to be generally known in production.

The Workflow supports different working methods. Choose from the available approaches:

• Article-based Workflow – Print Data is stored in a structure – assignment of Collections, etc. –, prepared as "print-ready" for production, customized with customer-specific Color Mapping, and released. Only then is the Data assembled and Output within a Production Order.
• Order-based Workflow – Print Data can be organized as an order with different order items, processed, customized with customer-specific Color Mapping, released, and transferred into a Production Order. Whether a single order becomes a Production Order or a Production Order is created from multiple orders depends on the company's Workflow.
• Production-based Workflow – Print Data is created within a Production Order, processed, assigned to an Output configuration, assembled, and transferred to the printer.
• Automated Workflow – Print Data can either be automatically created as an Article, within an Order, or within a Production Order based on information from leading ERP systems, or automatically generated as a Production Order ready for Output by monitoring a Hotfolder.
• Workflow without using the User Interface – Print Data can be fully defined in leading systems and handed over for Print Data preparation. The user interface is only needed for setting up automation tools and handling errors that may occur.