DE102007009737B4 - Method, printing system and computer program for automatically processing job-related data of a print job - Google Patents

Abstract

Method for automatically processing order-related data of a print job, which contain control parameters for controlling a printing operation, in a printing system with a print job manager (1), several input modules (2/1), which are each connected to a computer (3) to which print jobs are generated and to a print server for feeding the print jobs to a print device
Receiving a print job with the job-related data from one of the computers (3) by means of the input modules (2/1) and forwarding to the print job manager (1),
Checking the order-related data for errors, wherein the check is carried out according to predetermined ticket rules centrally on the print job manager (1), and the job-related data are modified and corrected accordingly if necessary, and outputting a printing system-specific job ticket, and
- Forward the print job with the printing system-specific job ticket to the print server.

Description

The The invention relates to a method, a computer program and a printing system for automatically processing order-related data of a print job.

In Digital Printing, Technology and printing techniques of Océ digital printing presses, 9 ^th edition, February 2005 (ISBN 3-00-001081-5) is described in Chapter 18.2 an Order Distribution System (ODS), which is also referred to as Workflow Manager , With this Order Distribution System, you can control the entire digital printing process, including a pre-press, a high-performance printer, and finishing. In pre-press, image and text files from different sources, such as scanners, digital cameras, data carriers or a computer network, are brought together and finalized at a layout station. Subsequently, a printer driver converts the data created on different platforms, for example, into postscript files. These files can then be forwarded to a print server for printing. Print servers convert the data into compressed bitmaps, which are automatically imposed and forwarded to the printing system. The print server controls the printing process. The finishing of the printed product includes, for example, the binding or insertion of release sheets.

The Order Distribution System is also responsible for the central management of Production variants responsible. This includes also the printing service for Intranet and Internet users. The Order Distribution System informs User over released production variants, takes print jobs together digital order bag, causes the automatic processing until the pressure. The Order Distribution System also monitors the correct one execution the selected one Printing and finishing options.

The Order Distribution System processes so-called job tickets. A job ticket is a file in a specific data format that Control parameter for controlling the printout of print data of a print job contains. The job ticket can be used by the user when creating the print job or automatically created in a printing system.

conventional Job tickets have clear instructions to implement accordingly are. The printing process is becoming increasingly extensive, as more and more equipment be integrated into a printing process, whereby the variety of functions increases. In addition, printing processes are increasing through the Internet and intranet distributed regionally or assigned to a pool of printers that may be regionally distributed. In addition, increasingly equipment different manufacturers work together in one process. To cope with these increased demands, one became Uniform specification for the exchange of data formats in the printing process which is called Job Definition Format (JDF). For this is there a corresponding job message format (Job Messaging Formats or JMF), which is specified accordingly. The specification JDF can be downloaded from the website www.cip4.org At present, the current specification is JDF specification Release 1.3.

JDF is an XML-based format that specifies the instructions for the printing process arranged in a tree structure. Each node of the tree structure includes an instruction or set of instructions. The top one Node is called root. The end nodes will be at branches referred to as leaf nodes.

The Special feature of JDF is that it is called Intent node which contain a very general instruction for a printing process, which specifies it needs to be on a device accomplished to be able to.

From the DE 10 2004 047 327 A1 outlines a method that uses the JDF format to incrementally specify a print job.

From the EP 1 197 838 A2 A method is known for processing print jobs in a network, in which a job ticket is used to check whether a print service provider has the resources required to process the print job.

From the US 2002/0080400 A1 is a method for a document processing system out in which a document processing job can be edited multiple times in different ways. How the document processing job is processed in detail is controlled by different job tickets. The peculiarity of this known method is that the different Job tickets can be accessed at one time by means of a master job ticket, also referred to as a super job ticket, so that the multiple document processing jobs can be posted by the master job ticket at once in the document processing system.

From the US 5,718,520 A is a method for editing job tickets, in which when editing a particular control parameter, a window is generated on a display device in which all possible values are displayed, which can be used for the control parameter.

Out Digital Printing Technology, and Printing Techniques of Digital Océ Printing Presses (a.o.) enters with the trade name Océ PRISMAproduction designated server system that processes a wide range of data streams or converted, which will then be printed on IPDS printers. The Océ PRISMAproduction Server system includes a Printjobmanager PJM (see chapter 15.2.4 and 18.2) with the print jobs generated on any client client and in this server system be edited and managed. The print job manager will too referred to as print job manager.

Become a "server" Software modules that do a central job. As "clients" become Software modules that are associated with a server and receive or transmit data from the server. With a server can several clients are in contact at the same time.

at This known client / server system will print jobs generates the clients. A print job includes those to be printed Print data and a job ticket, the control parameter for controlling the printout includes the print data.

The print jobs can come from different sources. At the print job manager upstream clients control the incoming print jobs and adjusted if necessary. This customization can print the job accompanying data or information, the content the job ticket is adapted to the printing environment. It is also possible, that from the data accompanying the print job and one at the print manager existing ticket for the first time a job ticket at the print job manager is created. The format of any incoming job tickets is usually OK, but often contains parameters that are not are usable or even lead to contradictions. So include job tickets often printer names that are not present in this printing system are. To correct such erroneous job tickets are on the clients Computer programs are provided, which control the job tickets automatically and correct if necessary. These computer programs are called Scripts individually for programmed the individual clients and their applications. It is also common that several such scripts are provided on a client, for example, different sources or job tickets with print data to be revised in different data formats. These scripts have proven to be very effective because this automatically controls the incoming print jobs and corrected so that the entire printing process runs without delay can.

