JP2016071859A - Information processing system, control method of information processing system, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce the possibility that template data including a plurality of pieces of part data is used for document data without satisfying conditions for use of the template data indicating whether or not the individual use of each piece of the part data included in the template data is permitted.SOLUTION: When template data included in document data that is created on a creation screen for creating document data does not satisfy conditions for use, an information processing system notifies an information processing apparatus of the effect.SELECTED DRAWING: Figure 12

Description

  The present invention relates to an information processing system, a control method for the information processing system, and a program, and in particular, whether template data including a plurality of part data permits individual use of each part data included in the template data. It is related with the mechanism which can reduce possibility of being used for document data, without satisfy | filling the usage condition of the said template data which shows.

  When creating electronic document data that is commonly used in a company, in order to facilitate the creation of electronic document data (hereinafter abbreviated as electronic document), part data (also referred to as part data) to be laid out in the electronic document is used. (Hereinafter abbreviated as “parts”) and template data created by combining multiple parts (hereinafter abbreviated as “template”) are created in advance by the person in charge of creating each data, and the person in charge of creating the electronic document An electronic document is created by laying out the parts and templates on each page of electronic document data.

  In that case, the person in charge of creating each data publishes the created part or template for creating an electronic document, and the person in charge of creating the electronic document selects the published part or template and performs layout processing. To create electronic document data.

  In addition, in any case of parts, templates, and electronic documents, data widely used in the company is created by the person in charge of data creation and then released with the approval of the approver. ing.

  Patent Document 1 discloses a document processing system capable of creating a document and approving the document.

JP 2000-90181 A

  By the way, among the templates that have been approved by the approver, there is a template in which the parts are overlapped (hereinafter, the template in which the parts are overlapped is referred to as template A).

  For a template in which parts overlap each other like the template A, even if the template is approved by the approver, the person in charge of creating the electronic document using the template A creates the template A Create an electronic document using template A with only the part (hereinafter referred to as part C) over which part B overlapped by deleting the overlapping part (hereinafter referred to as part B). May not be approved by the approver.

  This is because, if the part data B is deleted from the template A, the part of the baht C that was not visible due to the overlapping of the parts B will be visible by deleting the part B.

  However, whether the approver permits the person in charge of creating the electronic document to use the template A with only the part A from which the part B is deleted when the electronic document is created using the template A. Since it is not known whether the electronic document may be created using the template A with only the part C, it may not be known.

  Since Patent Document 1 does not describe a countermeasure for the above-described problem, whether or not an electronic document may be created using the template A including only the part C when the electronic document is created using the template A is determined. The electronic document creator may still not know.

  Also, among the templates created by the person in charge of creating the template data and approved by the approver, even if the part B and the part C do not overlap, the part C is used when the part B is used. It may not be deleted.

  Specifically, for example, if part B is a character of a company and part C is copyrighted, part B may be changed to another character of the company, but part B is used. In some cases, part C must be used together.

  Further, for example, when part B is a part indicating a discount such as “5 discount” and part C is a part indicating a discount period, when part B is used, it is necessary to use part C together. .

  In the above two specific examples, the approver and the person in charge of template data creation approve the template assuming that parts B and C are used together. Although there is a risk of unintentional use by the person in charge of creating the template data, the person in charge of creating the electronic document uses the template with only the part C from which the part B has been deleted when creating the electronic document using the template. Since it is not known whether or not the approver permits the use of the document, there is a possibility that it may not be determined whether or not an electronic document may be created using the template of only the part B.

The present invention uses template data including a plurality of part data for document data without satisfying the use condition of the template data indicating whether or not each part data included in the template data is allowed to be used alone. It is an object to provide a mechanism capable of reducing the possibility of being performed.

  The present invention is template data that includes a plurality of parts data, and includes template data used for creating document data, and whether or not each part data included in the template data is permitted to be used alone An information processing system that manages use conditions of template data, the display control means for controlling to display a creation screen for creating document data, and via the creation screen displayed by the display control means A receiving unit that receives an instruction to edit the template data included in the created document data, and a determining unit that determines whether or not the template data edited according to the editing instruction received by the receiving unit satisfies the use condition. And according to the editing instruction received by the receiving means by the determining means Collecting template data, if it is determined not to satisfy the conditions of use, characterized in that it comprises a notifying means for notifying to that effect.

  Further, the present invention is template data including a plurality of part data, and the template data used for creating the document data and whether or not each part data included in the template data is permitted to be used alone. A display control process for controlling an information processing system to manage use conditions of the template data to be displayed, wherein the display control means of the information processing system controls to display a creation screen for creating document data A receiving step in which the receiving unit of the information processing system receives an editing instruction for the template data included in the document data created via the creation screen displayed by the display control step; and a determination of the information processing system Template data edited by the means according to the editing instruction received in the receiving step A determination step for determining whether or not the use condition is satisfied, and template data edited by the notification unit of the information processing system according to the edit instruction received in the reception step by the determination step, And a notification step of notifying that when it is determined that the condition is not satisfied.

  Further, the present invention is template data including a plurality of part data, and the template data used for creating the document data and whether or not each part data included in the template data is permitted to be used alone. A program for causing a computer of the information processing system to execute a control method of the information processing system for managing the use conditions of the template data to be displayed, the computer displaying a creation screen for creating document data Display control means for controlling to perform, receiving means for receiving an instruction to edit the template data included in the document data created via the creation screen displayed by the display control means, and editing accepted by the receiving means The template data edited according to the instructions satisfies the use conditions. A determination means for determining whether or not the template data edited by the determination means according to the editing instruction received by the reception means does not satisfy the use condition It is made to function as a notification means to do.

  According to the present invention, template data including a plurality of part data is document data without satisfying the use condition of the template data indicating whether or not each part data included in the template data is allowed to be used alone. It is possible to reduce the possibility of being used.

It is a system configuration diagram showing an example of a document management system of the present invention. FIG. 2 is a diagram illustrating an example of a hardware configuration of an information processing apparatus applicable as the document management server 101 and the client terminal 102 in FIG. 1. It is a figure which shows an example of the structure of the electronic document data produced with the document production assistance system of this invention. It is a figure which shows an example of the process in which the template preparation person who produces template data operates the client terminal 102, and performs the approval request which approves template data in the document preparation assistance system of this application. It is a figure which shows an example of the process in which the template approver who approves template data approves template data in the document preparation assistance system of this application. It is a figure which shows an example of the process in which the document preparation person who produces document data makes the approval request which approves document data by producing document data in the document creation assistance system of this application. It is a figure which shows an example of the process in which the document approver who approves document data approves document data in the document preparation assistance system of this application. It is a figure which shows an example of the screen displayed on the display 210 of the client terminal 102 of a template preparation person in the document preparation assistance system of this application. It is a figure which shows an example of the template data list screen which the template approver is in charge of the approval displayed on the display 210 of the client terminal 102 of the template approver in the document creation support system of the present application. It is a figure which shows an example of the approval screen of the template data which the template approver is in charge of approval displayed on the display 210 of the client terminal 102 of the template approver in the document creation support system of the present application. 3 is a diagram illustrating an example of a data table for managing electronic document data managed by an external memory 211 of the document management server 101 in the document creation support system of the present application. FIG. It is a figure which shows an example of the screen which a document creation person produces document data displayed on the display 210 of the client terminal 102 of a document creation person in the document creation support system of this application. It is a figure which shows an example of the approval screen of the document data which the document approver is in charge of approval displayed on the display 210 of the client terminal 102 of the document approver in the document creation support system of the present application. 3 is a diagram illustrating an example of a data table for managing part data managed by an external memory 211 of the document management server 101 in the document creation support system of the present application. FIG. 3 is a diagram illustrating an example of a data table for managing template data managed by an external memory 211 of the document management server 101 in the document creation support system of the present application. FIG. It is a figure which shows an example of the screen displayed on the display 210 of the client terminal 102 of a document preparation person in charge or a document approver in the document preparation assistance system of this application. 6 is a diagram illustrating an example of a data table of editing information stored in the external memory 211 of the client terminal 102 in step S602 in the document creation support system of the present application. FIG. It is a figure which shows an example of the list screen of the document data which the document approver is in charge of approval displayed on the display 210 of the client terminal 102 of the document approver in the document creation support system of the present application. It is a figure which shows an example of the approval screen of the template data which the template approver is in charge of approval displayed on the display 210 of the client terminal 102 of the template approver in the document creation support system of the present application. It is a figure which shows an example of the screen which a document creation person produces document data displayed on the display 210 of the client terminal 102 of a document creation person in the document creation support system of this application. It is a figure which shows an example of the approval screen of the document data which the document approver is in charge of approval displayed on the display 210 of the client terminal 102 of the document approver in the document creation support system of the present application. It is a figure which shows an example of the screen displayed on the display 210 of the client terminal 102 of a document preparation person in charge or a document approver in the document preparation assistance system of this application. It is a figure which shows an example of the approval screen of the template data which the template approver is in charge of approval displayed on the display 210 of the client terminal 102 of the template approver in the document creation support system of the present application. 2 is a diagram illustrating an example of a data table of template data managed by an external memory 211 of the document management server 101 in the document creation support system of the present application. FIG. 2 is a diagram illustrating an example of a data table of template data managed by an external memory 211 of the document management server 101 in the document creation support system of the present application. FIG.

  DESCRIPTION OF EXEMPLARY EMBODIMENTS Hereinafter, preferred embodiments to which the invention is applied will be described in detail with reference to the accompanying drawings. First, FIG. 1 will be described.

