DE102007009737A1 - Method for automatic operation of support data of print job, involves producing print job on one or more clients in printing system with print job manager, where print job contains control parameters for controlling printing process - Google Patents

Abstract

The method involves producing a print job on one or more clients (2) in a printing system with a print job manager (1). The print job contains control parameters for controlling a print process. A print server supplies the print job to a printing device. The print job is received with a support data by the clients through the print job manager. The support data is checked according to predetermined ticket rules central at the print job manager, where a print system-specific job ticket is released. Independent claims are also included for the following: (1) a print system for automatic operating of a job ticket (2) a computer program for carrying a support data operating method.

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 Digital Océ printing presses, 9th edition, February 2005 (ISBN 3-00-001081-5) Chapter 18.2 describes an Order Distribution System (ODS), which is also referred to as Workflow Manager. With this order Distribution System can control the entire digital printing process be a pre-press, a high-performance printer and a Finishing includes. In prepress, image and text files are created from different sources, such as scanner, digital camera, data carrier or a computer network merged and connected to one Layout station brought to its final form. Subsequently converts a printer driver created on different platforms For example, to convert data to Postscript files. These files can then be passed to a print server for printing. Print server Convert the data into compressed bitmaps that are fully automatic be imposed and forwarded to the printing system. The print server controls the printing process. The finishing of the Printed product includes, for example, binding or pasting of dividers.

The Order Distribution System is also for the central administration of the production variants. This includes the print service for Intranet and internet users. The Order Distribution System informs users about released production variants, takes print jobs complete with digital order bag, initiates automatic processing until the pressure. The Order Distribution System also monitors the correct execution of the selected printing and postprocessing 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 created by the user when creating of the print job or created automatically in a printing system become.

Traditional job tickets have clear instructions that must be implemented accordingly. The printing process is becoming more and more extensive as more and more devices are integrated into a single printing process, which increases the variety of functions. In addition, the Internet and Intranet increasingly make print processes regionally distributed or assigned to a pool of printers that can be regionally distributed. In addition, devices from different manufacturers increasingly have to work together in one process. In order to cope with these increased requirements, a uniform specification for the exchange of data formats in the printing process has been agreed, which is referred to as the Job Definition Format (JDF). There is a corresponding job message format (Job Messaging Formats or JMF), which is specified accordingly. The specification of JDF may be from the website www.cip4.org The current specification is JDF Specification Release 1.3.

JDF is an XML-based format with instructions for the printing process are arranged in a tree structure. Every node (node) of the tree structure comprises an instruction or a set of instructions. The topmost node is called the root. The end nodes Branches are called leaf nodes.

The Special feature of JDF is that it is called Intent node which can be a very general statement for one Include printing process that needs to be specified to to be able to be executed on a device.

From the EP-A2-1 197 838 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 by means of a master job ticket, which is also referred to as a super job ticket, can be controlled at once, so that the multiple document processing jobs by means of the master job ticket at a time in the documents Processing system can be abandoned.

From the US 5,718,520 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.a.a.0.) Comes with the trade name Océ PRISMAproduction server system that handles a wide range of data streams processed or converted, which is then printed on IPDS printers become. The Océ PRISMAproduction server system includes one Print job manager 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.

As a "server" are called software modules that do a central job. As "clients" software modules are called with a server and receive data from the server or transmit to them. With a server can several clients are in contact at the same time.

at This known client / server system will print jobs generated by 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 come. At the clients upstream of the print job manager the incoming print jobs are checked and if necessary customized. This adjustment may be data accompanying the print job or information, including the contents of the job tickets the printing environment is adjusted. 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. For example, job tickets often contain printer names that are in the present Printing system are not available. To correct such erroneous Job tickets are provided to the clients computer programs that Check the job tickets automatically and correct them if necessary. These computer programs are individualized as scripts programmed the individual clients and their applications. It is Also common is that on a client several such scripts are provided, for example, different sources or Job tickets with print data in different data formats each to revise. These scripts have proven themselves because hereby the incoming print jobs become automatic controlled and corrected so that the entire printing process without Delay can expire.

