Information processing device and information processing program

Abstract

To provide an information processing device and an information processing program for reducing a burden on a user when defining the process related to inspection of the information described in a form.SOLUTION: In a form system, an information processing device includes a processor. The processor includes the steps of: receiving, from a user, first inspection processing information on the inspection of the information described in an item of a first form (S300); acquiring second inspection processing information on the inspection of the information described in an item of a second form indicating the inspection process common to the first inspection process (S302); performing a proposal for the commonization of the first inspection processing information and the second inspection processing information (S304); accepting, from the user, whether or not to commonize both the first inspection processing information and the second inspection processing information (S306); and reflecting the change on the other when the commonization of the first inspection processing information and the second inspection processing information is received and then, when one of the first inspection processing information and the second inspection processing information is changed (S308).SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The present disclosure relates to an information processing device and an information processing program. [Background technology]

[0002] Conventionally, there has been known a technique for verifying whether character recognition was successful for data extracted from a form by OCR in an information processing device that performs information processing (OCR) to recognize characters on an image obtained by optically scanning a form. For example, Patent Document 1 discloses a technique for an OCR input data screen correction means that recognizes information written on a form using OCR and corrects the recognition results. This technique is characterized by including: a recognition result management means that can store the recognition results for one form, extract the recognition results for each individual field, and store the page image for one form; a character field correction means that can acquire the recognition results for each individual field from the recognition result management means, display and correct them, and, if corrected, notify the recognition result management means of the corrected recognition results; and an image display means that can display an image of an individual image field or an image of the entire page from the recognition result management means.

[0003] Patent Document 2 also discloses a technology for a data check device that checks data to be checked according to a data check execution program. This technology is characterized by having a check condition incorporating means that incorporates the check condition file corresponding to the data format of the data to be checked this time into a data check base program section that can incorporate any of a plurality of check condition files prepared for each data format, and creates a program to execute a data check to be applied in the current check, and a check procedure control means that executes a check of the data to be checked according to the created data check execution program.

[0004] Furthermore, Patent Document 3 discloses a technology for an OCR data input processing method that includes an OCR device and an OCR data input program, and that, under the control of the OCR data input program, reads OCR data entered on a form, checks for general-purpose logical errors, and corrects the read results if necessary before inputting them. This technology is characterized by providing a user program that performs a user-specific logical error check on the read OCR data, and by setting a calling relationship from the OCR data input program to the user program at the processing stage of reading character data from a form in the OCR data input program and the processing stage of correcting errors in the read data, and having the user program perform detailed logical checks of the OCR data at each processing stage. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2000-155802 [Patent Document 2] Japanese Patent Application Laid-Open No. 2014-044631 [Patent Document 3] Japanese Patent Application Publication No. 04-354080 Summary of the Invention [Problem to be solved by the invention]

[0006] Incidentally, an information processing device that processes information recorded on a form may require processing related to the verification of the information recorded on the form, such as verifying that a character string matches a system database. In this case, the verification processing is defined for each form item. The amount of definition information defining the verification processing for each form item increases as the number of forms increases. On the other hand, the same verification processing may be defined for multiple different form items. In this case, definition information defining the same verification processing is generated for multiple different form items. However, if the definition of the verification processing is changed for one of multiple forms for which the same verification processing is defined, the definition of the verification processing must also be changed for each of the other forms for which the same verification processing is defined. Therefore, when the same verification processing is defined for multiple forms, each time the definition information for one form is changed, the same change must be reflected in the definition information for the other forms, increasing the user's configuration burden. To address this issue, there is a function that allows you to standardize the inspection process definitions defined for multiple report items in advance, and when the standardized inspection process definition is changed, the changes can be reflected all at once in all the report items for which the inspection process definition is set. However, to use this function, the user must first understand and specify which report items' inspection process definitions should be standardized. It is a heavy burden for the user to have to understand the inspection process definitions for many report items in advance.

[0007] The present disclosure aims to provide an information processing device and an information processing program that can reduce the burden on a user compared to when the user understands in advance the items of multiple reports for which the same inspection process is defined and instructs them to be standardized. [Means for solving the problem]

[0008] In order to achieve the above object, a first aspect is an information processing device that includes a processor, which receives from a user first inspection processing information that indicates a first inspection processing related to the inspection of information described in an item of a first form, which is set in an item of a first form; obtains second inspection processing information that indicates an inspection processing common to the first inspection processing and indicates a second inspection processing related to the inspection of information described in an item of a second form that is different from the first form; proposes standardizing the first inspection processing information and the second inspection processing information; receives from the user whether or not to standardize the first inspection processing information and the second inspection processing information; and, if it is accepted that the first inspection processing information and the second inspection processing information will be standardized, when at least a portion of the inspection processing indicated in the inspection processing information of one of the first inspection processing information and the second inspection processing information is changed, reflects the changed change information in the other inspection processing information.

[0009] The second aspect proposes that in the information processing device relating to the first aspect, when the processor receives from a user the first inspection processing information newly set in an item of the first form, the processor standardizes the first inspection processing information and the second inspection processing information.

[0010] The third aspect proposes that in the information processing device relating to the first aspect, when the processor receives from the user the inspection processing information set in the items of the second form as the first inspection processing information to be used in the first inspection processing, the processor standardizes the first inspection processing information and the second inspection processing information.

[0011] The fourth aspect proposes that in the information processing device relating to the first aspect, when the processor receives from the user the inspection processing information set in the item of the second form as the first inspection processing information to be used in the first inspection processing, the processor does not share the first inspection processing information and the second inspection processing information.

[0012] In a fifth aspect, in the information processing device according to the second or third aspect, the processor displays related information related to a proposal as to whether or not to standardize the first inspection processing information and the second inspection processing information.

[0013] In a sixth aspect, in an information processing device according to any one of the first to third aspects, the processor displays information indicating that when either the first inspection processing information or the second inspection processing information is changed, the change is reflected in the other inspection processing information.

[0014] In a seventh aspect, in an information processing device according to the fourth aspect, the processor accepts the cancellation of the sharing for the other inspection processing information, and when the cancellation of the sharing is accepted, the processor does not reflect the changes to the other inspection processing information.

[0015] In an eighth aspect, in an information processing device according to any one of the first to fifth aspects, the processor acquires inspection processing information that has been set for an item of a third form, accepts any one of the acquired multiple pieces of inspection processing information as the first inspection processing information, and acquires, as the second inspection processing information, inspection processing information that has been set and is different from the first inspection processing information from the acquired multiple pieces of inspection processing information.

[0016] In a ninth aspect, in an information processing device according to any one of the first to fifth aspects, when the processor receives an instruction from a user to acquire set inspection processing information that indicates an inspection processing that is common to the first inspection processing, the processor acquires the set inspection processing information and acquires the acquired set inspection processing information as the second inspection processing information.

[0017] A tenth aspect proposes that, in the information processing device according to the first aspect, the processor displays information including image information relating to the items of the first form set in the inspection processing information to achieve the commonality.

[0018] An eleventh aspect is an information processing program that causes a processor to receive from a user first inspection processing information that is set in an item of a first form and indicates a first inspection processing related to the inspection of information described in an item of the first form; acquire second inspection processing information that indicates an inspection processing common to the first inspection processing and indicates a second inspection processing related to the inspection of information described in an item of a second form that is different from the first form; propose commonizing the first inspection processing information and the second inspection processing information; receive from the user whether or not to commonize the first inspection processing information and the second inspection processing information; and, if it is accepted that the first inspection processing information and the second inspection processing information are common, when at least a portion of the inspection processing indicated in one of the first inspection processing information and the second inspection processing information is changed, reflect the changed change information in the other inspection processing information. [Effects of the Invention]

