JP2004288038A - Data processing system and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To flexibly manage history information of a job when performing a predefined series of processing in cooperation on a network. <P>SOLUTION: Setting of an adding condition whether or not an original document (original data) from a user is added to the history information and setting of condition of the number to be an upper limit value of the registration number of the history information which is registered as a job history, by displaying a condition setting screen (step ST2, ST3). Storage condition information for indicating the adding condition and the condition of the number set by a user is generated (step ST4). The generated storage condition information is stored in association with a corresponding rule (step ST5). When a rule is implemented, the original data is added and the number of the registration of the job history is managed, based on the storage condition indicated from the storage condition information, in reference to the storage condition information stored in association with the implemented rule. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a data processing system and a program, and more particularly, to a data processing system and a program that perform a series of predefined processes in cooperation with each other on a network.
[0002]
[Prior art]
2. Description of the Related Art Conventionally, a network in which a paper document and electronic information are shared by connecting a scanner, a facsimile (hereinafter, referred to as a “FAX”), a copying machine, or a multifunction machine combining these, a personal computer, and a mail server via the network. There is a system.
[0003]
Such a network system fetches a document file from an input system such as a scanner or a paperless facsimile that reads a document, passes through a processing system such as image processing and character recognition, and then outputs the document file via an output system such as a printer or a mail server. To the outside.
[0004]
Usually, the import, processing, and distribution of a document file are performed independently. For this reason, if the operator wants to continuously execute the import, processing, and distribution of the document file, the operator must perform predetermined settings for each of the import, processing, and distribution. In other words, the operator has to open windows for capturing, processing and distribution one by one and perform a predetermined input operation, which is very inconvenient.
[0005]
For this reason, conventionally, a workflow system has been introduced which executes a series of processes from capture to distribution in a predetermined order in cooperation with each other on a network. A workflow system is often developed by directly converting an existing paper-based business system as it is, assuming a workflow generally used in an office such as approval and circulation (for example, see Patent Document 1, Patent Document 1). Reference 2 and Patent Reference 3).
[0006]
[Patent Document 1]
JP-A-2002-99686
[Patent Document 2]
JP 2001-325389 A
[Patent Document 3]
JP 2001-195295 A
[0007]
[Problems to be solved by the invention]
However, the conventional workflow system uniformly manages the history of the input job, which may cause inconvenience to the user.
[0008]
For example, from the viewpoint of error recovery, it is preferable to keep the original document data in the job history, but in the case of highly confidential document data, it is required to delete the original data immediately after the processing is completed. If it remains in the job history, it will cause a problem.
[0009]
Further, for example, since original document data is added to the job history, if the number of storable job histories becomes extremely small due to the limitation of the memory capacity, it becomes meaningless as history information. More specifically, when the frequency of inputting a job is high, such as receiving a facsimile frequently, if normal jobs are input one after another after an abnormal job in which an error has occurred, the job history of the normal job input later is used. When the memory becomes full, the history of the abnormal job may be erased from the memory, and the error cannot be recovered.
[0010]
The present invention has been made in order to solve the above problems, and a data processing system capable of flexibly managing job history information when performing a series of predefined processes in cooperation with a network. The purpose is to provide the program.
[0011]
[Means for Solving the Problems]
In order to achieve the above object, a data processing system according to claim 1 accepts and accepts settings of a destination of a document data, a method of processing the captured document data, and a distribution destination of the processed document data. Storage means for storing a rule that defines a series of processing for taking, processing, and distributing the document data based on the setting result, and execution means for executing the series of processing in a network in accordance with the rule. Storage means for storing job history information as a history of executing the series of processes in accordance with the rule by the execution means; and a condition for adding or not storing the document data to the job history information. Setting means for setting an accumulation condition; and managing accumulation of the job history information in the accumulation means based on the accumulation condition set by the setting means. It is characterized in that it comprises a management means.
[0012]
According to the data processing system of the first aspect, the storage unit accepts and accepts the setting of the destination of the document data, the method of processing the captured document data, and the distribution destination of the processed document data. Based on the result of the setting, a rule defining a series of processing of taking, processing, and distributing the document data is stored. The rule is read out as appropriate, and a series of processing according to the rule is executed by the execution unit. Are executed in cooperation on the network. As described above, when a series of processes according to the rules are executed by the execution unit, job history information indicating the execution state at that time is accumulated in the accumulation unit as a job history (so-called job history).
[0013]
The setting means sets accumulated information including at least whether or not to add document data to the job history information. Then, the storage of the job history information in the storage is managed by the management based on the storage information set by the setting. That is, if the document data is set as the storage condition, the document data corresponding to the job history information is added and stored in the storage unit, and if the document data is not added, the job history is added. Only information is stored in the storage means.
[0014]
By setting the storage conditions in this way and storing the job history information based on the set storage conditions, the job history can be managed flexibly.
[0015]
In addition, the accumulation condition may further include, for example, an upper limit of the accumulation of the job history information, in addition to whether or not the document data is attached.
[0016]
Further, as set forth in claim 3, the setting unit distinguishes, for each rule, a normal job in which the series of processes has been completed normally and an error job in which an error has occurred in the series of processes. The accumulation condition according to at least one of a job type, a device type on the network, the capturing destination, the processing method, and the distribution destination that are constituent elements of the rule, and at least one of the types of the jobs. Should be set.
[0017]
The above data processing system can be realized by causing a computer on a network to execute the following data processing program.
[0018]
That is, as described in claim 4, the computer accepts the settings of the destination of the document data, the method of processing the captured document data, and the destination of the processed document data, and the received setting result Based on the above, a series of processes according to the rules are controlled such that the series of processes are performed in cooperation with each other on a network according to a rule that defines a series of processes of taking, processing, and distributing the document data. Is a data processing program for accumulating job history information indicating an execution state when is executed, wherein the computer includes at least a condition as to whether the document data is added to the job history information and accumulated. A condition is set, and accumulation of the job history information in the accumulation means is managed based on the set accumulation condition. It is sufficient to execute the over data processing program.
[0019]
In the above-mentioned data processing program, the computer may be configured to set the accumulation condition further including a registration upper limit number of the job history information.
[0020]
In addition, as described in claim 6, for each of the rules, a job type distinguished by a normal job in which the series of processes has been normally completed and an error job in which an error has occurred in the series of processes, The storage condition may be set according to at least one of a type of a device on a network, the capture destination, the processing method, and a distribution destination that are constituent elements of the rule, and a type of the job. It may be.
[0021]
BEST MODE FOR CARRYING OUT THE INVENTION
Next, an example of an embodiment according to the present invention will be described in detail with reference to the drawings.
[0022]
[System configuration]
FIG. 1 is a diagram showing a schematic configuration of a document sharing network system 1 according to an embodiment of the present invention.
[0023]
The document sharing network system 1 includes a plurality of MFPs 10 having both a print function, a scanner function, and a facsimile function, a mail server 20 for transmitting and receiving e-mail, a plurality of terminal devices 25, and a predetermined fetching of document. And a control device 30 for performing control for distributing to a predetermined distribution destination after performing predetermined processing by taking in from a destination. The document referred to here corresponds to the document data of the present invention and is mainly image data relating to the document. However, the document may include text data according to the state of the processing, and is not particularly limited. .
[0024]
The multifunction peripheral 10, the mail server 20, each terminal device 25, and the control device 30 are interconnected via the network 5. Although not shown, a printer, a scanner, and a facsimile machine may be connected to the network 5, respectively.
[0025]
FIG. 2 is a diagram illustrating an outline of the processing of the document sharing network system 1. The MFP 10, the mail server 20, and the terminal device 25 are interconnected via the network 5, but usually operate independently. Therefore, the control device 30 sets a capture destination, a processing method, and a distribution destination in the document sharing network system 1, and automates / standardizes a series of processes from capturing, processing, and distribution of a document to provide a core service. It is.
[0026]
Here, what is defined for automating / typing a series of processes is called a "rule". The setting of the rule will be described later. In addition, application programs that provide specific functions of capture, processing, and distribution are referred to as input plug-ins, processing plug-ins, and output plug-ins.
[0027]
FIG. 3 is a block diagram illustrating a configuration of the multifunction peripheral 10.
[0028]
The multifunction peripheral 10 can provide functions of an input system plug-in and an output system plug-in, and includes a scanner unit 11 that reads an image recorded on a document, an electrostatic latent image recorded on a photoconductor, and an electrostatic latent image. A printer unit 12 that develops the latent image using monochrome toner or color toner, transfers the developed image to recording paper, and outputs the same, and a facsimile (hereinafter, “FAX”) unit 13 that sends and receives facsimile messages. Have.
[0029]
The multi-function device 10 further includes a controller 14 for controlling the entire device, a memory 15 for storing image data read by the scanner unit 11, image data received via the network 5, data of a FAX reception message, and the like. A display panel 16 for displaying an operation screen and inputting operation information in response to a touch on an icon, an input / output port 17 for inputting / outputting data, and a communication control unit for communicating with devices connected to a network 18 is provided.
[0030]
The scanner unit 11, the printer unit 12, the FAX unit 13, the controller 14, the memory 15, the display panel 16, and the input / output port 17 are interconnected via a bus. The input / output port 17 is connected to the network 5 via the communication control unit 18. Note that the scanner unit 11 may be incorporated as a part of the FAX unit 13.
[0031]
In the MFP 10 according to the present embodiment, the predetermined storage area of the memory 15 is partitioned as a plurality of confidential BOXs 15B, and each confidential BOX 15B is managed by a BOX number (for example, BOX numbers 1 to 300). The multifunction device 10 can also assign a file name to a document scanned by the scanner unit 11 or a document received by the FAX unit, save the document in the confidential BOX 15B, and transmit the document to a destination set in advance for the confidential BOX 15. It has become.
[0032]
The mail server 20 can provide functions of an input system plug-in and an output system plug-in, and is a server that performs transmission and reception of e-mail of each terminal device 25 connected to the network 5.
[0033]
The terminal device 25 can provide the functions of an input system plug-in, a processing system plug-in, and an output system plug-in, and is a so-called personal computer. The terminal device 25 transmits / receives an e-mail to / from the outside via the mail server 20, stores a document in a file folder, and performs predetermined image processing on the document.
[0034]
The control device 30 sets a rule as a workflow, and executes a series of processes from fetching, processing, and distribution of a document based on the rule. Note that the control device 30 may be a processing system plug-in.
[0035]
FIG. 4 is a block diagram illustrating a configuration of the control device 30.
[0036]
The control device 30 includes a CPU (Central Processing Unit) 31 for controlling the whole, a RAM (Random Access Memory) 32 for temporarily storing data as a work area, a ROM (Read Only Memory) 33 for storing a control program of the CPU 31, and a rule. And a CD-ROM drive 35 for displaying a rule setting screen or the like for setting a rule.
[0037]
The control device 30 further stores and reads out a program for automating / standardizing a series of processes from document acquisition, processing and distribution, an application program for functioning as a processing system plug-in, predetermined data, and the like. It includes a hard disk drive 36, a keyboard 37 for inputting sentences and symbols, a mouse 38 as a pointing device, an interface 39 to which these are connected, an input / output port 40, and a communication control unit 41.
[0038]
The CPU 31, the RAM 32, the ROM 33, the interface 39, and the input / output port 40 are connected to a communication control unit 41 that communicates with another device such as the MFP 10 connected to the network 5.
[0039]
The keyboard 37 is used to directly input information specified by the user when various setting screens are displayed on the display 34. When various setting screens are displayed on the display 34, the mouse 38 is used to select the displayed one or to input the contents of the setting instruction.
[0040]
[Example of rules]
FIG. 5 is a diagram illustrating an example of a rule that can be created by the control device 30 by arbitrarily combining an input system plug-in, a processing system plug-in, and an output system plug-in.
[0041]
For example, Rule 1 fetches a document from a plurality of input system plug-ins (FAX reception service, file folder, scan service), and processes a plurality of processing system plug-ins (image processing, optical character recognition (OCR), attribute assignment / distribution). , It is defined that the document that has undergone these processes is delivered to a plurality of output system plug-ins (file folder, print output).
[0042]
Rule 2 defines that a document is fetched from a file folder and a Mail_MAPI input, and the processed document is distributed to an external service cooperation folder via image processing and attribute assignment / distribution processing.
[0043]
Rule 3 defines that a document is fetched from a file folder, and the processed document is delivered to the file folder through image processing, an OCR cooperation module, and attribute assignment / distribution processing.
[0044]
Rule 4 is that a document is fetched from a confidential BOX 15B of a predetermined BOX number, processed through automatic erecting, OCR, file name creation / attachment, image / text binding processing, and a plurality of output system plugs (File folder, print output).
[0045]
The rules 1 to 4 perform format (FMT) conversion necessary for the next process before and after each processing system plug-in.
[0046]
Here, as the input system plug-in, for example, there are a FAX reception service, a file folder, a scan service, a Mail_SMTP input, a POP client, and a Mail_MAPI input, as shown in FIG. The confidential box shown in FIG.
[0047]
Processing plug-ins include image processing, OCR, attribute assignment / distribution, and OCR coordination modules.
[0048]
The output system plug-in includes, for example, a file folder, an external service cooperation folder, an ftp output, a file message, a Mail_SMTP output, and a Mail_MAPI output. Note that the input, processing, and output plug-ins are not limited to those described above.
[0049]
[Functional configuration of control device]
Next, with reference to FIG. 6, a description will be given of a function of the control device 30 according to the present embodiment for automating / standardizing a series of processes from creation of the above-described rule and acquisition, processing, and distribution of the document. I do. FIG. 6 is a diagram showing a functional configuration constructed in the control device 30 by using the hardware resources shown in FIG.
[0050]
As shown in FIG. 6, the functions of a core service unit 200, an application service unit 210, and a communication unit 220 are configured in the control device 30.
[0051]
The core service unit 200 is constructed by executing, by the CPU 31, a control program resident in the memory when the control device 30 is started, and includes a rule creation / management unit 201, a rule check unit 202, a plug-in state check unit. 203, a storage condition creation unit 204, and a rule / storage condition memory 205.
[0052]
The rule creation / management unit 201 displays a rule setting screen (details will be described later) on the display 34, and sets an import destination, a processing method, and a distribution destination based on information input by the user via the rule setting screen. , Create a rule that defines a series of processes from document acquisition, processing, and distribution.
[0053]
The rule creation / management unit 201 stores the created rule in the rule / accumulation condition memory 205. That is, the rule / accumulation condition memory 205 corresponds to the storage unit of the present invention, and a predetermined storage area of the hard disk drive 36 can be used as the rule / accumulation condition memory 205, for example. Further, an external storage medium (not shown) may be used as the rule / accumulation condition memory 205.
[0054]
Further, the rule creation / management unit 201 can also accept a rule modification via the rule setting screen and update the rule registered in the rule / accumulation condition memory 205. The rule creation / management unit 201 manages only the currently executable rules from the created rules so that the rules can be executed.
[0055]
The rule check unit 202 checks the consistency of the created rules. Specifically, based on the data format that can be input / output of each plug-in, it is determined whether or not there is a format mismatch between the plug-ins connected before and after, thereby checking whether the rules are appropriate. Based on the check result, the rule creation / management unit 201 notifies the user of an error, prompts the user to correct the rule, and receives the rule correction.
[0056]
The plug-in status check unit 203 checks the status (operable / inoperable) of each plug-in. Specifically, it is determined whether devices (multifunction device 10, mail server 20, terminal device 25, control device 30, etc.) functioning as plug-ins are connected to network 5, and whether the devices are activated. Or whether an application program for causing this apparatus to function as a corresponding plug-in is installed, and for a file folder or confidential BOX, whether the file folder or confidential BOX exists or not, and whether the memory is full. Checked. The rule creation / management unit 201 manages whether each rule is executable based on the check result of the plug-in status check unit 203.
[0057]
The accumulation condition creation unit 204 functions as a setting unit of the present invention, and sets accumulation conditions of history information that is a job history of a rule executed by the rule execution unit 211 described below. More specifically, various screens for setting accumulation conditions (hereinafter, referred to as condition setting screens, which will be described in detail later) are displayed on the display 34, and based on information input from the user via the condition setting screens, accumulation conditions for the history information are displayed. Set. That is, the user can set desired storage conditions.
[0058]
The storage condition set here may include at least a condition (hereinafter, an attachment condition) as to whether or not to attach an original document (hereinafter, original data) to the history information. In the present embodiment, A description will be given of a case where, as the accumulation condition, a condition of an upper limit value of the number of registrations of the history information to be registered as the job history (hereinafter, a number condition) is set together with the attachment condition. In addition, for example, when the original data is attached, whether to compress the data may be set as the storage condition.
[0059]
Further, in the present embodiment, as an example, a case will be described in which a storage condition is set for each rule, and information representing the set storage condition is stored in the rule / storage condition memory 205 in association with a corresponding rule.
[0060]
The application service unit 210 operates when a predetermined execution timing of a rule is reached, that is, is constructed when the CPU 31 executes a process according to the rule, and includes a rule execution unit 211, a history registration management unit 212, and a history memory 213. It has.
[0061]
The rule execution unit 211 functions as an execution unit, and executes a rule, that is, performs a control process so that a series of processes is performed according to the rule. In the following, a single control process in the rule execution unit 211 for performing a series of processes according to a rule is referred to as a “job”, and a process in which the control process is completed (rule execution completed) is referred to as a “completed job”. A completed job in which a series of processes is completed normally is referred to as a “normal job”, and a job in which an error occurs during the series of processes is referred to as an “error job”.
[0062]
Specifically, the rule execution unit 211 uses the RAM 32 as the buffer 211A and, when a job is started, first stores the document fetched from the input plug-in in the buffer as original data. Then, processing of the processing system plug-in and storage of the original data in the output system plug-in are performed. At this time, various data (so-called intermediate files) generated on the way are also appropriately stored in the buffer. After the job is completed, data related to the job, such as original data and intermediate files, is deleted from the buffer 211A.
[0063]
The history registration management unit 212 functions as a management unit of the present invention. Specifically, when the rule is executed by the rule execution unit 211, the history registration management unit 212 generates history information (corresponding to job history information) indicating that the rule has been executed. The history information in this case includes, for example, information indicating a rule name (or an ID given by the system for managing the rule), a job ID, the number of pages of the document, an execution result (normal end / error), and the like. It is.
[0064]
In addition, the history registration management unit 212 refers to the accumulation condition information stored in the rule / accumulation condition memory 205 in association with the executed rule, and generates, based on the accumulation condition indicated by the information. The registered history information is registered in the history memory 213 as a job history. As a result, history information is accumulated in the history memory 213. That is, the history memory 213 corresponds to the storage unit of the present invention, and a predetermined storage area of the hard disk drive 36 can be used as the history memory 213, for example. Further, an external storage medium (not shown) may be used as the history memory 213.
[0065]
The communication unit 220 uses the core service unit 200 and the application service unit 210 to transmit / receive data to / from another device, check the status of a plug-in realized by the other device, and notify an error to the other device. And a communication through the network 5.
[Create Rule]
FIG. 7 is a diagram showing an example of the rule setting screen 50 for creating a new rule or editing an existing rule.
[0066]
The rule setting screen 50 is displayed on the display 34 by the operation of the rule creation / management unit 201, and instructs a rule name box 51 for entering a rule name, a rule explanation box 52 for entering a rule explanation, and automatic creation of a rule explanation. An explanation automatic creation button 53, an OK button 54 for creating a rule in accordance with the contents entered in each item, and a cancel button 55 for canceling the input processing are provided.
[0067]
The rule name box 51 displays a rule name of a rule to be newly created or edited. At the time of new creation, the rule name box 51 is blank, and the rule name is a required input item.
[0068]
The rule description box 52 displays the description of the rule name displayed in the rule name box 51. The input in the rule explanation box 52 is optional.
[0069]
The description automatic creation button 53 is a button for automatically creating a rule description based on the contents of the plug-ins of the input destination, processing method, and distribution destination that have already been input. Then, the rule description created when the automatic description creation button 53 is clicked is displayed in the rule description box 52.
[0070]
The OK button 54 is a button for creating a rule based on the contents of the plug-in of the import destination, the processing method, and the distribution destination. The cancel button 55 is a button for canceling a new rule creation or editing process.
[0071]
Here, the rule setting screen 50 includes a capture destination drop-down list 61, a capture destination drop-down button 62, a capture destination list box 63, a capture destination edit button 64, and a capture destination delete button 65 related to the capture destination. .
[0072]
The import destination drop-down list 61 displays “Please select an item” by default, but when the import destination drop-down button 62 is clicked, one or more input plug-ins (eg, , File folder, etc.) and ready-made (recommended menu). When one input system plug-in is selected from the import destination drop-down list 61, a setting dialog for the input system plug-in is displayed.
[0073]
The import destination list box 63 displays input plug-ins for which the settings in the setting dialog have been completed normally. Specifically, the import destination list box 63 displays an icon representing the input plug-in together with the name of the set input plug-in. Note that at least one input plug-in must be displayed in the import destination list box 63 before the OK button 54 is clicked.
[0074]
The import destination edit button 64 is a button for instructing setting and editing of the input plug-in selected from one or more input plug-ins displayed in the import destination list box 63. Note that a desired input system plug-in may be selected from the import destination list box 63 and double-clicked. The capture destination delete button 65 is a button for instructing deletion of a selected input plug-in from one or more input plug-ins displayed in the capture destination list box 63.
[0075]
The rule setting screen 50 includes a processing method drop-down list 71, a processing method drop-down button 72, a processing method list box 73, a processing method order change buttons 74U and 74D, a processing method edit button 75, and a processing method delete. A button 76 is provided.
[0076]
The processing method drop-down list 71 displays “Please select an item” by default, but when the processing method drop-down button 72 is clicked, one or more processing system plug-ins (eg, , Image processing, optical character recognition processing (OCR), etc.) and ready-made. When one processing system plug-in is selected from the processing method drop-down list 71, a setting dialog for the processing system plug-in is displayed.
[0077]
The processing method list box 73 displays the processing system plug-ins for which the settings in the setting dialog have been completed normally. Specifically, the processing method list box 73 displays an icon representing the processing system plug-in together with the name of the processing system plug-in that has been set.
[0078]
The processing method order change buttons 74U and 74D are buttons for changing the execution order of each processing system plug-in when a plurality of processing system plug-ins are displayed in the processing method list box 73. For example, each time the processing method order change button 74U is clicked, the order of the processing system plug-ins selected in the processing method list box 73 is increased by one. On the other hand, each time the processing method order change button 74D is clicked, the order of the processing system plug-ins selected in the processing method list box 73 is lowered by one.
[0079]
For example, in rule 1 shown in FIG. 5, the processing system plug-ins are in the order of image processing, OCR, and attribute assignment / distribution. Therefore, by clicking the processing method order change buttons 74U and 74D, for example, editing for changing the order of the image processing and the OCR becomes possible.
[0080]
The processing method edit button 75 and the processing method delete button 76 are used to edit / delete the processing system plug-in displayed in the processing method list box 73 by the same operation as the above-described import destination edit button 64 and import destination delete button 65, respectively. Instructions can be given.
[0081]
The rule setting screen 50 includes a distribution destination drop-down list 81, a distribution destination drop-down button 82, a distribution destination tree 83, a distribution destination editing button 84, and a distribution destination delete button 85 as related to the distribution destination.
[0082]
The distribution destination drop-down list 81 displays "Please select an item" by default, but when the distribution destination drop-down button 82 is clicked, one or more output plug-ins (for example, , File folder, print output, mail SMTP output, etc.) and ready-made. When one output system plug-in is selected from the distribution destination drop-down list 81, a setting dialog of the output system plug-in is displayed.
[0083]
The distribution destination tree 83 displays an icon representing the output system plug-in together with the name of the set output system plug-in. Specifically, when the setting in the setting dialogue ends normally, the distribution destination tree 83 displays a distribution condition, a distribution format, a notification condition, and a notification method of the output plug-in in a tree. FIG. 7 shows only “delivery conditions” and “sample notification” (notification method and notification condition).
[0084]
The distribution destination edit button 84 is a button for editing the distribution conditions, the distribution format, the notification method, and the contents of the notification conditions of the output plug-in displayed in the distribution destination list box 83.
[0085]
The delivery destination delete button 85 is a button for instructing to remove the selected output system plug-in from the rule. If the output plug-in has not been selected, the delivery destination deletion button 85 cannot be clicked.
[0086]
As described above, the control device 30 sets the capture destination, the processing method, and the distribution destination based on the information input via the rule setting screen 50, and performs a series of processes up to the capture, processing, and distribution of the document. Defined rules can be created. Then, the created rule is stored in the hard disk drive 36 as the rule / accumulation condition memory 205 via the RAM 32 or in an external storage medium (not shown).
[0087]
[Setting of accumulation condition]
After creating a rule as described above, the control device 30 sets an accumulation condition for the rule. In the following, as an initial value of the accumulation condition, the attachment condition is set in advance so that the original data is not attached to the history information of all the completed jobs (hereinafter, such a setting is referred to as “all unattached”). .), And a case where 1000 cases are set as the number condition is described as an example. In the case where all the jobs are not attached, the original data of all the completed jobs is deleted from the buffer 211A together with the intermediate files and the like when the job is completed, and does not remain in the system 1.
[0088]
FIG. 8 is a flowchart illustrating a procedure when the CPU 31 of the control device 30 sets the accumulation condition. 9 to 14 are diagrams illustrating examples of a condition setting screen displayed to accept a setting of a storage condition from a user.
[0089]
When the OK button 54 on the rule setting screen 50 described above is clicked, the control device 30 starts the processing in FIG.
[0090]
First, in step ST1, the CPU 31 of the control device 30 displays, for example, the condition setting screen 100 shown in FIG. 9 on the display 34, and determines whether or not the accumulation condition can be kept at the initial value.
[0091]
The condition setting screen 100 shown in FIG. 9 includes buttons 101 and 102. Button 101 is a button for setting an attachment condition to an initial value, and button 102 is a button for setting other than the initial value.
[0092]
In this example, since the initial value of the attachment condition is all non-attached, the user deletes the original data of all completed jobs, that is, the case where the original data of all completed jobs does not need to remain in the system 1. May click the button 101 to retain the original data. If it is not necessary to delete the data of all the completed jobs, click the button 102.
[0093]
When the button 101 is clicked, the CPU 31 of the control device 30 makes an affirmative decision in step ST1 of FIG. 8 and proceeds to step ST3 described below. .
[0094]
In step ST2, for example, the condition setting screens of FIGS. 10 to 13 are appropriately displayed on the display, and the setting of the conditions for attaching the original data from the user is accepted.
[0095]
The condition setting screen 110 shown in FIG. 10 is displayed when the button 102 is clicked on the condition setting screen 100 shown in FIG. 9 and includes buttons 111 and 112. A button 111 is a button for attaching the original data to save the job history, and a button 112 is a button for setting the attachment condition for saving the job history without attaching the original data to all attachments. is there.
[0096]
If the user wants to keep the original data, he or she clicks the button 111 and deletes the original data of all the completed jobs. That is, if the original data of all the completed jobs does not need to remain in the system 1, Click the button 112.
[0097]
The condition setting screen 120 shown in FIG. 11 is displayed when the button 112 is clicked in order to confirm with the user whether the attachment condition may be set to all non-attachment, and includes buttons 121 and 122. . The button 121 is a button for setting the attachment condition to all non-attachment, and the button 122 is a button for canceling the setting of all non-attachment.
[0098]
The user clicks the button 121 if he / she really wants to delete the original data of all the completed jobs, and clicks the button 122 if he wants to keep the original data.
[0099]
The condition setting screen 130 shown in FIG. 12 is displayed when the buttons 112 and 122 are clicked, and includes buttons 131 and 132. The button 131 is a button for setting, as an attachment condition, the original data to be attached to the history information of all completed jobs (hereinafter, such a setting is referred to as “all attached”). A button for setting attachment conditions other than attachment and all non-attachments.
[0100]
The user clicks the button 131 when he wants to keep the original data of all the completed jobs, and does not have to keep the original data for all the completed jobs, but clicks the button 132 when he wants to keep it.
[0101]
The condition setting screen 140 shown in FIG. 13 is displayed when the button 132 is clicked, and includes buttons 141 and 142. The button 141 is a button for setting to attach the original data to only the normal job and save the job history (hereinafter, such a setting is referred to as “normal job attachment”), and the button 142 is an error job. Is a button for setting so that the original data is attached and the job history is saved (hereinafter, such a setting is referred to as “error job attachment”).
[0102]
The user clicks the button 141 to leave the original data only for the normal job among the completed jobs, and clicks the button 142 to leave the original data only for the error job.
[0103]
The user can set desired attachment conditions (all non-attached / all attached / normal job attached / error job attached) through the condition setting screens of FIGS. When the user sets the attachment conditions, the process proceeds to the next step ST3 in FIG.
[0104]
In step ST3, for example, a condition setting screen as shown in FIG. 14 is appropriately displayed on the display, and the setting of the number condition is received from the user.
[0105]
The condition setting screen 150 shown in FIG. 14 includes an input box 151 and an OK button 152. In the input box 151, the upper limit value of the number of registrations of the history information to be registered as the job history of the rule is input. In the initial state, “1000” which is an initial value of the number condition is input in the input box 151. The OK button 152 is a button for setting the number condition to the number entered in the input box 151. The user inputs a desired number in the input box 151 and clicks an OK button 152 to set the number condition.
[0106]
In the next step ST4, accumulation is performed on the basis of the initial value when the determination is affirmative in step ST1, and the attached condition set in step ST2 when the determination is negative in step ST1 and the number condition set in step ST3. The storage condition information indicating the attached condition and the number condition is generated as a condition.
[0107]
In step ST5, the generated storage condition information is stored in the rule / storage condition memory 205 in association with the corresponding rule, and the processing in FIG. 8 ends.
[0108]
As described above, the control device 30 determines whether or not to attach the original data to the history information as a storage condition for each rule based on information input via the condition setting screens as shown in FIGS. Can be set, and an attachment condition as to whether or not to attach the attachment condition, and a number condition which is an upper limit value of the number of registrations of the history information registered as the job history can be set.
[0109]
Execute Rule
The control device 30 fetches a document from the document sharing network system 1 based on a rule stored in the hard disk drive 36 as the rule / accumulation condition memory 205 or an external storage medium, processes the document, and then performs predetermined distribution. A series of processing up to the first distribution is executed.
[0110]
FIG. 8 is a flowchart illustrating a procedure when the CPU 31 of the control device 30 executes a process according to the rule when a job for executing the rule managed to be executable is input.
[0111]
That is, first, in step ST1, the CPU 31 of the control device 30 executes a rule corresponding to the input job. Specifically, the document is imported from the input plug-in set as “import destination” in the rule, and the processing of the processing plug-in set as “processing method” is sequentially performed on the imported document, It distributes to the output plug-in set as "delivery destination" according to the distribution conditions.
[0112]
For example, in the case of Rule 4 shown in FIG. 5, if a document obtained by scanning or receiving a fax by the scanner unit 11 or the FAX unit 13 is stored in the confidential BOX 15B of a predetermined BOX number, the confidential BOX 15B , And sequentially retrieves the stored documents in page units. Then, while performing an appropriate format conversion on the captured document, automatic erecting and optical character recognition (OCR) for rotating the document (image) so that the document (image) is erect, a part of the recognized characters is obtained. Is used to create a file name, add it to the text after OCR processing, bind the document image, store it in the file folder, and print it out.
[0113]
When the job is completed, the process proceeds to step ST11, and history information about the completed job is generated. Subsequently, in the next step ST12, the storage condition information stored in association with the executed rule is referred to.
[0114]
Then, if the referred storage condition information is such that the attached condition is set to attach the original data and save the history information for the completed job, the process proceeds from the next step ST13 to step ST14. Otherwise, the process proceeds from step ST13 to step ST15.
[0115]
That is, when the attachment condition indicated by the accumulation condition information referred to in step ST12 is all attached, the process proceeds to step ST14, and when the attached condition is not all attached, the process proceeds to step ST15. When the attachment condition is a normal job attachment, if the completed job is a normal job, the process proceeds to step ST14. If the completed job is an error job, the process proceeds to step ST15. If the attachment condition is an error job attachment, the process proceeds to step ST14 if the completed job is an error job, and proceeds to step ST15 if the completed job is a normal job.
[0116]
In step ST14, the original data is read from the buffer 211A, and the read original data is attached to the history information generated in step ST11 and registered in the history memory 213 as a job history. In step ST15, only the history information generated in step ST11 is registered in the history memory 213 as a job history. Although not shown, when steps ST14 and ST15 are performed, all data relating to the job including the original data is deleted from the buffer 211A.
[0117]
If the number of registered job histories exceeds the upper limit of the number of registered items indicated by the number condition of the accumulation condition information referred to in step ST12 by the registration of the job history in step ST14 or step ST15, the next step The process proceeds from ST16 to step ST17, where the oldest history information is deleted from the job history, and the processing in FIG. 15 ends. On the other hand, if the number of registered jobs in the job history is equal to or smaller than the upper limit of the number of registered jobs indicated by the number condition, the process in FIG.
[0118]
As described above, the control device 30 sets via the condition setting screen such as the attachment condition of whether or not to attach the original data for each rule and the number condition indicating the upper limit of the registration number of the history information registered as the job history. Job history information can be flexibly managed based on the stored accumulation conditions, such as attaching original data to the history information and registering the same in the job history, or limiting the number of registered job histories.
[0119]
As a result, only original rules can be attached to the job history, and the original data can be stored even after the job is completed. Other rules that do not require original data or highly confidential original data are used. As for the rules, the original data is deleted after the job is completed, so that the memory resources such as the hard disk drive 36 can be effectively used and the security can be improved.
[0120]
Also, since the upper limit of the number of registered job histories is variable, even if original data is stored, it can be adapted to the environment of each user such as the memory capacity of the hard disk drive 36 as the history memory 213. Even if the original data is not stored, the history information is stored. Therefore, the variable upper limit of the number of registered jobs in the job history can be set to a number suitable for the past log investigation for each user. There is also an effect.
[0121]
In the above description, the accumulation condition is set for each rule. However, the present invention is not limited to this. In addition, according to the type of job, the type of plug-in, the type of device, etc. , Storage conditions can be set.
[0122]
For example, a condition setting screen as shown in FIG. 16 may be displayed on the display 34, and an attachment condition as to whether or not to attach the original data to the job history may be set as the accumulation condition.
[0123]
More specifically, the condition setting screen 160 shown in FIG. 16 includes radio buttons 161A to 161E, radio buttons 162A and 162B, check buttons 163A to 163C, check buttons 164A to 164C, and an OK button 165.
[0124]
The radio button 161A is a button for setting the attachment condition to all non-attachment. The radio button 161B is a button for setting the attachment condition to all attachments. The radio button 161C is a button for setting the attachment condition according to the type of the job. The radio button 161D is a button for setting the attachment condition according to the type of plug-in. The radio button 161E is a button for setting the attachment condition according to the device.
[0125]
Of these radio buttons 161A to 161E, only one of them is always selected. That is, when any radio button is clicked, only the clicked radio button becomes selected and all other radio buttons are selected. The radio button is in a non-selected state.
[0126]
The check button 162A is a button for setting the attachment condition to normal job attachment. The check button 162B is a button for setting the attachment condition to error job attachment.
[0127]
The check buttons 162A and 162B can be selected when the radio button 161C is in the selected state, and only one of them is always in the selected state while the radio button 161C is available.
[0128]
The check buttons 163A to 163C are buttons provided one for each plug-in that is a component of the rule. FIG. 16 shows a case where the functions of three plug-ins are realized in the system 1. The check buttons 163A to 163C can be selected when the radio button 161D is in a selected state. When the check buttons 163A to 163C are selectable, each check button is clicked to switch the selection ON / OFF. However, they can be simultaneously selected.
[0129]
Each of the check buttons 163A to 163C is a button for setting, for a completed job processed through the corresponding plug-in, original data to be attached to the job history. That is, by turning ON / OFF the selection of the check buttons 163A to 163C, it is possible to set so that the original data is attached to the job history related to the process using the specific plug-in.
[0130]
The check buttons 164A to 164C are buttons provided one by one for each device constituting the system 1. In FIG. 16, the system 1 is composed of three devices (two multifunction devices and a control device). Is shown. The check buttons 164A to 164C can be selected when the radio button 161E is in a selected state. During the selectable state, each check button is clicked to switch the selection between ON and OFF, and even one check button is provided. However, they can be simultaneously selected.
[0131]
Each of the check buttons 164A to 164C is a button for setting so that the original data is attached to the job history for the completed job processed by the corresponding device. That is, by turning ON / OFF the selection of the check buttons 164A to 164C, it is possible to set so that the original data is attached to the job history related to the process using the specific device.
[0132]
The OK button 165 is a button for setting an attachment condition based on the selection state of the above radio buttons or check buttons. The user selects the above radio button or check button so that the desired attachment condition is obtained, and clicks an OK button 165 to set the attachment condition.
[0133]
By accepting the setting of the accumulation condition (attachment condition) from the user via the condition setting screen 160, the control device 30 determines whether or not to attach the original data uniformly to all the completed jobs as the accumulation condition. Whether or not to attach original data can be set for each job type, each plug-in type, and each device type. If the condition setting screen 160 is used to set the initial value of the accumulation condition, the initial value of the accumulation condition can be arbitrarily changed.
[0134]
Alternatively, the storage condition may be set for each job. For example, when a job is input, a condition setting screen as shown in FIG. 17 is displayed on the display 34 or a display means (for example, the display panel 16) of the apparatus to which the job is input, and the job history is stored as a storage condition. Attachment conditions for whether or not to attach the original data may be set.
[0135]
More specifically, the condition setting screen 170 shown in FIG. 17 includes buttons 171 and 172. The button 171 is a button for setting the original data to be attached to the job history when the input job is completed. The button 172 is a button for registering a job history without attaching original data when an input job is completed.
[0136]
By accepting the setting of the storage condition (attachment condition) from the user via the condition setting screen 170 at the time of job input, it is possible to set whether or not to attach the original data for each job. Further, when the condition setting screen is displayed on a display unit provided in a device other than the control device 30 such as the display panel 16 and the setting of the storage condition is received from the user, the control device 30 naturally communicates with the other devices by communication. It goes without saying that the user receives the setting result of the storage condition (attachment condition) from the device and registers the job history based on the received storage condition.
[0137]
FIGS. 16 and 17 show the case where the attachment condition is set as the accumulation condition. However, although not shown, the number of conditions condition is not limited to each rule, but also the job type, plug-in type, It may be set for each device type and job.
[0138]
Further, the accumulation condition may be set according to a plurality of rules, a job type, a plug-in type, a device type, and a job.
[0139]
Further, in the above description, when the original data is left (stored), the original data is attached to the history information and registered in the history memory 213, but the present invention is not limited to this. For example, a backup folder may be provided on the hard disk drive 36 or an external recording medium (not shown), and the history information may be stored separately from the history memory 213, and the original data may be stored separately from the backup folder. In this case, the link information to the original data stored in the backup folder is added to the history information and registered in the history memory 213.
[0140]
Further, in the above description, the control device 30 is provided on the network 5, and a service for performing a series of processes from document capture to processing and distribution is controlled on the network 5 by the control of the control device 30 in accordance with a predetermined rule as a workflow. Although the document sharing network system 1 that is processed in cooperation is described as an example in which the present invention is applied as a data processing system, the present invention is not limited to this. The data processing system to which the present invention is applied may be in any form as long as a series of processes can be continuously executed according to a workflow.
[0141]
【The invention's effect】
As described above, the present invention has an excellent effect that it is possible to flexibly manage job history information when a series of predefined processes are performed in cooperation with each other on a network.
[Brief description of the drawings]
FIG. 1 is a schematic diagram of a document sharing network system according to an embodiment of the present invention.
FIG. 2 is a diagram illustrating an outline of processing of a document sharing network system.
FIG. 3 is a block diagram illustrating a configuration of the multifunction peripheral.
FIG. 4 is a block diagram illustrating a configuration of a control device.
FIG. 5 is a diagram illustrating an example of a rule that can be generated by arbitrarily combining an input plug-in, a processing plug-in, and an output plug-in.
FIG. 6 is a block diagram illustrating a functional configuration of a control device.
FIG. 7 is a diagram illustrating an example of a rule setting screen.
FIG. 8 is a flowchart illustrating a procedure for setting an accumulation condition in a rule created by a CPU of a control device.
FIG. 9 is a diagram showing an example of a condition setting screen.
FIG. 10 is a diagram showing an example of a condition setting screen.
FIG. 11 is a diagram showing an example of a condition setting screen.
FIG. 12 is a diagram showing an example of a condition setting screen.
FIG. 13 is a diagram showing an example of a condition setting screen.
FIG. 14 is a diagram showing an example of a condition setting screen.
FIG. 15 is a flowchart illustrating a procedure when the CPU of the control device executes a process according to a rule.
FIG. 16 is a diagram showing another example of the condition setting screen.
FIG. 17 is a diagram showing another example of the condition setting screen.
[Explanation of symbols]
1 Document sharing network system
5 Network
10 MFP
15 Memory
25 Terminal device
30 Control device
31 CPU
36 Hard Disk Drive
50 Rule setting screen
100, 110, 120, 130, 140, 150, 160, 170 Condition setting screen
200 Core Services Department
201 Rule Creation and Management Department
202 Rule Check Section
203 Plug-in status check unit
204 Accumulation condition creation unit
205 Rule / accumulation condition memory
210 Application Service Department
211 Rule execution unit
212 History registration management unit
213 History memory

