JP2006099330A - Business processing system, business processing method and computer program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a business processing system for ensuring that an electronic document has been authenticated by a legal authenticator. <P>SOLUTION: This business processing system is configured to impress a seal on an electronic document showing a document having a first region whose writing is permitted to a user who operates a client 3 and a second region whose writing is not permitted. The business processing system is provided with a work flow management system 20 for assigning a user who impresses a seal to the electronic document based on a work flow, and for generating work flow data including data for specifying the user and progress data showing the progress of the work flow by adding identification data for identifying the work flow data and an electronic seal sub-system 21 for confirming the progress circumstance of the work flow from the work flow data, and for specifying the user assigned according to the confirmed progress circumstance, and for embedding the seal data of the user in the second region and for embedding the progress data and the identification data in the second region so that those data cannot be visualized by the user. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a business processing system for electronically processing various documents such as approval documents and various notifications in a company and processing them efficiently, and in particular, a business processing system for stamping each electronic document with an electronic seal stamp. About.

  In a workflow that stipulates paperwork in a company, when a document creator requests authentication from his / her manager, he / she authenticates the manager after describing and stamping the required information on the form prescribed by the company. It is common to take a procedure of having a seal stamp to prove this. Such a procedure is realized by a business processing system such as a so-called workflow system in accordance with the digitization of business.

  In each authentication stage in the workflow system, a so-called electronic seal stamp system may be used to perform the seal electronically. Many electronic seal stamp systems, for example, disclosed in Japanese Patent Application Laid-Open No. 2003-6361 (title of the invention: recording medium on which an electronic seal stamp system and an electronic seal stamp program are recorded) include an imprint as a seal stamp on an electronic document as a document. Electronic marking is realized by electronically pasting image data.

  When the workflow system and the electronic seal stamp system are linked, it is necessary to install the client side program of the workflow system and the electronic seal stamp system on all clients, for example, in a client-server type system. Therefore, management is complicated and the cost tends to be high. In addition, since the electronic seal stamp system is installed in all clients, there is a risk that the image data of the seal image can be easily duplicated or can be easily stamped by anyone.

  A client on which a conventional electronic seal stamp system is installed is usually realized by a general-purpose personal computer or the like. With a general-purpose personal computer, when an electronic document can be opened or displayed, the electronic document can be saved with a different name, or the image can be copied by using screen capture software while it is displayed on the screen. Can be easily replicated.

  As described above, stamping using an electronic seal stamp is basically the same processing as “pasting image data on an electronic document” with word processing software or the like. When the image data of the seal is copied, it can be easily improperly stamped by pasting it on the electronic document. Therefore, in an environment where the image data of the seal imprint can be copied, authentication by a valid certifier cannot be guaranteed.

  As described above, if the image data of the seal imprint is easily copied or anyone can make a seal with an electronic seal, authentication by a legitimate authenticator cannot be guaranteed. Furthermore, as long as the image data of the seal is present, the electronic seal stamp can be freely attached or deleted on the electronic document, and the seal becomes meaningless at all.

  In view of the above problems, an object of the present invention is to provide a paper processing system, a paper processing method, and a computer program that guarantee that an electronic document has been authenticated by a valid authenticator.

  The business processing system of the present invention that solves the problems as described above includes a communication unit that enables data transmission / reception with one or more clients, and allows a user who operates the client to write data. This is a business processing system for marking an electronic document representing a document provided with one area and a second area not permitted based on a predetermined workflow. The business processing system assigns a user who performs the seal to the electronic document in accordance with the progress of processing based on the workflow, and data for specifying the assigned user and progress data representing the progress of the workflow Workflow management means for generating workflow data including identification data for identifying the workflow data, and confirming the progress of the workflow with the workflow data and assigning according to the confirmed progress The user is identified, and the imprinting data of the identified user is embedded in the second area of the electronic document to perform the sealing, and the progress data and the identification data are stored in the second area of the electronic document, Electronic seal stamp means embedded invisible to the user. The workflow management unit is configured to store the electronic document in which the seal stamp data, the progress data, and the identification data have been embedded in a predetermined storage unit in association with the corresponding workflow data.

In such a business processing system, the user is unable to directly stamp the electronic document because the stamping is performed in an area where writing by the user is not permitted. Due to such a configuration, the user cannot perform unauthorized marking.
In addition, since progress data representing the progress status of the workflow is embedded in the electronic document, the version of the electronic document can be managed. For this reason, even if the information is improperly imprinted by some method, since the progress data does not indicate that imprinting has been performed, the fraud can be recognized.

The seal impression data becomes an impression when displayed on the display of the client. For example, the seal stamp data may include a character string for expressing an image. In this case, the storage unit stores the character string for each user, and the electronic seal stamp unit acquires the character string of the user from the storage unit, and generates the imprint data of the user from the character string. Configured.
In addition, the storage means may be configured to store the seal impression data for each user. In this case, the electronic seal stamp means is configured to acquire seal data of the user who performs the seal from the storage means.

