JP5594409B2 - Information processing apparatus, information processing method, and computer program - Google Patents

Description

  The present invention relates to a technology for supporting an approval operation for a document created using a plurality of materials, and in particular, an approval support based on whether or not the component data used for the creation of electronic document data can be used for approval. It relates to the technology to be performed.

  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 so that the matters stipulated by laws and regulations are described.

  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

  Data widely used in the company, such as proposals to customers, is created by the creator and then released with the approval of the approver. In the case of performing such approval, a workflow process is performed in which the creator creates an electronic document data and then the superior of the creator approves the electronic document data.

  Generally, in an electronic document data approval workflow, even if a change is made to a part of the created electronic document data, it is common to proceed with the approval process without notifying such a situation. In some cases, electronic document data including parts that have been changed and become unusable are erroneously approved.

  In view of the above-described problems, the present invention suitably prevents erroneous approval processing from being performed when an electronic document data created by laying out a part includes an unapproved part. For the purpose.

The present invention provides a information processing apparatus capable of communicating with a cluster Ian preparative terminal, first information that associates a designation accepting means for accepting a designation of document data, and the availability information of the component data and the component data a storage means for storing the second information for managing component data that is laid out in the document data, the document data has been accepted designated by the designation receiving unit, usability information Ru unavailable der parts The component data determination unit that determines whether data is laid out by using the first information and the second information, and the component data determination unit lays out component data for which the availability information is unusable. when it is determined that there, a reception screen for accepting an input of the approval or denial with respect to the document data received designation by the designation receiving unit, the designation A screen generating unit that component data with means that are not used in the document data has been accepted specification that has been laid to produce so as to be identified, the reception screen generated by the screen generating means, And a notification means for notifying the client terminal .