[0019] The first and eleventh aspects have the advantage of reducing the burden on the user compared to when the user understands in advance the items of multiple reports for which the same inspection process is defined and instructs them to be standardized. According to the second aspect, there is an advantage that the burden on the user can be reduced compared to when the user instructs standardization after defining a new inspection process for an item of a form. According to the third aspect, there is an effect that the burden on the user can be reduced compared to the case where standardization is proposed regardless of the content of the first inspection processing information received from the user. According to the fourth aspect, there is an effect that the burden on the user can be reduced compared to the case where no sharing is proposed regardless of the content of the first inspection processing information received from the user. According to the fifth aspect, there is an effect that the burden on the user can be reduced compared to when related information is not displayed. According to the sixth aspect, there is an effect that the burden on the user can be reduced compared to when the user knows the shared inspection processing information in advance and instructs the sharing. According to the seventh aspect, there is an effect that the burden on the user can be reduced compared to the case where cancellation of sharing of shared inspection processing information is not accepted. According to the eighth aspect, there is an effect that the burden on the user can be reduced compared to the case where standardization is not proposed for the already set inspection processing information. According to the ninth aspect, there is an effect that the burden on the user can be reduced compared to the case where standardization is not proposed for the already set inspection processing information. According to the tenth aspect, there is an effect that the burden on the user can be reduced compared to when information including image information relating to the items of the first form is not displayed. [Brief explanation of the drawings]

[0020] [Figure 1] 1 is a diagram illustrating a schematic configuration of a form system according to an embodiment. [Figure 2] FIG. 1 is a diagram illustrating an example of a schematic electrical configuration of an information processing apparatus according to an embodiment. [Figure 3] FIG. 2 is a diagram illustrating an example of a functional configuration of an information processing apparatus according to an embodiment. [Figure 4] 10 is a flowchart illustrating an example of a flow of information processing by an information processing program according to the embodiment. [Figure 5] FIG. 10 is a diagram illustrating an example of a setting screen for setting a business check. [Figure 6] FIG. 10 is a diagram illustrating an example of a setting screen related to editing processing of task check settings. [Figure 7] 10 is a flowchart illustrating an example of the flow of a sharing proposal process. [Figure 8] FIG. 10 is a diagram showing an example of a display screen in the first promotion process. [Figure 9] FIG. 10 is a diagram illustrating an example of a screen for specifying a task check. [Figure 10] FIG. 10 is a diagram showing a confirmation screen for business check information. [Figure 11] FIG. 10 is a diagram showing a setting screen in the second promotion process. [Figure 12] FIG. 10 is a diagram illustrating an example of a setting screen related to a common selection process. [Figure 13] FIG. 10 is a diagram illustrating an example of a setting screen related to a common selection process. [Figure 14] 10 is a flowchart illustrating an example of the flow of a common selection process. [Figure 15] 10 is a flowchart illustrating an example of the flow of a commonality confirmation process. [Figure 16] FIG. 10 is a diagram illustrating an example of a confirmation screen displayed in the sharing confirmation process. [Figure 17] FIG. 10 is a diagram illustrating an example of a confirmation screen displayed in the sharing confirmation process. [Figure 18] FIG. 10 is a diagram illustrating an example of a confirmation screen displayed in the sharing confirmation process. [Figure 19] 10 is a flowchart illustrating an example of the flow of a common addition process. [Figure 20] FIG. 10 is a diagram showing an example of a designation screen displayed in the sharing addition process. [Figure 21] FIG. 10 is a diagram illustrating an example of a confirmation screen displayed in the sharing addition process. DETAILED DESCRIPTION OF THE INVENTION

[0021] An example of an embodiment for implementing the technology of the present disclosure will be described in detail below with reference to the drawings. Note that components and processes that perform the same operations, actions, and functions are assigned the same reference numerals throughout the drawings, and duplicated descriptions may be omitted as appropriate. Each drawing is merely a schematic illustration to allow a sufficient understanding of the technology of the present disclosure. Therefore, the technology of the present disclosure is not limited to the illustrated examples. Furthermore, in the embodiments, descriptions of configurations that are not directly related to the present invention or well-known configurations may be omitted.

[0022] FIG. 1 is a diagram showing a schematic configuration of a form system 10 according to this embodiment.

[0023] 1, a form system 10 includes an information processing device 20, a client terminal 40, and an input device 60. These devices are connected to a network (not shown) and can communicate with each other via the network. Examples of the network include the Internet, a LAN (Local Area Network), and a WAN (Wide Area Network).

[0024] The information processing device 20 performs OCR (Optical Character Recognition) processing on image data of multiple documents, including forms, input through the input device 60, and manages a series of processing flows for outputting the results of the OCR processing to a predetermined output destination. The specific configuration and operation of the information processing device 20 will be described later.

[0025] The client terminal 40 transmits various instructions related to the OCR process to the information processing device 20. Examples of the various instructions include an instruction to start reading information from image data and an instruction to display the results of reading the information from the image data. The client terminal 40 also displays various information, such as the results of the OCR process performed by the information processing device 20 in response to the received instructions, and notifications related to the OCR process. Examples of the client terminal 40 include a server computer or a general-purpose computer such as a personal computer (PC). While FIG. 1 illustrates only one client terminal 40, the present invention is not limited to this. A plurality of client terminals 40 may be provided, and different client terminals 40 may be used for different processes, for example.

[0026] The input device 60 inputs image data to be subjected to OCR processing into the information processing device 20. Examples of the input device 60 include a general-purpose computer device such as a server computer or a PC, and an image forming device having a scanning function, a printing function, a fax function, etc. In addition to the input device 60, image data may also be input to the information processing device 20 from the client terminal 40.

[0027] Next, an overview of the form system 10 will be described.

[0028] The form system 10 is a system in which an information processing device 20 performs OCR processing on image data input via an input device 60, and outputs the results of the OCR processing to a predetermined output destination.

[0029] The information processing device 20 manages various processes in the OCR process, including (1) business design and operational verification, (2) data input, (3) data reading, (4) document discrimination, confirmation, and correction, (5) reading result confirmation and correction, (6) business check, (7) data output, and (8) return. In this embodiment, the OCR process refers not only to the process of simply reading characters and symbols from image data, but also to post-processing such as character correction.

[0030] As an example of the management of various processes, (1) business design and operation verification, (2) data input, (3) data reading, (6) business check, and (7) data output processes are each automatically executed by the information processing device 20. Also, as an example of the management of various processes, (4) document discrimination, confirmation, and correction, and (5) reading result confirmation and correction processes are each accepted by input by the user via the client terminal 40. Also, as an example of the management of various processes, (8) return processing may be automatically executed by the information processing device 20 or may be accepted by input by the user via the client terminal 40.

[0031] In the (1) business design and operational verification process, job rules are created that include read definition settings, output settings, and business check settings. In the read definition settings, for example, the read range, which is the range in which image data information is read in the "(3) data reading" process, is set. More specifically, for example, a definition can be set such that the item value, which is the value, is read from near the right of the item extracted as a key. In the output settings, for example, the file format and output destination of the output data to be output in the "(7) data output" process are set. In the business check settings, for example, the required input fields in the form to be detected in the "(6) business check" process, and the format, such as the number of characters that can be entered, are set.

[0032] In the (2) data input process, image data is accepted as input from the input device 60. The accepted image data is registered as a job, which is the execution unit of the "(3) data reading" process.