kick nevertheless an error due to a wrong parameter in the job ticket while of the printing process, it is in the present embodiment of the printing system difficult to determine where and by what the Error has been caused. For this purpose must be reconstructed on the one hand be over which client the print job has been sent to the print job manager is, and then it has to be determined, with which script the job ticket works has been. Even if this is clear, it is often difficult to do that Script to analyze if it caused the error or possibly the error when creating the print job when Customers or when transferring the print job has been caused to the client.

In the DE 103 35 124 A1 discloses a method in which already used and screened print jobs can be reused and modified. The "old" print jobs are located on a control device of a printing device. They can be retrieved from a client, with the client requesting the appropriate job ticket from the printing device. This job ticket is then reworked by the client, with instructions inserted to insert the changed pages, so that the unaltered pages from the old print job can be accepted at the printing device and only the pages to be replaced are rasterized.

In the US 2004/0111430 A1 A system for automatically generating a workflow will be described. This workflow can be a print job. Services are offered by different client computers, with each offering being evaluated by a workflow controller and assembled into a workflow.

Of the The invention is therefore based on the object, a method, a Printing system and a computer program for automatic editing Order-related data for to create a printing process that, without delaying the printing process a automatic control of job tickets allowed and yet easy is traceable and manageable.

The The object is achieved by a method having the features of the claim 1, a printing system with the features of claim 12 and a computer program solved with the feature of claim 17. Advantageous embodiments The invention are specified in the respective subclaims.

• – Empfangen eines Druckauftrages mit Auftragsbegleitdaten von einem der Clients durch den Druckauftragsmanager,
• – Überprüfen der Auftragsbegleitdaten nach vorbestimmten Ticket-Regeln und Ausgeben eines drucksystemspezifischen Jobtickets, und
• – Weiterleiten des Druckauftrages mit dem Jobticket zum Druckserver.

The inventive method for automatically processing order-related data of a print job, the control parameters for controlling the print job, in a printing system with a print job manager, one or more clients on which print jobs are generated, and a print server for supplying the print jobs to a printing device, comprising following steps:

• Receiving a print job with job-related data from one of the clients by the print job manager,
• Checking the job-related data according to predetermined ticket rules and outputting a printing-system-specific job ticket, and
• - Forward the print job with the job ticket to the print server.

The inventive method is characterized by the fact that checking the order-related data according to the predetermined ticket rules centrally on the print job manager accomplished becomes.

There the order-related data centrally and preferably exclusively on Print job manager checked or are controlled for a specific print order applied ticket rules easily traceable, because the ticket rules are only in one place, namely the print job manager, and not, as in the prior art the case is present on different clients and there respectively to investigate. Furthermore, by centrally executing the review of the Job-related data at the print job manager ensures that all incoming order-related data are checked according to the same ticket rules or be controlled and if necessary amended accordingly and Getting corrected.

Farther are by the central running of checking the Order-related data to manage the ticket rules centrally, which they are also centrally controllable and avoids similar ones Order-related data or similar Errors in order-related data are corrected differently.

One Another advantage of checking the Job-related data is central to the print job manager, that the review of Order-related data in the process chain very close to the concrete Pressure device takes place, so this review is very specific for the respective pressure device carried out can be. This can significantly increase the quality of the review. In the execution the review of Job-related data to the clients is the problem that the Clients communicate with different print job managers can, so that carried out a review of the Job-related data to the printing devices working with the different print job managers can be achieved must be adapted, which in turn is very difficult.

By the central administration of the ticket rules is also possible to the Operator tools available to facilitate the creation and management of ticket rules. In particular, it is appropriate to a graphical user interface (GUI) in which the ticket rules are created and managed can be and provide a software module with which the syntax of the edited Ticket rules are automatically checked for correct syntax.

To explain the present invention, some terms are defined below:
An entire order contains at least one document processing order, in particular a print job.

One Contains a print job at least one print file to be printed.

One Order ticket contains information about one Overall order, such as B. delivery address, order date, desired Delivery date, etc.

A job ticket contains all the data required to process a print job. This data around summarize control parameters that are relevant in a workflow for the print job (job-workflow). The job ticket is coded in a corresponding ticket format.

One Contains default job ticket Standard data that is suitable for a print job that has no contains further processing information in an existing printing system or an existing printing environment. Such data is Control parameters and can z. B. names or addresses of printing devices that are connected to the respective Print servers are connected.

Under A data ticket is understood to be information provided by a a job creating system, such as an MFS Mainframe computer system generated print job along with the Print data are generated. The scope of such data is systemic very limited and their format is not standardized, which is why they are not be regarded as job tickets in the above sense.

The Job-related data can both a total order ticket, a job ticket and / or a data ticket or control parameters that are attached to a print job in a different form, include. Control parameters are more often in the filename of the Inserted a print job.

is If no job ticket is attached to the print job, then the Print Order Manager by means of the default job ticket and possibly further control parameters and the ticket rules generated a pressure system specific job ticket. If, however, a job ticket is attached to the print job, then Using the ticket rules the job ticket checks to see if it is printing system specific Jobticket is suitable and if necessary., - which is the rule - changed and in particular by pressure system-specific parameters from the default ticket added.

The The invention will now be described in more detail by way of example with reference to the drawings shown embodiment explained. The drawings show:

1 : essential parts of a printing system for carrying out the method according to the invention schematically simplified in a block diagram;

2 a screen shot of the graphical user interface of the system of the invention;

3 to 7 : Extracts of the screenshot of the graphical user interface 2 , and

8th to 17 : Copies of Graphical User Interface Windows to Display and Edit Ticket Rules.

With the method according to the invention incoming order-related data from corresponding print jobs are received from a print job manager at a printing system 1 ( 1 ) automatically processed.