FIG. 1 is a system configuration diagram showing an example of a configuration of a document management system (information processing system) in an embodiment of the present invention.
In the figure, reference numeral 101 denotes a document management server which functions as an information processing apparatus in the present invention.

  Reference numeral 102 denotes a client terminal, which is used by a person in charge of data creation to create electronic document data, template data, part data, and the like in the document management system. The client terminal 102 is also used by the approver to perform approval processing for determining whether or not other users can use the data created by the person in charge of creating each data.

  Reference numeral 103 denotes a network such as a LAN (Local Area Network) for connecting the document management server 101 and the client terminal 102 to each other so that data communication is possible.

  FIG. 2 is a diagram illustrating an example of a hardware configuration of an information processing apparatus applicable as the document management server 101 and the client terminal 102 in FIG.

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

  The CPU 201 implements various operations by loading a program necessary for execution of processing into the RAM 203 and executing the program. An input controller (input C) 205 controls input from a pointing device such as an input device 209 or a mouse (not shown). A video controller (VC) 206 controls display on a display device such as the display 210. The display device is, for example, a CRT display or a liquid crystal display. These are used by the administrator as needed. The present invention is not directly related.

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

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

  Note that the CPU 201 enables display on the display 210 by executing outline font rasterization processing on a display information area in the RAM 203, for example. Further, the CPU 201 enables a user instruction with a mouse cursor (not shown) on the display 210.

A program used to execute the various processes of the present invention is recorded in the external memory 211 and is executed by the CPU 201 by being loaded into the RAM 203 as necessary. Furthermore, definition files and various information tables used by the program according to the present invention are stored in the external memory 211.
Next, the structure of electronic document data created by the document creation support system of the present application will be described with reference to FIG.

  FIG. 3 is a diagram showing an example of the structure of electronic document data created by the document creation support system of the present invention.

  In the document creation support system of the present application, electronic document data is created by arranging part data or template data formed by a plurality of part data at a desired position.

In the drawing, 300 represents one page of document data. One document data is created by arranging part data and template data in 300 according to the operation of the input device 209 by the user.
Reference numeral 301 denotes part data, which is data such as graphic data, photo data, and character data.

  Reference numeral 302 denotes template data formed by combining a plurality of part data. In FIG. 3, template data 1 is formed by combining part number 1 and part number 2. The creator of the template data can also create the part number 1, the part number 2, and the part number 6 as template data.

  The document data 300, the part data 301, and the template data 302 are stored and managed in the external memory 211 of the document management server 101 (data tables shown in FIGS. 11, 14, and 15 described later).

  FIG. 11 is a diagram illustrating an example of a data table for managing electronic document data managed by the external memory 211 of the document management server 101.

  A document management table 1100 in FIG. 11 is a data table of electronic document data created by the document management server 101 in accordance with a user operation and managed by the external memory 211 of the document management server 101. The document management table 1100 includes a document number 1101 and a page number 1102. , Template number 1103, part number 1104, coordinates 1105, creator ID 1106, approver ID 1107, status 1108, and the like.

The document number 1101 stores identification information for uniquely identifying electronic document data.
The page number 1102 stores a page number indicating the page number of the electronic document data.

  The template number 1103 stores a template number (corresponding to 1501 described later) used for creating the electronic document data.

  The part number 1104 stores a part number (corresponding to 1401 described later) used for creating the electronic document data. The part number included in the template is not stored in 1104 because it is stored in a data table in FIG. 15 (1502 in FIG. 15) described later.

  The coordinate 1105 stores information on the template number 1103 and the coordinates of the part number 1104 in the page of the electronic document data. The coordinates 1105 are the coordinates of the template number 1103 and the part number 1104 when the upper left coordinate of the page is (0, 0).

  The creator ID 1106 stores the user ID of the creator who created the electronic document data. The approver ID 1107 stores the user ID of the approver who approves the electronic document data.

  The status 1108 stores the approval status of the electronic document data by the approver. The status 1108 stores information “unapproved” if the approver has not yet approved the electronic document data, and information “approved” if the approver has approved the electronic document data. If the approver has rejected the electronic document data, information “rejected” is stored.

  FIG. 14 is a diagram illustrating an example of a data table for managing part data managed by the external memory 211 of the document management server 101.

  A parts management table 1400 in FIG. 14 is a data table for managing parts data created by the document management server 101 and managed by the external memory 211 in accordance with a user operation. The parts management table 1400 includes a part number 1401, a creator ID 1402, It consists of an approver ID 1403, a status 1404, and the like.

The part number 1401 stores a part number (corresponding to 1104) for uniquely identifying the part data.
The creator ID 1402 stores the user ID of the creator who created the part data.
The approver ID 1403 stores the user ID of the approver who approves the part data.

  The status 1404 stores the approval status by the approver of the part data. In the status 1404, information “unapproved” is stored if the approver has not yet approved the part data, and information “approved” is stored if the approver has approved the part data, If the approver has denied the part data, information “rejected” is stored.

  FIG. 15 is a diagram illustrating an example of a data table for managing template data managed by the external memory 211 of the document management server 101.

  A template management table 1500 in FIG. 15 is a data table for managing template data created by the document management server 101 and managed in the external memory 211 according to a user operation. The template management table 1500 includes a template number 1501, a part number 1502, and a layer. Information 1503, coordinates 1504, creation person ID 1505, approver ID 1506, status 1507, and the like.

  15 to 1505 in FIG. 15 are stored in the external memory 211 of the document management server 101 when the person in charge of template data creation creates the template data. Reference numerals 1506 and 1507 in FIG. When the template data is approved or rejected, it is stored in the external memory 211 of the document management server 101.

  The template number 1501 stores a template number (corresponding to 1103) for uniquely identifying template data. The part number 1502 stores the part number used to create the template data.

  The layer information 1503 stores the order in which the part data is arranged when the template data is created. More specifically, the first placed part data (bottom layer) is “0”, and thereafter, “1”, “2”,... . Note that the layer information 1503 is stored regardless of whether each part data overlaps.

  The coordinate 1504 stores the upper left coordinate (X, Y) of the part data arranged in the template data, with the upper left of the entire template data (outer frame) being the coordinate reference (0.0). The creator ID 1505 stores the user ID of the creator who created the template data. The approver ID 1506 stores the user ID of the approver who approves the template data.

  The status 1507 stores the approval status by the template approver. Specifically, the status 1507 stores information “unapproved” if the approver has not approved the template data yet, and “approved” if the approver has approved the template data. If the information is stored and the approver has rejected the template data, the information “rejected” is stored.

  The overlap approval information table 1500-1 in FIG. 15 is a data table created by the document management server 101 and managed in the external memory 211 in accordance with the operation through the screen in FIG. 10 by the approver of the template data. 15 is a data table for managing whether or not to permit use in a state where there is no upper part for the part data in which other parts overlap among the part data included in the template data in 1500. is there.

  In addition, among the part data included in the template data in 1500 of FIG. 15, which part data is the part data with which other parts overlap is determined by 1501 of FIG. Then, it is determined whether or not the part data overlaps according to the size information of each part data (rectangular information on the outer periphery of the part data).

  Also, when the part data overlaps, which part data is the front is determined by determining that the part data having the larger layer information 1503 is the front and the part data having the smaller layer information 1503 is the front. It is determined that the part data is the back, that is, the other part data is overlapped.

  The overlap approval information table 1500-1 is composed of an approval target part number 1508, an overlap part number 1509, a template number 1510, an approver ID 1511, whether or not a higher part can be used 1512, and the like.

  In the part number 1508 to be approved, the part number (corresponding to 1502 in FIG. 15) of the part data in which other parts overlap among the part data included in the template data 1500 in FIG. 15 is stored.

  The overlapping part number 1509 stores the part number of the part data (corresponding to 1502 in FIG. 15) that overlaps the part data 1508 out of the part data included in the template data 1500 in FIG.

  The template number 1510 stores the template data number (corresponding to 1501 in FIG. 15) in which the part data 1508 is arranged. That is, the template data whose number is stored in the template number 1510 can be said to be template data formed by overlapping a plurality of part data.

  The approver ID 1511 stores the user ID of the template approver where the part data 1508 is arranged, that is, the user ID of the same approver as the approver ID 1506.

  Information indicating whether or not the template data including the part data 1508 may be used in the state 1515 of whether or not the upper part can be used is used in the state where the part data 1508 is not overlapped with the part data 1509 is stored. If the part data of 1508 is not overlapped with the part data of 1509 and the template data including the part data of 1508 may be used, the information “OK” is stored in 1512, and the part data of 1508 is stored in 1509. If the template data including the part data 1508 should not be used in a state where the part data is not overlapped, information “impossible” is stored in 1512.

  Note that “the state data of 1509 do not overlap” means that the part data of 1509 is deleted or the order of the layers 1508 and 1509 is changed, that is, the part 1508 is in front of the part 1509. In this case, template data including part data 1508 is used.

  Next, detailed processing of the present embodiment will be described with reference to FIGS. 4 to 7 is realized by loading a program stored in the external memory 211 into the RAM 203 and executing it by the CPU of each device.

  FIG. 4 is a diagram illustrating an example of a process in which a template creation person who creates template data operates the client terminal 102 to create template data and issues an approval request for approving the template data.

  In step S <b> 401, the client terminal 102 starts a browser and logs into the document management server 101. The login is performed by inputting the user ID and password of the person in charge of template creation and executing authentication. After login, a template creation screen (FIG. 8 to be described later) for creating template data is received from the document management server 101 and displayed on the display 210 of the client terminal 102.

  In step S <b> 402, the client terminal 102 accepts an instruction to place part data used for template data in accordance with an operation of the mouse or the like by the user.

  In step S403, the client terminal 102 has received an input of an approval request for the template data created by placing the parts in step S402 from the user via the screen shown in FIG. 8 (802 in FIG. 8) to be described later. Determine whether.

  If the input of the template data approval request is received from the user, the process proceeds to step S404. If the input of the template data approval request is not received from the user, the process returns to step S402.

  In step S404, the client terminal 102 transmits an approval request for the template data created by arranging the parts in step S402 to the client terminal 102 of the template approver, and ends the process in FIG.