kick nevertheless an error due to a wrong parameter in the job ticket during the printing process, so it is at the present Design of the printing system difficult to determine where and through what the error has been caused. For this must be on the one hand be traced over which client the print job has been supplied to the print job manager, and then It must be determined with which script the job ticket is processed 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 Customer or when transferring the print job to the client has been caused.

Of the The invention is therefore based on the object, a method, a Printing system and a computer program for automatic editing to create job-related data for a printing process, this without delay of the printing process an automatic Control of job tickets allowed and yet easy to understand 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, the 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 drucksys specific job tickets, and
• - Forward the print job with the job ticket to the print server.

The inventive method is characterized from that checking the job-accompanying data according to the predetermined ticket rules centrally on the print job manager is performed.

There the order-related data centrally and preferably exclusively Checked or checked at the print job manager are those that are applied to a particular print job Ticket rules easy to understand, because the ticket rules are only in one place, namely the print order manager, and not, as is the case in the prior art, on a wide variety of Clients available and there to examine each. Furthermore is through the central execution of the review the order-related data at the print order manager ensures that all incoming order-related data is checked according to the same ticket rules or controlled and if necessary amended accordingly and corrected.

Farther are by centrally performing the checking the order-related data to manage the ticket rules centrally, whereby they are also centrally controllable and avoided that similar order-related data or similar Errors in order-related data are corrected differently.

One Another advantage of checking the order-related data central to the print job manager is that the review the job-related data in the process chain very close to the concrete Pressure device is done, so this review very specific to the particular printing device can be. This can improve the quality of the review be increased considerably. In the execution of the review of Job-related data to the clients is the problem that the Clients communicate with different print job managers can, so have a check on it the job-related data to the pressure equipment associated with the different print order managers can be reached, must be adapted, which in turn is very difficult.

By the central administration of the ticket rules it is also possible to provide the operator with tools that Create and manage the ticket rules easier. Especially it is useful to have a graphical user interface (GUI) in which the ticket rules are created and managed be able to provide a software module with which the syntax of the edited ticket rules automatically to a correct one Syntax is checked.

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 Print job contains at least one print job Print file.

One Order ticket contains information about a whole order, such as B. delivery address, order date, desired delivery date, etc.

One Jobticket contains all for processing a print job necessary data. These data include control parameters that in a workflow for the print job (lob-workflow) are relevant. The job ticket is in a corresponding ticket format coded.

One Default job ticket contains default data that is appropriate are, a print job that has no further editing information contains, in an existing printing system or an existing printing environment issue. Such data are control parameters and can z. B. names or addresses of printing devices, the the respective print server 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 Order-related data can be both a total order ticket, a job ticket and / or a data ticket or control parameters that are attached in a different form to a print job include. Control parameters are often in the file name of the print job inserted.

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 the job is accompanied by a job ticket, the job ticket is checked based on the ticket rules, whether it is suitable as a pressure system-specific job ticket and if necessary, - what The rule is - changed and in particular by Pressure system-specific parameters from the default ticket added.

The The invention will be described in more detail below by way of example explained in the drawings embodiment. 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 the print order 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 using the ticket rule module and on the print job manager brought to execution.

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 Jobticket contains a list of control parameters for controlling of the respective print job. The control parameter list is in with subdivided sections. There is one 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" and a specific value, called "value" is designated. For example, in the section "files" a control parameter with 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 each branch by the conditions "condition" or "else" and the leaves are running 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 to this Function containing 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 have its own Windows are entered manually. Optionally, the generated Description or the self-generated description. The manually created description will be accompanied by a corresponding description Usually saved.

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

One User can specify if a specific rule is active or "inactive." The "inactive" mode is used when a certain rule is not on incoming job tickets should be applied. This is useful with old rules, which should not be used temporarily or for new ones Rules that have not been tested yet. Thus it is possible a ticket rule for later use too 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 included 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.

