JP6015794B2 - Electronic form system, its processing method and program - Google Patents

Description

  The present invention relates to an electronic form system capable of continuously processing forms, a processing method thereof, and a program.

  In a conventional electronic form management system, a form that is a paper medium is stored and managed as an electronic form (form data), so that only necessary forms can be searched from a large amount of forms easily and quickly. For example, when searching for form data, an electronic form system that searches for desired form data after designating an area (search target area) to be searched with electronic form information and inputting a condition that matches the search target area. It has been proposed (see Patent Document 1).

  In general, a company that has introduced an electronic form management system browses and outputs, for example, a monthly sales slip as a routine work.

  Even though the form to be viewed in a routine job is decided, the worker searches for the form, displays it, and exports the data at the required location. Alternatively, the same operation is repeated every time a routine work is performed, such as printing a necessary form.

  As a way to improve the efficiency of such work, it is conceivable to keep a link of a document file as a favorite and to browse a desired document file by specifying the link when working.

JP 2007-179201 A

  However, even if the link of the document file is registered as a favorite, it is necessary to specify a form every time and execute the function (display, export, print, etc.) corresponding to the work, and perform a routine work. It was.

In order to achieve the object of the present invention, the present invention uses a template to increase the efficiency of work on a plurality of electronic forms by sequentially executing desired processes from a plurality of different processes on the plurality of electronic forms. Provide a mechanism.

To achieve the object of the present invention, an electronic document server for managing electronic form, in pairs in a plurality of electronic form so as to execute a desired process in the order, and document identification information of the electronic document executing processing , applied to the electronic document, associating the processing set arbitrarily from a plurality of different processing, storage means for storing the correspondence template that defines the execution order of the process, as the template by the storage means and document identification information of the previous SL electronic form that stored, the process associated with the document identification information obtaining means for obtaining the execution order of the process, electronic form, which is stored in the template in the order of execution of the processing as but are processed, processing of using said electronic document acquired based on the acquired document identification information by acquiring means, executes a process that is correlated to the document identification information Characterized in that it comprises an execution unit.

In addition, when the electronic form is registered in the electronic form server, an electronic form determination unit that determines whether the template stored in the storage unit includes form identification information of the electronic form is further included. And the process execution means uses the electronic form to determine the form identification acquired by the acquisition means when the electronic form determination means determines that the template contains the form identification information of the electronic form. A process associated with information is executed.

Further, in order to register as a template to execute a desired process on a plurality of the electronic form in the order, and document identification information of the electronic document executing the process, be applied to the electronic form is arbitrarily set from a plurality of different processing It is further characterized by further comprising an accepting means for accepting designation from the user with respect to the execution order of the associated processes .

The plurality of different processes include a process for searching for the electronic form, a process for displaying the electronic form, and a process for outputting data included in the electronic form to a file having a format different from that of the electronic form. It is characterized by including at least one .

According to the present invention, by using a template, it is possible to execute a desired process in order from a plurality of different processes on a plurality of electronic forms to increase the efficiency of work on the plurality of electronic forms .

It is a figure which shows schematic structure of an electronic form management system 2 is a block diagram illustrating an example of a hardware configuration of a form server 100. FIG. It is a figure which shows the structural example of the form file 213. 2 is a block diagram showing a schematic configuration of functional parts of a form server 100 and client PCs 101 and 102. FIG. It is a flowchart which shows the whole template process. It is a flowchart which shows a template addition process. It is a flowchart which shows the process which deletes the registered template and the form. It is a flowchart which shows the execution process of a template This is a screen displayed on the display unit 210 when a display action is executed during execution of a business template. It is an export result display screen displayed on the display unit 210 when an export action is executed. It is an initial display screen displayed on the display unit 210 before selecting a business template This is the template list screen that is displayed when there is no template information for the logged-in user. It is a template list screen when template information is added by the user. This is the screen when a check is entered in the check box of the "Sales" business template It is a data image of the template management information master managed for each user It is a flowchart which shows the template addition process of 2nd Embodiment. It is a template list screen of a 2nd embodiment. It is a flowchart which shows the execution process of the template of 2nd Embodiment. It is a data image of the template management information master of 2nd Embodiment. It is a data image of action flag master It is a data image of the search template management master It is an image figure of a search condition setting screen for registering a search template It is an image figure of a search template screen which chooses a search template at the time of setting search action.