The template approval request may be sent directly from the template creator's client terminal 102 to the template authorizer's client terminal 102 by e-mail, or may be temporarily sent from the template creator's client terminal 102 to the document management server. An approval request may be transmitted to 101 and a template approval request may be transmitted from the document management server 101 to a template approval person managed in the external memory 211 of the document management server 101.
The approval request includes a URL for accessing the document management server 101.

  Here, with reference to FIG. 8, a screen on which the person in charge of template creation creates template data by operating the client terminal 102 and makes an approval request for approving the template data will be described.

  FIG. 8 shows a screen displayed on the display 210 of the client terminal 102 of the template creator. The template creator operates the input device 209 of the client terminal 102 to create template data. This is a screen for requesting approval to be approved.

  When the button 801 is pressed by an operation of the input device 209 of the client terminal 102 by the person in charge of template creation, from the part data stored in the external memory 211 of the client terminal 102 or the external memory 211 of the document management server 101 The person in charge of template creation can select part data to be used for template data. The part data selected by the person in charge of template creation can be arranged at a location desired by the person in charge of template creation as long as it is within the frame 803 of the template data.

  When the button 802 is pressed by an operation of the input device 209 of the client terminal 102 by the person in charge of template creation, an approval request for the template data created by placing the part data in the frame 803 is sent to the document management server 101. Or the template data created by the person in charge of template creation is stored in the template management table 1500 shown in FIG.

  Next, a process in which the approver approves the template data requested by the template creator in the process of FIG. 4 will be described with reference to FIG.

  FIG. 5 is a diagram illustrating an example of a process in which a template approver who approves template data approves template data.

  In step S501, according to the operation of the input device 209 by the template approver, the client terminal 102 selects the URL described in the approval request mail transmitted from the client terminal 102 of the template creator in step S404 in FIG. As a result, the browser is started and the document management server 101 is logged in.

  The login is performed by inputting the user ID and password of the template approver and executing authentication. After login, the main screen of the document management system is received from the document management server 101 and displayed on the display 210 of the client terminal 102 of the template approver.

  In step S502, the client terminal 102 receives a request from the template approver via the main screen of the document management system, and receives a request for obtaining a list screen of the template data for which the template approver logged in step S501 is in charge of approval. Send to server 101.

  In step S503, the document management server 101 receives a template data list screen acquisition request for which the template approver logged in in step S501 is in charge of approval from the client terminal 102, and the template approver who has logged in in step S501 A list screen of template data that is in charge of approval is generated and transmitted to the client terminal 102.

  More specifically, the document management server 101 generates a list screen of template data in which the user ID of the template approver logged in in step S501 matches the approver ID 1506 in FIG. 15 and the status 1507 is unapproved template data. And transmitted to the client terminal 102.

  In step S <b> 504, the client terminal 102 receives a list screen of template data for which the template approver logged in step S <b> 501 is responsible for approval from the document management server 101, and displays it on the display 210 of the client terminal 102. The screen displayed on the display 210 of the client terminal 102 in step S504 is FIG.

  In step S <b> 505, the client terminal 102 receives selection of template data to be approved from the template approver, and transmits an acquisition request for an approval screen for the template data selected by the template approver to the document management server 101. More specifically, the template data 901 to be approved by the template approver is selected by pressing the template data 901 in accordance with the operation of the input device 209 by the template approver among 901 in FIG. 9 described later.

  In step S506, the document management server 101 receives the template data information (template number) selected from the template approver in step S505.

  In step S507, the document management server 101 determines whether the template data specified by the template data information received in step S506 is formed by overlapping a plurality of part data. More specifically, the determination is made based on whether or not the template number of the template data is in the template number 1510 of 1500-1 in FIG.

  In step S507, if the template data specified by the template data information received in step S506 is formed by overlapping a plurality of part data, the process proceeds to step S508, and the template data information received in step S506. If the template data specified by is not formed by overlapping a plurality of part data, the process proceeds to step S509.

  Step S507 is an example of determination means for determining whether or not the template data requested for approval is formed by overlapping a plurality of part data in the present invention.

  In step S508, the document management server 101 adds display information regarding a plurality of overlapping part data included in the template data specified by the template data information received in step S506 to the approval screen for the template data. . The display information added in step S508 is, for example, 1003 to 1006 and 1008 in FIG.

  In step S509, the document management server 101 transmits to the client terminal 102 a template data approval screen specified by the template data information received in step S506.

  Step S509 is an example of display instruction means for instructing the client terminal to display an approval screen for approving the use of the template data requested for approval according to the display request from the client terminal in the present invention. When it is determined that they are formed by overlapping, a display instruction is given to display the approval screen to which display information indicating whether or not to permit use of the template data in a state where a plurality of part data does not overlap is added. This is an example of a display instruction unit, and when it is determined by the determination unit that it is formed by overlapping, an indication as to whether or not to permit use of the template data by exchanging a plurality of parts data layers It is an example of a display instruction means for instructing display of the approval screen to which information is added. Which is of an example of a receiving unit that receives a request to display the setting screen of the template data, including parts data.

  In step S <b> 510, the client terminal 102 receives the template data approval screen transmitted from the document management server 101 in step S <b> 509 and displays it on the display 210 of the client terminal 102.

  In step S511, the client terminal 102 inputs template data approval or template data denial (1001 and 1002 in FIG. 10 to be described later) on the template approval screen displayed on the display 210 of the client terminal 102 in step S510. This is accepted according to the operation of the input device 209 by the template approver. Approval here means to approve the disclosure of the template data so that other users can use it. The denial here means that the template data is not allowed to be disclosed so that other users can use it.

  If display information is added to the approval screen for the template data received from the document management server 101 in step S510, the client terminal 102 overlaps the overlapping part data in the template data. Selection of whether or not to allow the use of the template data by deleting the part data on the overlapping side or replacing the part data on the overlapping side with the part data on the overlapping side (see FIG. 10 to be described later) 1004) is also accepted according to the operation of the input device 209 by the template approver.

  Even if the display information is added to the template data approval screen received from the document management server 101 in step S510, the overlapping part data in the plurality of overlapping part data in the template. If it is not selected whether or not to allow the use of the template data by replacing the part data of the overlapping part with the part data of the overlapping part, Even if input from the template approver is accepted, an error message indicating that the selection has not been made is displayed on the template approval screen, and the template approver does not approve it.

  In step S512, the client terminal 102 determines whether or not an approval input has been received from the template approver in step S511.

  If the approval input from the template approver is accepted in step S511, the client terminal 102 transmits the approval information of the template data to the document management server in step S514, and the approval input from the template approver in step S511. If not accepted (that is, if a denial input is accepted), the client terminal 102 transmits denial information of the template data to the document management server 101 in step S513.

In step S515, the document management server 101 receives the approval / denial information of the template data from the client terminal 102, and stores the template data 1507 in which the template number 1501 matches the template data in the data table of FIG. Remember. In step S511, in the overlapping part data in the template, the part data on the overlapping side is deleted or the part data on the overlapping side is replaced with the part data on the overlapping side. When the selection of whether or not to allow use of template data (1004 in FIG. 10 described later) is also accepted, the information is stored in 1512 in 1500-1 of FIG.
When the process of step S515 ends, the process of FIG. 5 ends.

  Here, with reference to FIG. 9, a template data list screen, which is displayed on the display 210 of the client terminal 102 in step S504 of FIG.

  FIG. 9 is a view showing an example of a list screen of template data displayed on the display 210 of the client terminal 102 of the template approver, in which the template approver is in charge of approval. The screen of FIG. Is generated by the document management server 101 according to the data table.

  In FIG. 9, reference numeral 901 displays a thumbnail of template data for which the template approver is in charge of approval. Next to 901, the template number of the template data is displayed.

  When 901 is selected according to the operation of the input device 209 by the template approver, an approval screen for the selected template (FIG. 10 described later) is displayed on the display 210 of the client terminal 102 of the template approver.

  9, after the selection of 1004 on the screen of FIG. 10 to be described later when the template data for which the template approver is in charge includes the overlapping part data, 902 and 903 in FIG. When the approval button (1001) or the denial button (1002) is not pressed by the template approver, the return button (1007) is pressed by the template approver or when the return button (1007) is not selected. Is pressed by the template approver, information indicating that part data overlapping the template data is included and information indicating whether 1004 is selected are displayed. If 1004 is selected, information 903 is displayed. If 1004 is not selected, information 902 is displayed.

  By displaying information 902 and 903 in FIG. 9, information indicating that 1004 is not selected even though there is part data overlapping with the template data, or an approval button is displayed although 1004 is selected. The template approver can easily check the information indicating that the approval process is not completed because the (1001) or the denial button (1002) is not pressed from the template data list screen.

  Reference numeral 904 denotes a return button. When the return button 904 is pressed according to the operation of the input device 209 by the template approver, the screen returns to the main screen of the document management system.