It Not only can the ticket rules be added by adding and / or remove actions are defined, but the actions even can be changed, deleted or be recreated. These are different action definition windows intended. These windows each show a list of all available 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 get the status "true" by a black one Font is displayed. When a status is "wrong" the color of the font red. An example of an action with a "wrong" 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 rules definition window by means of a suitable 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 become. When editing an action by one or more Rules is used, a window opens in which the Names of all ticket rules are listed that perform this action use and the user is prompted to confirm this since this changes the definitions of the corresponding ticket rules becomes.

Below The individual action definition windows are explained in more detail. Some general features and agreements apply to all action definition windows. So every action can have a specific one Have names. This name is unique to all ticket rules and allows the actions to be called globally in all ticket rules. This means that when an action is changed with a global name will change all the ticket rules that use this action become. However, an action can also be provided without a name. But then it can only be called in a single ticket rule become.

A such "nameless" action is only applied locally the right mouse button can be a corresponding action definition window be called to add a new action. This Window contains a list of all global and local actions. If such a local action is added again, then They also listed in this list, too if an action of the same type already exists in the list should be. Hereby the actions with the respective Parameters are copied as often as possible, each copy being a local Action independent of the original action is.

The Action Definition windows have a column for control parameters on. This control parameter column sees a special combo box for entering a ticket section and a control parameter (key) in front. If the control parameter column is empty and the combo box is selected, becomes a list of all known sections displayed. After that, the user can call the combo box again and a list of all keys of the selected section is displayed. This can be done by double-clicking the control parameter be selected without it being necessary to have an extensive List of all control parameters. If a section and A control parameter has also been selected Field ".." offered to go back to the first mode of the Combo box, which only displays the list of known sections. Again, an empty field is offered, in which a new section or a new key can be entered. These self-defined Control parameters may be from the list of known control parameters to be deleted.

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 Condition contains a parameter, an operator and a Value and can be given a name. The respective section and key can be selected from a pop-up window respectively become. The offered list of keys depends on each one selected section.

• – 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 is different from "is not set", which checks whether a given 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 one is true Parameter matches the statement that is in the corresponding value column in the condition definition table 33 is specified.

One Value can refer to a variable. Variables are labeled "$ {variable name}" shown. For example, it is possible to check 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 use the Check contents of variables. Therefore, the parameter allows Combo box also has a special variable selection. If chosen a list of all defined variable names is displayed.

Of the Section "Files" needs a special treatment, because he can occur several times. A condition in the section "Files" is true if it applies to at least one section. If a setting action follows this condition, then this setting action exclusively in the file sections executed 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 as "[delete]" be, which means that the entire entry of the control parameter to delete the keys in the job ticket. This makes a difference itself from the entry "", with which nothing is registered in the key.

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

The section "files" needs a special treatment because this section can occur multiple times, if a set action follows a condition in a file section, which is true if it is on one File section is applied, then this setting action is performed exclusively only in this file section. If a set action is defined in a file section and does not depend on a condition that uses the file section, then the set 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 that satisfy a condition and that are selected during the condition check, the key "file_copies" is set to a new variable value, so if the set action does not depend on a condition using the file section, the Key "File_Copies" in all files set to this value.

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 have been changed.

• – 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: Replaces a predefined string with another string.
• - 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, and if no field delimiter is specified, then that character is a separate data field Characters are 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 which the data fields are numbered twice, namely with positive integers, with the data field at the left Value 1 is assigned and these values are increased from data field to data field by 1. When numbering with integer numbers, the numbering on the right arranged data field ends with the Value -1 and decreases from data field to data field by 1 towards 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 out certain numerical records be used.

In the variable definition table 37 In the "Alteration Type" column, the entry "Replacement" can be entered, with which predefined strings are replaced by other strings by opening 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 data field line "Occurances", where either a whole positive number or "all" is entered, which means that all found character 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 advantageous in connection with the centralized execution of all ticket rules, since these messages, which are primarily warnings and error messages, are output centrally at one point in the print job manager and thus 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 in order for the message to be valid.