[First Embodiment]
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a diagram showing a schematic configuration of an electronic form management system according to an embodiment of the present invention.

  In FIG. 1, a form server 100 stores, as an electronic form management device, data of multiple types of electronic forms (hereinafter simply referred to as “forms”) (hereinafter referred to as “form data” or “form file”). It manages and provides services such as browsing and searching for form files to the client PCs 101 and 102 via the network 103.

  In addition, the form server 100 receives data to be converted into an electronic form from a mainframe (not shown), and saves it in a format that can be viewed as an electronic form (form file 213).

  The client PCs 101 and 102 are information processing apparatuses such as personal computers used by users. The client PCs 101 and 102 are configured to be able to communicate with the form server 100 via the network 103, and can make a form file search request to the form server 100, view search results, and the like.

  The network 103 is configured by, for example, a LAN (Local Area Network), the Internet, or the like. Note that various devices connected to the network 103 are not limited to the illustrated example, and various devices may be connected depending on applications and purposes.

  FIG. 2 is a block diagram illustrating an example of a hardware configuration of the form server 100 in FIG.

  In FIG. 2, a CPU (Central Processing Unit) 201 controls various devices connected to the system bus 204 and implements various functions by executing various programs. A RAM 202 is a main memory of the CPU 201 and functions as a work area, a temporary save area, and the like. The ROM 203 or the external memory 211 stores an operating system (OS) that is a control program of the CPU 201 and a program 212 for realizing various functions in the form server 100. The CPU 201 loads these programs into the RAM 202 and executes them as necessary. A form file 213 used when the program 212 is executed is stored in the external memory 211. A detailed description thereof will be described later. The DB (database) 215 stores a template management information master shown in FIG. These will be described later. Although not shown, user ID and password information for user authentication are also managed.

  The input controller 205 controls an operation input from the input unit 209 configured with, for example, a keyboard and a mouse. The display controller 206 controls display on the display unit 210. The display unit 210 is configured by, for example, a CRT or a liquid crystal display.

  An external memory controller (MC) 207 controls access to the external memory 211 that stores a boot program, various applications, user files, and edit files. In addition, various tables and parameters for realizing various functions of the server or each client PC are stored. The external memory 211 includes a hard disk (HD), a flexible disk (FD), a magnetic tape drive, and the like.

  The communication I / F controller 208 controls communication with an external device such as a client PC performed via the network 103.

Since the client PCs 101 and 102 have substantially the same hardware configuration as the form server 100, the description thereof is omitted. The DB 215 is not held. As for the form file 213, the client PC receives only the part necessary for display from the form server 100, so that the client PCs 101 and 102 do not hold them in advance. The client PCs 101 and 102 hold a client module for displaying the form file 213 and hold a program different from the program 212 in the form server 100. Further, the client PCs 101 and 102 can display the form file 213 or specify a search condition for an arbitrary form file 213. The CPU of the form server 100 processes each step executed by the form server in the flowchart described later, and the CPU of the client PC 101 or 102 processes each step executed by the client PC in the flowchart described later.
FIG. 3 is a diagram illustrating a configuration example of the form file 213.

  The form file 213 includes form information 3301 that defines a layout such as ruled lines and drawings in the form, form text data 3302 relating to characters included in the form, form layout definition information 3303 that defines line pitch, character font, and the like in the form, The form is composed of form text arrangement information 3304 for determining the arrangement of the form text data in the form.

  When the client PC 101 displays a form (form image), the form server 100 generates form data for display from the four information files shown in the figure, downloads the form data, temporarily stores it on the hard disk, and loads it into the work memory After that, it is displayed on the display as a form. For example, in the case of a client server type system, four information files are downloaded from the form server 100, form data for display is generated by the client PC 101, and displayed as a form on the display. May be. The form layout definition information 3303 includes information related to the form layout, and the height of each line of the form is defined from this information.

  The form file 213 is composed of one or a plurality of files and contains one or a plurality of pages. The form server 100 manages the same type of a plurality of form files 213 as a group, and each form file 213 is called a generation within the group. For example, like the business daily report, the same type of forms with different dates and times are managed as generations. The form ID is assigned to each group. Further, the form file 213 is stored in association with the bibliographic information (form ID, form name, form registration date, form file storage location, etc.) of the form file, and the bibliographic information is stored and managed in an external memory (for example, a database). ing.

  Next, functions of the form server 100 and the client PCs 101 and 102 will be described.

  FIG. 4 is a block diagram showing a schematic configuration of functional parts of the form server 100 and the client PCs 101 and 102.

  The client PCs 101 and 102 have functional units such as a template information display unit 401, a form selection unit 402, a processing content setting unit 403, and an execution instruction unit 404. The form server 100 includes a template information storage unit 405, a form acquisition unit. 406, a setting process acquisition unit 407 and a process execution unit 408.

  The template information display unit 401 is a functional unit that acquires, from the form server 100, the template information of the user who has logged in from the template management information master and is stored and managed in the DB 215 of the form server 100 and displays the template information on the display unit 210.

  The form selection unit 402 is a functional unit that selects a form for executing an action from the form list and adds it to the business template.

  The processing content setting unit 403 is a functional unit that sets what kind of processing (display, export, printing, etc.) is to be executed (action) on the form selected by the form selection unit 402, and is desired by the user. You can set action settings.

  The execution instructing unit 404 is a functional unit for instructing execution of an action for a form stored in correspondence with a business template designated by the user, and by transmitting the template ID of the designated business template to the form server 100, A form action can be executed.

  The template information storage unit 405 is a functional unit that registers business templates, forms, and processing (action) setting information instructed by the client PCs 101 and 102 in the template management information master of the DB 215.

  The form acquisition unit 406 has a function of acquiring a form (form file) stored in correspondence with the business template instructed to be executed by the execution instruction unit 404 of the client PC 101 or 102 from the external memory 211 according to the form ID.

  The setting processing acquisition unit 407 is a functional unit that acquires processing for executing processing of the form acquired by the form acquisition unit 406.

  The process execution unit 408 transmits the form to the client PCs 101 and 102 to display the form in accordance with the form acquired by the form acquisition unit 406 and the process acquired by the setting process acquisition unit 407, and extracts text data from the form. It is a functional unit that executes a process of exporting and outputting a form to a predetermined printing apparatus.

  Next, detailed processing of this embodiment in the electronic form management system of FIG. 1 will be described using the flowcharts of FIGS.

  FIG. 5 is a flowchart showing the entire template processing in the electronic form management system of FIG.

