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

Description

Regarding the information processing system, the control method of the information processing system, and the program , especially when there is part data to be changed in the part data used in the already created electronic document data, the person in charge of changing the part data And a mechanism for facilitating the understanding of a change request by a person in charge of changing the component data .

  In order to create electronic document data that is commonly used in the company, those electronic document data that can be used in common are made into parts in advance, and the electronic document is created by laying out the parts. ing. In that case, the part created by the person in charge of creating the part is made public for creating electronic document data, and the person in charge of creating the electronic document creates the electronic document by selecting the part data and performing layout processing. .

  Since the above-mentioned parts cannot be used as they are once created, it is naturally possible to perform an update process as necessary. Of course, electronic document data including parts before update may not be used. For example, it is determined by laws and ordinances, etc., in materials for explaining financial products to customers, etc. In such cases, electronic document data must be included in electronic document data. Electronic document data must be created in compliance with the laws and regulations.

  Therefore, Patent Document 1 discloses a technique for replacing a part in the structured document data with a new updated part when the part is updated so that the part included in the structured document data is the latest. Has been.

Japanese Patent Laid-Open No. 06-119335

  When multiple parts are used in one electronic document data, there is a risk that consistency between multiple parts may not be achieved if updated to the latest one. It is desirable to let the creator determine whether or not to update the part, and update the part used in the electronic document data if necessary.

  However, the creator of the part data and the creator of the electronic document data are not necessarily the same, and in order to recognize whether or not the part included in the electronic document data created by the creator of the electronic document data has been updated. Must receive a notification from the creator of the part data or always confirm the update of the part data.

  It is difficult for the creator of the part data to grasp all of the electronic document data in which the created part data is used, and the creator of the electronic document data including the part data created by itself is informed to the part data It was difficult to notify the update. As a result, there has been a problem in that electronic document data using a component that is prohibited from being continuously used continues to be used without updating the electronic document data that needs to be updated.

The present invention, in the component data already used in the electronic document data created, if there is to be change part data, and notify the change personnel of the component data, and changes in charge of the component data an object of the present invention that you facilitate the understanding of the change request by the person.

The present invention is an information processing system that supports the creation of document data created by laying out part data, the management means managing part data laid out in the document data, and the management means The document data is created using the component data for information indicating a change request for the component data, including notification that the component data is inconsistent with other component data. a change request accepting unit that accepts from the document creation user, storage means for storing information indicating a change request received by the change request accepting unit, a display request receiving means for receiving a display request of the component data, the display request receiving means information indicating a change request for the component data accepting the display request is stored in the memory means by The case, characterized in that it comprises a corresponding component data, and display means for displaying an identifiable screen the other component data which is the component data inconsistent. The present invention also provides an information processing system that supports creation of document data created by laying out component data, the management unit managing component data laid out in the document data, and the management unit. Information indicating a change request for managed component data, a change request receiving unit that receives from the document creation user who creates the document data using the component data, and information indicating the change request received by the change request receiving unit Information indicating a change request for the component data for which the display request has been received by the display request receiving unit. to, be the component data at identifiable screen, a change request for the component data shown Display means for displaying a screen including the information, to the component data displayed by the display unit, when receiving an editing instruction from the component creation user, the document creation you make changes requested by the change request accepting unit And updating means for updating the component data laid out in the document data created by the user.

Further, the present invention is a control method for an information processing system that includes management means for managing component data laid out in document data, and supports creation of document data created by laying out the component data, The change request receiving unit of the information processing system issues a change request for the component data including a notification that the component data is inconsistent with other component data for the component data managed by the management unit. Information indicating the change request received from the document creation user who creates the document data using the component data, and the change request received by the storage unit of the information processing system in the change request receiving step. The storing step for storing and the display request receiving means of the information processing system receive the display request for the component data. And shows the request receiving step, when the display unit of the information processing system, information indicating a change request for the component data of accepting the display request by the display request receiving step is stored in the storing step, the component data When, characterized in that it comprises a display step of displaying the part data and screens capable of identifying and said other component data which is to be inconsistent. Further, the present invention is a program executable by an information processing system that includes management means for managing component data laid out in document data and supports creation of document data created by laying out the component data. Information indicating a change request for the component data including notification that the component data is inconsistent with other component data for the component data managed by the management unit. and a change request accepting unit that accepts from the document creation user creating the document data by using the component data, storage means for storing information indicating a change request received by the change request accepting unit, the display of the component data Display request receiving means for receiving a request, and the component data for which a display request has been received by the display request receiving means When the information indicating the change request against is stored in the storage means, to function as the part data and, the part data and display means for displaying an identifiable screen the other component data is inconsistent It is characterized by that. Further, the present invention is a control method for an information processing system that includes management means for managing component data laid out in document data, and supports creation of document data created by laying out the component data, the change request accepting means of the information processing system, information indicating a change request for the component data managed by said management means, the component change request accepting step of data using the accepted from document creation user creating the document data And a storage step in which the storage means of the information processing system stores information indicating the change request received in the change request reception step, and a display request reception means of the information processing system receives the display request for the component data. The display request receiving step and the display means of the information processing system are displayed by the display request receiving step. When the information indicating the change request for requesting the accepted part data is stored in the storing step, a corresponding component data is identifiable screen, displays the screen including information indicating a change request for the component data performing a display step of, updating means of the information processing system, with respect to the component data displayed by said display step, when receiving an editing instruction from the component creation user, a change request by the change request accepting step And an update step of updating the component data laid out in the document data created by the document creation user. Further, the present invention is a program executable by an information processing system that includes management means for managing component data laid out in document data and supports creation of document data created by laying out the component data. The change request receiving means for receiving a change request for the component data managed by the management means from a document creation user who creates the document data using the component data, and the change request receiving Storage means for storing the change request received by the means, display request receiving means for receiving the display request for the component data, and a change request for the component data for which the display request has been received by the display request receiving means is stored in the storage means. The part data can be specified, and the part data Said display means for displaying a screen including a change request, to the component data displayed by the display unit, when receiving an editing instruction from the component creation user, who made the change requested by the change request accepting unit against It is made to function as an update means for updating the component data laid out in the document data created by the document creation user.

According to the present invention, in the component data already used in the electronic document data created, if there is to be change part data, and notify the change personnel of the component data, and change of the component data the grasp of the changes requested by the person in charge can you easily.

It is a system configuration diagram showing an example of a document management system of the present invention. It is a block diagram which shows an example of the hardware constitutions of the information processing apparatus applicable as a document management server. It is a schematic diagram which shows the structure of the electronic document data produced with the document production assistance system of this application. It is a schematic diagram which shows the structure of the various data used for electronic document data preparation. It is a schematic diagram for demonstrating the update / public / non-disclosure / continuation use disabling setting of material data, part data, and template data of the present invention. 4 is a flowchart illustrating document management processing performed by the document management server 101. It is a flowchart which shows the detail of the "material data update process" of step S603 of FIG. 7 is a flowchart showing “details of part data update processing” in step S605 of FIG. 6. It is a flowchart which shows the detail of "template data update process" of step S607 of FIG. 7 is a flowchart showing details of “electronic document data update processing” in step S609 of FIG. 6. FIG. 11 is a flowchart showing details of “template / part update status confirmation processing” in step S1002 of FIG. 10. FIG. 12 is a flowchart showing details of the “template data update status confirmation process” in step S1101 of FIG. 12 is a flowchart showing details of “in-page component status confirmation processing” in step S1102 of FIG. It is a flowchart which shows the detail of the "in-parts component status confirmation process" of step S1305 of FIG. 12 is a flowchart showing details of “in-page component update confirmation processing” in step S1103 of FIG. 11. It is a flowchart which shows the detail of the "parts update status confirmation process in parts" of step S1508 of FIG. 7 is a flowchart showing details of “electronic document data approval processing” in step S611 of FIG. 6. It is a schematic diagram which shows an example of the list screen of electronic document data. It is a schematic diagram which shows an example of the detailed display screen of electronic document data. It is a schematic diagram which shows an example of a data edit screen. It is a schematic diagram which shows an example of an approval data list display screen. It is a schematic diagram which shows an example of an electronic document data approval input screen. 10 is a flowchart illustrating document management processing performed by the document management server 101 in the second embodiment. It is a flowchart which shows the detail of the update process of step S2303 of FIG. It is a flowchart which shows the detail of the raw material data update process of step S2405 of FIG. It is a flowchart which shows the detail of the object data update process of step S2407 of FIG. 24, S2409, and S2411. It is a flowchart which shows the detail of the approval process of step S2305 of FIG. It is a flowchart which shows the detail of the object data approval process of step S2705 of FIG. 27, S2707, S2709, and S2711. It is a flowchart which shows the detail of the automatic update process of step S2832 of FIG. It is a flowchart which shows the detail of the components data automatic update process of step S2901 of FIG. 29, and S2902. 6 is a diagram illustrating an example of a configuration of an editable data list screen displayed on a client device. FIG. It is a figure which shows an example of a structure of a detailed display screen (material data). It is a figure which shows an example of a structure of a detailed display screen (document data). It is a figure which shows an example of a structure of an approval data required list screen. It is a figure which shows an example of a structure of the detailed screen of approval object data.

  Embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 is a system configuration diagram showing an example of the configuration of a document management 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 according to the present invention. Reference numeral 102 denotes a client device, which is a terminal used by a user who creates and approves electronic document data and the like in the document management system. Reference numeral 103 denotes a network such as a LAN (Local Area Network) for connecting the document management server 101 and the client apparatus 102 so as to be capable of data communication with each other.

  FIG. 2 is a schematic diagram illustrating an example of a hardware configuration of an information processing apparatus applicable as the document management server 101 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. The input controller 205 controls input from a pointing device such as a keyboard 209 or a mouse (not shown). The video controller 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.

  The memory controller 207 has an adapter in a hard disk (HD), floppy disk (registered trademark FD) or PCMCIA card slot for storing a boot program, 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 the network.

  The communication I / F controller 208 is connected to and communicates with an external device via a network, and executes communication control processing on 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 202, 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 document management server 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 management system of the present invention will be described with reference to FIG. FIG. 3 is a schematic diagram showing the structure of electronic document data created by the document management system of the present invention.