The print job manager 1 (DAM) is with multiple clients 2 (CL) connected. In the present embodiment, three different types of clients are provided, namely input modules 2 / 1 , a print job client 2 / 2 and a ticket rule client 2 / 3 ,

Usually there are several input modules 2 / 1 provided, each with one or more computers 3 (RE) for generating a print job via data lines 46 are connected.

Typically, the print job manager 1 and the input modules 2 / 1 arranged at an operator of a printing center and the computers 3 For the production of the print jobs are the customers of the operator of the printing system and transmit over a network, such as the Internet, their print jobs to the input modules.

The clients 2 and the print job manager 1 are each computer program units. They can be installed and run on a common computer. However, it is equally possible and preferred, at least the print job manager 1 and the clients 2 on at least two separate computers to install and run there. Between the clients 2 and the print job manager 1 are interfaces 47 provided over which data, in particular print jobs can be exchanged.

The print job manager is also referred to as the PJM server (print job manager server). The to Print Job Manager 1 corresponding print job client 2 / 2 This allows the operator of the printing system to execute already existing print jobs. Such print jobs are, for example, print jobs that could not or could not be printed correctly. The operator can use the print job client 2 / 2 Change the print job and in particular the job ticket of such a print job and the respective print job to the print job manager 1 to print to a printing device.

At the print job manager 1 the job-related data of the incoming print jobs are supplemented with data, in particular control parameters, from a default job ticket. In particular, missing, but necessary in the existing printing environment control parameters are added to the job-related data. If there is a complete order ticket, the data, in particular control parameters of the total order ticket in the print order manager 1 added to the press-specific job ticket. During further processing, the so-supplemented pressure system-specific job ticket is taken into account. In the following, therefore, the term job ticket is understood to mean a printing-system-specific job ticket which is supplemented by data from an overall order ticket or a default job ticket, if such exists. The print job manager 1 has a ticket rule module 4 (TRM) in which ticket rules are stored. The ticket rules are managed by the ticket rule module and executed on the print job manager.

The ticket rule module 4 has an interface 48 to the ticket rule client 2 / 3 on which a bidirectional communication is possible. The ticket rule client 2 / 3 includes a rule editor module that can edit the ticket rules stored in the ticket rule module. The rule editor module is provided with a graphical user interface (GUI), which will be explained in more detail below. The ticket rule module and / or the rule editor module are designed such that edited ticket rules are automatically checked for a correct syntax. Corresponding errors are displayed on the graphical user interface and, if necessary, a correction proposal is displayed.

The ticket rule module 4 can also work with multiple ticket rule clients 2 / 3 be connected. However, all ticket rules are only in the ticket rule module 4 at the print order manager 1 saved. With the ticket rule clients 2 / 3 can only access the in the ticket rule module 4 stored ticket rules are accessed and changed there.

The Job ticket contains a list of control parameters for controlling the respective print job. The Control parameter list is in each with a name provided sections divided. There is a section called "files". This Section can occur multiple times in a job ticket. The other sections are provided only once. Within each section are the control parameters with a label called "key" is provided and a specific value called "value". For example, there is a control parameter in the "files" section the key "File_Copies", where the value of the control parameter is an integer that represents the number defines the copies to be printed.

• – condition: Ein Wert („value”) der Auftragsbegleitdaten wird mit einem vorbestimmten Wert verglichen und bei Übereinstimmung wird das Ergebnis „wahr” und bei einer Unterscheidung das Ergebnis „falsch” ermittelt.
• – else: Die Aktion else entspricht der Aktion condition, wobei bei einer Übereinstimmung das Ergebnis „falsch” und bei einer Unterscheidung das Ergebnis „wahr” ermittelt wird.
• – setting: Mit dieser Aktion wird ein Steuerparameter in den Auftragsbegleitdaten auf einen vorbestimmten Wert gesetzt.
• – variable: Mit der Aktion variable kann eine Variable definiert werden.
• – message: Die Aktion message erzeugt eine Nachricht in Abhängigkeit von einem bestimmten Steuerparameter der Auftragsbegleitdaten.
• – rule: Mit der Aktion rule wird innerhalb einer vorbestimmten Ticket-Regel eine weitere Ticket-Regel aufgerufen, die im folgenden als Unter-Ticket-Regel bezeichnet wird. Der Aufruf dieser Unter-Ticket-Regel erfolgt in Abhängigkeit eines oder mehrerer Steuerparameter der Auftragsbegleitdaten.
• – break: Die Aktion break beendet sofort die Ausführung der Ticket-Regel und falls die Ticket-Regel, die beendet wird, eine Unter-Ticket-Regel sein sollte, wird mit der übergeordneten Ticket-Regel fortgefahren.
• – exit: Die Aktion exit beendet sofort die Ausführung der Ticket-Regel. Hierbei wird nicht mit einer übergeordneten Ticket-Regel weiter fortgefahren.
• – exit and stopjob: Diese Aktion beendet sofort die Ausführung der Ticket-Regel. Es wird nicht mit einer übergeordneten Ticket-Regel fortgefahren und die Bearbeitung des Druckauftrages wird auch beendet.
• – switch/case: Mit dieser Aktion wird ein Wert eines Steuerparameters der Auftragsbegleitdaten mit einem jeden Wert verglichen, der in einer ersten Spalte einer Tabelle angegeben ist. Falls eine Übereinstimmung mit einem der Werte vorliegt, werden die Werte der Zeile dieser Tabelle automatisch in entsprechende Datenfelder, insbesondere in eine entsprechende Tabelle in der Ticket-Regel eingetragen. Dies erlaubt das automatische Übertragen von Datensätzen aus Tabellen, wobei die Tabellen außerhalb der Ticket-Regeln mit einem herkömmlichen Tabellenkalkulationsprogramm editiert werden können.