In step S501, it is determined whether or not the client PC 101 or 102 has logged into the form server 100. Specifically, the determination is made by transmitting the user ID and password input by the client PC 101 or 102 to the form server 100 and comparing with the user information stored in the form server 100. If there is matching user information, login permission is received from the form server 100, and the process proceeds to step S502. If they do not match, the user ID and password are requested again as an error.

  In step S <b> 502, the client PCs 101 and 102 transmit a screen request for the screen 1101 for the form list to the form server 100.

  In step S503, the form server 100 receives a request transmitted from the client PC 101 or 102.

In step S504, the form server 100 transmits a form list screen 1101 to the client PCs 101 and 102. Note that the form list screen 1101 is configured so that information on forms managed by the form server 100 can be acquired and displayed as a list.

  In step S505, the form list screen 1101 transmitted from the form server 100 is received, and in step 506, the form list screen 1101 is displayed.

In step S507, it is determined whether or not the template button 1102 has been pressed. If it is determined that the template button 1102 has been pressed, the process proceeds to step S508. If the template button has not been pressed, the process waits.

  Although not described in the present embodiment, when a form list button, bookmark button, or personal information button other than the template button 1102 is pressed, various processes are executed.

  In step S508, when the template button 1102 is pressed, the client PCs 101 and 102 request the template server 100 for template information in order to display the template list screen 1201 or 1301.

  In step S509, the form server 100 receives a request for template information transmitted from the client PCs 101 and 102.

  In step S510, the form server 100 transmits template information to the client PCs 101 and 102. Specifically, the template management information master in FIG. 15 is searched for the template information of the logged-in user, and the acquired template information is transmitted.

  It should be noted that the template information is stored in association with the user ID (not shown) so that the template information of the logged-in user can be searched with reference to the template management information master of FIG.

  In step S511, the template information is received, and the template list screen 1301 in FIG. 13 is displayed. The template list screen 1301 is an example of a screen when template information is registered. A template list screen 1201 is a screen when template information is not registered.

  In step S512, it is determined whether the add button 1304 has been pressed or the execute button 1306 has been pressed from the business template creation button 1202 in FIG. 12 or 13 and the form list in FIG. If it is detected that the business template creation button 1202 or the add button 1304 is pressed from the form list, the process advances to step S513 to create template information. When it is detected that the execution button 1306 is pressed, it is determined whether or not a check is input to the check box 1302. If a check is input, the process advances to step S514 to execute a form registered corresponding to the business template name for which the check is input in accordance with the set action.

  In step S513, a business template is added as template information. The process of adding a business template as template information will be described in detail with reference to FIG. In this embodiment, the business template is created and registered by the client PCs 101 and 102. However, the business template (for example, “sales” and “sales management” in FIG. 14) is stored and managed in advance in the form server 100. It is possible to configure as shown.

  In step S514, the selected business template is executed according to the action. The template execution process will be described in detail with reference to FIG.

  FIG. 6 is a flowchart showing the template addition process in step S5013 of FIG.

  In step S601, it is determined whether or not a business template creation button 1202 has been pressed, and it is determined whether or not a new business template is to be created (added). If a new business template is to be created, the process proceeds to step S602. If a new business template is not created, the process proceeds to step S607.

  In step S <b> 602, the client PC 101 or 102 transmits a screen request for a screen for creating a business template to the form server 100.

  In step S603, the form server 100 receives the screen request transmitted from the client PC 101 or 102.

  In step S604, the form server 100 transmits a business template creation screen to the client PCs 101 and 102. A business template creation screen (not shown) is stored in advance in the external memory 211 of the form server 100. Further, the business template creation screen has an area in which a business template name to be created (added) can be input. Also, a registration button and a cancel button are provided, and when the registration button is pressed, a template with the input business template name is registered.

  In step S605, the business template creation screen transmitted from the form server 100 is received, and input of a business template name newly created in step S605 is accepted. In other words, the process in step S605 is a template creation process for creating a business template.

  In step S606, the business template name input in step 605 is registered and displayed in the business template name on the template list screen 1201 in FIG. In other words, the process in step S606 is an additional display process for additionally displaying the business template on the display unit 210.

  The created business template name is temporarily stored in the RAM 202. Note that it is checked whether the same business template name is registered in the template management information master of FIG.

  In step S607, it is determined whether or not the add button 1304 is pressed from the form list, and it is determined whether to add the form to the business template. If a form is to be added, the process proceeds to step S608. If a form is not added, the process proceeds to step S614.

  In step S608, in 1301, an input to the check box 1302 is accepted for the business template to which a form is to be added. If a check is input to the check box 1302, the process proceeds to step S609. In other words, the process in step S608 is a template selection process for selecting a business template for continuously executing the process.

  It is also possible to press the add button 1304 from the form list after a check is input to the check box 1302.

  In step S609, a form list display request is transmitted from the client PC 101 or 102 to the form server 100 in order to add a form to the business template.