In the document management system of the present invention, part data composed of part data such as material data and a plurality of material data is arranged in a template selected by the user at a desired position as part data constituting electronic document data. Thus, electronic document data is created.

  In the figure, reference numeral 300 denotes template data, which is designated by the CPU 201 in accordance with the input unit operation by the user. In the template data 300, material data 301 and part data 302 can be arranged.

  301 is material data, for example, image data. By laying out the material data 301 on the template data 300, the part data 302 can be created using the material data 301. Reference numeral 302 denotes part data, which is created by combining a plurality of material data 301 and character string data. These template data 300, material data 301, and part data 302 are stored and managed in the external memory 211 of the document management server 101.

  With reference to FIG. 4, the configuration of various data used for creating electronic document data stored and managed in the external memory 211 of the document management server 101 will be described. In the external memory 211 of the document management server 101, an electronic document information table 401, an electronic document page part information table 402, a template information table 403, a part information table 404, a part internal part information table 405, and a material information table 406 are stored and managed. Has been.

  The electronic document information table 401 is a data table for managing electronic document data, which is created by the document management server 101 according to a user operation and stored in the external memory 211. The document number 401-1, the template number 401- 2, template update number 401-3, status 401-4, person in charge 401-5, and the like.

  The document number 401-1 includes identification information for uniquely identifying electronic document data, and the template number 401-2 includes a template number used to create the electronic document data (corresponding to 403-1 described later). Is memorized. The template update number 401-3 stores an update number (corresponding to update information 403-2 in a template information table 403 described later) for specifying the version of the template data being used. The status 401-4 stores the status of the electronic document data (for example, being created, waiting for approval, available, etc.). In the person in charge 401-5, person-in-charge information of a person in charge of creating the electronic document data is registered.

  The electronic document page component information table 402 is a data table for managing component data such as material data and part data used in the electronic document data, and includes a document number 402-1, a document page number 402-2, An update number 402-3, a component serial number 402-4, a component classification 402-5, a component number 402-6, a component update number 402-7, a warning flag 402-8, and the like.

  The document number 402-1 stores a document number for specifying a document, and corresponds to the document number 401-1 in the electronic document information table 401 described above. The document page number 402-2 stores information indicating the page number of the electronic document data. The update number 402-3 stores information indicating the number of updates of specific page data in the electronic document data uniquely indicated by the document number 402-1 and the document page number 402-2. When any page data in any electronic document data is updated, records are newly added to the electronic document page component table 402 by the number of components used in the page.

  The component serial number 402-4 stores the serial number of the component used in the page. The part classification 402-5 stores information indicating the classification of the parts in the page managed by the record, that is, whether the data is material data or part data. In the part number 402-6, when a part managed in the record is material data, a material number (corresponding to a material number 406-1 in a material information table 406 described later) is part data. Stores a part number (corresponding to a part number 404-1 in a part information table 404 described later). The component update number 402-7 stores an update number for specifying the version of the component being used. The warning flag 402-8 stores information indicating that the part data is in an unusable state, information indicating that the part data has been updated, and the like.

  The template information table 403 is a data table for managing information of template data used for electronic document data creation in the document management system, and includes a template number 403-1, an update number 403-2, a disclosure flag 403-3, and a continuation. It consists of an unusable flag 403-4 and the like.

  In the template number 403-1, identification information for uniquely identifying template data is stored. In the update number 403-2, update number information for specifying the version of the template data is stored. In the public flag 403-3, flag information (for example, 1: public 0: non-public) indicating whether or not the template data managed in the record is public is stored. The continuous use disable flag 404-4 stores a flag (for example, 1: use 0: use disabled) for determining whether or not the template data managed in the record can be used continuously.

  The part data information table 404 is a data table for managing part data information that can be used for electronic document creation in the document management system. The part number 404-1, the update number 404-2, and the disclosure flag 404-3. The continuous use disable flag 404-4 and the like.

  The part number 404-1 stores identification information for uniquely identifying the part data. The update number 404-2 stores an update number for specifying the version of the part data. In the disclosure flag 404-3, flag information (for example, 1: disclosure 0: non-disclosure) indicating whether or not the part data managed in the record is disclosed is stored. The continuous use disable flag 404-4 stores a flag (for example, 1: use 0: use disabled) for determining whether or not the part data managed in the record can be used continuously.

  The part-in-part information table 405 is a data table for managing parts used in the part data managed in the part information table 404, and includes a part number 405-1, an update number 405-2, and a part serial number. 405-3, part classification 405-4, part number 405-5, update number 405-6, warning flag 405-7, and the like.

  The part number 405-1 stores identification information (corresponding to the part number 404-1 in the part information table 404) for specifying the part data. The update number 405-2 stores update information for specifying which version of the part data specified by the part number 405-1 is used by the part managed in the record.

  The part serial number 405-3 stores the serial number of the part used in the part. In the part classification 405-4, information indicating the classification of the parts in the parts managed by the record, that is, whether the part is material data or part data is stored. In the part number 405-5, when the part data is material data, the material number for specifying the material data is part data. When the part data is part data, the part number for specifying the part data is used. Is memorized. The component update number 405-6 stores update information for specifying the version of the component data. The warning flag 405-7 stores information indicating that the component data is in an unusable state and that the component data has been updated.

  The material information table 406 is a data table for managing information on material data that can be used for electronic document creation in the document management system, and includes a material number 406-1, an update number 406-2, a disclosure flag 406-3, It consists of a continuous use disable flag 406-4 and the like.

  The material number 406-1 stores identification information for uniquely identifying the material data. The update number 406-2 stores an update number for specifying the version of the material data. In the disclosure flag 406-3, flag information (for example, 1: disclosure 0: non-disclosure) indicating whether or not the part data managed in the record is disclosed is stored. If it is open to the public, it can be used for new electronic document data and part data to be created. The continuous use disable flag 406-4 stores a flag (for example, 1: usable 0: unavailable) for determining whether or not the material data managed in the record can be used continuously. If the continuous use disabling flag is 0, the material data is material data that cannot be used even with existing electronic document data and part data.

  The above is a description of the configuration of various data used for creating electronic document data managed by the external memory 211 of the document management server 101.

  Next, with reference to FIG. 5, the update / public / non-disclosure / continuous use disabled setting of the material data, part data, and template data of the present invention will be described. As shown in FIG. 5, in the present invention, update data can be created after creating material data, part data, and template data. In order to manage the update history of the same data, an update number is assigned. Data version management by preparing different data update numbers for the same data number (template number for template data, part number for part data, material number for material data) It is carried out. Data disclosure (the data can be used to create new electronic document data, etc. (including update data)) / non-disclosure (creation of new data, such as new document data (including update data)) Can be used in the existing electronic document data (can be used in the already created electronic document data) / impossible (already available) The setting of “cannot continue to use the data in the created electronic document data” is managed by the continuous use disable flag.