In the second area, an area that can be stamped may be determined for each process based on the workflow. In this case, the workflow management unit is configured to assign a user who performs the seal for each process based on the workflow, and the electronic seal unit performs a seal in the process for each process based on the workflow. The imprint data of the user assigned in this way is configured to be embedded in a predetermined area that can be imprinted. With such a configuration, it becomes possible to seal different areas of the electronic document for each applicant and authenticator.
For example, the process based on the workflow includes at least a first process for marking the first user who created the electronic document and a second process for marking the second user who authenticates the electronic document. In addition, at least the first marking area where the first user is marked and the second marking area where the second user is marked are determined in the area where the electronic document can be marked. The workflow management unit is configured to assign the second user to a user who performs the second process, and the electronic seal unit is configured to imprint the first user in the first seal area during the first process. In addition to embedding data, the imprint data of the second user is embedded in the second seal area during the second processing. The first user corresponds to the applicant and the second user corresponds to the authenticator.

  In such a paper processing means, for example, the workflow management means is configured to update the progress data each time processing based on the workflow is executed one by one, and the electronic seal stamp means It is preferable that the progress data written in the electronic document is updated each time the process is performed, so that the progress data is always matched with the progress of actual processing.

  According to the business processing method of the present invention, communication data that enables transmission / reception of data to / from one or more clients, workflow data indicating an order of executing the processes and a user who executes the processes based on a predetermined workflow. This is a method executed by a business processing system having a workflow management means for generating and an electronic seal stamp means for performing electronic seal. In this method, when the workflow management means receives from the client an electronic document representing a document provided with a first area where writing by a user operating the client is permitted and a second area where writing is not permitted, Identification data for identifying the workflow data is added to the workflow data including the data for identifying the allocated user and the progress data indicating the progress of the workflow, by assigning the user who performs the seal to the document. And the electronic seal stamp means confirms the progress status of the workflow based on the workflow data, identifies the assigned user according to the confirmed progress status, and stores the identified user's seal impression data in the electronic data The seal is performed by embedding in the second area of the document, and the previous The step of embedding progress data and the identification data in the second area of the electronic document invisible to the user, and the workflow management means has finished embedding the imprint data, the progress data, and the identification data Storing the electronic document in association with the corresponding workflow data in a predetermined storage means.

  According to the computer program of the present invention, a computer having a communication unit that enables transmission and reception of data to and from one or more clients is performed by a user who operates the client in accordance with the progress of processing based on a predetermined workflow. The assignment of a user to be stamped on an electronic document representing a document provided with a first area that permits writing and a second area that does not allow writing, and data indicating the assigned user and the progress of the workflow Workflow management means for generating workflow data including progress data with identification data for identifying the workflow data, confirming the progress of the workflow by the workflow data, and according to the confirmed progress The assigned user is identified, and the imprint data of the identified user An electronic seal is provided that embeds the progress data and the identification data in the second area of the electronic document in an invisible manner to the user while embedding in the second area of the electronic document. A computer program for forming and storing the electronic document in which the imprint data, the progress data, and the identification data have been embedded in a predetermined storage unit in association with the corresponding workflow data. It is.

  Hereinafter, an embodiment of a workflow system using the business processing system of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating a configuration of an entire system 1 including a server 2 in which a workflow system according to the present embodiment is formed.

This system 1 is configured as a so-called client-server type, and a plurality of clients 3 are connected to a server 2 via a network 4. The server 2 and the client 3 are each configured to have a communication device so that data can be transmitted and received between each other via the network 4.
The server 2 includes an input device such as a keyboard and an output device such as a display, and is configured by a general-purpose server device having a function as a Web server. In the server 2, a workflow system is formed. The client 3 includes an input device such as a keyboard and an output device such as a display, and is configured by a general-purpose personal computer equipped with a Web browser.

  FIG. 2 shows a detailed configuration of the workflow system formed in the server 2. This workflow system electronically stamps an electronic document based on a predetermined workflow. For this purpose, the workflow system formed in the server 2 includes a workflow management system 20, an electronic seal stamp subsystem 21, an authentication ID confirmation servlet 22, and a database 23. Each component is formed, for example, when the CPU of the server 2 executes the computer program of the present invention.

  The workflow management system 20 is a system for managing processing executed based on a predetermined workflow. The workflow management system 20 is formed as a Web application using an application API (Application Program Interface), and includes an engine 210 connected to the database 23, an application API 211, an application 212, a management API 213, a management tool 214, and a flow definition tool. 215 and a batch tool 216.

  The engine 210 is a core module of the workflow management system 20 and performs various processes that can be executed by the workflow management system 20, status management, and the like. The engine 210 is connected to the database 23, and performs database management such as input / output, update, and deletion of data to / from the database 23.