Claims (6)

The setting of the destination of the document data, the method of processing the captured document data, and the distribution destination of the processed document data is received, and a series of the capturing, processing, and distribution of the document data is performed based on the received setting result. Storage means for storing rules defining the processing of
Executing means for executing the series of processes in cooperation with each other on a network according to the rules,
Accumulation means for accumulating job history information as a history of executing the series of processes according to the rule by the execution means,
Setting means for setting storage conditions including a condition as to whether or not to store the document data by adding the document data to the job history information;
Management means for managing the accumulation of the job history information in the accumulation means based on the accumulation condition set by the setting means;
Data processing system equipped with. The accumulation condition further includes an accumulation upper limit number of the job history information.
The data processing system according to claim 1, wherein: The setting means, for each of the rules, a job type distinguished by a normal job in which the series of processing has been completed normally and an error job in which an error has occurred in the series of processing, a type of a device on the network, Setting the accumulation condition according to at least one of the capture destination, the processing method, and the type of the distribution destination, which are constituent elements of a rule, and at least one for each job;
The data processing system according to claim 1 or 2, wherein: On the computer,
The setting of the destination of the document data, the method of processing the captured document data, and the distribution destination of the processed document data is received, and a series of the capturing, processing, and distribution of the document data is performed based on the received setting result. A data processing program that controls the series of processes to be executed in cooperation with each other on a network according to a rule that defines the process, and accumulates job history information as a history of execution of the series of processes according to the rule. So,
To the computer,
Setting a storage condition including at least a condition of whether or not to store the document data by adding the document data to the job history information;
A data processing program for managing storage of the job history information in the storage unit based on the set storage condition. To the computer,
Setting the storage condition further including a registration upper limit number of the job history information;
The data processing program according to claim 4, wherein: To the computer,
For each of the rules, the type of job, the type of device on the network, the type of device on the network, the components of the rule, The storage condition is set according to at least one of the capture destination, the processing method, the type of the distribution destination, and at least one of the jobs.
The data processing program according to claim 4 or 5, wherein

Images