The ticket rules comprise a sequence of actions that are applied to incoming order-related data of the received print job. The following actions can be performed:

• - Condition: A value ("value") of the job-related data is compared with a predetermined value, and if it matches, the result is "true" and if different, the result "false" is determined.
• - else: The action else corresponds to the action condition, where the result is "false" for a match and the result "true" for a distinction.
• - setting: With this action, a control parameter in the order-related data is set to a predetermined value.
• - variable: With the action variable a variable can be defined.
• - message: The action message generates a message depending on a specific control parameter of the job-related data.
• - rule: With the action rule, another ticket rule is called within a predetermined ticket rule, which is referred to below as a sub-ticket rule. This sub-ticket rule is called in dependence of one or more control parameters of the order-related data.
• - break: The break action immediately stops the execution of the ticket rule, and if the ticket rule that terminates should be a sub-ticket rule, the parent ticket rule continues.
• - exit: The exit action immediately stops the execution of the ticket rule. This will not continue with a parent ticket rule.
• - exit and stopjob: This action immediately stops the execution of the ticket rule. It does not continue with a higher-level ticket rule and the processing of the print job is also terminated.
• - switch / case: This action compares a value of an order-tracking data control parameter with each value specified in a first column of a table. If there is a match with one of the values, the values of the row of this table are automatically entered into corresponding data fields, in particular into a corresponding table in the ticket rule. This allows the automatic transfer of records from tables, whereby the tables outside the ticket rules can be edited with a conventional spreadsheet program.

The Sequence of actions of a ticket rule can be branched like in a tree be, with the branches are each carried out by the conditions "condition" or "else" and the leaves of the tree are represented by actions, which then enter the respective condition (s) are executed.

In the present embodiment, a client becomes one 2 incoming print job to the print job manager 1 passed on, with this forwarding or transmission of the print job from the client 2 to the print order manager 1 a function is called, which carries out the processing of the respective print job. By calling this function is the client 2 a parameter is passed to this function, which contains a reference to a corresponding ticket rule with which the order-related data of the print job are checked. This function therefore calls the ticket rule on the print job manager, depending on the parameter passed 1 on.

A screen shot of the Ticket Rule Client GUI 2 / 3 is in 2 shown.

The graphical user interface includes a main bar 5 (Main tool bar), a drop-down menu 6 for the ticket rules (Ticket Rules drop down menu), a rules definition window 7 (Rule definition window), a rule definition bar 8th (Rule definition tool bar) and a rule activation list 9 (Rule activation list).

The main bar 5 is in 3 shown again in an enlarged view. It has seven pictograms 10 . 11 . 12 . 13 . 14 . 15 . 16 on. By clicking on one of the pictograms with a computer mouse, a specific function can be triggered.

With the pictogram 10 The current configuration of the ticket rules is saved. These changes will be in the ticket module 4 saved. If changes have been made to ticket rules on the graphical user interface, they will only be applied to incoming order-related data if the icon 10 has been pressed, that is, when in the ticket rule module 4 are stored.

When operating the pictogram 11 any changes made since the last time the ticket rules were saved are discarded.

With the pictogram 12 a new rule is generated. The user is first asked for the name of the new rule. The new rule will then be sent to the rule activation list 9 attached and is activated. It does not contain any actions yet.

With the pictogram 13 An existing ticket rule can be copied to a new ticket rule. Again, the user is first asked for the name of the new ticket rule. All actions of the copied ticket rule are copied to the new ticket rule.

The pictogram 14 is used to delete a ticket rule. With the pictograms 15 and 16 can be found in the rule activation list 9 ticket rules are moved up or down one step at a time.

4 shows the drop-down menu 6 in the unfolded state, in which the above based on the pictograms 10 to 16 explained functions can be called.

In the rule activation list 9 ( 5 ) all ticket rules are tabulated. In a first column, the activation state is indicated, in a second column the rule name and in a third column a rule description.

These Rule description can either automatically from the existing Sequence of actions generated or can manually through its own window be entered. Optionally, the generated description or the self-generated description will be displayed. The manual created description will be together with a corresponding rule stored.

It There are three activation states: (active, inactive) and sub-rule (sub-rule).

One User can specify if a particular rule is active or inactive should. The "inactive" mode is used if a particular rule is not applied to incoming job tickets should. This is expedient with old rules that are temporary should not be used or new rules that are not yet are sufficiently tested. Thus, it is possible a ticket rule for later use define.

In the "active" mode, a rule can be set if it is executable and not a sub-ticket rule. The individual rules are determined by the rule module 4 automatically checked for their feasibility, that is for the correctness of their syntax. This check is performed after each change of a rule. If the rule is executable, it will be displayed in black in the rule activation list. However, if it is not executable, it will be displayed in this list with a red font. In "inactive" mode, the font is always transparent.

A ticket rule with sub-ticket rule mode can only be used as a sub-ticket rule, which means that it must be called by another parent rule. Sub-ticket rules are in the rule activation list 9 in italics in black for executable and in red for non-executable rules. Double clicking on an element in the third column (rule description) opens a window ( 8th ) for editing the rule description. If the pictogram "Ok" is clicked in this window, the corresponding rule description is adopted.

The rules definition bar 8th ( 6 ) contains pictograms 17 . 18 . 19 . 20 . 21 . 22 . 23 . 24 . 25 and 14 which are used to add and delete actions for a rule definition.

With the pictogram 17 becomes a condition definition window 26 ( 10 ), with which conditions can be edited. This will be explained below.

With the pictogram 18 becomes a setting definition window 28 ( 11 ) open. Each setting definition includes a name, a control parameter, a value, and an override flag. A set definition serves to set a control parameter in the job ticket to a specific value. This is explained in more detail below.