Workflow data, which will be described later, is associated with an electronic document processed by the workflow system. The engine 210 attaches an authentication ID (hereinafter referred to as “authentication ID”) to the workflow data. The authentication ID is a unique ID that can uniquely identify workflow data held by the workflow system.
The authentication ID is generated by, for example, a hash key generated from an algorithm that does not generate the same key consisting of 60 digits. The authentication ID is composed of a business ID for identifying workflow data and a work ID representing the progress of the workflow. The work ID is a kind of progress data indicating the progress status of the process. The work ID is generated by combining, for example, data (for example, ID) for identifying the certifier and the date and time of the work. By referring to the authentication ID, the workflow and the electronic document can be specified, and the progress of the workflow can be known.

  The application API 211 is an API for using the engine 210 by the application 212. An application API 211 is used to develop an application executed by the workflow management system 20.

  The application 212 is an application program executed by the workflow system. It is used when processing such as login, application, and approval is executed in response to an input from the client 3.

  The management API 213 is an API for creating a management screen for managing the workflow management system 20. The management API 213 can be used to customize the management screen or create a new management screen. The management screen is displayed on the display of the server 2, and the administrator of the server 2 can manage the server 2 by inputting commands and data through the management screen and the input device.

  The management tool 214 cooperates with the engine 210 to monitor / manage the workflow system in addition to registering / updating / deleting various data (templates) recorded in the database 23.

The flow definition tool 215 performs workflow description, route setting, and the like. The flow definition tool 215 assigns, for example, certifiers (approver, reviewer, finalizer) from new application to approval, review, and settlement based on the workflow. The flow definition tool 215 is a process for processing an application document based on a workflow when a new electronic document (hereinafter simply referred to as “application document”) is created and sent from the client 3 to the server 2. And the certifier is determined, and workflow data representing the determined processing procedure and certifier is created. The created workflow data is given an authentication ID and is stored in the database 23 in association with the application document. One workflow data is created for one application document.
The assignment of the certifier may be fixed in advance, and for example, the boss (section manager, general manager) of the applicant who created the application documents may be assigned according to the order, but it is not necessarily the boss of the applicant. For example, the certifier dynamically assigned may be changed depending on the type of application document.

  Workflow data is one transaction, and when there is work such as stamping or authentication, an instance is generated and recorded in the transaction. Specifically, after the marking or authentication, the engine 10 writes the certifier who performed the work and the date and time of the work in the workflow data. For this reason, the workflow history is known from the workflow data.

  The workflow data is created based on, for example, a workflow as shown in FIG. In this workflow, first, when an application document is created by the applicant, the electronic seal stamp subsystem 21 stamps the applicant. Next, the approver, who is the boss of the applicant, approves the application document, and the electronic seal stamp subsystem 21 seals the approver. Next, the reviewer who is the supervisor of the applicant and the approver performs the review of the application document, and the seal of the reviewer is performed by the electronic seal stamp subsystem 21. Next, the approver who is the supervisor of the applicant, the approver, and the reviewer performs approval of the application document, and the electronic seal stamp subsystem 21 seals the approver. The flow definition tool 215 assigns approvers, reviewers, and finalists based on, for example, the affiliation (section, section) of the applicant.

  The batch tool 216 cooperates with the engine 210 to execute processes that need to be performed collectively, such as registration and update of various data recorded in the database 23 and transmission of mail.