In step S610, the form server 100 receives the form list display request transmitted from the client PC 101 or 102.

  In step S611, the form server 100 receives the display request, generates a list of form files 213 stored in the external memory 211 of the form server 100, and configures the client PCs 101 and 102 with, for example, a list of form names. Send the form list screen. In addition to the form name, the storage destination directory (binder position) where the form is stored is also held.

  In step S612, the form list screen is received and displayed on the display unit 210 (list display process). Accepts selection of a form to be added to the business template from the form list (form designation process). In other words, the process in step S612 is a setting process for setting an electronic form to be executed.

  In step S613, the form name of the form selected in step S612 is registered and displayed in the checked business template. At this time, the binder position other than the form name is also displayed. Also, an action setting screen for setting the action of the registered form is displayed. The added form and the business template name stored in step S606 are associated with each other and stored in the RAM 202.

  In step S614, a setting input is accepted in order to determine an action for the registered form. In other words, the process of step S614 is a setting process for setting the processing content for the electronic form to be executed.

  In this embodiment, the action is set by inputting a number for executing the action (setting the processing order), and the action number and the action content (display, export, etc.) input to the RAM 202 in association with the added form. Print) is stored. As will be described later, the action is executed according to the input number. The action content is not limited to display, export, and printing, but can be set as the action content as long as it is a function (for example, search) that can be executed by the electronic form management system.

  Further, when an add button 1304 is pressed from the business template creation button 1202 or the form list, the action can be set by controlling the action 1310 so that the action can be set.

  In step S615, in accordance with pressing of the save button 1311, the added template information including the added business template, the form name, and the like, the action number, and the action content is transmitted to the form server 100. When the form server 100 receives the additional template information, it registers the additional template information in the template management information master of FIG. In other words, the processing of step S615 is the form server 100 that includes the template identification information (template ID) of the added business template, the form identification information (form ID or form name) of the set electronic form, and the processing content (action content). It is the transmission process which transmits to. The form server 100 corresponding to the process of step S615 includes template identification information (template ID) of the added business template, form identification information (form ID and form name) of the set electronic form, and processing contents (action Content) and the form identification information and the processing content are stored in the template management information master of FIG. 15 according to the template identification information.

  An example of adding template information (adding a business template and a form) on the template list screen 1301 in FIG. 13 is the template list screen 1307 in FIG. “Sales management” is added as a business template, and a demo form 4 and a demo form 5 are added. The demonstration form 4 has an “display” action setting, and the demo form 5 has an “export” action setting.

  The template information displayed on the template list screen 1307 in FIG. 13 corresponds to the template management information master in FIG.

  A business template name 1308 in FIG. 13 corresponds to the template ID 1501 and the business template name 1502 in FIG. A form name 1309 corresponds to a form ID 1503 and a form name 1504. Action 1310 corresponds to action 1505.

  FIG. 7 is a flowchart showing processing for deleting a registered template or form.

  The deletion process is configured such that the delete button 1305 can be pressed while the template form list screen is displayed. When the delete button is pressed, the business template or the form for which a check is input is entered. Can be deleted. Note that when a business template is deleted, a form stored correspondingly is also deleted.

First, the template screen of FIG. 13 is displayed in order to delete the business template and the form.

  In step S702, a business template to be deleted or a form registered in the business template is selected by the user. In the case of deletion, a check is input to the check box 1302 and the check box 1303 in FIG.

  In step S703, when pressing of the delete button 1305 is detected, the business template name (or business template ID) or form name (or the business template name) selected to execute the deletion of the checked business template or the form registered in the business template (or A deletion request including a form ID) is transmitted to the form server 100.

  In step S704, a deletion request including a business template name (or business template ID) and a form name (or form ID) is received.

  In step S705, deletion information such as a business template name (or business template ID) and a form name (or form ID) is acquired from the deletion request, and the corresponding template information is deleted from the template management information master of FIG.

  In step S706, a result indicating deletion is transmitted to the client PCs 101 and 102 that have requested deletion.

  In step S707, the deletion result is received and the deletion result is displayed. The deletion result is, for example, the deleted business template name or form name. When the check box 1302 in FIG. 13 is checked and the deletion process is performed, the display is updated as shown in the screen in FIG.

  FIG. 8 is a flowchart showing template execution processing.