Further, the present invention is an information processing method performed by communicable information processing apparatus and the client terminal, associating a designation accepting step for accepting a designation of document data, and the availability information of the component data and the component data a first information, a storage step of storing the second information for managing component data that is laid out in the document data, the document data has been accepted designated by the designation accepting step, availability information and determining component data determination step of determining unavailable der Ru component data is laid out by using the first information and the second information, by the component data determination step, usability information is unavailable If the component data is determined to have been laid, the input of the approval or denial with respect to the document data received designation by the designation accepting step The reception screen that the Ru reception, a screen generation step of component data that that have been laid to produce so as to be identified is unavailable in the document data has been accepted designated by the designation accepting step, the screen generation A notification step of notifying the client terminal of the reception screen generated in the step .

  According to the present invention, in the electronic document data approval process, it is determined whether or not the electronic document data subject to the approval process includes a prohibited part. It is possible to suitably prevent erroneous approval for the electronic document data included.

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 raw material data update process of FIG.6 S603. It is a flowchart which shows the detail of the part data update process of FIG.6 S605. It is a flowchart which shows the detail of the template data update process of FIG.6 S607. It is a flowchart which shows the detail of the electronic document data update process of step S609 of FIG. It is a flowchart which shows the detail of the template and components update advanced king confirmation process of step S1002 of FIG. It is a flowchart which shows the detail of the update condition confirmation process of the template data of step S1101 of FIG. It is a flowchart which shows the detail of the in-page component status confirmation process of FIG.11 S1102. It is a flowchart which shows the detail of the part status confirmation process in parts of step S1305 of FIG. 12 is a flowchart showing details of an in-page component update confirmation process in step S1103 of FIG. 11. FIG. 16 is a flowchart showing details of an in-parts component update status confirmation process in step S1508 of FIG. It is a flowchart which shows the detail of the electronic document data approval process of step S611 of FIG. 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 an electronic document 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.

  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. An input controller (input C) 205 controls input from a pointing device such as a keyboard 209 or a mouse (not shown). A video controller (VC) 206 controls display on a display device such as the display device 210. The display device is, for example, a CRT display or a liquid crystal display. These are used by the administrator as needed. The present invention is not directly related.

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

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

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

  A program used to execute various processes of the 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 creation support system of the present application will be described with reference to FIG. FIG. 3 is a schematic diagram showing the structure of electronic document data created by the document creation support system of the present application.

  In the document creation support system of the present application, part data composed of part data such as material data and a plurality of material data is arranged at a desired position as part data constituting electronic document data in a template selected by the user. 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. The material data can be arranged in the template data 300, or the part data 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, material data, and part data 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 that is stored and managed in the external memory 211 by 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 created by the document management server 101 and managed by the external memory 211 in accordance with a user operation. The document number 401-1 and the template number 401- 2 and the template update number 401-3.

  The document number 401-1 is identification information for uniquely identifying electronic document data. The template number 401-2 stores the template number (corresponding to 403-1 described later) used for creating the electronic document data. 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 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 a use addition 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. Flag information (for example, 1: public 0: non-public) indicating whether or not the template data managed by 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 template data managed in the record can be used continuously.

  The part data information table 404 is a data table for managing information on part data that can be used for creating an electronic document in the document management system. 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, part 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 the update data is created.

  An example of document management processing performed by the document management server 101 will be described with reference to FIG. 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 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 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 acquired (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 treated as unusable material data when creating electronic document data or creating part 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 handled as material data that cannot be used. That is, the existing electronic document data and part data that use the existing version of the 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. Will be 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. 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, the part number 404-2 input via the screen is acquired (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, based on the information acquired from the client apparatus 102 in steps S804 and S806, the part data information table 404 is updated, and the part data in-part 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 template number input via the screen is acquired (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 obtained from the electronic document data information table 401 (step S1001). Thereafter, a template / part update status confirmation process is performed for all the electronic document data acquired in step S601 (step S1002). Details of this template / part update status confirmation processing will be described with reference to FIG.

  FIG. 11 describes details of the template / part update status confirmation processing in step S1002 of FIG. In this process, whether the template data, part data, and material data used in the electronic document data to be checked is continuously unavailable, or whether a new version of the data is registered (updated). Check.

  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, it is confirmed 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. 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 S13101). 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 the parts can be continuously used, the part status confirmation process in the parts is performed to check whether other parts data and material data used in the part data are 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 S1303 or step S1308 that the component data is unusable, the process proceeds to step S1309, and the component data is stored in the RAM 202 as the continuously unusable 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. . 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 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 the part data that has not been updated even though the part data used in the process has been 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 this 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, details of the electronic document data approval processing 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.

CPU 201, when judging that the approval process request of the electronic document data (YES in step S Step S6 10 in FIG. 6), CPU 201, the user specified in the login processing (Step S601 in FIG. 6) of a person 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 received electronic document data approval acceptance screen is generated and transmitted to the client apparatus 102 (step S170 5 ).

FIG. 22 is a schematic diagram showing an example of an electronic document data approval acceptance screen. As shown in FIG. 22, the electronic document data approval input has a display field for detailed information of electronic document data to be approved, a control for inputting approval (“Approval” in the figure), and approval. A control ("denied" in the figure) is provided. A warning message is displayed when the electronic document data for which the continuation unusable data (template, part, material) is to be approved is used (220 0 ). In addition, if this approval is to approve the disclosure of the electronic document data, the electronic document data to be approved can be used as a control for inputting approval (template, part, material) ) Is used, the control for inputting approval is grayed out (invalidated) so that the input of approval cannot be performed (220 1 ). 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 S170 6 ), 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.

  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.

  In the present invention, a software program (in the embodiment, a program corresponding to the flowcharts shown in FIGS. 6 to 17) for realizing the functions of the above-described embodiments is supplied directly or remotely to a system or apparatus. Including. The present invention also includes a case where the system or the computer of the apparatus is achieved by reading and executing the supplied program code.

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

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

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

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

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

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

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

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

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

101 Document management server 102-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 (11)