The electronic seal stamp subsystem 21 uses the application 212 of the workflow management system 20 to perform a seal with an electronic seal stamp on a predetermined area of the application document, and an authentication ID in an invisible state in other areas of the application document. It is designed to be embedded.
The seal used for the seal is automatically generated by the electronic seal stamp subsystem 21 by acquiring from the database 23 a seal stamp character string for the person who performs the seal (applicant, reviewer, approver, etc.). Yes.

  The electronic seal stamp subsystem 21 has a program for creating seal stamp data from a seal stamp character string (hereinafter referred to as “seal stamp program”). When performing the seal, the electronic seal stamp subsystem 21 uses the seal character string of the person who performs the seal to generate seal data by the seal program. Sealing is performed by embedding the seal data in the application document. The imprint data is data displayed as an imprint when the application document is displayed on the display of the client 3.

  It should be noted that the image file of the seals of all employees may be stored in the workflow system and directly embedded in the application document. However, in this case, the larger the company, the larger the number of image files, and the more difficult it is to maintain. In this embodiment, since the imprint data is generated by executing the imprint program every time it is stamped, it is not necessary to store a large amount of image files, and maintenance is facilitated.

  The imprinting program generates the imprint data using the imprinted character string, but the time and random number may be taken into account here. For example, an image that becomes noise is generated from the imprint program at a time, a random number, or the like so that characters can be recognized as the imprint, and is superimposed on the imprint. An image obtained by overlaying an imprint and an image that becomes noise is used as an imprint image. The image generated in this way is a different image each time because an image that becomes noise is generated from time, random numbers, or the like. For this reason, the security of the seal is improved.

  The authentication ID confirmation servlet 22 confirms the progress of the application document according to an instruction from the client 3. The workflow data associated with the application document indicates the progress of the workflow. The authentication ID confirmation servlet 22 confirms the workflow data and returns the progress status of the application document to the client 3 that has been instructed.

  The database 23 is a recording device that records various data used in the workflow system, and includes a large-capacity recording device such as a hard disk drive. The database 23 is managed by the workflow management system 20 such as data input / output, reference, update, and deletion. The database 23 stores data on the status representing the processing status of the workflow.

  Examples of data recorded in the database 23 are shown in FIGS. 4a, b, c, d, e, and FIG. The database 23 includes user data (FIG. 4a) about the person who uses the workflow system, organization data representing the organization of the company (FIG. 4b), title data representing the order of the titles in the company (FIG. 4c), Workflow data (Fig. 4d) for application documents processed or processed in the past, template management data (Fig. 4e) of various application documents that can be applied in the workflow system, templates (Fig. 5), application documents, etc. are recorded Is done.

  The user data includes a user name of a person who can log in to the server 2 (users such as an applicant, an approver, and an authorizer), a user ID for identifying the user, a password, an organization ID, a title ID, authority, and an email address. , An imprint character string, and a description. This user data is data used at the time of user login, creation / update of workflow data, and stamping by the electronic seal stamp subsystem 21, and is created in advance by the administrator of the server 2.

The user ID and password are data used for user login, and are referred to when the user ID and password are input from the client 3.
The organization ID is data representing which organization (department, section, etc.) the user belongs to. The title ID is data representing the title of the user (employee, section manager, etc.). The authority is data indicating whether the user has the authority to become an applicant, an approver, a reviewer, or a finalizer. For example, if the authority is “1”, it represents the authority to become an applicant, “2” represents the authority to be an applicant and approver, and if “3”, the applicant, Represents becoming an approver and reviewer.

  The imprint character string is used to generate imprint data that is used when the electronic seal stamp subsystem 21 performs the seal. Based on the seal character string, the electronic seal stamp subsystem 21 generates seal stamp data using a seal stamp program. In addition, the seal character string may be associated with the image data of the seal imprint used at the time of stamping. When the electronic seal stamp subsystem 21 performs the seal, the image data of the seal imprint associated with the seal stamp character string is stored. You may make it use.

  The organization data is associated with the organization ID of the user data, and includes the organization name, organization head name, parent organization ID, description, and the like in addition to the organization ID. The organization name represents the organization name of the organization ID. The organization head name indicates the name of the head of the organization, for example, when the organization is a section. The parent organization ID represents the parent organization of the organization, for example, the department organization ID when the organization is a section.

The title data is associated with the title ID of the user data, and includes the title name, class, description, etc. in addition to the title ID. The title name represents the title name of the title ID. The class represents the class of the title.
User data, organization data, and title data are used to assign certifiers (authorizers, reviewers, and finalists) in the workflow.

  The workflow data includes the document number and work ID representing the application document processed by the workflow, the work ID indicating the current status of the processing according to the workflow, and the application representing the applicant of the application document processed by the workflow. An ID of an approver, an approver ID representing an approver, a reviewer ID representing a reviewer, and an authorizer ID representing an authorizer. The user ID of the corresponding person is used as the applicant ID, the approver ID, the reviewer ID, and the authorizer ID. The document number is a number assigned to manage the application documents in the real world. When a user calls an application document created from the client 3, it is easier to use a document number because the number of digits is smaller than to use an authentication ID.

  The template management data is data for managing templates stored in the database 23. In order to be able to identify the template of each application document by the document ID, it is attached to each template. When the document name of the required application document is input from the client 3, the workflow management system 20 searches the document ID of the input document name with reference to the template management data, and reads the template having the document ID. And sent to the client 3.

  The template recorded in the database 23 is given a document ID for identifying each template, and is read out by a request from the client 3 and sent to the client 3. The template is created in advance using the management tool 214 by the administrator of the server 2. The user operates the client 3 to write necessary items in the template, thereby creating an application document. An example of the template is shown in FIG. This template is provided with an area where writing by a user is possible and a protection area where writing is prohibited. As for the writable area by the user, a different area is specified depending on whether the user is an applicant, an approver, a reviewer, or an approver.

  In the example of FIG. 5, the area (cells 1 to 4) where the electronic seal stamp is stamped is a protected area in which writing is prohibited from any user. The electronic seal stamp subsystem 21 embeds seal stamp data. The area to be stamped is determined by the progress of the workflow. The workflow data includes a work ID indicating the progress status of the workflow, and an area for embedding the seal impression data is determined in accordance with the progress status. For example, if the work ID indicates that the application by the applicant has been completed, the area to be stamped is determined as “cell 1”.