The pictogram 19 is used to add and edit variables. Pressing this icon turns into a variable editor window 28 open ( 12 ).

The pictogram 20 Opens a message editor window 29 ( 16 ) and allows editing of messages.

With the pictogram 21 can be added to sub-ticket rules. From a list of all defined sub-ticket rules one can be selected.

The pictogram 22 is used to add the condition "else" into a sequence of actions.

The pictogram 23 Adds the action "break" to a sequence of actions.

The pictogram 24 Used to add the action "exit" in a sequence of actions.

The pictogram 25 Adds the exit and stopjob action to a sequence of actions.

With the pictogram 14 in the rules definition bar 8th a selected action can be deleted from a sequence of actions.

Not only can the ticket rules be defined by adding and / or removing actions, but the actions themselves can be changed, deleted or recreated. These are under provided different action definition window. These windows each display a list of all the present actions of a type and allow editing, adding new actions, removing actions and copying actions. Each action has a specific status. Only correctly defined actions receive the status "true" which is represented by a black font. If false, the color of the font is red. An example of an action with a "false" status would be a condition without a defined control parameter.

• 1. Mit der rechten Maustaste wird eine ausgewählte Aktion im Regeldefinitions-Fenster 7 angeklickt.
• 2. Nach Auswahl einer Aktion im Regeldefinitionsfenster 7 wird ein geeignetes Piktogramm zum Hinzufügen einer Aktion (Piktogramm 17 bis Piktogramm 25) in der Regeldefinitionsleiste 8 angeklickt.

There are basically two ways to open an action definition window.

• 1. Right-click to select a selected action in the Rules Definition window 7 clicked.
• 2. After selecting an action in the rule definition window 7 becomes a suitable pictogram for adding an action (pictogram 17 to pictogram 25 ) in the rules definition bar 8th clicked.

The action definition window can be left by clicking on a "Cancel" or "OK" icon. The "OK" icon can only be selected if a valid entry of an action is selected. If the action definition window is removed from the policy definition window by means of an appropriate add icon 7 has been called, the new action is added to the existing sequence of actions after the selected action. Appeared by clicking a specific action in the rules definition window 7 When the action definition window is invoked, it will be the one in the rules definition window 7 Selected action replaced by the new action defined.

Actions, which are currently not used by any rule can be deleted. When editing an action being used by one or more rules opens a window listing the names of all ticket rules, who use this action and the user is prompted to do so to confirm, since this will change the definitions of the corresponding ticket rules.

Below The individual action definition windows are explained in more detail. Some General characteristics and agreements apply to all action definition windows. So every action can have a specific name. This name is unique for all ticket rules and allows the actions globally in all Call ticket rules. This means that if an action with changed a global name will be changed to all ticket rules that use this action. However, an action can also be provided without a name. Then can However, they are called only in a single ticket rule.

A such "nameless" action is only applied locally. With the right mouse button, a corresponding Action Definition window called to add a new action become. This window contains a list of all global and local actions. Will such a added local action again, so she will be added to this list lists even if an action of the same type already exists in the list should be. Hereby can copies the actions with the respective parameters as often as you like where each copy is a local action regardless of the original one Action is.

The Action Definition windows have a column for control parameters. These Control parameter column sees a special combo box to enter a ticket section and a control parameter (key). If the control parameter column is empty and the combo box is selected, a list of all known sections is displayed. After that you can the user the combo box call again and a list of all keys of the selected section is displayed. This can be done by double-clicking the control parameter selected without it being necessary to have an extensive list of all Call control parameters. If a section and a control parameter selected Also, a box ".." is offered to go back to first mode of the combo box to go, only the list of known Displays sections. Again, an empty box is offered, in a new section or key can be entered. These self-defined control parameters can be distinguished from the list of known ones Control parameters deleted become.

The action definition window for conditions, the condition definition window 26 ( 10 ) includes a condition definition menu bar 31 and a condition definition table 32 , The condition definition menu bar 31 includes the pictograms explained above 13 . 14 and 17 with the respective functions of adding, deleting and copying conditions.

each Contains condition a parameter, an operator and a value and can with a Be provided with names. The respective section and key can be out a pop-up window can be selected in each case. The offered List of keys hangs from the selected one Section off.

• – gleich
• – gleich (Groß- und Kleinschreibung ignorieren)
• – nicht gleich
• – nicht gleich (Groß- und Kleinschreibung ignorieren)
• – enthält
• – enthält (Groß- und Kleinschreibung ignorieren)
• – enthält nicht
• – enthält nicht (Groß- und Kleinschreibung ignorieren)
• – beginnt mit
• – beginnt mit (Groß- und Kleinschreibung ignorieren)
• – endet mit
• – endet mit (Groß- und Kleinschreibung ignorieren)
• – existiert nicht
• – kleiner als
• – größer als
• – kleiner oder gleich
• – größer oder gleich
• – ist nicht gesetzt
• – ist gesetzt
• – ist ganze Zahl
• – ist Fließkommazahl
• – ist Hexadezimalzahl
• – ist ASCII-Code
• – ist alphanumerisches Zeichen (A–Z, a–z)
• – ist Alnum (A–Z, a–z, 0–9)
• – ist eine Ziffer
• – ist eine Hexadezimalziffer (0–9, A–F, a–f)
• – ist regex

The operator can be selected from a pop-up window. The following operators exist:

• - equal
• - equal (case insensitive)
• - not equal
• - not equal (ignore case)
• - contains
• - contains (ignore case)
• - does not contain
• - does not contain (case insensitive)
• - begins with
• - starts with (case insensitive)
• - ends with
• - ends with (case insensitive)
• - does not exist
• - less than
• - greater than
• - Smaller or equal
• - greater or equal
• - is not set
• - is set
• - is integer
• - is floating point number
• - is hexadecimal number
• - is ASCII code
• - is alphanumeric character (A-Z, a-z)
• - is Alnum (A-Z, a-z, 0-9)
• - is a number
• - is a hexadecimal digit (0-9, A-F, a-f)
• - is regex

A condition with the operator "does not exist" is "true" if the specified key of the section should not exist in the job-related data. This condition differs from "is not set", which checks if a certain existing key is empty or does not exist. It suffices that one of these two conditions is met. The operator "is regex" is true if the particular parameter matches the digest that is in the corresponding value column in the condition definition table 33 is specified.

One Value can refer to a variable. Variables are represented by "$ {variable name}". To the Example it is possible to consider, whether the printer name (printer_name) equals the print job name (job_name) is. The definition of variables is described below.

If the variables are defined, it is also possible to change the content of variables to consider. Therefore the parameter Combo-Box also allows a special variable selection. If chosen a list of all defined variable names is displayed.

Of the Section "Files" requires one Special treatment, as it can occur several times. One condition in the Files section is true if it is applicable to at least one section. If a placement action (Setting) follows this condition, then this setting action is exclusively in running the file sections, that meet these conditions. If a set action is defined in a file section that is not followed by a condition using the file section, then the set action is executed in all file sections.

The definition of a condition is always automatically checked for correctness. If there should be errors, such as a reference to an undefined variable or to a control parameter containing only one key, then the condition action defined in red will be in the condition definition table 33 shown. If the condition is correct, it will be displayed in black.

Set actions become in the set definition window 27 ( 11 ) that defines a setting definition menu bar 33 (Setting definition menu bar) and a setting definition table 34 (Setting definition table) includes. The setting definition menu bar 34 includes the pictograms already explained above 18 . 13 and 14 for adding, deleting and copying set actions. Furthermore, it includes a pictogram 35 with which job tickets can be imported. A window displays all available job tickets. After selecting such a job ticket, it will be imported with all its actions, keys and values and can now be edited. This feature is primarily intended to generate default job tickets from the print job manager 1 be connected to the job-related data of the incoming print jobs and to supplement non-existent control parameters in incoming job-related data.

each Set action includes at least one parameter, a value, and an override flag and can be named. One value can change to one Refer to variable. A value can also be set to "[delete]", which means that the entire entry of the control parameter down to the keys in the Job ticket to delete is. This is different from the entry "", with nothing in the key is registered.

If the set action an already existing section or key entry Overwrite in the job-related data should, then the corresponding override flag must be set. The default status is a set overwrite flag.

Of the Section "files" requires one special treatment as this section can occur multiple times. If a set action follows a condition in a file section, which is true when applied to such a file section is, then this setting action is also carried out only in this file section. If a set action is defined in a file section and not depends on a condition that uses the file section, then the setting action applies to all file sections.

The correctness of the definitions of a set action is always checked automatically. If an error is detected, the set action becomes in the set definition table 35 shown in red letters. Otherwise it will be displayed in black letters.

• – der Name des Druckauftrages wird auf einen neuen Wert gesetzt, der mit dem Inhalt einer Variablen ($V>new_job_prefix<) beginnt und vom gefolgt wird und mit dem Wert einer weiteren Variablen ($V>new_job_name<) endet. Da das Überschreib-Flag gesetzt wird, wird diese Setz-Aktion auch ausgeführt, wenn ein entsprechender Eintrag bereits existiert.
• – Der Wert des Key „Client_Company” des Abschnittes „client” wird auf „MyCompany” gesetzt, aber nur wenn der Key nicht bereits existiert, da das Überschreib-Flag nicht gesetzt ist.
• – Für alle File-Abschnitte, die eine Bedingung erfüllen und die während der Bedingungsprüfung ausgewählt sind wird der Key „file_copies” auf einen neuen Variablenwert gesetzt. Falls die Setz-Aktion nicht von einer Bedingung abhängt, die den File-Abschnitt verwendet, wird der Key „File_Copies” in allen Dateien auf diesen Wert gesetzt.

The in the set definition window 27 ( 11 ) example of set actions mean the following:

• - the name of the print job is set to a new value that starts with the contents of a variable ($ V> new_job_prefix <) and is followed by and ends with the value of another variable ($ V> new_job_name <). Since the overwrite flag is set, this set action is also executed if a corresponding entry already exists.
• - The value of the key "Client_Company" of the section "client" is set to "MyCompany", but only if the key does not exist already, because the override flag is not set.
• - For all file sections which satisfy a condition and which are selected during the condition check, the key "file_copies" is set to a new variable value. If the set action does not depend on a condition that uses the file section, the key "File_Copies" will be set to this value in all files.

To edit variables is the variable editor window 28 ( 12 ) intended. The variable editor window 28 includes a variable definition menu bar 36 and a variable definition table 37 ,

each Variable has at least one unique variable name and a parameter. The name is necessary to make a variable can call. All variables represent global entries. Variables are called in the following form $ {variable name}.

A in a sequence of actions arranged variable delivers in operation a control parameter at the location where the variable is located is. This control parameter can already by previous actions changed have been.

• – Feld (Field): Hiermit wird der Inhalt einer Variable in Felder aufgeteilt und ein gewünschtes Feld wird herausgeschnitten.
• – Ersetzung (Replacement): Hiermit wird eine vorbestimmte Zeichenfolge durch eine andere Zeichenfolge ersetzt.
• – Berechnung (Calculation): Ändert den Wert einer ganzzahligen Variablen oder Fließkommazahlvariablen mittels einer mathematischen Operation.