Next, the template data approval screen displayed on the display 210 of the client terminal 102 in step S510 of FIG. 5 and used by the template approver in charge of approval will be described with reference to FIG.
<Description of FIG. 10>

  FIG. 10 is a diagram showing an example of a template data approval screen displayed on the display 210 of the client terminal 102 of the template approver, in which the template approver is in charge of approval. The screen in FIG. It is generated according to the data table.

  Reference numeral 1001 in FIG. 10 denotes an approval button. When the approval button 1001 is pressed according to the operation of the input device 209 by the template approver, the template data is approved.

  Reference numeral 1002 in FIG. 10 denotes a denial button. When the denial button 1002 is pressed according to the operation of the input device 209 by the template approver, the template data is denied.

  In FIG. 10, when 1003 includes overlapping part data, the part name including thumbnails of overlapping part data, the order in which the part data overlaps (layer information), and the template data Permits the use of the template data by deleting the overlapping part data or replacing the overlapping part data with the overlapping part data in multiple overlapping part data A button for accepting whether or not the template approver is selected according to the operation of the input device 209 by the template approver is displayed.

  1004 in FIG. 10 is the template in which the part data on the overlapping side is deleted or the part on the side overlapping the part data on the overlapping side is replaced in a plurality of overlapping part data in the template. This button accepts selection of whether or not to permit use of data in accordance with the operation of the input device 209 by the template approver.

  When the “permitted” button of 1004 in FIG. 10 is pressed according to the operation of the input device 209 by the template approver, the part data on the overlapping side is deleted from the overlapping part data in the template. Alternatively, it is permitted to use the template data by exchanging the overlapping part data with the overlapping part data.

  In addition, when the “don't allow” button 1004 in FIG. 10 is pressed according to the operation of the input device 209 by the template approver, the overlapping part data in a plurality of overlapping part data in the template Is not permitted to use the template data by deleting or replacing the overlapping part data with the overlapping part data.

  In 1004 of FIG. 10, the template approver approves the template because the part approver is in a state where a plurality of part data are overlapped by making it possible to accept the pressing of “not permitted” according to the operation of the input device 209 by the template approver. Regardless of the intention of the template approver, the user who creates document data using the template data deletes the overlapping part data in the overlapping part data in the template. Alternatively, the possibility of using the template data can be reduced by exchanging the overlapping part data with the overlapping part data.

  Note that the case where “not permitted” is pressed according to the operation of the input device 209 by the template approver in 1004 of FIG. 10 is, for example, in the case of FIG. 10 where the part data 001 of the part data 002 overlaps. , If there is a trademark of another company, or if the part data 002 is an image of a car and the part data 001 of the part data 002 overlaps with the car number, there is no limit to other users This is a case where there is information that should not be disclosed in the part where the part data 001 of the part data 002 overlaps.

  Reference numeral 1005 in FIG. 10 denotes a radio button for selecting part data to be displayed as a preview in 1006 described later when there are a plurality of overlapping part data in the template. A preview of the overlapping part data with the radio button 1005 selected is displayed in 1006 described later.

  When the overlapping part data is included in the template data, 1006 in FIG. 10 displays the overlapping part data side by side in parallel without overlapping each other. Furthermore, as for the part data where other part data overlaps, the part where the other part data overlaps is identified and displayed as 1008 in FIG. Thereby, it becomes easy for the template approver to recognize the part where the other part data overlaps, and it becomes easier to appropriately determine whether or not to approve the template.

  In this embodiment, as shown by 1008 in FIG. 10, the part where the other part data overlaps is identified and displayed with diagonal lines, but the template approver identifies the part where the other part data overlaps. As long as it is possible, the part where other part data overlaps may be blinked or displayed with color.

  Reference numeral 1007 in FIG. 10 denotes a return button. When the return button 1007 is pressed according to the operation of the input device 209 by the template approver, the screen returns to the template data list screen in FIG.

  Next, a process of creating document data by a person in charge of creating document data using the template data approved by the template approver in the process of FIG. 5 will be described with reference to FIG.

  FIG. 6 is a diagram illustrating an example of a process in which a document creation person who creates document data creates document data and issues an approval request to approve the document data.

  In step S <b> 601, the client terminal 102 starts a browser and logs in to the document management server 101. The login is performed by inputting the user ID and password of the person in charge of document creation and executing authentication. After login, a document creation screen (FIG. 12 to be described later) for creating document data is received from the document management server 101 and displayed on the display 210 of the client terminal 102.

  Step S601 is an example of a display instruction unit that instructs the client terminal to display a document data creation screen for creating document data in accordance with a display request from the client terminal according to the present invention.

  In step S602, the client terminal 102 receives an instruction to arrange part data used for document data or template data on a page in accordance with an operation of the input device 209 by a person in charge of document creation. In step S602, when a part data or template data placement instruction is received, the part data or the template data information (information in the data table in FIG. 14 or FIG. 15) for which the placement instruction has been received is transmitted to the outside of the client terminal 102. The data is temporarily stored in the memory 211.

  In addition, when part data included in template data formed by overlapping multiple parts data is deleted, the layer of part data included in template data is changed, or the shape of part data is changed Editing information for the template data is also temporarily stored in the external memory 211 of the client terminal 102 (FIG. 17 described later).

  In step S603, the client terminal 102 presses an approval request button (1201 in FIG. 12 to be described later) on the document creation screen displayed on the display 210 of the client terminal 102 according to the operation of the input device 209 by the person in charge of document creation. It is judged whether it was done. If the approval request button is pressed according to the operation of the input device 209 by the document creator, the process proceeds to step S604. If the approval request button is not pressed according to the operation of the input device 209 by the document creator, step S602 is performed. Return to.

  In step S604, the client terminal 102 determines whether or not the data arranged in each page of the document data in step S602 includes template data formed by overlapping a plurality of part data. The determination is made based on whether or not template data information (template data having a number in the template number 1510 of the data table in FIG. 15) formed by overlapping a plurality of part data in the memory 211 is temporarily stored.

  When the template data formed by overlapping a plurality of part data is included in the data arranged on each page of the document data in step S602, the client terminal 102 advances the process to step S605, and in step S602. If the data arranged on each page of the document data does not include template data formed by overlapping a plurality of part data, the client terminal 102 advances the process to step S612.

  In step S605, if the client terminal 102 includes template data formed by overlapping a plurality of part data in the data arranged in each page of the document data in step S602, the template data is edited. Whether template data editing information (FIG. 17 described later) is temporarily stored in the external memory 211 of the client terminal 102 is determined.

  If the template data has been edited, the client terminal 102 proceeds to step S606. If the template data has not been edited, the client terminal 102 proceeds to step S612.

  In step S <b> 606, the client terminal 102 uses the template data editing information temporarily stored in the external memory 211 of the client terminal 102 as part data included in the template data formed by overlapping a plurality of part data. It is determined in accordance with 1703 in FIG. 17 described later whether the information is deleted or whether the information is information obtained by changing the layer of the part data included in the template data formed by overlapping a plurality of part data.

  Template data editing information temporarily stored in the external memory 211 of the client terminal 102 is information indicating that part data included in template data formed by overlapping a plurality of part data is deleted, or a plurality of pieces of information In the case of the information obtained by changing the layer of the part data included in the template data formed by overlapping the part data, the client terminal 102 proceeds to step S607, and if it is other editing information, the client terminal 102 In step S612, the process proceeds to step S612.

  In step S <b> 607, the client terminal 102 uses the template data editing information temporarily stored in the external memory 211 of the client terminal 102 as part data included in the template data formed by overlapping a plurality of part data. Temporarily storing in the external memory 211 of the client terminal 102 the information indicating that the data has been deleted, or the template data approval format, which is information obtained by changing the layer of the part data included in the template data formed by overlapping a plurality of part data. This is confirmed by referring to the template data 1512 in which the template number 1501 matches the template data in the data table of FIG.

  In step S608, as a result of the confirmation in step S607, the client terminal 102 deletes the overlapping part data or overlaps the part data in the plurality of overlapping part data in the template. It is determined whether or not the template data permits the use of the template data by exchanging the parts that are overlapped with each other.

  If the template is a plurality of overlapping part data in the template, delete the overlapping part data or replace the overlapping part data with the overlapping part data. If the template data is permitted to be used, the client terminal 102 advances the process to step S612, and the template data is the part data on the overlapping side in the plurality of part data overlapping in the template. If the template data does not permit the use of the template data by replacing the overlapping part data with the overlapping part data, the client terminal 102 proceeds to step S609. Proceed with the process.

  In step S <b> 609, the client terminal 102 converts the template data formed by overlapping a plurality of part data onto the document creation screen displayed on the display 210 of the client terminal 102 into a plurality of part data overlapping in the template. Even though it is not permitted to delete the part data on the overlapping side, or replace the part on the side that overlaps the part data on the overlapping side to use the template data A warning display (1202 and 1203 in FIG. 12, which will be described later) is displayed to indicate that it is being used.

  Step S609 is a template which is display information that does not permit use in a state where a plurality of part data does not overlap document data created via the document data creation screen instructed to be displayed by the display instruction means in the present invention. This is an example of a notification means for notifying when data is used in a state where a plurality of parts data is not overlapped. Document data created via the document data creation screen instructed to be displayed by the display instruction means When the template data, which is display information that is not permitted to be used by exchanging multiple parts data layers, is used by exchanging multiple parts data layers, a notification means for notifying the client terminal to that effect It is an example.

  In step S610, the client terminal 102 receives an instruction to edit the document data again and an instruction to request approval (1201 in FIG. 12 described later) in accordance with the operation of the input device 209 by the person in charge of document creation.

  In step S611, the client terminal 102 determines in step S611 whether or not an instruction for requesting approval of document data (1201 in FIG. 12 described later) has been accepted in accordance with the operation of the input device 209 by the person in charge of document creation.

  In step S611, if an instruction to approve document data is received in accordance with the operation of the input device 209 by the document creator, the client terminal 102 proceeds to step S612, and the document creator in step S611. If an instruction to approve document data is not accepted in accordance with the operation of the input device 209, the client terminal 102 returns the process to step S610.

  In step S612, the client terminal 102 stores part data and template data information (in the data table of FIG. 14 or FIG. 15) temporarily stored in the external memory 211 of the client terminal 102 in step S602. The approval request including the document data information including the information) and the data table information illustrated in FIG. 17 is transmitted to the client terminal 102 of the document data approver, and the process illustrated in FIG. 6 ends.

  The document data approval request may be sent directly from the client terminal 102 of the document creator in charge to the client terminal 102 of the document authorizer, or may be temporarily managed from the client terminal 102 of the document creator. An approval request may be transmitted to the server 101 and a document approval request may be transmitted from the document management server 101 to a document approval person managed in the external memory 211 of the document management server 101.

  Further, when the process of step S612 is executed, in step S602, the part data used for the document data and the document data information created by arranging the template data on each page of the document data are stored in the document management. The data is stored in the data table of FIG. Further, the document management server 101 manages the data table information shown in FIGS. 11, 14, 15, and 17 in association with each other.

  Next, a screen on which the document creator in charge creates document data displayed on the display 210 of the client terminal 102 of the document creator in step S601 of FIG. 6 will be described with reference to FIG.

