JP2012141966A - Business form generation device, business form generation system, control method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To automatically generate a secondary business form in the same business form style with that of a primary business form according to predetermined conditions every time an original business form is registered as the primary business form.SOLUTION: A client PC 31 transmits to a business form server 1 a requirement of generating a computer-aided name identification business form according to conditions input with respect to a displayed electronic business form (steps S100 to S116). The business form server 1 generates the computer-aided name identification business form based on the transmitted conditions, which is displayed in the client PC (steps S118 to S126), stores the conditions in the business form server 1 itself (steps S128 to S152), and then automatically generates the computer-aided business form by the conditions stored in itself when the electronic business form of a new generation is registered in the business form server.

Description

  The present invention relates to a form generation device, a form generation system, a control method, and a program for generating a secondary form for form data transferred from a host system.

  Some electronic form systems have a mechanism to search for forms saved in themselves, gather the search hit results, and generate secondary forms (named forms) with the search results embedded. To do.

  The flow of generating a name identification form is as follows. First, after an operator designates a search area for an electronic form, using the screen shown in FIG. 1, a search condition for the search area (the target area S1 shown in FIG. 1 is a search area) (the type shown in FIG. Specify the condition) and make a search request.

  Next, in response to the search request, the electronic form system displays the form data matching the search condition as a search result list as shown in FIG.

  Then, after the operator sets the upper and lower limit coordinates for pasting the search result to the electronic form of the search source, and makes a name identification form creation request, the electronic form system displays the form of the original form as shown in FIG. , Generate a name collation form in which the search result is embedded, and display it.

  Currently, the electronic form system is often operated as a company's core system, and the level of the contents of registered forms is a large unit from the individual level, such as the company-wide unit or the business unit unit. There are many. Accordingly, the user generates a name identification form and generates and uses a form of a level that is easy for an individual to use from a large level of form contents.

  In this way, at present, as the personal level form has increased the opportunity to use the name identification form, create a personal level form from the original form (primary form) registered in the electronic form system, The time-consuming work of using the created form is required.

  On the other hand, for the purpose of efficiently using a form, Patent Document 1 discloses a technique for secondarily using a former form registered in an electronic form system.

JP 2010-140122 A

  According to the invention described in Patent Literature 1, when an electronic form is generated and displayed, form data including the displayed layout information is extracted, and the extracted data is used as input data for another electronic form system or the like. This is a secondary utilization method that can be used.

  However, according to the technique described in Patent Document 1, it is not a technique to extract only necessary data in the same electronic form system and use it as a form with the same form image as the original form. It is suggested only to preserve like.

  Therefore, for example, in a state where the sales report of the entire company is registered monthly as a ledger report, each time a form is registered, a collated report that automatically filters only the sales of its own department for generations for the past half year In the case of generation, the current technology for generating a name collation form cannot be realized because there is no function for automatically generating a form, and there is only a method for recreating the name collation form after displaying the original form.

  Furthermore, in the current technology for generating a name collation form, since there is no relation (concept of generation) to the name collation form, a comment described in the name collation form created previously does not remain.

  Therefore, for example, in a state where the company-wide sales report is registered monthly as a ledger report, there is a comment created and attached to a name collation report that filtered only the sales of its own department for the generation for the past half year , If you want to display the attached comment on the next name collation form, it is not related to the name collation form, so no comment is displayed on the newly created name collation form, and a new comment is created. It is necessary to redo.

  In this way, at present, when generating a name collation form, only a form that filters the data part of the original form registered in the electronic form system is created, and the form created as a name collation form is continuously created. It is not suitable for use.

  The present invention solves the above-described problem, and enables the efficient generation of a name identification form from a source form, thereby reducing the labor involved in generating a name identification form, a form generation system, It is an object to provide a control method and a program.

  A first invention for achieving the above object is a form generation device for generating a secondary form from form data in a designated original form area, and a storage unit for storing the original form area; Form generation for generating the secondary form using form data of the new ledger form in the ledger area stored by the storage unit after receiving a new ledger form in the same format as the ledger form And a display control means for controlling the display of the secondary form generated by the form generation means.

  A second invention for achieving the above object is a form generation system in which a client apparatus and a form generation apparatus for storing and managing an original form for generating a secondary form are connected via a network. The client device comprises: designation means for designating an area for the original form; and display means for displaying the secondary form generated by the form generation means, wherein the form generation device comprises: Storage means for storing the ledger area designated by the designation means; and after receiving a new ledger form in the same format as the ledger form, the new source in the ledger area stored by the storing means A form generation system comprising: form generation means for generating the secondary form using form data of a form.

  A third invention for achieving the above object is a control method of a form generation device for generating a secondary form from form data in a designated original form area, and stores the original form area. And generating a secondary form using the form data of the new ledger form in the ledger area stored in the storage step after receiving the new ledger form in the same format as the step And a display control step for controlling the display of the secondary form generated by the form generation process.

  A fourth invention for achieving the above object is a method for controlling a form generation system in which a client apparatus and a form generation apparatus for storing and managing an original form for generating a secondary form are connected via a network. The client device executes a designation step for designating an area for the original form, and a display step for displaying the secondary form generated by the form generation step, The form generation device stores the ledger area specified in the specifying process, and after receiving a new ledger form in the same format as the original form, the form generating device stores the ledger area in the ledger area stored in the storing process. And a form generation step of generating the secondary form using the form data of the new original form.

  A fifth invention for achieving the above object is a program executed in a form generation device for generating a secondary form from form data in a designated original form area, and stores the original form area And receiving the new ledger form in the same format as the ledger form, and using the form data of the new ledger form in the former ledger area stored by the storing means, the secondary form Is a program that causes a function to generate a form generating means and a display control means for controlling the display of the secondary form generated by the form generating means.

  A sixth invention for achieving the above object is executed in a form generation system in which a client apparatus and a form generation apparatus for storing and managing a former form for generating a secondary form are connected via a network. The client device functions as a specifying unit for specifying an area for the original form and a display unit for displaying the secondary form generated by the form generation unit. The form generation device, the storage means for storing the ledger area designated by the designation means, and the new ledger form stored in the storage means after receiving a new ledger form in the same format as the former form A program that functions as a form generation unit that generates the secondary form using the form data of the new original form in the region.

  According to the present invention, conditions for generating a secondary form from an electronic form are stored, and when a new generation of electronic form is registered thereafter, a secondary form is generated based on the condition. There is an effect that it is possible to improve the efficiency of business by automatically generating a form.