The variable definition table 38 includes further columns "Alteration Type" and "Alteration Code". Here, a statement can be defined with which the content of the variable is changed when a control parameter for the variable is taken from incoming order-related data. There are three types of variable-changing actions:

• - Field: This divides the contents of a variable into fields, and a desired field is cut out.
• - Replacement: This is a predetermined string by another string replaced.
• - Calculation: Changes the value of an integer variable or floating-point variable by means of a mathematical operation.

To define the change rules, see the variable definition table 37 click on the corresponding variable. By clicking on the corresponding fields in the columns "Alteration Type" and "Alteration Code", respective drop-down menus open from which suitable entries can be selected.

If the value "Field" is entered in the column Alteration Type, a field definition window opens 38 ( 13 ) with which data fields are defined. This window defines a delimiter, which is a character used to separate each field entry in a string. If no field delimiter is specified, then this character is a separate data field. As a field delimiter, only a single character can be entered.

The input fields "From Field" and "To Field" can be used to enter the range of data fields to be extracted from a predefined string. For this purpose, the data fields are numbered twice, namely with positive integers, wherein the data field arranged at the left edge is assigned the value 1 and these values are increased from data field to data field by 1 in each case. When numbering with whole negative numbers, the numbering on the right arranged data field ends with the value -1 and decreases from data field to data field by 1 in the direction to the left. The following is an example of this numbering for the string "Testring":

In the input fields "From Field" and "To Field" both numbering can be used alternatively. The positive numbers are used when one wants to define a particular data field with respect to the left edge, and the negative numbers are used when one wants to define a particular data field with respect to the right edge. In this field definition window 38 In each case, a data field example ("Example") is automatically specified and in the line below it is shown what becomes of this data field example by the defined action ("becomes").

These Field definition is mainly used to cut out strings. However, it can also be used to cut certain numeric records become.

In the variable definition table 37 In the "Alteration Type" column, the entry "Replacement" can be entered, with which predetermined strings are replaced by other strings. This opens a replace definition window 39 in which a searched string is entered in the data field line "Find" and the string with which the searched string is to be replaced is entered in the data field line "Replace".

Furthermore, the number of replacements to be performed can be entered in the "Occurances" data field line. Either a whole positive number or "all" is entered here, which means that all found strings are replaced. Setting a flag will replace the string regardless of the case. Also in this replace definition window 39 Again, there is an example line "Example" in which a string is specified, which is changed in the line below it according to the defined definition ("becomes"). In the example lines, a user can also enter any string, which is then converted accordingly.

Is in the variable definition table 37 in the column "Alteration Type" a value "Calculation" is entered, then a calculation definition window opens 40 ( 15 ). In this calculation definition window 40 can in a field 41 an operator of one of the four basic arithmetic operations "+", "-", "*", or "/" can be entered and in a field 42 the calculation value that is applied to a variable for integers or floating-point numbers using the corresponding operator.

The system according to the invention allows the output of messages when the ticket rules at the print job manager 1 to be selected. This is particularly beneficial in conjunction with the centralized execution of all ticket rules, as these messages are mostly warnings and error messages are issued centrally in one place in the print job manager and so a reliable monitoring of the same is possible.

By clicking on the pictogram 20 in the rules definition bar 8th becomes the message editor window 29 ( 16 ) open. This window includes a message definition menu bar 43 and a message definition table 44 , In the message definition menu bar 43 are pictograms 20 . 14 . 13 to add, delete, and copy a message. Each message includes a message identifier ("Message-ID"), a message type ("Type"), a short message text ("Short Text"), a long message text ("Long Text") and an optional text ("Optional Text "). At least one short and one long message text must be entered for the message to be valid. The body of the message can also use variables whose contents are displayed when they are called.

To The creation of a message is always checked Correctness of the message. If the message is incorrect should, it is displayed in red, otherwise in black Font.

When clicking on the pictogram 21 in the rules definition bar 8th becomes a sub-rule window 45 ( 17 ), which lists all sub-ticket rules. Adding new sub-ticket rules is done in the rule activation list 9 by changing the corresponding entry for a specific rule to sub-rule rule in the Activation column. Therefore, the sub-rule window is used 45 for information only and not for editing the sub-ticket rules.

In the above-described system for automatically processing a print job, the print jobs with the associated job-related data automatically become the print job manager 1 edited, which is generated according to a predetermined ticket rule a pressure system specific job ticket.

In the context of the invention, it is also possible for a ticket rule to be called explicitly in the order-related data, so that control parameters of the job ticket or data ticket are not accidentally changed. To do this, enter the following command in the order-related data: TicketRule = "Test Rule 1" Between the quotation marks is the name of the ticket rule to be called.

The entry of the ticket rule in the order-related data can be done on the client 2 or at an upstream processing stage and / or when creating the job-accompanying data.

in the Within the scope of the invention, it is also possible to provide a super-ticket rule, the basically all incoming order-related data according to predetermined criteria and Parameters checked and in dependence from the exam calls up a suitable ticket rule, if one exists is, or an incoming job ticket without further verification by forward a ticket rule. In such an embodiment of the invention are not corresponding in the order accompanying data References to ticket rules to enter or no call when calling Provide parameters.

The Invention has been explained above with reference to an embodiment, in which either an incoming job ticket is supplemented or by a default job ticket one for the printing system specific job ticket is generated. As part of the However, it is also possible that an incoming job ticket of a certain format in the format used for job tickets in the present printing system.

The invention can be briefly summarized as follows:
The invention relates to a method, a printing system and a computer program for automatically processing order-related data of a print job.

With The invention relates to incoming order-related data of a print job checked centrally at a print job manager by means of predetermined ticket rules and, if necessary supplemented by further printing parameters or changed, so that from the order accompanying data a pressure system specific Job ticket is formed, with which the print order is correct in the respective printing system can be printed.

