JP2010097583A - Record browsing system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To improve efficiency of confirming validity of business by leaving a record showing on the basis of what (by browsing which record) the business is determined as one function for supporting business validity confirmation in support of browsing daily business record. <P>SOLUTION: This record browsing system includes: a client terminal 110 with which a user performs various operations; a record management device 130 for managing a processing record; a business processor 120 for managing business data, such as transaction data and an approval record; a web access log management device 140 for managing a log of a device accessed by the client terminal 110; and a verification device 150 for verifying whether the user browses a necessary record in business. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a technique for supporting browsing of records in various operations, and particularly for supporting browsing of records in audits.

In recent years, in order to prove the legitimacy of business due to various legal developments and social backgrounds, companies appropriately manage records generated in business and make records available for inspection when necessary. Or need to be presented.
In addition, not only records that occurred in the business, but also a mid-term decision process (based on what was judged) from the record that occurred as input to the record that was obtained as the output of business processing An explanation is required. The company presents records regarding the decision process as needed, and verbal explanation is necessary if no records remain.

  Records include, for example, paper documents, e-mails, electronic files created on PCs (Personal Computers), operation logs of application programs, and business data managed by the business system (eg, date) , Product name, price, etc.). There are many systems that collect and manage these records individually. However, since each record is managed independently by each system, it is necessary to access each system individually when browsing the record for auditing or the like, which is very troublesome.

  In order to deal with such problems, Patent Document 1 aims to improve the efficiency of access to records for auditing, etc. by integrating the business process and the system for managing evidence such as electronic files and associating the business process with the evidence. ing.

  Further, examples of the record relating to the determination process include the addition of annotations (where the information has been confirmed) to the viewing location of the paper document. As a method for leaving such a record, it is common to add an annotation with a pointing device such as a mouse using dedicated software (see, for example, Patent Document 2).

  Further, in the work involving the collation work, it is necessary to leave a record that the worker has surely confirmed the items to be collated. For that purpose, it is necessary to appropriately show the worker the location to be verified. As a method for indicating a portion to be collated, there is a method of extracting a confirmation item defined in advance from a paper document by using a character recognition function (for example, see Patent Document 3).

JP 2007-200202 A JP 2004-151898 A JP 2008-59157 A

  Certainly, with the technique disclosed in Patent Document 1, it is possible to improve the efficiency of browsing records during an audit. However, in order to confirm the legitimacy of business, there is not only a record of purchase orders and various application forms, but also a record of what was judged (eg, a record viewed at the time of approval). It is also important that In other words, in order to prevent malicious arrangements, it is important to check not only the results of work but also the grounds for the results. Patent Document 1 does not disclose a method for leaving a record including such a basis. Moreover, although such a situation is the same also about daily work other than an audit, the method of assisting browsing of the record in such daily work is not disclosed.

  Moreover, in patent document 2, the record of what was confirmed can be left as a record of what was judged based on. However, the system is premised on a single operation, and a usage method or an annotation control method in cooperation with a business processing device is not disclosed.

  Patent Document 3 discloses a method for extracting confirmation items on a document and presenting them to an operator, but does not disclose a method such as comparison / collation with a screen of another system.

  The present invention has been made in consideration of the above-described problems of the prior art, and an object thereof is to improve the efficiency of business legitimacy confirmation.

In order to achieve the above object, when supporting the browsing of the record in the daily work, a record indicating what the work is judged based on is left as one of the functions for supporting the validity check of the work.
Aspects of the present invention for doing so include a client terminal for a user to operate various processes, a record management apparatus for managing process records, a business process apparatus for managing business data such as transaction data and approval records, A Web access log management device that manages a log of each device accessed by the client terminal; and a verification device that verifies whether a user is viewing a necessary record in business.

  The client terminal includes a record browsing support unit for browsing a record managed by the record management apparatus. The record browsing support unit acquires a monitoring rule managed by the Web access log management device, monitors Web access to the business processing device based on the monitoring rule, and records a list of records from the record management device. get. The list of records is displayed on the screen of the client terminal.

  The verification device reads a verification rule for determining whether a user is browsing a necessary record in business. Based on the verification rule, a related Web access log is acquired from the Web access log management apparatus, and a document name of a record viewed from the Web access log is acquired. It is determined from the document name of the acquired record and the verification rule whether or not the user is viewing the necessary record.

In addition, in order to achieve the above-mentioned purpose, when confirming the legitimacy of the work, an intermediate determination process is recorded by a method of adding annotations.
Aspects of the present invention for doing so include a client terminal for a user to operate various processes, a record management apparatus for managing process records, a business process apparatus for managing business data such as transaction data and approval records, A recording display device that controls display when displaying a record on a client terminal, and a capture data management device that manages a capture rule that defines timing for capturing a display screen when displaying a record on the client terminal It is.

  The record display device reads a control rule that defines the authority of a user using a client terminal, such as adding an annotation to a record. Further, the client terminal reads the capture rule from the capture data management device, captures the screen when the recording is displayed, and transmits the capture data including the image data when captured to the capture data management device. The captured data can be said to be data that records the judgment process.

In order to achieve the above object, in order to appropriately indicate to the worker the items to be collated with the worker in the collation work, the items to be collated are stored in advance and collated according to the user's operation. Highlight the item that should be.
Aspects of the present invention for doing so include a client terminal for a user to operate various processes, a record management apparatus for managing process records, a business process apparatus for managing business data such as transaction data and approval records, It is what has. The client terminal includes a collation support unit that highlights a portion to be collated on the screen displayed by the display unit.

  Each device may be implemented by software on at least one computer. Further, there may be one client terminal or two or more client terminals. Details will be described later.

  According to the present invention, it is possible to improve the efficiency of business justification.

It is the figure which showed the example of the system configuration | structure which concerns on 1st Embodiment. It is the figure which showed the structural example of the computer which implement | achieves each apparatus. It is the figure which showed the example of the recording attribute data managed with a recording management apparatus. It is the figure which showed the example of the recording access log managed by a recording management apparatus. 6 is a diagram illustrating an example of a web access log managed by a web access log management apparatus. FIG. It is the figure which showed the example of the monitoring rule managed with a Web access log management apparatus. It is the figure which showed the example of the verification rule managed with a verification apparatus. 5 is a flowchart showing processing of a record browsing support unit in a client terminal. It is the flowchart which showed the process of the recording acquisition part in a recording management apparatus. It is the flowchart which showed the process of the verification part in a verification apparatus. It is the figure which showed the example of the system configuration | structure which concerns on 2nd Embodiment. 7 is a flowchart showing processing of a record browsing support unit in a business processing device. It is the figure which showed the example of the system configuration | structure which concerns on 3rd Embodiment. It is the figure which showed the example of the annotation data managed with a recording display apparatus. FIG. 5 is a diagram illustrating an example of a control rule managed by a recording / display device and a capture rule managed by a capture data management device. It is the figure which showed the operation example of the recording display part. 5 is a flowchart showing processing of a recording display unit in a client terminal and a display control unit in a recording display device. 5 is a flowchart showing processing related to generation of a recording display screen of a display control unit in the recording display device. 6 is a flowchart showing processing related to reception of annotation operation of a recording display unit in a client terminal. 5 is a flowchart showing processing related to annotation data registration of a display control unit in a recording / display apparatus. FIG. 5 is a diagram showing an example of annotation session information managed by a recording / display device. This is a flowchart showing the processing of the screen capture unit in the client terminal. It is a figure showing an example of capture data managed by a capture data management device. It is the figure which showed the example of the system configuration | structure which concerns on 4th Embodiment. It is the figure which showed the example of the collation rule managed with a collation assistance apparatus. It is the figure which showed the example of the work screen data managed with a collation assistance apparatus. It is the figure which showed the example of the recording screen data managed with a collation assistance apparatus. It is the figure which showed the example of the collation log managed with a collation assistance apparatus. It is the figure which showed the example of the business screen control rule managed with a business screen control apparatus. It is the figure which showed the operation example of the recording display part. It is the flowchart which showed the process of the collation assistance part in a client terminal. It is the flowchart which showed the process regarding determination of the collation object screen of the collation assistance part in a client terminal. It is the flowchart which showed the process of the work screen control part in a client terminal.

  Hereinafter, the best mode (hereinafter referred to as “embodiment”) for carrying out the record browsing system of the present invention (hereinafter sometimes simply referred to as “system”) will be described with reference to the drawings as appropriate. .

<< First Embodiment >>
In the first embodiment, technical contents for executing processing necessary for recording browsing in a client terminal will be described.

