JP5454663B2 - Information processing system, control method and program thereof, and management server, control method and program thereof - Google Patents

Description

The present invention relates to a scan instruction is available mechanism to the image processing apparatus, especially a scanning data read by the image processing apparatus, of the replaced from the image processing apparatus capable of information processing system, a control method, and a program, The present invention also relates to a management server, a control method thereof, and a program.

  2. Description of the Related Art Conventionally, there are many business workflow systems that apply for transportation expenses when traveling or going out. In general, when using train or bus transportation, the accounting process is done only by applying on the workflow system. However, when using certain transportation such as taxis or bullet trains, the receipt Submission is required. In a conventional business workflow system, in the case of a travel expense application that requires receipt, a receipt is pasted on a mount and pasted on the mount as well as an application on the business workflow.

  On the other hand, in many companies, an opportunity to digitize by scanning a paper document with an image processing apparatus is increasing. In addition, image processing apparatuses have become more sophisticated, and various reading settings can be made when digitizing. Information about where to read the read image can also be set. Accordingly, receipts, application forms, and the like attached to the above-described business workflow system are scanned by an image processing apparatus, and the generated scan data is attached at the time of application to request approval.

  However, since each user can perform scan settings in the image processing apparatus, the scan data may not be digitized as intended by the approver. In recent years, the scanning function has been enhanced, and the number of setting items has increased, making computerization complicated and error prone.

  In order to solve such a problem, for example, in Patent Document 1 below, an image reading attribute and a transfer destination of a read image are registered in the server in advance as a job template, and the user reads an image with the image processing apparatus. A mechanism has been disclosed that makes it easy to read an image by using the job template.

  Also, in Patent Document 2 below, when scan data is required for a workflow application, a scan ticket in which the instruction content for executing image reading is defined is generated, and the scan ticket is used. A mechanism that can be scanned and attached to a workflow application is disclosed.

JP 2000-270148 A JP 2011-124962 A

  Conventionally, paper documents that need to be attached to the business workflow system can be scanned and attached to the application in this way. However, in actual business, the receipt is wrong and needs to be replaced. Insufficient numbers may need to be added, or workflows once applied may be withdrawn.

  In such a case, an operation is performed in which the client terminal is used to log in to the business workflow system, cancel the applied workflow once, and scan again using the scan ticket from the multifunction peripheral. Therefore, since the applicant needs to input the application contents again from the client terminal and apply, and scan the paper document from the image processing apparatus, the burden of rework is very large.

The present invention has been made in view of the above problems, and an object of the present invention is to provide a mechanism capable of appropriately replacing scan data stored using a scan ticket from an image processing apparatus. .

To achieve the above object, an information processing system of the present invention, a management server, an information processing system including a scannable image processing apparatus paper document, the management server, the scan settings defined a scan ticket is data storage means for memorize a Ru generated scan data by scanning a paper document in the image processing apparatus, the stored scan ticket in the storage unit to the image processing apparatus a scan ticket transmitting unit for transmitting a scan data receiver that will receive the scan data generated using the transmitted scan ticket in the scan ticket transmitting unit from the image processing apparatus, with the scan data receiving means the received scan data and a scan data storage means for storing in said storage means, said image Processor, scan data to generate scan data by scanning a paper document using the scan ticket receiving means for receiving a scan ticket transmitted, the scan ticket received by the scan ticket receiving means from said management server comprising a generation unit, and a scan data transmission means for transmitting the scan data generated by the scan data generation means to the management server, the scan data generation means is defined in the scan ticket used in the scan data generating means Based on the scan setting, the scan data storage unit generates scan data to be replaced with the scan data stored in the storage unit, and the scan data storage unit includes the scan data stored in the storage unit and Scan to replace When receiving the data, set the scan data the received, characterized in that stored replacing the scanned data stored in the storage means.

According to the present invention, since the scan data can be replaced based on the settings defined in the used scan ticket , the user's business efficiency can be improved.