The central check of the order-related data at the print job manager allows an easy administration of the ticket rules and the proximity to the print server and the connected printing A printing system-specific processing of job tickets is possible.

1

Print Job Manager

2

client

3

computer

4

Ticket control module

5

main bar

6

dropdown

7

Rule Definition window

8th

Rule definition bar

9

Rule Action List

10

pictogram

11

pictogram

12

pictogram

13

pictogram

14

pictogram

15

pictogram

16

pictogram

17

pictogram

18

pictogram

19

pictogram

20

pictogram

21

pictogram

22

pictogram

23

pictogram

24

pictogram

25

pictogram

26

Condition definition window

27

Sit-definition window

28

Variable Editor window

29

News Editor window

30

31

Condition defining menu bar

32

Condition definition table

33

Sit-definition menu bar

34

Put Definition Table

35

pictogram

36

Variable definition menu bar

37

Variable definition table

38

Field Definition window

39

Replace definition window

40

Calculation definition window

41

field

42

field

43

News-definition menu bar

44

News Definition Table

45

Under Rule window

46

data line

47

interface

48

interface

Claims (18)

Method for automatically processing job-related data of a print job, which contain control parameters for controlling a printing process, in a printing system with a print job manager ( 1 ), several input modules ( 2 / 1 ), each with a computer ( 3 ), at which print jobs are generated, and a print server for feeding the print jobs to a print device, comprising Receiving a print job with the job-related data from one of the computers ( 3 ) by means of the input modules ( 2 / 1 ) and forwarding to the print order manager ( 1 ), - check the order-related data for errors, the check being performed according to predetermined ticket rules centrally at the print job manager ( 1 ), and the job-related data are changed and corrected as necessary, and outputting a printing system-specific job ticket, and - forwarding the print job with the printing system-specific job ticket to the print server. Method according to claim 1, characterized in that a central ticket rule module ( 4 ) on the print order manager ( 1 ), which manages all ticket rules. A method according to claim 2, characterized in that the job tickets exclusively by means of the ticket rule module ( 4 ) provided ticket rules are checked. Method according to claim 2 or 3, characterized in that the checking of the job tickets by the ticket rule module ( 4 ) is performed. Method according to one of claims 1 to 4, characterized that when checking the Job-related data a job ticket contained therein if required automatically changed becomes. Method according to one of claims 1 to 5, characterized in that the print job manager ( 1 ) order-related data incoming with a print job are combined with a default job ticket. Method according to one of claims 1 to 6, characterized that when checking the Job-related data the format of a job ticket contained therein automatically changed if necessary becomes. Method according to one of claims 1 to 7, characterized that the ticket rules comprise a sequence of actions. Method according to claim 8, characterized, that the sequence of actions one or a combination of one or includes several of the following actions: - condition: A value of one The control parameter of the job ticket is given a predetermined value compared and matched the result becomes "true" and at a distinction determines the result "wrong". - else: A value of a control parameter of the job-accompanying data is included compared to a predetermined value and at a match the result is "wrong" and at a distinction determines the result "true". - setting: This action becomes a key of a control parameter set to a predetermined value in the job ticket. - variable: The action variable defines a variable. - message: The message action generates a message depending on the value of a particular message Control parameters of the job-related data. - rule: With the action rule becomes another ticket rule within a predetermined ticket rule, the sub-ticket rule, called, calling the sub-ticket rule dependent on one or more control parameters of the order accompanying data takes place. - break: The action break immediately stops the execution of the ticket rule and if the ticket rule that terminates is a sub-ticket rule should be with the parent Ticket rule continued. - exit: The exit action ends Immediately the execution the ticket rule and if the ticket rule that terminates, one Under-ticket rule should not be with a parent Ticket rule continued. - exit and stopjob: This action stop execution immediately the ticket rule and it will not work with a parent ticket rule The processing of the print job is also finished. - switch / case: This action becomes a value of a control parameter of the job-related data compared with each value in a first column of a Table is specified and if a match with one of Values, the values of the row of this table become automatic in corresponding data fields, in particular in a corresponding Table entered in the ticket rule. A method according to any one of claims 1 to 9, characterized in that a variable arranged in a sequence of actions in operation has a control parameter at the location where the variable is located is, delivers. Method according to claim 10, characterized, that the contents of a variable are variable by one of the following Actions changed becomes: - Field: This splits the contents of a variable into fields and a desired one Field is cut out. - Replacement: Hereby becomes a replaced predetermined string with another string. - Calculation: Changes the Value of an integer variable or floating-point variable by means of a mathematical operation. A printing system for automatically processing a job ticket, comprising - a print job manager ( 1 ), - one or more clients ( 2 ), at which print jobs are generated, and - a print server for feeding the print jobs to a printing device, wherein the print job manager ( 1 ) for carrying out a method according to one of claims 1 to 10 with a ticket rule module ( 4 ) is provided. Printing system according to claim 12, characterized in that the ticket rule module ( 4 ) with an interface to clients ( 2 ), which are provided with a rule editor module with which ticket rules can be edited. Printing system according to claim 13, characterized the rule editor module has a graphical user interface (GUI) having. Printing system according to claim 13 or 14, characterized in that the ticket rule module ( 4 ) and / or the rules editor module are designed such that edited ticket rules are automatically checked for a correct syntax. Printing system according to one of claims 13 to 15, characterized in that the ticket rule module ( 4 ) and / or the rule editor module are designed such that all edited ticket rules stored in the ticket rule module and managed there. Computer program that is required to perform a procedure one of the claims 1 to 11 is formed. Computer program according to claim 17, characterized that the computer program is stored on a data medium.