A information processing apparatus capable of communicating with a cluster Ian DOO terminal,
A specification accepting means for accepting specification of document data;
A first information associating the availability information of the component data and the component data, storage means for storing the second information for managing component data that is laid out in the document data,
Wherein the designation accepting means the document data received designation in determines part data determined using the first information and the second information whether the component data availability information Ru Unavailable der is laid Means ,
By the part data determining means, when the component data availability information is unavailable is determined to have been laid, accepting an input of the approval or denial with respect to the document data received designation by said designation receiving means the reception screen, and the screen generating unit component data that that have been laid to produce so as to be identified is unavailable in the document data has been accepted designated by the specification receiving means,
Notification means for notifying the client terminal of the reception screen generated by the screen generation means;
The information processing apparatus comprising: a.   An approval receiving means for receiving from the client terminal an input of approval or denial for the document data whose specification has been received by the specification receiving means;
  The approval receiving unit does not receive an input of approval for the document data from the client terminal when the component data determining unit determines that the component data whose use availability information is unusable is laid out. The information processing apparatus according to claim 1. The reception screen is provided with a control for receiving an input of approval or denial for the document data that has been designated by the designation receiving means .
The approval-receiving means is more able to accept input from the control, according to claim 2 wherein the approval of the document data has been accepted designated by designation accepting means or characterized by receiving an input of denial Information processing device. The screen generating unit, when the more component data decision means, component data availability information is unavailable is determined to be laid, control for accepting input of the authorization is disabled the The information processing apparatus according to claim 3 , wherein a reception screen is generated. The part data includes sub-part data,
5. The apparatus according to claim 1, further comprising an updating unit configured to update the availability information of the part data to unavailable when the parts data includes the sub part data whose availability information is unavailable. The information processing apparatus according to any one of the above.   According to a user operation instruction, an approval process start request receiving unit that receives an approval process start request for document data from the client terminal;
  And a specifying means for specifying the document data for which the user is in charge of the approval process,
  The information processing apparatus according to claim 5, wherein the updating unit updates the document data specified by the specifying unit. Further to comprising a list screen generating means for generating a display screen including list information of document data that requires approval processing,
The designation accepting means, the information processing apparatus according to any one of claims 1 to 6, characterized in that accepts a designation of document data via the display screen. Wherein the display screen, information according to claim 7, wherein the approval processing usability information to the document data requiring Unavailable der Ru component data includes information indicating that it is laid Processing equipment.   The storage unit also stores the component data,
  The list screen generation means, when new part data replacing the part data stored in the storage means is added, so that the new part data can be identified, The information processing apparatus according to claim 7, wherein a display screen is generated. An information processing method performed by a client terminal capable of communicating with information processing device,
A designated acceptance process for accepting designation of document data;
A first information associating the availability information of the component data and the part data, a storage step of storing the second information for managing component data that is laid out in the document data,
Wherein the designation accepting the document data received designation in step determines part data determined using the first information and the second information whether the component data availability information Ru Unavailable der is laid Process ,
By the component data determination step, when the component data availability information is unavailable is determined to have been laid, accepting an input of the approval or denial with respect to the document data received designation by the designation accepting step the reception screen, a screen generation step of component data that that have been laid to produce so as to be identified is unavailable in the document data has been accepted designated by the designation accepting step,
A notification step of notifying the client terminal of the reception screen generated in the screen generation step;
An information processing method characterized in that it comprises a. Communicable information processing apparatus and the client terminal,
A specification accepting means for accepting specification of document data;
A first information associating the availability information of the component data and the component data, storage means for storing the second information for managing component data that is laid out in the document data,
Wherein the designation accepting means the document data received designation in determines part data determined using the first information and the second information whether the component data availability information Ru Unavailable der is laid Means ,
By the part data determining means, when the component data availability information is unavailable is determined to have been laid, accepting an input of the approval or denial with respect to the document data received designation by said designation receiving means the reception screen, and the screen generating unit component data that that have been laid to produce so as to be identified is unavailable in the document data received designation by said designation receiving means,
The screen reception screen generated by the generating means, the computer program characterized by Ru to function as a notifying means for notifying the client terminal.

Images