It is a block diagram which shows the structure of the screen which designates the conditions at the time of generating a name collation form It is explanatory drawing for demonstrating the result of having searched the form data of the original form by the said conditions when producing | generating a name collation form. It is a figure which shows an example of a name collation form. It is a block diagram which shows schematic structure of the form system which concerns on embodiment of this invention. It is a block diagram which shows schematic structure of the hardware of the form server which concerns on embodiment of this invention. It is a flowchart which shows the flow of a basic process of the form production | generation system which concerns on embodiment of this invention. In an embodiment of the present invention, it is a figure showing the state where the electronic form was displayed on the screen. It is a figure which shows an example of the electronic form A in embodiment of this invention. In an embodiment of the present invention, it is a figure showing an example of a name collation performance form which a form server generated from an electronic form. It is a block diagram which shows the structure of the menu screen which concerns on embodiment of this invention. It is a block diagram which shows the structure of the template name input screen which concerns on embodiment of this invention. It is a block diagram which shows the structure of the template update confirmation screen which concerns on embodiment of this invention. It is a figure which shows an example of the electronic form B in embodiment of this invention. In an embodiment of the present invention, it is a figure showing an example of a name collation performance form which a form server generated from an electronic form. It is a flowchart which shows the flow of a template production | generation process in the form production | generation system which concerns on embodiment of this invention. It is a flowchart which shows the flow of an annotation production | generation process in the form production | generation system which concerns on embodiment of this invention. It is a flowchart which shows the flow of the automatic generation process of a name collation performance form in the form production | generation system which concerns on embodiment of this invention. It is a block diagram which shows the structure of the name collation template information table which concerns on embodiment of this invention. It is a block diagram which shows the structure of the name collation performance form generation table which concerns on embodiment of this invention. It is a block diagram which shows the structure of the annotation information table which concerns on embodiment of this invention. It is a flowchart which shows the flow of the name collation performance form display process to which the annotation was attached in the form production | generation system which concerns on embodiment of this invention. In an embodiment of the present invention, it is a figure showing an example when annotation information exists in the past generation of the name collation results form generated by the form server. It is a block diagram which shows the structure of the annotation complement information table which concerns on embodiment of this invention. In an embodiment of the present invention, it is a lineblock diagram showing composition of a screen for referring to a name collation performance form which a form server generates.