In step S801, an input for selecting a business template for which an action is to be executed is received from the template list screen 1301 of FIG. In other words, the process in step S801 is a template selection process for selecting a business template for continuously executing the process.

  In step S802, it is determined whether or not the execution button 1306 in FIG. 13 has been pressed. If it is detected that the execution button 1306 has been pressed, the process proceeds to step S803. In other words, the process in step S802 is an execution instruction process for instructing execution of a template.

  In step S803, the template ID of the business template selected in step S801 is transmitted to the form server 100.

In step S804, the form server 100 receives the template ID transmitted from the client PC 101 or 102.

  In step S805, the form and action stored corresponding to the received template ID are acquired from the template management information master of FIG. The form and action are acquired according to the action order 1506. When the next action request is received in step S812, which will be described later, the next action is acquired in the order of actions. In other words, the process of step S805 is an acquisition process of acquiring an electronic form registered in association with the template ID instructed to be executed and a processing content (action) corresponding to the electronic form.

  For example, when a check is entered in 1302 on the template list screen 1301 in FIG. 13 and the execute button 1306 is pressed, the demo form 1 (display), demo form 1 (export), demo form 2 (export), demo The action of form 3 (printing) is executed.

  In step S806, it is determined whether all actions have been executed. In the example of FIG. 13, it is determined whether the action has been executed up to the last action, demo form 3 (printing). If all actions have been executed, the process ends. If there is a next action, the process proceeds to step S807.

  In step S807, it is determined whether the action acquired in step S805 is a display. If it is displayed, the process proceeds to step S808.

  In step S808, the form ID to be displayed is acquired from the form ID 1503 of the template management information master in FIG. 15, and the latest generation form among the forms corresponding to the form ID is searched from the form file 213. Then, the retrieved form is transmitted to be displayed on the client PC 101 or 102 where the action has been executed (process execution). In the example of FIG. 13, the form ID “DEMO001” is acquired, and the form file corresponding to this form ID “DEMO001” is searched.

  In step S809, the form transmitted from the form server 100 is received, and the form is displayed on the display unit 210 of the client PC 101 or 102 as shown in FIG.

  In step S810, it is determined whether or not the next action execution button 901 has been pressed by the user. If the next action execution button 901 is pressed, the process proceeds to step S811.

  In step S811, in order to execute the next action, an action execution request for executing the next action is transmitted to the form server 100. In other words, the process of step S811 is an execution instruction process for executing the next process.

  In step S812, an action execution request is received from the client PC 101 or 102. When the action execution request is received, the process proceeds to step S805, and the next action is acquired according to the action order 1506.

  In step S813, it is determined whether the action acquired in step S805 is export. If it is an export, the process proceeds to step S814. If it is not export, that is, if the action is printing, the process proceeds to step S817.

  In step S814, the form ID to be exported is acquired from the form ID 1503 of the template management information master in FIG. 15, and the form of the latest generation among the forms corresponding to the form ID is searched from the form file 213. Then, the text data of the retrieved form is output to the RAM 202 or the external memory 211 (processing execution). Note that the export can be configured such that when the action is set in FIG. 6, the export area is set by the client PC 101 or 102, and the text data included in the area is acquired and exported from the export area. is there.

  As the export, it is possible to export in a predetermined file format such as a format that can be displayed on the display unit 210 of the client PC 101 or 102 or a comma-delimited CSV.

  In step S815, the export result indicating that the export has been completed is transmitted to the client PC 101 or 102 that has executed the action.

  In step S816, the export result is displayed as shown in FIG. Further, when the result display button is pressed, the text data stored in the RAM 202 or the external memory 211 is transmitted from the form server 100 and displayed.

  In step S817, the form ID to be printed is acquired from the form ID 1503 of the template management information master in FIG. 15, and the form of the latest generation among the forms corresponding to the form ID is searched from the form file 213. The retrieved form is printed (process execution) via a printer driver stored in advance in a printing apparatus (not shown). Note that the print destination when executing printing is set by the client PCs 101 and 102 when the action is set in FIG. 6, and is stored in the template management information master in FIG.

  In step S818, the printing result indicating that the printing has been executed is transmitted to the client PC 101 or 102 that has executed the action.

  In step S819, the print result is displayed on the display unit 210 in the same manner as the export result in FIG.

  In step S807 and step S813, the action is determined in the order of display, export, and print. However, the order of determination such as the order of export, print, and display may be any order.

  Next, exemplary screens displayed on the display unit 210 of the client PCs 101 and 102 will be described with reference to FIGS.

  FIG. 9 shows a screen displayed on the display unit 210 when a display action is executed when the business template is executed.

  FIG. 10 is an export result display screen displayed on the display unit 210 when an export action is executed when a business template is executed.

  FIG. 11 is an initial display screen displayed on the display unit 210 before selecting a business template.

  FIG. 12 is a screen example of a template list screen that is displayed when there is no template information of the logged-in user. The screen is displayed on the display unit 210 when the template button 1102 is pressed.

  FIG. 13 is a screen example of the template list screen when the template information of the logged-in user is displayed and the template information is added by the user. A template list screen 1307 is an example of a screen when template information is added by pressing the business template creation button 1202 on the template list screen 1301 and the add button 1304 from the form list.

  In addition, a delete button 1305 is provided. By pressing the delete button 1305, a business template checked in the check box 1302 can be deleted. Further, by pressing a delete button 1305, a form checked in the check box 1303 can be deleted.

  When template information is added on the template list screen 1301, a save button 1311 is displayed on the template list screen 1307. By pressing this save button 1311, the template information added by the client PC 101 or 102 is stored in the form server. 100.

  FIG. 14 is an example of a screen when a check is input to the check box 1401 of the “business” business template on the template list screen 1307. When the execution button 1402 is pressed, the demo form 1 (display) and the demo are displayed. Form 1 (export), demo form 2 (export), and demo form 3 (print) are executed.

  FIG. 15 is a template management information master managed for each user, and stores business templates and forms for executing actions and set actions. The template management information master includes a template ID 1501, a business template name 1502, a form ID 1503, a form name 1504, an action 1505, and an action order 1506. The template management information master is stored in a DB (database) 215 of the form server 100.

