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

Abstract

PROBLEM TO BE SOLVED: To notify a user who approves electronic document data using part data having another part data overlapped thereon, of the fact that the part data is not permitted to be used when the another part data is not overlapped thereon.SOLUTION: When instructing display on a client terminal of an approval screen for approving the use of document data in response to a request to approve the use according to a request to display from the client terminal, if template data that is display information not permitting the use thereof when a plurality of pieces of part data are not overlapped thereon is used wen a plurality of part data are not overlapped thereon for the document data the use of which is request to be approved, an information processing system instructs the client terminal to display an approval screen displaying the effect in an identifiable way (1303).SELECTED DRAWING: Figure 13

Description

  The present invention relates to an information processing system, a control method for an information processing system, and a computer program, and in particular, part data that overlaps other part data is permitted to be used in a state where other parts do not overlap. The present invention relates to a mechanism capable of notifying a user who approves electronic document data using the part data when there is no such data.

  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 of the template, there are templates in which the parts are overlapped (hereinafter, the template in which the parts are overlapped is referred to as template A).

  For templates with overlapping parts such as template A, even if the template is approved by the approver of the template, the person in charge of creating the electronic document using the template A creates an electronic document. Delete the overlapping part (hereinafter referred to as part B) in template A, and create an electronic document using template A with only part A (hereinafter referred to as part C) over which part B overlapped. The template approver may not allow you to do so.

  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, the person in charge of creating the electronic document allows the approver of the template to use the template A with only the part A in which the part B is deleted when the electronic document is created using the template A. Because the approver of the template does not permit the use of template A with only part C, the person in charge of creating the electronic document uses the template A with only part C. It is possible to request approval of the electronic document created by the person in charge of creating the electronic document to the approver of the electronic document.

  Then, since the approver of the electronic document may not be the same as the approver of template A, the approver of the electronic document does not know that part A and part C overlapped in the first place, so the part Since it is not known that the template approver does not permit the use of the template A only for C, there is a possibility that an electronic document using the template A only for the part C may be erroneously approved.

  Since Patent Document 1 does not describe a countermeasure for the above problem, even if the technique of Patent Document 1 is used, the template approver still does not permit the use of the template A with only the part C. Nevertheless, the approver of the electronic document may erroneously approve the electronic document using the template A including only the part C.

The present invention relates to a user who approves electronic document data using the part data when the part data which is overlapped with other part data is not permitted to be used in a state where the other parts are not overlapped. The purpose is to provide a mechanism capable of notifying the fact.

  The present invention is an information processing system that manages template data formed by a plurality of parts data and display information indicating whether or not the template data is permitted to be used in a state where the plurality of parts data do not overlap. In accordance with a display request from the client terminal, display instruction means for instructing the client terminal to display an approval screen for approving the use of the document data requested for approval, and a plurality of parts in the document data requested for approval. Determination means for determining whether or not template data, which is display information that is not permitted to be used in a state where data is not overlapped, is used in a state where a plurality of part data is not overlapped, and the display instruction means The determination unit does not overlap the document data requested for approval with a plurality of part data. When it is determined that template data, which is display information that is not permitted to be used in a state, is used in a state where a plurality of part data do not overlap, the approval screen that makes it possible to identify that is displayed on the client terminal The display is instructed.

  The present invention also provides an information processing system for managing template data formed by a plurality of part data and display information indicating whether or not to permit use of the template data by exchanging layers of the plurality of part data. In accordance with a display request from the client terminal, a display instruction means for instructing the client terminal to display an approval screen for approving the use of the document data requested for approval, and a plurality of the document data requested for approval Determination means for determining whether or not template data, which is display information that is not permitted to be used by exchanging parts data layers, is used by exchanging a plurality of parts data layers, the display instruction means, The determination means inserts a plurality of parts data layers into the document data requested for approval. If it is determined that the template data, which is display information that is not permitted to be used, is used by switching the layers of multiple parts data, the client terminal is instructed to display the approval screen that can identify that fact. It is characterized by doing.

  The present invention also provides information processing for managing template data formed by a plurality of parts data and display information indicating whether or not the template data is permitted to be used in a state where the plurality of parts data do not overlap. A method for controlling a system, wherein the display instruction means of the information processing system instructs 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. Template data that 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 to be approved by the determination unit of the process and the information processing system. And a determination step for determining whether or not the display instruction device is being used. 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, is used in a state where a plurality of part data does not overlap. If it is determined that the approval screen is displayed, the client terminal is instructed to display the approval screen that can identify the fact.

  The present invention also provides an information processing system for managing template data formed by a plurality of part data and display information indicating whether or not to permit use of the template data by exchanging layers of the plurality of part data. The display instructing means of the information processing system instructs the client terminal to display an approval screen for approving the use of the document data requested for approval in accordance with the display request from the client terminal, Template data, which is display information that does not permit use by replacing the plurality of parts data layers with the document data requested for approval, is used by replacing the plurality of parts data layers. A determination step for determining whether or not the display instruction step is performed. When it is determined that template data, which is display information that does not permit use by replacing a plurality of parts data layers with the document data requested for approval, is used by replacing a plurality of parts data layers In addition, the client terminal is instructed to display the approval screen that can identify the fact.