[0033] In the (3) data reading process, the information of the image data in the job is read using the job rule for the job to be executed, selected by the user from the job rules created in the process of "(1) Business Design and Operational Verification." As an example, this process identifies the form included in the image data in the job (hereinafter referred to as "form identification") and reads the characters and symbols within the reading range.

[0034] In the (4) form identification, confirmation, and correction process, the image data in the job is divided into records that indicate the forms included in the job based on the results of the form identification performed in the "(3) Data Reading" process. After that, in this process, the divided records are displayed, and the user can confirm and correct the form identification.

[0035] In the process of (5) checking and correcting the read result, the read result of the characters and symbols within the read range obtained in the process of "(3) data reading" is displayed, and the user can check and correct the read result.

[0036] In the (6) business process check process, errors in each preceding process are detected by the business process check settings included in the job rules for the job selected by the user from the job rules created in the "(1) business process design and operation verification" process. The detection results may be presented to the user.

[0037] (7) In the data output process, output data is created using the output settings included in the job rules for the job selected by the user from the job rules created in the process of "(1) Business design and operational verification," and the created output data is output to a predetermined output destination.

[0038] In the (8) return process, the process executed in the OCR process is returned to the process one or more steps earlier. For example, the return is instructed by the user from the client terminal 40 during the execution of various processes such as "(4) Document discrimination, confirmation, and correction" and "(5) Read result confirmation and correction." In addition, for example, the return is instructed from the administrator's client terminal 40 in accordance with the results of the administrator's check performed between the processes of "(6) Business check" and "(7) Data output."

[0039] In the above OCR processing, the process of "(1) Business Design and Operation Verification" is executed before the processes from "(3) Data Reading" onwards are carried out, i.e., before the operation of the report system 10. Furthermore, the process of "(1) Business Design and Operation Verification" may be executed during the operation of the report system 10, when the processes from "(3) Data Reading" onwards are being carried out. As an example, the job rules created in the process of "(1) Business Design and Operation Verification" before the operation of the report system 10 can be appropriately modified according to the results of the process of "(5) Check and Correct Reading Results" during the operation of the report system 10.

[0040] (Information processing device) Next, an example of the configuration of the information processing device 20 will be described with reference to Fig. 2. Fig. 2 is a diagram showing an example of a schematic electrical configuration of the information processing device 20 according to this embodiment. The information processing device 20 may be, for example, a server computer or a general-purpose computer device such as a PC.

[0041] 2, the information processing device 20 includes a computer main body 21. The computer main body 21 includes a CPU (Central Processing Unit) 22, a RAM (Random Access Memory) 23, a ROM (Read-Only Memory) 24, a storage unit 25, and an input / output port (I / O) 26. The CPU 22, RAM 23, ROM 24, storage unit 25, and I / O 26 are connected to one another via a bus.

[0042] In addition, functional units including a communication unit 27 that enables communication with external devices, an operation input unit 28 that enables operation input by the user, and a display unit 29 that enables image display are connected to the I / O 26. These functional units are capable of mutual communication with the CPU 22 via the I / O 26.

[0043] The computer main unit 21 may be configured as a sub-controller that controls part of the operation of the information processing device 20, or may be configured as part of a main control unit that controls the overall operation of the information processing device 20. For example, integrated circuits such as LSI (Large Scale Integration) or IC (Integrated Circuit) chip sets are used for some or all of the blocks of the computer main unit 21. Individual circuits may be used for each of the above blocks, or a circuit in which some or all of the blocks are integrated may be used. The above blocks may be provided integrally, or some of the blocks may be provided separately. Furthermore, part of each of the above blocks may be provided separately. The integration of the computer main unit 21 is not limited to LSI, and a dedicated circuit or a general-purpose processor may also be used.

[0044] The storage unit 25 stores an information processing program 25P for causing the information processing device 20 to function as the information processing device of the present disclosure. The CPU 22 reads the information processing program 25P from the storage unit 25, loads it into the RAM 23, and executes processing. As a result, the information processing device 20 that has executed the information processing program 25P operates as the information processing device of the present disclosure. The information processing program 25P may be provided by a recording medium such as a CD-ROM. Specific processing by the information processing device 20 will be described later.

[0045] The storage unit 25 may be, for example, an auxiliary storage device such as a hard disk drive (HDD), a solid state drive (SSD), or a flash memory. The storage unit 25 stores an information processing program 25P for realizing the information processing according to this embodiment. The CPU 22 reads the information processing program 25P from the storage unit 25, loads it into the RAM 23, and executes the processing. As a result, the information processing device 20 that executes the information processing program 25P operates as the information processing device of the present disclosure.

[0046] The information processing program 25P may be stored in the ROM 12C. The information processing program 25P may also be pre-installed in the information processing device 20, for example. The information processing program 25P may be stored in a non-volatile storage medium, or may be realized by appropriately installing program information distributed via a network (not shown) in the information processing device 20. Examples of non-volatile storage media include a CD-ROM (Compact Disc Read Only Memory), a magneto-optical disk, a HDD, a DVD-ROM (Digital Versatile Disc Read Only Memory), a flash memory, a memory card, etc.

[0047] The storage unit 25 also stores a system program 25S for realizing each function of OCR processing in the information processing device 20. The CPU 22 reads the system program 25S from the storage unit 25, loads it into the RAM 23, and executes the OCR processing. As a result, the information processing device 20 that has executed the system program 25S operates so as to be able to execute the system functions based on the OCR processing.

[0048] In this embodiment, the information processing program 25P and the system program 25S are described as separate programs, but the information processing program 25P may be executed as a part of a process included in the system program 25S.

[0049] The storage unit 25 also stores a database 25D that includes various types of information that can be used by the information processing device 20. The information stored in the database 25D is not limited to being stored in advance in the storage unit 25. For example, the information may be stored in an external device (not shown) and may be acquired from the external device (not shown) via a communication line.

[0050] The communication unit 27 is connected to a communication network, and is configured to enable communication between the information processing device 20 and an external device. The "communication network" is a concept that includes a network that enables data exchange between devices via a communication line that is at least one of a wired connection and a wireless connection. Examples include a narrow area communication network (e.g., a local area network (LAN)) that enables data exchange at a company's base, and a wide area communication network (e.g., a wide area network (WAN)) such as the Internet that enables data exchange via public communication lines.

[0051] The operation input unit 28 is provided with devices for operation input, such as a keyboard and a mouse.

[0052] The display unit 29 may be, for example, a liquid crystal display (LCD) or an organic EL (Electro Luminescence) display. A touch panel having the functions of the operation input unit 28 may be used as the display unit 29. The operation input unit 28 and the display unit 29 receive various instructions from the user of the information processing device 20. The display unit 29 displays various information such as the results of processing executed in response to instructions received from the user and notifications regarding the processing.

[0053] FIG. 3 is a block diagram showing an example of the functional configuration of the information processing device 20 according to this embodiment. The information processing device 20 reduces the burden on the user by suggesting standardization when creating or editing business checks for a form, without the user needing to know in advance which items of multiple forms have the same business check defined (set). Note that in the following explanation, defining a business check may sometimes be referred to as setting a business check.

[0054] 3, the CPU 22 of the information processing device 20 according to this embodiment functions as the information processing device of the present disclosure by executing an information processing program 25P. The information processing device of the present disclosure includes functional units that function as a reading unit 220, a sharing unit 221, and a display control unit 228. The sharing unit 221 includes a first receiving unit 222, an acquiring unit 223, a proposing unit 224, a second receiving unit 225, and a reflecting unit 226.