[Second Embodiment]
Next, an embodiment in which a search is entered in the action will be described. In the first embodiment, the template is executed according to the user's specification. In the present embodiment, an embodiment will be described in which the form is executed in accordance with registration of the form in addition to the user's specification.

Hereinafter, the second embodiment will be described with reference to FIGS.
Note that FIG. 6 of the first embodiment is replaced with FIG. 16, and FIG. 8 is replaced with FIG. Regarding the other drawings, the first embodiment and the second embodiment are equivalent, and the description thereof is omitted. Further, the same steps as those in the first embodiment are given the same step numbers and description thereof is omitted.

  The CPU of the form server 100 processes each step executed by the form server of the flowchart described later, and the CPU of the client PC 101 or 102 processes each step executed by the client PC of the flowchart described later.

  A process for setting a search action in a template and setting an action execution method (manual / automatic) will be described with reference to FIG. Steps S601 to S614 are the same as the processing in FIG.

  However, in the action setting in step S614, “search” can be set as indicated by 1701 in FIG. 17, and in addition to display, export, and printing, the CPU of the client PC sets the “search” setting according to the user's specification. Do.

  In step S1601, in order to determine whether or not action contents (display, export, print, and search) are to be automatically performed, an input of a setting for whether or not to execute automatically in accordance with a user instruction is accepted (for automatic execution). Execution settings). Automatic execution means that form data is output to a form server 100 from a mainframe (not shown), received by the form server 100, a form file is generated, and a template action is executed at the timing registered in the external memory 211. It is to be.

  In step 1602, in accordance with pressing of the save button 1311 in FIG. 17, additional template information including the added business template and form information such as form name, action number, action content, and action execution flag for automatic action execution is transmitted to the form server 100. To do. When the form server 100 receives the additional template information, it registers the additional template information in the template management information master of FIG. In other words, the processing in step S1615 is the template identification information (template ID) of the added business template, the form identification information (form ID or form name) of the set electronic form, the processing content (action content), and the processing execution flag ( Action execution information) is transmitted to the form server 100. The form server 100 corresponding to the process of step S1602 includes template identification information (template ID) of the added business template, form identification information (form ID and form name) of the set electronic form, and processing contents (action Contents) and process execution information (action execution flag) are received, and the form identification information and the process contents are stored in the template management information master of FIG. 15 according to the template identification information.

  In the present embodiment, the items 1701 “Search” action and 1702 “Automatic execution (action execution information)” are added to the template list screen 1301 of FIG. Reference numeral 1301 in FIG. 17 shows an example in which the demo form 3 is set in the business template “sales”, and the action “search” is set in the demo form 3, and 1307 in FIG. In this example, a template of “sales management” is added to the above, demo reports 4 and 5 are set in “sales management”, and automatic execution is set in both.

  The action 1701 in FIG. 17 corresponds to the action 1505 in FIG. Further, automatic execution (action execution information) 1702 and 1703 are stored corresponding to the action flag master 1902.

  When search is selected in action 1701, a screen for setting a search template in FIG. 23 is displayed. When a search template (this search template is set in advance according to the input from FIG. 22) is selected in 2301, the template contents (search conditions) are displayed in 2302, so which search condition (search template) is used. Can be specified.

  FIG. 22 is a screen for setting (creating) a search template to be selected in FIG. The search template is set in the search condition setting screen 2201 and the search template name is set in 2202. This search template is stored in the external memory of the form server 100. When the search template name is displayed in FIG. 23, the search template name and search conditions stored in the form server 100 are acquired from the form server 100 and displayed. When a search template is selected in FIG. 23, the template ID currently specified in the search template management master in FIG. 21, the form ID of the form in which the search action is specified, and the selected search template name are 2101 and 2102, respectively. Saved in 2103

  Next, template execution processing according to the second embodiment will be described with reference to FIG. Steps S801 to S819 are the same as the processing in FIG.

  In this embodiment, there are processing for executing an action by selecting a template according to a user instruction in step S801 and processing for executing an action by registering a form file in the form server 100 in step S1801. The processing for executing an action by selecting a template according to the user's instruction in step S801 has been described in the first embodiment, and thus the description thereof is omitted.

  In step S1801, it is determined whether a form has been registered (registration determination). More specifically, the CPU 201 detects that a new form file is stored in the external memory 211. If detected, the process moves to step S1802. The detection of the form file may be the timing at which it is detected that it is stored in the external memory 211, or the external memory is searched for a newly added form file at a predetermined interval (time). It may be the timing when the search can be performed.

  In step S1802, whether the form file detected in step S1801 is new or is a form file to which a generation (in the form server, for example, a monthly report file is managed as a generation in a group called 2010 monthly report) is added. judge. If it is detected that a generation has been added, the process proceeds to step S1803. The form server has management information for managing form files (stored in an external memory), and manages which form file is added as which group as a form ID.

  In step S1803, the form server 100 acquires the form ID of the detected form file from the management information of the form file. The form ID may be configured to be stored in the form file, and the form ID may be acquired. That is, the form ID may be acquired using any method.

  In step S1804, the template management information master (DB) in FIG. 19 is referred to, and it is determined whether or not the form ID received in step 1803 matches the form ID registered in the template management information master (DB). If they match, the process proceeds to step S1805. If they do not match, the process ends.

  In step S1805, the template ID stored corresponding to the form ID matched in step 1805 is acquired, and it is determined whether or not the template ID matches the template ID of the action flag master in FIG. If they match, the process proceeds to step S1806, and if they do not match, the process ends.