According to the present invention, when part data that is overlapped with other part data is not permitted to be used in a state where other parts are not overlapped, electronic document data using the part data is approved. This is notified to the user, and it is possible to prevent the part data in which the other part data overlaps from being used in a state in which the other parts do not overlap.

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.

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.
<Description of FIG. 1>

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.

<Description of FIG. 2>

  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 203 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 202 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 202 and executing the program. An input controller (input C) 205 controls input from a pointing device such as a keyboard 209 or a mouse (not shown). A video controller (VC) 206 controls display on a display device such as the display device 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 device 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 device 210.

A program used to execute 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 202 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.

<Description of FIG. 3>

  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, the template 1 is formed by combining part number 1 and part number 2.

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).

<Description of FIG. 11>

  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 for managing electronic document data created by the document management server 101 and managed in the external memory 211 in accordance with a user operation, and includes a document number 1101, a page number 1102, A template number 1103, a part number 1104, coordinates 1105, a creation person ID 1106, an approver ID 1107, a status 1108, and the like are included.

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 coordinates of the template data 1103 and the part data 1104 in the page of the electronic document data. The coordinates 1105 are the coordinates of the template data 1103 and the part data 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.

<Description of FIG. 14>

  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.

<Description of FIG. 15>

  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.

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 it overlaps with other part data.

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. The status 1507 stores information “unapproved” if the approver has not yet approved the template data, and stores information “approved” if the approver has approved the template data. If the approver has denied the template data, 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 in accordance with a user operation and managed by the external memory 211, and is included in the template data in 1500 in FIG. It is a data table for managing whether or not to permit use in a state where there is no upper part for part data in which other parts overlap among the data.

  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 in which the part data 1508 is arranged, that is, the user ID of the same approver as the approver 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. Run.

<Description of FIG. 4>

  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.

<Description of FIG. 8>

  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 to the client terminal 102 of the template approver.

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.
<Description of FIG. 5>

  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 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 to display the approval screen to which information is added.

  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.

  When display information is added to the approval screen for the template data received from the management server 101 in step S510, the client terminal 102 determines that the overlapping side of the plurality of overlapping part data in the template The selection of whether or not to allow the use of the template data by deleting the part data or replacing the overlapping part data with the overlapping part data (1004 in FIG. 10 described later) is also possible. This is 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 management server 101 in step S510, the part data on the overlapping side of the overlapping part data in the template is displayed. If it is not selected whether to allow the use of the template data by deleting or replacing the overlapping part data with the overlapping part data, even if the approval Even if input is accepted from the template approver, 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 on the side overlapping the overlapping part data is replaced with the template. When selection (1004 in FIG. 10 described later) of whether or not to permit use of data 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.

<Description of FIG. 9>

  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. It is generated 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 approve the template and judge whether it is good.

  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.

<Description of FIG. 6>

  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 template number 1510 in 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 process proceeds to step S605, and arranged on each page of the document data in step S602. In the case where the template data formed by overlapping a plurality of parts data is not included in the processed data, the process proceeds 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 process proceeds to step S606. If the template data has not been edited, the process 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 If it is information obtained by changing the layer of the part data included in the template data formed by overlapping the part data, the process proceeds to step S607, and if it is other editing information, 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 process advances to step S612 to delete or overlap the overlapping part data in the plurality of overlapping part data in the template. If the template data does not permit the use of the template data by replacing the part on the side overlapped with the part data on the side, the process proceeds to step S609.

  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 accepted according to the operation of the input device 209 by the document creator, the process proceeds to step S612. In step S611, the operation of the input device 209 is performed by the document creator. If the instruction to approve the document data is not accepted, the process returns 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.

<Description of FIG. 12>

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.

  1205 displays a preview of data arranged on the page. 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 template creation within the frame 1205 of the document data.

Next, a screen 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.

<Description of FIG. 16>

  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.

  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.

<Description of FIG. 17>

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.