FIG. 12 is a diagram showing an example of a screen on which the document creator in charge creates document data displayed on the display 210 of the client terminal 102 of the document creator.
Reference numeral 1201 denotes a button for transmitting an approval request for document data created by the person in charge of document creation on the screen of FIG. 12 to the document management server 101.

  In 1202, in the template data formed by overlapping a plurality of part data, it is not permitted to delete the part data on the overlapping side of the plurality of overlapping part data in the template. It is not allowed to use the template data by replacing the layer of the part of the overlapping part and the part data of the overlapping part in the template. Regardless, a warning is displayed indicating that you are using it.

  In 1203, in the template data formed by overlapping a plurality of part data, it is not permitted to delete the part data on the overlapping side of the overlapping part data in the template. In such a case, the part data on the overlapping side (remaining part data in the template) is identified and displayed.

  In addition, in template data formed by overlapping multiple part data, it is allowed to use the template data by switching the layer of the part on the overlapping part in the template. If the template is used, the template is identified and displayed.

  The identification display method 1203 includes blinking part data or template data, or enclosing part data or template data with a thick frame.

  1204, in the template data formed by overlapping a plurality of part data, it is not permitted to delete the overlapping part data of the overlapping part data in the template, In such a case, or in template data formed by overlapping multiple parts data, replace the layer of the part on the overlapping side with the part data on the overlapping side in the template. This button is displayed for the part data and template data that have been used when such use is made even though the use of the data is not permitted.

  When the button 1204 is pressed according to the operation of the input device 209 by the person in charge of document creation, the screen transitions to the screen of FIG.

  In 1205, a preview of data arranged on the page is displayed, and in the case of FIG. 12, data arranged on page number 1 is displayed.

  When the button 1206 is pressed in accordance with the operation of the input device 209 by the person in charge of document creation, the document data is retrieved from the part data or template data stored in the external memory 211 of the client terminal 102 or the external memory 211 of the document management server 101. The person in charge of document creation can select part data and template data to be used for data. The part data and template data selected by the person in charge of document creation can be arranged at a location desired by the person in charge of document creation within the frame 1205 of the document data.

  Next, a screen generated by the document management server 101 and displayed on the display 210 of the client terminal 102 of the person in charge of document creation when the detail button 1204 in FIG. 12 is pressed will be described with reference to FIG.

  FIG. 16 is a diagram showing an example of a screen displayed on the display 210 of the client terminal 102 of the document creator or the document approver. The template data formed by overlapping a plurality of part data is in the template. Permits the use of the template data by deleting the part data on the overlapping part data or replacing the layer of the part on the overlapping part data. It is an example of the figure which shows the detail of the content of a warning in the case of such use although it is not done.

  Note that the screen of FIG. 16 is created by the document management server 101 and transmitted to the client terminal 102.

  In 1601, the part data included in the template data is previewed in parallel. At this time, even if the part data on the overlapping side of multiple overlapping part data in the template data is deleted, the deleted part data in the template data and the part data that has not been deleted in the template data Display each.

  Furthermore, as for the part data in which other part data overlaps, the part where the other part data overlaps is identified and displayed as 1605.

  In this embodiment, as shown by 1605, the part where the other part data overlaps is identified and displayed by hatching. However, the person in charge of document creation or the document approver overlaps the other part data. It suffices if the part can be identified, and the part where other parts data overlaps may be blinked or displayed with a color.

  If the part data on the overlapping side of a plurality of overlapping part data in the template data is deleted in 1601, the deleted part data in the template data and the undeleted part data in the template data are also displayed. By displaying each of them, the person in charge of document creation can grasp again what part data he / she has deleted.

  1602 is a warning that the part data on the overlapping side of a plurality of overlapping part data in the template is deleted in the template data formed by overlapping a plurality of part data, as in 1202 of FIG. Alternatively, a warning that the template data is being used is displayed by replacing the layer of the part on the overlapping side with the part data on the overlapping side in the template.

  Reference numeral 1603 denotes a return button. When the return button 1603 is pressed according to the operation of the input device 209 by the person in charge of document creation, the screen changes to the screen of FIG.

  When the part data on the overlapping side of the plurality of overlapping part data in the template is deleted from the template data formed by overlapping the plurality of part data, 1604 displays the part data on the overlapping side. This button is used to return to the original layer when the template data is used by replacing the layer of the part that is overlapped with the part data on the overlapping side in the template. is there.

  Next, the edit information data table stored in the external memory 211 of the client terminal 102 in step S602 and stored in the external memory 211 of the document management server 101 in step S612 will be described.

  FIG. 17 is a data table of editing information stored in the external memory 211 of the client terminal 102 in step S602 and stored in the external memory 211 of the document management server 101 in step S612. 209 is an example of a data table of editing information for template data included in document data created in accordance with operation 209.

  1701 stores the page number of document data (1704) in which a template having editing information is arranged.

  In 1702, a template number (corresponding to 1501) for uniquely identifying the template data arranged in the document data in step S602 is stored.

  In 1703, editing information stored in the external memory of the client terminal 102 in step S602 is stored. More specifically, information that the part data included in the template data formed by overlapping multiple parts data is deleted, information that the layer of the part data included in the template data is changed, Information that the shape has been changed is stored.

  Next, a process in which the approver approves the document data requested by the document creator in the process of FIG. 6 will be described with reference to FIG.

  FIG. 7 is a diagram illustrating an example of a process in which a document approver who approves document data approves document data.

  In step S701, according to the operation of the input device 209 by the document approver, the client terminal 102 selects the URL described in the approval request email transmitted from the client terminal 102 of the document creator in step S612 of FIG. As a result, the browser is started and the document management server 101 is logged in.

  The login is performed by inputting the user ID and password of the document approver and executing authentication. After logging in, the main screen of the document management system is received from the document management server 101 and displayed on the display 210 of the client terminal 102 of the document approver.

  In step S <b> 702, the client terminal 102 receives a document data acquisition request from the document approver via the main screen of the document management system and receives a document data list screen for which the document approver logged in step S <b> 501 is in charge of approval. Send to server 101.

  In step S703, the document management server 101 receives an acquisition request for a list screen of document data for which the document approver logged in in step S501 is in charge of approval from the client terminal 102, and the document approver who has logged in in step S501 A list screen of document data in charge of approval is generated and transmitted to the client terminal 102.

  More specifically, document data in which the user ID of the document approver logged in in step S701 matches the approver ID 1107 in FIG. 11 and the status 1108 is unapproved is extracted, and the extracted document data The document management server 101 generates a list screen and transmits it to the client terminal 102.

  In step S703, the template data included in the document data extracted by the document management server 101 is template data formed by overlapping a plurality of part data, and the plurality of overlapping part data in the template. Although it is not permitted to delete the part data on the overlapping side of the template, if it is used in such a way, or if it is overlapped with the overlapping part data in the template If you do not have permission to use the template data by exchanging layers of parts, add information to that effect to the document data list screen ( In step 1802 in FIG.

  In step S <b> 704, the client terminal 102 receives from the document management server 101 a list screen of document data for which the document approver logged in in step S <b> 701 is responsible for approval, and displays it on the display 210 of the client terminal 102. The screen displayed on the display 210 of the client terminal 102 in step S704 is FIG.

  In step S <b> 705, the client terminal 102 receives selection of document data to be approved from the document approver, and transmits an acquisition request for an approval screen for the document data selected by the document approver to the document management server 101. More specifically, the document data 1801 to be approved by the document approver is selected by pressing the 1801 in FIG. 18 described later according to the operation of the input device 209 by the document approver.

  In step S706, the document management server 101 receives the document data information (document number) selected from the document approver in step S705.

  In step S707, the document management server 101 determines whether the document data specified by the document data information received in step S706 includes information to which display information should be added.

  More specifically, first, it is determined whether or not the document data that matches the document data information (document number) received in step S706 is in the data table 1704 of FIG.

  Next, when the document data matching the document data information (document number) received in step S706 is in the data table 1704 of FIG. 17, the editing information 1703 of the template data included in the document data is referred to. .

  The editing information 1703 is information that the part data included in the template data formed by overlapping a plurality of part data is deleted, information that the layer of the part data included in the template data is changed, and , Delete the part data on the overlapping side or replace the part that overlaps the part data on the overlapping side for the part data that overlaps in the template. If the template data does not permit the use of data (when 1512 in FIG. 15 is “impossible”), it is determined that the information to be added with the display information is included.

  If it is determined in step S707 that the document data specified by the document data information received in step S706 contains information to which display information should be added, the process proceeds to step S708, and the document received in step S706 is received. If it is determined that the document data specified by the data information does not contain information to which display information should be added, the process proceeds to step S709.

  In step S707, the template data, which is display information that does not permit use in a state where a plurality of part data does not overlap with the document data requested for approval in the present invention, is used in a state where a plurality of part data does not overlap. Display instruction means for instructing the client terminal to display an approval screen for approving the use of document data requested for approval in accordance with a display request from the client terminal. Determining whether or not template data, which is display information that does not permit use by replacing a plurality of parts data layers, is used by replacing the plurality of parts data layers in the document data requested for approval It is an example of a means.

  In step S708, the document management server 101 adds display information to the document data approval screen specified by the document data information received in step S706.

  The display information added in step S708 is, for example, information of 1301 to 1303 in FIG.

  In step S <b> 709, the document management server 101 transmits a document data approval screen specified by the document data information received in step S <b> 706 to the client terminal 102.

  Step S709 is an example of display instruction means for instructing the client terminal to display an approval screen for approving the use of document data requested for approval in accordance with a display request from the client terminal in the present invention. When it is determined that the template data, which is display information that is not permitted to be used when a plurality of part data does not overlap with the document data requested for approval, is used without a plurality of part data overlapping. In addition, it is an example of a display instruction means for instructing the client terminal to display the approval screen that can be identified to that effect, and is used by replacing a plurality of parts data layers with the document data requested for approval by the determination means. Template data, which is display information that does not allow If it is determined to be used Te, which is an example of a display instruction unit for displaying an instruction to the approval screen that enables identifying the fact to the client terminal.

  In step S710, the client terminal 102 receives the document data approval screen transmitted from the document management server 101 in step S709, and displays it on the display 210 of the client terminal 102 (FIG. 13 to be described later).

  In step S711, the client terminal 102 inputs document data approval or document data denial on the document data approval screen displayed on the display 210 of the client terminal 102 in step S710 (1304 and 1305 in FIG. 13 described later). Is accepted according to the operation of the input device 209 by the document approver.

  Approval here means to approve the disclosure of the document data so that other users can use it. Further, the denial here means that the document data is not allowed to be disclosed so that other users can use it.

  In step S712, the client terminal 102 determines whether or not an approval input has been received from the document approver in step S711.

  If the approval input from the document approver is accepted in step S711, the client terminal 102 transmits the approval information of the document data to the document management server in step S714, and the approval input from the document approver in step S711. If it is not accepted (that is, if a denial input is accepted), the client terminal 102 transmits denial information of the document data to the document management server 101 in step S713.

  In step S715, the document management server 101 receives document data approval or denial information from the client terminal 102, and stores it in the document data 1108 in which the document data and the document number 1101 in the data table in FIG. To do.

  When the process of step S715 ends, the process of FIG. 7 ends.

  Here, with reference to FIG. 18, the document data list screen that is displayed on the display 210 of the client terminal 102 in step S704 of FIG.

  18 is a diagram showing an example of a list screen of document data displayed on the display 210 of the client approver 102 of the document approver and in which the document approver is in charge of approval. The screen of FIG. 15 and FIG. 17 according to the data table.

  In FIG. 18, 1801 displays a thumbnail of document data for which the document approver is in charge of approval. Next to 1801, the document number of the document data is displayed.

  When 1801 is selected according to the operation of the input device 209 by the document approver, an approval screen (FIG. 13 to be described later) for the selected document data is displayed on the display 210 of the client terminal 102 of the document approver.

  In step 1802 of FIG. 18, the template data included in the document data extracted by the document management server 101 in step S703 is template data formed by overlapping a plurality of part data, and the template data overlaps. Even if you are not allowed to delete the part data on the overlapping side of multiple part data that are overlaid, if they are used in such a way, or if they overlap with the part data on the overlapping side in the template If the use of the template data is not permitted by exchanging the layer of the part on the side, the information to that effect is displayed.

  By displaying the information 1802 in FIG. 18, the document approver easily confirms that the document data that he / she is responsible for includes the document data to be approved after carefully checking the contents. It becomes possible to know.

  Reference numeral 1803 denotes a return button. When the return button 904 is pressed according to the operation of the input device 209 by the document approver, the screen returns to the main screen of the document management system.

  Next, the document data approval screen displayed on the display 210 of the client terminal 102 in step S710 of FIG. 7 and used by the document approver in charge of approval will be described with reference to FIG.

  FIG. 13 is a diagram illustrating an example of an approval screen for document data displayed on the display 210 of the client terminal 102 of the document approver, in which the document approver is in charge of approval. The screen in FIG. Are generated in accordance with the data table of FIG.

  In the template data formed by overlapping a plurality of part data, 1301 in FIG. 13 is not permitted to delete the part data on the overlapping side of the overlapping part data in the template. Nevertheless, if such use is made, the part data on the overlapping side (remaining part data in the template) is identified and displayed.

  In addition, in template data formed by overlapping multiple part data, it is allowed to use the template data by switching the layer of the part on the overlapping part in the template. When the template is used, the template is identified and displayed.

  The identification display method 1301 includes blinking part data or template data, or enclosing part data or template data with a thick frame.

  Reference numeral 1302 in FIG. 13 indicates that in the template data formed by overlapping a plurality of part data, it is not permitted to delete the part data on the overlapping side of the overlapping part data in the template. Regardless, in such a case, or in template data formed by overlapping multiple part data, the layer of the part on the overlapping side in the template is replaced. This button is displayed for the part data and template data that have been used when such use is made even though the use of the template data is not permitted.

  When the button 1302 is pressed according to the operation of the input device 209 by the person in charge of document creation, the screen transitions to the screen of FIG.

  Since FIG. 16 has already been described, detailed description thereof is omitted here. As a difference from the case where the screen is changed from 1204 in FIG. 12 to the screen in FIG. 16, 1604 is not displayed when the screen is changed from 1302 in FIG. 13 to the screen in FIG.

  By displaying the screen of FIG. 16 on the display 210 of the client terminal 102 of the document approver, for example, a template in which the part data on the overlapping side of a plurality of overlapping part data in the template is deleted is used. When the person in charge of creating the document creates document data, the part data that was deleted is the part data that has been deleted, or the deleted part data has not been deleted. Since the document approver can confirm how they overlap, the document approver can more appropriately determine whether to approve the document data.

  In the template data formed by overlapping a plurality of part data, 1303 in FIG. 13 is not permitted to delete the part data on the overlapping side of the plurality of overlapping part data in the template. Nevertheless, it is allowed to use the template data by replacing the layer of the part data on the overlapping side with the part data on the overlapping side in the template. Although it is not, a warning that it is used is displayed.

  Reference numeral 1304 in FIG. 13 denotes an approval button. When the approval button 1304 is pressed according to the operation of the input device 209 by the document approver, the document data is approved.

  Reference numeral 1305 in FIG. 13 denotes a denial button. When the denial button 1305 is pressed according to the operation of the input device 209 by the document approver, the document data is denied.

  Reference numeral 1306 in FIG. 13 denotes a return button. When the return button 1306 is pressed according to the operation of the input device 209 by the document approver, the screen returns to the document data list screen in FIG. This is the end of the description of FIG.

  As described above, when a plurality of part data overlaps with the template data, the document creator has set the approval format (use conditions) of the template data and uses the template data contrary to the approval format. In the case of template data including multiple part data created by the person in charge of creating template data, even if the template data does not overlap the part data, some part data In the case of using (part B), there is a case where other part data (part C) is deleted and template data is not used.

  Specifically, for example, if part B is a character of a company and part C is copyrighted, part B may be changed to another character of the company, but part B is used. In some cases, part C must be used together.

  Further, for example, when part B is a part indicating a discount such as “5 discount” and part C is a part indicating a discount period, when part B is used, it is necessary to use part C together. .

  In the above two specific examples, if the part C is deleted when the document creator uses the template data, the person who creates the template data or the approver of the template data may use it unintentionally. There was a problem of being done.

  Therefore, an embodiment that solves the above problem will be described with reference to FIGS.

  First, with reference to FIG. 19, another embodiment of the template data approval screen displayed on the display 210 of the client terminal 102 in step S510 of FIG. Example) will be described.

  FIG. 19 is a diagram showing an example of a template data approval screen displayed on the display 210 of the template approver's client terminal 102, in which the template approver is in charge of approval. The screen in FIG. Generated by the document management server 101 in accordance with the template management table of FIG. 15 stored in the external memory 211 of the server 101.

  More specifically, the document management server 101 refers to the template management table in FIG. 15 and identifies the template data received by the template approver in step S505 in FIG. 5 and the part data included in the template data. Each information of FIG. 19 is displayed.

  1901 in FIG. 19 is an approval button. When the approval button 1901 is pressed in accordance with the operation of the input device 209 by the template approver, the template data received by the template approver in step S505 in FIG. Registered as approved in the template management table 1500 of FIG. 15 stored in the external memory 211 of the server 101 (status 1507 becomes approved).

  At this time, if a check box 1905 described later is checked by the approver, the information is stored in the data table of FIG.

  Here, the data table of FIG. 24 will be described.

  The data table in FIG. 24 is a data table stored in the external memory 211 of the document management server 101 (also temporarily stored in the external memory 211 of the client terminal 102 in step S602 in FIG. 6). When the approval button 1901 is pressed according to the operation of the input device 209 by the template approver, if a check box 1905 described later is checked by the template approver, the information is stored in the data table.

  In FIG. 24 and FIG. 25 described later, template data including a plurality of part data, which is used for creating document data, and each part data included in the template data is allowed to be used independently. Managing the use condition of the template data indicating whether or not.

  The template number 2401 includes a template number (information for identifying template data) displayed on the screen of FIG. 19 when the approval button 1901 is pressed according to the operation of the input device 209 by the template approver. Yes, it may be the ID of the template data or the name of the template data).

  In the part number 2402, in FIG. 19, a part name 1903 in the same row as a field of a part 1904 to be used in combination and including a part data whose check box 1905 is checked by the template approver. The part number (information for identifying part data, which may be an ID of part data or a name of part data) is stored.

  In the part number 2403 to be used in combination, the part number of the part data to be used in combination with the part data stored in 2402 (part data checked in the check box 1905 by the template approver) is stored. The

  2404 stores the ID of the template approver who has approved the template data of the template number 2401.

  The information stored in 2401 to 2403 in FIG. 24 will be described with reference to FIG. 19 as an example. “001” indicating template data 001 is stored in the template number 2401, and part data 1 is stored in the part number 2402. “1” is stored, and “2” indicating part data 2 is stored in the part number 2403 to be used in combination. Above, description of FIG. 24 is complete | finished.

  Returning to the description of FIG. Reference numeral 1902 in FIG. 19 is a denial button. When the denial button 1902 is pressed in accordance with the operation of the input device 209 by the template approver, the template data whose specification has been accepted by the template approver in step S505 in FIG. Is registered in the template management table 1500 of FIG. 15 stored in the external memory 211 of the document management server 101 (status 1507 is denied).

  1903 in FIG. 19 represents a part name. The part name 1903 is included in the template data when the template data received by the template approver in step S505 in FIG. 5 includes a plurality of part data. The part name including the thumbnail of each part data is displayed.

  In FIG. 19, 1904 (parts 1904 to be used in combination) designates part data to be used in combination with each part data displayed in the part name 1903 (part data displayed in the part name 1903 alone. "Specify whether to permit use" is a column for accepting a check on the check box 1905 according to the operation of the input device 209 by the approver of the template.

  Reference numeral 1904 in FIG. 19 denotes display control means for controlling to display the setting screen for the template data for which the display request has been received by the receiving means in the present invention. The determination means displays the setting screen display request by the receiving means. When it is determined that the received template data includes a plurality of part data, the use condition of the template data indicating whether or not each part data included in the template data is permitted to be used alone is specified. It is an example of the display control means which controls to display the setting screen which can be received.

  The approver uses the template data indicating whether or not each part data included in the template data including a plurality of part data is allowed to be used depending on whether or not the check box 1905 in FIG. 19 is checked. Therefore, it is possible to reduce the possibility that the template data is used in a state not intended by the approver.

  If the template data is formed by overlapping multiple part data, delete the part data on the overlapping side or replace the part data on the overlapping side with the part data on the overlapping side If the approver does not want to allow the use of the template data, the approver must use the parts that are part data on the side where the part name 1903 is overlapped. The check box 1905 for the part data on the overlapping side in 1904 may be checked.

  In the column of parts 1904 to be used in combination, the part data included in the template data received by the template approver in step S505 in FIG. 5 is displayed.

  Specification of part data that must be used in combination with each part data displayed in the part name 1903 in FIG. 19 is possible by accepting a check for the check box 1905 according to the operation of the input device 209 by the approver of the template data. The template approver uses the template data against the intention of the template approver despite the fact that the template approver has approved the template data because multiple parts data are used in combination. It is possible to reduce the possibility that the user who creates the document data deletes any of the plurality of part data used in combination in the template data and uses the template data.

  In 1906 (preview 1906) in FIG. 19, a preview of the template data that has been designated by the template approver in step S505 in FIG. 5 is displayed.

  19 is a return button. When the return button 1907 is pressed according to the operation of the input device 209 by the template approver, the template data list screen of FIG. 9 is displayed again.

  19 has been described so far. In the case of the embodiment of FIG. 19, in step S505 of FIG. 5, the document management server 101 determines that the template data specified by the template data information received in step S506 is The document management server 101 determines that the template data specified by the template data information received in step S506 is template data including a plurality of part data without determining whether or not the plurality of parts data are formed by overlapping. (An example of determination means for determining whether or not the template data for which the display request has been received by the reception means in the present invention includes a plurality of part data). In this case, step S505 is not an essential process.

  If the document management server 101 determines that the template data specified by the template data information received in step S506 is template data including a plurality of parts data, the document management server 101 displays 1903 to 1905 on the approval screen in FIG. An approval screen with “” added is generated and transmitted to the client terminal 102. This is the end of the description of FIG.

  Next, referring to FIG. 23, another embodiment of the template data approval screen (FIG. 10, FIG. 10) displayed on the display 210 of the client terminal 102 in step S510 of FIG. Another embodiment of FIG. 19 will be described.

  FIG. 23 is a diagram showing an example of a template data approval screen displayed on the display 210 of the template approver's client terminal 102, in which the template approver is in charge of approval. The screen in FIG. Is generated by the document management server 101 according to the data table.

  More specifically, the document management server 101 refers to the data table in FIG. 15 and identifies the template data that has been designated by the template approver in step S505 in FIG. 5 and the part data included in the template data. Each information of FIG. 23 is displayed.

  Reference numeral 2301 in FIG. 23 denotes an approval button. When the approval button 2301 is pressed in accordance with the operation of the input device 209 by the template approver, the template data that has been designated by the template approver in step S505 in FIG. Are registered in the template management table 1500 of FIG. 15 stored in the external memory 211 of the document management server 101 (status 1507 is approved).

  At this time, if a check box 2304 described later is checked by the approver, the information is stored in the data table of FIG.

  Here, the data table of FIG. 25 will be described.

  The data table in FIG. 25 is a data table stored in the external memory 211 of the document management server 101 (also temporarily stored in the external memory 211 of the client terminal 102 in step S602 in FIG. 6). When the approval button 2301 is pressed according to the operation of the input device 209 by the template approver, if a check box 2304 (to be described later) is checked by the approver, the information is stored in the data table.

  The template number 2501 includes a template number (information for identifying template data) displayed on the screen of FIG. 23 when the approval button 2301 is pressed according to the operation of the input device 209 by the template approver. Yes, it may be the template data ID or the template data name).

  In the part number 2502 forbidden to be deleted, the part number of the part data checked by the template approver in the check box 2304 in FIG. 23 is stored.

  In 2503, the ID of the template approver who has approved the template data of the template number 2401 is stored.

  The information stored in 2501 and 2502 in FIG. 25 will be described with reference to FIG. 23. For example, “001” indicating template data 001 is stored in the template number 2501, and the part number 2502 for which deletion is prohibited includes “2” indicating the part data 2 is stored. Above, description of FIG. 25 is complete | finished.

  Returning to the description of FIG. 232 in FIG. 23 is a denial button. When the denial button 2302 is pressed in accordance with the operation of the input device 209 by the template approver, the template data that has been designated by the template approver in step S505 in FIG. Is registered in the template management table 1500 of FIG. 15 stored in the external memory 211 of the document management server 101 (status 1507 is denied).

  The part name 2303 in FIG. 23 displays the part name of each part data included in the template data when the template data received by the template approver in step S505 in FIG. 5 includes a plurality of part data. Is done.

  A check box 2304 in FIG. 23 is a check box for specifying part data that is prohibited from being deleted from the template among the part data displayed in the part name 2303 according to the operation of the input device 209 by the approver of the template. By receiving a check for 2304, this is a receiving column.

  In this embodiment, the check box 2304 in FIG. 23 indicates that the part data displayed in the part name 2303 is part data that is prohibited from being deleted from the template by the approver of the template data. The check box 2304 is received by receiving a check for the check box 2304 according to the operation of the input device 209. As another example, the check box 2304 in FIG. The specification of the part data that is permitted to be used in the field may be received by receiving a check on the check box 2304 according to the operation of the input device 209 by the approver of the template.

  A preview 2305 in FIG. 23 displays a preview of the template that has been designated by the template approver in step S505 in FIG.

  23 is a return button. When the return button 2306 is pressed according to the operation of the input device 209 by the template approver, the template data list screen of FIG. 9 is displayed again.

  23 has been described so far. In the case of the embodiment of FIG. 23, in step S505 of FIG. 5, the document management server 101 determines that the template data specified by the template data information received in step S506 is The document management server 101 determines that the template data specified by the template data information received in step S506 is template data including a plurality of part data without determining whether or not the plurality of parts data are formed by overlapping. Determine whether.

  If it is determined that the template data specified by the template data information received in step S506 is template data including a plurality of part data, the document management server 101 displays 2303 and 2304 on the approval screen in FIG. An approval screen with “” added is generated and transmitted to the client terminal 102.