[0055] The reading unit 220 is a functional unit that reads an image (image information) of a form as a paper document and also reads character string information written on the form. In this embodiment, the character string information is read by obtaining a corrected or identified reading result (character string information) using the recognition result obtained by performing character recognition on an image of a character string written on the form. Specifically, character string information is obtained at the end of execution of the OCR process in the information processing device 20 up to the process of checking and correcting the reading result (process (5) shown in FIG. 1). The reading unit 220 can also read by obtaining an image of the form and various information for identifying the form.

[0056] The standardization unit 221 is a functional unit that proposes standardization of business checks for multiple forms to which the same business check is set as a process for inspecting information written in form items. The standardization unit 221 proposes standardization for multiple forms based on information received from the user. When the standardization unit 221 receives a request for standardization from the user and some of the business checks for multiple forms are changed, the standardization unit 221 executes a process to reflect the changed content in the business checks of the unchanged common forms.

[0057] Sharing refers to sharing business checks set for multiple forms, and when at least a part of one of the shared business checks is changed, adding shared settings to the business checks so that the other business checks reflect the changed content. In addition, inspection-related processing (inspection processing) can be specified by definition information that indicates the type of inspection processing, processing content, etc.

[0058] Specifically, the first receiving unit 222 is a functional unit that receives information indicating a business check (hereinafter referred to as business check information) from a user. The business check information (hereinafter referred to as first business check information) received by the first receiving unit 222 is set in an item of a form (first form) designated by the user, and is an example of first inspection processing information that indicates a first inspection process related to the inspection of information described in the item of the first form.

[0059] The acquisition unit 223 is a functional unit that acquires business check information (hereinafter referred to as second business check information) that is different from the first business check information (first inspection processing information). The different business check information is inspection processing information that indicates an inspection processing that is common to the first inspection processing, and is an example of second inspection processing information that indicates a second inspection processing related to the inspection of information written in an item of a form (second form) that is different from the first form. The acquisition unit 223 includes a function that extracts the second business check information from the storage unit 25 (for example, database 25D).

[0060] The acquisition unit 223 can also acquire the second operation check information according to predetermined acquisition conditions. The acquisition conditions indicate, for example, conditions for extracting the second operation check information from the database 25D. The acquisition unit 223 includes a function for extracting the acquisition conditions from the storage unit 25 (for example, the database 25D).

[0061] The business check information includes information indicating what business checks can be applied to a form. For example, common business checks are often applied to similar forms. Furthermore, even different forms may have similar business checks applied to some parts. Therefore, in this embodiment, at least the common business checks are identified, and the identified business check information is acquired. Therefore, the condition indicating whether to acquire the common business check information is an example of an acquisition condition. The acquisition unit 223 includes a function to extract the acquisition conditions from the memory unit 25 (for example, database 25D).

[0062] Note that common business check information is not limited to matching business check information. For example, it includes similar business check information that has some common parts. For example, the acquisition unit 223 includes a function for determining the similarity of documents or business checks when identifying common business checks or similar business check information.

[0063] The degree of similarity (similarity) between form images can be derived, for example, through image processing. The similarity can be derived from the ratio of matching image areas between form images. For example, a user can check the similarity between form images by comparing the entire images of multiple forms. It is preferable to set the similarity of a characteristic image corresponding to the user's appearance so that it is higher than the similarity of other images. Examples of characteristic images include an image of a representative name of a form written in a font larger than other fonts, and a shape image of the form format, such as the size and arrangement of frames, and the layout pattern of character string information. Furthermore, the similarity of a name can be derived by determining the similarity of the characters indicated by the name. Character similarity can be derived from the ratio of the number of matching characters in the character string information.

[0064] Note that the similarity may be determined by predetermining a threshold for the visually similar forms described above, and determining that form images exceeding the threshold are similar. Furthermore, the similarity of operational checks may be determined by deriving the similarity between multiple pieces of operational check information. Using this similarity, it is also possible to identify common operational check information. For example, a threshold for similar operational check information may be predetermining, and operational check information exceeding the threshold may be determined to be common operational check information.

[0065] The suggestion unit 224 is a functional unit that proposes standardizing the first task check information received by the first reception unit 222 and the second task check information acquired by the acquisition unit 223. In other words, the suggestion unit 224 proposes standardizing the first task check information and the second task check information.

[0066] The second receiving unit 225 is a functional unit that receives information from the user indicating whether or not to standardize the multiple pieces of business check information (here, the first business check information and the second business check information) proposed by the proposing unit 224. In other words, the second receiving unit 225 receives from the user whether or not to standardize the first business check information and the second business check information.

[0067] The reflection unit 226 is a functional unit that executes processing to standardize the first business check information and the second business check information when the second receiving unit 225 receives information indicating the standardization of business checks. The reflection unit 226 also includes a function that, when part of the business checks of multiple forms is changed, reflects the changed content in the business checks of the unchanged forms that have been standardized. In other words, when the reflection unit 226 receives that the first business check information and the second business check information are to be standardized, and at least part of the inspection processing indicated in either the first business check information or the second business check information is changed, the reflection unit 226 reflects the changed change information in the other business check information.

[0068] The reflecting unit 226 includes a function to set information indicating standardization for business checks of multiple forms, and a function to set information indicating cancellation of standardization for any of the business checks of multiple forms. The reflecting unit 226 also includes a function to propose standardization or cancellation of standardization before reflecting the standardization or cancellation of standardization.

[0069] The display control unit 228 is a functional unit that controls the display of the above-mentioned various information on the display unit 29.

[0070] Next, the operation of the information processing device 20 according to this embodiment will be described. In this embodiment, we will explain the business check process (process (6) shown in FIG. 1) among the OCR processes executed by the information processing device 20 on image data of a form input through the input device 60. In the business check process, first, a process is performed to define definition information indicating a definition of a process related to the inspection of information written in items on the form using the read results from the form. That is, in the business check process, a process related to the inspection of information written in items on the form is defined for the business check settings included in the job rule for the job selected by the user from among job rules created in advance, and the definition is stored as business check information.

[0071] 4 is a flowchart showing an example of the flow of information processing by the information processing program 25P according to this embodiment. The information processing executes a definition of processing related to the inspection of information entered in the items of the target form, that is, a processing for defining a business check.

[0072] First, when the information processing device 20 is instructed to start the information processing program 25P, the CPU 22 executes the following steps.

[0073] In step S10, initial settings related to the business check are made, including the setting of various information such as the business check name for identifying the content of the business check.

[0074] In step S20, the reading result is obtained by obtaining character string information read from the document on which the character string is written. The character string information indicating the reading result can be obtained from the execution result at the end of the execution of the reading result confirmation and correction process (process (5) shown in FIG. 1) among the OCR processes processed by execution of the system program 25S in the information processing device 20. The process of step S20 is an example of the function of the reading unit 220 shown in FIG.

[0075] In step S30, a process for defining a business check for the target form is executed. In the process for defining a business check for the form, a process for standardizing the first business check information of the first form and the second business check information of the second form is executed. The process for standardizing the business check information will be described in detail later. The process of step S30 is an example of a process including a function executed by the standardization unit 221 shown in FIG.

[0076] In step S40, a display process is executed to display the defined task check information, and the series of processes by the information processing program 25P is terminated. Note that the display process is not limited to step S40, and each of the above-mentioned steps may display the respective information. Displaying this information is an example of displaying related information, and the related information is information related to the proposal for sharing. The process of step S40 is an example of the function of the display control unit 228 shown in FIG.

[0077] Next, information processing including processing related to standardization of a plurality of pieces of work check information will be described in detail. In the information processing device 20, when the setting of a job rule is completed and the user instructs the setting of a business rule to define the business check, the business check setting process is executed for the business check included in the job rule.