As shown in the figure, it is possible to publish a plurality of versions of data at the same time, or not immediately after creating update data.

  An example of document management processing performed by the document management server 101 will be described with reference to FIG. A program used to execute this process is stored in the external memory 211 of the document management server 101. When performing this process, the CPU 201 loads the program into the RAM 202 and performs the process according to the control of the program. Will do.

  First, when receiving a connection request from the client apparatus 102, the CPU 201 performs a login process (step S601). In the login process, the login process is performed by receiving data necessary for user authentication, such as a user ID and password, from the client apparatus 102 and determining whether the set of these data is registered in a user information table (not shown). Done.

  When the login process is performed, after that, a request for updating material data is received from the client device 102 (step S602), a request for updating part data is received (step S604), or a request for updating template data is received (step S604). S606), whether an electronic document data update request has been accepted (step S608), or whether an electronic document approval processing request has been accepted (step S610) is constantly monitored. If it is determined that the material data update process has been accepted (YES in step S602), the material data update process (step S603: details are shown in FIG. 7) and the part data update request is accepted (YES in step S604). If it is determined that the part data update process (step S605: details are shown in FIG. 8), the template data update process is received (step S607: YES in step S606). The details will be shown in FIG.

  Furthermore, when it is determined that an electronic document data update request has been received (YES in step S608), an electronic document data update process (step S609: FIG. 10 for details), an electronic document data approval process request has been received (step If YES is determined in step S610, electronic document data approval processing (step S611: details are shown in FIG. 17) is performed.

  The above process is repeated until it is determined in step S612 that an instruction to end the process has been received. The above is an example of the document management process performed by the CPU 201 of the document management server 101.

  Next, details of the material data update processing in step S603 of FIG. 6 will be described with reference to FIG. In this material data update processing, new material data registration, registration of a new version of existing material data, change processing of the existing material data public flag 406-3, and continuation unavailable flag 406-4 are performed. become.

  First, when receiving a material data update processing request from the client device 102, the CPU 201 transmits screen information for displaying a material data selection screen (not shown) on the display device of the client device 102. Then, the material number input via the screen is received (step S701). Here, when the material number is not sent from the client apparatus 102, material data having a new material number is registered.

  After that, whether to register the material data, that is, update the part data specified by the material number and register the new version of the material data or the material data with the new material number. The determination is made according to the instruction information received from the client apparatus 102 (step S702).

  If YES in the determination process in step S702 (that is, material data is registered), the process proceeds to step S703, and newly registered data is acquired from the client apparatus 102. At this time, on the client device 102 side, designation of data (image data or the like) to be newly registered as material data is accepted in accordance with an input unit (keyboard 209 or a pointing device not shown) operation by the user. Then, the data for which the designation is accepted is transmitted to the document management server 101.

  Information input based on the user's operation in the client apparatus 102 as the status information of the material data acquired in step S703 is acquired from the client apparatus 102 (step S704).

  After that, whether to change the status information of the material data of the existing version is determined based on the instruction information received from the client apparatus 102 (step S705), and if it is determined to change the status (YES in step S705) The client apparatus 102 acquires the update number for identifying the version whose status is to be changed and the status information (public flag 406-3, continuation unusable flag 406-4, etc.) received by the client apparatus 102 from the user ( Step S706).

Here, when information indicating that the disclosure flag is set to “unpublished” is acquired as the status information, as described with reference to FIG. 5, the material data of the existing version is received after the information is received (or After this information is reflected in the material data information table 406), it is handled as unusable material data when creating electronic document data or parts data.

  In addition, when the status information is acquired to make the existing material data “unusable continuously”, the material data of that version is not only the electronic document data and parts data to be created in the future, but also the existing electronic data. Document data and other parts data are treated as material data that cannot be used. That is, existing electronic document data and part data that use existing versions of material data are data that must be updated. Note that material data for which the disclosure flag is set to “unpublished” and “continuous use is not allowed” is not accepted, but it can still be used with existing electronic document data and part data. Is recommended update data (data that should be updated).

  Then, the material data information table 406 is updated based on the information acquired from the client apparatus 102 in steps S703, S704, and S706 (step S707). This update can be performed immediately after information is acquired (real-time processing), or when a certain time is reached (for example, midnight), the information acquired so far can be updated all at once (batch processing). Either one does not matter.

  The above is the material data update processing. By performing this process, it is possible to suitably add or update material data, change the status, and the like.

  Next, the part data update processing in step S605 of FIG. 6 will be described with reference to FIG. In this part data update process, new part data registration, new part data registration of existing part data, change process of existing part data disclosure flag 404-3 and continuation unavailable flag 404-4 are performed. Will do.

  First, when receiving a part data update processing request from the client device 102, the CPU 201 transmits screen information for displaying a part data selection screen (not shown) on the display device of the client device 102. Then, by acquiring the part number 404-2 input via the screen, the specification of the part data is accepted (step S801). Here, when the part number is not sent from the client apparatus 102, the part data having a new part number is registered.

After that, whether to register the part data, that is, update the part data specified by the part number, whether to register the new version of the part data or the part data with the new part number The determination is made according to the instruction information received from 102 (step S802).

  If YES in the determination process in step S802 (that is, registering part data), the process proceeds to step S803, and information on the part data to be newly registered is acquired from the client apparatus 102 (step S803). This part data information includes information on parts included in the part data (material number, update number of material data, part number and update number of other part data).

  Then, the information input as the status information of the part data acquired in step S803 is acquired from the client device 102 (step S804). After that, whether to change the status information of the existing part data of the version is determined based on the instruction information received from the client apparatus 102 (step S805), and when it is determined to change the status (YES in step S805). Is an update number 404-2 for specifying a version for updating the status information, and status information received from the user by the client apparatus 102 as the updated status information (public flag 404-3, continuation unavailable flag 404- 4) from the client apparatus 102 (step S806).

Here, when the information that the disclosure flag 404-3 is set to “unpublished” is acquired as the status information, the specified version of the part data is registered after this information is registered in the part data information table 404. When electronic document data or other part data is created, it is treated as part data that cannot be selected (that is, cannot be used).

  In addition, when the status information is acquired to make the existing parts data “unusable”, the version of the part data is not only the electronic document data and other parts data to be created in the future, but also the existing part data. The electronic document data and other parts data cannot be used as parts. In other words, the electronic document data and other parts data that use the version of the part data are data that must be updated. For part data that has been set to “unpublished” and the designation of “unusable continuously” has not been accepted, it is possible to continue using existing electronic document data or other part data. Data and other parts data are recommended update data (data that should be updated).

  Then, the parts data information table 403 is updated based on the information acquired from the client device 102 in steps S804 and S806, and the parts data internal parts information table 405 is updated based on the information acquired in step S803. This update can be performed immediately after information is acquired (real-time processing), or when a certain time is reached (for example, midnight), the information acquired so far can be updated all at once (batch processing). Either one does not matter.

  The above is the update process of parts data. By performing this process, it is possible to suitably add or update part data, change the status, and the like.

  Next, the template data update processing in step S607 of FIG. 6 will be described with reference to FIG. In this template data update processing, new template data registration, registration of new version data of existing template data, change processing of the existing template data public flag 403-3 and continuation unusable flag 403-4 are performed. Will do.

  First, when receiving a template data update processing request from the client device 102, the CPU 201 transmits screen information for displaying a template data selection screen (not shown) on the display device of the client device 102. And the specification of template data is received by acquiring the template number input via the screen (step S901). If the template number is not sent from the client apparatus 102, template data having a new template number is registered.

  After that, whether to register template data, that is, whether to update template data specified by the template number, register new version template data, or register template data having a new template number. The determination is made according to the instruction information received from the client device 102 (step S902).

  If YES in the determination process in step S902 (that is, template data is registered), the process proceeds to step S903, and newly registered data is acquired from the client device 102.

  Then, information input based on the user operation in the client apparatus 102 as the status information of the template data acquired in step S903 is acquired from the client apparatus 102 (step S904). After that, whether to change the status information of the template data of the existing version is determined based on the instruction information received from the client apparatus 102 (step S905), and if it is determined to change the status (YES in step S905) , An update number 403-2 for specifying the version of the template data whose status is to be changed, and status information received by the client device 102 from the user (public flag 403-3, continuation unavailable flag 403-4) Etc.) from the client device 102 (step S906).