<Explanation of FIG. 7>

  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.

<Description of FIG. 18>

  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.

<Description of FIG. 13>

  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 the present invention.

  As described above, according to the present invention, when the part data that is overlapped with other part data is not permitted to be used in a state where the other parts are not overlapped, the electronic document data using the part data is converted. It is possible to provide a mechanism capable of notifying the user who approves the fact.

  Further, according to the present invention, the template data, which is display information that is not permitted to be used in a state where a plurality of part data do not overlap, is used in the document data when the plurality of part data do not overlap. When the template data, which is display information that does not allow the use of replacing multiple parts data layers in the document data, is used by replacing multiple parts data layers, the electronic document using that template It is possible to provide a mechanism that can notify a user who approves data to that effect.

  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 (8)

An information processing system that manages template data formed by a plurality of parts data and display information as to whether or not to permit use of the template data in a state where the plurality of parts data do not overlap,
Display instruction means for instructing the client terminal to display an approval screen for approving the use of the document data requested for approval in accordance with the display request from the client terminal;
It is determined whether or not template data, which is display information that is not permitted to be used in a state where a plurality of part data do not overlap with the document data requested for approval, is used in a state where a plurality of part data does not overlap. Determination means for
The display instructing means does not have a plurality of part data overlapped with template data, which is display information that does not permit use in a state where a plurality of part data does not overlap the document data requested for approval by the determination means. An information processing system characterized by instructing a client terminal to display the approval screen that makes it possible to identify when it is determined that it is being used in a state. An information processing system for managing template data formed by a plurality of parts data and display information as to whether or not to permit use of the template data by exchanging layers of the plurality of parts data,
Display instruction means for instructing the client terminal to display an approval screen for approving the use of the document data requested for approval in accordance with the 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 Means and
The display instructing means replaces the plurality of parts data layers with the template data, which is display information that does not permit the use by replacing the plurality of parts data layers with the document data requested for approval by the determination means. An information processing system that, when determined to be used, instructs a client terminal to display the approval screen that makes it possible to identify the fact.   The display instructing means includes template data that 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 by the determination means, but the plurality of part data does not overlap. 2. The information processing system according to claim 1, wherein, when it is determined that the data is used in a state, the information processing system instructs to display the approval screen in which thumbnails of the plurality of part data are further displayed.   The display instructing unit displays the approval screen so as to be able to identify a part where the other part data overlaps among the part data overlapping among the thumbnails of the plurality of part data. The information processing system according to claim 3, wherein an instruction is given. In accordance with a display request from the client terminal, further comprising a list screen display instruction means for instructing the client terminal to display a list screen of the document data that has not been approved,
The list screen display instruction means is template data that is display information that is not permitted to be used in a state where a plurality of part data do not overlap among the document data included in the list screen, and the plurality of parts data overlap. 5. The display of a list screen of the document data that has not been approved so as to be able to identify document data including template data that is used in a state where the document data is not used is instructed to be displayed on a client terminal. The information processing system according to any one of claims. A control method for an information processing system that manages template data formed by a plurality of part data and display information indicating whether or not to permit use of the template data in a state where the plurality of part data do not overlap. And
A display instruction step in which the display instruction means of the information processing system instructs the client terminal to display an approval screen for approving the use of the document data requested for approval in accordance with the display request from the client terminal;
The determination means of the information processing system is in a state in which 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, does not overlap a plurality of part data And a determination step for determining whether or not it is used in
In the display instruction step, 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 by the determination step, does not overlap a plurality of part data. A control method for an information processing system, characterized in that, when it is determined that the information is being used in a state, the client terminal is instructed to display the approval screen that can identify the fact. An information processing system for managing template data formed by a plurality of parts data and display information as to whether or not to permit use of the template data by exchanging layers of the plurality of parts data,
A display instruction step in which the display instruction means of the information processing system instructs the client terminal to display an approval screen for approving the use of the document data requested for approval in accordance with the display request from the client terminal;
The determination means of the information processing system uses the template data, which is display information that does not permit the use of replacing the plurality of parts data layers with the document data requested for approval, by replacing the plurality of parts data layers. A determination step for determining whether or not
In the display instruction step, the template data, which is display information that does not permit the use of replacing the plurality of parts data layers with the document data requested for approval in the determination step, replaces the plurality of parts data layers. A control method for an information processing system, characterized in that, when it is determined that the approval screen is being used, an instruction to display the approval screen that makes it possible to identify the fact is displayed on a client terminal. The computer program for functioning a computer as each means of the information processing system of any one of Claims 1 thru | or 5.

Images