[0078] FIG. 5 is a diagram showing an example of a setting screen for a task checklist relating to task check settings.

[0079] When the task check setting process is executed, a setting screen 80 shown in FIG. 5 is displayed. The setting screen 80 is a screen that allows the user to confirm the types of task checks to be executed and the settings. The setting screen 80 displays a task checklist 800 that lists the task checks to be executed by type based on the settings. FIG. 5 shows the task checklist 800 in which required input checks, numerical calculation checks, date checks, and list checks have been added as task check types. The task checklist 800 is registered as a record that associates the priority, task check name, item name, and type for each task check to be executed. The priority is information that indicates the execution order of the task checks included in the task checklist 800, and the task check name is information that indicates the name of the task check. The item name is information that indicates the item to be verified in the task check, and the type is information that indicates the type of task check. Note that the task checklist 800 shown in FIG. 5 is not displayed during the initial task check setting process.

[0080] The setting screen 80 allows the user to operate the task checklist 800 and the task checks for each type by operating buttons. The setting screen 80 includes an add item button 802 for adding a new task check to the task checklist 800. The setting screen 80 also includes an OK button 803 for finishing setting the task checklist 800, and a cancel button 804 for canceling. For task check settings, pressing the edit button (shown as a three-dot image in FIG. 5) 801 allows the user to select a process to execute one of the editing processes, such as editing, deleting, or changing priority, for the task check settings. When the edit button 801 is pressed and the process to execute editing is selected, the screen transitions to editing processing for the task check settings that was pressed.

[0081] The following describes the case where a new transaction check is added. When the add item button 802 is pressed, a process for adding a new transaction check is executed, and settings related to the new transaction check are made.

[0082] FIG. 6 is a diagram showing an example of a setting screen for editing the settings of a new business check. When the process to add a business check is executed, a settings screen 81 is displayed. The settings screen 81 displays an input field 811 for inputting information about the business check. The input field 811 is editable. The input field 811 can be displayed in a drop-down format, for example, so that the content to be input can be selected from predetermined items.

[0083] The setting screen 81 includes an OK button 818 for finishing the task check setting, and a Cancel button 819 for canceling the setting. When the OK button 818 is pressed, the process returns to the task checklist setting process, and the task checklist setting screen 80 shown in Figure 5 is displayed. If a new task check item is created, the content of the created task check is added to the task checklist 800. On the other hand, when the Cancel button 819 is pressed, the set content is discarded and the process returns to the task checklist setting process, and the task checklist setting screen 80 shown in Figure 5 is displayed.

[0084] The process of setting the information entered in the entry field 811 is an example of the process in step S20.

[0085] The setting screen 81 includes an input field 812 below an input field 811 for inputting a conditional expression for the condition. The input field 812 is editable. In the example shown in Fig. 6, the input field 812 displays an instruction button 813 for instructing the user to set a conditional expression that can be set and input by the user.

[0086] (Commonization proposal processing) Here, if the user were to grasp in advance the items of multiple forms for which the same business checks are defined and then input the business check settings one by one, the burden on the user would increase. Therefore, when creating or editing business checks for a form, the information processing device 20 performs processing including suggestions regarding the standardization of business checks by executing a standardization proposal process, thereby supporting the user in setting business checks to reduce the burden on the user.

[0087] Specifically, when information about a business check is entered into the input field 811 shown in Fig. 6, a standardization proposal process is executed to propose standardizing the business check. The timing at which information about the business check is entered into the input field 811 is, for example, when first inspection process information newly set in an item of the first form is received from the user. Note that, here, a case will be described in which the standardization proposal process is executed by pressing the input field 811, but an instruction button may be provided on the setting screen 81 so that the standardization proposal process is executed by pressing the instruction button. Also, when the OK button 818 is pressed and the input field 811 is blank, the standardization proposal process may be executed after prompting the user to enter information into the input field 811.

[0088] FIG. 7 is a flowchart showing an example of the flow of the sharing proposal process included in the information processing of the information processing program 25P.

[0089] First, when an instruction is given to start the sharing proposal process included in the information processing program 25P in the information processing device 20, the CPU 22 executes the following steps.

[0090] In step S300, the CPU 22 receives from the user first task check information related to the inspection of information entered in the items of the first form. That is, the CPU 22 acquires task check information for the form (first form) to be created (or edited). The process of step S300 is an example of a part of the function of the common unit 221 and the function of the first receiving unit 222 shown in FIG.

[0091] In step S302, second business check information related to the inspection of information written in the items of the second form is obtained from the database. That is, the CPU 22 executes a process of obtaining, from the database 25D, business check information of a registered form (second form) that is different from the target form (first form) and has common or similar business checks. The process of step S302 is an example of part of the function of the standardization unit 221 and the function of the acquisition unit 223 shown in FIG.

[0092] In step S304, a proposal is made to share the first business check information of the first form and the second business check information of the second form. That is, the CPU 22 executes a process of outputting to the display unit 29 information proposing to share the business check information of the first form specified by the user with the business check information applied to the registered form (second form). The process of step S304 is an example of part of the function of the standardization unit 221 and the function of the proposal unit 224 shown in FIG.

[0093] In step S306, information regarding the standardization proposed in step S304 is accepted from the user. That is, the CPU 22 acquires and determines user instruction information from the operation input unit 28, thereby executing a process of accepting the user's intention regarding the proposed standardization of multiple business checks. The process of step S306 is an example of a part of the function of the common unit 221 and the function of the second receiving unit 225 shown in FIG.

[0094] In step S308, if a standardization instruction is given, the proposed plurality of pieces of business check information are standardized. That is, the CPU 22 executes a process to reflect the standardization by setting information that shares the first business check information of the first form specified by the user and the second business check information applied to the registered second form in the business check information of both. The process of step S308 is an example of a part of the function of the standardization unit 221 and the function of the reflection unit 226 shown in FIG.

[0095] Step S308 also includes executing a process to reflect changes to other operation checks in multiple pieces of common operation check information. That is, in step S308, when any one piece of common operation check information is changed, the change is reflected in the other pieces of operation check information. Specifically, when a command to share is received from the user, and at least a part of the inspection process indicated in one of the first operation check information and the second operation check information is changed, the changed change information is reflected in the other operation check information.

[0096] (First accelerated treatment) Here, proposing common task check information contributes to reducing the burden on users. For this reason, it is preferable to promote the use of common task check information. Therefore, in this embodiment, a promotion process is executed in the commonization proposal process to promote the use of task check information. First, a first promotion process will be described as an example of a promotion process that can be executed in the sharing proposal process.

[0097] 8 is a diagram showing an example of a screen displayed in the sharing proposal process as a setting screen 82. The screen 82 shown in FIG. 8 is also an example of a display screen in the first promotion process.

[0098] When the first promotion process is executed, a setting screen 82 is displayed. The setting screen 82 includes an input field 821 and an input field 822 similar to the setting screen 81. An OK button 828 and a cancel button 829 are also included.

[0099] An instruction button 824 has been added to the setting screen 82. The instruction button 824 is displayed on the setting screen 82 when common business check information exists in the database 25D when input is made into the input field 811 (FIG. 6). The instruction button 824 also displays information indicating that the common business check exists.

[0100] Specifically, database 25D is searched for business check information that is the same as or similar to the business check information that has already been entered (information entered in input field 821 shown in Figure 8), and if the search results contain one or more pieces of business check information that are the same or similar, instruction button 824 is displayed.