In step S1806, the action execution method stored corresponding to the template ID matched in step S1805 is acquired from the action flag master of FIG. 20, and whether or not the action set in association with the template is automatically executed. (Electronic form determination). Note that the action execution method is automatic or manual action execution flag 1902. An action execution method is registered as an action execution flag in 1902 in the action flag master of FIG. If the action execution method is automatic, the process proceeds to step S1807. If the action execution method is manual, the process is terminated because automatic execution is not performed. In the case of manual operation, an action is executed by selecting a template in step S801.
Steps S1803 to S1806 indicate whether or not the registered form file is a form included in the automatically executed template according to the form ID of the group to which the form file belongs when it is determined that the form file is registered. This is a process for determining.

  Furthermore, exemplifying the process for determining automatic execution, when the form ID = DEMO001 is acquired in step S1803, the template management information master (DB) in FIG. 19 is referred to and matches the column 1503 of the template management information master. Check the form ID. If they match, the template ID corresponding to the form ID = DEMO001 is acquired from the row 1501 (the template ID corresponding to the form ID = DEMO001 is TEN001). When the template ID is acquired, the action flag master of FIG. 20 is referred to, the template ID = TEN001 is referred to from the column 1901, and the action execution flag is acquired from the line 1902. Since the action execution flag of template ID = TEN001 is automatic, the process proceeds to step S1807 when template ID = TEN001.

  In step S1807, if the user is not logged in, the client PC 101 or 102 and the form server 100 are not in session, so the form file cannot be transmitted to the client PC and displayed. It is determined whether or not the user is logged in.

  When the user logs in to the form server, the form server establishes a session with the client PC to which the user has logged in. The form server manages the logged-in user ID and manages which user is logged in with which client PC and a session is established.

  Further, since the template management information master (DB) in FIG. 19 is managed for each user (managed in association with the user ID), a user ID corresponding to an automatically executed action can be acquired. By comparing this user ID with the managed logged-in user ID, it can be determined whether or not the user is logged in.

  If it is determined in step S1807 that the user is logged in, it can be automatically executed, and the process proceeds to step S805. That is, when the user is logged in and the registered form file is included in the template to be automatically executed, the processing contents of the template are executed without instructing execution of the template on the client PC.

  If it is determined in step S1807 that the user is not logged in, the process moves to step S1808, and an email notifying that the user is not logged in is transmitted. The form server 100 manages user information (user ID, password, mail address), and sends a mail to a mail server (not shown) by using a mail address that can be acquired from this user information, and is logged in. Wait until The user who receives the mail logs in to the form server from the client PC. If login is detected, the process proceeds to step S805. If there is no login for a predetermined time, it is also possible to configure the processing to be terminated so that automatic execution is not performed. In the case of automatic execution, it is assumed in step S805 that an action is acquired from the template ID whose form ID matches in step S1804.

  Since the “display”, “export”, and “print” actions in steps S805 to S819 have been described in the first embodiment, description thereof will be omitted in this embodiment, and search processing added in this embodiment will be described.

  In step S1809, it is determined whether or not the action acquired in step S805 is a search. If the action is not a search but printing, the process proceeds to step S817 described in the first embodiment. If the acquired action is a search, the process proceeds to step S1810.

  In step S1810, the template ID of the currently executed action is compared with the template ID 2101 of the search template management master in FIG. 21, and the search template name 2103 of the matched record is acquired. A search condition corresponding to the search template name 2103 is acquired from the external memory 211, a form file group managed by generation is specified from the form ID of the matched record, and a form file matching the condition is searched.

  In step S1811, a search result that is a list of searched form files (a list of bibliographic information such as form ID, form name, form registration date and time) is transmitted to the client PCs 101 and 102.

  In step S1812, the search results received from the form server 100 are displayed on the display units of the client PCs 101 and 102. Thereafter, when it is detected that the next action execution button 901 has been pressed according to the user's operation, the process proceeds to step S810.

  According to the above configuration, it is possible to increase the efficiency of work on a form by registering the form to be processed and the processing content for the form so that a plurality of forms can be collectively processed.

  Also, by registering the processing content and processing procedure for a form, the efficiency of work on the form can be increased.

  In particular, it is possible to register forms used for work together for each work and set processing (display, export, print, display, etc.) of each form. Thus, by selecting a business, work related to a form can be executed in a batch, and work efficiency can be improved. In addition, if a form file used for business is registered as a template, the form file can be registered and automatically executed at the same time, so that it is possible to improve work efficiency for a user who performs a routine work.

  It should be noted that the configuration and contents of the various data described above are not limited to this, and it goes without saying that the various data and configurations are configured according to the application and purpose.

  Although one embodiment has been described above, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or recording medium, and specifically includes a plurality of devices. The present invention may be applied to a system including a single device.

  Further, the program according to the present invention is a program that allows a computer to execute the processing methods of FIGS. 5 to 8, and the storage medium according to the present invention executes the processing methods of FIGS. 5 to 8, 16, and 18. Possible programs are stored. The program in the present invention may be a program for each processing method of each device in FIGS. 5 to 8, 16, and 18.

  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. It goes without saying that the object of the present invention can also be achieved by executing the reading.

  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 (operating system) operating on the computer based on an instruction of the program is actually It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the processing and the processing is 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 by 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.