[First Embodiment]

  Hereinafter, a first embodiment of a form generation system of the present invention will be described in detail with reference to the drawings.

  FIG. 4 is a configuration diagram showing a configuration of the form generation system 10 according to the embodiment of the present invention. The form generation system 10 includes a form server 1 (form generation apparatus), a host 2 (server), and client PCs 31 and 32 ( A user terminal device) is connected via the network 4.

  It should be noted that the configuration of various terminals connected on the network 4 in FIG. 4 is an example, and it goes without saying that there are various configuration examples depending on applications and purposes.

  The form server 1 receives the form print data transferred from the host 2, converts the received form print data, and saves it as form data in an electronically reusable format (for example, a form record table or Form record file).

  In the present embodiment, what is displayed on a display device such as a user's terminal device by the form data is referred to as an electronic form (or form). In addition, the form server 1 manages form data and executes the processing of this embodiment to perform search, analysis, and the like.

  The host 2 has a structure capable of performing a response process for access from the client PCs 31 and 32, and the network 4 is configured by a LAN having an environment capable of communication using a protocol such as TCP / IP. It is what is done.

  The client PCs 31 and 32 are general-purpose PCs used by the user, and have a communication function capable of bidirectional communication with the form server 1 and the host 2 and an electronic form browsing function.

  Next, the hardware configuration of the form server 1 of the present invention will be described with reference to FIG. Since the host 2 (server) can have the same configuration as that shown below, description thereof is omitted.

  In FIG. 5, the central processing unit 12 comprehensively controls each device connected to the system bus, and an operating system that is a control program for the central processing unit 12 is stored in the storage device 13 or the external auxiliary storage device 16. (OS) and programs for realizing various functions described later of each server or each client are stored.

  The IO interface device 17 executes communication control processing with an external device via the network 4, and specifically, transmits data including form data to the partner device via the network 4, or to the network. Receive data from other connected devices.

  As described above, the form server 1 has been mainly described. The client PCs 31 and 32, which are general-purpose personal computers, are not particularly described because the basic configuration is the same as that of the form server 1, but the form server is not limited to the form server 1. The electronic form can be displayed by communicating with 1 or the host 2, and the object of the present invention can be achieved if an input mouse or keyboard is provided.

  The processing of each device described below is realized by the central processing unit of each device performing calculations and the like using programs and data stored in the storage device 13 or the external auxiliary storage device 16 of each device.

  Next, the basic processing flow of the form generation system 10 of the present invention will be described with reference to FIG.

  First, in step (1), when the form print data is transferred from the host 2 to the form server 1, in step (2), the form server 1 converts the form print data into a form convenient for subsequent processing (form data ) And save. In this embodiment, for example, the form record table 7 and the form record file 9 are stored and managed separately.

  In a state where such form data is managed, if there is a request for reference to form data from the client PCs 31 and 32 in step (3), the form server 1 first responds to the reference request in step (4). It is determined whether or not the target form data can be referred to by referring to the form result table 7. If the reference is possible, the requested form data is read from the form result file 9 and sent to the client PCs 31 and 32 in step (5). Send.

  The client PCs 31 and 32 that have received the form data can display or print the form data on the screen as shown in the example of FIG.

  Next, the outline of the template generation and name identification record generation processing, which is a feature of the present invention, will be described with reference to FIGS.

  In the present embodiment, by issuing a template generation instruction for the electronic form shown in FIG. 8, the name identification form shown in FIG. 9 is generated in the same format as the electronic form shown in FIG. 8 using the generated template. .

  Specifically, for the electronic form shown in FIG. 8, a specific condition is specified to display the name identification form shown in FIG. 9, and then a template generation instruction is issued from the menu displayed on the screen shown in FIG.

  Then, by inputting the template name using the template name input screen shown in FIG. 11, the conditions for generating the name identification form are saved as a template, and at the same time, the name identification form shown in FIG. Generation management is performed by saving in the same format as the electronic form shown. If there is a template with the same template name, it is possible to select a process on the template update confirmation screen shown in FIG.

  Next, the outline of the annotation storing process in the name identification result form, which is a feature of the present invention, will be described with reference to FIG.

  In the present embodiment, an annotation can be generated for any location in the name identification form shown in FIG. 9 and can be stored. For example, when it is desired to leave a comment regarding the actual value of the camera sales department in September, it is possible to create a mark like a balloon at the actual value and store the name identification form with the comment attached.

  Next, an outline of the name collation result form automatic generation processing that is a feature of the present invention will be described with reference to FIGS. 9 and 13 to 14.

  In the present embodiment, when a template has already been generated, an electronic form as shown in FIG. 13 is registered to automatically generate a name identification result form based on the template information.

  For example, in the state where the name identification form shown in FIG. 9 has already been registered as the name identification result form, a new electronic form as shown in FIG. 13 is registered, and sales for November are added to the name identification result form shown in FIG. If you want to create a template and register it in advance, it is possible to determine under what conditions the name identification result form should be generated from the registered template information. A performance report can be automatically generated.

  In addition, in the present invention, it is possible to take over the annotation attached to the previous name identification record at the time of generation, and to determine which value the annotation was created and display the annotation in an appropriate place It is said.

  The functions provided in the present embodiment are as described above. Specific processing for realizing these functions will be described later. Below, the example of the concrete use case in the form production | generation system 10 of this invention is demonstrated first.

  As a specific use case in an electronic form system, a case is assumed in which a form such as a sales report handled by an accounting business such as an accounting department arrives every month.

  As an example of a specific business model, a certain accounting department regularly receives a company-wide sales report and registers it as a ledger. The accounting department stores a past report of the ledger every time a ledger is registered. For a half year generation, assume a business model that creates a collation form that filters only the sales of its own department and leaves comments on the sales.

  For example, the sales report that arrives every month is registered in the sales report A registered in the previous month (last month is October) as shown in FIG. 8, and in the current month (this month is November) as shown in FIG. Suppose that there are two sales reports, Sales Report B, that will be released.

  In such a business model, the following cases are assumed as specific cases for generating name identification forms.

  For the past six months of generations of sales reports using the electronic form system, we have created a collation form that filters only the sales of our department and leaves comments on sales. Every time a report was registered, a name collation form was generated, but sales were processed without worrying about the amount.

  However, as the economic situation worsened, it was reported as a comment that the sales information for the month was analyzed and clarified. Therefore, it is necessary to enter the current month's comments in the generated name collation form, including sales up to the previous month and comments.

  As a specific user action in such a case, when the current electronic form system is used, an action of confirming the sales amount from the generated name collation form can be assumed.

  Then, it is conceivable to analyze sales from the generated name collation form, leave a comment, and save the name collation form in the client PC. In addition, when a new form is registered in the next month, it may be possible to confirm the sales amount after generating a name collation form again.

  After that, the name collation form saved last month is displayed again to confirm the sales analysis results up to last month, and the analysis is performed with the sales for the current month, and comments are left.

  It is assumed that such a work is repeated every month and a name identification form is created indefinitely. In order to solve the problem that occurs in this use case, the process executed in the form generation system 10 of this embodiment will be described in detail below.

  FIGS. 15 to 17 and FIG. 21 are diagrams specifically showing processing executed by the form generation system 10 according to the present embodiment using flowcharts, and FIGS. 18 to 20 are diagrams illustrating the present embodiment. It is the figure which showed the structure of the table used by the process performed with the form production | generation system 10 which concerns on a form.

  First, specific processing will be described with respect to the flowchart of template generation and name identification result form generation processing shown in FIG.

  First, in step S100, the client PC 31 transmits an electronic form display request to the form server 1 via the network 4, and in step S102, the form server 1 receives the electronic form display request transmitted from the client PC 31. In step S104, the form server 1 determines whether or not the electronic form corresponding to the display request received in step S102 can be referred to by using the form result table 7. 9 to obtain an electronic form.

  In step S106, the form server 1 transmits the electronic form acquired in step S104 to the client PC 31 that has requested display via the network 4, and in step S108, the client PC 31 transmits from the form server 1 in step S106. Received electronic forms.

  In step S110, the client PC 31 displays the electronic form received in step S108, for example, form A shown in FIG. 8 on a screen (not shown), and in step S112, the client PC 31 is requested to generate a name identification form. Whether or not a name collation form generation button or the like (not shown) provided on a screen (not shown) has been pressed.

  When a request for generating a name collation form is made, in step S114, the client PC 31 displays a screen as shown in FIG. 1, and a search condition for generating the name collation form input on the screen (in this embodiment, The generation is collected for the past six months, and the name identification form is generated only from the form data of the camera sales department). The search condition includes the coordinates of the search area to be searched for the form data of form A.

  In step S116, the client PC 31 sends a request for generating a name identification form including information for identifying the form A (such as an ID for uniquely identifying the electronic form) and a search condition via the network 4 to the form server 1. In step S118, the form server 1 receives a name identification form generation request.

  In step S120, the form server 1 obtains information specifying the form A received in step S118 and form data corresponding to the search condition from the form record file 9 or the like as name identification form data. In step S122, the form server 1 The name identification form data acquired in step S120 is transmitted to the client PC 31 via the network 4.

  In step S124, the client PC 31 receives the name identification form data transmitted from the form server 1 in step S122. In step S126, the client PC 31 displays the name identification form data received in step S124 on the screen as a name identification form. Then, a name identification form including the form data of form A shown in FIG. 9 is displayed.

  Next, in step S128, the client PC 31 determines whether or not to create a template for automatically generating a name identification form thereafter, based on whether or not template creation is selected from the menu shown in FIG.

  If it is determined that template creation has been selected, the process proceeds to step S130. In step S130, the client PC 31 displays the template name input screen shown in FIG. 11, and the OK button 11 provided in the template name input screen. Is detected, and the template name input in the template name input field 8 provided in the template name input screen is acquired. In the present embodiment, it is assumed that “camera” is input as the template name.

  In step S132, the client PC 31 sends a template generation request including information specifying the form A received in step S118, the search condition acquired in step S114, and the template name acquired in step S130 via the network 4. Send to the form server 1.

  In step S134, the form server 1 receives the template generation request transmitted from the client PC 31 in step S132. In step S136, the form server 1 newly creates a template based on the template generation request received in step S134. It is determined whether or not the request is to be made.

  This determination can be made, for example, by holding a table that stores a template name every time a template is generated, and determining whether or not the template name of a newly generated template is stored in the table. .

  Specifically, the determination is made based on whether or not the template name of the template to be newly generated is stored in the template ID of the name registration template information table 30 shown in FIG.

  If it is determined that there is a template name, that is, if the template requested to be generated is not newly created, the process proceeds to step S138. In step S138, the form server 1 transmits the template already registered via the network 4. A template update notification for confirming to the user whether or not to update is sent to the client PC 31.

  In step S140, the client PC 31 receives the template update notification transmitted from the form server 1 in step S138. In step S142, the client PC 31 displays the template update screen shown in FIG.

  In step S144, the client PC 31 determines whether or not the template is updated based on whether or not the OK button 21 or the cancel button 22 provided on the template update screen is pressed. If the OK button 21 is pressed, that is, the template is updated. If it is determined that the update is to be performed, the process proceeds to step S146. If the cancel button 22 is pressed, that is, if it is determined that the template is not to be updated, the process ends.

  In step S146, the client PC 31 transmits a template update request to the form server 1 via the network 4, and in step S148, the form server 1 receives the template update request transmitted in step S146, and step S150. Then, the form server 1 updates the template information based on the template generation request received in step S134. Note that the template information generation processing method is performed when the following processing is described.

  In step S136, when the form server 1 determines that there is no template name, that is, when the template requested to be generated is newly created, the process proceeds to step S152.

  In step S152, the form server 1 stores the template name included in the template generation request received in step S134, information specifying the form A, and template information based on the search condition in the name identification registered template information table 30 shown in FIG. Remember.

  The name identification registration template information table 30 stores a template ID for storing a template name input and designated using FIG. 11 when generating a template, and an ID for uniquely identifying an electronic form that is a basis for generating a name identification form. ID of the original form to be registered, name identification condition 1 (search) for storing the search conditions described above when generating the name identification form, and name identification condition 1 for storing the position (upper limit, lower limit coordinates) of the original form to which the search result is pasted (Vertical coordinates).

  In step S138, the template information described in this step is generated, and the already existing template information is updated using the template information.

  Next, in step 154, the form server 1 generates the name identification form data temporarily created in step S120 as a name identification result form (in the embodiment of the present invention, generated in the same format as the form A which is the original form). In step S156, the form server 1 stores information related to the generation of the name identification result form generation table 40 shown in FIG.

  The name identification result form generation table 40 includes a form ID generated by combining the ID (original form ID) for uniquely identifying the original form of the name identification form and the template name, a generation number indicating the generation for the form ID, and the name identification result form It includes the number of pages indicating the total number of pages, the file size of the name identification result form specified by the form ID, and detailed settings indicating detailed information related to the name identification result form.

  Furthermore, the name identification record form generation table 40 includes name identification line information, but the name identification line information is created from any line of any generation of the original form of the name identification result form specified by the form ID. Is stored.

  For example, if the first line of the first generation of an electronic form is hit as a result of a name identification search for an electronic form with the original form ID uriage, it is stored in the name identification line information with an ID of uriage-1-1. It becomes. If the first line of the second generation of the electronic form is hit, it is stored in the name identification line information with the ID uriage-2-1.

  Accordingly, in this step, the template ID, ledger ID, and generation number of the template information used in step S152 are 1 (because a new template is created in this step), and the name identification results generated in step 154 The total number of pages of the form, the file size of the generated name identification result form, detailed information about the generated name identification result form, the line information of the form A of the name identification form data generated in step S120 (Note that the generation of the original form is Form ID, generation number, number of pages, file of name identification result form generation table 40 in the order of information for identifying form A, that is, it can be determined by including it in ID and storing and managing it in form server 1 Store in size, detailed settings, and name identification line information. For example, the first record 41 of the name identification record form generation table 40 shown in FIG. 19 is assumed.

  In step S158, the form server 1 stores the name identification result form generated in step S154 as the form result file 9.

  Next, a specific process for the process of adding an annotation to the name identification result form and storing it will be described with reference to the flowchart shown in FIG.

  First, in step S200, the client PC 31 transmits a display request for the name identification result form to the form server 1 via the network 4, and in step S202, the form server 1 displays a request for display of the name identification result form transmitted in step S200. Receive.

  In step S204, the form server 1 acquires the name identification record corresponding to the display request received in step S202 from the form record file 9, and in step S206, the form server 1 acquires in step S204 via the network 4. Send name identification record. Note that the name identification line information of the name identification result form generation table 40 is held in correspondence with the form data displayed in each line of the name identification result form acquired in step S204. Thereafter, the name identification line information is generated and held in correspondence with the form data displayed in each line of the name identification result form.

  In step S208, the client PC 31 receives the name identification result form transmitted in step S206, and in step S210, the client PC 31 displays the name identification result form received in step S208.

  In step S212, the client PC 31 determines whether or not an annotation is attached to the name identification result form. If it is determined that the annotation is attached, the process proceeds to step S214.

  As shown in FIG. 9, in the state where annotations are attached to the name identification result form, since it is a new product for next month, a purchase refusal, before the bonus, etc. are attached as annotations.

  In step S214, the client PC 31 identifies the form ID of the name identification record attached as an annotation, the name identification line information of the name identification record attached with the annotation, the position information of the annotation (for example, the distance from the left end of the line), the annotation Size, annotation type, comments entered in annotation, etc. are acquired as annotation information.

  In step S216, the client PC 31 transmits a request for storing the annotation information acquired in step S214 via the network 4.

  In step S218, the form server 1 receives the annotation information storage request transmitted in step S216. In step S220, the form server 1 stores the annotation information received in step S218 in the annotation information table 50 shown in FIG.

  The annotation information table 50 stores and manages to which line of the name identification result form an annotation is attached, an annotation ID for uniquely identifying the annotation, a former form ID indicating the form ID of the name identification result form, an annotation Name identification line information for storing the information of the name identification record line to which is attached, the position coordinate of the attached annotation with respect to the name identification result line to which the annotation is attached (for example, the X coordinate is the distance from the left end of the line) Stored as position coordinates, and for the Y coordinate, the position that divides the vertical width of the line into two is fixed), the size indicating the size of the annotation, the type indicating the type of annotation, and the comment indicating the information input to the annotation It is comprised including.

  In this step, the annotation ID stores a value obtained by adding 1 to the maximum registered annotation ID, and the form ID, name identification line information, position information, size, annotation ID of the annotation information transmitted in step S216. In the order of type and comment, the original form ID, name line information, coordinates, size, type, and comment are stored in the annotation information table 50.

  Next, specific processing of name identification result form automatic generation processing will be described using the flowchart shown in FIG. Since this process is processed only by the form server 1, there is no process on the client PC 31 side in the flowchart shown in FIG. Further, in the present embodiment, specific processing in a state in which a name identification result form including a template for generating a name identification result form and an annotation has already been registered is shown.

  First, in step S300, the form data of the name identification result form (sales report B, hereinafter, form B) shown in FIG. 13 is accepted as the form result file 9 of the form server 1, and in step S302, the form data is obtained in step S300. It is determined whether or not there is a template related to the accepted ledger, that is, whether or not the ID exists in the ledger ID of the name identification registration template information table 30 using an ID for uniquely identifying the ledger. Thus, it is determined whether or not there is a related template.

  If it is determined that there is a related template, the process proceeds to step S304. If it is determined that there is no related template, the process ends.

  In step S304, in order to acquire the template information of the related template from the name identification registration template information table 30 in step S302, the ID is used to uniquely identify the original form, and the ID is stored in the name identification registration template information table 30. Template information existing in the original form ID is acquired.

  In step S306, name identification result form data is generated using the form data of the original form accepted in step S300 and the name identification condition of the template information acquired in step S304. At this time, a form ID for uniquely identifying the name identification result form data is generated by using the template ID and the original form ID of the template information.

  In step S308, in order to determine whether or not a name identification result form has been previously generated to be generated, whether or not the form ID of the name identification result form data generated in step S306 exists in the form ID of the name identification result form generation table 40. If it is determined that it exists, if a previous name identification result form has been generated, the process proceeds to step S310. If it is not determined that it exists, if a previous name identification result form has not been generated, The process proceeds to S314.

  In step S310, the generation information of the name identification result form is stored in the name identification result form generation table 40. The form ID generated in step S306, a value obtained by adding 1 to the maximum value of the generation number corresponding to the form ID, in step S306 In the order of the name identification result form generation table 40, the number of pages of the generated name identification result form data, the file size of the name identification result form data, the detailed information about the name identification result form data, and the name identification line information for generating the name identification result form data are sequentially displayed. The form ID, generation number, number of pages, file size, detailed settings, and name identification line information are stored.

  For example, assuming that the second generation name identification record is registered in this step, 41 is stored as the first record of the name identification record generation table 40 as shown in FIG. 19, and two records are recorded in this step. 42 is stored as an eye.

  In this case, since the name identification record is generated using the former form of the 6th generation as the name identification condition, the first record 41 indicating the first generation name identification record is used as the name identification line information in uriage-1-1. To uriage-6-1 are stored, but in the second record 42 indicating the second generation name identification record, uriage-2-1 to uriage-7-1 are stored.

  That is, the value indicating the line remains unchanged, but the numerical value indicating the generation is incremented by one from the first generation name identification line information (1 to 6) to obtain the second generation name identification line information (2 To 7).

  In step S312, a name identification result form is generated using the name identification result form data generated in step S306, and is stored as the form result file 9.

  In step S314, new generation information is stored in the name identification result form generation table 40 for the name identification result form data generated in step S306. In step S316, the name identification result form data is generated using the name identification result form data generated in step S306. It is generated and stored as a form record file 9. Note that the processing in step S314 or step S316 has the same contents as the processing in step S156 and step S158, and thus detailed description thereof is omitted.

  Next, specific processing of the name identification result form display processing with annotation will be described using the flowchart shown in FIG. In the present embodiment, an annotation is attached to the name identification result form, and specific processing when a display request for a certain generation is made will be described.

  First, in step S400, the client PC 31 transmits a display request for the name identification result form (including the form ID and generation number of the name identification result form) to the form server 1 via the network 4, and in step S402, the form server 1 Receives the name identification record display request transmitted in step S400.

  In step S404, the form server 1 acquires a name identification result form from the form result file 9 based on the display request received in step S402. In step S406, the form server 1 is included in the display request received in step S402. Annotation information related to the name identification result information corresponding to the former form ID of the annotation information table 50 corresponding to the form ID of the name identification result form to be acquired is acquired.

  In step S408, the form server 1 acquires the name identification line information stored in the name identification record generation generation table 40 based on the display request received in step S402, and in step S410, it is included in the annotation information acquired in step S406. Get name line information.

  In step S412, the form server 1 specifies a matching portion using the name identification line information acquired in step 408 and the name identification line information acquired in step 410. In the next step S414, the form server 1 determines in step S404. An annotation is generated and attached to the location identified in step S412 based on the annotation information obtained in step S406 corresponding to the identified location with respect to the acquired name identification record.

  In step S416, the form server 1 transmits the name identification record attached with the annotation in step S414 to the client PC 31 via the network 4, and in step S418, the client PC 31 is attached with the annotation transmitted in step S416. Receive name identification results.

  In step S418, the client PC 31 displays the name identification result form to which the annotation received in step S416 is attached.

  FIG. 22 shows a state in which annotations are attached to past generations of the name identification record. Assuming the case where the sales report as of October is generated as the original report, the form of name identification shown in FIG. 9 shows a report reflecting the sales report for two months from this point in time. Assumed as a thing.