[0101] In the example of Fig. 8, if there is a shared business check that matches items such as the business check type, condition, and conditional expression, a button saying "Shared business check exists" is displayed. By displaying instruction button 824, it is possible to have the user confirm the existence of shared business checks. Note that even if there is no shared business check, information indicating that the business check does not exist may be displayed.

[0102] When the instruction button 824 is pressed, the process proceeds to the process of specifying the common business check information. This process is a process for encouraging the use of the common business check information when setting business checks.

[0103] FIG. 9 is a diagram showing, as a designation screen 83, an example of a screen displayed when the instruction button 824 is pressed and common task check information is designated.

[0104] The specification screen 83 includes a display area 830. The display area 830 is an area that displays the contents of the business check intended by the user. It includes a specification area that allows the user to specify the intention. In the example shown in FIG. 9, the business check name, update date, business check type, comparison conditions, and number of reference data can be specified. Furthermore, information that corresponds to the business check type and conditions from the business check information that has already been entered (information entered in the input field 811 shown in FIG. 8) is acquired and displayed in the display area 830 as the business check type and comparison conditions. The information displayed in the display area 830 can be entered and modified by the user.

[0105] Screen 83 also includes an Apply button 832. Apply button 832 is a button for instructing a search for shared task check information that matches the content of the task check intended by the user. Pressing Apply button 832 is an example of accepting the first task check information in step S300.

[0106] Furthermore, screen 83 includes a display area 834 that displays the search results. In display area 834, the business check information is displayed so that any one of the business check information displayed as the search results can be selected. Screen 83 also includes an OK button 838 as an instruction button for proceeding to the next process, and a cancel button 839 for canceling the search process and instructing to return to the previous process.

[0107] When one piece of business check information from the search results displayed in the display area 834 is selected and the OK button 838 is pressed, the selected business check information is set as the second business check information, and the shared business check information becomes available. That is, the second business check information of the shared second form is reflected in the first business check information of the first form, and a business check for the target form is defined (step S30).

[0108] As described above, the first promotion process displays information including the apply button 832 that can be pressed by the user, making it possible to present the existence of common task check information that corresponds to the task check content intended by the user. This makes it possible to promote the use of common task check information.

[0109] (Second Accelerated Treatment) Next, the second promotion process will be explained. When registered second task check information is used as the first task check information, the two will have at least some of the content identical. When one piece of the same task check information is changed, it is preferable that the change be reflected in the other pieces of task check information. In other words, it is preferable to treat the same task check information as multiple shared groups. Therefore, in this embodiment, when setting (defining) the task check information, a second promotion process is executed to encourage the sharing of task check information.

[0110] The second promotion process is executed when the setting (definition) of the business check information is completed. Specifically, the second promotion process is executed when the OK button 828 shown in Fig. 8 is pressed. In the second promotion process, it is first determined whether a similar business check that is at least partially the same as the set business check information exists in the database 25D. If the determination result is that there is no similar business check, the second promotion process is not carried out and the process moves to the next process, but if the determination result is that there is a similar business check, the second promotion process is carried out.

[0111] FIG. 10 is a diagram showing a confirmation screen 84 as an example of a screen displayed when the determination result indicates that the same task check information exists. The confirmation screen 84 includes a display area 840 for a message prompting the user to confirm whether or not to continue the business check standardization process. The confirmation screen 84 also includes an OK button 848 for instructing the user to continue the process, and a Cancel button 849 for canceling the process. When the OK button 848 is pressed by the user, the second promotion process proceeds, and when the Cancel button 849 is pressed, the information up to that point is discarded and the process ends.

[0112] This process allows the user to confirm whether to continue or cancel the sharing process when the same business check information exists, thereby confirming the user's intention regarding sharing and reducing unnecessary processing that is not intended by the user.

[0113] 11 is a diagram showing an example of a screen displayed in the second promotion process as a setting screen 85. The setting screen 85 is displayed when the second promotion process proceeds (when the OK button 848 shown in FIG. 10 is pressed).

[0114] The setting screen 85 includes display areas 850 and 852, an OK button 858, and a cancel button 859. The OK button 858 is an instruction button for proceeding to the next process, and the cancel button 859 is an instruction button for canceling the process.

[0115] Display area 850 is a display area that displays second task check information that includes the same setting values ​​as the set first task check information. Display area 850 displays the displayed second task check information that includes the same setting values ​​so that any one of them can be selected.

[0116] The setting screen 85 also includes an instruction area 852 for instructing the order of the work check information displayed in the display area 850.

[0117] The instruction area 852 allows the user to select from predefined setting values ​​the order of the business check information to be displayed in the display area 850 using a pull-down menu or the like. Examples of predefined setting values ​​include "by name," "by date," "by similar design," and "by similar rule name" as the order in which the information is sorted. "By name" indicates sorting by name of the business check information. "By date" indicates sorting by date, such as the registration date or update date of the business check information. "By similar rule name" indicates sorting by "by similar design," which sorts the form images in descending order of similarity, and sorting by job rule name.

[0118] On the other hand, display area 856 is a display area that displays a form image of the selected business check information, and the displayed form image also displays a reading frame on the form for the business check item. By displaying the reading frame, it becomes possible for the user to confirm information indicating which position (item) on the target form will be subject to business check. By displaying the form image, it becomes possible for the user to determine whether the business check information to be shared is appropriate.

[0119] As described above, the second promotion process encourages standardization of task check information when the task check information is set, thereby making it possible to promote standardization of task check information.

[0120] (Common selection process) When standardizing the above-mentioned business check information, there are cases where a user desires or does not desire the business check information to be standardized. For example, in the case of business operations that handle similar forms, promoting standardization may improve business efficiency compared to not promoting standardization. On the other hand, in the case of business operations that frequently use multiple different forms, promoting standardization may decrease business efficiency compared to not promoting standardization. Therefore, when standardizing business check information, it is preferable to reflect the user's intentions. Therefore, in this embodiment, when setting business check information, a standardization selection process is executed to select whether or not to standardize the business check information.

[0121] 12 and 13 are diagrams showing examples of setting screens for the standardization selection process when setting up task checks. Fig. 12 shows a setting screen 86A as the setting screen when introducing task check information in a job rule into the task check information to be set up. Fig. 13 shows a setting screen 86B as the setting screen when introducing standardized task check information into the task check information to be set up.

[0122] The setting screen 86A includes a display area 860A. The display area 860A is a display area that allows the user to confirm whether or not to share the task checks when introducing task check information (second task check information) in a job rule into the task check information (first task check information) being set. The display area 860A includes radio buttons that allow the user to select whether or not to share the task check information (indicated as "Share" and "Do not share" in FIG. 12). The setting screen 86A also includes an OK button 868 for instructing continuation of processing, and a cancel button 869 for canceling the processing.

[0123] If the cancel button 869 is pressed, the processing is stopped. On the other hand, if the OK button 868 is pressed by the user, processing is executed according to the instruction in the display area 860A. If "Share" is instructed, the business check information in the job rule is introduced into the business check information of the setting target, the introduced business check information of the setting target is made common, and the commonization selection processing is terminated. On the other hand, if "Do not share" is instructed, the business check information in the job rule is introduced into the business check information of the setting target, and the commonization selection processing is terminated without commonizing the introduced business check information of the setting target.

[0124] The setting screen 86B includes a display area 860B. The display area 860B is a display area that allows the user to confirm whether or not to reflect the business checks in consideration of the sharing when introducing the shared business check information (second business check information) into the business check information to be set (first business check information). In the example of Fig. 13, the messages "Install while maintaining sharing" and "Install while discarding sharing" are displayed and can be selected.