100 Form server 101 Client PC 1
102 Client PC 2
103 Network 201 CPU
202 RAM
203 ROM
210 Display unit 215 DB
211 External memory

Claims (6)

An electronic form server that manages electronic forms,
Corresponding in order to execute a plurality of the electronic form in pairs to desired processing sequentially, and the document identification information of the electronic document executing the process, be applied to the electronic document, and a processing set of a plurality of different process optionally Storage means for storing a template defining the execution order of the associated processing ;
And document identification information of the previous SL electronic form which is stored as the template by the storage means, and processing associated with the document identification information obtaining means for obtaining the execution order of the process,
As electronic form that is stored in the template in the order of execution of the processing is processed, using the electronic document acquired based on the acquired document identification information by the acquisition unit, the processing that is correlated to the document identification information An electronic form server comprising processing execution means for executing. An electronic form determination unit that determines whether the template stored in the storage unit includes form identification information of the electronic form when the electronic form is registered in the electronic form server;
The process execution means includes
If it is determined that the document identification information of the electronic document is included in the template by the electronic document determination unit, by using the electronic document, the process associated with the acquired the document identification information by the acquisition unit The electronic form server according to claim 1, wherein the electronic form server is executed. In order to register a desired processing with respect to a plurality of electronic document as a template to be executed sequentially, and document identification information of the electronic document executing the process, it applies to the electronic document, which is arbitrarily set from a plurality of different treatment process preparative association, the execution order of the associated process, electronic form server according to claim 1 or 2, further comprising a reception means for receiving a designation from the user. The plurality of different processes are
Including at least one of a process for searching the electronic form, a process for displaying the electronic form, and a process for outputting data included in the electronic form to a file having a format different from that of the electronic form.
The electronic form server according to any one of claims 1 to 3. And managing electronic form, set the desired processing against a plurality of electronic document to be executed sequentially, and document identification information of the electronic document executing the process, applies to the electronic form, optionally from a plurality of different processing by associating the processing, a processing method in an electronic document server comprising a storage means for storing a template that defines the order of execution of the associated process,
The electronic form server is
And document identification information of the previous SL electronic form which is stored as the template by the storage means, and processing associated with the document identification information, an acquisition step of acquiring the execution order of the process,
As electronic form that is stored in the template in the order of execution of the processing is processed, using the electronic document acquired based on the acquired document identification information by the acquisition step, a process that is correlated to the document identification information And a processing execution step to be executed. And managing electronic form, set the desired processing against a plurality of electronic document to be executed sequentially, and document identification information of the electronic document executing the process, applies to the electronic form, optionally from a plurality of different processing associating the process that is, a program executable in the electronic form server comprising a storage means for storing the template that defines the execution order of the processes associated,
The electronic form server
And document identification information of the previous SL electronic form which is stored as the template by the storage means, and processing associated with the document identification information obtaining means for obtaining the execution order of the process,
As electronic form that is stored in the template in the order of execution of the processing is processed, using the electronic document acquired based on the acquired document identification information by the acquisition unit, the processing that is correlated to the document identification information A program which functions as a process execution means to be executed.

Images