As with the part data and material data, when the information that the disclosure flag is set to “private” is acquired as the status information, the template data of the existing version is received after the information is received (or this information is the template data). After being reflected in the information table 403), it is handled as unusable template data when electronic document data is created.

  In addition, when information indicating that the existing template data is set to “unusable continuously” is acquired as the status information, the template data of the version is not only the electronic document data to be created in the future, but also the existing electronic document data. It will be treated as unusable template data. That is, the existing electronic document data that uses the existing version of the template data is data that must be updated. Note that template data for which the public flag has been set to “unpublished” and “continuous use disabled” has not been accepted can be used with existing electronic document data or part data. The data is recommended update data (data that should be updated).

  Then, the template data information table 403 is updated based on the information acquired from the client apparatus 102 in steps S903, S904, and S906 (step S907). This update can be performed immediately after information acquisition (real-time processing), or when a certain time is reached (for example, midnight), the information acquired so far can be updated all at once (batch processing). Either one does not matter.

  The template data update processing has been described above. By performing this process, it is possible to suitably add or update template data, change the status, and the like.

  Next, the electronic document data update processing in step S609 in FIG. 6 will be described with reference to FIG. This processing is performed when the part data (part data or material data) used in the electronic document data that the person in charge is responsible for cannot be used continuously, It is performed for the purpose of suitably notifying that a new version has been registered. This processing is performed by the CPU 201 of the document management server 101 in accordance with the control of the program stored in the external memory 211 of the document management server 101.

  If the CPU 201 determines that an electronic document data update request has been received (YES in step S608 in FIG. 6), the electronic document data in which the user specified in the login process (step S601 in FIG. 6) is the person in charge is electronically stored. Obtained from the document data information table 401 (step S1001). Thereafter, template / part update status confirmation processing is performed for all electronic document data acquired in step S1001 (step S1002). Details of this template / part update status confirmation processing will be described with reference to FIG.

  Details of the template / part update status confirmation processing in step S1002 of FIG. 10 will be described with reference to FIG. In this process, the CPU 201 continues to disable use of template data, part data, and material data used in electronic document data to be checked, or a new version of data is registered (updated). Check whether or not.

  First, in step S1101, the CPU 201 performs a template data update status confirmation process (step S1101). Details of this processing will be described with reference to FIG.

  FIG. 12 is a flowchart showing details of the template data update status confirmation processing in step S1101 of FIG. In this process, the CPU 201 confirms whether the template data used in the electronic document data is unusable or whether a new version of the template data is registered (updated).

  First, in step S1201, the template data information table 403 is searched using the template number 401-2 of the electronic document data as a key, and a record having the same template number as the template data used in the electronic document data is acquired. Of these records, the continuation unusable flag 403-4 of the version of the template data used in the electronic document data (the record whose update number matches the template update data 401-3) is confirmed to be used. It is determined whether the template data being stored is data that cannot be used continuously (step S1202). If the CPU 201 determines in step S1202 that the data cannot be used continuously (YES), the process proceeds to step S1203, and the RAM 202 stores that the template data is data that cannot be used continuously.

  Thereafter, whether or not the template data has been updated by checking whether there is a record having an update number 403-2 that is larger than the template update number 401-3 among the records acquired in step S1201 (update Whether there is information) is determined (step S1204). If the CPU 201 determines in step S1204 that there is update information (YES), the process proceeds to step S1205, and the fact that the template data is template data with update is stored in the RAM 202.

  By performing the above processing, it is possible to suitably check whether the template data used for the electronic document data is unusable or updated template data.

  Returning to the description of FIG. After the processing in step S1101, the in-page component status confirmation processing (step S1102) and the in-page component update confirmation processing (step S1103) are performed on all pages of the electronic document data. Details of the in-page component status confirmation processing will be described with reference to FIG. 13, and details of the in-page component update confirmation processing will be described with reference to FIG.

  FIG. 13 is a flowchart showing details of the in-page component status confirmation processing in step S1102 of FIG. This process is performed to determine whether each component data used in the electronic document data is not continuously usable, and is performed by the CPU 201 of the document management server 101. The program used to execute this process is stored in the external memory 211 of the document management server 101. The CPU 201 loads the program into the RAM 202 when performing this process, and executes this process according to the control of the program. Will do.

  First, the CPU 201 acquires all component data used in the designated page of the electronic document data from the electronic document data component information table 402 (step S1301). Then, the processing in steps S1302 to S1309 is performed on all the component data acquired in step S1301.

  In step S1302, the CPU 201 determines whether the component data to be processed is part data or material data according to the component classification 402-5 of the electronic document data component information table 402 (step S1302). If it is determined that the data is part data (part in step S1302), the process proceeds to step S1303, and the part data in the part data information table 404 (parts having the same part number and update number) cannot be used continuously. The flag 404-4 is acquired. In accordance with the acquired value in step S1303, it is determined whether the part data can be used continuously (step S1304).

  If it is determined in step S1304 that continuous use is possible, the part status confirmation process in the part is performed to check whether other part data or material data used in the part data is not continuously usable. Is performed (step S1305). Details of this processing will be described with reference to FIG.

  Thereafter, the continuation unusable flag 404-4 of the part data, which may be updated in the process of step S1305, is acquired.

  If it is determined in step S1302 that the CPU 201 determines that the data is material data, the process proceeds to step S1307, and the material data (parts having the same material number and update number) in the part data information table 406 are transferred. The continuous use disable flag 406-4 is acquired.

  Then, after the process of step S1306 or step S1307 is completed, it is determined whether the part can be used continuously (step S1308). In this process, it is determined whether the continuous use disable flag 404-4 for the part data acquired in step S1306 or the continuous use disable flag 406-4 for the material data acquired in step S1307 is disabled.

  If it is determined in step S1304 or step S1308 that the component data cannot be used continuously, the process proceeds to step S1309, and the component data is stored in the RAM 202 as continuous use disabled data.

  By the above processing, when the component data used in the page of the electronic document data includes the component data that cannot be used continuously, it is possible to accurately acquire the data that cannot be used continuously.

  Next, with reference to FIG. 14, the details of the in-part component status confirmation processing in step S1305 of FIG. 13 will be described. This process is performed to determine whether each component (material data, part data) used in the part data is not continuously usable, and is performed by the CPU 201 of the document management server 101. . A program used to execute this processing is stored in the external memory 211 of the document management server 101, and the CPU 201 loads the program into the RAM 202 when performing this processing, and performs this processing in accordance with the control of the program. It will be.

  First, the CPU 201 acquires all the part data used in the part data to be confirmed from the part data in-part information table 405 (step S1401). Then, the processing in steps S1402 to S1410 is performed on all the component data acquired in step S1401.

  In step S1402, the CPU 201 determines whether the part data to be processed is part data or material data according to the part classification 405-4 of the part data in-part information table 405. If it is determined that the data is part data (part in step S1402), the process proceeds to step S1403, and the part data (parts having the same part number and update number) in the part data information table 404 cannot be used continuously. The flag 404-4 is acquired. Thereafter, it is determined whether the part data can be continuously used according to the acquired value in step S1403 (step S1404).

  If it is determined in step S1404 that continuous use is possible (YES in step S1404), in order to confirm whether other part data and material data used in the part data are not continuously usable, A part status confirmation process is performed using the part data, which is part data, as the confirmation target part data (step S1405).

  After that, the continuation unusable flag 404-4 of the part data that is subject to the confirmation process and that may be updated in the process of step S1405 is acquired.

  If it is determined in step S1402 that the CPU 201 determines that the data is material data, the process proceeds to step S1407, and the material data (parts having the same material number and update number) in the part data information table 406 are transferred. The continuous use disable flag 406-4 is acquired.

  Then, after the process of step S1406 or step S1407 is completed, it is determined whether the component data can be used continuously (step S1408). In this process, it is determined whether the continuous use disable flag for the part data acquired in step S1406 or the continuous use disable flag for the material data acquired in step S1407 is disabled.

  If it is determined in step S1404 or step S1408 that continuous use is not possible, the process proceeds to step S1409, and the continuous use disable flag 404-4 for the part data to be confirmed in the part data information table 404 is displayed. Is set to be unusable (step S1409). Thereafter, the component data is stored in the RAM 202 as data that cannot be used continuously (step S1410).

  As a result of the above processing, if the part data used in the part data contains part data that cannot be used continuously, the part data that is continuously unavailable cannot be obtained without fail. It is possible to set the part data that is used as the part data as the data that cannot be used continuously.

  Next, the details of the in-page component update confirmation process in step S1103 of FIG. 11 will be described with reference to FIG. This process is performed to determine whether each component data used in the electronic document data has been updated, and is performed by the CPU 201 of the document management server 101. The program used to execute this process is stored in the external memory 211 of the document management server 101. When this process is performed, the program is loaded into the RAM 202, and the process is performed according to program control. become.

  First, the CPU 201 acquires all the component data used in the designated page of the electronic document data from the electronic document data component information table 402 (step S1501). Then, the processing in steps S1502 to S1510 is performed on all the component data acquired in step S1501.

  In step S1502, the CPU 201 determines whether the component data to be processed is part data or material data according to the component classification 402-5 of the electronic document data component information table 402. If it is determined that the data is part data (part in step S1502), the process proceeds to step S1503, and a record having the same part number as the part data in the part data information table 404 is acquired. Then, by determining whether the record acquired in step S1503 has a record with an update number that is newer (a larger numerical value) than the update number of the part data to be confirmed, there is update data for the part data. Is determined (step S1504).

  If it is determined in step S1504 that there is update data (YES in step S1504), the process proceeds to step S1507. If it is determined that there is no update data (NO in step S1504), the process proceeds to step S1508. To migrate.

  If the CPU 201 determines that the data is material data in step S1502, a record having the same material number as the material data is acquired from the material data information table 406 (step S1505). Then, by determining whether the record acquired in step S1505 has a record that has a newer (larger numerical value) update number than the update number of the material data to be confirmed, there is update data for the material data. Is determined (step S1506). If it is determined that there is update data (YES in step S1506), the process proceeds to step S1507.

  In step S1507, the CPU 201 stores the component data determined to have update data in the RAM 202 as updated data.

  If it is determined NO in step S1504, the CPU 201 performs an in-part component update status confirmation process (step S1508). The reason for this processing is that the part data used in the part data is checked for updates to the creator of the electronic document data or the approver of the electronic document data. This is to provide information on parts data that has not been updated according to the update even though the part data used in the process is updated. Details of this processing will be described later with reference to FIG.

  As a result of the confirmation processing in step S1508, if it is determined that there is update data in the part data in the part (YES in step S1509), the part data (part data in this case) to be confirmed is not updated part data. Is stored in the RAM 202 (step S1510).

  The above is the description of the in-page data update confirmation process. By performing this processing, it is possible to suitably check whether or not the updated part data exists in the page of the electronic document data.

  With reference to FIG. 16, the details of the in-parts part update status confirmation processing in step S1508 of FIG. 15 will be described. This process is performed to determine whether each part data used in the part data has been updated, and is performed by the CPU 201 of the document management server 101. The program used to execute this process is stored in the external memory 211 of the document management server 101. When this process is performed, the program is loaded into the RAM 202, and the process is performed according to program control. become.

  First, the CPU 201 acquires all the part data used in the part data from the part data in-part information table 405 (step S1601). Then, the processing in steps S1602 to S1610 is performed on all the component data acquired in step S1601.

  In step S1602, the CPU 201 determines whether the part data to be processed is part data or material data according to the part classification 405-4 of the part data in-part information table 405. If it is determined that the data is part data (part in step S1602), the process proceeds to step S1603, and a record having the same part number as the part data registered in the part data information table 404 is acquired. Then, it is determined whether there is a record having an update number (larger numerical value) than the update number of the part data to be processed in the record acquired in step S1603, so that there is update data of the part data. Is determined (step S1604).

  If it is determined in step S1604 that there is update data (YES in step S1604), the process proceeds to step S1607. If it is determined that there is no update data (NO in step S1604), the process proceeds to step S1608. To migrate.

  If the CPU 201 determines in step S1602 that the data is material data, a record having the same material number as the material data is acquired from the material data information table 406 (step S1605). Then, it is determined whether there is a record having an update number (larger numerical value) than the update number of the material data to be confirmed in the record acquired in step S1605, so that there is update data of the material data. Is determined (step S1606). If it is determined that there is update data (YES in step S1606), the process proceeds to step S1607.

  In step S1607, the CPU 201 stores the component data determined to have update data in the RAM 202 as updated data.

  If it is determined NO in step S1604, the CPU 201 performs an in-part part update status confirmation process for the part data used as part data in the part data to be confirmed (step S1608).

  As a result of the confirmation processing in step S1608, if it is determined that there is update data in the part data in the part data to be confirmed (YES in step S1609), the part data in the part (in this case, part data) is not yet stored. The updated part data is stored in the RAM 202 (step S1610).

  The above is the description of the data update confirmation process in parts data. By performing this process, it is possible to suitably check whether updated part data exists in the part data.

  Returning to the description of FIG. Thereafter, screen information for displaying a list of electronic document data for which the user is in charge is displayed on the display device of the client device 102 (step S1003). The list screen is, for example, a screen as shown in FIG.

  FIG. 18 is an example of a list screen of electronic document data displayed on the display device of the client device 102. As shown in FIG. 18, when the electronic document data displayed in the list includes data that cannot be used continuously or data that has been updated, the information is displayed on the screen in order to provide the information to the user. (1801 in the figure). By generating screen information for displaying such a screen on the display device, it is possible to accurately notify the user of the presence of electronic document data including data that cannot be used continuously or data that has been updated.

  Returning to the description of FIG. Thereafter, when the document number 401-1 of the electronic document data input according to the input unit operation by the user operating the client device 102 is acquired from the client device 102 (step S 605), the document number 401-1 is specified. Screen information for displaying the detailed display screen of the electronic document data is generated and transmitted to the client apparatus 102 (step S606).

  FIG. 19 is an example of a detailed display screen of electronic document data displayed on the display device of the client device 102. As shown in FIG. 19, when the page of electronic document data displayed in detail includes data that cannot be used continuously or data that has been updated, the information is displayed on the screen to provide the user with the information. (1901, 1902 in the figure). In the example of FIG. 19, the material A on the test page 1 and the part B on the test page 2 are updated parts, and the part C on the test page 3 is a part that cannot be used continuously. To make it possible to recognize pages that contain parts that cannot be used continuously and pages that contain only updated parts and do not contain parts that cannot be used continuously, as shown in FIG. These pages are displayed with different display forms such as lines. This is an example.For example, by changing the color of the border or changing the display area, you can create a page that contains parts that cannot be used continuously and a page that contains only updated parts and no parts that cannot be used continuously. Of course, the user may be notified.

  When “edit this page” in the electronic document data detail display screen 1900 is designated, the electronic document data editing screen shown in FIG. 20 is displayed on the display device of the client device 102. The screen information necessary for this display is generated by the document management server 101.

  FIG. 20 is a diagram showing an example of an electronic document data editing screen. The user can input various instructions for creating electronic document data to the document management server 101 via this screen. If the page to be edited includes data that cannot be used continuously or data that has been updated, replacement candidate parts are displayed as shown in 2001. As a result, the user can accurately grasp the replacement candidate parts, and can easily perform the update operation.

  Returning to the description of FIG. Thereafter, when the CPU 201 of the document management server 101 receives an electronic document data registration request from the client device 102 (YES in step S1006), the electronic document data information (template, template), input from the client device 102 via FIG. Parts, materials, etc.) are acquired (step S1007), and the acquired electronic document data is registered in the electronic document data information tables 401 and 402 (step S1008). At that time, the status 401-3 of the electronic document data is registered as “waiting for approval” in order to register the electronic document data as data that needs to be approved.

  Thereafter, it is determined whether or not other data is to be updated. If it is determined that other electronic document data is to be updated, the processing from step S1004 to step S1008 is repeated.

  The above is the description of the electronic document data update process shown in FIG.

  Next, the details of the electronic document data approval process in step S611 in FIG. 6 will be described with reference to FIG. This process is used when the person in charge of approval of electronic document data makes part data (part data or material data) used for the electronic document data that he / she is in charge of continuation unavailable, or parts data This is performed for the purpose of suitably notifying that the new version of the electronic document data has been registered and preventing the approval processing for the electronic document data including the part data for additional use. This processing is performed by the CPU 201 of the document management server 101 in accordance with the control of the program stored in the external memory 211 of the document management server 101.

  If the CPU 201 determines that an electronic document data approval processing request has been received (YES in step S608 in FIG. 6), the CPU 201 is in charge of the user specified in the login processing (step S601 in FIG. 6). The obtained electronic document data is acquired from the electronic document data information table 401 (step S1701). Thereafter, template / part update status confirmation processing is performed for all electronic document data acquired in step S601 (step S1702). Details of the template / parts update status confirmation processing are as described with reference to FIG.

  Thereafter, screen information for displaying a screen including the list information of the document data requiring approval on the display device is generated and transmitted to the client device 102 (step S1703).

  FIG. 21 is a schematic diagram illustrating an example of the approval-necessary data list display screen displayed on the display device of the client device 102. As shown in FIG. 21, when the electronic document data displayed in the list includes data that cannot be used continuously or data that is updated, the information is displayed on the screen to provide the information to the person in charge of approval. (2101 in the figure). By generating screen information for displaying such a screen on the display device, it becomes possible to accurately notify the person in charge of the existence of electronic document data including data that cannot be used continuously or data that is updated.

  Returning to the description of FIG. After that, when the document number 401-1 of the electronic document data input according to the input unit operation by the approval person who operates the client device 102 is acquired from the client device 102 (step S1704), the document number 401-1 is specified. Screen information for displaying the electronic document data approval input screen is generated and transmitted to the client apparatus 102 (step S1706).

  FIG. 22 is a schematic diagram showing an example of an electronic document data approval input screen. As shown in FIG. 22, on the electronic document data approval input screen, a detailed information display column of electronic document data to be approved, a control for inputting approval (“Approval” in the figure), and a denial A control ("deny" in the figure) for inputting is provided. A warning message is displayed when data that cannot be used continuously (template, part, material) is used for electronic document data to be approved (2201). In addition, in the case of approval for publishing the electronic document data, the control for inputting approval for the electronic document data to be approved is grayed out (invalidated) and the approval input is This is prohibited (2202). As a result, it is possible to suitably prevent the approval of disclosure of electronic document data including data that cannot be used continuously.

  Returning to the description of FIG. Thereafter, the CPU 201 accepts an input of an approval / denial instruction input via FIG. 22 from the client device 102 (step S1701), and updates the electronic document data information table according to the received instruction (step S1707). More specifically, the status of the electronic document data subject to approval / denial is changed.