[0125] When the OK button 868 is pressed by the user, processing is performed according to the instructions in the display area 860B. If "Maintain sharing and implement" is instructed, the commonized task check information is reflected in the task check information to be set while maintaining the commonality, and the commonization selection processing is terminated. On the other hand, if "Discard sharing and implement" is instructed, processing is performed that simply reflects the commonized task check information in the task check information to be set, and the commonization selection processing is terminated without commonization.

[0126] FIG. 14 is a flowchart showing an example of the flow of the common selection process included in the information processing of the information processing program 25P.

[0127] In the information processing device 20, when the setting of the business check information is completed and an instruction to reflect the information is given, the CPU 22 starts the common selection processing process included in the information processing program 25P and executes the following steps. The instruction to reflect the information after the setting of the business check information is completed can be confirmed, for example, by obtaining information indicating that the OK button 828 shown in Figure 8 has been pressed.

[0128] The CPU 22 acquires the business check information in step S310, acquires information indicating whether or not sharing is possible in step S312, and reflects the information indicating whether or not sharing is possible in sharing in step S314, thereby terminating this processing routine.

[0129] As described above, the commonality selection process allows the user to select whether or not to commonalize the business check information when setting the business check information, thereby making it possible to reflect the user's intentions regarding the commonality of business check information.

[0130] In the above-mentioned commonalization selection process, when the source business check information (second business check information) is reflected (introduced) into the target business check information (first business check information), it is possible to propose whether or not to commonalize it.

[0131] Information about the form can be used as a criterion for proposing whether or not to share. One example of information about the form is the background image of the form. Specifically, if the similarity between the background image of the source form (second form) and the background image of the target form (first form) is higher than a threshold, the background images are considered to be similar and a suggestion to "share" is made. On the other hand, if the similarity is lower than the threshold, a suggestion to "do not share" is made. When proposing whether or not to share, it is preferable to present both form images (form images of the first form and second form). By presenting both form images (form images of the first form and second form), it is possible to present intuitive information to the user indicating whether or not they are similar.

[0132] (Commonization confirmation process) A user may change part of a piece of business check information. If the changed business check information is shared, the change information indicating the changed content is also reflected in other business check information. However, the user may or may not want the change information to be reflected in all shared business checks. Therefore, in this embodiment, when business check information is changed, a sharing confirmation process can be executed to confirm the scope of the shared business check information to be reflected.

[0133] 15 is a flowchart showing an example of the flow of the commonality confirmation processing. In the information processing device 20, when an instruction to start the commonality confirmation processing process included in the information processing program 25P is given, the CPU 22 executes the following steps. The instruction to start the commonality confirmation processing process can be, for example, obtained by obtaining information indicating that the OK button 828 shown in FIG. 8 has been pressed after the business check information has been changed.

[0134] In step S320, the CPU 22 acquires the set (defined) business check information, i.e., the changed business check information, and in the next step S322, determines whether the business check information before the change is standardized business check information. If the business check information before the change is not standardized, the result in step S322 is negative, and in step S324 the changed business check information is saved in database 25D, and the process proceeds to step S326.

[0135] In step S326, it is determined whether or not there is business check information identical to the saved business check information in database 25D. If there is no business check information, this processing routine is terminated; if there is business check information, commonality is proposed and then this processing routine is terminated. In step S326, business check information that matches the business check information before the change and the business check information after the change is searched for as the same business check information from database 25D. In other words, business check information to which change information indicating that the business check information has been changed is searched for. The search results are output (in other words, control is performed to display them on display unit 29).

[0136] When searching for the same task check information as the saved task check information, either the task check information before the change or the task check information after the change may be output as a candidate for commonality. This is because the task check information before the change may be task check information that is preferable to reflect the change information, and proposing commonality can help reduce the user's burden. On the other hand, the task check information after the change is task check information that reflects the change information, and may be task check information that is preferable to commonality, and proposing commonality can help reduce the user's burden. This allows the user to check task check information that can reflect the same change at the time the user changes the task check.

[0137] 16 is a diagram showing an example of the confirmation screen displayed in step S326 of the standardization confirmation process as confirmation screen 87A. Confirmation screen 87A includes a display area 870, an OK button 878, and a cancel button 879. Display area 870 is an area that displays the same business check information, and check boxes are added to display the business check information in the search results so that it can be selected as business check information to be standardized.

[0138] On the other hand, if the pre-change task check information has been standardized, the result in step S322 of FIG. 15 is affirmative, and the process proceeds to step S328. In step S328, a standardization permission determination process is executed to determine the reflection range of the standardized task check information. The standardization permission determination process is a process in which the user confirms job rules including the standardized task check information (i.e., task check information affected by the reflection of the change information of the changed task check information) and determines the confirmation results. Specifically, the CPU 22 outputs the job rules including the standardized task check information as the reflection range, and obtains the confirmation results of the reflection range specified by the user.

[0139] FIG. 17 is a diagram showing an example of the confirmation screen displayed in step S328 as confirmation screen 87B. Confirmation screen 87B includes a display area 872, an OK button 878, and a Cancel button 879. Display area 872 is an area for displaying the business check information that will be affected by the reflection of the change information of the changed business check information. In the example shown in FIG. 17, display area 872 displays the message "The following job rules will be affected by this change to the business check" as an example of information indicating that the change information will be reflected. When OK button 878 is pressed, information indicating that the impact is allowed is output, and when Cancel button 879 is pressed, information indicating that the impact is not allowed is output.

[0140] When the commonalization permission determination process (step S328) is completed, in step S330, it is determined whether or not to allow the change information to be reflected in the commonalized business check information based on the determination result of the commonalization permission determination process. If the result in step S330 is affirmative, in step S338, the changed business check information is saved while maintaining the commonalization, and this processing routine is terminated.

[0141] On the other hand, if the result in step S330 is negative, the process proceeds to step S332, where a sharing cancellation determination process is executed. The sharing cancellation determination process is a process in which the user confirms whether or not to cancel the sharing of the changed task check information or the job rule including the changed task check information, and the result of the confirmation is determined. Specifically, the CPU 22 outputs information related to the cancellation of sharing and acquires the confirmation result instructed by the user.

[0142] 18 is a diagram showing an example of the confirmation screen displayed in step S332 as confirmation screen 87C. Confirmation screen 87C includes a display area 874, an OK button 878, and a Cancel button 879. Display area 874 is an area for displaying a message notifying that the standardization of the changed business check information will be released and saved. When OK button 878 is pressed, information indicating that the standardization will be released is output, and when Cancel button 879 is pressed, information indicating that the standardization will not be released is output.

[0143] When the sharing cancellation determination process (step S332) is completed, it is determined whether or not to cancel the sharing of the changed business check information based on the determination result of the sharing cancellation determination process. If the result in step S334 is negative, the process proceeds to step S338, but if the result in step S334 is positive, the sharing is canceled and the changed business check information is saved in step S336, and this processing routine is terminated.

[0144] As described above, the commonization confirmation process allows the user to confirm the scope of reflection of the commonized business check information by presenting other business check information that is affected when part of the business check information is changed.

[0145] (Common additional processing) However, there are cases where a user wishes to standardize business check information that was saved without being standardized after saving it. Therefore, in this embodiment, it is possible to execute a standardization addition process that adds standardization to business check information that has already been set.

[0146] 19 is a flowchart showing an example of the flow of the sharing addition process. In the information processing device 20, when an instruction to start the sharing addition process included in the information processing program 25P is given, the CPU 22 executes the following steps. The sharing addition process can be executed after the above-mentioned process or independently.

[0147] In step S340, the CPU 22 acquires business check information that is the same as (or similar to) the business check information specified by the user. Acquisition of the shared business check information may be initiated when the user selects business check information from the list of shared business check information displayed, or when the user selects business check information on the selection screen 83 (FIG. 9).