For example, as of October, in order for the camera sales department in September and the camera sales department in June, in order for the new product next month, we will attach a purchase note and annoying growth before the bonus, and two months later, this implementation When the processing in the form generation system 10 according to the form is performed, as shown in FIG. 22, the camera sales department September annotation attached as of October remains and the camera sales department June annotation is not displayed. Is going.
[Second Embodiment]

  In the first embodiment of the present invention, an annotation is attached to each line even when new form data is added to the original form after an annotation is attached to each line of the name identification result form. Although reference is made to referencing the name identification result form as it is, in the second embodiment, when an annotation is attached to each line of the name identification result form, it is reflected in the original form including each line with the annotation attached. .

  Since the second embodiment of the present invention basically has the same configuration as that of the first embodiment, the differences from the first embodiment will be described, and the same as the first embodiment. About a structure etc., it demonstrates using the same code | symbol.

  First, an annotation is attached to the name identification result form, and information indicating that the annotation is attached to the original form having a line with the annotation attached is stored.

  Specifically, in step S220 shown in the flowchart of FIG. 16, information related to the annotation attached to the name identification result form is stored in the annotation information table 50. At this time, the original form is specified, and the original Information on the annotation attached to the form is stored in the annotation complement information table 60 shown in FIG.

  The annotation complement information table 60 includes an annotation ID, ledger ID, name identification line information, coordinates, size, type, and comments. The annotation ID stored in the annotation information table 50 and the annotation information table 50 are in this order of description. The first half (the ID of the ledger is indicated. The template ID after the hyphen is displayed), the name identification line information stored in the annotation information table 50, coordinates, size, type, and comment are stored. To do.

  Then, when displaying the original form, the following processing is specifically performed in order to take over and display the annotation attached to the name identification result form.

  When acquiring the electronic form, the client PC is used to specify the search condition including the form ID and the number of generations, and the form server 1 acquires the electronic form from the form result file 9 using the search condition. At that time, the annotation complement information stored in the annotation complement information table 60 shown in FIG. 23 is acquired, and it is determined whether or not the annotation is to be attached.

  It is determined whether or not the form ID of the electronic form to be acquired matches the original form ID of the annotation supplement information table 60. If the form ID matches, the record (annotation supplement information) is regarded as an electronic form to which an annotation is attached. To get.

  And for the name identification line information of the acquired record (annotation completion information), the numerical value written at the right end indicates the number of generations, so the record (annotation) including name identification line information having the number of generations included in the search condition Complementary information) is acquired.

  For example, in FIG. 23, the numerical value described at the right end indicates 1 for uriage-5-1 of the name identification line information, and indicates 1 for uriage-2-1.

  After that, the line of the electronic form is specified using the name identification line information included in the acquired annotation supplement information, but the numerical value between the hyphens of the name identification line information indicates the line for the electronic form. Decide which row of the annotation will be annotated.

  For example, in FIG. 23, the numerical value sandwiched between hyphens of name identification line information indicates 5 for uriage-5-1 of name identification line information, and 2 for uriage-2-1.

  After specifying the line to which the annotation is attached to the electronic form, the coordinates included in the annotation complement information are used to determine at which position of the line the annotation is attached.

  When the coordinates are specified, an annotation is generated from the size, type, and comment included in the annotation complement information, and the annotation is attached to the determined line and position of the electronic form.

  The form server 1 attaches the annotation to the electronic form, transmits the electronic form to the client PC, and displays the received electronic form on the client PC.

  Further, when displaying a name collated form as in the case of displaying a source form, in step S120 shown in FIG. 15, when a name collated form is acquired, a search including a form ID and the number of generations is performed using the client PC. By designating the conditions, the form server 1 acquires the name identification form data from the form record file 9 using the search conditions, and at this time, the annotation completion information stored in the annotation completion information table 60 shown in FIG. It is acquired and it is determined whether or not it is an annotation attachment target.

  It is determined whether or not the form ID of the name identification form to be acquired matches the original form ID of the annotation supplement information table 60. If they match, the record (annotation completion information) is assumed to be a name identification form to which an annotation is attached. To get.

  And for the name identification line information of the acquired record (annotation completion information), since the numerical value written at the right end indicates the number of generations, the record containing the name identification line information having the number of generations included in the search condition (annotation completion) Information).

  After that, the name identification line is specified using the name identification line information included in the acquired annotation completion information, but the numerical value sandwiched between hyphens in the name identification line information indicates the line for the name identification form. Decide which line you want to annotate.

  After identifying the line to which the annotation is attached to the name identification form, the coordinates included in the annotation complement information are used to determine at which position of the line the annotation is attached.

  When the coordinates are specified, an annotation is generated from the size, type, and comment included in the annotation complement information, and the annotation is attached to the determined name identification form line and the position related to the line.

  After attaching the annotation to the name identification form, the form server 1 transmits the name identification form to the client PC, and displays the received name identification form on the client PC.

  Further, in the subsequent steps, it is assumed that a name identification result form is generated using a name identification form attached with an annotation. In this case, in step S156 shown in FIG. 15, information on the generation of the name identification result form is obtained. After registration in the name identification record form generation table 40, information related to the annotation is stored in the annotation information table 50 shown in FIG. 20 and the annotation supplement information table 60 shown in FIG.

  Annotation ID, ledger form ID, name identification line information, coordinates, size, type, and comment in the order of description of the annotation information table 50 plus one maximum ID of annotation ID stored in the annotation information table 50, name identification result form Form ID of the generation table 40, name identification line information corresponding to the line to which the annotation is attached, name identification line information of the generation table 40 of the name identification, coordinates of the line to which the annotation is attached, annotation size, type of annotation, comment described in the annotation Remember.

  The annotation supplement information table 60 stores the same information except for the information registered in the annotation information table 50 and the original form ID, and the original form ID stores the first half of the hyphen of the form ID. is doing.