<Second Embodiment>
Hereinafter, a second embodiment of the present invention will be described. In the second embodiment of the present invention, an example will be described in which when material data and part data included in a plurality of electronic documents are updated, they are collectively changed. In this embodiment, when a change is made to a certain material data or part data, the person in charge of creating the document data, etc., instead of updating the document data etc. in which the material data and the part data are used collectively. However, an example will be described in which a change request is made to material data, part data, etc. other than its own charge, and automatic update is performed when an update that satisfies the change request is performed.

  FIG. 23 is a flowchart illustrating document management processing performed by the CPU 201 of the document management server 101 in the second embodiment. The program used to execute this process is stored in the external memory 211 of the document management server 101. When this process is performed, the program is loaded into the RAM 202, and the process is performed according to program control. become.

  First, when receiving a connection request from the client apparatus 102, the CPU 201 performs a login process (step S2301). During the login process, the client apparatus 102 receives information necessary for user authentication, such as a user ID and password, and determines whether the data set is registered in a user information table (not shown). I do.

  When the user is specified by performing the login process, thereafter, the client apparatus 102 receives an update process or approval process request for material data, part data, template data, and electronic document data.

  If a data update process request is received (YES in step S2302), the process advances to step S2303 to perform a data update process. Details of this processing will be described later with reference to FIG.

  If a data approval process request is received (YES in step S2304), the process advances to step S2305 to perform data approval process. Details of this processing will be described later with reference to FIG.

  Then, the above process is performed until it is determined that the process is to be ended due to a logoff request from the client apparatus 102 or no request from the client apparatus 102 for a certain period of time (YES in step S2306). The above is the document management processing by the CPU 201 of the document management server 101 in the second embodiment.

  Next, details of the “update process” in step S2303 of FIG. 23 will be described with reference to FIG. Note that the processing shown in steps S2401 to S2412 in this figure is executed by the CPU of the client apparatus 102, and the processing shown in steps S2421 to S2425 is executed by the CPU 201 of the document management server 101.

  First, the client apparatus 102 transmits a data update request including the user information authenticated by the user authentication process in step S2301 of FIG. 23 to the document management server 101 (step S2401). When a data update request including user information is received from the client apparatus 102 (step S2421), the user is in charge of the document data 401, template data 403, part data 404, and material data 406 stored in the external memory 211. The data that is a person is acquired (step S2422). Then, the target data status confirmation process is performed on all the data acquired in step S2422 (step S2423). Here, for example, when the target data is part data, the in-part part status confirmation process of FIG. 14 is performed.

  In this process, the part data or part data used as part data, template data, or document data part data or material data is in a state in which unusable data is included, or is used for the data. This is a process of checking whether data that is not up-to-date is included by creating and registering data with different versions of part data and material data.

  In step S2423, after the target data confirmation processing for all the data acquired in step S2422 is completed, list screen information of target data to be displayed on the display device of the client device 102 is created (step S2424), and the created list is displayed. The screen information is transmitted to the client apparatus 102 that has made the data update request (step S2425).

  When receiving the list screen information from the document management server 101 (step S2402), the CPU of the client apparatus 102 performs screen display according to the list screen information (step S2403). The editable data list screen displayed here is a screen as shown in FIG. 31, for example.

  Here, an example of the editable data list screen 3100 displayed on the display device of the client device 102 in step S2403 of FIG. 24 will be described with reference to FIG. Since this list screen 3100 is substantially the same as the list screen 1800 already described with reference to FIG. 18, only different items will be described.

  The difference from the list screen 1800 shown in FIG. 18 is that, in addition to information such as unusable part data and updated part data used as part of data related to document data, part data, etc., parts Information indicating that the data has become inconsistent ("Inconsistent": 3101) or automatically updated in document data or other data when part data is updated The information ("automatic update": 3102) indicating whether or not the setting for updating the part data includes part data set in other document data or the like is displayed. The above is the description of FIG.

  Returning to the description of FIG. After the display of the list screen in step S2403, if designation for the material data included in the list screen 3100 is accepted (YES in step S2404), a material data update process is performed (step S2405). Details of this processing will be described with reference to FIG.

  If designation for part data included in list screen 3100 is received (YES in step S2406), target data update processing (parts) is performed (step S2407). If designation for template data is accepted (YES in step S2408), target data update processing (template) is performed (step S2409). If designation for document data is received (YES in step S2410), target data update processing (document) is performed (step S2411). Details of the processing in steps S2407, S2409, and S2411 will be described later with reference to FIG.

  When the processes in steps S2405, S2407, S2409, and S2411 are completed, it is determined whether to continue or end the data update process according to the operation instruction from the user (step S2412). (NO in step S2412), the process proceeds to step S2401, and the subsequent processes are repeatedly executed.

  On the other hand, if it is determined that the present process is to be terminated (YES in step S2412), the present process is terminated. The above is the details of the update processing in step S2303 in FIG.

  Next, the details of the material data update processing in step S2405 in FIG. 24 will be described with reference to FIG. Note that the processing shown in steps S2501 to S2512 in this figure is performed by the CPU of the client apparatus 102, and the processing shown in steps S2521 to S2532 is performed by the CPU 201 of the document management server 101.

  First, the CPU of the client device 102 transmits a detailed data request for material data that has been designated on the list screen 3100 displayed on the display device, to the document management server 101 (step S2501).