[0148] FIG. 20 is a diagram showing, as a designation screen 88, an example of a screen displayed in the designation process of the shared task check information in step S340 of the shared task addition process.

[0149] The specification screen 88 includes an input field 880, an apply button 882, a display area 884, an OK button 888, and a cancel button 889, similar to the specification screen 83 shown in FIG.

[0150] In the specification screen 88, an instruction button 886 (shown as a three-dot image in FIG. 20) has been added to the display area 884. The instruction button 886 has been added to each of the listed common business check information, and is an instruction button for transitioning to commonality confirmation processing. Pressing the instruction button 886 displays a pop-up menu from which it is possible to select a process to execute: editing or deleting the business check information, or confirming commonality. When the instruction button 886 is pressed and confirmation of commonality is selected, the CPU 22 transitions to processing to confirm commonality for the pressed business check information.

[0151] When the CPU 22 acquires information indicating that the instruction button 886 has been pressed, it searches the database 25D for business check information that is the same as the instructed business check information, and acquires the corresponding business check information (step S340). Specifically, in the example of Fig. 20, the business check name is "tally check" and the job rule name is "invoice 101," and "confirm commonality" is instructed in the business check information.

[0152] Next, in step S342, the CPU 22 determines whether or not there is any work check information identical to the specified work check information, and if the determination is affirmative, proceeds to step S344. In step S344, similar to step S326 (FIG. 15) described above, the CPU 22 executes a standardization process, and then ends this processing routine.

[0153] On the other hand, if the determination in step S342 is negative, information indicating that no other shared work check information exists is output in step S346, and this processing routine is terminated.

[0154] 21 is a diagram showing an example of a screen on which information indicating that no other shared task check information exists is displayed as a confirmation screen 89. The confirmation screen 89 includes a display area 890 that displays information indicating that no other shared task check information exists, and an OK button 898.

[0155] Therefore, if the CPU 22 finds the same business check information in the database 25D, it displays the business check information in the search results as candidates for sharing and executes the sharing process in accordance with the user's specifications (FIG. 16). On the other hand, if the same business check information is not found, it displays information indicating that no other similar business check information exists (FIG. 18) and ends the process.

[0156] As described above, in the commonalization addition process, it is possible to commonalize business check information that has been saved without being commonalized after saving, thereby reducing the burden on the user.

[0157] As described above, according to this embodiment, it is possible to reduce the burden on the user compared to when the user understands in advance the items of multiple reports for which the same inspection process is defined and instructs them to be standardized.

[0158] Although the technology of the present disclosure has been described above using embodiments, the technical scope of the technology of the present disclosure is not limited to the scope described in the above embodiments. Various modifications or improvements can be made to the above embodiments without departing from the gist of the technology, and such modifications or improvements are also included in the technical scope of the disclosed technology.

[0159] In the above-described embodiment, the processing is performed by executing a program stored in an auxiliary storage device, but at least a part of the processing of the program may be realized by hardware. The processing flow of the program described in the above embodiment is also an example, and steps may be deleted, new steps may be added, or the processing order may be changed within the scope of the gist.

[0160] Furthermore, the processes in the above-described embodiments may be stored as a program on a storage medium such as an optical disk and distributed.

[0161] Furthermore, in the above-described embodiment, a CPU was used as an example of a general-purpose processor, but in the above-described embodiment, the term "processor" refers to a processor in a broad sense, and includes general-purpose processors (e.g., CPU: Central Processing Unit, etc.) and dedicated processors (e.g., GPU: Graphics Processing Unit, ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array, programmable logic device, etc.).

[0162] Furthermore, the operation of the processor in the above-described embodiments may not only be performed by a single processor, but may also be performed by multiple processors working together, or may be performed by multiple processors located in physically separate locations working together. [Explanation of symbols]

[0163] 10 Reporting System 20 Information processing equipment 21 Computer main body 25 Memory section 25D Database 25P Information Processing Program 25S System Program 27 Communications Department 28 Operation input section 29 Display section 220 Reading unit 221 Commonization Department 222 Reception Section 1 223 Acquisition Department 224 Proposal Department 225 Second Reception Department 226 Reflection section 228 Display control unit

Claims

1. a processor; The processor: receiving, from a user, first inspection processing information that indicates a first inspection processing related to an inspection of information described in an item of the first form, the first inspection processing information being set in the item of the first form; acquiring second inspection process information indicating a second inspection process related to an inspection of information described in an item of a second form different from the first form, the second inspection process information indicating a common inspection process with the first inspection process; It is proposed to standardize the first inspection processing information and the second inspection processing information, Accepting from a user whether or not the first inspection processing information and the second inspection processing information are to be made common; When it is accepted that the first inspection process information and the second inspection process information are to be made common, if at least a part of the inspection process indicated by one of the first inspection process information and the second inspection process information is changed, the changed change information is reflected in the other inspection process information. Information processing device.

2. The processor: When the first inspection processing information newly set in the item of the first form is received from the user, It is proposed to standardize the first inspection processing information and the second inspection processing information. The information processing device according to claim 1 .

3. The processor: When the inspection process information set in the items of the second form is received from the user as the first inspection process information to be used in the first inspection process, It is proposed to standardize the first inspection processing information and the second inspection processing information. The information processing device according to claim 1 .

4. The processor: When the inspection process information set in the items of the second form is received from the user as the first inspection process information to be used in the first inspection process, It is proposed that the first inspection processing information and the second inspection processing information are not made common. The information processing device according to claim 1 .

5. The processor: displaying related information related to a proposal as to whether or not to standardize the first inspection processing information and the second inspection processing information; 4. The information processing device according to claim 2 or 3.

6. The processor: When one of the first inspection processing information and the second inspection processing information is changed, information indicating that the change is to be reflected in the other inspection processing information is displayed. The information processing device according to any one of claims 1 to 3.

7. The processor: The cancellation of the sharing for the other inspection processing information is accepted, and when the cancellation of the sharing is accepted, the change is not reflected in the other inspection processing information. The information processing device according to claim 4 .

8. The processor: Obtaining the inspection processing information already set for the items of the third form; Accepting any one of the acquired plurality of pieces of inspection processing information as the first inspection processing information; acquiring, as the second inspection process information, inspection process information that has been set and is different from the first inspection process information, from among the acquired plurality of pieces of inspection process information; The information processing device according to any one of claims 1 to 5.

9. The processor: When an instruction indicating an inspection process common to the first inspection process and acquiring already-set inspection process information is received from a user, the already-set inspection process information is acquired, and the acquired already-set inspection process information is acquired as the second inspection process information. The information processing device according to claim 1 .

10. The processor: and displaying information including image information relating to the items of the first form set in the inspection processing information, and proposing the commonalization. The information processing device according to claim 1 .

11. An information processing program, The processor receiving, from a user, first inspection processing information that indicates a first inspection processing related to an inspection of information described in an item of the first form, the first inspection processing information being set in the item of the first form; acquiring second inspection process information indicating a second inspection process related to an inspection of information described in an item of a second form different from the first form, the second inspection process information indicating a common inspection process with the first inspection process; It is proposed to standardize the first inspection processing information and the second inspection processing information, receiving, from a user, whether or not the first inspection processing information and the second inspection processing information are to be made common; When it is accepted that the first inspection process information and the second inspection process information are to be made common, if at least a part of the inspection process indicated by one of the first inspection process information and the second inspection process information is changed, the changed change information is reflected in the other inspection process information. An information processing program that processes information.

Images