Also, the authentication ID is embedded in the protected area by the electronic seal stamp subsystem 21 so that the user cannot see it. Since the work ID is included in the authentication ID, the progress status in the workflow of the application document can be known from the embedded authentication ID.
The template includes an “authentication” button for confirming authentication. When the “authentication” button is clicked, the progress of the application document is confirmed by the authentication ID of the workflow data stored in the database 23 by the authentication ID confirmation servlet 22, and the history of the application document is displayed on the display of the client 3. It has come to be. This history makes it possible to know even when unauthorized authentication is performed, and it is possible to guarantee authentication by a valid authenticator.
Further, the document ID is embedded in the protected area so as not to be visually recognized by the user, and this document ID is referred to when the template is read.

  The area that the applicant can write is only the “subject” and “content” areas, and the other areas are protected areas. The area that can be written by the approver is only the “approval comment” area, and the other areas are protected areas. The area that can be written by the reviewer is only the area of “Review comment”, and the other areas are protected areas. The area that the authorizer can write is only the “settlement comment” area, and the other areas are protected areas. The writable area can be specified by a macro defined for each work in the workflow. For example, different macros are read depending on the work ID, and the writable area is changed.

Processing performed by the system 1 as described above will be described with reference to FIGS.
FIG. 6 is a diagram for explaining the workflow in this process and the apparatus used for the process. The flow definition tool 215 creates workflow data based on this workflow. In this workflow, in the new creation process, the applicant creates an application document by the client A and the applicant's seal is performed by the electronic seal stamp subsystem 21. Next, in the authentication process, the certifier (authorizer) authenticates the application document by the client B, and the electronic seal stamp subsystem 21 performs the seal of the certifier. Next, in the authentication process, the certifier (inspector) inspects the application document by the client C, and the electronic seal stamp subsystem 21 performs the seal of the certifier. Next, in the authentication process, the authenticator (authorizer) authenticates the application document by the client D, and the electronic seal stamp subsystem 21 performs the seal of the authenticator.

  7 to 9 are diagrams showing the flow of processing using this workflow system. FIG. 7 shows the flow of a new application document creation process, FIG. 8 shows the flow of the application document authentication (approval, inspection, approval) process, and FIG. 9 shows the user authentication history as a client. 3 shows the flow of processing displayed on the display 3. FIG. 10 is a diagram for explaining a screen displayed on the display of the client 3.

  In these processes, first, the user needs to log in to the server 2 from the client 3. At that time, the user starts up a Web browser included in the client 3 and accesses the server 2. When the Web browser is started and the server 2 is accessed, a login screen as shown in FIG. 10A is displayed on the display of the client 3.

  When the user inputs his / her user ID and password with the input device of the client 3, the input user ID and password are sent from the client 3 to the workflow management system 20 of the server 2 (step S701). The workflow management system 20 checks the sent user ID and password against the user data recorded in the database 23, and confirms whether or not the user is a legitimate user (step S702). If it is confirmed that the user is a legitimate user, the user can use the workflow system. When it is not confirmed that the user is a legitimate user, the workflow management system 20 displays on the display of the client 3 that the login has failed.

  When confirming that the user is a regular user, the workflow management system 20 displays a menu screen as shown in FIG. 10B on the display of the client 3 (steps S703 and S704). The user selects a process to be performed from the menu screen displayed on the display. In this embodiment, three processes of “new application”, “authentication process”, and “history confirmation” can be selected.

“New application” is a menu for calling a function for creating a new application document from a template and drafting a new workflow.
The “authentication process” is a menu for calling a function for authenticating data waiting for processing in response to an authentication request by a logged-in user.
“History confirmation” is a menu for calling a function for confirming workflow data related to the past by the logged-in user.