When the CPU 201 of the document management server 101 receives the detailed data request for the material data from the client apparatus 102 (step S2521), the CPU 201 acquires information on the material data from the external memory 211 (step S2522). The judges then whether the change request data with respect to the material data is registered in the change request data table (step S2523).

  If it is determined in step S2523 that the change request data is registered in the change request data table, the process proceeds to step S2524, and the change request data is acquired.

  Thereafter, detailed display screen information of the material data is created (step S2525), and the created detailed display screen information is transmitted to the client apparatus 102 that has requested the detailed data of the material data (step S2526). Then, when receiving the detailed display screen information from the document management server 101 (step S2502), the CPU of the client device 102 displays the detailed display screen (material data) shown in FIG. 32 on the display device according to the detailed display screen information (step S2502). Step S2503).

  Here, with reference to FIG. 32, an example of the configuration of a detailed display screen (material data) 3200 displayed on the display device of the client apparatus 102 in step S2503 of FIG. 25 will be described.

  As shown in FIG. 32, the detailed display screen (material data) 3200 includes a material data basic information display column 3201, a status change button 3202, an edit button 3203, an inconsistent data list display unit 3204, a change request data list display unit 3205, An update button 3206, a new creation button 3207, and a cancel button 3208 are provided.

  The material data basic information display column 3201 is a display column in which the material ID, update number, and thumbnail image of the material data are displayed. A status change button 3202 is a button used to give an instruction to change the status of the material data. When an instruction to press this button is received, a status editing screen (not shown) is displayed, and a status change input can be performed. An edit button 3203 is a button used to issue an instruction to edit new material data ((updated version material data, material data having a new ID derived from the material data). A data editing screen as shown in FIG. 20 is displayed, and material data can be edited.

  The inconsistent data list display unit 3204 is a display unit that displays other component data (material data, part data) that is inconsistent with the material data. Each inconsistent data is set with link information 3204-1 used to refer to the data. When receiving a click instruction for the link information, the client PC 102 requests the document management server 101 for component data that is inconsistent data.

The change request data list display unit 3205 is a display field for displaying a change request for the material data, and is a display field for displaying why a user makes a change request for the material data. Although only one data is displayed in FIG. 32, when a plurality of change requests are made for different reasons, a plurality of change request data are displayed in this column.

  After editing the material data, the person in charge of the material data inputs which change request corresponds to the editing of the material data. The cancellation check box 3205-1 is a control for accepting the input.

  An update button 3206 is a button used to request registration of material data having the same material number but different update numbers. A new creation button 3207 is a button used to request registration of material data having a different material number, which is derived from the material data. A cancel button 3208 is a button used for ending the editing operation in accordance with the user's input device operation via this screen. The above is an example of the configuration of the detailed display screen (material data) 3200 in FIG.

  Returning to the description of FIG. Upon receiving a press instruction for the inconsistent data link information 3204-1 included in the detailed display screen (material data) 3200 displayed in step S2503, the CPU of the client apparatus determines that there is a request for displaying inconsistent data. (YES in step S2504), the document management server 101 is requested for inconsistent data, which is other component data that is inconsistent with the material data, in accordance with the link information of the inconsistent data for which the pressing instruction has been accepted. When the inconsistent data transmitted in response to the request is received from the document management server 101, the inconsistent data is displayed on the display device (step S2505). By adopting such a configuration, the person in charge of the material data can perform the change processing of the material data while referring to other component data that has caused inconsistency.

  Also, when an instruction to create new material data input by receiving an instruction to press the edit button 3203 on the detail display screen 3200 is received (YES in step S2506), the edit screen shown in FIG. 20 is displayed on the display device. The material data is edited (step S2507).

Further, when receiving the status change request for existing data entered by user presses instruction to the status change button 3202 details display screen 3200 (YES in step S2508), the input of the status information after the change of the existing data Is received (step S2509). For example, here, the non-public data (public flag: 0) is made public data (public flag: 1), or the continuously usable data (continuous use flag: 1) is made continuously unavailable data (continuous use flag: 0). Change processing to be accepted.

  Thereafter, when an update instruction input by a press instruction to the update button 3206 or the new creation button 3207 is received (YES in step S2510), update information of material data is created (step S2511). When an instruction to press the update button 3206 on the detail display screen 3200 is received, update information for registering the update version data of the material data is received. When an instruction to press the new creation button 3207 is received, Update information for creating new material data derived from the material data is created. If only status change processing is performed, only the update button 3206 is valid.

  At this time, the information included in the update information includes update data or status information such as the release flag and the continuation unusable flag in the case of creating an updated version or new material data. Corresponding information (information indicating which cancellation check box 3205-1 was checked) or the like.

  In step S 2512, the material data update information created in step S 2511 is transmitted to the document management server 101.

  The CPU 201 of the document management server 101 receives the material data update information from the client device 102 (step S2527). If the material data update information is a status change of the existing data (YES in step S2508), the status of the existing data is changed (step S2529).

  In the case of registration of new material data (update version material data, derived new material data) (YES in step S2530), the new material data is registered (step S2531).

  Then, the material data whose status has been changed by the above processing and the newly created material data are set as the approval required data (step S2532). The above is the details of the material data update processing in step S2405 in FIG.

Next, the details of the target data update processing in steps S2407, S2409, and S2411 in FIG. 24 will be described with reference to FIG. Note that the processing shown in steps S2601 to S2616 in this figure is performed by the CPU of the client apparatus 102, and the processing shown in steps S2621 to S2637 is performed by the CPU 201 of the document management server 101.

  First, when the client apparatus 102 determines that part data specification is received in step S2406 in FIG. 24, when it is determined that template data specification is received in step S2408, or when document data specification is received in step S2410. Then, a request for detailed data of the data (target data) whose designation has been received is transmitted to the document management server 101 (step S2601).

  When receiving the detailed data request for the target data from the client apparatus 102 (step S2621), the CPU 201 of the document management server 101 acquires the detailed data of the target data from the external memory 211 (step S2622). Thereafter, the status confirmation process of the target data for which the designation is accepted is performed (step S2623). This process has already been described with reference to FIG. 11 (template / part update status confirmation process) and FIG. 12 (template data status confirmation process). Thereafter, it is determined whether a change request is made for the target data (step S2624). If it is determined that a change request is made (YES in step S2623), the change request data is acquired (step S2623). S2625).

  The detailed display screen information is created using the detailed data of the target data acquired in step S2622, the change request data acquired in step S2624, and the like (step S2626). Is transmitted to the client apparatus 102 that has performed (step S2627).

  When receiving the detailed display screen information from the document management server 101 (step S2602), the CPU of the client device 102 displays the detailed display screen 3300 shown in FIG. 33 on the display device according to the detailed display screen information (step S2603).

  Here, with reference to FIG. 33, an example of a detailed screen display displayed on the display device of the client device 102 in step S2603 of FIG. 26 will be described. FIG. 33 shows an example of a detailed display screen (document data) 3300 displayed when the document data is target data.

  As shown in FIG. 33, the detailed display screen (document data) 3300 includes a document data basic information display field 3301, a status change button 3302, an edit button 3303, a used component data list display unit 3304, a change request data list display unit 3305, A change request data input unit 3306, an update button 3307, a new creation button 3308, and a cancel button 3309 are provided.

  The document data basic information display unit 3301 is a display field for displaying the ID of the document data, the ID of the template data being used, the update number, the thumbnail image information of the document data, and the like. The status change button 3302 is a button used for giving an instruction to change the status of the document data. When an instruction to press this button is received, a status editing screen (not shown) is displayed, and a status change input can be performed. The edit button 3303 is a button used to instruct editing of new document data (update version document data, document data having a new ID derived from the document data). When the button pressing instruction is received, a data editing screen as shown in FIG. 20 is displayed, and the document data can be edited.

  The used component data list display unit 3304 is a display unit that displays a list of component data used in the document data. Each part data category (material, part), material number or part number (displayed in the ID column), update number and caution information, whether there is an updated version of the part data (with updated parts) ), Information indicating whether the part data cannot be used continuously (unusable part) and whether a change request has been made to the part data by another user (change request) is displayed.

  In the change request data list display unit 3305, change request data that has already been applied to the part data (material data, part data) used in the document data displayed in the drawing when editing other document data or the like is displayed. Is displayed. Further, link information 3305-1 for displaying a confirmation screen (not shown) for confirming the change request data is set in the request ID displayed on the display unit, and the confirmation screen is displayed. be able to. The automatic update check box 3305-2 is used to input whether or not to perform automatic update of the component data when a change according to the change request data is performed by a person in charge of editing the component data. It is a check box.