It is a lineblock diagram showing an example of information processing system 100 in an embodiment of the present invention. FIG. 2 is a configuration diagram illustrating an example of a hardware configuration of a client terminal 101 and a scan ticket server 102 illustrated in FIG. 1. FIG. 2 is a configuration diagram illustrating an example of a hardware configuration of a multifunction machine 103 illustrated in FIG. 1. FIG. 2 is a configuration diagram illustrating an example of a module configuration of a client terminal 101, a scan ticket server 102, and a multifunction machine 103 illustrated in FIG. It is a flowchart which shows the flow of the process of the application in embodiment of this invention. It is a flowchart which shows the flow of the process of the scan ticket application in embodiment of this invention. It is a flowchart which shows the flow of the process of approval in embodiment of this invention. It is a flowchart which shows the flow of the process of the historical ticket application in embodiment of this invention. It is a flowchart which shows the flow of the unapproved process in step S410 of FIG. It is a flowchart which shows the flow of the process during approval in step S411 of FIG. It is a flowchart which shows the flow of the denial process in step S412 of FIG. It is a block diagram which shows an example of a structure of the scan ticket table 1200 and the log | history ticket table 1210 in a present Example. It is a block diagram which shows an example of a structure of the application information table 1300 and workflow table 1310 in a present Example. It is a block diagram which shows an example of a structure of the application screen 1400 in a present Example. It is a block diagram which shows an example of a structure of the scan ticket selection screen 1500 in a present Example. It is a block diagram which shows an example of a structure of the historical ticket selection screen 1600 in a present Example. It is a block diagram which shows an example of a structure of the unapproved menu screen 1700 in a present Example. It is a block diagram which shows an example of a structure of the menu screen 1800 in approval in a present Example. It is a block diagram which shows an example of a structure of the rejection menu screen 1900 in a present Example. It is a flowchart which shows the flow of a process of the scan ticket application in the 2nd Embodiment of this invention. It is a flowchart which shows the flow of the process of the historical ticket application in the 2nd Embodiment of this invention. It is a flowchart which shows the flow of the unapproved process in step S410 of FIG. It is a flowchart which shows the flow of the process during approval in step S411 of FIG. It is a flowchart which shows the flow of the denial process in step S412 of FIG. It is a block diagram which shows an example of the structure of the scan ticket table 1200 in 2nd Embodiment.

  Hereinafter, an example of an embodiment of the present invention will be described with reference to the drawings.

  FIG. 1 is a diagram illustrating an example of a system configuration of an information processing system 100 according to the present invention. An information processing system 100 according to the present invention includes a client terminal 101, a scan ticket server 102, and a multifunction peripheral 103 (image processing apparatus). These apparatuses are connected to each other via a network 104 such as wireless communication so that data communication can be performed. ing. The configuration of various terminals connected to the network 104 in FIG. 1 is an example, and it goes without saying that there are various configuration examples depending on the application and purpose.

  The client terminal 101 is an apparatus for connecting to the scan ticket server 102 and approving and applying various workflows. In the present embodiment, the client terminal 101 is described on the assumption of a PC (Personal Computer), but it may be a device such as a smartphone or a tablet terminal, or another device.

  The scan ticket server 102 (scan management server) issues a scan ticket for scanning a paper document to be attached in response to a workflow approval request from the client terminal 101, and requests the scan ticket from the multifunction device 103. Send according to. When the scan data generated using the scan ticket is received from the multifunction device 103, a history ticket that can change the scan data is issued, and the history ticket is transmitted in response to a request from the multifunction device 103. . Further, the scan ticket server 102 also manages a workflow for applying for approval. When scan data is transmitted using a scan ticket in the MFP 103, the workflow is operated to request approval from a predetermined user. In this embodiment, the scan ticket server 102 is described as performing both management of scan tickets and history tickets, and workflow for approval applications. However, the scan ticket server 102 may be operated on different devices.

  The multi-function peripheral 103 receives scan tickets and history tickets from the scan ticket server 102, scans a paper document based on the scan settings set in these tickets, and transmits them to the scan ticket server 102. The multifunction machine 103 has a function as an MFP (Multifunction Printer) such as printing and scanning.

  FIG. 2 is a diagram showing a hardware configuration of the client terminal 101 and the scan ticket server 102 in the embodiment of the present invention.

  The CPU 201 comprehensively controls each device and controller connected to the system bus 204.

  Further, the ROM 202 or the external memory 211 is necessary to realize a BIOS (Basic Input / Output System), an operating system program (hereinafter referred to as OS), which is a control program of the CPU 201, and a function executed by each server or each PC. Various programs to be described later are stored. The RAM 203 functions as a main memory, work area, and the like for the CPU 201.

  The CPU 201 implements various operations by loading a program necessary for execution of processing into the RAM 203 and executing the program.

  An input controller (input C) 205 controls input from a pointing device such as a keyboard 209 or a mouse (not shown).

  A video controller (VC) 206 controls display on a display device such as a CRT display (CRT) 210. The display device may be a liquid crystal display as well as a CRT. These are used by the administrator as needed.

  A memory controller (MC) 207 is a hard disk (HD), floppy disk (registered trademark FD) or PCMCIA card slot for storing boot programs, browser software, various applications, font data, user files, editing files, various data, and the like. Controls access to an external memory 211 such as a card-type memory connected via an adapter.

  A communication I / F controller (communication I / FC) 208 is connected to and communicates with an external device via a network, and executes communication control processing in the network. For example, Internet communication using TCP / IP is possible.

  For example, the CPU 201 can perform display on the CRT 210 by executing outline font rasterization processing on a display information area in the RAM 203. In addition, the CPU 201 enables a user instruction with a mouse cursor (not shown) on the CRT 210.

  Various programs and the like used for executing various processes described later by the respective apparatuses of the present invention are recorded in the external memory 211, and are executed by the CPU 201 by being loaded into the RAM 203 as necessary. Furthermore, definition files and various information tables used by the program according to the present invention are stored in the external memory 211.

  Next, an example of a hardware configuration of the multifunction machine 103 will be described with reference to FIG.

  The controller unit 316 is connected to a scanner unit 314 functioning as an image input device and a printer unit 312 functioning as an image output device, and is connected to a LAN or WAN (Wide Area Network) to thereby store image data and device information. Perform input / output.

  The CPU 301 is a processor that controls the entire system. A RAM 302 is a system work memory for the operation of the CPU 301, and is a program memory for recording a program and an image memory for temporarily recording image data.

  The ROM 303 stores a system boot program and various control programs. A hard disk drive (HDD) 304 stores various programs for controlling the system, image data, and the like.

  An operation unit interface (operation unit I / F) 307 is an interface unit with the operation unit 308, and outputs image data to be displayed on the operation unit 308 to the operation unit 308. The operation unit I / F 307 serves to transmit information (for example, user information) input by the system user from the operation unit 308 to the CPU 301. Note that the operation unit 308 includes a display unit having a touch panel, and various instructions can be given by a user pressing (touching with a finger or the like) a button displayed on the display unit.

  A network interface (Network I / F) 305 is connected to a network (LAN) and inputs / outputs data. A modem (MODEM) 306 is connected to a public line and inputs / outputs data such as FAX transmission / reception.

  An external interface (external I / F) 318 is an USB (Universal Serial Bus), IEEE 1394 (Institut of Electrical and Electronic Engineers 1394), a printer port, an RS-232C (Recommended Standard 232) A card reader 319 for reading an IC card, which is an F section and is necessary for authentication in this embodiment, is connected to the external I / F 318.

  Further, the CPU 301 can control reading of information from the IC card by the card reader 319 via the external I / F 318, and can acquire information read from the IC card. The above devices are arranged on the system bus 309.

  An image bus interface (IMAGE BUS I / F) 320 is a bus bridge that connects the system bus 309 and an image bus 315 that transfers image data at high speed and converts a data structure.

  The image bus 315 is configured by a PCI bus (Peripheral Components Interconnect bus) or IEEE1394. The following devices are arranged on the image bus 315.

  A raster image processor (RIP) 310 develops vector data into a bitmap image.

  A printer interface (printer I / F) 311 connects the printer unit 312 and the controller unit 316, and performs synchronous / asynchronous conversion of image data.

  A scanner interface (scanner I / F) 313 connects the scanner unit 314 and the controller unit 316, and performs synchronous / asynchronous conversion of image data.

  The image processing unit 317 performs correction, processing and editing on input image data, printer correction, resolution conversion, and the like on print output image data. In addition to this, the image processing unit 317 also rotates the image data, JPEG (Joint Photographic Experts Group) for multi-valued image data, and JBIG (Joint Bi-level Image Experts Group) for binary image data. And so on.

  The scanner unit 314 illuminates an image on paper as a document and scans it with a CCD line sensor, thereby converting it into an electrical signal as raster image data. The original paper is set on the tray of the original feeder, and when the apparatus user gives a reading start instruction from the operation unit 308, the CPU 301 gives an instruction to the scanner unit 314, and the feeder feeds the original paper one by one to read the original image. Perform the action.

  The printer unit 312 is a part that converts raster image data into an image on paper. The method is an electrophotographic method using a photosensitive drum or a photosensitive belt, and ink is ejected from a micro nozzle array directly on the paper. There is an inkjet method for printing an image, but any method may be used. The activation of the printing operation is started by an instruction from the CPU 301. The printer unit 312 has a plurality of paper feed stages so that different paper sizes or different paper orientations can be selected, and includes paper cassettes corresponding to the paper feed stages.

  The operation unit 308 has an LCD (Liquid Crystal Display) display unit, and a touch panel sheet is pasted on the LCD, displays a system operation screen, and displays position information when a displayed key is pressed. This is transmitted to the CPU 301 via the operation unit I / F 307. The operation unit 308 includes, for example, a start key, a stop key, an ID key, a reset key, and the like as various operation keys.

  Here, the start key of the operation unit 308 is used when starting a document image reading operation. At the center of the start key, there are two color LEDs, green and red, which indicate whether or not the start key can be used. Further, the stop key of the operation unit 308 functions to stop the operation in operation. The ID key of the operation unit 308 is used when inputting the user ID of the user. The reset key is used when initializing settings from the operation unit.

  With the configuration described above, the multi-function peripheral 103 transmits image data read from the scanner unit 314 to the LAN from the network I / F 305, and print data received from the LAN from the printer unit 312 via the network I / F 305. Can be printed out.

  Further, the image data read from the scanner unit 314 can be faxed to the public line by the modem 306, and the image data received by fax from the public line can be output by the printer unit 312.

  Next, a functional configuration diagram showing module configurations of the client terminal 101, the scan ticket server 102, and the multifunction machine 103 will be described with reference to FIG. It should be noted that the module configurations of the various apparatuses in FIG. 4 are merely examples, and it goes without saying that there are various configuration examples depending on the application and purpose.

  The client terminal 101 includes a screen display module 401, a transmission / reception module 402, an application module 403, and an approval module 404.

  The screen display module 401 is a module for acquiring various data and tables and displaying them on the CRT 210. In addition, instruction contents and input contents instructed by the user are also acquired on the displayed screen. The transmission / reception module 402 is a module for transmitting / receiving data to / from various devices including the scan ticket server 102 and the multifunction machine 103. The application module 403 is a module that makes various applications for the business workflow managed by the scan ticket server 102. The approval module 404 is a module for approving or rejecting the application executed by the application module 403. Information received by the application module 403 and the approval module 404 is transmitted to the scan ticket server 102 by the transmission / reception module 402.

  The scan ticket server 102 includes a storage module 411, a transmission / reception module 412, a scan ticket management module 413, a history ticket management module 414, and a workflow management module 415.

  The storage module 411 is a module for storing various data and tables (storage means). In this embodiment, a scan ticket table 1200 (see FIG. 12), a history ticket table 1210 (see FIG. 12), an application information table 1300 (see FIG. 13), and a workflow table 1310 (see FIG. 13), which will be described later, are stored. The transmission / reception module 412 is a module for transmitting / receiving data to / from various devices including the client terminal 101 and the multifunction peripheral 103. The scan ticket management module 413 is a module for managing a scan ticket that is generated with an application for a business workflow and in which scan settings are defined. Manages creation, deletion, and storage of scan tickets. The history ticket management module 414 is a module for managing a history ticket generated by using a scan ticket. Manage the creation, deletion, and storage of history tickets. The workflow management module 415 manages an application for approval in the business workflow. Approval is requested from each approver based on the application contents applied from the client terminal 101. It also receives approval or denial instructions from the client terminal 101 and manages the approval status.

  The multifunction machine 103 includes a screen display module 421, a transmission / reception module 422, and a scan module 423.

  The screen display module 421 is a module for acquiring various data and tables and displaying them on the CRT 210. In addition, instruction contents and input contents instructed by the user are also acquired on the displayed screen. The transmission / reception module 422 is a module for transmitting / receiving data to / from various devices including the client terminal 101 and the scan ticket server 102. The scan module 423 is a module for scanning a paper document and generating scan data. At the time of scanning, the scan setting is changed based on the scan ticket or history ticket received from the scan ticket server 102. The generated scan data is transmitted to the scan ticket server 102 by the transmission / reception module 422.

  Next, processing related to a workflow approval application performed by the information processing system 100 according to the embodiment of the present invention will be described with reference to the flowchart shown in FIG. This flowchart is a process for connecting to the scan ticket server 102 from the client terminal 101 and making a workflow application. Note that steps S101 and S104 to S108 are performed under the control of the CPU 201 in the client terminal 101. In addition, the steps S102, S103, and S109 to S112 are performed under the control of the CPU 201 in the scan ticket server 102.

  First, in step S101, the client terminal 101 requests the scan ticket server 102 for an application screen 1400 (see FIG. 14) in order to apply for a workflow. In step S102, the scan ticket server 102 receives an application screen acquisition request from the client terminal 101. In step S103, the scan ticket server 102 acquires the application screen 1400 and transmits it to the client terminal 101.

  In step S104, the client terminal 101 receives the application screen 1400 from the scan ticket server 102. In step S105, the client terminal 101 displays the received application screen 1400 on the CRT 210. The application screen 1400 accepts input of various information in order to make an application that requires approval. An application screen 1400 shown in FIG. 14 is a screen for applying for transportation expenses.

  In step S <b> 106, the client terminal 101 receives input for each input item on the application screen 1400. In step S107, it is determined whether or not the input button 1401 provided on the application screen 1400 has been pressed after completion of the input. If it is determined that the application button 1401 has been pressed, the process proceeds to step S108; otherwise, the process waits until the application button 1401 is pressed.

  In step S <b> 108, the client terminal 101 transmits various information received in step S <b> 106 to the scan ticket server 102 as application information. In step S <b> 109, the scan ticket server 102 receives the application information transmitted from the client terminal 101.

  In step S110, based on the application information received in step S109, the scan ticket server 102 generates a scan ticket in which the scan setting of the scan data to be attached with the application is defined, and the scan ticket table 1200 (FIG. 12). (Scan ticket generation means). The scan ticket includes items as shown in the scan ticket table 1200 of FIG. The scan ticket defines the reading settings at the time of scanning, the storage destination of the scan data, and the like, and the multi-function peripheral 103 can change the settings of the multi-function peripheral 103 based on these settings and execute the scan. For example, when scanning a receipt required for transportation expenses application, it is defined that the scanning ticket for transportation expenses application is scanned with file format “PDF”, resolution “300 dpi”, “monochrome, single-sided”. If a transportation fee application is made, this scan ticket is automatically issued. If an attached file is required every time an application is made, a fixed scan ticket can be issued and the user can be requested to scan with a predetermined scan setting, thereby saving the user's trouble.

  The scan ticket table 1200 (see FIG. 12) includes a scan ticket ID 1201 (identification information), an owner 1202, a generation date and time 1203, a file format 1204, a resolution 1205, a reading setting 1206, a page number 1207, and a storage destination 1208. The scan ticket ID 1201 is an identification number assigned to each generated scan ticket. The owner 1202 indicates the user name of the user who uses the scan ticket. The generation date and time 1203 is information indicating the date and time when the scan ticket is generated. The file format 1204, the resolution 1205, the reading setting 1206, and the number of pages 1207 are information indicating scan settings in the MFP 103, respectively. A storage destination 1208 is information indicating a storage destination of scan data scanned by the multifunction machine 103.

  In step S111, the scan ticket server 102 associates the application information received in step S109 with the scan ticket generated in step S110. In step S112, the scan ticket server 102 registers the application information in the application information table 1300 (see FIG. 13). To do. Since the workflow is registered in the application information table 1300 and operates only when the scan data is received, the workflow is not yet applied at this time. That is, “0” indicating unapplied is stored in the approval status flag 1306 of the application information table 1300.

  The application information table 1300 (see FIG. 13) includes an application ID 1301, a ticket ID 1302, an applicant 1303, a processing date 1304, a workflow ID 1305, an approval status flag 1306, an application content 1307, a denial reason 1308, and scan data 1309. The application ID 1301 is an identification number assigned for each piece of application information. The ticket ID 1302 stores a scan ticket or a scan ticket ID 1201 or a history ticket ID 1211 of a history ticket described later. That is, it is information that associates which scan ticket the application information uses. The applicant 1303 is information indicating the name of the user who made the approval application. The processing date and time 1304 is information indicating the date and time when the application information is updated. The workflow ID 1305 stores a workflow ID 1311 of a workflow table 1310 (see FIG. 13) described later. In order to identify the type of the application and the approver, it is associated with the workflow table 1310. The approval status flag 1306 is a flag indicating the approval status of the workflow. In this embodiment, “0” indicates unapplied, “1” indicates unapproved, “2” indicates approval, and “3” indicates denial. The type of flag is not limited to this. The application content 1307 stores the application content input by the user in step S105. The rejection reason 1308 stores a comment input by the approver who rejected the application when the application is rejected. The scan data 1309 stores scan data scanned using a scan ticket to make the application. The file path to the directory where the scan data is stored may be stored, or the scan data itself may be stored.

  In this way, by accepting an application from the user, a scan ticket corresponding to the application is issued and stored. In this embodiment, the scan ticket is issued in response to the application. However, a reusable scan ticket may be prepared for each application in advance.

  Next, processing related to scan ticket use performed by the information processing system 100 according to the embodiment of the present invention will be described with reference to the flowchart shown in FIG. In this flowchart, the MFP 103 receives a scan ticket from the scan ticket server 102, changes the scan setting of the MFP 103 based on the scan ticket, and executes a scan. Note that the steps S203, S204, S210, S211, and S216 to S220 are performed under the control of the CPU 201 in the scan ticket server 102. The steps S201, S202, S205 to S209, and S212 to S215 are processed under the control of the CPU 301 in the multifunction machine 103.

  First, in step S201, the multi-function peripheral 103 logs in according to an instruction from the user. The login may be anything as long as the user who uses the MFP 103 can be specified.

  In step S202, the multi-function peripheral 103 requests a scan ticket list from the scan ticket server 102 in order to obtain a list of scan tickets possessed by the user who has logged in in step S201. In step S 203, the scan ticket server 102 acquires the scan ticket of the user who has logged in in step S 201 from the scan ticket table 1200 in response to the scan ticket list acquisition request from the multifunction device 103. For example, when the logged-in user is “Kaneshiro”, records in which “Kaneshiro” is stored in the owner 1202 in the scan ticket table 1200 shown in FIG. To get. Here, since it is only necessary to obtain a list of scan tickets, only information necessary for screen display in step S206 described later is obtained. In this embodiment, the scan ticket list is acquired in this way, but a scan ticket (a record in the scan ticket table 1200) may be acquired in this step.

  In step S <b> 204, the scan ticket server 102 transmits the scan ticket list acquired in step S <b> 203 to the multi-function peripheral 103. In step S205, the MFP 103 receives the scan ticket list transmitted from the scan ticket server 102, and in step S206, displays the received scan ticket list on the scan ticket selection screen 1500 (see FIG. 15).

  In step S207, the multi-function peripheral 103 accepts a scan ticket selection. In step S208, the multi-function peripheral 103 determines whether a scan instruction has been issued to perform scanning based on the scan ticket received in step S207. Specifically, it is determined whether or not the scan start button 1501 is pressed in a state where the scan ticket is selected by the user. If it is determined that the scan start button 1501 has been pressed, the process proceeds to step S209. If not, the process waits until the scan start button 1501 is pressed.

  In step S209, the multi-function peripheral 103 transmits a scan ticket acquisition request to the scan ticket server 102 in order to acquire the selected scan ticket. In step S <b> 210, the scan ticket server 102 acquires the scan ticket selected by the user in step S <b> 207 from the scan ticket table 1200 in response to the scan ticket acquisition request transmitted from the MFP 103. Specifically, the scan ticket ID 1201 of the scan ticket selected from the MFP 103 may be transmitted, and the scan ticket that matches the scan ticket ID 1201 transmitted by the scan ticket server 102 may be extracted from the scan ticket table 1200.

  In step S211, the scan ticket server 102 transmits the scan ticket acquired in step S210 to the multi-function peripheral 103 (identification information transmitting unit). In step S212, the multifunction device 103 receives the scan ticket transmitted from the scan ticket server 102 (identification information receiving unit). In step S213, the scan setting of the multifunction device 103 is changed based on the received scan ticket. . In step S214, the multi-function peripheral 103 executes a scan with the scan setting changed in step S213 in accordance with an instruction from the user.

  In step S215, the multi-function peripheral 103 transmits the scan data scanned in step S214 and the scan ticket ID 1201 of the scan ticket used for the scan to the scan ticket server 102 (scan data transmitting unit). In step S216, the scan ticket server 102 receives the scan data and the scan ticket ID 1201 transmitted from the multifunction machine 103. In step S217, the scan ticket server 102 specifies application information based on the received scan ticket ID 1201. That is, it identifies which application should be associated with the received scan data.

  In step S218, the scan ticket server 102 stores the scan data received in step S216 in the scan data 1309 of the application information specified in step S217 (scan data registration unit). In this way, the application information is associated with the scan data. When the association is completed, the approval status flag 1306 of the application information is changed to “1” indicating unapproved, and the workflow is executed.

  In step S219, the scan ticket server 102 updates the scan data stored in step S218 based on the application information specified in step S217 or the scan ticket specified from the scan ticket ID 1201 received in step S216. A history ticket is issued and stored in the history ticket table 1210 (see FIG. 12) (history ticket generating means). The history ticket is a scan ticket transmitted in response to a request from the multi-function peripheral 103, and the scan data transmitted to the scan ticket server 102 can be updated. When the history ticket is generated, the history ticket ID 1211 of the history ticket table 1210 is stored in the ticket ID 1302 of the application information specified in step S217 and updated. In this way, the history ticket is associated with the application information.

  The history ticket table 1210 (see FIG. 12) has almost the same configuration as the scan ticket table 1200. The history ticket ID 1211 is an identification number assigned to each history ticket. Since the owner 1212, generation date / time 1213, file format 1214, resolution 1215, read setting 1216, page number 1217, and storage destination 1218 are the same as those in the scan ticket table 1200, description thereof is omitted.

  In step S220, the scan ticket server 102 deletes the scan ticket used in step S213 from the scan ticket table 1200 (scan ticket deletion unit). The used scan ticket is deleted by deleting the scan ticket specified based on the scan ticket ID 1201 received in step S216.

  In this embodiment, the description will be made assuming that a new scan ticket called a history ticket is issued. However, the scan ticket used in step S213 may be left without being deleted. In this case, the ticket ID 1302 of the application information specified in step S217 is not updated and is left as it is. If a scan ticket for application is acquired in step S203, the scan ticket corresponding to the application information whose approval status flag 1306 is “0” is acquired, so that it is a scan ticket for application. It is possible to determine whether the scan ticket is for update / update. Therefore, a new history ticket may be issued or the used scan ticket may be left. There may be a scan ticket that can update the scan data already transmitted to the scan ticket server 102.

  Next, processing related to approval performed by the information processing system 100 in the embodiment of the present invention will be described with reference to the flowchart shown in FIG. This flowchart is a process in which an approver receives unapproved application information to the client terminal 101, browses attached scan data and application contents, and approves or rejects the information. Note that steps S301, S304 to S309 are performed under the control of the CPU 201 in the client terminal 101. In addition, each step of S302, S303, S310 to S314 is performed under the control of the CPU 201 in the scan ticket server 102.

  In step S <b> 301, the client terminal 101 requests the scan ticket server 102 for application information to be approved by the user who has logged in to the client terminal 101. In step S <b> 302, the scan ticket server 102 receives an unapproved application information acquisition request transmitted from the client terminal 101 and acquires it from the application information table 1300. In step S <b> 303, the scan ticket server 102 transmits the acquired unapproved application information to the client terminal 101.

  In step S304, the client terminal 101 receives unapproved application information transmitted from the scan ticket server 102, and in step S305, displays the received application information on an approval screen (not shown). In step S306, an instruction to approve or reject the displayed application information is accepted.

  In step S307, the client terminal 101 determines whether the instruction from the user accepted in step S306 is approval or denial. If it is determined that an approval instruction has been issued, the application ID 1301 is transmitted to the scan ticket server 102 for approval, and the process proceeds to step S310. If it is determined that a denial instruction has been issued, the process proceeds to step S308. To proceed.

  In step S308, since the client terminal 101 has been instructed to deny in step S306, the client terminal 101 receives an input of the reason for the denial. In step S 309, the input rejection reason and the application information application ID 1301 are transmitted to the scan ticket server 102.

  On the other hand, in step S310, the scan ticket server 102 identifies corresponding application information from the application information table 1300 based on the application ID 1301 transmitted from the client terminal 101, and the approval status flag 1306 of the application information is being approved. Change to “2” indicating If “2” is already stored, it can be left as it is.

  In step S311, the scan ticket server 102 determines whether there is a subsequent approver for the application. The subsequent approver identifies the workflow ID 1311 corresponding to the workflow ID 1305 of the application information of the application from the workflow table 1310 (see FIG. 13), refers to the approver defined in the workflow, and the subsequent approver Judgment is made. If it is determined that there is a subsequent approver, this series of processes is terminated. If it is determined that there is no subsequent approver, the process proceeds to step S312.

  In step S312, since there is no subsequent approver, the scan ticket server 102 completes the approval and deletes the history ticket corresponding to the application information for which the approval has been completed (history ticket deletion means). The application information may be deleted when the applicant confirms it, or may be deleted at this step.

  In step S316, the scan ticket server 102 receives the denial information transmitted in step S309, and in step S317, updates the corresponding application information based on the received denial information. Specifically, the application information corresponding to the received application ID 1301 is identified from the application information table 1300, and the approval status flag of the identified application information is changed to “3” indicating denial. Further, the reason for rejecting the input received in step S308 is stored in the reason for rejecting 1308. As described above, processing for accepting or rejecting an application from an approver is received and processed.

  Next, processing related to history ticket use performed by the information processing system 100 according to the embodiment of the present invention will be described with reference to the flowchart shown in FIG. This flowchart is a process in which the applicant receives a history ticket from the multifunction machine 103 and updates the scan data that has already been transmitted. Each step of S403 and S404 is processed under the control of the CPU 201 in the scan ticket server 102. In addition, steps S401, S402, and S405 to S412 are processed under the control of the CPU 301 in the multifunction machine 103.

  First, in step S401, the multifunction device 103 logs in to the multifunction device 103 in accordance with an instruction from the user. As long as the user can be specified, any login method may be used.

  In step S402, the multi-function peripheral 103 requests the scan ticket server 102 for a history ticket list in order to obtain a list of history tickets possessed by the user who has logged in in step S401. In step S 403, the scan ticket server 102 acquires the history ticket of the user who has logged in in step S 401 from the history ticket table 1210 in response to the history ticket list acquisition request from the multifunction device 103. For example, when the logged-in user is “Kaneshiro”, records in which “Kaneshiro” is stored in the owner 1212 in the history ticket table 1210 shown in FIG. To get. Here, since it is only necessary to acquire a list of history tickets, only information necessary for screen display in step S406 described later is acquired. In this embodiment, the history ticket list is acquired in this way, but a history ticket (record in the history ticket table 1210) may be acquired in this step.

  In step S <b> 404, the scan ticket server 102 transmits the history ticket list acquired in step S <b> 403 to the multifunction machine 103. In step S405, the multifunction peripheral 103 receives the history ticket list transmitted from the scan ticket server 102, and in step S406, displays the received history ticket list on the history ticket selection screen 1600 (see FIG. 16). In step S407, selection for the displayed history ticket is accepted.

  In step S408, the multi-function peripheral 103 determines whether a history ticket has been selected by an operation from the user. If it is determined that a history ticket has been selected, the process proceeds to step S409. If not, the process waits until it is selected.

  In step S409, the MFP 103 indicates whether the approval status flag 1306 of the selected history ticket indicates unprocessed (“1”), indicating approval (“2”), or denial (“3”). It is determined whether. The approval status flag 1306 may be transmitted from the scan ticket server 102 in step S404, or the history ticket ID 1211 of the history ticket selected in step S409 is transmitted to the scan ticket server 102, and the corresponding history ticket is displayed. You may acquire from the application information linked. If the approval status flag 1306 indicates unprocessed, the process proceeds to step S410. If the approval status flag 1306 indicates approval, the process proceeds to step S411, and the approval status flag 1306 indicates denial. Advances the process to step S412.

  In step S410, the multi-function peripheral 103 displays a history ticket usage menu in the case of unapproved, accepts menu selection from the user, and executes the selected menu. Details of the unapproved process are shown in FIG.

  In step S411, the multi-function peripheral 103 displays a history ticket usage menu in the case of approval, accepts menu selection from the user, and executes the selected menu. Details of the approval process are shown in FIG.

  In step S412, the multi-function peripheral 103 displays a history ticket usage menu when it is being denied, accepts a menu selection from the user, and executes the selected menu. Details of the rejection process are shown in FIG.

  Next, processing related to the use of a history ticket at the time of non-approval performed by the information processing system 100 in the embodiment of the present invention will be described using the flowchart shown in FIG. This flowchart is a process of using a history ticket when an application associated with the selected history ticket is not approved by any approver. Note that each of steps S505, S506, S511 to S513, S515, and S516 is performed under the control of the CPU 201 in the scan ticket server 102. In addition, steps S501 to S504, S507 to S510, and S514 are performed under the control of the CPU 301 in the multifunction machine 103.

  First, in step S501, the multi-function peripheral 103 displays an unapproved menu screen 1700 (see FIG. 17) that displays a menu that can be used with a history ticket when it is in an unapproved state (accepting means). In step S502, a selection for a menu provided in the displayed unapproved menu screen 1700 is accepted.

  In step S503, the multi-function peripheral 103 determines whether the menu accepted in step S502 is scan data replacement or application cancellation. Specifically, it is determined whether the replace button 1701 provided in the unapproved menu screen 1700 has been pressed or whether the withdrawal button 1702 has been pressed. If it is determined that the scan data is to be replaced, the process proceeds to step S504. If it is determined that the application is to be withdrawn, the process proceeds to step S514.

  In step S <b> 504, the multi-function peripheral 103 transmits a history ticket acquisition request received in step S <b> 407 to the scan ticket server 102. In step S 505, the scan ticket server 102 receives the history ticket acquisition request transmitted from the multi-function peripheral 103, and acquires from the history ticket table 1210 the history ticket that has been selected in step S 407. Specifically, the history ticket ID 1211 of the history ticket selected from the MFP 103 may be transmitted, and the history ticket matching the history ticket ID 1211 transmitted by the scan ticket server 102 may be extracted from the history ticket table 1210.

  In step S506, the scan ticket server 102 transmits the history ticket acquired in step S505 to the multi-function peripheral 103 (history ticket transmission unit). In step S507, the MFP 103 receives the history ticket transmitted from the scan ticket server 102. In step S508, the MFP 103 changes the scan setting of the MFP 103 based on the received history ticket. In step S509, the multifunction peripheral 103 executes a scan with the scan setting changed in step S508 in response to an instruction from the user.

  In step S510, the multifunction peripheral 103 transmits the scan data scanned in step S509 and the history ticket ID 1211 of the history ticket used in association with the scan to the scan ticket server 102 (update data transmission unit). In step S511, the scan ticket server 102 receives the scan data and the history ticket ID 1211 transmitted from the multifunction machine 103. In step S512, the scan ticket server 102 specifies application information based on the received history ticket ID 1211. That is, it specifies which scan data the received scan data should be replaced with.

  In step S513, the scan ticket server 102 stores the scan data received in step S511 in the scan data 1309 of the application information specified in step S512 (scan data update unit). By doing this, the scan data is replaced.

  On the other hand, if it is canceled in step S503, in step S514, the multi-function peripheral 103, together with the history ticket ID 1211 of the history ticket selected in step S407, in order to cancel the application to the scan ticket server 102, A request for withdrawal of application information is transmitted to the scan ticket server 102.

  In step S 515, the scan ticket server 102 receives the request for withdrawal of application information transmitted from the multifunction device 103 and deletes the application information specified from the history ticket ID 1211 from the application information table 1300. In other words, the application will be withdrawn.

  In step S 516, the scan ticket server 102 deletes the history ticket specified from the history ticket ID 1211 transmitted from the multifunction machine 103 from the history ticket table 1210. In this way, unnecessary history tickets are deleted.

  Next, processing related to the use of a history ticket during approval performed by the information processing system 100 according to the embodiment of the present invention will be described with reference to the flowchart shown in FIG. This flowchart is a process of using a history ticket when a part of an approver has approved an application associated with the selected history ticket. Note that steps S604 and S605 are performed under the control of the CPU 201 in the scan ticket server 102. In addition, each step of S601 to S603 is performed under the control of the CPU 301 in the multifunction machine 103.

  First, in step S601, the multi-function peripheral 103 displays a menu screen for approval 1800 (see FIG. 18) that displays a menu that can be used in the history ticket when the MFP is in the approval status (reception unit). In step S602, a selection for the menu provided on the displayed approval menu screen 1800 is accepted. The fact that the application has been approved by some approver means that the replacement of the scan data may result in an illegal application, and therefore only the withdrawal of the application is accepted on the in-approval menu screen 1800. When the pressing of the withdrawal button 1801 is accepted, the process proceeds to step S603.

  In step S603, the MFP 103 transmits a request for withdrawal of application information to the scan ticket server 102 together with the history ticket ID 1211 of the history ticket selected in step S407 in order to withdraw the application from the scan ticket server 102. .

  In step S <b> 604, the scan ticket server 102 receives the request for withdrawal of application information transmitted from the multi-function peripheral 103, and deletes the application information specified from the history ticket ID 1211 from the application information table 1300. In other words, the application will be withdrawn.

  In step S <b> 605, the scan ticket server 102 deletes the history ticket specified from the history ticket ID 1211 transmitted from the multifunction peripheral 103 from the history ticket table 1210. In this way, unnecessary history tickets are deleted.

  Next, processing related to history ticket use when the information processing system 100 according to the embodiment of the present invention is denied will be described with reference to the flowchart shown in FIG. This flowchart is a process of using a history ticket when an application associated with the selected history ticket is rejected by the approver. Note that each of steps S705, S706, S711 to S714, S716, and S717 is performed under the control of the CPU 201 in the scan ticket server 102. In addition, steps S701 to S704, S707 to S710, and S715 are processed under the control of the CPU 301 in the multifunction machine 103.

  First, in step S701, the MFP 103 displays a rejection menu screen 1900 (see FIG. 19) that displays a menu that can be used in the history ticket in the rejection state (accepting means). In step S <b> 702, a selection for a menu provided on the displayed disapproval menu screen 1900 is accepted. On the denial menu screen 1900, the reason for the denial may be displayed and used as a reference for subsequent processing. The reason for rejection may be acquired together with the history ticket list in step S403, or may be received from the scan ticket server 102 when the rejection menu screen 1900 is displayed in step S701.

  In step S703, the multi-function peripheral 103 determines whether the menu received in step S702 is replacement of scan data or withdrawal of an application. Specifically, it is determined whether the replacement button 1901 provided in the denial menu screen 1900 is pressed or the withdrawal button 1902 is pressed. If it is determined that the scan data is to be replaced, the process proceeds to step S704. If it is determined that the application is to be withdrawn, the process proceeds to step S715.

  In step S <b> 704, the multi-function peripheral 103 transmits a history ticket acquisition request received in step S <b> 407 to the scan ticket server 102. In step S <b> 705, the scan ticket server 102 receives the history ticket acquisition request transmitted from the MFP 103, and acquires the history ticket whose selection has been accepted in step S <b> 407 from the history ticket table 1210. Specifically, the history ticket ID 1211 of the history ticket selected from the MFP 103 may be transmitted, and the history ticket matching the history ticket ID 1211 transmitted by the scan ticket server 102 may be extracted from the history ticket table 1210.

  In step S706, the scan ticket server 102 transmits the history ticket acquired in step S705 to the multi-function peripheral 103. In step S707, the multifunction peripheral 103 receives the history ticket transmitted from the scan ticket server 102. In step S708, the scan setting of the multifunction peripheral 103 is changed based on the received history ticket. In step S709, the multi-function peripheral 103 executes a scan with the scan setting changed in step S708 in response to an instruction from the user.

  In step S710, the multi-function peripheral 103 transmits the scan data scanned in step S709 and the history ticket ID 1211 of the history ticket used in association with the scan to the scan ticket server 102. In step S711, the scan ticket server 102 receives the scan data and the history ticket ID 1211 transmitted from the multifunction machine 103. In step S712, the scan ticket server 102 specifies application information based on the received history ticket ID 1211. That is, it specifies which scan data the received scan data should be replaced with.

  In step S713, the scan ticket server 102 stores the scan data received in step S711 in the scan data 1309 of the application information specified in step S712. By doing this, the scan data is replaced.

  In step S714, the scan ticket server 102 returns the approval regarding the application information specified in step S712 to a predetermined approver. Since it is considered that the scan data that has been rejected by the approver and has resolved the reason for rejection is uploaded, the application is returned to the predetermined approver for re-approval and the approval is resumed. The return destination may be the first approver or the rejected approver. It can be changed by setting.

  On the other hand, since an application withdrawal instruction has been given, in step S715, the multifunction peripheral 103 requests application information from the scan ticket server 102 together with the history ticket ID 1211 of the history ticket selected in step S407. Is sent to the scan ticket server 102.

  In step S 716, the scan ticket server 102 receives the request for withdrawal of application information transmitted from the multifunction machine 103 and deletes the application information specified from the history ticket ID 1211 from the application information table 1300. In other words, the application will be withdrawn.

  In step S 717, the scan ticket server 102 deletes the history ticket specified from the history ticket ID 1211 transmitted from the multifunction machine 103 from the history ticket table 1210. In this way, unnecessary history tickets are deleted.

  In this way, when a scan ticket is used, a new history ticket is issued, and when the issued history ticket is used, the scan data sent using the scan ticket is updated or the application is withdrawn. Can do.

  Next, a second embodiment will be described in which a used scan ticket is reused without newly issuing a history ticket. In the above-described processing, when a scan ticket is used, a history ticket for update is newly issued. However, the used scan ticket may be used as it is without being deleted. Hereinafter, a description will be given of the point that the used scan ticket can be used from the history.

  Since the system configuration, hardware configuration, and module configuration are the same as those described above, description thereof will be omitted. 5 and FIG. 7 are the same as those described above, and thus the description thereof is omitted.

  First, processing relating to scan ticket use performed by the information processing system 100 according to the second embodiment of the present invention will be described with reference to the flowchart shown in FIG. In this flowchart, the MFP 103 receives a scan ticket from the scan ticket server 102, changes the scan setting of the MFP 103 based on the scan ticket, and executes a scan. Note that steps S203, S204, S210, S211, S216 to S218, and S801 are processed under the control of the CPU 201 in the scan ticket server 102. The steps S201, S202, S205 to S209, and S212 to S215 are processed under the control of the CPU 301 in the multifunction machine 103.

  Steps S201 to S218 in FIG. 20 are the same as steps S201 to S218 in FIG.

  In step S801, the scan ticket server 102 changes the scan ticket used in step S213 to “used”. Specifically, the scan ticket is identified from the scan ticket ID 1201 received in step S216, and the used 2501 of the scan ticket is changed to “1”. A scan ticket table 1200 used in the second embodiment is shown in FIG. The scan ticket table 1200 of FIG. 25 includes a new used 2501. Used 2501 is information indicating whether or not the scan ticket has been used. If “1” is stored, it indicates that it has been used. If “0” is stored, it is unused. It shows that. In the second embodiment, the scan ticket whose used 2501 is “1” is referred to as a history ticket.

  Next, processing related to history ticket use performed by the information processing system 100 in the embodiment of the present invention will be described with reference to the flowchart shown in FIG. This flowchart is a process in which the applicant receives a history ticket from the multifunction machine 103 and updates the scan data that has already been transmitted. Note that steps S1002 and S1003 are performed under the control of the CPU 201 in the scan ticket server 102. Further, steps S401, S407 to S412, S1001, S1004, and S1005 are processed under the control of the CPU 301 in the multi-function peripheral 103.

  Step S401 and steps S407 to S412 in FIG. 21 are the same as step S401 and steps S407 to S412 in FIG.

  In step S1001, the multi-function peripheral 103 requests a history ticket list from the scan ticket server 102 to acquire a list of history tickets possessed by the user who has logged in in step S401. In step S1002, the scan ticket server 102 acquires the history ticket of the user logged in in step S401 from the scan ticket table 1200 shown in FIG. 25 in response to the history ticket list acquisition request from the multifunction device 103. For example, when the logged-in user is “Kaneshiro”, in the scan ticket table 1200 shown in FIG. 25, records (1, 5) in which “Kaneshiro” is stored in the owner 1212 and “1” is stored in the used 2501. 2) of the record. Here, since it is only necessary to obtain a history ticket list, only information necessary for screen display in step S1005 described later is obtained.

  In step S1003, the scan ticket server 102 transmits the history ticket list acquired in step S1002 to the multi-function peripheral 103. In step S1004, the multifunction peripheral 103 receives the history ticket list transmitted from the scan ticket server 102, and in step S1005, the received history ticket list is displayed on the history ticket selection screen 1600 (see FIG. 16). In this way, a used scan ticket is acquired and selection is accepted.

  Next, processing related to the use of a history ticket at the time of non-approval performed by the information processing system 100 in the embodiment of the present invention will be described using the flowchart shown in FIG. This flowchart is a process of using a history ticket when an application associated with the selected history ticket is not approved by any approver. Note that the steps S1102, S1103, S1106 to S1108, S1110, and S1111 are processed under the control of the CPU 201 in the scan ticket server 102. Further, steps S501 to S503, S508, S509, S1101, S1104, S1105, and S1109 are processed under the control of the CPU 301 in the multi-function peripheral 103.

  Steps S501 to S503, S508, and S509 in FIG. 22 are the same as steps S501 to S503, S508, and S509 in FIG.

  In step S <b> 1101, the MFP 103 transmits a history ticket acquisition request received in step S <b> 407 to the scan ticket server 102. In step S1102, the scan ticket server 102 receives the history ticket acquisition request transmitted from the multi-function peripheral 103, and acquires the history ticket whose selection has been accepted in step S407 from the scan ticket table 1200. Specifically, the scan ticket ID 1201 of the history ticket selected from the MFP 103 may be transmitted, and the history ticket that matches the scan ticket ID 12101 transmitted by the scan ticket server 102 may be extracted from the scan ticket table 1200.

  In step S <b> 1103, the scan ticket server 102 transmits the history ticket acquired in step S <b> 1102 to the multifunction machine 103. In step S <b> 1104, the multifunction machine 103 receives the history ticket transmitted from the scan ticket server 102.

  When a scan is executed based on the received history ticket, in step S1105, the multi-function peripheral 103 scans the scan data scanned in step S509 and the scan ticket ID 1201 of the history ticket used along with the scan. Send to. In step S1106, the scan ticket server 102 receives the scan data and the scan ticket ID 1201 transmitted from the multifunction machine 103. In step S1107, the scan ticket server 102 specifies application information based on the received scan ticket ID 1201. That is, it specifies which scan data the received scan data should be replaced with.

  In step S1108, the scan ticket server 102 stores the scan data received in step S1106 in the scan data 1309 of the application information specified in step S1107. By doing this, the scan data is replaced.

  On the other hand, if it is canceled in step S503, in step S1109, the multi-function peripheral 103, together with the scan ticket ID 1201 of the history ticket selected in step S407, in order to cancel the application to the scan ticket server 102, A request for withdrawal of application information is transmitted to the scan ticket server 102.

  In step S <b> 1110, the scan ticket server 102 receives a request for withdrawal of application information transmitted from the multi-function peripheral 103, and deletes application information specified from the scan ticket ID 1201 from the application information table 1300. In other words, the application will be withdrawn.

  In step S <b> 1111, the scan ticket server 102 deletes the history ticket specified from the scan ticket ID 1201 transmitted from the multifunction device 103 from the scan ticket table 1200. In this way, unnecessary history tickets are deleted.

  Next, processing related to the use of a history ticket during approval performed by the information processing system 100 according to the embodiment of the present invention will be described with reference to the flowchart shown in FIG. This flowchart is a process of using a history ticket when a part of an approver has approved an application associated with the selected history ticket. Note that steps S1202 and S1203 are performed under the control of the CPU 201 in the scan ticket server 102. Further, each step of S601, S602, and S1201 is performed under the control of the CPU 301 in the multifunction machine 103.

  Steps S601 and S602 in FIG. 23 are the same as steps S601 and S602 in FIG.

  In step S1201, the MFP 103 transmits a request for withdrawal of application information to the scan ticket server 102 together with the scan ticket ID 1201 of the history ticket selected in step S407 in order to cancel the application to the scan ticket server 102. .

  In step S <b> 1202, the scan ticket server 102 receives the request for withdrawal of the application information transmitted from the multifunction machine 103 and deletes the application information specified from the scan ticket ID 1201 from the application information table 1300. In other words, the application will be withdrawn.

  In step S <b> 1203, the scan ticket server 102 deletes the history ticket specified from the scan ticket ID 1201 transmitted from the multifunction machine 103 from the scan ticket table 1200. In this way, unnecessary history tickets are deleted.

  Next, processing related to history ticket use when the information processing system 100 in the embodiment of the present invention is denied will be described with reference to the flowchart shown in FIG. This flowchart is a process of using a history ticket when an application associated with the selected history ticket is rejected by the approver. The steps S714, S1302, S1303, S1306 to S1308, S1310, and S1311 are processed under the control of the CPU 201 in the scan ticket server 102. Further, steps S701 to S703, S708, S709, S1301, S1304, S1305, and S1309 are processed under the control of the CPU 301 in the multi-function peripheral 103.

  Steps S701 to S703, S708, and S709 in FIG. 24 are the same as Steps S701 to S703, Step S708, and Step S709 in FIG.

  In step S <b> 1301, the multi-function peripheral 103 transmits a history ticket acquisition request received in step S <b> 407 to the scan ticket server 102. In step S <b> 1302, the scan ticket server 102 receives the history ticket acquisition request transmitted from the multifunction peripheral 103, and acquires the history ticket whose selection has been accepted in step S <b> 407 from the scan ticket table 1200. Specifically, the scan ticket ID 1201 of the history ticket selected from the MFP 103 may be transmitted, and the history ticket that matches the scan ticket ID 1201 transmitted by the scan ticket server 102 may be extracted from the scan ticket table 1200.

  In step S1303, the scan ticket server 102 transmits the history ticket acquired in step S1302 to the multi-function peripheral 103. In step S 1304, the multifunction peripheral 103 receives the history ticket transmitted from the scan ticket server 102.

  When a scan is executed based on the received history ticket, in step S1305, the multi-function peripheral 103 scans the scan data scanned in step S709 and the scan ticket ID 1201 of the history ticket used in association with the scan. Send to. In step S1306, the scan ticket server 102 receives the scan data and the scan ticket ID 1201 transmitted from the multifunction machine 103. In step S1307, the scan ticket server 102 specifies application information based on the received scan ticket ID 1201. That is, it specifies which scan data the received scan data should be replaced with.

  In step S1308, the scan ticket server 102 stores the scan data received in step S1306 in the scan data 1309 of the application information specified in step S1307. By doing this, the scan data is replaced.

  On the other hand, since an application withdrawal instruction has been given, in step S1309, the multifunction machine 103 requests application information from the scan ticket server 102 together with the scan ticket ID 1201 of the history ticket selected in step S407 in order to cancel the application. Is sent to the scan ticket server 102.

  In step S <b> 1310, the scan ticket server 102 receives the application information withdrawal request transmitted from the multi-function peripheral 103, and deletes the application information specified from the scan ticket ID 1201 from the application information table 1300. In other words, the application will be withdrawn.

  In step S1311, the scan ticket server 102 deletes the history ticket specified from the scan ticket ID 1201 transmitted from the multifunction machine 103 from the scan ticket table 1200. In this way, unnecessary history tickets are deleted.

  In this way, the transmitted scan data can be updated by allowing the used scan ticket to be reused.

  As described above, according to the present embodiment, by using a scan ticket for generating scan data to be attached to an approval application, a history ticket for changing the scan data is issued, and the history ticket Since it is possible to easily change the scan data transmitted with the scan ticket, it is possible to improve the business efficiency of the user.

  The present invention can be implemented as a system, apparatus, method, program, storage medium, or the like, and can be applied to a system including a plurality of devices. You may apply to the apparatus which consists of one apparatus.

  Note that the present invention includes a software program that implements the functions of the above-described embodiments directly or remotely from a system or apparatus. The present invention also includes a case where the system or the computer of the apparatus is achieved by reading and executing the supplied program code.

  Accordingly, since the functions of the present invention are implemented by computer, the program code installed in the computer also implements the present invention. In other words, the present invention includes a computer program itself for realizing the functional processing of the present invention.

  In that case, as long as it has the function of a program, it may be in the form of object code, a program executed by an interpreter, script data supplied to the OS, and the like.

  Examples of the recording medium for supplying the program include a flexible disk, hard disk, optical disk, magneto-optical disk, MO, CD-ROM, CD-R, and CD-RW. There are also magnetic tape, nonvolatile memory card, ROM, DVD (DVD-ROM, DVD-R) and the like.

  As another program supply method, a browser on a client computer is used to connect to an Internet home page. The computer program itself of the present invention or a compressed file including an automatic installation function can be downloaded from the homepage by downloading it to a recording medium such as a hard disk.

  It can also be realized by dividing the program code constituting the program of the present invention into a plurality of files and downloading each file from a different homepage. That is, a WWW server that allows a plurality of users to download a program file for realizing the functional processing of the present invention on a computer is also included in the present invention.

  In addition, the program of the present invention is encrypted, stored in a storage medium such as a CD-ROM, distributed to users, and key information for decryption is downloaded from a homepage via the Internet to users who have cleared predetermined conditions. Let It is also possible to execute the encrypted program by using the downloaded key information and install the program on a computer.

  Further, the functions of the above-described embodiments are realized by the computer executing the read program. In addition, based on the instructions of the program, an OS or the like running on the computer performs part or all of the actual processing, and the functions of the above-described embodiments can also be realized by the processing.

  Further, the program read from the recording medium is written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer. Thereafter, the CPU of the function expansion board or function expansion unit performs part or all of the actual processing based on the instructions of the program, and the functions of the above-described embodiments are realized by the processing.

  The above-described embodiments are merely examples of implementation in carrying out the present invention, and the technical scope of the present invention should not be construed as being limited thereto. That is, the present invention can be implemented in various forms without departing from the technical idea or the main features thereof.