The client 3 notifies the workflow management system 20 of the content selected by the user. The workflow management system 20 executes a process according to the selection content notified from the client 3. Here, the process of “new application” is selected by the user and notified from the client 3 to the workflow management system 20 (step S705). When confirming that the user's selection is “new application”, the workflow management system 20 sends a template to the client 3 (steps S706 and S707).
When a plurality of templates are prepared in the database 23, it may be possible to select which template is used for a new application when the user selects a menu. For example, when the user selects the “new application” process, the document name is input. The workflow management system 20 sends a template corresponding to the document name to the client 3.

  When the template is sent from the workflow management system 20, the template is displayed on the display of the client 3 (step S708). The user writes the necessary items in the writable area of the template and creates an application document. The application document will be given a document number. The created application document is sent together with the document number from the client 3 to the workflow management system 20 (step S709). This is the end of the process related to the new application for application documents by the client 3. Since the template is protected and protected, the applicant cannot directly stamp the application document by himself / herself. When the applicant finishes sending the application document to the workflow management system 20, he logs out from the server 2 and ends the process (step S710).

  When the application document is sent from the client 3, the workflow management system 20 accepts the application document, and the flow definition tool 215 creates workflow data for the application document based on the workflow of FIG. 6, together with the application document. Save in the database 23 (step S711). In the workflow data, the user who created the application document becomes an applicant, and an authenticator (an approver, a reviewer, a finalizer) is assigned according to the applicant. As the authentication ID, a business ID for identifying the workflow data and a work ID indicating that the application has been made are added. Next, the workflow management system 20 notifies the electronic seal stamp subsystem 21 of workflow data (step S712).

  The electronic seal stamp subsystem 21 receives the workflow data (step S713). The electronic seal stamp subsystem 21 determines that the workflow data is newly created from the notified authentication ID of the workflow data. The electronic seal stamp subsystem 21 transmits an authentication ID of workflow data to request an application document, confirms the applicant ID of workflow data, and requests an applicant's seal character string (step S714).

  In response to a request from the electronic seal stamp subsystem 21, the workflow management system 20 sends the application document for the authentication ID and the applicant's seal character string to the electronic seal stamp subsystem 21 (step S715). The electronic seal stamp subsystem 21 generates seal stamp data from the seal stamp character string sent from the workflow management system 20. Thereafter, the electronic seal stamp subsystem 21 performs sealing by embedding the applicant's seal data in the application document sent from the workflow management system 20 (step S716).

  The application document includes a macro for releasing the protection protection when sent to the electronic seal stamp subsystem 21. Therefore, the electronic seal stamp subsystem 21 can embed seal stamp data in an area that is originally protected and protected. The electronic seal stamp subsystem 21 embeds the applicant's seal data in the “cell 1” area where the seal is to be performed, since it can be seen from the authentication ID of the workflow data that this application document has been newly created. Once the seal is finished, the application document will be protected again.

  When the seal is completed, the electronic seal stamp subsystem 21 notifies the workflow management system 20 of the end of the seal. When receiving the notification of the end of the seal, the workflow management system 20 updates the work ID of the workflow data to indicate that the seal of the applicant has ended (step S717). The workflow management system 20 sends the updated workflow data to the electronic seal stamp subsystem 21.

  Upon receiving the updated workflow data from the workflow management system 20, the electronic seal stamp subsystem 21 writes the authentication ID of this workflow data in the protection area from the user of the application document (step S718). The authentication ID is written, for example, in the “authentication ID” area of the template shown in FIG.

  The application document for which the seal and the authentication ID have been written is stored in the database 23 by the workflow management system 20 (step S719). As described above, new application documents are created, stored, and managed.

  Next, a process in which the certifier (approver, reviewer, and finalizer) authenticates (approves, reviews, and finalizes) the application document will be described. Approval, censorship, and approval are the same process. Here, the approval process will be described as an example.

  Since the process from login to display of the menu screen (steps S801 to S804) is the same as steps S701 to S704 at the time of new application, description thereof is omitted here. When the menu screen is displayed on the display of the client 3, the user selects “authentication process”. The selected content is notified to the workflow management system 20 (step S805). When the workflow management system 20 confirms that the user's selection is “authentication processing”, the workflow management system 20 searches for application documents that require authentication by the user (steps S806 and S807). This can be understood from the workflow data stored in the database 23. Since the workflow progress status is known from the work ID of the workflow data, the workflow data that has been completed up to the applicant's seal is searched. Also, the workflow data to which the logged-in user is assigned as the approver is searched. The workflow data included in any search result becomes the workflow data of the application document that requires authentication by the user. The document number attached to the workflow data is notified to the client 3 as a search result (step S808).

  The client 3 displays the search result notified from the workflow management system 20 on the display (step S809). For example, a list of document numbers is displayed on the display. An input screen as shown in FIG. 10C is displayed. The user inputs a desired document number among the document numbers displayed on the display in the “document NO” field of the input screen. The client 3 requests the application document by sending the input document number to the workflow management system 20 (step S810). The workflow management system 20 retrieves the application document from the document number sent from the client 3 and sends it to the client 3 (step S811). The workflow management system 20 searches the workflow data for an authentication ID corresponding to the document number sent from the client 3, and specifies an application document corresponding to the searched authentication ID. The specified application document is sent to the client 3.

  The application document sent from the workflow management system 20 is displayed on the display of the client 3 (step S812). The user decides whether to review and approve the displayed application document. In the case of approval, for example, “authentication” is clicked from the authentication screen as shown in FIG. By clicking “authentication”, a notification indicating authentication is sent from the client 3 to the workflow management system 20 (step S813). If either “authentication” or “denial” is clicked, the screen returns to the search result display screen in step S 809, and it is possible to proceed to authentication work for other application documents. When the authentication work is completed, the approver logs out from the server 2 and ends the process (step S814).

  When the workflow management system 20 receives a notification from the client 3 indicating that the application document has been authenticated, the workflow management system 20 indicates that the work ID included in the workflow data of the application document stored in the database 23 has been approved. Update to work ID. After the update, the workflow data is notified to the electronic seal stamp subsystem 21 (step S815).

  The electronic seal stamp subsystem 21 receives the workflow data (step S816). The work ID of the notified workflow data indicates that the workflow has been approved. According to the workflow, the electronic seal stamp subsystem 21 performs the seal of the approver, which is the next process. For this purpose, the workflow management system 20 sends an authentication ID of workflow data to request an application document, The approver ID of the workflow data is confirmed, and an imprint character string of the approver is requested (step S817).

  In response to the request from the electronic seal stamp subsystem 21, the workflow management system 20 sends the application document of the authentication ID and the seal character string of the approver to the electronic seal stamp subsystem 21 (step S818). The electronic seal stamp subsystem 21 generates imprint data of the approver from the imprint character string of the approver using the imprint program, and embeds it in the application document sent from the workflow management system 20 (step S819). Since the work ID of the workflow data indicates that the workflow of the application document indicates the approver's seal, the electronic seal stamp subsystem 21 embeds the seal data in the “cell 2” area. When the embedding of the seal stamp data is finished, the electronic seal stamp subsystem 21 notifies the workflow management system 20 of the end of the seal. Upon receiving the notification of the end of the seal, the workflow management system 20 updates the work ID of the workflow data to indicate that the approver's seal has ended (step S820). The updated workflow data is notified to the electronic seal stamp subsystem 21. The electronic seal stamp subsystem 21 updates the authentication ID embedded in the application document based on the notified work ID (step S821). In a series of processing from the stamping to the update of the authentication ID, as in the case of a new application, the protection protection of the application document is once released, and the protection protection is again applied after completion.

  The application document for which the approver's seal and authentication ID have been updated is overwritten and saved in the database 23 by the workflow management system 20. Thereby, the application document is updated (step S822). As described above, the approval process by the approver is completed. The same process is performed for censorship and approval.

  The workflow of FIG. 6 is completed by executing the processing of FIG. 7 (application) → FIG. 8 (approval) → FIG. 8 (inspection) → FIG. 8 (decision). By repeating the authentication process by the number of authenticators, even when there are more authenticators, all authentication processes are performed.