By having such control, the person in charge of editing the document data checks the content of the change request made by another user, and when the change according to the change request is made, It is possible to determine whether or not there is a need to update the component data used in the data.
In addition, it is possible to perform automatic update setting when there is a change in part data without newly making a similar change request, and it is no longer necessary to make multiple similar change requests individually. The person in charge of editing the part data does not need to confirm each of a plurality of change requests having the same contents, thereby improving the work efficiency.

  The change request data input unit 3306 is an input unit used to input a change request for the component data used in the document data. In the change request data input unit 3306, a component designation unit 3306-1, a reason input unit 3306-2, and an automatic update designation unit 3306-3 are set.

  The component designation unit 3306-1 is a designation unit for designating component data for which a change request is made. The reason input unit 3306-2 is an input unit for inputting the reason for making the change request. The reason detail input unit 3306-21 and the inconsistent data input unit 3306-22 are set to input the reason for the change request. Has been. The reason detail input unit 3306-21 is an input unit that inputs details of the reason for change. The reason detail input unit 3306-21 accepts input of reason details such as “there is a typo” and “mismatch” with other component data. The inconsistency data input unit 3306-22 accepts input of other component data that is inconsistent with the component data for which the change request is made when “inconsistency” is input to the reason detail input unit 3306-21. .

  The automatic update designation unit 3306-3 designates whether or not the component data is to be automatically updated when a change according to the change request is made on the component data for which the change request has been made. It is.

  The update button 3307 is a button used to request registration of document data with the same document number but different update numbers, for example, when the target data is document data. The same applies to parts data data and template data. The new creation button 3308 is a button used to request registration of document data having a different document number derived from the document data when the target data is document data. A cancel button 3309 is a button used to end an editing operation in accordance with a user input device operation via this screen.

  In the description of this figure, the configuration example of the detail display screen (document data) has been described. However, in the case of the detail display screen (part data), the change request data list display unit 3205 of the detail display screen (material data) 3200 and A similar change request data list display section is set. The change request data list display section set on the detail display screen (part data) is the same as the change request data list display section 3205 of the detail display screen (material data) 3200, and therefore detailed description thereof is omitted. The above is the description of the configuration of the detail display screen (document data) in FIG.

  Returning to the description of FIG. After displaying the detailed display screen corresponding to the classification of the target data in step S2603, upon receiving a pressing instruction for the inconsistent data link information included in the screen, the CPU of the client device has received a request for displaying inconsistent data. Judgment is made (YES in step S2604), and the document management server 101 is requested for inconsistent data, which is other component data inconsistent with the target data, in accordance with the link information of the inconsistent data for which the pressing instruction has been accepted. When the inconsistent data transmitted in response to the request is received from the document management server 101, the inconsistent data is displayed on the display device (step S2605). By adopting such a configuration, the person in charge of the target data can perform the process of changing the target data while referring to other component data that has caused inconsistency.

  Further, when an instruction to create new data input by accepting an instruction to press the edit button 3303 on the detail display screen 3300 is accepted (YES in step S2606), the edit screen shown in FIG. The target data is edited (step S2607).

In addition, when a request for changing the status of existing data input by receiving a pressing instruction for the status change button 3302 on the detailed display screen 3300 is received (YES in step S2608), input of status information after changing the existing data is input. Accept (step S2609). For example, here, the non-public data (public flag: 0) is made public data (public flag: 1), or the continuously usable data (continuous use flag: 1) is made continuously unavailable data (continuous use flag: 0). Change processing to be accepted. When a change request for component data is received (YES in step S2610), input of change information is received (step S2611). When an automatic update instruction is accepted (YES in step S2612), the data is set as an automatic update target (step S2613).

Thereafter, when an update instruction input by a press instruction to the update button 3307 or the new creation button 3308 is received (YES in step S2614 ), update information of the target data is created (step S2615 ). When an instruction to press the update button 3307 on the detail display screen 3300 is received, update information for registering update version data of the target data is received. When an instruction to press the new creation button 3308 is received, Update information for creating new target data derived from the target data is created. If only status change processing is performed, only the update button 3307 is valid. Then, the target data update information is transmitted (step S2616).

The CPU 201 of the document management server 101 receives the target data update information from the client device 102 (step S2628 ). If the target data update information is a status update of existing data (YES in step S2629), the status of the existing data is changed (step S2630).

  In the case of registration of new target data (update version target data, derived new target data) (YES in step S2631), the new target data is registered (step S2632).

  Then, the target data whose status has been changed by the above process and the newly created target data are set as approval required data (step S2633).

  Also, it is determined whether the change request data input unit 3306 in FIG. 33 has received a change request instruction for the component data used in the target data (step S2634: there is a change request for the component data), and the change request instruction is received. If it is determined that there is a change request, the component that has received the instruction is set as change request data (step S2635).

  Thereafter, a change request is made in the automatic update check box 3305-2 set in the change request data list display unit 3305 in FIG. 33 or the automatic update designation unit 3306-3 set in the change request data input unit 3306. When correction corresponding to the change request is added to the component data, it is determined whether or not the setting for automatically updating the component data is made (step S2636). If it is determined in the determination process in step S2636 that the automatic update setting has been made, the process proceeds to step S2637, and the component data used in the target data is set as an automatic update target (step S2638). The above is the detailed description of the processing in steps S2407, S2409, and S2411 in FIG.

  Next, with reference to FIG. 27, details of the approval processing in step S2305 of FIG. 23 will be described. Note that the processing shown in steps S2701 to S2712 in this figure is performed by the CPU of the client apparatus 102, and the processing shown in steps S2721 to S2725 is performed by the CPU 201 of the document management server 101.

  First, the CPU 201 of the client apparatus 102 transmits a data approval request including the user information of the user authenticated by the user authentication process of FIG. 23 to the document management server 101 (step S2701).

  When the CPU 201 of the document management server 101 receives a data approval request from the client device 102, the CPU 201 acquires material data, part data, template data, and document data (data to be approved) whose user is indicated by the user information. (Step S2722). Then, target data status confirmation processing is performed for all the data acquired in step S2722 (step S2723). This process has already been described with reference to FIGS. 11, 12, 13, and the like.

  Then, after the process of step S2723 is completed for all the approval target data acquired in step S2722, the process proceeds to step S2724, the list screen information of the approval target data is created, and the created list screen information is transmitted to the client apparatus 102. (Step S2725).

  When the list screen information is received from the document management server 101 (step S2702), the approval required data list screen is displayed on the display device according to the list screen information (step S2703).

  Here, with reference to FIG. 34, the approval required data list screen 3400 displayed on the display device of the client device 102 will be described. The approval required data list screen 3400 is displayed on the approval required data list display screen 2100 already described with reference to FIG. 21, and electronic document data includes unusable parts and part data with updated parts. In addition to the information, information indicating whether there is a mismatch between the component data being used is displayed as information for the approver. The above is the description of the approval required data list screen 3400 in FIG.

  Returning to the description of FIG. Thereafter, when material data designation is accepted on the approval data list screen 3400 (YES in step S2704), target data approval processing (material data) is accepted (step S2705), and part data designation is accepted (YES in step S2706). When the object data approval process (part data) is received (step S2707) and the specification of template data is accepted (YES in step S2708), the object data approval process (template data) is received (step S2709) and the specification of document data is accepted. (YES in step S2710), target data approval processing (document data) is performed (step S2711). Since the processing in steps S2705, S2707, S2709, and S2711 is substantially the same, it will be described later with reference to FIG.

  The above processing is performed until YES is determined in the end determination processing in step S2712.

  Next, the details of the target data approval process in steps S2705, S2707, S2709, and S2711 in FIG. 27 will be described with reference to FIG. Note that the processing from step S2801 to step S2810 is performed by the CPU of the client apparatus 102, and the processing from step S2821 to step S2833 is performed by the CPU 201 of the document management server 101.

  First, when the CPU 201 of the client apparatus 102 accepts designation of any of the approval target data on the approval target data list screen 3400 in FIG. 34, the CPU 201 transmits a detailed data request for the approval target data to the document management server 101 (step S100). S2801).

  When the CPU 201 of the document management server 101 acquires a detailed data request from the client device 102 (step S2821), the CPU 201 acquires detailed data of the target data (step S2822). Thereafter, it is determined whether or not there is inconsistent data in the target data (step S2823). If there is inconsistent data (YES in step S2823), the inconsistent data is acquired (step S2824).

  Then, using the information acquired in step S2822 and step S2824, detailed screen display information for displaying the detailed screen of the target data is created (step S2825) and transmitted to the client device 102 (step S2826).

  When receiving the detailed screen display information (step S2802), the CPU 201 of the client apparatus 102 displays the detailed screen of the approval target data according to the received information.

  Here, with reference to FIG. 35, a detailed screen of the approval target data displayed on the display device of the client device 102 will be described. FIG. 35 shows an example of a document data approval screen.

  As shown in FIG. 35, the approval target data details screen 3500 includes a management information display section 3501, an approval target data detail display section 3502, an unusable data display instruction button 3503, a part data display instruction button 3504 with update data, A matching data display instruction button 3505, a display page switching instruction button 3506, an approval button 3507, a denial button 3508, and the like are set.

  The management information display unit 3501 is a display unit that displays information such as the creator of the approval target data and the creation department. The approval target data detail display unit 3502 is a display unit that displays an image of the approval target data.

  An unusable data display instruction button 3503 is a button for inputting an instruction to display unusable data included in the approval target data. When this button is pressed, the unusable data included in the approval target data is changed to another button. Display control is performed so as to be distinguishable from the component data. A part data display instruction button 3504 with update data is a button for inputting an instruction to display updated part data included in the approval target data. When this button is pressed, an update included in the approval target data is displayed. Display control is performed so that existing part data can be distinguished from other part data. The inconsistent data display instruction button 3505 is a button for inputting an instruction to display inconsistent data included in the approval target data. When this button is pressed, the inconsistent data included in the approval target data is displayed. Display control is performed so as to be distinguishable from the component data.

  A page switching button 3506 ("Previous page" button and "Next page" button in the figure) is a button for instructing switching of the display page when the approval target data is data of a plurality of pages.

  An approval button 3507 is a button used to input an approval instruction for the approval target data to the document management server 101, and a denial button 3508 is used to input a denial instruction for the approval target data to the document management server. The above is the description of the configuration of the details screen 3500 of the approval target data in FIG.

  Returning to the description of FIG. When the client apparatus 102 receives a display request for inconsistent data input by pressing the inconsistent data display instruction button 3505 in the approval target data detail screen 3500 (YES in step S2803), the approval target data Inconsistent data is displayed (step S2804). As a result, the person in charge of approval can easily know whether or not there is inconsistent data in the data to be approved, which can be used for the determination of approval or rejection.

  When a denial input is received when a denial button on the details screen 3500 for approval target data is pressed (YES in step S2805), the process proceeds to step S2806, and denial acceptance information is transmitted to the document management server 101. To do.

  When the CPU 201 of the document management server 101 receives the denial acceptance information from the client device 102 (step S2827), the CPU 201 changes the status to send back indicating that the status is denied (step S2828), and returns the processing result to the client device 102 (step S2828). Step S2833).

  On the other hand, when accepting an approval input by pressing an approval button in the details screen 3500 of the approval target data displayed on the display device of the client device 102 (YES in step S2807), the CPU 201 of the client device 102 accepts the approval. Information is transmitted to the document management server 101 (step S2808).

  When receiving the approval acceptance information from the client device 102 (step S2829), the CPU 201 of the document management server 101 changes the status to approved (step S2830). Then, it is determined whether the approved data is document data (step S2831). If it is determined that the approved data is not document data (NO: that is, component data), the document data using the component data, Performs automatic update processing of component data. Details of this processing will be described later with reference to FIG.

  If the CPU 201 of the document management server 101 determines NO in step S2831, or after the process of step S2832, the process proceeds to step S2833 and transmits the processing result to the client apparatus 102. Upon receiving the processing result from the document management server 101 (step S2809), the client device 102 displays the processing result on the display device (step S2810). The above is the detailed description of the target data approval process in steps S2705, S2707, S2709, and S2711 of FIG.

  Here, with reference to FIG. 29, the details of the automatic update processing in step S2832 of FIG. 28 will be described. This process is a process performed by the CPU 201 of the document management server 101.

  The CPU 201 performs an automatic component update process (part data) on all the part data registered in the external memory 211 (step S2901). Thereafter, the part data automatic update process (document data) is performed on all the document data (step S2902). Details of steps S2901 and S2902 will be described with reference to FIG. The above is the description of the automatic update process in step S2832 of FIG.

  Next, details of the component data automatic update processing in steps S2901 and S2902 in FIG. 29 will be described with reference to FIG. This process is a process performed by the CPU 201 of the document management server 101.

  First, the CPU 201 acquires target data stored in the external memory 211 (step S3001). In the case of the part data automatic update process (part data) in step S2901 in FIG. 29, the part data is the target data here, and in the case of the part data automatic update process (document data) in step S2902, the document data is the target data here. .

  Then, it is determined whether there is component data for which automatic update is set in the target data (step S3002). If it is determined that there is component data for which automatic update is set (YES in step S3002), an approval process has already been performed, and whether the component data for which update has been approved is a target of automatic update. Determination is made (step S3003). If YES is determined in the step S3003, the already approved component data is updated (step S3004).

  When a plurality of change requests are made for the updated component data, a plurality of update data may be created corresponding to each change request. In this case, when the update of the component data corresponds to the change request when the automatic update is performed, the CPU 201 determines YES in the determination process of step S3003.

  Then, after the component data update process in step S3004, it is determined whether there is any other component data that is subject to automatic update in the target data acquired in step S3001 (step S3005). If the CPU 201 determines that there is no other part data subject to automatic update (NO in step S3005), the process proceeds to step S3006 to determine whether unusable data is not used for the target data. To do.

  If NO in step S3006, the CPU 201 determines that the process proceeds to step S3007, and the target data acquired in step S3001 is set as approval required data.

  If NO is determined in steps S3002 and S3003, or YES is determined in steps S3005 and S3006, the process is terminated without using the target data acquired in step S3001 as approval-required data.

  In the second embodiment of the present invention, by adopting the configuration as described above, when the part data is changed in response to the part data change request, the part data used in the document data is changed. Updates can be made automatically. In addition, even when a plurality of different change requests are made for one component data, it is input whether the component data has been changed to respond to which change request, and a change corresponding to the change request is made. If the component data is automatically updated when it is performed, the component data used in the set document data can be updated. Thereby, there is an effect that the burden on the person in charge of creating the document data can be reduced.

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

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

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

  In that case, as long as it has the function of a program, it may be in the form of object code, a program executed by an interpreter, script data supplied to the OS, or 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-1 and 102-2 Client device 103 Network 201 CPU