≪Configuration≫
FIG. 1 is a diagram illustrating an example of a system configuration according to the first embodiment. As shown in FIG. 1, this system includes a client terminal 110, a business processing device 120, a recording management device 130, a Web access log management device 140, and a verification device 150, which are mutually connected via a network 101. Connected and configured. Each device connected to the network 101 is a computer including at least a CPU (Central Processing Unit) and a storage device, and may be referred to as a terminal, a server, or the like depending on its functions. Hereinafter, the configuration and operation of each of these devices and the devices will be described.

  In FIG. 1, the user uses a Web browser (not shown) of the client terminal 110 to perform tasks such as quotation and ordering (for example, tasks for which a predetermined workflow is established). Specifically, the user accesses the business processing apparatus 120 using a Web browser, and inputs data necessary for performing the business using input means such as a keyboard and a mouse. Further, the client terminal 110 registers a file created by the client terminal 110 itself, a file received by e-mail or the like from another apparatus, a file obtained by digitizing a paper document by a scanner or the like in the recording management apparatus 130. In addition, the client terminal 110 acquires a record that needs to be browsed in the business from the record management apparatus 130 and displays it on a screen (display means such as a display). Perform business.

  Further, the client terminal 110 realizes a processing unit such as the recording / viewing support unit 111 by the CPU executing dedicated software stored in the storage device.

  The record browsing support unit 111 analyzes the data transmitted from the client terminal 110 to the job processing device 120 and the content displayed on the Web browser, identifies the job content performed by the user, and records related to the job. Is obtained from the record management apparatus 130, thereby supporting browsing of records related to business. The record browsing support unit 111 also has a function of collecting access logs to the job processing device 120 and the record management device 130.

  The business processing device 120 includes transaction data and approval data (approval records such as who and when has been approved) input by a user (user who performs business) using the client terminal 110, and the content of the business to be performed. Certain business data 121 is stored in its own storage device. Examples of the system using the business processing device 120 include an order management system and a travel expense clearing system. Note that the business processing apparatus 120 may be an existing apparatus that is already in operation, not a newly introduced apparatus.

  The record management device 130 executes processes such as the related record search unit 131 and the record acquisition unit 132, and manages data such as the record data 133, the record attribute data 134, and the record access log 135 in its own storage device. In addition, the record management device 130 realizes processing units such as a related record search unit 131 and a record acquisition unit 132 by the CPU executing dedicated software stored in the storage device.

  In response to the search request from the client terminal 110, the related record search unit 131 returns a list of records related to the business to the client terminal 110.

  The record acquisition unit 132 returns the record data 133 to the client terminal 110 in response to an acquisition request for a specific record (record selected by the user using the client terminal 110) from the client terminal 110.

  The record data 133 is a record that is electronically managed with respect to the processing related to the business, and is a file registered (transmitted) by the client terminal 110. Data that has been subjected to a predetermined conversion process so that the business data 121 is stored in the storage device of the recording management device 130 may also be included. For convenience of explanation, the recording data may be simply abbreviated as “recording”.

  The record attribute data 134 is attribute information related to the record data 133 such as business name, document name, registrant, registration date and time, and transaction number. Details will be described with reference to FIG.

  The recording access log 135 is a log related to registration, reference, update, and deletion of the recording data 133. In addition, an access log for recording attribute information (that is, recording attribute data 134) may be recorded in the recording access log 135. Details will be described with reference to FIG.

  The web access log management device 140 manages data such as the monitoring rule 141 and the web access log 142 in its own storage device.

  The monitoring rule 141 is setting information regarding the operation of the record browsing support unit 111 of the client terminal 110. That is, the monitoring rule 141 is information that defines a range in which a user who performs recording browsing can perform recording browsing of the recording data 133 using the recording browsing support unit 111. Details will be described with reference to FIG.

  The Web access log 142 is URL (URL) acquired by the record browsing support unit 111 or data (log) transmitted from the client terminal 110 by the GET or POST method. Details will be described with reference to FIG.

  The verification device 150 executes processing such as the verification unit 151 and manages data such as the verification rule 152 in its own storage device. Further, the verification device 150 realizes a processing unit such as the verification unit 151 by the CPU executing dedicated software stored in the storage device.

  Based on the verification request from the user, the verification unit 151 acquires the recording data 133, the recording access log 135, and the web access log 142 related to the business from the recording management device 130 and the web access log management device 140, and necessary recording Verify whether is being viewed in business.

  The verification rule 152 is setting information regarding the operation of the verification unit 151. That is, the verification rule 152 is information that defines a range in which a user who audits a job can perform verification necessary for the audit using the verification unit 151. Details will be described with reference to FIG.

  There may be two or more devices connected to the network 101. Two or more of the recording management device 130, the web access log management device 140, and the verification device 150 may be combined to form one device. In FIG. 1, in order to make the explanation easy to understand, each device is configured by an independent computer, but the function sharing to the computer is appropriately optimized. If it is a small-scale system, you may comprise with the client computer as a terminal device, and the server computer which performs a predetermined | prescribed process.

  With reference to FIG. 2, a configuration example of a computer that realizes each device according to the present embodiment will be described. As shown in FIG. 2, a computer 201 is connected to a CPU 202, a main storage device 203, an auxiliary storage device 204, a network interface 205 connected to the network 101, display means such as a display, and input means such as a keyboard and a mouse I ( Hardware resources including an (Input) / O (Output) interface 206 are connected to each other via an internal bus 207. In this specification, when the main storage device 203 and the auxiliary storage device 204 are collectively referred to, they are simply referred to as “storage device”. Each device is provided with a ROM (Read Only Memory) for recording a program necessary for information processing such as a record browsing process and an audit process of the present embodiment.

  With reference to FIG. 3, an example of the recording attribute data 134 managed by the recording management apparatus 130 according to the present embodiment is shown. As shown in FIG. 3, the record attribute data 134 includes a record ID (Identification) 1341, a record hash value 1342, a registrant 1343, a registration date 1344, an IP (Internet Protocol) address 1345, a business name 1346, a document name 1347, and A field such as a transaction number 1348 is provided and constitutes attribute information of the recording data 133.

  In the recording ID 1341, identification information of the recording data 133 is registered. In the present embodiment, the recording management device 130 assigns the identification information.

  In the recording hash value 1342, the hash value of the recording data 132 is registered. In the present embodiment, for example, when the recording management device 130 stores the recording data 133, the hash value is calculated and registered in the recording hash value 1342. When the client terminal 110 or the verification device 150 accesses the specific recording data 133, it can be accessed by designating the corresponding recording ID 1341 or recording hash value 1342 from the input means, for example. In addition, the recording ID 1341 may be specified as long as it is unique within the recording management apparatus 130, but a hash value of the recording may be used as an example. In this case, since the recording ID 1341 and the recording hash value 1342 are equal, the recording hash value 1342 may not be included in the recording attribute data 134.

Subsequently, the registrant 1343 registers the identification information of the user who registered the recording (operated to store the recording data 133 in the recording management device 130).
In the registration date and time 1344, the date and time when the recording was registered (recording data 133 was stored in the recording management device 130) is registered.
In the IP address 1345, the IP address of the client terminal 110 that has registered the recording (requested that the recording management device 130 store the recording data 133) is registered.

In the business name 1346, business identification information related to the recording data 133 is registered. For example, identification information indicating business such as order receipt and travel expense settlement is registered.
In the document name 1347, document identification information of the recording data 133 is registered. For example, identification information indicating documents such as an estimate, an order, an invoice, and a receipt is registered.
In the transaction number 1348, identification information for identifying each transaction such as application or order is registered and assigned by the business processing device 120.

  Other arbitrary data may be added to the recording attribute data 134 in accordance with a system design change. In addition, data can be deleted in accordance with system design changes.

  With reference to FIG. 4, an example of the recording access log 135 managed by the recording management apparatus 130 according to the present embodiment is shown. As shown in FIG. 4, the recording access log 135 includes fields such as a user name 1351, an access date and time 1352, an IP address 1353, an access type 1354, and recording identification information 1355, and constitutes a log relating to access to the recording data 133. .

In the user name 1351, information for identifying a user who has accessed the recording data 133 is registered.
In the access date and time 1352, the date and time when the user accessed the recording data 133 using the client terminal 110 is registered.
In the IP address 1353, the IP address of the client terminal 110 that has accessed the recording data 133 is registered.

In the access type 1354, identification information indicating the type of access to the recording data 133 such as registration, reference, update, and deletion is registered.
The record identification information 1355 is information for identifying the accessed record data 133, and is a record ID or a record hash value. Desirably, a record hash value is registered in the record identification information 1355.

  With reference to FIG. 5, an example of the web access log 142 managed by the web access log management apparatus 140 according to the present embodiment is shown. As shown in FIG. 5, the Web access log 142 is provided with fields such as a user name 1421, access date and time 1422, IP address 1423, URL (Uniform Resource Locator) 1424, transmission data 1425, related URL 1426, and related transmission data 1427. The log of the Web access by the client terminal 110 is configured.

Registered in the user name 1421 is information for identifying a user who has accessed the business processing device 120 or the recording management device 130 from the client terminal 110. For example, the user name logged in to the client terminal 110 is registered.
In the access date 1422, the date and time when the business processing device 120 or the recording management device 130 is accessed is registered. In this embodiment, the date and time when the business processing apparatus 120 is accessed is registered.
In the IP address 1423, the IP address of the client terminal 110 that has accessed the business processing device 120 or the recording management device 130 is registered.

In the URL 1424, the URL of the business processing device 120 or the recording management device 130 accessed by the client terminal 110 is registered. In the present embodiment, the URL of the business processing device 120 is registered. For convenience of explanation, the “URL of the business processing device 120” means data indicating the location of a web site or web data stored in the memory of the business processing device 120. The same applies to the URL of the recording management apparatus 130.
As the transmission data 1425, a part or all of the data transmitted by the client terminal 110 to the business processing apparatus 120 or the recording management apparatus 130 by the GET or POST method is registered. The registered transmission data also includes record identification information (record ID or record hash value) of the record data 133 accessed by the client terminal 110.

  The related URL 1426 and the related transmission data 1427 are data recorded when the recording management apparatus 130 is accessed. Specifically, in the present embodiment, the URL of the recording management apparatus 130 is registered in the related URL 1426. . In the related transmission data 1427, a part or all of the data transmitted from the client terminal 110 to the business processing device 120 is registered. The data includes the recording ID of the recording data 133 or the hash value thereof, and in particular, among the recording ID of the recording data browsed by the recording browsing support unit 111 or the hash value thereof, The record ID of the user's selection or its hash value is included. In this embodiment, there are two monitoring targets for Web access: the job processing device 120 and the record management device 130, but only the record management device 130 may be used. In addition, a log may be left with the access to other devices being monitored.

  With reference to FIG. 6, an example of the monitoring rule 141 managed by the Web access log management apparatus 140 according to the present embodiment is shown. As shown in FIG. 6, the monitoring rule 141 is provided with fields such as a monitoring target URL 1411, monitoring target transmission data 1412, a decoding rule 1413, a record management device URL 1414, and a QUERY 1415, and setting information regarding the operation of the record browsing support unit 111. Constitute.

  In the monitoring target URL 1411, a URL to be monitored by the record browsing support unit 111 is registered. In FIG. 6, the URL of the business processing device 120 (http://order.hoge.com/*) is registered as the monitoring target URL, but it may be the URL of another device.

  In the monitoring target transmission data 1412, a variable name of data transmitted from the client terminal 110 to the monitoring target URL device by the GET or POST method is registered. In FIG. 6, a variable name “orderNo” (meaning an order number attached to one form of transaction called order) and a variable “process” (meaning one procedure of a work for which a workflow is established) Name is registered.

  In the decoding rule 1413, a decoding method of data transmitted from the client terminal 110 to the monitoring target URL device is registered. Used when the data to be transmitted is encoded. In FIG. 6, “orderNo” means that the decoding method “Base64” is adopted, and “process” means that the decoding method is not particularly adopted (Null). .

  Subsequently, the record management apparatus URL 1414 registers the URL of the record management apparatus in which records related to the data stored in the monitoring target URL apparatus are stored. In FIG. 6, the URL (http://record.hoge.com/) of the record management device 130 is registered.

In the QUERY 1415, a URL and data for acquiring a list of related records (acquired by the related record search unit 131) from the record management apparatus 130 indicated by the record management apparatus URL 1414 are registered. It can be said that the QUERY 1415 sets the access authority of the recording data 133 that can be viewed by the user who performs the recording browsing. In FIG. 6, variables are enclosed in “<>”, and in the example of FIG. 6, the value of the monitoring target transmission data “orderNo” is stored when the monitoring rule 141 is processed. Specific examples of the QUERY 1415 include identification information such as a transaction number (transactionNo), a business name, and a process name (process). As shown in Fig. 6, when the value "getreclist.cgi? TranactionNo = <orderNo>& process = <process>" is registered, it shows http://record.hoge.com/ <orderNo>&<process> The client terminal 110 accesses the URL. Then, the transaction number (transactionNo) and the process name (process) are displayed on the screen as the specified record data 133.
Note that the monitoring rule 141 in this embodiment requires the monitoring target URL 1411 and other attributes are arbitrary.
As another embodiment, a feature amount on a display screen may be used instead of the monitoring target transmission data 1412. The feature amount on the display screen is screen identification information other than the URL information, such as a screen title and a value of a specific HTML element.

  With reference to FIG. 7, an example of the verification rule 152 managed by the verification apparatus 150 according to the present embodiment is shown. As shown in FIG. 7, the verification rule 152 includes a business name 1521, a business processing device URL 1522, a processing name 1523, a processing identification condition 1524, a Web access log search condition 1525, a recorded access log search condition 1526, and a browsing document name 1527. A field is provided and configures setting information regarding the operation of the verification unit 151.

  In the business name 1521, a business name related to the verification rule 152 or information (symbol etc.) for identifying the business is registered. In FIG. 7, the value “order received” is registered, which means that the order receiving operation is verified.

  In the business processing device URL 1522, the URL of a device that executes a business to which the verification rule 152 is applied is registered. In FIG. 7, the value “http://order.hoge.com/*” is registered, which means that the verification rule 152 is applied to the data related to the business executed by the business processing device 120.

  In the process name 1523, information indicating a role in business such as application, approval, and approval, or information (symbol etc.) for identifying the role is registered. In FIG. 7, the value “approval” is registered, which means that the role (processing) of approval of the order receiving work is a target of verification (audit).

  The process identification condition is a method for identifying a process name. In the process identification condition 1524, a pattern is extracted from data or a URL transmitted from the client terminal 110 to the business processing apparatus 120 by a GET or POST method. The condition is registered. In FIG. 7, the value “process = approval” is registered, which means that the process name “approval” is identified.

  In the Web access log search condition 1525, a search condition for acquiring the Web access log 142 from the Web access log management apparatus 140 in the processing of the verification unit 151 is registered. In FIG. 7, the value “URL = record.hoge.com / * & related transmission data. Process = approval & related transmission data. OrderNo = <transactionNo>” is registered, and among the recording data 133 in the recording management device 130 This means that the Web access log 142 corresponding to the order number input by the user who performs the verification with the process name “approval” is to be searched.

  In the recording access log search condition 1526, a search condition for acquiring the recording access log 135 from the recording management apparatus 130 in the processing of the verification unit 151 is registered. In FIG. 7, the value “record management device URL = http: //record/hoge.com/ & transaction number = <orderNo> & access type = read” is registered, and among the recorded data 133 in the record management device 130 This means that browsing related to the order number input by the user performing verification is set as a search target.

In the browsing document name 1527, the document name of the document (record) to be browsed in the business process identified by the business name 1521 and the process name 1523 of the verification rule 152 is registered. In FIG. 7, the value “order form & quotation” is registered, which means that it is verified whether or not the order form and the quotation are being browsed in the work of approving the order receiving work.
Above, description of the structure regarding 1st Embodiment is complete | finished.

<< Process >>
Next, with reference to FIG. 8, the process of the record browsing support unit 111 in the client terminal 110 according to the present embodiment will be described. The record browsing support unit 111 starts to be executed by an operation by a user (a user who performs record browsing) or when logging in to the client terminal 110.

  In FIG. 8, the record browsing support unit 111 first performs user authentication (step S801). This user authentication is authentication for the recording management apparatus 130 and the Web access log management apparatus 140. Information necessary for authentication (eg, user ID, password) is stored in advance in the storage device of the client terminal 110, and the recording / viewing support unit 111 reads information necessary for authentication during execution of step S801, and performs authentication processing. Do. Or you may input at the time of execution of the recording browsing assistance part 111 by operation (operation from an input means) by a user. The user authentication method is not limited to the above-described method as long as the recording management device 130 and the Web access log management device 140 can identify the user operating on the client terminal 110. For example, the use of single sign-on technology is also effective. After performing user authentication, the process proceeds to step S802.

  Subsequently, the record browsing support unit 111 accesses the Web access log management device 140 and acquires the monitoring rule 141 (step S802). After acquisition, the process proceeds to step S803.

  Subsequently, the record browsing support unit 111 monitors Web access by the client terminal 110 (step S803). The record browsing support unit 111 compares the monitoring target URL of the monitoring rule 141 with the URL accessed by the client terminal 110 via the Web. After monitoring, the process proceeds to step S804.

  Subsequently, the record browsing support unit 111 determines whether the access to the monitoring target device is performed by the client terminal 110 (step S804). It is determined whether or not the value registered in the monitoring target URL 1411 of the monitoring rule 141 matches the URL that the client terminal 110 is accessing on the Web. As a result, if they match (Yes in step S804), the process proceeds to step S805. If they do not match (No in step S804), the process returns to step S803. When the URL accessed from the client terminal 110 is an IP address, an inquiry is made to the DNS (Domain Name System), the FQDN (Fully Qualified Domain Name) name is acquired, and the monitoring target URL of the monitoring rule 141 Check again whether they match. In the present embodiment, the monitoring target device is the business processing device 120, and the monitoring target device will be described as the “business processing device 120” below.

  Subsequently, the record browsing support unit 111 verifies whether the data transmitted from the client terminal 110 to the business processing device 120 matches the monitoring rule 141 (step S805). More specifically, it is verified whether the GET transmitted by the client terminal 110 to the business processing device 120 or the data transmitted by the POST method includes a variable name that matches the value of the monitoring target transmission data 1412 of the monitoring rule 141. . After verification, the process proceeds to step S806.

  Subsequently, the record browsing support unit 111 determines whether the data transmitted from the client terminal 110 to the business processing device 120 matches the monitoring rule 141 (step S806). If the transmitted data matches the monitoring rule 141 (Yes in step S806), the process proceeds to step S807, and if not (No in step S806), the process proceeds to step S812.

  Subsequently, the record browsing support unit 111 transmits the URL and transmission data of the business processing device 120 to the Web access log management device 140 (step S807). Here, the URL of the business processing device 120 is the URL of the business processing device 120 accessed by the client terminal 110, and the transmission data is the monitoring rule 141 of the data transmitted to the business processing device 120 by the client terminal 110. These are the variable name and value indicated by the monitoring target transmission data 1412. The value of the transmission data is converted based on the value of the decoding rule 1413 of the monitoring rule 141. When the decoding rule is “NULL”, the conversion process is not performed. After the transmission, the process proceeds to step S808.

  In step S806, as a process in the case where they do not match, the record browsing support unit 111 transmits the URL of the business processing device 120 to the web access log management device 140 (step S812). In particular, there is no monitoring target transmission data subject to the monitoring rule 141. As in step S807, the URL of the business processing device 120 is the URL of the business processing device 120 accessed by the client terminal 110. After the transmission, the process returns to step S803.

  Subsequently, the record browsing support unit 111 accesses the record management apparatus 130 based on the monitoring rule 141, acquires a list of records, and displays the list (step S808). More specifically, the record browsing support unit 111 can combine the value (URL) of the record management device URL 1414 of the monitoring rule 141 with data obtained by assigning a value to a variable surrounded by “<>” of the QUERY 1415. The URL is accessed to obtain a list of records. For the record list, the related record search unit 131 of the record management device 130 analyzes the data transmitted from the client terminal 110 and returns the related record list information to the client terminal 110. Thereby, it is possible to acquire and display a list of records related to the business data 121 displayed on the client terminal 110 without changing the existing business processing device 120 that is already in operation. The record management device 130 includes at least a record ID or a record hash value in the record list information. Preferably, a recorded hash value is good. After obtaining and displaying, the process proceeds to step S809.

  Subsequently, the record browsing support unit 111 waits for an instruction from the user (step S809). The user waits for an instruction on which record to view. If there is an instruction, the process proceeds to step S810.

  Subsequently, the record browsing support unit 111 acquires the record selected by the user from the record management apparatus 130 and displays it on the screen (step S810). The record acquisition unit 132 acquires the record data and returns it to the client terminal 110. Thereby, the user can view a desired record. After the display, the process proceeds to step S811.

Subsequently, the record browsing support unit 111 transmits data regarding the displayed record to the Web access log management apparatus 140 (step S811). Specifically, the URL of the displayed record, a part or all of the data transmitted by the GET or POST method from the client terminal 110 to the record management apparatus 130, and the Web access log management apparatus 140 in step S807. The transmitted URL and transmission data of the business processing device 120 are transmitted to the Web access log management device 140. When the record hash value is included in the record list information acquired in step S808, the hash value of the record displayed by the user is recorded in the Web access log 142 of the Web access log management apparatus 140. After the transmission, the process returns to step S803.
Above, description of the process of the record browsing assistance part 111 in the client terminal 110 is complete | finished.

  As another process, the record browsing support unit 111 calculates the hash value of the record data 133 displayed in step S810, and the record hash value is added to the data that the client terminal 110 transmits to the Web access log management apparatus 140 in step S811. May be included. By calculating the hash value at the client terminal 110, the reliability of the Web access log 142 can be expected to improve.

As another process, only a part of the list acquired from the record management apparatus 130 may be displayed as the list of records displayed in step S808. Specifically, first, the verification rule 152 is read from the verification device 150 when the record browsing support unit 111 executes the process. Subsequently, the URL of the business processing device 120 transmitted from the client terminal 110 to the Web access log management device 140 in step S807 matches the value of the business processing device URL 1522 of the verification rule 152, and the processing identification condition of the verification rule 152 Transmission data having the same value of 1524 is transmitted. Subsequently, in step S808, at least the data (value) of the document name 1347 is acquired from the recording attribute data 134, and only the record that matches the value of the browse document name 1527 of the verification rule 152 is displayed on the client terminal 110. By displaying in this way, recording browsing by the recording browsing support unit 111 and verification (audit) support by the verification unit 151 can be performed simultaneously, and the processing is simplified.
As another process, when one record is included in the list of records acquired in step S808, the record may be displayed on the screen without displaying the list of records. In this case, the user operation in step S809 can be omitted, and the process is simplified.

  Next, with reference to FIG. 9, the process of the recording acquisition unit 132 in the recording management apparatus 130 according to the present embodiment will be described. The recording acquisition unit 132 is started by a recording acquisition request from the client terminal 110.

  In FIG. 9, first, the record acquisition unit 132 receives record identification information from the client terminal 110 (step S901). The record identification information is, for example, a record ID and a record hash value. After receiving, the process proceeds to step S902.

  Next, the recording acquisition unit 132 acquires recording data 133 that matches the identification information of the recording, and transmits it to the client terminal 110 (step S902). After the transmission, the process proceeds to step S903.

Next, the recording acquisition unit 132 records an access log for recording (Web access log to the recording data 133 acquired by the client) in the recording access log 135 (step S903).
Above, description of the process of the record acquisition part 132 in the recording management apparatus 130 is complete | finished.

  Next, processing of the verification unit 151 in the verification device 150 according to the present embodiment will be described with reference to FIG. Execution of the verification unit 151 is started by a verification request from the client terminal 110 or the like.

  In FIG. 10, first, the verification unit 151 receives identification information to be audited (step S1001). The identification information to be audited in the present embodiment includes a business name (eg, order), a process name (eg, approval), a transaction number (eg, order number), and the like. A user such as an auditor transmits the identification information from the client terminal 110 to the verification device 150 using a Web browser, for example. After the verification unit 151 receives the data, the process proceeds to step S1002.

  Subsequently, the verification unit 151 reads the verification rule 152 that matches the identification information to be audited (step S1002). In this embodiment, the conformance determination is performed by reading the verification rule 152 in which the business name and the processing name included in the identification information to be audited match the value of the business name 1521 of the verification rule 152 and the value of the processing name 1523. . After reading, the process proceeds to step S1003.

  Subsequently, the verification unit 151 acquires the related Web access log 142 from the Web access log management device 140 based on the verification rule 152 (see FIG. 7) (step S1003). Specifically, the Web access log 142 that matches the value of the Web access log search condition 1525 of the verification rule 152 is acquired from the Web access log management device 140. In the example of the verification rule 152 in FIG. 7, the URL of the Web access log 135 is the URL of the recording management device 130 (http://record.hoge.com/*), and “process = approval” is included in the related transmission data. And “orderNo = <transactionNo>” are acquired. “<TransactionNo>” is a transaction number included in the identification information to be audited received in step S1001. After acquisition, the process proceeds to step S1004.

  Subsequently, the verification unit 151 acquires the related recording access log 135 from the recording management apparatus 130 based on the verification rule 152 (step S1004). More specifically, a record access log 135 that matches the value of the record access log search condition 1526 of the verification rule 152 is acquired from the record management apparatus 130. After acquisition, the process proceeds to step S1005.

  Subsequently, the verification unit 151 verifies the consistency of the Web access log 142 and the recording access log 135 acquired in Steps S1003 and S1004 (Step S1005). Specifically, the record access log 135 that matches the value of the IP address 1423 of the Web access log 142 acquired in step S1004 and the record identification information (record ID or record hash value) included in the transmission data 1425 is included. Confirm whether or not Then, it is confirmed whether or not the difference between the access dates (1422, 1352) is within a predetermined range. After verification, the process proceeds to step S1006.

  Subsequently, the verification unit 151 acquires the document name of the record viewed in the business from the record management apparatus 130 (step S1006). Specifically, first, each record identification information (record ID or record hash value) included in the web access log 142 and the record access log 135 acquired in steps S1003 and S1004, that is, registered in the transmission data 1425 is registered. The record identification information included in the transmitted data and the record identification information registered in the record identification information 1355 are extracted so as not to overlap. Next, an inquiry is made to the record management device 130 using each record identification information as a key, and the document name of the inquired record is acquired. To obtain the document name, the document name 1347 of the recording attribute data 134 is referred to. After the acquisition, go to step 1007.

  As another process, only the record identification information included in the Web access log 142 may be extracted, and the record management apparatus 130 may be inquired using each record identification information as a key to obtain the document name of the inquired record.

  Subsequently, the verification unit 151 verifies whether a necessary record is browsed based on the verification rule 152 (step S1007). Specifically, it is confirmed whether the document name list acquired in step S1006 includes a value (document name) registered in the browse document name 1527 of the verification rule 152. If the document name included in the browse document name 1527 is not included in the list of document names, verification fails. After verification, the process proceeds to step S1008.

  Subsequently, the verification unit 151 accesses the recording management apparatus 130 to verify the presence / absence of recording and the presence / absence of falsification (step S1008). These verification functions may be provided in the recording management apparatus 130 for verifying the presence / absence of recording and the presence / absence of falsification, or may be provided in the verification apparatus 150. When the verification device 150 includes these functions, whether or not recording is performed is determined based on whether or not recording can actually be acquired from the recording management device 130. In addition, whether or not the record is falsified is determined by acquiring the record data 133 to be verified from the record management device 130 and calculating the hash value, and by calculating the record hash value included in the record access log 135 or the Web access log 142. Do by comparing. As another process, a digital signature or a tamper-detectable time stamp may be added at the time of recording registration, and stored together with the recording data 133 and used at the time of verification. After verification, the process proceeds to step S1009.

Subsequently, the verification unit 151 displays the verification result (step S1009). As a display method, the verification results of step S1005, step S1007, and step S1008 may be displayed individually, “success” is displayed only when all the verifications are successful, and “failure” is displayed otherwise. You may do it. This verification result is displayed on the screen of the client terminal 110 used by the user who is performing verification, for example.
Above, description of the process of the verification part 151 in the verification apparatus 150 is complete | finished.

  In addition, each process of step S1005, step S1007, and step S1008 may operate | move independently, and the order of a process may be replaced.

  As another process, data may be acquired from the job processing apparatus 120 as a batch process such as daily or weekly, and the process of the verification unit 151 may be comprehensively executed for all data. In this case, in FIG. 10, identification information to be audited is acquired from the job processing apparatus 120 in step S1001. In step S1009, a list of verification results or a list of verification targets for verification failure is transmitted to an administrator or the like using mail or the like. Desirably, the verification result may be stored in the storage device of the verification device 150. According to the present embodiment, it can be used not only as a support tool when an auditor designates an audit target and confirms the legitimacy of business during an audit, but also as a daily monitoring tool.

<< Second Embodiment >>
In the second embodiment, technical contents for executing processing necessary for browsing the record in the business processing device will be described.

≪Configuration≫
FIG. 11 is a diagram illustrating an example of a system configuration according to the second embodiment. The difference from the system configuration according to the first embodiment is that the business processing device 120 executes the process of the record browsing support unit 111 instead of the client terminal 110. By executing the processing of the record browsing unit 111 in the business processing device 120, it is possible to support browsing of the record without newly installing software on the client terminal 110. The record browsing support unit 111 is implemented in the business processing device 120 as a plug-in of Web server software, for example. Hereinafter, processing of the record browsing support unit 111 in the second system configuration will be described.

<< Process >>
With reference to FIG. 12, the processing of the record browsing support unit 111 in the business processing device 120 according to the present embodiment will be described. Execution of the record browsing support unit 111 is started when the business processing apparatus 120 is activated.

  In FIG. 12, first, the record browsing support unit 111 accesses the Web access log management apparatus 140 and acquires the monitoring rule 141 (step S1201). The record browsing support unit 111 may acquire only the monitoring rule 141 in which the value of the monitoring target URL 1411 matches the URL of the business processing device 120. After acquisition, the process proceeds to step S1202.

  Subsequently, the record browsing support unit 111 monitors Web access and verifies whether the data transmitted from the client terminal 110 to the business processing device 120 matches the monitoring rule 141 (step S1202). Specifically, it is verified whether the GET transmitted by the client terminal 110 to the business processing device 120 or the data transmitted by the POST method includes a variable name that matches the value of the monitoring target transmission data 1412 of the monitoring rule 141. . After verification, the process proceeds to step S1203.

  Subsequently, the record browsing support unit 111 determines whether the data transmitted from the client terminal 110 to the business processing device 120 matches the monitoring rule 141 (step S1203). If it matches the monitoring rule 141 (Yes in step S1203), the process proceeds to step S1204. If it does not match (No in step S1203), the process proceeds to step S1206.

  Subsequently, the record browsing support unit 111 transmits the URL and transmission data of the business processing device 120 to the Web access log management device 140 (step S1204). Here, the URL of the business processing device 120 is the URL of the business processing device 120 accessed by the client terminal 110, and the transmission data is the monitoring rule 141 of the data transmitted to the business processing device 120 by the client terminal 110. These are the variable name and value indicated by the monitoring target transmission data 1412. Further, the value of this transmission data is converted based on the value of the decoding rule 1413 of the monitoring rule 141. When the decoding rule is “NULL”, the conversion process is not performed. After the transmission, the process proceeds to step S1205.

  In step S1203, as a process when they do not match, the record browsing support unit 111 transmits the URL of the business processing device 120 to the web access log management device 140 (step S1206). In particular, there is no monitoring target transmission data subject to the monitoring rule 141. As in step S1204, the URL of the business processing device 120 is the URL of the business processing device 120 accessed by the client terminal 110. After the transmission, the process returns to step S1202.

  Subsequently, the record browsing support unit 111 accesses the record management apparatus 130 based on the monitoring rule 141, acquires a list of records, and inserts a code to be displayed into response data for request data from the client terminal 110 ( Step S1205). In general, in Web access, a Web server receives request data by a GET or POST method from the client terminal 110, and displays information on a Web browser operating on the client terminal 110 such as an HTML (Hyper Text Markup Language) file. The data for this is transmitted to the client terminal 110 as response data. In step S1205, a code is inserted into the header of the HTML file. The code is executed when the Web browser of the client terminal 110 receives the response data. Further, the code displays another window, acquires a list of records based on the monitoring rule 141 from the record management apparatus 130, displays the list, and transmits a log related to the record selected by the user to the Web access log management apparatus 140. It has functions such as In addition, user authentication for accessing the recording management apparatus 130 is performed by displaying an authentication screen when the Web browser of the client terminal 110 is executed for the first time. Thus, authentication may be omitted.

<< Third Embodiment >>
In the third embodiment, technical contents for executing processing necessary for an annotation operation for recording will be described.

≪Configuration≫
FIG. 13 is a diagram illustrating an example of a system configuration according to the third embodiment. There are three differences from the system configuration according to the first embodiment and the second embodiment. The first point is that a recording display device 160 is added. The second point is that the client terminal 110 includes a recording display unit 112. The third point is that a capture data management device 170 is added.

  The recording display device 160 executes processing such as the display control unit 161 in controlling the display when the recording is displayed on the client terminal 110, and also stores data such as the annotation data 162, the control rule 163, and the annotation session information 164. It is managed by its own storage device (storage unit). Further, the recording / displaying device 160 realizes a processing unit such as a display control unit by the CPU executing dedicated software stored in the storage device.

  The display control unit 161 restricts an operation request such as adding an annotation or referring to a specific record (a record selected by a user using the client terminal 110) from the client terminal 110.

  The annotation data 162 is information regarding annotations that the user using the client terminal 110 has performed operations such as addition, confirmation, or deletion. Details will be described later with reference to FIG.

  The control rule 163 is setting information related to annotation addition, reference, essential check items, and the like. The display control unit 161 restricts operation requests such as annotation addition and reference based on the control rule 163. That is, the control rule 163 is information that defines a range in which the user can operate the annotation using the display control unit 161. Details will be described later with reference to FIG.

  The annotation session information 164 is information for identifying individual communication with the client terminal 110 by the recording / display device 160. The display control unit 161 verifies whether the data transmitted by the client terminal 110 is appropriate based on the annotation session information 164. Details will be described later with reference to FIG.

  The record display unit 112 receives data (record) from the business processing device 120 and the record display device 160 and displays the data on the screen of the client terminal 110. The recording display unit 112 is realized by a Web browser, for example.

  The screen capture unit 113 captures and images the entire screen displayed on the client terminal 110 and transmits the imaged image data to the capture data management device 170.

  The capture data management device 170 manages data such as capture rules 171 and capture data 172 in its own storage device. In addition, the capture data management device 170 realizes a processing unit included in the capture data management device 170 by the CPU executing dedicated software stored in the storage device (storage unit).

  The capture rule 171 is setting information regarding the timing at which the screen capture unit 113 captures a screen, the capture target, and the like. The screen capture unit 113 performs screen capture based on the capture rule 143. That is, the capture rule 171 is information that defines a range in which the user can capture the screen of the client terminal 110 using the screen capture unit 113. Details will be described later with reference to FIG.

  The capture data 172 is information such as image data captured by the screen capture unit 113. Details will be described later with reference to FIG.

  Referring to FIG. 14, an example of annotation data 162 managed by the recording display device 160 according to the present embodiment is shown. The annotation data 162 includes annotation registration data 16200 and annotation detail data 16210. As shown in FIG. 14, the annotation registration data 16200 includes fields such as a transaction ID 16201, a user name 16202, a registration date 16203, an IP address 16204, a business process ID 16205, a transaction number 16206, a record ID 16207, and an annotation ID list 16208. The annotation detail data 16210 includes fields such as an annotation ID 1621, page number 16212, operation date 16213, operation content 16214, related annotation ID 16215, and annotation entity 16216.

  In the transaction ID 16201, unique identification information created by the display control unit 161 using a random number generation function or the like is registered. This identification information is used to identify communication between the recording display device 160 and the client terminal 110. Further, it is also used for association with other data, for example, capture data 172.

  In the user name 16202, information for identifying a user who has performed an operation such as adding an annotation is registered.

  The registration date and time 16203 registers the date and time when the record display device 160 received the annotation data 162 from the client terminal 110. The registration date and time 16203 may be the date and time when the client terminal 110 transmits to the recording display device 160. The former is the clock time held by the recording display device 160, and the latter is the clock time held by the client terminal 110.

In the IP address 16204, the IP address of the client terminal 110 that has performed an operation such as adding an annotation is registered.
In the business process ID 16205, business identification information indicated as the business data 121 is registered.
In the transaction number 16206, identification information for identifying each transaction such as application or order is registered. The transaction number 16206 is assigned by the business processing device 120.

In the recording ID 16207, identification information of the recording data 133 for which an operation such as addition of annotation has been performed is registered. This record ID 16207 is assigned by the record management apparatus 130.
In the annotation ID list 16208, a group of added annotation detail data 16210 is registered as a list.

In the annotation ID 1621, information for uniquely identifying the annotation detail data 16210 is registered. The annotation ID 16211 is assigned by the recording display device 160 or the client terminal 110.
Registered in the page number 16212 is the page number of the recording data 133 for which an operation such as adding an annotation has been performed.

In the operation date and time 16213, the date and time when an operation such as adding an annotation was performed is registered. Alternatively, an elapsed time after the record is displayed on the client terminal 110 may be registered.
Registered in the operation content 16214 is information for identifying an operation such as addition, change, or deletion of an annotation.

  In the related annotation ID 16215, when an operation is performed on an already registered annotation, an annotation ID for specifying the registered annotation is registered. If the operation is not for a registered annotation, the value is not registered.

  In the annotation entity 16216, coordinate information to which an annotation is added (for example, coordinate values of two-dimensional coordinates on the screen of the client terminal 110), comment information, shape, color, and the like are registered.

  With reference to FIG. 15, examples of the control rule 163 and the capture rule 164 managed by the recording display device 160 according to the present embodiment will be shown.

  First, an example of the control rule 163 will be shown with reference to FIG. As shown in FIG. 15A, the control rule 163 includes a control rule ID 16300, a business processing device URL 16301, a process identification condition 16302, user role information 16303, an addition right 16304, a deletion right 16305, a reference right 16306, and a change right 16307, essential. A field such as a check item 16308 is provided, and configures setting information regarding the operation of the display control unit 161.

  In the control rule ID 16300, identification information for uniquely specifying the control rule 163 is registered. In FIG. 15A, the value “CR00031” is registered, which means that the display control unit 161 specifies the control rule by the value “CR00031”. The display control unit 161 assigns a value to the control rule ID 16300.

  In the business processing device URL 16301, the URL of the business processing device 120 that executes the business to which the control rule 163 is applied is registered. In FIG. 15A, a value “http://order.hoge.com/” is registered, and a business executed by the business processing device 120 whose URL is “http://order.hoge.com/”. This means that the control rule 163 is applied.

  The process identification condition 16302 is a method for identifying a process name (the name of a process performed in a business). The client terminal 110 transmits the process identification condition 16302 to the business processing apparatus 120 by a GET or POST method. Conditions for extracting a pattern from data or a URL are registered. In FIG. 15A, a value “process = approval” (a value meaning “approval”) is registered, and “process = approval” is included in the data transmitted by the GET or POST method. It means identifying whether or not.

  In the user role information 16303, information for identifying user role (role: job title) information is registered. In FIG. 15A, when the value “section manager” is registered and the role of the user accessing the recording display device 160 from the client terminal 110 is the section manager, this means that the control rule 163 is applied. The user role information is registered by the system administrator or the like as attribute information when the user is registered in the system.

  In the addition right 16304, identification information relating to the presence or absence of the annotation addition right is registered. In FIG. 15A, the value “◯” is registered, which means that the client terminal 110 has the authority to add annotations.

  In the deletion right 16305, identification information regarding presence / absence of annotation deletion authority is registered. In FIG. 15A, the value “x” is registered, which means that the client terminal 110 has no authority to delete the annotation.

  In the reference right 16306, identification information regarding presence / absence of the annotation reference right is registered. In FIG. 15A, the value “x” is registered, which means that the client terminal 110 does not have the authority to refer to annotations added by other users.

  In the change right 16307, identification information relating to the presence / absence of an annotation change right is registered. In FIG. 15A, the value “x” is registered, which means that the client terminal 110 has no authority to change the annotation.

  In the mandatory check item 16308, a list of items that the user must always check in the recorded data when there is an authority such as adding an annotation is registered. In FIG. 15, a value “amount, date” is registered, which means that the client terminal 110 must check “amount” and “date”. If not checked, the display control unit 161 performs processing such as returning an error.

  As another embodiment, a check item list field may be provided instead of the essential check item 16308. The check item list is a list of a pair of an item name and information for identifying whether each item is essential or optional. In this way, items other than essential items can be displayed on the client terminal 110.

  As another embodiment, an item for setting an annotation correction right (including at least one of an addition right, a deletion right, a reference right, and a change right) may be provided for each type of annotation. As types of annotation, there are, for example, flags such as marking, comment, and confirmed / approved for already registered annotation. In this way, for example, when performing a specific job, marking cannot be performed on the displayed record, but a confirmed flag can be set for an already registered annotation, etc. It is possible to control the annotations flexibly according to the content of the business.

  Next, an example of the capture rule 164 will be shown with reference to FIG. As illustrated in FIG. 15B, the capture rule 164 includes fields such as a capture rule ID 16401, screen identification information 16402, an event 16403, and a capture target 16404, and configures setting information regarding the operation of the screen capture unit 113.

  In the capture rule ID 16401, identification information for uniquely identifying the capture rule 164 is registered. In FIG. 15B, the value “CapR00223” is registered, which means that the screen capture unit 113 specifies the capture rule by the value “CapR00223”. The capture data management apparatus 170 assigns the capture rule ID 16401.

  In the screen identification information 16402, the identification information of the screen (window) to be monitored is registered. In FIG. 15B, the value “http://records.hoge.com” is registered, and the screen capture unit 113 monitors the screen opening the site “http://records.hoge.com”. It means to do. The screen identification information 16402 may be information that can uniquely identify the screen such as a window title name in addition to the URL.

  In the event 16403, event identification information that triggers screen capture is registered. In FIG. 15B, a value of “[Confirm] button click” is registered, and screen capture is triggered by an event of “[Confirm] button click” generated on the screen specified by the screen identification information 16402. (See FIG. 16). In addition, an event “annotation addition” may be used as a trigger. It will be possible to confirm at a later date whether or not the scene to be collated has been displayed at the timing of adding the annotation.

  In the capture target 16404, information for identifying a screen capture target is registered. In FIG. 15B, the value “All” is registered, which means that the screen capture unit 113 captures the entire screen displayed on the display of the client terminal 110. When only a specific screen is captured, screen identification information is designated. In cases other than capturing the entire screen, the screen identification information is the same as the format specified by the screen identification information 16402.

  Next, with reference to FIG. 21, an example of the annotation session information 164 managed by the recording display device 160 according to the present embodiment is shown. As shown in FIG. 21, the annotation session information 164 includes fields such as a transaction ID 16401, a user name 16402, an IP address 16403, and a control rule ID 16404, and configures setting information regarding the operation of the display control unit 161.

  In the transaction ID 16401, identification information for communication between the recording display device 160 and the client terminal 110, which is generated by the display control unit 161 using a random number generation function or assigning a serial number, is registered.

  In the user name 16402, information for identifying the user of the client terminal 110 who has performed an operation such as adding an annotation is registered.

  In the IP address 16403, the IP address of the client terminal 110 that has performed an operation such as adding an annotation is registered.

  Registered in the control rule ID 16404 is the control rule ID 16300 of the control rule 163 applied to the record transmitted by the display control unit 161 to the client terminal 110.

  Next, an example of capture data 172 managed by the capture data management apparatus 170 according to this embodiment will be described with reference to FIG. The capture data 172 includes image attribute data 1721 and image data 1722. As shown in FIG. 23, the image attribute data 1721 is provided with fields such as a capture data ID 17201, a transaction ID 17202, a capture date 17203, and an IP address 17204.

  In the capture data ID 17201, information for uniquely identifying the image data 1722 is registered. This capture data ID 17201 is assigned by the capture data management apparatus 170.

  In the transaction ID 17202, identification information of communication between the recording display device 160 and the client terminal 110, which is generated by the display control unit 161 using a random number generation function or assigning a serial number, is registered.

  In the capture date and time 17203, the date and time when the capture data management device 170 received the image data captured by the screen capture unit 113 is registered.

  In the IP address 17204, the IP address of the client terminal 110 that transmitted the image data is registered.

  Next, with reference to FIG. 16, an operation example of the recording display unit 112 in the client terminal 110 according to the present embodiment will be described. Execution of the recording display unit 112 is started by a user operation or the like. The recording display unit 112 may be, for example, a commonly used web browser. In FIG. 16, a display as a display device of the client terminal 110 is drawn, and a web browser screen is displayed on the display.

  The record display unit 112 accesses the business processing device 120 by a user operation and displays data (business) received from the business processing device 120. In FIG. 16, it is assumed that the business processing device 120 is a travel expense settlement system, and the application content is displayed as a business processing apparatus screen 1601 on the approval screen for travel expense settlement.

  At this time, the record browsing support unit 111 acquires a list of related records from the record management apparatus 130 via the display control unit 161, and the record display unit 112 displays the list on the screen. The user selects a record from the list, and the record display unit 112 displays the record via the display control unit 161. In FIG. 16, a receipt related to the application details for the travel expense adjustment on the left side is displayed on the right side as a record display screen 1602.

  In the processing flow of the record browsing support unit shown in FIG. 8, in step S808 and step S810, a list of records and a record selected by the user are acquired from the record management device 130. In the third embodiment, the recording management device 130 is replaced with the recording display device 160. That is, in step S808 and step S810, the record browsing support unit 111 of the client terminal 110 accesses the record display device 160 to obtain a list of records or a record selected by the user. Similarly, in FIG. 12, the recording management device 130 in step S1205 is replaced with the recording display device 160.

  Subsequently, the user confirms that the application content and the content of the record (receipt) are consistent. The user attaches a mark (annotation) to the confirmed place on the record (receipt) displayed on the screen by using a pointing device such as a mouse or a touch panel. The mark may have any shape that can be recognized by surrounding a corresponding portion with a rectangle, drawing a line, or confirming. After marking the confirmed location, the user inserts a comment as an annotation or specifies the item name of the marked location as necessary. The specified content is a value registered in the annotation entity 16216. In FIG. 16, the user encloses the confirmed place with a rectangle 1603 and then selects “date” as a (required) check item.

  After marking all the confirmed locations, the user presses a “Confirm” button 1604 and presses an “Approve” button 1605 on the business processing device screen 1601. Thereby, the approval work is completed. When the “confirm” button 1604 is pressed, the entire screen is captured (see FIG. 15B).

  As another embodiment, a button or link for acquiring a list of related records may be added on the screen created by the business processing apparatus 120 without using the record browsing support unit 111. In this case, it is necessary to change the setting information of the business processing device 121, but it is not necessary to incorporate the record browsing support unit 111 into the client terminal 110 or the business processing device 120, and the processing is simplified.

<< Process >>
Next, processing of the recording display unit 112 in the client terminal 110 and the display control unit 161 in the recording display device 160 according to the present embodiment will be described with reference to FIG.

In FIG. 17, first, the display control unit 161 is in a waiting state for receiving the reference source information and the record identification information from the record display unit 112 (step S1701). After the reference source information and the record identification information are received, the process proceeds to step S1702. Here, the reference source information is information for identifying the content of the business, and the URL of the screen of the business processing device 120 displayed by the client terminal 110 (location of business data processed by the business processing device 120) Identification information of a screen such as information), parameter information of GET and POST transmitted from the client terminal 110 to the business processing device 120 to display the screen, and identification of processing (for example, approval) performed in business Data including information.
The record identification information is a record ID for uniquely specifying a record stored in the record management device 130 (a search condition for specifying one record) or a search condition for specifying a plurality of records. As a search condition, one of values included in the recording attribute data 134 or a combination thereof is designated. In addition, when the session is already established between the client terminal 110 and the recording display device 160, for example, when the authentication has been completed in advance, the reference source information is referred to in the session information when the session is established. By managing the original information together, the client terminal 110 does not need to transmit the reference source information to the recording / displaying device 160 again. Instead, the client terminal 110 may transmit information for identifying a session such as a session ID to the recording / displaying device 160, and the recording / displaying device 160 may specify the reference source information based on the identification information of the session.

  Subsequently, the display control unit 161 generates a user authentication screen (step S1702). After the generated screen (eg, HTML data) is transmitted to the client terminal 110, the process proceeds to step S1703.

  Subsequently, the record display unit 112 transmits authentication information such as a user name and a password input by the user from the input device of the client terminal 110 to the record display device 160 (step S1703). In addition to the user inputting the authentication information, setting information in which the user name and password are stored in advance is prepared in the client terminal 110, and the recording display unit 112 reads the setting information and records the user name and password in the recording display device. 160 may be transmitted. If the authentication has already been completed, the record display unit 112 holds the authentication session information at the stage when the first authentication is completed, and the stored session information is recorded and displayed after the second authentication. The authentication process may be omitted by transmitting to the device 160. In addition, the use of single sign-on technology is also effective. After transmitting the authentication information, the process proceeds to step S1704.

  Subsequently, the display control unit 161 performs user authentication using the authentication information transmitted by the client terminal 110 (step S1704). After the user authentication is successful, the process proceeds to step S1705.

  Subsequently, the display control unit 161 generates a record display screen based on the user name, reference source information, and record identification information (step S1705). Details will be described later with reference to FIG. After the recording display screen is generated and transmitted to the client terminal 110, the process proceeds to step S1706.

  Subsequently, the recording display unit 112 receives an annotation display on the screen and an annotation operation by a user operation (step S1706). Annotation operations include corrections such as addition, deletion, reference, and change. These operations are limited based on the control rule 160 when the record display screen is generated in step S1705. When these operations are performed, annotation operation data indicating the operations is generated. The annotation operation data includes at least fields having the same function as the transaction ID 16201, the record ID 16207, and the annotation ID list 16208 (see FIG. 14), and values corresponding to the operations are registered. Further, when the mandatory check item 16308 is specified in the control rule 160 (some value is registered), the annotation operation data cannot be transmitted to the recording display device 160 until all the mandatory check items are checked. Details of the processing related to the reception of the annotation operation and the essential check items will be described later with reference to FIG. After the annotation operation data is transmitted to the recording display device 160, the process proceeds to step S1707.

Subsequently, the display control unit 161 receives the annotation operation data transmitted from the client terminal 110, creates annotation data 162 from the annotation operation data, and registers it. Details will be described later with reference to FIG.
Above, the outline | summary description of the process of the recording display part 112 in the client terminal 110 and the display control part 161 in the recording display apparatus 160 is complete | finished.

  As another embodiment, after the reference source information is received in step S1701, the Web access log management device 140 is accessed and the client terminal 110 is accessing the business processing device 120 identified by the reference source information. You may check whether or not. By performing such processing, it can be confirmed that the client terminal 120 is accessing the business processing device 120 identified by the reference source information, and it can be verified that the reference source information is not improperly designated.

  Next, details of the processing of step S1705, step S1706, and step S1707 will be described with reference to FIG. 18, FIG. 19, and FIG.

  First, with reference to FIG. 18, the process (step S1705) relating to the generation of the recording display screen of the display control unit 161 in the recording display device 160 according to the present embodiment will be described.

  In FIG. 18, first, the display control unit 161 uses the record identification information acquired in step S1701 to access the record management device 130 and search for a corresponding record (step S1801). After obtaining the search result from the record management apparatus 130, the process proceeds to step S1802.

  Subsequently, the display control unit 161 determines whether there are one or more records included in the search result (step S1802). If there is one record included in the search result (Yes in step S1802), the process proceeds to step S1803. If there are two or more records (No in step S1802), the process proceeds to step S1806. If there are no search results, the process is interrupted and an error is returned (not shown).

  Subsequently, the display control unit 161 reads the control rule 163 that matches the reference source information acquired in step S1701 (step S1803). Specifically, the reference source information includes the business processing device URL 16301 and the processing identification condition 16302 in the control rule 163, and the control rule 163 that matches these is read. If the recording / display device 160 or another device that manages the authentication information manages the user role information together with the user name and password, the user role information is acquired from the user name acquired in step S1703, and In addition to the reference source information, a control rule 163 having the same user role information may be read. After reading the control rule 163, the process proceeds to step S1804.

  Subsequently, the display control unit 161 generates annotation session information 164 (step S1804). After the annotation session information 164 is generated, the process proceeds to step S1805.

Subsequently, the display control unit 161 generates a recording display screen including an annotation control code based on the control rule 163 (step S1805). Specifically, the display control unit 161 refers to the addition right 16304, the deletion right 16305, the reference right 16306, the change right 16307, and the essential check item 16308 of the control rule 163, and records only the functions to which the right is given. Incorporate into the display screen. Further, when the mandatory check item 16308 is designated, control is performed so that the “confirm” button 1604 in FIG. 16 cannot be pressed unless annotations are added to all items designated by the mandatory check item 16308. Incorporate the code to be used in the recording display screen. For example, a table of required check items and check flags (value 0) is prepared, and when the user checks the required check items, the check flags of the corresponding required check items are rewritten to 1, and all the check flags are rewritten to 1. This can be realized by activating the “confirm” button.
Regarding the annotation addition right, deletion right, reference right, and change right, for example, a code (annotation control code) for realizing these controls is prepared in advance for each of the add right, deletion right, and change right. If necessary, this can be realized by inserting the code into the recording display screen. The reference right can be dealt with by not transmitting unnecessary data to the client terminal 110. In addition, the transaction ID is included in the record display screen or URL. The transaction ID is used when the client terminal 110 transmits annotation operation data to the recording display device 160. After the recording display screen is transmitted to the client terminal 110, the process proceeds to step S1706 in FIG.

Next, a process when there are two or more search results in the process of step S1802 will be described. The display control unit 161 transmits a list of search results to the client terminal 110 (step S1806). After transmitting the list of search results, the display control unit 161 waits for a specific record to be designated, and waits for reception of record identification information as shown in S1701. If the recording is designated, the process proceeds from S1802 to S1803.
Above, description of the process (step S1705) regarding the production | generation of the recording display screen of the display control part 161 in the recording display apparatus 160 is complete | finished.

  Next, with reference to FIG. 19, in the case where the mandatory check item 16308 is specified in the control rule 163 in the processing (step S1706) regarding the reception of the annotation operation of the recording display unit 112 in the client terminal 110 according to the present embodiment. The process will be described.

  In FIG. 19, first, the record display unit 112 displays a record from data received from the record display device 160 (at least including data for a record display screen) (step S1901). After displaying the record, the process proceeds to step S1902.

  Subsequently, the recording display unit 112 enters a state of waiting for an operation from the user (step S1902). In the meantime, the user confirms the description items necessary for approving the business, for example. Referring to FIG. 16, the items described in the receipt displayed on the record display screen 1602 are confirmed in order to approve the travel expense settlement. After waiting for an operation from the user, the process proceeds to step S1903.

  Subsequently, the user adds an annotation using a pointing device such as a mouse (user operation: step S1903). After adding the annotation, the process proceeds to step S1904.

  Subsequently, the record display unit 112 displays a list of check items (step S1904). In step S1805, the display control unit 161 embeds a necessary code in the recording display screen, and displays a list of essential check items triggered by the user's annotation addition. After displaying the list of check items, the process proceeds to step S1905.

  Subsequently, the user selects an item related to the annotation added by the user in step S1903 from the check item list displayed by the recording display unit 112 (user operation: step S1905). After the user selects a check item, the process proceeds to step S1906.

  Subsequently, the recording display unit 112 acquires the check item selected by the user (step S1906). The record display unit 112 manages which of the essential check items are checked at the present time. After obtaining the check item, the process proceeds to step S1907.

  Subsequently, the record display unit 112 checks whether or not the user has checked all the essential check items (step S1907). If all are checked (Yes in step S1907), the process proceeds to step S1908. If not (No in step S1907), the process returns to step S1902.

  Subsequently, the record display unit 112 activates (presses) the confirmation button (step S1908). In the example of FIG. 16, in the stage of step S1901, the “confirm” button 1604 is in a state where it cannot be pressed, which means that it can be pressed in step S1908. Note that there is no necessity for a button, and it is sufficient that the state does not change to the state of step S1910 described later. After activating the confirmation button, the process proceeds to step S1909.

  Subsequently, the user presses a confirmation button (user operation: step S1909). When the confirmation button is pressed, corresponding annotation operation data is generated. Note that the annotation operation data may be generated, for example, when all the essential check items are checked. After the confirmation button is pressed, the process proceeds to step S1910.

Subsequently, the record display unit 112 transmits annotation operation data together with the transaction ID to the record display device 160 (step S1910).
If the essential check item 16308 is not specified in the control rule 163, step S1907 is omitted, and the confirmation button is activated in step S1908 from, for example, the time when the record is displayed (S1901).
The description of the processing when the essential check item 16308 is specified in the control rule 163 in the processing related to the reception of the annotation operation of the recording display unit 112 in the client terminal 110 is finished.

  Next, with reference to FIG. 20, processing related to registration of annotation data of the display control unit 161 in the recording display device 110 according to the present embodiment will be described.

  In FIG. 20, first, the display control unit 161 receives annotation operation data including a transaction ID from the client terminal 110 (step S2001). After the annotation operation data is received, the process proceeds to step S2002.

  Subsequently, the display control unit 161 verifies whether the annotation operation data is appropriate (step S2002). Specifically, first, the annotation session information 164 specified by the transaction ID transmitted by the client terminal 110 is read. The display control unit 161 reads the control rule 163 specified by the control rule ID 16404 of the annotation session information 164. Subsequently, the display control unit 161 checks whether the control rule 163 and the received annotation operation data are consistent. For example, when the addition right 16304 is “x”, it is confirmed that the added annotation has not been added. If the mandatory check item 16308 is designated, it is confirmed whether all the essential check items are checked. If there is a mismatch as a result of the annotation operation data verification, an error is returned to the client terminal 110 (not shown). Otherwise, the process proceeds to step S2003.

  Subsequently, the display control unit 161 creates (generates) annotation data 162 from the annotation operation data transmitted by the client terminal 110 and registers it in the storage device (step S2003). Specifically, it is created by setting fields other than the fields set in the annotation operation data among the fields set in the annotation data 162 and registering corresponding values (see FIG. 14). The value to be registered can be acquired from the client terminal 110. After registration, the process proceeds to step S2004.

Subsequently, the display control unit 161 deletes the annotation session information 164.
Above, description about the process regarding the registration of the annotation data of the display control part 161 in the recording display apparatus 110 is complete | finished.

  Next, processing of the screen capture unit 113 in the client terminal 110 according to the present embodiment will be described with reference to FIG. Execution of the screen capture unit 113 is started upon user operation or login to the client terminal 110.

  In FIG. 22, first, the screen capture unit 113 reads the capture rule 172 from the capture data management apparatus 170 (step S2201). After reading the capture rule 172, the process proceeds to step S2202.

  Subsequently, the screen capture unit 113 monitors an event on the client terminal 110 based on the capture rule 172 (step S2202). In the case of the example of the capture rule 164 in FIG. 15B, it is monitored that the “Confirm” button is clicked on the Web browser that opens the Web site “http://records.hoge.com”. After the designated event occurs, the process proceeds to step S2203.

  Subsequently, the screen capture unit 113 performs screen capture of the portion specified by the capture target 16404 of the capture rule 172 (step S2203). In the example of the capture rule 164 in FIG. 15B, the capture target 16404 is “All”, and the entire screen displayed on the display of the client terminal 110 is captured. By capturing the entire screen, it is possible to confirm at a later date whether or not the screen of the business processing device 120 that is the target of collation confirmation was displayed when the annotation was added. After screen capture is complete, the process advances to step S2204.

Subsequently, the screen capture unit 113 transmits the screen-captured image data to the capture data management device 170 (step S2204). At the time of transmission, image attribute data including the capture rule ID 16401 of the applied capture rule 171 and the transaction ID included in the recording display screen is also transmitted to the capture data management apparatus 170. Association with the annotation data 162 is performed by the transaction ID. The capture data management device 170 associates the image data and image attribute data transmitted by the client terminal 110 and stores them in the storage device as capture data 172.
Above, description of the process of the screen capture part 113 in the client terminal 110 is complete | finished.

<< Fourth Embodiment >>
In the fourth embodiment, the technical contents for executing the processing necessary for supporting the collation work between the business screen and the record will be described.

≪Configuration≫
FIG. 24 is a diagram illustrating an example of a system configuration according to the fourth embodiment. There are three differences from the system configuration according to the first and second embodiments. The first point is that the client terminal 110 includes a recording display unit 116, a collation support unit 114, and a business screen control unit 115. The second point is that a verification support device 180 is added. The third point is that a business screen control device 190 is added.

  The collation support device 180 manages data including the collation rule 181, the work screen data 182, the recording screen data 183, and the collation log 184 with its own storage device. Moreover, the collation support apparatus 180 implement | achieves the process part with which the collation support apparatus 180 is provided, when CPU runs the exclusive software stored in the memory | storage device.

  The collation rule 181 is setting information regarding the operation of the collation support unit 114 of the client terminal 110. That is, the collation rule 181 is information that defines the range of business screens and recording screens for which the collation support unit 114 performs collation support (for example, how business screens or recording screens are collated and supported). It is. Here, the “business screen” refers to a screen on which the recording display unit 116 displays business data 121 managed by the business processing device 120. Similarly, the “recording screen” refers to a screen on which the recording display unit 116 displays the recording data 133 managed by the recording management device 130. The business screen and the recording screen defined by the collation rule 181 may be referred to as “collation target business screen” and “collation target recording screen”, respectively. Further, the collation target business screen and the collation target recording screen may be collectively referred to as a “collation target screen”. Details will be described with reference to FIG.

  The business screen data 182 is information related to the collation location included in the business screen. Here, the “collation location” is a location where the collation operator confirms the consistency of the description contents on the business screen or the recording screen. For example, in the travel expense recognizing approval operation, the approver (verification worker) collates an item in which the amount of travel expense approval screen is described with an item in which the amount of receipt is described. In this case, “travel amount approval screen amount” and “receipt amount” are the collation points. When the contents described in different verification locations represent the same content, these verification locations belong to the same verification item. For example, the collation location where the amount is written in the travel expense approval screen and the collation location where the amount is written in the receipt belong to the same collation item “amount”. In the collation work, the collation worker uses a collation location on the business screen (business screen collation location (business screen collation location)) and a collation location on the recording screen (record collation location (record screen collation location) belonging to the same collation item. Check if the contents written in)) match. Details will be described with reference to FIG.

  The recording screen data 183 is information on a collation location included in the recording screen. Details will be described with reference to FIG.

  The verification log 184 is data transmitted from the client terminal 110 when the user performs a verification operation. Details will be described with reference to FIG.

  The business screen control device 190 stores and manages business screen control rules 191 and the like in its own storage device. Details will be described with reference to FIG. In addition, the business screen control apparatus 190 realizes a processing unit included in the business screen control apparatus 190 when the CPU executes dedicated software stored in the storage device.

  The recording display unit 116 receives the business data 121 or the recording data 133 from the business processing device 120 or the recording management device 130, and displays the data on the screen of the client terminal 110. The recording display unit 116 is realized by a Web browser, for example.

  The business screen control rule 191 is setting information regarding the operation of the business screen control unit 115. That is, the business screen control rule 191 is information that defines a range in which the business screen control unit 115 can change the content displayed by the recording display unit 116. Details will be described with reference to FIG.

  The collation support unit 114 assists the collation operation between the business screen and the recording screen by the worker, and based on the collation rule 181 acquired from the collation support device 180, the business display screen and the recording screen on which the recording display unit 116 is a collation target. It is determined whether or not a set of is displayed. Further, based on the operation from the approver's input means, the collation location belonging to the same collation item on the business screen and the recording screen is highlighted. In addition, the verification log 184 is created and transmitted to the verification support apparatus 180.

  The business screen control unit 115 changes the content displayed by the recording display unit 116 based on the business screen control rule 191 acquired from the business screen control device 190. For example, the button attribute is changed so that the “approval button” cannot be pressed. The reason for making such a change is mainly to guide the approver to an appropriate approval action, in other words, to prevent the approver from performing an inappropriate operation as the approval action.

With reference to FIG. 25, an example of a matching rule 181 managed by the matching support apparatus 180 according to the present embodiment is shown.
As shown in FIG. 25, the collation rule 181 includes fields such as a collation rule ID 1811, a collation target business screen URL 1812, a recording management device URL 1913, and a business screen format ID 1814.

  In the matching rule ID 1811, identification information for uniquely identifying the matching rule 181 is registered.

  In the collation target business screen URL 1812, the URL of the collation target business screen that is a target for which the collation support unit 114 performs collation support is registered.

  In the record management apparatus URL 1813, the URL of the record management apparatus in which the record data 133 to be verified is stored is registered. When the URL of the recording management apparatus is registered, information processing is performed so that the recording data 133 to be supported for collation is determined. However, the URL of the verification target recording screen may be registered or additionally registered instead of the URL of the recording management device.

  In the business screen format ID 1814, identification information for uniquely identifying the business screen format data 18200 associated with the business screen to be verified is registered.

  Further, as another field, the feature amount of the collation target business screen and the feature amount of the collation target recording screen may be added. Here, the feature amount is screen identification information other than URL information, and is, for example, a screen title, a value of a specific HTML element, or the like. As a result, even when the URL is the same and the displayed screen contents are different, the verification target business screen and the verification target recording screen can be identified.

With reference to FIG. 26, an example of business screen data 182 managed by the collation support apparatus 180 according to the present embodiment is shown.
The business screen data 182 includes business screen format data 18200 and business screen collation location data 18210. The business screen data 182 defines the type of collation location included in a specific business screen, the position on the screen, and the like.

  The business screen format data 18200 is provided with fields such as a business screen format ID 18201 and a business screen collation location ID list 18202.

  The business screen collation location data 18210 is provided with folds such as a business screen collation location ID 18211, identification information 18212, and a collation item ID 18213. The business screen collation location data 18210 defines the collation location included in the business screen based on these data.

  In the business screen format ID 18201, identification information for uniquely identifying the business screen format data 18200 is registered.

  In the business screen collation location ID list 18202, business screen location data 18210 defining a correspondence between a collation location existing on the business screen and a collation location existing on the recording screen is registered as a list.

  In the business screen collation location ID 18211, identification information for uniquely identifying the business screen collation location data 18210 is registered.

  In the identification information 18212, information for identifying a collation location on the business screen is registered. As the identification information 18212, for example, there is a value of an ID attribute of an HTML element. When the collation support unit 114 acquires the event that occurred in the recording display unit 116, the identification information indicating the HTML element in which the event has occurred is compared with the identification information 18212 included in the business screen collation location data 18210, and the event has occurred. It is determined whether or not the HTML element is a collation location.

  In the verification item ID 18213, identification information (identifier) for uniquely identifying the verification item to which the business screen verification part belongs is registered. The collation item ID 18213 has a role of associating a specific business screen collation location with a specific record collation location. Similar to the business screen collation location, the collation item ID 18313 is registered in the record collation location, and the collation location having the same collation item ID becomes the corresponding collation location. The collation support unit 114 instructs the worker on the location to be browsed by highlighting the corresponding collation locations.

With reference to FIG. 27, an example of the recording screen data 183 managed by the collation support apparatus 180 according to the present embodiment is shown.
As shown in FIG. 27, the recording screen data 183 includes recording format data 18300 and recording collation location data 18310.

  The recording format data 18300 includes fields such as a recording format ID 18301 and a recording collation location ID list 18302.

  The record collation location data 18310 is provided with fields such as a record collation location ID 18311, identification information 18312, and a collation item ID 18313. The record collation location data 18310 defines a collation location included in the recording screen based on these data.

  In the recording format ID 18301, identification information for uniquely specifying the recording format data 18300 is registered. The recording format data 18300, together with the recording verification location data 18310, defines the correspondence between the location of the verification location existing on the recording screen and the business screen verification location. The recording format ID 18301 is managed by adding a field to the recording attribute data 134 managed by the recording management apparatus 130. The record display unit 116 displays the record format ID 18301 together with the record data 133, and the collation support unit 114 extracts the record format ID 18301 displayed by the record display unit 116, and the record format data identified by the record format ID 18301. By referring to 18300 and the record verification location data 18310, the location of the verification location existing in the record data 133 is associated with the business screen verification location.

  In the record collation location ID list 18302, the record collation location data 18310 defining the location of the collation location existing in the recording data 133 and the correspondence between the collation location and the business screen collation location is registered as a list.

  In the record collation location ID 18311, identification information for uniquely identifying the record collation location data 18310 is registered.

  In the identification information 18312, information for identifying the collation location on the recording screen is registered. As the identification information 18312, for example, coordinate information representing a recording range including a recording collation location is registered.

  In the collation item ID 18313, identification information (identifier) that uniquely identifies the collation item to which the record collation part belongs is registered.

  The business screen verification location data 18210 and the recorded verification location data 18310 may be collectively referred to as “verification location data”.

With reference to FIG. 28, an example of a verification log 184 managed by the verification support apparatus 180 according to the present embodiment is shown.
As shown in FIG. 28, the collation log 184 includes fields such as transaction ID 1841, user name 1842, collation date and time 1843, IP address 1844, collation rule ID 1845, business screen URL 1846, record ID 1847, and collation item ID 1848, and client terminal. The log of the collation work by 110 is constructed.

  In the transaction ID 1841, unique identification information created by the verification support apparatus 180 using a random number generation function or the like is registered. This transaction ID 1841 is generated by the verification support apparatus 180.

  In the user name 1842, information for identifying the user of the client who has performed an operation such as confirmation of a collation item is registered.

  In the collation date and time 1843, the date and time when the user confirmed the collation item at the client terminal 110 is registered.

  In the IP address 1844, the IP address of the client terminal 110 that has performed an operation such as confirmation of a collation item is registered.

  In the matching rule ID 1845, the matching rule ID 1811 of the matching rule 181 to which the business screen on which the matching work has been performed belongs is registered.

In the business screen URL 1846, the URL of the business screen on which the collation work has been performed is registered.
In the record ID 1847, identification information for uniquely identifying the record for which the collation work has been performed is registered.
In the collation item ID 1848, identification information for uniquely identifying the collation item for which the user performed the confirmation operation during the collation work is registered.

  Next, with reference to FIG. 30, an operation example of the recording display unit 116 in the client terminal 110 according to the present embodiment will be described. Note that FIG. 29 will be referred to later when the business screen control rule 191 is described.

  Execution of the recording display unit 116 is started by a user operation or the like. The recording display unit 116 may be, for example, a commonly used web browser. In FIG. 30, a display as a display device of the client terminal 110 is drawn, and a screen of a Web browser is displayed on the display.

  The record display unit 116 accesses the business processing device 120 by a user operation and displays data (business) received from the business processing device 120. In FIG. 30, it is assumed that the business processing device 120 is a travel expense settlement system, and the application content is displayed as the business processing apparatus screen 3001 on the approval screen for travel expense settlement.

  At this time, the record browsing support unit 111 acquires a list of related records from the record management apparatus 130, and the record display unit 116 displays the list on the screen. The user selects a record from the list, and the record display unit 116 displays the record. In FIG. 30, a receipt related to the application details for the travel expense adjustment on the left side is displayed as a record display screen 3002 on the right side.

  Subsequently, the user confirms that the application content and the content of the record (receipt) are consistent. The user uses a pointing device (input means) such as a mouse and performs an action such as a click at the collation point. For example, a click is performed in the vicinity of a portion written as transportation expenses on the travel expense adjustment screen (business processing device screen 3001). The collation support unit 114 acquires information about the place where the user clicked, and obtains a corresponding collation location on another screen (record display screen 3002) based on the collation rule 181.

  Next, the collation support unit 114 highlights the obtained place and the clicked place. The highlighting is performed by surrounding the corresponding part with a rectangle, drawing a line, changing the background color, or the like. In FIG. 30, a rectangle 3003 on the business processing device screen 3001 and a rectangle 3004 on the recording display screen 3002 are highlighted. After the collation support unit 114 highlights the collation part, the user visually confirms that the contents of the two collated parts highlighted are consistent. After confirmation, the user clicks on the collation location on the record display screen 3002. When the user clicks, the collation support unit 114 displays a confirmation button 3005. The user presses a confirmation button 3005. The user performs the same operation on the other items, confirms all the items to be collated, and then presses the work end button 3006. Thereafter, an approval action is realized by pressing an approval button 3007.

  With reference to FIG. 31, the process of the collation support unit 114 in the client terminal 110 according to the present embodiment will be described together with the process of the user operation.

  In FIG. 31, the collation support unit 114 first accesses the collation support device 180 and acquires the collation rule 181 (step S3101). After acquisition, the process proceeds to step S3102.

  Subsequently, the collation support unit 114 determines the collation target screen (step S3102). The collation support unit 114 determines whether the recording display unit 116 displays both the business screen and the recording screen to be collated. Details of the determination process will be described with reference to FIG. After determining the collation target screen, the process proceeds to step S3103. The recording screen may be displayed manually by the user, or may be displayed based on the monitoring rule 141 by the recording browsing support unit 111.

  Subsequently, the collation support unit 114 waits for an instruction from the user (step S3103). Wait for the user to click on the verification target screen. Here, the collation target screen refers to the business screen or the recording screen that the collation support unit 114 determines as the collation target screen in step S3102. After waiting for an instruction from the user, the process proceeds to step S3104.

  Subsequently, the user clicks on the collation target screen (step S3104). Here, it is assumed that items on the screen to be confirmed by the user in the collation work are determined in advance. The user searches for the item on the screen and clicks on the screen where the item is displayed. After clicking, the process proceeds to step S3105.

  Subsequently, the verification support unit 114 verifies whether the location clicked by the user is included in the verification location (step S3105). Specifically, the collation support unit 114 first identifies the identification information of the place where the user clicked the collation target screen (the same kind of information as 18212 and 1831 and is included in the data of the collation target screen, for example). To get. Next, the collation support unit 114 compares the identification information of the clicked portion with the identification information (18212, 18312) included in the business screen collation portion data 18210 or the record collation portion data 18310 of the collation rule 181 to determine whether they match. Verify whether or not. After verification, the process proceeds to step S3106.

  Subsequently, the collation support unit 114 determines whether the location clicked by the user is included in the collation location (step S3106). As a result, if it is included in the collation location (Yes in step S3106), the process proceeds to step S3107. If not included (No in step S3106), the process returns to step S3103.

  Subsequently, the collation support unit 114 acquires the business screen data 182 or the recording screen data 183 corresponding to the collation target screen, and the collation location (corresponding collation location on the other screen corresponding to the collation location on the screen clicked by the user. ) Is determined (step S3107).

  Specific processing flow, taking as an example the case where the screen clicked by the user is a business screen (corresponding to the business processing device screen 3001 in FIG. 30) and the collation target is a recording screen (corresponding to the recording display screen 3002 in FIG. 30). Will be explained. First, the collation support unit 114 acquires the business screen data 182 corresponding to the clicked business screen, and sets the collation item ID 18213 of the part clicked by the user (for example, an area indicated by reference numeral 3003 in FIG. 30) as the business screen data 182. Is determined from the business screen collation location data 18210. Next, the collation support unit 114 acquires the recording screen data 183 corresponding to the recording screen to be collated, and specifies the recording collation location data 18310 including the collation item ID 18313 whose value matches the collation item ID 18213. The identification information 18312 included in the specified record collation location data 18310 is determined as a collation location (for example, an area indicated by reference numeral 3004 in FIG. 30) having the same collation item ID as the collation location clicked by the user. When the screen clicked by the user is a recording screen, the collation location on the business screen corresponding to the collation location clicked is determined. After the determination, go to step S3108.

  Subsequently, the collation support unit 114 refers to the collation rule 181 and highlights the collation location clicked by the user and the corresponding collation location (step S3108). The position on the screen to be highlighted is determined based on the identification information (18212, 18312) included in the business screen data 182 and the recording screen data 183. Examples of highlighting include displaying a frame line surrounding the collation location (eg, reference numerals 3003 and 3004 (FIG. 30)), changing the background color of the collation location, and the like. These can be realized by the collation support unit 114 creating an HTML element representing a frame line or a translucent rectangle and inserting it at the position of the collation location or changing the attribute of the HTML element. This makes it possible to highlight the collation location (either one or both) on the business screen or the recording screen without changing the existing business processing device 120 that is already in operation. After highlighting, the process proceeds to step S3109.

  Subsequently, the collation support unit 114 waits for an instruction from the user (step S3109). The collation support unit 114 waits for the user to click on the highlighted record collation part. During this time, the user visually confirms the highlighted one or a plurality of matching points. After waiting for an instruction from the user, the process proceeds to step S3110.

  Subsequently, the user clicks a collation location on the collation target recording screen (step S3110). After clicking, the process proceeds to step S3111.

  Subsequently, the collation support unit 114 displays a confirmation menu on the collation target recording screen (step S3111). The confirmation menu is specifically a confirmation button 3005 (see FIG. 30). After the display, the process proceeds to step S3112.

  Subsequently, the verification support unit 114 waits for an instruction from the user (step S3112). The collation support unit 114 waits for the user to select a confirmation menu. After waiting for an instruction from the user, the process proceeds to step S3113.

  Subsequently, the user selects the confirmation menu displayed by the collation support unit 114 (step S3113). After selection, the process proceeds to step S3114.

  Subsequently, the collation support unit 114 creates a collation log 184 (step S3114). The verification log 184 includes data shown in FIG. The created verification log 184 is held inside the verification support unit 114 (storage device). The collation support unit 114 determines that the collation portion where the user has selected the confirmation menu is the confirmed collation portion. After creating the collation log 184 for the confirmed collation location, the process proceeds to step S3115.

  Subsequently, the user determines whether or not all items (collation points) on the screen to be confirmed specified in advance have been confirmed (step S3115). As a result, if there are still items to be confirmed (No in step S3115), the process returns to step S3104, another item is clicked, and the same processing as described above is performed. If all items to be confirmed have been confirmed (Yes in step S3115), the process proceeds to step S3116.

  Subsequently, the user ends the work (step S3116). Specifically, for example, the work is finished by pressing a work end button 3006 (see FIG. 30) included in the recording screen. After finishing the work, the process proceeds to step S3117.

Subsequently, the collation support unit 114 transmits all of the collation logs 184 created by the end of the work to the collation support device 180 (step S3117). For example, it is executed by pressing an approval button 3007 (FIG. 30) included in the business screen.
Above, description of the process of the collation assistance part 114 is complete | finished.

With reference to FIG. 32, the process of determining the collation target screen will be described. As described above, this process is executed in the process of S3102.
In FIG. 32, the collation support unit 114 first monitors the recording display unit 116, and when the recording display unit 116 detects that a new screen is displayed, acquires the URL of the access destination (step S3201). After acquisition, the process proceeds to step S3202.

  Subsequently, the collation support unit 114 verifies whether the acquired URL is included in the collation rule 181 (step S3202). Specifically, it is verified whether the collation target business screen URL 1812 or the record management apparatus URL 1813 registered in the collation rule 181 matches the acquired URL. The verification of matching may be partial matching. After verification, the process proceeds to step S3203.

  Subsequently, the collation support unit 114 determines whether the acquired URL is included in the collation rule 181 (step S3203). As a result, if it is included (Yes in step S3203), the process proceeds to step S3204. If not included (No in step S3203), the process returns to step S3201.

  Subsequently, the collation support unit 114 determines that the screen displayed by the recording display unit 116 that is determined that the acquired URL is included in the collation rule 181 is a collation target screen (step S3204). Specifically, the collation rule ID 1811 of the collation rule 181 including the identification information of the window displaying the screen and the acquired URL (1812, 1813) is acquired and held inside the collation support unit 114. Such information is referred to as “display screen data”. After the determination, go to step S3205.

  Subsequently, the verification support apparatus 180 extracts a transaction number from the screen determined as the verification target screen (step S3205). This is realized, for example, by the following method. The collation support unit 114 stores in advance the identification information of the HTML element including the transaction number for each collation target screen. When extracting the transaction number, the collation support unit 114 acquires identification information corresponding to the screen to be extracted from the identification information of the HTML element stored in advance. Next, the HTML element designated by the acquired identification information is determined from the HTML elements of the screen to be extracted. Next, a transaction number is extracted by acquiring a value included in the determined HTML element. The collation support unit 114 adds the extracted transaction number to the display screen data acquired in step S3204. Each time the collation support unit 114 determines a collation target screen, the collation support unit 114 acquires the corresponding display screen data and holds it internally. The collation support unit 114 discards the corresponding display screen data when the screen is not displayed, for example, when the user closes the window. After extracting the transaction number, the process proceeds to step S3206.

  Subsequently, the collation support unit 114 verifies whether the collation target screen corresponding to the screen determined as the collation target screen in step S3204 has already been displayed by the recording display unit 116 (step S3206). Specifically, the display screen data held by the verification support unit 114 is searched for data having the same transaction number. As a result, when corresponding display screen data is found, the collation support unit 114 determines that the corresponding collation target screen is displayed. After verification, the process proceeds to step S3207.

  Subsequently, the collation support unit 114 displays whether or not the collation target screen corresponding to the screen determined to be the collation target screen in step S3204 has already been displayed by the recording display unit 116, that is, the result of the verification in S3206. Whether it is displayed or not displayed is determined (step S3207). As a result, if it is displayed (Yes in step S3207), the process proceeds to step S3208. If not displayed (No in step S3207), the process returns to step S3201.

Subsequently, the collation support unit 114 associates the two screens, the screen determined as the collation target screen in step S3204 and the screen determined as the collation target screen corresponding in step S3207 (step S3208). Specifically, two display screen data held inside are associated with each other and stored.
This is the end of the description of the verification target screen determination process.

With reference to FIG. 29, an example of the business screen control rule 191 managed by the business screen control apparatus 190 according to the present embodiment is shown.
As shown in FIG. 29, the business screen control rule 191 includes fields such as a control target business screen URL 1911, a control end event 1912, control target screen element identification information 1913, a control target screen element attribute 1914, and an after-change attribute value 1915. . This manages information such as which screen element of which business screen is to be controlled, when control starts and ends, and how attributes of screen elements are changed during control. .

  In the control target business screen URL 1911, the URL of the business screen to be controlled is registered. The business screen control unit 115 compares the URL of the screen displayed by the recording display unit 116 with the control target business screen URL 1911 to determine the business screen to be controlled.

  In the control end event 1912, identification information of an event (change end condition) that occurs in the client terminal 110 that triggers the control end is registered. For example, the control ends when the user presses the work end button.

  In the control target screen element identification information 1913, identification information of a screen element (changed part) to be controlled is registered. As the identification information, for example, an ID attribute value of an HTML element is registered.

  In the control target screen element attribute 1914, the attribute name of the screen element to be controlled is registered. The attribute name registered here is changed by the business screen control unit 115 that acquired the control start event.

  Registered in the post-change attribute value 1915 is a value after the attribute value (post-change value) of the screen element to be controlled is changed by the business screen control unit 115.

  As a specific example of the business screen control rule, let us consider a case where a control is realized in which the approval button on the business screen cannot be pressed until the user presses the work end button on the recording screen. In this case, the control end event 1912 registers information for identifying the event of the user pressing the work end button, and the control target screen element identification information 1913 registers information for identifying the approval button of the business screen. In the control target screen element identification information 1913, a “disabled attribute” that is an attribute for invalidating the button press is registered, and “on” indicating that the “disabled attribute” is valid in the changed attribute value 1915. Can be registered. By setting the business screen control rule in this way, it is possible to prevent the situation where the approver completes the approval procedure without confirming anything.

  Normally, the work end button is pressed after all the verification points (the verification points on the work screen and the recording screen) have been confirmed. In order to make this effective, check all the verification points. Control may be performed so that the work end button cannot be pressed until the input is made, that is, until the input is made.

  Moreover, you may add the feature-value of a control object screen as another field. The feature amount of the control target screen is screen identification information other than the URL information, such as a screen title and a value of a specific HTML element. This makes it possible to identify the control target business screen even when the displayed URL contents are the same with different URLs.

  Further, as another field, a control start event that is identification information of an event (change start condition) that defines the timing of starting control may be added. In this case, after the record display unit 116 displays the control target screen, control is started at the timing when the business screen control unit 115 acquires the event registered in the control start event. When no control start event is added, the control start event is preferably that the client terminal 110 has accessed the business processing device 120, for example.

  With reference to FIG. 33, processing of the business screen control unit 115 in the client terminal 110 will be described.

  In FIG. 33, the business screen control unit 115 first accesses the business screen control device 190 and acquires the business screen control rule 191 (step S3301). After acquisition, the process proceeds to step S3302. Note that the access to the business screen control apparatus 190 may be performed when the business processing apparatus 120 is accessed, for example. The condition setting for accessing the business screen control apparatus 190 is basically a design matter of those skilled in the art.

  Subsequently, the business screen control unit 115 monitors the recording display unit 116 and compares whether the screen displayed by the Web browser that realizes the recording display unit 116 matches the control target business screen (step S3302). Specifically, first, when the recording display unit 116 displays a new screen (corresponding to the business processing device screen 3001 in FIG. 30), the business screen control unit 115 acquires the URL of the screen. Next, the business screen control unit 115 compares the acquired URL with the control target business screen URL 1911 registered in the business screen control rule 191. After the comparison, the process proceeds to step S3303.

  Subsequently, the business screen control unit 115 determines whether or not both screens match as a result of the comparison (step S3303). The business screen control unit 115 acquires the identification information of the window displaying the control target business screen, thereby identifying the window displaying another screen and the window displaying the control target business screen. Can do. If they match as a result of the comparison (Yes in step S3303), the business screen control unit 115 determines that the screen is a control target business screen, and the process advances to step S3304. On the other hand, if they do not match as a result of the comparison (No in step S3303), the business screen control unit 115 determines that the screen is not a control target business screen, returns to step S3302, and displays another screen displayed by the Web browser Execute the same process for.

  Subsequently, the business screen control unit 115 changes the displayed control target business screen based on the business screen control rule 191 (step S3304). Specifically, the business screen control unit 115 acquires the HTML code of the control target business screen, and searches the HTML element specified by the control target screen element identification information 1913 from the code. As a result of the search, the control target screen element attribute of the corresponding HTML element is changed to a value determined by the changed attribute value 1915. For example, in FIG. 30, an approval button 3007 is displayed to indicate that the input of the pointing device is not accepted. Here, the business screen control unit 115 acquires the attribute value before the change from the control target business screen and stores it in the business screen control unit 115. After the change, go to step S3305.

  Subsequently, the business screen control unit 115 monitors the client terminal 110 and acquires an event that occurs in the client terminal 110. Next, it is compared whether or not the acquired event matches the control end event 1912 of the business screen control rule 191 (step S3305). After the comparison, the process proceeds to step S3306.

  Subsequently, the business screen control unit 115 determines the result of the comparison, that is, whether or not the acquired event matches the control end event 1912 of the business screen control rule 191 (step S3306). As a result, if they match (Yes in step S3306), the process proceeds to step S3307. If they do not match (No in step S3306), the process returns to step S3305, and the same processing is executed for other events occurring in the client terminal 110.

Subsequently, the business screen control unit 115 restores the change of the control target business screen based on the business screen control rule 191 (step S3307). Specifically, the attribute value before change acquired in step S3304 is referred to, and the attribute value of the HTML element changed in step S3304 is returned to the attribute value before change. As a specific example, “off” indicating that the “disabled attribute” is invalid may be registered in the value of the changed attribute value 1915, thereby enabling the approval button (eg, reference numeral 3007 in FIG. 30). , Make it possible to accept the approval operation by the approver.
Above, description of the process of the work screen control unit 115 is finished.

≪Summary≫
As described above, since a list of records related to the business is displayed only by setting the rules (the monitoring rule 141 and the verification rule 152, the control rule 163 and the capture rule 171), a new apparatus is not introduced. As one of the functions that support the verification of the legitimacy of business in order to control the introduction cost and support the browsing of the record in daily work, what is the business based on (what record is viewed and what part is confirmed Since the record indicating whether it has been determined is left, it is possible to improve the efficiency of browsing the record in daily work. Further, in the case of approval or the like, it is possible to improve the efficiency of checking the validity of the audit by leaving a log indicating which record the user has viewed.

  Further, since the items to be noted for approval are highlighted on the business screen and the recording screen only by setting the verification rule 181, the verification work is facilitated, and only the business screen control rule is set. Thus, a screen display that can prevent an inappropriate operation by the approver (eg, approving without confirming an item to be noticed) is performed. Therefore, it is not necessary to introduce a new device, the introduction cost can be suppressed, and the validity of business can be confirmed efficiently.

≪Others≫
In addition, although the said form is the best thing for implementing this invention, the implementation form is not limited to this. Therefore, various modifications can be made to the implementation form without departing from the scope of the present invention.

  For example, specific configurations such as hardware, software, and flowcharts can be changed as appropriate without departing from the spirit of the present invention.

DESCRIPTION OF SYMBOLS 101 Network 110 Client terminal 111 Record browsing support part 112 Record display part 113 Screen capture part 114 Collation support part 115 Business screen control part 116 Record display part 120 Business processing apparatus 121 Business data 130 Record management apparatus 131 Related record search part 132 Record acquisition Unit 133 Recorded data 134 Recorded attribute data 135 Recorded access log 140 Web access log management device 141 Monitoring rule 142 Web access log 150 Verification device 151 Verification unit 152 Verification rule 160 Record display device 161 Display control unit 162 Annotation data 163 Control rule 164 Annotation Session information 170 Capture data management device 171 Capture rule 172 Capture data 180 Verification support device 181 Verification data Le 182 business screen data 183 recorded screen data 184 matching log 190 business screen control device 191 business screen control rules

Claims (25)

A client terminal having input means for receiving user data and display means for displaying the results of various processes;
A business processing device that executes business-related processing and manages business data that is the content of the business;
A record management device for managing record data recorded for processing related to the business;
A web access log management device for managing a web access log of a device to which the client terminal has made web access;
In a record viewing system that is connected via a network,
The client terminal includes a recording browsing support unit that browses the recording data managed by the recording management device,
The Web access log management device manages a monitoring rule including location information of a device to be monitored, which defines the browsing of the recording data by the recording browsing support unit.
The record browsing support unit
Obtaining the monitoring rule from the web access log management device, and monitoring web access to the business processing device by the client terminal based on the monitoring rule;
In accordance with the monitoring rule, from the record management device, obtain a list of recorded data recorded about the processing related to the business executed by the business processing device,
A list of recorded data is displayed on the display means of the client terminal. The record browsing support unit
Location information of the business processing device accessed by the client terminal via Web;
A part or all of data to be monitored according to the monitoring rule, which is transmitted from the client terminal to the business processing device;
To the Web access log management device,
The web access log management device
Identification information of a user who operates the client terminal that has accessed the business processing device via Web;
Date and time when the client terminal accessed the business processing device via Web,
Location information of the client terminal;
Location information of the business processing device,
A part or all of the data to be monitored transmitted to the business processing device;
The recording / viewing system according to claim 1, wherein the Web access log including: is stored. The record browsing support unit
Of the recorded data that has been displayed, when the user selects the recording means selected by the input means from the recording management device, when displaying the selected recording data on the display means,
Location information of the record management device;
Identification information of the displayed recorded data;
To the Web access log management device,
The web access log management device adds a web access log to the web access log.
Location information of the record management device;
Identification information of the displayed recorded data;
The record browsing system according to claim 2, wherein:   4. The record browsing system according to claim 3, wherein the identification information of the displayed recording data is a hash value of the identification information of the recording data. The monitoring rule is
Location information of business processing devices to be monitored,
A variable name of data to be monitored, which the client terminal sends to the business processing device;
Location information of the record management device capable of obtaining a list of recording data related to the business when the client terminal transmits a variable name of the data and a value substituted for the variable name to the business processing device; ,
A method of obtaining a list of the recording data from the recording management device;
The record browsing system according to any one of claims 1 to 4, further comprising: The record management device comprises:
From the client terminal, the hash value is received as identification information of the displayed recording data,
Transmitting the recording data specified by the identification information to the client terminal;
The recording management device records a log of web access to the recording data.
Identification information of a user when the client terminal makes a web access to the record management device;
Date and time when the client terminal accessed the recording management apparatus via the Web,
Location information of the client terminal that has made web access to the record management device;
Web access type for the recorded data;
Identification information of the recorded data;
The record browsing system according to claim 4, wherein the record viewing log is stored as a record access log. A verification device for verifying whether or not the recording data necessary for the user to confirm the legitimacy of the business is being browsed in the business is connected to the network,
The verification device includes:
Manage the verification rules stipulating the verification;
A verification unit that acquires the Web access log from the Web access log management device based on the verification rule and determines whether or not the user is browsing the recorded data from the Web access log;
The validation rule is
Location information of the business processing device to be verified; and
A search condition for obtaining the web access log from the web access log management device;
The name of the document to be viewed for the recorded data that the user needs to view,
The record browsing system according to claim 4, comprising: The verification rule further includes a search condition for acquiring the recording access log from the recording management device,
The verification unit
Obtaining the record access log from the record management device based on the verification rule;
It is confirmed whether or not information that matches the location information of the client terminal and the identification information of the displayed recording data included in the Web access log is included in the recording access log. Whether the difference between the date and time when the client terminal accessed the business processing device and the date and time when the client terminal accessed the recording management device and included in the recording access log is within a predetermined range The record browsing system according to claim 7, wherein: The verification rule further includes a search condition for acquiring the recording access log from the recording management device,
When the identification information of the recorded data displayed on the display means included in the Web access log is a hash value,
The verification unit
Obtaining the record access log from the record management device based on the verification rule;
Comparing the hash value of the identification information of the recorded data displayed on the display means included in the Web access log with the hash value of the identification information of the displayed recording data included in the recording access log. The record browsing system according to claim 7. A client terminal having input means for receiving user data and display means for displaying the results of various processes;
A business processing device that executes business-related processing and manages business data that is the content of the business;
A record management device for managing record data recorded for processing related to the business;
A web access log management device for managing a web access log of a device to which the client terminal has made web access;
In a record viewing system that is connected via a network,
The business processing device includes a record browsing support unit for browsing the recorded data managed by the record management device,
The Web access log management device manages a monitoring rule including location information of a device to be monitored, which defines the browsing of the recording data by the recording browsing support unit.
The record browsing support unit
Obtaining the monitoring rule from the web access log management device, and monitoring web access to the business processing device by the client terminal based on the monitoring rule;
In accordance with the monitoring rule, from the record management device, obtain a list of recorded data recorded about the processing related to the business executed by the business processing device,
In order to display the list of recorded data on the display means of the client terminal, a code for displaying the list of recorded data is inserted into data transmitted to the client terminal. A client terminal having input means for receiving user data and display means for displaying the results of various processes;
A business processing device that executes business-related processing and manages business data that is the content of the business;
A record management device for managing record data recorded for processing related to the business;
A record display device for controlling display of the record data by the client terminal;
In a record viewing system that is connected via a network,
The client terminal includes a recording display unit that accesses the recording display device and displays the recording data on the display means.
The record display device
Annotation data indicating the content of the annotation for the recorded data;
Regarding the control of the annotation, a control rule defined for each content of the business,
A storage unit for storing
Based on the control rule, a display control unit that performs annotation control according to the content of the work;
A record browsing system characterized by comprising: The display control unit of the recording / display apparatus includes:
From the record display unit of the client terminal, receiving reference source information including identification information of the content of the business, and record identification information including a search condition for specifying recording data recorded for processing related to the business,
Obtaining record data satisfying the search condition from the record management device;
Read the control rule specified by the reference source information,
The record browsing system according to claim 11, wherein a record display screen including an annotation control code that defines the correction authority of the annotation for the user is generated based on the read control rule. The record display device
Storing and managing annotation session information for identifying communication between the client terminal and the recording display device;
When generating the recording display screen, the display control unit includes a transaction ID for identifying communication between the client terminal and the recording display device, information for identifying the client terminal, and the recording data in the communication. The record browsing system according to claim 12, wherein the annotation session information having a control rule ID for identifying the applied control rule is generated. The control rule is
Location information of the business processing device,
Identification information of the content of the business transmitted from the client terminal to the business processing device;
Information identifying a user of the client terminal;
Information for identifying the correction authority of the annotation for the user;
The record browsing system according to claim 13, further comprising: The control rule further includes:
The record browsing system according to claim 14, wherein the user has an essential check item that must be checked in the record data. The recording display unit of the client terminal is
Displaying the recording display screen received from the recording display device on the display means;
When an annotation is added from the input means, the essential check items are displayed on the display means,
When all of the required check items are selected from the input means, the annotation that has been added is indicated, and annotation operation data including a transaction ID that identifies communication between the client terminal and the recording display device is generated. The record browsing system according to claim 15, wherein the generated annotation operation data is transmitted to the record display device. The display control unit of the recording / display apparatus includes:
Receiving the annotation operation data from the client terminal;
Reading the annotation session information specified by the transaction ID included in the annotation operation data;
Reading the control rule specified by the control rule ID included in the read annotation session information;
Verify whether or not consistency between the read control rule and the received annotation operation data is consistent with the correction authority of the annotation,
The record browsing system according to claim 16, wherein if the consistency is obtained, the annotation data is generated based on the annotation operation data. Capture that stores and manages image data when capturing a part or all of the screen displayed on the display means of the client terminal and a capture rule that defines at least a timing for capturing a part or all of the screen A data management device is connected to the network;
The client terminal includes a screen capture unit that captures a part or all of the screen displayed on the display unit,
The screen capture unit
Read the capture rule from the capture data management device,
Capturing part or all of the screen displayed on the display means at the timing specified in the read capture rule,
The record browsing system according to claim 11, wherein the image data is generated by the capture, and the generated image data is transmitted to the capture data management device. The capture rule is
The identification information of the screen to be monitored,
Identification information of an event that occurs on the screen specified by the identification information of the screen, which triggers the screen capture,
Information identifying the capture target;
The record browsing system according to claim 18, comprising: A client terminal having input means for receiving user data and display means for displaying the results of various processes;
A business processing device that executes business-related processing and manages business data that is the content of the business;
A record management device for managing record data recorded for processing related to the business;
A collation support device for controlling display related to collation between the business data and the recorded data in the client terminal;
In a record viewing system that is connected via a network,
The client terminal is
A recording display unit for accessing the business processing device and displaying the business data on the display unit as a business screen, and accessing the recording management device and displaying the recording data on the display unit as a recording screen;
A collation support unit that supports collation work of the collation for the business screen and the recording screen displayed on the display means,
The collation support device
A storage unit that stores identification information of the business data to be collated and identification information of the recording data, and stores a collation rule that defines at least a business screen to be collated and a recording screen;
The collation support unit acquires the collation rule from the collation support device, monitors access to the business processing device and the record management device by the client terminal based on the collation rule, and the record display unit It is determined whether or not a set of the business screen and the recording screen to be collated is displayed. The matching rule includes
Business screen data defining one or more business screen verification locations that the user should check on the business screen in the verification operation;
Recording screen data defining one or more recording screen verification locations that the user should check on the recording screen in the verification operation,
The business screen data and the recording screen data include an identifier that correlates the business screen collation location and the recording screen collation location,
The collation support unit
In one of the set of the business screen and the recording screen displayed on the display means, when the business screen collation location or the recording screen collation location is specified from the input means, the identifier is associated with the identifier. 21. The record browsing system according to claim 20, wherein the record screen collation part and / or the business screen collation part or both are highlighted. When the collation support unit is input from the input unit so as to designate the collation location for the business screen or the collation location for the recording screen, the identification information of the designated collation location for the business screen or the recording The record browsing system according to claim 21, wherein a collation log including identification information of a collation part for screen is created. A change location of the business screen, a changed value for changing the change location so as not to accept an input from the input means, and a change termination condition made at the client terminal; A business screen control device that stores and manages business screen control rules that prescribe changes in the displayed business screen is connected to the network,
The client terminal obtains the business screen control rule from the business screen control device, monitors access to the business processing device by the client terminal based on the business screen control rule, and is displayed on the display means A change to the post-change value at the change location of the business screen, and a work screen control unit that restores the original value from the post-change value at the change location if the change end condition is satisfied. The record browsing system according to claim 20. The record browsing system according to claim 23, wherein the work screen control rule includes a change start condition for changing to the post-change value at the change location. The matching rule includes
Business screen data defining one or more business screen verification locations that the user should check on the business screen in the verification operation;
Recording screen data defining one or more recording screen verification locations that the user should check on the recording screen in the verification operation,
24. The recording according to claim 23, wherein the change end condition is input from the input means that all of the business screen verification locations and the recording screen verification locations are designated. Browsing system.

Images