As a result, even when a name identification result form is generated from a name identification form, it is possible to inherit the annotation information attached to the name identification form.
[Third Embodiment]

  In the first embodiment of the present invention, in step S400 of the flowchart shown in FIG. 21, the display request for the name identification result form is directly performed. In the third embodiment, in the state where the original form is opened, The mode which assumed opening the name identification result form relevant to a name identification form is shown.

  The third embodiment of the present invention basically has the same configuration as that of the first embodiment, and therefore, different parts from the first embodiment will be described and the same as the first embodiment. About a structure etc., it demonstrates using the same code | symbol.

  In step S400 of the flowchart shown in FIG. 21, a request for displaying a name identification result form (including the form ID and generation number of the name identification result form) is transmitted to the form server 1, but the ledger form shown in FIG. 24 is displayed. Use the screen to request display of the name identification record.

  A form display screen 70 shown in FIG. 24 displays a display area 71 indicating an area for displaying a former form, a form ID input field 72 indicating a form ID input field for specifying a name identification result form, and a name identification result form. A search button 73 is provided for pressing the button.

  When the user inputs a form ID for specifying the name identification result form to be referred to in the form ID input field 72 and presses the search button 73, the form ID and the form ID input in the form ID input field 72 are displayed in the display area 71. In step S402, a request for displaying a name identification result form (including the form ID of the name identification result form and the month degree of the form data) is transmitted to the form server 1.

  In step S <b> 404, the form server 1 acquires a corresponding name identification result form from the form result file 9 based on the form ID and the degree of form data received in step S <b> 402.

  In the present embodiment, in response to the detailed setting of the name identification record form generation table 40 shown in FIG. 19, the information related to the generation of the name identification result form generation is stored in this table (step S156, step S310, and step S314). Set the information about the time to perform.

  Thereby, the generation number is specified by subtracting the month included in the time set in the detailed setting from the current month, and the specified name identification result form is acquired.

  In the present embodiment, the number of generations is considered every month, but this is not a limitation, and the number of generations may be considered such as every day or every year.

  According to the present invention, conditions for generating a secondary form from an electronic form are stored, and when a new generation of electronic form is registered thereafter, a secondary form is generated based on the condition. By automatically generating forms, business efficiency can be improved.

  In addition, by storing line information (an original form line) with annotations attached to a secondary form, the line information can also be used to generate a new secondary form. Since an annotation can be attached, it is possible to check a comment or the like previously input to the attached annotation, so that the work efficiency can be improved.

  Although the embodiment has been described in detail above, the present invention can take an embodiment as, for example, a method, a program, a storage medium, or the like. Specifically, the present invention is applied to a system composed of a plurality of devices. The present invention may be applied, or may be applied to an apparatus composed of one device.

  Although the embodiment in the form generation system is described, it is also possible to implement the function of the client PC in the form generation apparatus and the structure of the form generation apparatus alone.

  The program according to the present invention is a program that allows a computer to execute (read) each processing method, and the storage medium according to the present invention stores a program that allows the computer to execute each processing method.

  The program in the present invention may be a program for each processing method of each device.

  As described above, a recording medium that records a program that implements the functions of the above-described embodiments is supplied to a system or apparatus, and a computer (or CPU or MPU) of the system or apparatus stores the program stored in the recording medium. You can also read and execute