In this embodiment and the previous embodiment, 1003 to 1006 in FIG. 10, 19003 to 19006 in FIG. 19, and 2303 to 2305 in FIG. 23 are displayed on the display 210 of the client terminal 102 of the approver of the template data. As another embodiment, the template data creation screen displayed on the display 210 of the client terminal 102 of the person in charge of creating the template data includes 1003 to 1006 in FIG. 10, 19003 to 19006 in FIG. 19, and 2303 to 2305 in FIG. It may be displayed.
Above, description of FIG. 23 is complete | finished.

  Next, a screen on which the document creator in charge creates document data displayed on the display 210 of the client terminal 102 of the document creator in FIG. 6 will be described with reference to FIG.

  FIG. 20 is a diagram showing an example of a screen on which the document creator in charge creates document data displayed on the display 210 of the client terminal 102 of the document creator.

  The screen of FIG. 20 is a screen displayed on the display 210 of the client terminal 102 in step S601. The screen of FIG. 20 uses the template data approved by the approver on the approval screen of FIG. 19 or FIG. This is a screen on which the person in charge of document creation creates document data (an example of display control means for controlling to display a creation screen for creating document data in the present invention).

  Reference numeral 2001 denotes a button for transmitting an approval request for document data created by the person in charge of document creation on the screen of FIG. 20 from the client terminal 102 to the document management server 101.

  2002, template data including a plurality of part data used for document data satisfies a use condition of the template data indicating whether or not each part data included in the template data is allowed to be used alone. This is a notification field for notifying the person in charge of document creation to that effect (if the template data edited according to the editing instruction received by the receiving means by the determination means in the present invention does not satisfy the use conditions) An example of a notification means for notifying when it is determined).

  Specifically, the template data stored in the template number 2401 of the data table in FIG. 24 is used for the document data created by the person in charge of document creation, and the part in the same row as the template data in FIG. Although the part data stored in the number 2402 is used, the part data stored in the part number 2403 to be used in combination on the same line as the template data in FIG. 24 is not used. If so, notify that fact.

  Further, the template data stored in the template number 2501 of the data table in FIG. 25 is used for the document data created by the person in charge of document creation, and deletion of the same line as the template data in FIG. 25 is prohibited. When the part data stored in the part number 2502 has been deleted, this is notified.

  In 2003, the template data stored in the template number 2401 of the data table in FIG. 24 is used for the document data created by the person in charge of document creation, and the part number 2402 in the same row as the template data in FIG. The part data stored in the part number 2403 to be used in combination in the same row as the template data in FIG. 24 is not used even though the part data stored in The part data stored in the part number 2402 is identified and displayed.

  Note that the identification display method of 2003 includes blinking part data or surrounding the part data with a thick frame.

  Reference numeral 2004 denotes a template indicating whether or not template data including a plurality of part data used for document data created by a person in charge of document creation permits use of each part data included in the template data alone. This button is displayed when the data usage conditions are not satisfied. When the button 2004 is pressed according to the operation of the input device 209 by the person in charge of document creation, the screen transitions to the screen shown in FIG. 22 (template details screen).

  In 2005, a preview of data arranged on each page in the document data created by the person in charge of document creation is displayed. In FIG. 20, the data arranged on page 1 is displayed.

  Reference numeral 2006 denotes an arrangement button. When the arrangement button 2006 is pressed according to the operation of the input device 209 by the person in charge of document creation, parts stored in the external memory 211 of the client terminal 102 or the external memory 211 of the document management server 101 are displayed. From the data and template data, the person in charge of document creation can select part data and template data to be used for the document data.

  The part data and template data selected by the person in charge of document creation can be arranged at a location desired by the person in charge of document creation within the 2005 frame of the document data.

  In the case of the example in FIG. 20, in step S606 in FIG. 6, the client terminal 102 includes a part in which template data editing information temporarily stored in the external memory 211 of the client terminal 102 is included in the template data. It is determined according to 1703 in FIG. If the editing information of the template data temporarily stored in the external memory 211 of the client terminal 102 is information that the part data included in the template data is deleted, the process proceeds to step S607 and other editing information is used. If there is, the process proceeds to step S612.

  In the case of the example of FIG. 20, in step S607 of FIG. 6, the client terminal 102 deletes the part data whose template data includes template data editing information temporarily stored in the external memory 211 of the client terminal 102. The usage condition (approval format) of the template data indicating whether or not individual use of each part data included in the template data, which is information that has been performed, is temporarily stored in the external memory 211 of the client terminal 102 24, template data 2402 and 2403 whose template number 2401 matches the template data in the data table of FIG. 24, or template data whose template number 2501 matches the template data in the data table of FIG. Be confirmed by referring to the 2502 (an example of the present invention, the template data edited in accordance with the editing instruction accepted by accepting means, determining means for determining whether satisfies the use conditions).

  In step S607 of FIG. 6, the client terminal 102 refers to the data table of FIG. 24 in the case of the embodiment of FIG. 19, and refers to the data table of FIG. 25 in the case of the embodiment of FIG.

  In the example of FIG. 20, in step S608 of FIG. 6, as a result of the confirmation in step S607, the client terminal 102 indicates whether or not each part data included in the template data is permitted to be used alone. If the use condition of the template data is not satisfied, the process advances to step S609 to display a document data creation screen including notifications 2002 to 2004 in FIG.

  That is, in the example of FIG. 20, when the template data editing information (1703) is information that the part data included in the template data is deleted, the part data is stored in 2502, When the part data shown in 2402 is used even though the part data is stored in 2403, notifications shown in 2002 to 2004 in FIG. 20 are performed. Above, description of FIG. 20 is complete | finished.

  Next, referring to FIG. 22, when the detail button 2004 in FIG. 20 is pressed by the document creator, it is generated by the document management server 101 and displayed on the display 210 of the client terminal 102 of the document creator. The screen will be described.

  FIG. 22 is a diagram showing an example of a screen displayed on the display 210 of the client terminal 102 of the document creation person when the detail button 2004 in FIG. 20 is pressed by the person in charge of document creation. FIG. 10 is a diagram illustrating an example of a screen displayed on the display 210 of the client terminal 102 of the document approver when the detail button 2004 is pressed by the document approver.

  2201 satisfies the use condition of the template data indicating whether or not the template data including a plurality of part data used in the document data permits the individual use of each part data included in the template data. This is a notification column for notifying the details when there is not.

  Specifically, the template data stored in the template number 2401 of the data table in FIG. 24 is used for the document data created by the person in charge of document creation, and the part in the same row as the template data in FIG. Although the part data stored in the number 2402 is used, the part data stored in the part number 2403 to be used in combination on the same line as the template data in FIG. 24 is not used. If so, notify that fact.

  Further, the template data stored in the template number 2501 of the data table in FIG. 25 is used for the document data created by the person in charge of document creation, and deletion of the same line as the template data in FIG. 25 is prohibited. When the part data stored in the part number 2502 has been deleted, this is notified.

  2205 includes template data including a plurality of part data used for document data, and the use condition of the template data indicating whether or not each part data included in the template data is allowed to be used alone. A preview of the template data that does not satisfy is displayed.

  The template data is displayed as a preview of the template data before the person in charge of document creation edits the template data on the document data creation screen of FIG.

  Even if one of the plurality of part data included in the template data is deleted in 2205, by displaying the deleted part data and the part data that has not been deleted, The person in charge of document creation can grasp again what part data he / she has deleted.

  In 2202, the part data deleted by the document creator in the template is identified and displayed.

  Reference numeral 2203 denotes a return button. When the return button 2203 is pressed according to the operation of the input device 209 by the person in charge of document creation, the screen of FIG. 21).

  Reference numeral 2204 denotes a button for returning the part data deleted by the document creator in the template to the state before being deleted. This is the end of the description of FIG.

  Next, another embodiment of the document data approval screen displayed on the display 210 of the client terminal 102 in step S710 of FIG. 7 and in which the document approver is in charge of approval will be described with reference to FIG.

  FIG. 21 is a diagram showing an example of an approval screen for document data displayed on the display 210 of the client terminal 102 of the document approver, in which the document approver is in charge of approval. The screen in FIG. , And are generated according to the data tables of FIGS.

  21 is an approval button. When the approval button 2101 is pressed in accordance with the operation of the input device 209 by the document approver, the document data that has been designated by the document approver in step S705 of FIG. 7 is already approved. Is registered in the document management table 1100 of the document management server 101 (the status 1108 is approved).

  21 is a denial button. When the denial button 2106 is pressed in accordance with the operation of the input device 209 by the document approver, the document data whose designation is accepted by the document approver in step S705 of FIG. Is registered in the document management table 1100 stored in the external memory 211 of the document management server 101 (the status 1108 is denied).

  21 is a return button, and when the return button 2107 is pressed according to the operation of the input device 209 by the document approver, the screen returns to the document data list screen of FIG.

  Reference numeral 2102 denotes a field for notifying the document approver of the same information as 2002 in FIG.

  Since 2103 is the same as 2003 in FIG. 20, detailed description thereof is omitted.

  Since 2104 is the same as 2004 in FIG. 20, detailed description thereof is omitted.

  In the case of the example of FIG. 21, in step S707 of FIG. 7, the document management server 101 edits the template data when the template data is used for the document data for which the approval request has been accepted in step S705. Is determined based on the data table 1703 of FIG. 17 stored in the external memory 211 of the document management server 101 as to whether or not the information is that the part data included in the template data has been deleted.

  If the editing information of the template data is information that the part data included in the template data has been deleted, the template indicating whether or not each part data included in the template data is allowed to be used alone The data use conditions (approval format) are the template data 2402, 2403 of the template data whose template number 2401 matches the template data in the data table of FIG. 24 stored in the external memory 211 of the document management server 101, or FIG. This is confirmed by referring to the template data 2502 in which the template number 2501 matches the template data in the data table.

  In step S707 of FIG. 7, the document management server 101 refers to the data table of FIG. 24 in the case of the embodiment of FIG. 19, and refers to the data table of FIG. 25 in the embodiment of FIG.

  In the example of FIG. 21, in step S708 of FIG. 7, the document management server 101 determines whether or not to permit each part data included in the template data independently as a result of the confirmation in step S707. If the use condition of the template data to be shown is not satisfied, an approval screen including the notifications 2102 to 2104 in FIG. 20 is displayed. This is the end of the description of FIG. This is the end of the description of the present invention.

  As described above, according to the present invention, in the template data created by overlapping a plurality of part data, the part data in which other part data included in the template data is overlapped can be used in a state not intended by the approver. Can be reduced.

  Further, according to the present invention, the template data including a plurality of part data is a document without satisfying the use condition of the template data indicating whether or not each part data included in the template data is allowed to be used alone. The possibility of being used for data can be reduced.

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

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

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

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

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

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

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

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

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

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

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