202 RAM
203 ROM
204 System Bus 205 Input Controller 206 Video Controller 207 Memory Controller 208 Communication I / F (Interface) Controller 209 Keyboard 210 Display Device 211 External Memory

Claims (10)

An information processing system that supports creation of document data created by laying out component data,
Management means for managing component data laid out in the document data;
For the component data managed by the management means, information indicating a change request for the component data, including a notification that the component data is inconsistent with other component data, is obtained using the component data. Change request accepting means for accepting from a document creation user who creates the document data;
Storage means for storing information indicating a change request received by the change request receiving means;
Display request receiving means for receiving a display request for the component data;
When information indicating a change request for the component data of accepting the display request by the display request receiving means is stored in the storage means, the component data and the other component data which is the component data inconsistent An information processing system comprising: display means for displaying a screen that can identify A data display request accepting means for accepting a display request for the other component data via a screen displayed by the display means;
The information processing system according to claim 1, wherein the display unit displays the other component data on a screen when the display request for the other component data is received by the data display request reception unit. An information processing system that supports creation of document data created by laying out component data,
Management means for managing component data laid out in the document data;
Change request accepting means for accepting information indicating a change request for the part data managed by the managing means from a document creation user who creates the document data using the part data;
Storage means for storing information indicating a change request received by the change request receiving means;
Display request receiving means for receiving a display request for the component data;
When information indicating a change request for the component data for which the display request has been received by the display request receiving unit is stored in the storage unit, the screen can identify the component data, and the change request for the component data is received. Display means for displaying a screen including information to be displayed;
To the component data displayed by the display unit, when receiving an editing instruction from the component creation user, the document data to be laid to the document creation user who made the changes requested by the change request accepting unit creates An information processing system comprising: update means for updating the component data. By the change request accepting unit, information indicating a change request for the same component data, if received from a plurality of document creation user creating the document data by using the component data, information indicating the plurality of change requests Further comprising a designation receiving means for receiving designation of information indicating which change request has been edited,
4. The information processing system according to claim 3, wherein the updating unit updates the component data laid out in the document data created by the document creation user who has made the change request designated by the designation receiving unit. . The change request accepting unit, the part data comprises a notification that another component data inconsistent receives information indicating a change request for the component data, the change request said storage means stores If, the display means displays said part data which has received the display request by the display request receiving unit, capable of specifying screen and the component data and the additional component data notified to be inconsistent The information processing system according to claim 3 or 4, characterized by the above. A data display request accepting means for accepting a display request for the other component data via a screen displayed by the display means;
The information processing system according to claim 5, wherein the display unit displays a screen including the other component data when the display request of the other component data is received by the data display request reception unit. A control method of an information processing system comprising management means for managing component data laid out in document data, and supporting creation of document data created by laying out the component data,
The change request receiving unit of the information processing system issues a change request for the component data including a notification that the component data is inconsistent with other component data for the component data managed by the management unit. A change request accepting step for accepting information to be received from a document creation user who creates the document data using the component data;
A storage step of storing information indicating a change request received by the change request receiving step by the storage means of the information processing system;
A display request accepting step for accepting a display request for the component data;
When information indicating a change request for the component data for which the display unit of the information processing system has received the display request in the display request reception step is stored in the storage step, the component data, the component data, And a display step for displaying a screen capable of identifying the other component data determined to be inconsistent. A program that includes a management unit that manages component data laid out in document data, and that can be executed by an information processing system that supports creation of document data created by laying out the component data,
The information processing system;
For the component data managed by the management means, information indicating a change request for the component data, including a notification that the component data is inconsistent with other component data, is obtained using the component data. Change request accepting means for accepting from a document creation user who creates the document data;
Storage means for storing information indicating a change request received by the change request receiving means;
Display request receiving means for receiving a display request for the component data;
When information indicating a change request for the component data of accepting the display request by the display request receiving means is stored in the storage means, the component data and the other component data which is the component data inconsistent That functions as a display means for displaying a screen that can be specified. A control method of an information processing system comprising management means for managing component data laid out in document data, and supporting creation of document data created by laying out the component data,
The change request accepting means of the information processing system, information indicating a change request for the component data managed by said management means, the component change request accepting step of data using the accepted from document creation user creating the document data When,
A storage step of storing information indicating a change request received by the change request receiving step by the storage means of the information processing system;
A display request accepting step for accepting a display request for the component data;
When the information indicating a change request for the component data for which the display request has been received by the display request receiving step is stored in the storage step, the display unit of the information processing system is a screen on which the component data can be specified. A display step for displaying a screen including information indicating a change request for the component data;
Updating means of the information processing system, with respect to the component data displayed by said display step, when receiving an editing instruction from the component creation user, the document creation user who made the changes required by the change request accepting step An update process for updating the component data laid out in the document data created by the information processing system. A program that includes a management unit that manages component data laid out in document data, and that can be executed by an information processing system that supports creation of document data created by laying out the component data,
The information processing system;
A change request for the component data managed by said management means, and change request accepting unit that accepts from the document creation user creating the document data by using the component data,
Storage means for storing the change request received by the change request receiving means;
Display request receiving means for receiving a display request for the component data;
When a change request for the component data for which the display request is accepted by the display request accepting unit is stored in the storage unit, a screen that can identify the component data and includes a change request for the component data Display means for displaying;
To the component data displayed by the display unit, when receiving an editing instruction from the component creation user, the document data to be laid to the document creation user who made the changes requested by the change request accepting unit creates A program that functions as an update means for updating the relevant component data.

Images