It goes without saying that the purpose of the light is achieved.

  In this case, the program itself read from the recording medium realizes the novel function of the present invention, and the recording medium storing the program constitutes the present invention.

  As a recording medium for supplying the program, for example, a flexible disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD-R, DVD-ROM, magnetic tape, nonvolatile memory card, ROM, EEPROM, silicon A disk or the like can be used.

  Further, by executing the program read by the computer, not only the functions of the above-described embodiments are realized, but also an OS or the like operating on the computer based on an instruction of the program is a part of the actual processing or It goes without saying that the case where the functions of the above-described embodiments are realized by performing all of the above processing is also included.

  Furthermore, after the program read from the recording medium is written to the memory provided in the function expansion board inserted into the computer or the function expansion unit connected to the computer, the function expansion board is based on the instructions of the program code. It goes without saying that the case where the CPU or the like provided in the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

  Further, the present invention may be applied to a system composed of a plurality of devices or an apparatus composed of a single device. Needless to say, the present invention can be applied to a case where the present invention is achieved by supplying a program to a system or apparatus.

  In this case, by reading a recording medium storing a program for achieving the present invention into the system or apparatus, the system or apparatus can enjoy the effects of the present invention.

  Furthermore, by downloading and reading a program for achieving the present invention from a server, database, etc. on a network using a communication program, the system or apparatus can enjoy the effects of the present invention. In addition, all the structures which combined each embodiment mentioned above and its modification are also included in this invention.