To The creation of a message is always checked on correctness of the message. If the message is not correct it should be 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 particular rule to sub-rule rule in the Activation column, so 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 mark is the name of the person to call Ticket rule.

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 Under the invention, it is also possible to have a super ticket rule principle, all incoming order-related data checked according to predetermined criteria and parameters and depending on the exam one each calls appropriate ticket rule, if one exists, or an incoming job ticket without further verification through 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 The invention is explained above with reference to an embodiment in which either an incoming job ticket complements or by using a default job ticket for the printing system specific job ticket is generated. Within the scope of the invention However, it is also possible for an incoming job ticket of a certain format in that applied in the present printing system Format for job tickets is converted.

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 optionally supplemented by further pressure parameters or changed so that from the order accompanying data pressure-system-specific job ticket is formed with which of the Print order to be printed correctly in the respective printing system can.

The central review of order-related data The print job manager allows easy management of the ticket rules and by the proximity to the print server and the connected Pressure equipment is a very pressure system-specific processing Job tickets 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

QUOTES INCLUDE IN THE DESCRIPTION

This list The documents listed by the applicant have been automated generated and is solely for better information recorded by the reader. The list is not part of the German Patent or utility model application. The DPMA takes over no liability for any errors or omissions.

Cited patent literature

• - EP 1197838 A2 [0008]
• US 2002/0080400 A1 [0009]
• US 5718520 [0010]

Cited non-patent literature

• - www.cip4.org [0005]

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 ), one or more clients ( 2 ), 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 clients ( 2 ) by the print order manager ( 1 ), - check the order-related data according to predetermined ticket rules centrally at the print job manager ( 1 ) 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 in that when checking the job-accompanying data contains a job ticket if required is changed automatically. 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 in that when checking the job-accompanying data is the format of a job ticket contained therein Need to be changed automatically. Method according to one of claims 1 to 7, characterized in that the ticket rules a sequence of Include actions. A method according to claim 8, characterized in that the sequence of actions comprises one or a combination of one or more of the following actions: condition: a value of a control parameter of the job ticket is compared with a predetermined value and if it matches the result is "true" and if differentiated, the result is determined to be "false". - else: A value of a control parameter of the job-related data is compared with a predetermined value, and if there is a match, the result is determined to be "false" and if different, the result is "true". - setting: With this action, a designation (key) of a control parameter in the job ticket is set to a predetermined value. - variable: With the action variable a variable is defined. - message: The action message generates a message depending on the value of a specific control parameter of the job-related data. - rule: With the action rule, another ticket rule, the sub-ticket rule, is called within a predetermined ticket rule, whereby the call of this sub-ticket rule takes place as a function of one or more control parameters of the job-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, and if the ticket rule that terminates should be a sub-ticket rule, it will not continue with a parent ticket rule. - exit and stopjob: This action immediately stops the execution of the ticket rule and it does not proceed with a parent ticket rule and the processing of the print job is also terminated. Switch / case: This action compares a value of a control parameter of the job-related data with each value specified in a first column of a table and if a match with If one of the values is present, 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. Method according to one of claims 1 to 9, characterized in that one in a series of actions arranged variable in operation a control parameter at the location where the variable is located provides. Method according to claim 10, characterized, that the content of a variable by one of the following variable-changing ones Actions is changed: - field: hereby the content of a variable is divided into fields and a desired one Field is cut out. - Replacement: hereby becomes a predetermined string by another string replaced. - Calculation: Changes the value of a integer variables or floating-point variables using 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 that the rule editor module has a graphical user interface (GUI). Printing system according to claim 13 or 14, characterized in that the ticket rule module ( 4 ) and / or the rule 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 used to run a Method according to one of claims 1 to 11 formed is. Computer program according to claim 17, characterized that the computer program is stored on a disk is.