100 Information Processing System 101 Client Terminal 102 Scan Ticket Server 103 Multifunction Machine 104 Network 201 CPU
202 RAM
203 ROM
204 System Bus 205 Input Controller 206 Video Controller 207 Memory Controller 208 Communication I / F (Interface) Controller 209 Input Device 210 Display Device 211 External Memory

Claims (11)

An information processing system including a management server and an image processing apparatus capable of scanning a paper document ,
The management server
A scan ticket is data scan settings have been defined, a storage means for memorize a Ru generated scan data by scanning a paper document in the image processing apparatus,
A scan ticket transmitting means for transmitting the stored scan ticket in the storage unit to the image processing apparatus,
A scan data receiver that will receive the scan data generated using the transmitted scan ticket in the scan ticket transmitting unit from the image processing apparatus,
Scan data storage means for storing the scan data received by the scan data reception means in the storage means;
With
The image processing apparatus includes:
A scan ticket receiving means for receiving a scan ticket transmitted from the management server,
Scan data generating means for generating scan data by scanning a paper document using the scan ticket received by the scan ticket receiving means;
And a scan data transmission means for transmitting the scan data generated by the scan data generating means to said management server,
The scan data generation unit is configured to scan data for replacing the scan data stored in the storage unit by the scan data storage unit based on the scan setting defined in the scan ticket used by the scan data generation unit. Generate
When the scan data storage unit receives scan data for replacing the scan data stored in the storage unit, the scan data storage unit replaces the received scan data with the scan data stored in the storage unit and stores the received scan data. An information processing system characterized by this. The scan data generation unit re-uses the scan ticket used by the scan data generation unit, and generates scan data based on settings defined in the scan ticket . Information processing system. The management server
When the scan data received from the image processing apparatus by the scan data storage unit is stored in the storage unit, the scan data is replaced based on the scan ticket used when generating the scan data. It further comprises scan ticket generation means for generating a scan ticket,
The scan data generation unit uses the scan ticket generated by the scan ticket generation unit to generate scan data based on settings defined in the scan ticket. The information processing system described. The management server
When the scan ticket for replacing the scan data is generated by the scan ticket generation unit, the scan ticket generation unit further includes a scan ticket deletion unit that deletes the scan ticket used when generating the scan data. Item 4. The information processing system according to Item 3 . 5. The scan data storage unit stores the scan data received by the scan data reception unit in a storage area indicated by a storage destination defined in the scan ticket. The information processing system described. The scan data generation unit is stored in the storage unit by the scan data storage unit based on the file format, resolution, reading setting, and number of pages of the scan data defined in the scan ticket used by the scan data generation unit. the information processing system according to any one of claims 1 to 5, characterized in that to generate the scan data for replacing the scanned data. A management server having storage means for storing scan tickets, which are data for which scan settings are defined, and scan data generated by scanning a paper document with an image processing apparatus, and image processing capable of scanning a paper document An information processing system control method including an apparatus,
A scan ticket transmitting unit of the management server, the scan ticket transmitting step of transmitting the scan ticket stored in the storage unit to the image processing device;
A scan ticket receiving unit of the image processing apparatus for receiving a scan ticket transmitted from the management server; and
A scan data generating step of generating scan data by scanning a paper document using the scan ticket received by the scan ticket receiving step of the scan data generating means of the image processing apparatus;
A scan data transmitting unit of the image processing apparatus, the scan data transmitting step of transmitting the scan data generated in the scan data generating step to the management server;
A scan data receiving step in which the scan data receiving means of the management server receives the scan data generated using the scan ticket transmitted in the scan ticket transmitting step from the image processing device;
A scan data storage step of the management server storing the scan data received in the scan data reception step in the storage unit;
With
In the scan data generation step, based on the scan setting defined in the scan ticket used in the scan data generation step, scan data for replacing the scan data stored in the storage unit in the scan data storage step Generate and
The scan data storing step replaces the received scan data with the scan data stored in the storage unit when the scan data for replacing the scan data stored in the storage unit is received. A method for controlling an information processing system. A management server having storage means for storing scan tickets, which are data for which scan settings are defined, and scan data generated by scanning a paper document with an image processing apparatus, and image processing capable of scanning a paper document A computer-readable program for causing a computer to execute a control method of an information processing system including an apparatus,
The management server
Scan ticket transmission means for transmitting the scan ticket stored in the storage means to the image processing apparatus;
Scan data receiving means for receiving, from the image processing device, scan data generated using the scan ticket transmitted by the scan ticket transmitting means;
Scan data storage means for storing scan data received by the scan data receiving means in the storage means
Function as
The image processing apparatus;
Scan ticket receiving means for receiving a scan ticket transmitted from the management server;
Scan data generating means for generating scan data by scanning a paper document using the scan ticket received by the scan ticket receiving means;
Scan data transmitting means for transmitting scan data generated by the scan data generating means to the management server
Function as
The scan data generation unit is configured to scan data for replacing the scan data stored in the storage unit by the scan data storage unit based on the scan setting defined in the scan ticket used by the scan data generation unit. Generate and
When the scan data storage unit receives scan data for replacing the scan data stored in the storage unit, the scan data storage unit replaces the received scan data with the scan data stored in the storage unit and stores the received scan data. A program that can be read and executed by a computer. A scan ticket receiving unit that receives a scan ticket that is data defined by a scan setting transmitted from the management server, and scan data by scanning a paper document using the scan ticket received by the scan ticket receiving unit. Scan data generating means for generating the scan data, and scan data transmitting means for transmitting the scan data generated by the scan data generating means to the management server, wherein the scan data generating means uses the scan data generated by the scan data generating means. Based on the scan settings defined in the ticket, the scan data storage unit generates scan data to be replaced with the scan data stored in the storage unit, and is communicably connected to the image processing apparatus. , The scan ticket, Serial image processing apparatus a management server having a storage means for storing the scan data generated by scanning a paper document,
Scan ticket transmission means for transmitting the scan ticket stored in the storage means to the image processing apparatus;
Scan data receiving means for receiving, from the image processing device, scan data generated using the scan ticket transmitted by the scan ticket transmitting means;
Scan data storage means for storing the scan data received by the scan data reception means in the storage means;
With
When the scan data storage unit receives scan data for replacing the scan data stored in the storage unit, the scan data storage unit replaces the received scan data with the scan data stored in the storage unit and stores the received scan data. A management server characterized by that. A scan ticket receiving unit that receives a scan ticket that is data defined by a scan setting transmitted from the management server, and scan data by scanning a paper document using the scan ticket received by the scan ticket receiving unit. Scan data generating means for generating the scan data, and scan data transmitting means for transmitting the scan data generated by the scan data generating means to the management server, wherein the scan data generating means uses the scan data generated by the scan data generating means. Based on the scan settings defined in the ticket, the scan data storage unit generates scan data to be replaced with the scan data stored in the storage unit, and is communicably connected to the image processing apparatus. , The scan ticket, Serial image processing apparatus and a control method of a management server having a storage means for storing the scan data generated by scanning a paper document,
A scan ticket transmitting unit of the management server, the scan ticket transmitting step of transmitting the scan ticket stored in the storage unit to the image processing device;
A scan data receiving step in which the scan data receiving means of the management server receives the scan data generated using the scan ticket transmitted in the scan ticket transmitting step from the image processing device;
A scan data storage step in which the scan data storage means of the management server stores the scan data received in the scan data reception step in the storage means;
With
The scan data storing step replaces the received scan data with the scan data stored in the storage unit when the scan data for replacing the scan data stored in the storage unit is received. A control method for a management server. A scan ticket receiving unit that receives a scan ticket that is data defined by a scan setting transmitted from the management server, and scan data by scanning a paper document using the scan ticket received by the scan ticket receiving unit. Scan data generating means for generating the scan data, and scan data transmitting means for transmitting the scan data generated by the scan data generating means to the management server, wherein the scan data generating means uses the scan data generated by the scan data generating means. Based on the scan settings defined in the ticket, the scan data storage unit generates scan data to be replaced with the scan data stored in the storage unit, and is communicably connected to the image processing apparatus. , The scan ticket, Serial image processing apparatus comprising executable program read into the computer for executing a control method of a management server having a storage means for storing the scan data generated in the computer by scanning the paper document,
The management server
Scan ticket transmission means for transmitting the scan ticket stored in the storage means to the image processing apparatus;
Scan data receiving means for receiving, from the image processing device, scan data generated using the scan ticket transmitted by the scan ticket transmitting means;
Scan data storage means for storing scan data received by the scan data receiving means in the storage means
Function as
When the scan data storage unit receives scan data for replacing the scan data stored in the storage unit, the scan data storage unit replaces the received scan data with the scan data stored in the storage unit and stores the received scan data. A program that can be read and executed by a computer.

Images