DESCRIPTION OF SYMBOLS 1 Form server 2 Host 4 Network 7 Form results table 9 Form results file 10 Form generation system 12 Central processing unit 13 Storage device 16 External auxiliary storage device 17 IO interface device 31 Client PC
32 Client PC

Claims (10)

A form generation device for generating a secondary form from form data in a designated ledger area,
Storage means for storing the ledger area;
Form generation for generating the secondary form using form data of the new ledger form in the ledger area stored by the storage unit after receiving a new ledger form in the same format as the ledger form Means,
Display control means for controlling display of the secondary form generated by the form generation means;
A form generation device characterized by comprising:   The said form production | generation means produces | generates the said secondary form using the form data of the said original form in the said original form area memorize | stored by the said memory | storage means, and the form data of the said new ledger form. Form generator. Condition setting means for setting conditions for generating a secondary form for the form data in the original form area;
The form generation apparatus according to claim 1, wherein the form generation unit generates the secondary form from the form data of the original form that satisfies a condition set by the condition setting unit.   4. The form generation apparatus according to claim 3, wherein the condition setting unit sets the number of generations of the form data of the new original form. The storage means stores the original form area of attached information attached to the secondary form,
5. The form generation unit according to claim 1, wherein the attached form is attached to the ledger form area and the secondary form is generated using the form data of the new ledger form. The form generation device according to item 1. A form generation system in which a client apparatus and a form generation apparatus for storing and managing an original form for generating a secondary form are connected via a network,
The client device is
A designation means for designating an area for the ledger;
Display means for displaying the secondary form generated by the form generation means;
With
The vote generating device
Storage means for storing the ledger area designated by the designation means;
Form generation for generating the secondary form using form data of the new ledger form in the ledger area stored by the storage unit after receiving a new ledger form in the same format as the ledger form Means,
A form generation system characterized by comprising: A control method of a form generation device that generates a secondary form from form data in a designated ledger area,
A storage step for storing the ledger area;
Form generation for generating the secondary form using form data of the new ledger form in the ledger area stored in the storage step after receiving a new ledger form in the same format as the ledger form Process,
A display control step for controlling the display of the secondary form generated by the form generation step;
A control method for a form generation device, characterized in that A control method for a form generation system in which a client apparatus and a form generation apparatus for storing and managing a former form for generating a secondary form are connected via a network,
The client device is
A designation step for designating an area for the ledger;
A display step for displaying the secondary form generated by the form generation step;
Run
The vote generating device
A storage step of storing the ledger area designated by the designation step;
Form generation for generating the secondary form using form data of the new ledger form in the ledger area stored in the storage step after receiving a new ledger form in the same format as the ledger form Process,
A method for controlling a form generation system, characterized in that A program executed in a form generation device that generates a secondary form from form data in a designated ledger area,
Storage means for storing the ledger area;
Form generation for generating the secondary form using form data of the new ledger form in the ledger area stored by the storage unit after receiving a new ledger form in the same format as the ledger form Means,
Display control means for controlling display of the secondary form generated by the form generation means;
A program characterized by functioning. A program executed in a form generation system in which a client apparatus and a form generation apparatus for storing and managing a former form for generating a secondary form are connected via a network,
The client device;
A designation means for designating an area for the ledger;
Display means for displaying the secondary form generated by the form generation means;
Function as
The vote generating device;
Storage means for storing the ledger area designated by the designation means;
Form generation for generating the secondary form using form data of the new ledger form in the ledger area stored by the storage unit after receiving a new ledger form in the same format as the ledger form Means,
A program characterized by making it function.

Images