101 document management server 102 client terminal 103 network

Claims (9)

Template data including a plurality of part data, and the use of the template data used to create document data and the template data indicating whether or not each part data included in the template data is permitted to be used alone An information processing system for managing conditions,
Display control means for controlling to display a creation screen for creating document data;
Receiving means for receiving an instruction to edit the template data included in the document data created via the creation screen displayed by the display control means;
Determining means for determining whether template data edited in accordance with the editing instruction received by the receiving means satisfies the use condition;
When the determination unit determines that the template data edited according to the editing instruction received by the reception unit does not satisfy the use condition, the notification unit includes a notification unit that notifies the fact that the template data is not satisfied. Information processing system.   The information processing system according to claim 1, wherein the use condition includes a use condition of the template data indicating whether or not the use is permitted depending on a combination method of the part data included in the template data.   The information processing system according to claim 1, wherein the use condition further includes a use condition of the template data related to movement of each part data included in the template data.   The use condition of the template data relating to the movement of each part data includes a use condition indicating whether or not to permit replacement of a layer in which a plurality of part data included in the template data is arranged. The information processing system according to claim 3.   Whether or not the usage condition of the template data relating to the movement of each part data permits the movement so that the part data does not overlap when a plurality of part data included in the template data overlap. The information processing system according to claim 3, further comprising a use condition indicating   The information processing system uses the template data indicating whether or not to allow the use of the overlapping part data alone when a plurality of part data included in the template data overlap. 6. The information processing system according to claim 1, wherein conditions are managed. An approval request accepting means for accepting an approval request for document data created via the creation screen;
An approval screen display control means for controlling to display an approval screen for accepting an input of approval or denial for the document data for which the approval request has been received by the approval request receiving means;
A condition determination unit that determines whether or not the template data included in the document data for which the approval request has been received by the approval request reception unit satisfies the use condition;
The notification means further notifies the fact when the condition determination means determines that the template data that has received the approval request by the approval request reception means does not satisfy the use condition. The information processing system according to any one of claims 1 to 6. Template data including a plurality of part data, and the use of the template data used to create document data and the template data indicating whether or not each part data included in the template data is permitted to be used alone An information processing system control method for managing conditions,
A display control step of controlling the display control means of the information processing system to display a creation screen for creating document data;
A receiving step in which a receiving unit of the information processing system receives an instruction to edit the template data included in the document data created via the creation screen displayed by the display control step;
A determination step in which the determination unit of the information processing system determines whether template data edited according to the editing instruction received in the reception step satisfies the use condition;
A notification for notifying the information processing system when it is determined by the determination step that the template data edited in accordance with the editing instruction received in the reception step does not satisfy the use condition. And a process for controlling the information processing system. Template data including a plurality of part data, and the use of the template data used to create document data and the template data indicating whether or not each part data included in the template data is permitted to be used alone A program for causing a computer of the information processing system to execute a control method of the information processing system for managing conditions,
The computer,
Display control means for controlling to display a creation screen for creating document data;
Receiving means for receiving an instruction to edit the template data included in the document data created via the creation screen displayed by the display control means;
Determining means for determining whether template data edited in accordance with the editing instruction received by the receiving means satisfies the use condition;
When the determination unit determines that the template data edited in accordance with the editing instruction received by the reception unit does not satisfy the use conditions, the determination unit functions as a notification unit that notifies the fact. program.

Images