Next, authentication history confirmation processing by the user will be described.
Since the process from login to display of the menu screen (steps S901 to S904) is the same as steps S701 to S704 at the time of new application, description thereof is omitted here. When the menu screen is displayed on the display of the client 3, the user selects “confirm history”. The selected content is notified to the workflow management system 20 (step S905). When the workflow management system 20 confirms that the user's selection is “history confirmation”, the workflow management system 20 searches for application documents authenticated by the user (steps S906 and S907). This can be understood from the workflow data stored in the database 23. The workflow data in which the user is assigned as the certifier to the “approver”, “inspector”, and “approver” of the workflow data is searched. Next, from the search results, a search is performed for a user ID that has been authenticated by the work ID. The document number attached to the workflow data of the search result is notified to the client 3 as the search result (step S908).

  The client 3 displays the search result notified from the workflow management system 20 on the display (step S909). For example, a list of document numbers is displayed on the display. An input screen as shown in FIG. 10C is displayed. The user inputs a desired document number among the document numbers displayed on the display in the “document NO” field of the input screen. The client 3 requests the application document by sending the input document number to the workflow management system 20 (step S910). The workflow management system 20 searches for the application document from the document number sent from the client 3 and sends it to the client 3 (step S911). The workflow management system 20 searches the workflow data for an authentication ID corresponding to the document number sent from the client 3, and specifies an application document corresponding to the searched authentication ID. The specified application document is sent to the client 3.

  The application document sent from the workflow management system 20 is displayed on the display of the client 3 (step S912). In this way, application documents authenticated in the past from the user are retrieved and displayed. If it is desired to view other application documents, the application number may be requested by inputting the document number of the other application document in step S910. When the display of the application document ends, the user can end the process by logging out from the server 2 (step S913).

  With the configuration described above, even if the application document is duplicated, the progress of the application document can be known by centrally managing the workflow of the application document, so that unauthorized stamping can be prevented. Therefore, even in an environment where an electronic seal stamp can be copied, authentication by a valid certifier can be guaranteed.

The whole block diagram of a system provided with the server in which the workflow system of this invention was formed. The detailed block diagram of a workflow system. FIG. FIG. 4 is an exemplary diagram of user data. The example figure of organization data. The illustration figure of title data. FIG. 6 is a view showing an example of workflow data. FIG. 6 is an exemplary diagram of template management data. FIG. The figure for demonstrating the apparatus used for a workflow and a process. The figure which shows the flow of the process using a workflow system. The figure which shows the flow of the process using a workflow system. The figure which shows the flow of the process using a workflow system. FIG. 10A is an example of a screen displayed on a client display, FIG. 10A is a login screen, FIG. 10B is a menu screen, FIG. 10C is an input screen, and FIG. 10D is an authentication screen. It is a screen.

Explanation of symbols

1 System 2 Server 3 Client 4 Network 20 Workflow Management System 21 Electronic Seal Subsystem 22 Authentication ID Confirmation Servlet 23 Database 210 Engine 211 Application API
212 Application 213 Management API
214 Management Tool 215 Flow Definition Tool 216 Batch Tool

Claims (8)

A document is provided with a communication unit that enables transmission and reception of data to and from one or more clients, and represents a document provided with a first area that permits writing by a user who operates the client and a second area that does not permit An office processing system for marking electronic documents based on a predetermined workflow,
According to the progress of the process based on the workflow, assigning a user to perform the seal on the electronic document, and workflow data including data for specifying the assigned user and progress data indicating the progress of the workflow, Workflow management means for generating by adding identification data for identifying the workflow data;
The workflow data is used to confirm the progress of the workflow, identify the assigned user according to the confirmed progress, and embed the imprint data of the identified user in the second area of the electronic document. An electronic seal stamp means for embedding the progress data and the identification data in the second area of the electronic document invisible to the user,
The workflow management means is configured to store an electronic document in which the imprint data, the progress data, and the identification data have been embedded in a predetermined storage means in association with corresponding workflow data.
Business processing system. The seal imprint data includes a character string for expressing an image,
The storage means stores the character string for each user,
The electronic seal stamp means is configured to acquire the character string of the user from the storage means and generate the user's seal data from the character string.
The business processing system according to claim 1. The storage means stores the imprint data for each user,
The electronic seal stamp means is configured to acquire imprint data of a user who performs a seal from the storage means.
The business processing system according to claim 1. In the second area, an area that can be stamped is determined for each process based on the workflow.
The workflow management means is configured to assign a user who performs the seal for each process based on the workflow,
The electronic seal stamp means is configured to embed, in each process based on the workflow, imprint data of a user assigned to perform a seal in the process in a predetermined area that can be stamped.
The business processing system according to claim 1. The process based on the workflow includes at least a first process for marking the first user who created the electronic document and a second process for marking the second user who authenticates the electronic document.
In the area where the electronic document can be imprinted, at least a first imprint area where the first user is imprinted and a second imprint area where the second user is imprinted are determined,
The workflow management means is configured to assign the second user to a user who performs the second process.
The electronic seal stamp means embeds the imprint data of the first user in the first imprint area during the first process, and embeds the imprint data of the second user in the second imprint area during the second process. It is configured,
The business processing system according to claim 4. The workflow management means is configured to update the progress data every time processing based on the workflow is executed one by one,
The electronic seal stamp means is configured to update the progress data written in the electronic document each time the seal is performed.
The paperwork system in any one of Claims 1-5. A communication unit that enables transmission and reception of data to and from one or more clients, and a workflow management unit that generates workflow data indicating the order in which the processes are executed and the user who executes the processes based on a predetermined workflow A method executed by a business processing system having an electronic seal means for performing an electronic seal,
When the workflow management means receives from the client an electronic document representing a document provided with a first area that is allowed to be written by a user who operates the client and a second area that is not permitted, the seal is attached to the electronic document. Assigning a user to perform workflow, and generating workflow data including data for specifying the assigned user and progress data representing progress of the workflow, with identification data for identifying the workflow data being generated When,
The electronic seal stamp means confirms the progress status of the workflow based on the workflow data, identifies the user assigned according to the confirmed progress status, and stores the imprint data of the identified user in the second area of the electronic document. Embedding it in the seal, and embedding the progress data and the identification data in the second area of the electronic document invisible to the user;
The workflow management means includes storing the seal stamp data, the progress data, and the electronic document in which the identification data has been embedded in a predetermined storage means in association with the corresponding workflow data.
Paperwork method. A computer having communication means for enabling transmission and reception of data to and from one or more clients;
Assignment of a user who stamps an electronic document representing a document provided with a first area that allows writing by a user who operates the client and a second area that does not allow according to the progress of processing based on a predetermined workflow Workflow management means for generating workflow data including data for specifying the assigned user and progress data representing progress of the workflow with identification data for identifying the workflow data,
Based on the workflow data, the progress status of the workflow is confirmed, the assigned user is identified according to the confirmed progress status, and the imprint data of the identified user is embedded in the second area of the electronic document. Forming an electronic seal stamp means for embedding the progress data and the identification data in the second area of the electronic document invisible to the user,
In order for the workflow management means to store the seal stamp data, the progress data, and the electronic document in which the identification data has been embedded in a predetermined storage means in association with the corresponding workflow data,
Computer program.

Images