Document file approval system, document file approval method, and recording medium

Abstract

To provide a document file approval system and a program for easily setting whether or not it is necessary for an approver to sign or seal.SOLUTION: In a document file approval system 100, a first user terminal 110 displays a predetermined document approval setting screen 112 having a setting field 116 about the necessity of a signature or a seal of an approver, designates a document file DF to execute an upload operation, executes a setting operation about approver information, and selects the setting of the necessity of the signature or the seal of the approver. When the transmission operation is performed, the server 130 transmits the approval request notification to the second user terminal 120. The second user terminal 120 displays the content of the document file on the basis of the access operation. The server 130 changes the status to the approved status based on the approval operation including the signature operation or the postmark operation according to the setting of whether or not the signature SN or the postmark SP of the second user is necessary.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a document file approval system that includes a plurality of user terminals and a server and approves the contents of document files, and a program therefor. [Background technology]

[0002] Conventionally, there has been known a workflow system that includes a user terminal and a server, in which an approver is set on a workflow screen, and when an approval operation is performed on the workflow screen displayed by the browser on the approver's user terminal, the approver's user terminal sends information indicating approval to the server, and the server executes a predetermined operation on the server that is set in advance in accordance with the application content information based on the information indicating approval received from the approver's user terminal and the application content information of the workflow (for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2024-59298 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the conventional workflow system described above was configured so that the approver only had to press the approval button when approving the content to be approved, and had the problem that the applicant or the setting person could not set whether or not a seal or signature was required for the content to be approved.

[0005] Therefore, the present invention solves the problems of the prior art as described above, and the object of the present invention is to provide a document file approval system and a program therefor that allow the user to easily set whether or not the approver's signature or seal is required as needed. [Means for solving the problem]

[0006] The invention of claim 1 is a document file approval system that includes a plurality of user terminals and a server and approves the contents of a document file, wherein a first user terminal accesses the server, and the browser of the first user terminal displays a predetermined document approval setting screen, and the predetermined document approval setting screen has a setting field for the document file, a setting field for approver information, and a setting field for whether the approver's signature or seal is required, and when a document file is specified and an upload operation is performed on the predetermined document approval setting screen of the first user terminal, a setting operation for the approver information is performed, the setting for whether the approver's signature or seal is required is selected, and a send operation is performed, the server sends an approval request notification to a second user terminal that is the approver, and based on the access operation of the second user, the second user terminal accesses the server, and the browser of the second user terminal displays the contents of the document file, and based on the approval operation including a signing operation or a sealing operation in accordance with the setting for whether the second user's signature or seal is required, the server changes the status to approved, and based on the approval operations of all approvers, the server changes the status to completed, thereby solving the above-mentioned problem.

[0007] The invention of claim 2 further solves the above-mentioned problem by configuring the document file approval system as described in claim 1, in addition to the configuration of the document file approval system, in a setting field on a predetermined document approval setting screen of the first user terminal regarding whether or not the approver's signature or seal is required, if required, one of the items seal, handwritten signature, keyboard-input name signature, keyboard-input name text, and approval mark is displayed as a selectable option, the browser of the second user terminal displays the contents of the document file, and the server changes the status to approved based on an approval operation including an input operation by the second user in accordance with any of the settings selected by the first user, namely seal, handwritten signature, keyboard-input name signature, keyboard-input name text, and approval mark.

[0008] The invention of claim 3 further solves the above-mentioned problem by being configured such that, in addition to the configuration of the document file approval system described in claim 2, in a setting field regarding whether the approver's signature or seal is required, if required, one of the following items is displayed as a selectable option: seal, handwritten signature, keyboard-input name signature, keyboard-input name text, or approval mark; the selected item is displayed so that it can be freely positioned by drag-and-drop on the layout of the document file displayed on a specified document approval setting screen; and when the send operation is performed, the server sends a notification of an approval request to the second user terminal, who is the approver.

[0009] The invention of claim 4 further solves the above-mentioned problem by being configured such that, in addition to the configuration of the document file approval system described in claim 3, there is a setting operation for multiple approver information on the specified document approval setting screen, and when multiple items of the seal, handwritten signature, keyboard-input name signature, keyboard-input name text, and approval mark are set by drag-and-drop operation on the layout of the document file displayed on the specified document approval setting screen, when one placed field is selected for each placement, the browser of the first user terminal displays one of the multiple approver information items at will and allows for flexible assignment and setting.

[0010] The invention of claim 5 further solves the above-mentioned problem by being configured such that, in addition to the configuration of the document file approval system described in any one of claims 1 to 4, in a setting field on a predetermined document approval setting screen of the first user terminal regarding whether or not the approver's signature or seal is required, if a setting field indicates that a signature or seal is required, the browser of the second user terminal displays a seal location display button when displaying the contents of the document file, and when the seal location display button is operated, the browser of the second user terminal highlights the approval field for the second user on the layout of the document file.

[0011] The invention according to claim 6 is a program for a document file approval system for approving the contents of a document file, the program comprising: a predetermined document approval setting screen display step in which a first user terminal accesses a server, and a browser of the first user terminal displays a predetermined document approval setting screen having a setting field for the document file, a setting field for approver information, and a setting field for whether or not the approver's signature or seal is required; and a step in which a document file is designated and an upload operation is performed on the predetermined document approval setting screen of the first user terminal, a setting operation for the approver information is performed, a setting for whether or not the approver's signature or seal is required is selected, and a transmission operation is performed. The above-mentioned problem is solved by having a computer execute the following steps: an operation determination step of determining whether the second user terminal is authorized to approve the document; a notification step in which the server sends a notification of an approval request to the second user terminal who is the approver; a document file content display step in which the second user terminal accesses the server based on the access operation of the second user and the browser of the second user terminal displays the contents of the document file; and a status change step in which the server changes the status to approved based on an approval operation including a signing operation or a stamping operation depending on whether the second user's signature or stamping is required, and changes the status to completed based on the approval operations of all approvers. [Effects of the Invention]

[0012] The document file approval system of the present invention is equipped with multiple user terminals and a server, which not only enables communication between the multiple user terminals and the server to approve the contents of document files, but also provides the following unique effects.

[0013] According to the document file approval system of the invention of claim 1, the first user, who is the configurator, can freely set whether or not the approver's signature or seal is required, so the configurator can easily set whether or not the approver's signature or seal is required as needed.

[0014] According to the document file approval system of the invention of claim 2, in addition to the effects achieved by the invention of claim 1, the first user (the person setting up the system) can freely select and set one of the following for the second user (the approver): a seal, a handwritten signature, a keyboard-input name signature, a keyboard-input name text, or an approval mark. Therefore, the person setting up the system can easily set the input of the approver's seal, handwritten signature, keyboard-input name signature, keyboard-input name text, or approval mark as needed.

[0015] According to the document file approval system of the invention of claim 3, in addition to the effects achieved by the invention of claim 2, if necessary, the person setting it up can freely select from among a seal, handwritten signature, keyboard-input name signature, keyboard-input name text, and approval mark, and the placement position can also be freely set, so the person setting it up can select and set from among a seal, handwritten signature, keyboard-input name signature, keyboard-input name text, and approval mark depending on the content of the document file, and can also freely set the position.

[0016] According to the document file approval system of the invention of claim 4, in addition to the effect achieved by the invention of claim 3, when multiple approval columns are placed, it becomes difficult to know which approval column is for whom. However, since the person who sets it can freely set which approval column is for whom, each approver can easily understand which approval column they should enter their seal, handwritten signature, keyboard-input name signature, keyboard-input name text, or approval mark into. In other words, it is possible to prevent the approver from making an incorrect entry in the approval field.

[0017] According to the document file approval system of the invention of claim 5, in addition to the effect achieved by the invention of any one of claims 1 to 4, when the stamp location display button is operated, the approval field for the second user is highlighted, so that the second user can easily understand which location to operate to enter either a stamp, handwritten signature, keyboard-input name signature, keyboard-input name text, or approval mark.

[0018] According to the program for the document file approval system of the invention of claim 6, similar to the effect achieved by the invention of claim 1, the first user, who is the configurator, can freely set whether or not the approver's signature or seal is required, so the configurator can easily set whether or not the approver's signature or seal is required as needed. [Brief explanation of the drawings]

[0019] [Figure 1] 1 is a diagram showing the concept of a document file approval system according to an embodiment of the present invention; [Figure 2] 1 is a flowchart showing an example of the operation of a document file approval system according to an embodiment of the present invention; [Figure 3] (A) and (B) are figures showing how a document file is uploaded on the document file approval function screen for the configurator, which serves as the document approval setting screen displayed on the browser of the configurator terminal, which serves as the first user terminal of the document file approval system, which is an embodiment of the present invention, and how an approval document case is registered for the uploaded document file. [Figure 4] (A) and (B) are figures showing how approver information is set on the document file approval function screen for the configurator displayed on the browser of the configurator terminal of the document file approval system, which is an embodiment of the present invention, and how the setting for whether or not a signature or seal is required is selected. [Figure 5](A) and (B) are figures showing how the placement of stamp fields is set on the document file approval function screen for the configurator displayed on the browser of the configurator terminal of the document file approval system, which is an embodiment of the present invention, and how the approver to be assigned to the placed stamp field is set. [Figure 6] (A) and (B) are figures showing the state in which whether or not to add a comment is selected when an operation to send approval document case information to an approver is performed on the document file approval function screen for the configurator displayed on the browser of the configurator terminal of a document file approval system which is an embodiment of the present invention, and a figure showing the state in which an operation to add a comment and send is performed. [Figure 7] (A) and (B) are figures showing the status of the approver after performing an operation to send on the document file approval function screen for the configurator displayed on the browser of the configurator terminal of the document file approval system, which is an embodiment of the present invention, and a figure showing the state in which the browser of the approver terminal, which is a second user terminal, receives notification of approval document case information from the server and accesses the server by the approver's operation. [Figure 8] (A) and (B) are figures showing the state when the browser on the approver terminal of the document file approval system, which is an embodiment of the present invention, displays the document file approval function screen for the approver, and a figure showing the stamping operation being performed on the approver terminal. [Figure 9] 10A to 10D are diagrams showing an example of a configuration in which a handwritten signature is added to a document file instead of a seal when approving a document file, which is an embodiment of the document file approval system of the present invention; a diagram showing an example of a configuration in which a keyboard-input name signature is added to a document file instead of a seal; a diagram showing an example of a configuration in which keyboard-input name text is added to a document file instead of a seal; and a diagram showing an example of a configuration in which an approval mark is added to a document file instead of a seal. [Figure 10] (A) and (B) are figures showing the state in which whether or not to add a comment is selected when an operation to approve is performed on the document file approval function screen for the approver displayed on the browser of the approver terminal of the document file approval system, which is an embodiment of the present invention, and a figure showing the state in which a comment is added and an operation to approve is performed. [Figure 11](A) and (B) are figures showing how the status of approver information is changed on the approver document file approval function screen displayed on the browser of the approver terminal of a document file approval system that is an embodiment of the present invention, and how the browser of the configurator terminal receives notification emails indicating that approval operations have been completed from all approvers and attempts to access the server through the configurator's operation. [Figure 12] (A) and (B) are figures showing the browser on the configurator's terminal of the document file approval system, which is an embodiment of the present invention, displaying a document file with a seal and signature on the document file approval function screen for the configurator, and a figure showing the list of approved document case information displayed on the document file approval function screen for the configurator. DETAILED DESCRIPTION OF THE INVENTION

[0020] The document file approval system of the present invention includes a plurality of user terminals and a server, and when a first user terminal accesses the server, a browser on the first user terminal displays a predetermined document approval setting screen, and the predetermined document approval setting screen is provided with a setting field for the document file, a setting field for approver information, and a setting field for whether or not the approver's signature or seal is required, and when a document file is designated and an upload operation is performed, a setting operation for the approver information is performed, a setting for whether or not the approver's signature or seal is required is selected, and a send operation is performed, the server sends a The specific implementation may be any one as long as the system is configured such that a notification of an approval request is sent to the second user terminal, the second user terminal accesses the server based on the second user's access operation, the browser of the second user terminal displays the contents of the document file, the server changes the status to approved based on the approval operation including a signing operation or a sealing operation according to the second user's setting of whether a signature or sealing is required, and the server changes the status to completed based on the approval operations of all approvers, thereby allowing the setting person to easily set whether an approver's signature or sealing is required as needed. The program for the document file approval system of the present invention includes a predetermined document approval setting screen display step in which a first user terminal accesses a server, and a browser of the first user terminal displays a predetermined document approval setting screen having a setting field for the document file, a setting field for approver information, and a setting field for whether or not the approver's signature or seal is required; an operation determination step in which, on the predetermined document approval setting screen of the first user terminal, a document file is designated and an upload operation is performed, a setting operation for approver information is performed, a setting for whether or not the approver's signature or seal is required is selected, and a transmission operation is determined; and a step in which the server sends an approval request to a second user terminal that is the approver. The specific implementation may be any one as long as the setting person can easily set whether or not an approver's signature or seal is required as needed by having a computer execute the following steps: a notification step of sending a notification; a document file content display step in which the second user terminal accesses the server based on the second user's access operation and the browser of the second user terminal displays the contents of the document file; and a status change step in which the server changes the status to approved based on an approval operation including a signing operation or a sealing operation according to a setting of whether or not the second user's signature or seal is required, and changes the status to completed based on the approval operations of all approvers.

[0021] For example, the user terminal may be a desktop personal computer terminal, a notebook personal computer terminal, a smartphone terminal, a tablet terminal, a wristwatch terminal, an eyeglass terminal, or any other terminal that displays data on a screen in a browser on the display unit of the user terminal and connects to a server via a communication network including a wide area network such as the Internet, a local network, or a telephone line to send and receive data. Furthermore, the server may be a cloud server created in a cloud environment, and the number of physical servers that make up the server may be one or more. Furthermore, in this case, a document file can be any file that contains document information such as character information and numerical information, such as one that contains text data or one that consists of scanned pixel data without text data. The document file may be a single page or multiple pages. [Example]

[0022] A document file approval system 100 according to an embodiment of the present invention will be described below with reference to FIGS. 1 to 12(B). 1 is a diagram showing the concept of document file approval system 100 according to an embodiment of the present invention, FIG. 2 is a chart showing an example of the operation of document file approval system 100 according to an embodiment of the present invention, FIG. 3(A) is a diagram showing the state when a document file DF is uploaded on document file approval function screen 112 for setter as a document approval setting screen on browser 111 of setter terminal 110 as a first user terminal of document file approval system 100 according to an embodiment of the present invention, and FIG. 3(B) is a diagram showing the state when a document file DF is uploaded on document file approval function screen 112 for setter as a document approval setting screen on browser 111 of setter terminal 110 4A is a diagram showing how an approval document case is registered for an uploaded document file DF on the document file approval function screen 112, and FIG. 4(A) is a diagram showing how approver information GT is set on the document file approval function screen 112 for the setter in the browser 111 of the setter terminal 110 of the document file approval system 100, which is an embodiment of the present invention. FIG. 4(B) is a diagram showing how whether or not a signature (handwritten signature HR, handwritten-style signature SN, etc.) and a seal (seal impression SP) are required is selected on the document file approval function screen 112 for the setter in the browser 111 of the setter terminal 110. 5(A) is a diagram showing how the layout of the seal fields is set on the setter's document file approval function screen 112 on the browser 111 of the setter terminal 110 of the document file approval system 100, which is an embodiment of the present invention; FIG. 5(B) is a diagram showing how the approver to be assigned to the seal fields arranged on the setter's document file approval function screen 112 on the browser 111 of the setter terminal 110 is set; and FIG. 6(A) is a diagram showing how the layout of the seal fields is set on the setter's document file approval function screen 112 on the browser 111 of the setter terminal 110 of the document file approval system 100, which is an embodiment of the present invention; FIG. 6(B) is a diagram showing the state in which whether or not to add a comment is selected when an operation to send approval document case information to an approver is performed on the approval function screen 112; FIG. 6(B) is a diagram showing the state in which an operation to add a comment and send is performed on the document file approval function screen 112 for the configurator in the browser 111 of the configurator terminal 110; and FIG. 7(A) is a diagram showing the status of the approver after an operation to send is performed on the document file approval function screen 112 for the configurator in the browser 111 of the configurator terminal 110 of the document file approval system 100, which is an embodiment of the present invention.FIG. 7(B) is a diagram showing a state in which the approver terminal 120 as a second user terminal receives a notification of approval document matter information from the server 130 and accesses the server 130 by an operation of the approver. FIG. 8(A) is a diagram showing a state in which the browser 121 of the approver terminal 120 of the document file approval system 100 according to an embodiment of the present invention displays a document file approval function screen 122 for the approver. FIG. 8(B) is a diagram showing a state in which a seal operation is being performed on the document file approval function screen 122 for the approver on the browser 121 of the approver terminal 120. FIG. 9(A) is a diagram showing a state in which a seal operation is being performed on the document file approval function screen 122 for the approver on the browser 121 of the approver terminal 120. 9(A) and 9(B) are diagrams showing an example of a configuration in which a handwritten signature HR is added to a document file DF instead of a seal (seal impression SP) at the time of approval in the document file approval system 100 according to the present embodiment; FIG. 9(B) is a diagram showing an example of a configuration in which a keyboard-inputted name signature (handwritten-style signature SN) is added to a document file DF instead of a seal (seal impression SP); FIG. 9(C) is a diagram showing an example of a configuration in which a keyboard-inputted name text (name data NM) is added to a document file DF instead of a seal (seal impression SP); and FIG. 9(D) is a diagram showing an example of a configuration in which an approval mark MK is added to a document file DF instead of a seal (seal impression SP). 10(A) is a diagram showing a state where whether or not to add a comment is selected when an operation to approve is performed on the approver document file approval function screen 122 of the browser 121 of the approver terminal 120 of the document file approval system 100 which is an embodiment of the present invention, FIG. 10(B) is a diagram showing a state where a comment is added on the approver document file approval function screen 122 of the browser 121 of the approver terminal 120 and an operation to approve is performed, and FIG. 11(A) is a diagram showing a state where whether or not to add a comment is selected when an operation to approve is performed on the approver document file approval function screen 122 of the browser 121 of the approver terminal 120 of the document file approval system 100 which is an embodiment of the present invention, 11(B) is a diagram showing a state in which the status of the approver information GT is changed on the approver document file approval function screen 122 of the browser 121 of the approver terminal 120, and FIG. 11(B) is a diagram showing a state in which the setter terminal 110 receives a notification email that the approval operations from all approvers have been completed and attempts to access the server 130 by the setter's operation, and FIG. 12(A) is a diagram showing a state in which the browser 111 of the setter terminal 110 of the document file approval system 100, which is an embodiment of the present invention, displays a seal (seal impression SP) and a signature (handwritten signature HR,12(A) is a diagram showing a state in which a document file DF containing a handwritten signature SN is displayed, and FIG. 12(B) is a diagram showing a state in which a list of approval document case information is displayed on the document file approval function screen 112 for the scrivener of the browser 111 of the scrivener terminal 110.

[0023] As shown in FIG. 1, a document file approval system 100 according to an embodiment of the present invention includes a setter terminal 110 as a first user terminal, which is an example of a plurality of user terminals, an approver terminal 120 as a second user terminal, and a server 130. Although the number of approver terminals 120 is explained as two as an example, the number may be one or three or more. Note that the approver terminal 120 is intended as a second user terminal for the approver who approves the document file DF, but if the document file DF is a contract, it is intended as a contracting party terminal for the contracting parties, and is used as a second user terminal. In other words, it can be used for approval of an internal workflow or for an external contract. In the case of a contract with an external party, for example, one of at least two approver terminals 120 is internal and the other is external.

[0024] Furthermore, the setter terminal 110 as the first user terminal accesses the server 130, and the browser 111 of the setter terminal 110 displays the setter document file approval function screen 112 as a predetermined document approval setting screen. Here, the document file approval function screen 112 for the configurator is provided with a drag-and-drop area 113a as a setting field for the document file DF, a setting and display area 114 for the approver information GT as a setting field for the approver information GT, and a check box 116 for setting whether or not the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required. As for the drag-and-drop area 113a, the setting and display area 114 for the approver information GT, and the signature (handwritten signature HR, handwritten-style signature SN, etc.) and seal (seal impression SP) setting check box 116, it is sufficient to input data sequentially into the setting fields, and it is not necessary to display all of them at once. Then, it is assumed that a document file DF is designated and an upload operation is performed on the settler document file approval function screen 112 of the settler terminal 110 serving as the first user terminal. Furthermore, it is assumed that a setting operation for the approver information GT has been performed on the document file approval function screen 112 for the setter.

[0025] Next, the setting for whether or not the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required is selected, and the "Send" button 118b, which is an example of a sending operation (registration / setting completion operation), is operated. At this time, the server 130 transmits a request notification email ML1 as a notification of the approval request to the approver terminal 120, which is the second user terminal of the approver. Here, the method of notification is not limited to email, and a short message transmission / reception system such as chat may also be used.

[0026] The approver terminal 120 as a second user terminal accesses the server 130 based on the operation of the "Check document" button ML1a in the request notification email ML1, which is an example of an access operation by the approver who is the second user. Then, the browser 121 of the approver terminal 120 serving as the second user terminal displays the contents of the document file DF on the document file approval function screen 122 for the approver. Then, based on the approval operation including a signing operation or a stamping operation depending on the setting of whether or not the second user, who is the approver, needs to sign (handwritten signature HR, handwritten-style signature SN, etc.) or stamp (seal impression SP), the server 130 changes the status to approved. Furthermore, the server 130 is configured to change the status to completed based on the approval operations of all approvers.

[0027] This allows the setting person, who is the first user, to freely set whether or not the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required. As a result, the person setting the setting can easily set whether or not the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required, as needed.

[0028] Next, the operation of the document file approval system 100 will be described in more detail. As shown in FIG. 2, in step S1, as a step for determining whether or not the server 130 has been accessed from the first user terminal, the configurator terminal 110 (a step for displaying a predetermined document approval setting screen), it is determined whether or not a predetermined URL has been input into the configurator terminal 110 and an operation to access the server 130 has been performed.

[0029] More specifically, the browser 111 determines whether or not a login operation to the document file approval system 100 has been performed on the settlor terminal 110 and an HTTP request to the server 130 has been made. If it is determined that an http request has been received, the process proceeds to step S2, and if it is determined that no http request has been received, step S1 is repeated.

[0030] In step S2, as a predetermined document approval setting screen display step, the server 130 transmits data of the document file approval function screen 112 for the settler as a predetermined document approval setting screen to the settler terminal 110 as an HTTP response. Then, as shown in FIG. 3(A), the browser 111 of the setter terminal 110, which is the first user terminal, displays a setter document file approval function screen 112 as a predetermined document approval setting screen.

[0031] The document file approval function screen 112 for the configurator is provided with a drag-and-drop area 113a as a setting field for the document file DF, a setting and display area 114 for approver information GT as a setting field for the approver information GT, and a check box 116 for setting whether or not the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required. These will be explained in order as appropriate.

[0032] In step S3, as an upload operation determination step (operation determination step), the browser 111 determines whether or not a document file DF has been specified and an upload operation has been performed on the document file approval function screen 112 for the settler of the settler terminal 110, which is the first user terminal. More specifically, as shown in FIG. 3(A), when the configurator operates the "Create a new document" button 113 on the configurator document file approval function screen 112, a drag-and-drop area 113a is displayed. Here, "new documents" refers to new cases.

[0033] When the icon of the document file DF is moved to the drag-and-drop area 113a by the user using a drag-and-drop operation, the data of the document file DF is uploaded to the server 130. When the drag-and-drop area 113a is clicked, the browser 111 displays hierarchical folders, allowing the user to freely select any document file DF. When an arbitrary document file DF is selected and designated, the selected and designated document file DF is uploaded. In this way, if the browser 111 determines that an upload operation has been performed by specifying a document file DF, the process proceeds to step S4, but if it determines that no upload operation has been performed, step S3 is repeated.

[0034] Once uploaded, the contents of the uploaded document file DF are previewed on the document file approval function screen 112 for the settler, as shown in FIG. 3(B). At the same time, a case title input field 113b and a "Create document" button 113c are displayed on the document file approval function screen 112 for the settlor. When the person who sets the setting inputs the matter title information into the matter title input field 113b and operates the "Create document" button 113c, the matter is registered with the matter title information as the title.

[0035] As shown in FIG. 4(A), the document file approval function screen 112 for the configurator displays a setting and display area 114 for approver information GT as a setting field for the approver information GT, a signature (handwritten signature HR, handwritten-style signature SN, etc.) and seal (seal impression SP) presence / absence setting checkbox 116 as a setting field for whether the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required, and a document display area 117.

[0036] In step S4, as a step for setting approver information, setting whether or not to affix a seal (seal impression SP) and a signature (handwritten signature HR, handwritten-style signature SN, etc.), and determining whether or not a sending operation has been performed (operation determination step), a setting operation for the approver information GT is performed on the document file approval function screen 112 for the setter, which is a specified document approval setting screen, and the setting for whether or not the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required is selected, and the browser 111 determines whether or not a sending operation has been performed.

[0037] More specifically, as shown in FIG. 4(A), on the document file approval function screen 112 for the configurator, the setting and display area 114 for the approver information GT has an “Add new user” button 114a and an “Add from address book” button 114b. When the user operates the "Add New User" button 114a, the browser 111 displays a user addition setting window 115. The user addition setting window 115 is provided with, for example, an email address input field 115a, a name input field 115b, and a company name input field 115c.

[0038] For example, when an alphabet is entered in the email address input field 115a, the browser 111 is configured to predict and display candidates from the stored email address information. It is assumed that the person setting the settings inputs the approver information GT into each of these fields and operates the OK button. Then, as shown in FIG. 4(B), the input approver information GT is displayed in the setting and display area 114 for the approver information GT.

[0039] When the approver operates the "Add from Address Book" button 114b, the browser 111 displays a pre-registered address book, and the approver is designated by selecting from the address book, and the approver information GT of the designated approver is displayed in the setting and display area 114 for the approver information GT. The number of approvers may be one or more. When setting multiple approvers, after setting one approver, you can set the second and subsequent approvers by operating the "Add new user" button 114a or the "Add from address book" button 114b. As shown in FIG. 4(B), in this embodiment, as an example, two approvers are set in the order of "Takagi Nao" and "John Smith."

[0040] Next, a setting as to whether or not the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required will be described. As shown in FIG. 4(B), the document file approval function screen 112 for the setter has a check box 116 for setting whether or not the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required.

[0041] If you do not require a signature (handwritten signature HR, handwritten-style signature SN, etc.) or a seal (seal impression SP), check this box. When the check box is checked, and the "Send" button 118b of the "Save" button 118a and the "Send" button 118b provided on the document file approval function screen 112 for the setter is operated, the browser 111 determines that a sending operation has been performed. When the "save" button 118a is operated, the information of this case is saved in the draft.

[0042] On the other hand, if a signature (handwritten signature HR, handwritten-style signature SN, etc.) or a seal (seal impression SP) is required, leave the box unchecked. When the check box is unchecked, as shown in Figure 5(A), for example, the following items are displayed for free selection: a seal (seal impression SP) item 116a, a handwritten signature HR item 116b, a keyboard-input name signature (handwritten-style signature SN) item 116c, a keyboard-input name text (name data NM) item 116d, and an approval mark MK item 116e.

[0043] In other words, in the signature (handwritten signature HR, handwritten-style signature SN, etc.) and seal (seal impression SP) setting checkbox 116, which is an example of a setting field for determining whether or not the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required on the document file approval function screen 112 for the setter, which is a predetermined document approval setting screen of the setter terminal 110, which is the first user terminal, if the checkbox is unchecked and a signature (handwritten signature HR, handwritten-style signature SN, etc.) and seal (seal impression SP) are required, one of the items 116e, seal (seal impression SP), handwritten signature HR, keyboard-input name signature (handwritten-style signature SN), keyboard-input name text (name data NM), and approval mark MK, is displayed so that it can be selected freely.

[0044] As an example of this, when the stamp (seal impression SP) item 116a is moved by drag-and-drop onto the layout of the document file DF displayed in the document display area 117, an approval stamp field SA1 is placed in that location. Similarly, when the keyboard-input name signature (handwritten-style signature SN) item 116c is moved by drag-and-drop onto the layout of the document file DF displayed in the document display area 117, an approval signature field SA2 is placed in that location.

[0045] That is, in the checkbox 116 for setting whether or not the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required, which is an example of a setting field for setting whether or not the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required, if the checkbox is unchecked and a signature (handwritten signature HR, handwritten-style signature SN, etc.) and seal (seal impression SP) are required, one of the items 116e, seal (seal impression SP), handwritten signature HR, keyboard-input name signature (handwritten-style signature SN), keyboard-input name text (name data NM), and approval mark MK, is displayed for free selection, and the selected item can be freely arranged and set by drag-and-drop on the layout of the document file DF displayed in the document display area 117 of the document file approval function screen 112 for the setter, which is the specified document approval setting screen.

[0046] This allows the user to freely select from among a seal (impression SP), handwritten signature HR, keyboard-input name signature (handwritten-style signature SN), keyboard-input name text (name data NM), and approval mark MK when a signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (impression SP) is required, and also allows the user to freely set the placement position. As a result, the person setting the document can select and set one of the following depending on the contents of the document file DF: a stamp (stamp impression SP), a handwritten signature HR, a keyboard-input name signature (handwritten-style signature SN), a keyboard-input name text (name data NM), or an approval mark MK, and can also freely set the position of the signature.

[0047] Furthermore, when the approval seal field SA1 and the approval signature field SA2 are selected by clicking or the like, the browser 111 displays an allocation setting window 117a in each field. The allocation setting window 117a is configured to display email address information corresponding to the approver as candidates based on the email address information of the approver information GT displayed in the setting / display area 114 for the approver information GT. The person setting the settings selects email address information as an example of approver information GT in the allocation setting window 117a, and assigns which approver will apply the approval stamp (seal impression SP) and signature (handwritten signature HR, handwritten-style signature SN, etc.) to each approval stamp field SA1 and approval signature field SA2.

[0048] This is particularly effective when there are setting operations for a plurality of approver information GT on the document file approval function screen 112 for the setter, which is a predetermined document approval setting screen. For any of the items 116e, name stamp (impression SP), handwritten signature HR, keyboard-input name signature (handwritten-style signature SN), keyboard-input name text (name data NM), and approval mark MK, when multiple items are set by drag-and-drop operation on the layout of the document file DF displayed in the document display area 117 of the document file approval function screen 112 for the setter, when one placed field is selected for each placement, one of the multiple approver information GT can be selected and displayed, allowing for free assignment and setting.

[0049] That is, when multiple approval fields are arranged, it becomes difficult to know which approval field is for whom, but this allows the person setting the approval to freely set which approval field is for whom. As a result, each approver can easily understand in which approval field they should enter either a seal (seal impression SP), a handwritten signature HR, a keyboard-input name signature (handwritten-style signature SN), a keyboard-input name text (name data NM), or an approval mark MK. In other words, it is possible to prevent the approver from making an incorrect entry in the approval field.

[0050] In addition, as an indication of whether or not allocation has been set, if allocation has been set, a check mark is displayed in each of the approval seal field SA1 and approval signature field SA2. This allows easy display of whether an allocation has been set or not. As a result, it is possible to avoid leaving allocations unset and set allocations to all approval certificate fields such as the approval seal field SA1 and the approval signature field SA2.

[0051] Next, the sending operation will be described. As shown in FIG. 6(A), when the scribble user operates the "Send" button 118b on the scribble user document file approval function screen 112, the browser 111 displays a comment addition / non-addition setting window 119, for example. If the setter wants to add a comment to the approver, click the "Yes" button. Then, as shown in FIG. 6(B), a comment input field 119a is displayed at the bottom of the document file approval function screen 112 for the settler, allowing the user to freely input a comment.

[0052] The contents of the comment are displayed in a notification email to a person lower in the order, a completion email, the document file approval function screen 122 for the approver, and the document file approval function screen 112 for the settler. Then, when the user inputs a comment and operates the "send" button 118b, the browser 111 determines that a send operation has been performed. In this way, if it is determined that a transmission operation has been performed, the process proceeds to step S5, and on the other hand, if it is determined that no transmission operation has been performed yet, step S4 is repeated. At this time, the browser 111 transmits information on the document file approval function screen 112 for the settler to the server 130.

[0053] Then, as shown in FIG. 7(A), the status information ST is displayed in correspondence with the approver information GT in the setting and display area 114 for the approver information GT on the document file approval function screen 112 for the setter. Furthermore, for the approver in the order of approval, a "Remind" button RM is also displayed in correspondence with the approver information GT. When the "Remind" button RM is operated, the server 130 is configured to notify the approver terminal 120 of the approver whose turn it is to be approved of the request by sending a reminder email.

[0054] In addition, when the "Send" button 118b is operated once on the document file approval function screen 112 for the setter shown in Figure 6 (A), the browser 111 may be configured to send the information directly to the server 130 without displaying the comment addition setting window 119. Furthermore, if the "Send" button 118b is operated once on the document file approval function screen 112 for the setter shown in FIG. 6(A) and then the "No" button is operated on the comment addition / non-addition setting window 119, the browser 111 determines that a send operation has been performed and proceeds to step S5.

[0055] In step S5, as a request notification step (notification step), the server 130 transmits a request notification email ML1 as an example of a notification of an approval request to the approver terminal 120, which is the second user terminal that is the approver. Then, as shown in FIG. 7(B), the approver terminal 120 receives the request notification email ML1 from the server 130, and the browser 121 of the approver terminal 120 displays the received email, the request notification email ML1, as a webmail browser.

[0056] In step S6, as a step of determining whether or not there has been access to the server 130 from the approver terminal 120, which is the second user terminal, it is determined whether or not a predetermined URL has been input into the approver terminal 120 and an operation to access the server 130 has been performed. Here, the request notification email ML1 includes, as an example, a "Check document" button ML1a to which a predetermined URL is linked. When the approver clicks the "Check Document" button ML1a, the approver terminal 120 accesses the server 130, and the browser 121 of the approver terminal 120 displays a login window LW. The information on the comment content entered by the settler (see FIG. 6(B)) may be configured to be included in the content of the request notification email ML1.

[0057] It is assumed that the approver enters a login ID and password in the login window LW and operates the login button. Then, the browser 121 of the approver terminal 120 sends an HTTP request to the server 130. In this way, if the browser 121 determines that an access operation has been made from the approver terminal 120 to the server 130, the process proceeds to step S7, but if it determines that no access operation has been made yet, step S6 is repeated.

[0058] In step S7, as shown in FIG. 8(A), as a document file content display step, the approver terminal 120, which is the second user terminal, accesses the server 130, and the browser 121 of the approver terminal 120 displays the contents of the document file DF. More specifically, the browser 121 of the approver terminal 120 displays a document file approval function screen 122 for the approver. The approver document file approval function screen 122 is provided with an approver information GT display area 123, a document display area 125, and an "Agree to the contents of this document" button 127.

[0059] Of these, the approver information GT display area 123 displays approver information GT and the approver's status information ST. In addition, the document display area 125 displays the contents of the document file DF. If the setting does not require the approver to stamp (seal impression SP) or sign (handwritten signature HR, handwritten-style signature SN, etc.), the approver confirms the contents and then operates the "I agree to the contents of this document" button 127 to perform the approval operation.

[0060] On the other hand, if the setting requires the approver's seal (seal impression SP) or signature (handwritten signature HR, handwritten-style signature SN, etc.), approval fields such as approval seal field SA1 and approval signature field SA2 are placed on the layout of the document file DF. The document file DF displayed in the document display area 125 may be configured to display approval fields such as the approval stamp field SA1 and the approval signature field SA2 for all set approvers, but it may also be configured to display only the approval fields set for that approver based on the approver information GT and the login ID information at the time of login. Furthermore, the locations of approval fields such as the approval seal field SA1 and the approval signature field SA2 can be freely determined by the person who sets the field, and therefore may be difficult for the approver to understand at a glance.

[0061] Therefore, the approver document file approval function screen 122 is provided with a seal place display button 124 . As shown in Figure 8(A), when the approver operates the stamp location display button 124, the browser 121 is configured to highlight the approval fields such as the approval stamp field SA1 and the approval signature field SA2 assigned to the approver on the layout of the document file DF based on the allocation information of the approval fields such as the approval stamp field SA1 and the approval signature field SA2.

[0062] In other words, in the document file approval function screen 112 for the configurator, which is the specified document approval setting screen of the configurator terminal 110, which is the first user terminal, if the signature (handwritten signature HR, handwritten-style signature SN, etc.) and seal (seal impression SP) setting checkbox 116, which is a setting field for specifying whether the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required, and the signature (handwritten signature HR, handwritten-style signature SN, etc.) and seal (seal impression SP) are required, are not checked, then the browser 121 of the approver terminal 120, which is the second user terminal, will display the seal location display button 124 when it displays the contents of the document file DF. When the stamp location display button 124 is operated, the browser 121 of the approver terminal 120, which is the second user terminal, is configured to highlight the approval stamp field SA1 and approval signature field SA2 as approval fields for the approver on the layout of the document file DF.

[0063] As a result, when the seal place display button 124 is operated, the approval column for that approver is highlighted. As a result, the second user, who is the approver, can easily understand which part to operate to input either a seal (seal impression SP), a handwritten signature HR, a keyboard-input name signature (handwritten-style signature SN), a keyboard-input name text (name data NM), or an approval mark MK. In addition, if the configuration is such that approval fields such as the approval stamp field SA1 and the approval signature field SA2 for all the set approvers are displayed, when the stamp location display button 124 is operated, the browser 121 may be configured to highlight only the approval field set for that approver based on the login ID information at the time of login.

[0064] Then, as shown in Figure 8(B), when the approver selects the assigned approval field, such as the approval stamp field SA1 or the approval signature field SA2, by clicking or the like, the browser 121 displays a stamp creation window 126, which is an example of a stamp / signature creation window. Here, if multiple approval fields such as approval stamp field SA1 and approval signature field SA2 are set, when the approval field set for that approver is selected based on the login ID information at the time of login, browser 121 displays stamp creation window 126, which is an example of a stamp / signature creation window, and when the approval field set for another approver is selected, the stamp / signature creation window is not displayed, and instead a message such as "This is for another approver!" may be displayed.

[0065] The seal creation window 126 is provided with a name input field 126a, a "Create Seal Image" button 126b, a seal image display field 126c, and a "Stamp" button 126d. When the approver enters name information in the name input field 126a and operates the "Create Seal Image" button 126b, the browser 121 creates a seal impression SP based on the name information and today's date information, and the created seal impression SP is displayed in the seal image display field 126c. If the seal impression SP is acceptable, the approver operates the "Seal" button 126d, and the seal impression SP is entered and displayed in the approval seal field SA1.

[0066] In addition, depending on whether the setter has set any of the following items on the document file approval function screen 112 for the setter: stamp (seal impression SP) item 116a, handwritten signature HR item 116b, keyboard-input name signature (handwritten-style signature SN) item 116c, keyboard-input name text (name data NM) item 116d, and approval mark MK item 116e, when the approval field is selected on the document file approval function screen 122 for the approver, the browser 121 is configured to display a seal / signature creation window according to the setting. For example, when the approval seal field SA1 is selected, the browser 121 displays a seal creation window 126 to create a seal impression SP. Similarly, when the approval signature field SA2 is operated, the browser 121 displays a handwritten-style signature creation window in order to create a handwritten-style signature SN.

[0067] More specifically, as shown in FIG. 9(A), if the user has set the handwritten signature HR item 116b on the document file approval function screen 112 for the user, when the approval field is selected on the document file approval function screen 122 for the approver, the browser 121 is configured to display a handwritten signature creation window according to the setting. The approver then inputs the information by handwriting using a mouse or touch panel. This will create a handwritten signature HR.

[0068] Also, as shown in FIG. 9(B), if the scribble user has set the keyboard-input name signature (handwritten-style signature SN) item 116c on the document file approval function screen 112 for the scribble user, when the approval signature field SA2 is selected on the document file approval function screen 122 for the approver, the browser 121 is configured to display a handwritten-style signature creation window according to the setting. The approver then inputs character information such as alphabets or Chinese characters using a keyboard. The browser 121 then creates signature data in a font (typeface) that looks like a handwritten signature.

[0069] Furthermore, as shown in FIG. 9(C), if the setter has set the item 116d of keyboard-input name text (name data NM) on the document file approval function screen 112 for the setter, when the approval name field is selected on the document file approval function screen 122 for the approver, the browser 121 is configured to display a name creation window according to the setting. The approver then inputs character information such as alphabets or Chinese characters using a keyboard. Then, the browser 121 creates the name data NM in a predetermined font (typeface).

[0070] Also, as shown in FIG. 9(D), if the approval mark MK item 116e has been set by the configurator on the document file approval function screen 112 for the configurator, when the approval mark field is selected on the document file approval function screen 122 for the approver, the browser 121 is configured to display an approval mark input confirmation window according to the setting. The approver then operates the "Yes" button. Then, the browser 121 inputs and displays a predetermined approval mark MK in the approval mark field.

[0071] In step 8, as shown in Figures 10(A) and 10(B), the browser 121 determines whether or not the "I agree to the contents of this document" button 127 has been operated as a step for determining whether or not an approval operation has been performed, including a signing operation or a stamping operation depending on the setting of whether or not the second user's signature (handwritten signature HR, handwritten-style signature SN, etc.) or stamp (seal impression SP) is required. More specifically, if there is no seal (seal impression SP) or signature (handwritten signature HR, handwritten-style signature SN, etc.), it is determined whether the approver has operated the "I agree to the contents of this document" button 127. On the other hand, if a seal (seal impression SP) or signature (handwritten signature HR, handwritten-style signature SN, etc.) is present, it is determined whether the "I agree to the contents of this document" button 127 is operated after the approver has performed the seal (seal impression SP) or signature (handwritten signature HR, handwritten-style signature SN, etc.) operation.

[0072] For example, as shown in FIG. 10(A), when the approver operates the “I agree to the contents of this document” button 127 on the approver document file approval function screen 122, the browser 121 displays, as an example, a setting window 128 for whether or not to add a comment. If the approver wants to add a comment to other lower approvers or the person who set the return regarding the order, he / she operates the "Yes" button. Then, as shown in FIG. 10(B), a comment input field 128a is displayed at the bottom of the approver document file approval function screen 122, allowing comments to be freely input. The contents of the comment are displayed in a notification email to a person lower in the order, a completion email, the document file approval function screen 122 for the approver, and the document file approval function screen 112 for the settler. If a higher ranking setter or approver has entered a comment, the comment is displayed near the comment input field 128a.

[0073] Then, when the approver inputs a comment and operates the "I agree to the contents of this document" button 127, the browser 121 determines that an approval operation has been performed. In this way, if it is determined that an approval operation has been performed, the process proceeds to step S9, and on the other hand, if it is determined that an approval operation has not been performed yet, step S8 is repeated. At this time, the browser 121 transmits information on the approver document file approval function screen 122 to the server 130.

[0074] In step S9, as a status change step, the server 130 changes the status to approved. Then, as shown in FIG. 11(A), in the setting and display area 114 for the approver information GT on the approver document file approval function screen 122, the status information ST is changed from "Stamping" to "Stamped" in correspondence with the approver information GT.

[0075] Furthermore, approval date and time information ST1 is also displayed. In other words, the browser 121 of the approver terminal 120, which is the second user terminal, displays the contents of the document file DF, and the server 130 is configured to change the status to approved based on an approval operation including an input operation by the approver, which is the second user, according to any of the settings selected and set by the setter terminal 110, which is the first user, such as a seal (seal impression SP), a handwritten signature HR, a keyboard-input name signature (handwritten-style signature SN), a keyboard-input name text (name data NM), or an approval mark MK.

[0076] This allows the first user, who is the setter, to freely select and set one of the following for the second user, the approver: a seal (stamp SP), a handwritten signature HR, a keyboard-input name signature (handwritten-style signature SN), a keyboard-input name text (name data NM), or an approval mark MK. As a result, the person setting up the system can easily set the input of the approver's seal (seal impression SP), handwritten signature HR, keyboard-input name signature (handwritten-style signature SN), keyboard-input name text (name data NM), or approval mark MK as needed.

[0077] In addition, on the document file approval function screen 122 for the approver shown in Figure 10 (A), once the ``I agree to the contents of this document'' button 127 is operated, the browser 121 may be configured to send the information directly to the server 130 without displaying the comment addition setting window 128. Furthermore, if the "I agree to the contents of this document" button 127 is operated once on the document file approval function screen 122 for the approver shown in Figure 10 (A) and then the "No" button is operated in the comment addition / non-addition setting window 128, the browser 121 determines that an approval operation has been performed and proceeds to step S9.

[0078] The operations of the second approver (John Smith) are similar to those of the first approver (Nao Takagi), so a detailed explanation will be omitted. Then, based on the approval operations of all approvers, the server 130 changes the status to completed. At the same time, in a completion notification step (notification step), server 130 transmits completion notification email ML2 as an example of a completion notification to settler terminal 110, which is the first user terminal that is the settler. Then, as shown in FIG. 11(B), the setter terminal 110 receives the completion notification email ML2 from the server 130, and the browser 111 of the setter terminal 110 displays the received email, the completion notification email ML2, as a webmail browser. The information on the comment content entered by the approver (see FIG. 10(B)) may be configured to be included in the content of the request notification email ML2. It may also be configured so that other approvers are notified.

[0079] Here, the completion notification email ML2 includes, as an example, a "Check document" button ML2a to which a predetermined URL is linked. When the setter clicks on the "Check Documents" button ML2a, the setter terminal 110 accesses the server 130, and the browser 111 of the setter terminal 110 transmits an http request to the server 130. 12(A), the setter terminal 110, which is the first user terminal, accesses the server 130, and the browser 111 of the setter terminal 110 displays a document file approval function screen 112 for the setter.

[0080] As shown in the setting and display area 114 for the approver information GT, all of the status information ST corresponding to the approver information GT is set to "sealed." In addition, in the document file DF displayed in the document display area 117, a seal impression SP is displayed in the approval stamp field SA1, which is a pre-set approval field, and a handwritten-style signature SN is displayed in the approval signature field SA2.

[0081] As a result, as described above, the setting person, who is the first user, can freely set whether or not the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required. As a result, the person setting the setting can easily set whether or not the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required, as needed.

[0082] As shown in FIG. 12(B), the document file approval function screen 112 for the settler displays a display switching filter item FL. When the user selects a desired display switching filter item FL, a list of case information AN that satisfies the filter condition is displayed. The case information list AN is configured to display status information ST for each case. This makes it easy to see which items have been completed and which items are in the process of being stamped.

[0083] The document file approval system 100 thus obtained as an embodiment of the present invention includes a scribbling person terminal 110 which is a first user terminal as an example of a plurality of user terminals, an approver terminal 120 which is a second user terminal, and a server 130. The scribbling person terminal 110 which is the first user terminal accesses the server 130, and a browser 111 of the scribbling person terminal 110 which is the first user terminal displays a scribbling person document file approval function screen 112 which is a predetermined document approval setting screen. In the scribbling person document file approval function screen 112, a document file DF is approved. A drag-and-drop area 113a as a setting field, a setting and display area 114 for approver information GT as a setting field for approver information GT, and a signature (handwritten signature HR, handwritten-style signature SN, etc.) and seal (seal impression SP) presence / absence setting check box 116 as a setting field for whether or not the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required are provided, and when a document file DF is specified on a document file approval function screen 112 for a scrivener of a scrivener terminal 110, which is a first user terminal, When an upload operation is performed, a setting operation for the approver information GT is performed, a setting as to whether the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required is selected, and a send operation is performed, server 130 sends a notification of an approval request to the second user terminal who is the approver, and based on the access operation of the second user approver, approver terminal 120, which is the second user terminal, accesses server 130, and the browser 121 of approver terminal 120, which is the second user terminal, displays the contents of the document file DF on the approver's document file approval function screen 122, and based on the approval operation including a signing operation or a seal operation in accordance with the setting as to whether the second user approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required, server 130 changes the status to approved, and based on the approval operations of all approvers, server 130 changes the status to completed.This configuration allows the setting person to easily set whether the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required as needed.

[0084] Furthermore, in the document file approval function screen 112 for the scribble user terminal 110, which is the first user terminal, in the check box 116 for setting whether or not the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required, if the check box 116 is unchecked and a signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required, one of the items 116e of seal (seal impression SP), handwritten signature HR, keyboard-input name signature (handwritten-style signature SN), keyboard-input name text (name data NM), and approval mark MK is selectably displayed, and the browser 116 of the approver terminal 120, which is the second user terminal, is displayed. 21 displays the contents of the document file DF on the approver's document file approval function screen 122, and the server 130 changes the status to approved based on the approval operation including the input operation of the approver, who is the second user, according to any of the settings selected by the first user, who is the setter, such as a seal (seal impression SP), handwritten signature HR, keyboard-input name signature (handwritten-style signature SN), keyboard-input name text (name data NM), or approval mark MK.This allows the setter to easily set the input of any of the approver's seal (seal impression SP), handwritten signature HR, keyboard-input name signature (handwritten-style signature SN), keyboard-input name text (name data NM), or approval mark MK as needed.

[0085] In addition, in the check box 116 for setting whether or not the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required, if the check box 116 is unchecked and a signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required, one of the items 116e, name seal (seal impression SP), handwritten signature HR, keyboard input name signature (handwritten-style signature SN), keyboard input name text (name data NM), and approval mark MK, is displayed for selection, and the selected item is displayed in the document file for the setter. The layout of the document file DF displayed on the document approval function screen 112 can be freely set by dragging and dropping, and when a send operation is performed, the server 130 sends a request notification email ML1, which is a notification of the approval request, to the approver terminal 120, which is the second user terminal of the approver.This allows the person setting the approval mark MK to select and set one of a seal (seal impression SP), handwritten signature HR, keyboard-input name signature (handwritten-style signature SN), keyboard-input name text (name data NM), and approval mark MK depending on the content of the document file DF, and can also freely set its position.

[0086] Furthermore, on the document file approval function screen 112 for the setter, there are setting operations for a plurality of approver information GT, and when any of the items 116e, name stamp (seal impression SP), handwritten signature HR, keyboard-input name signature (handwritten-style signature SN), keyboard-input name text (name data NM), and approval mark MK, are set in a plurality of positions by drag-and-drop operation on the layout of the document file DF displayed on the document file approval function screen 112 for the setter, when an approval stamp field SA1 or approval signature field SA2, which is an example of one arranged field, is selected for each position, the browser 111 of the setter terminal 110 displays one of the plurality of approver information GT in the allocation setting window 117a, allowing for flexible allocation setting, so that each approver can easily understand into which approval field they should enter either the seal (seal impression SP), handwritten signature HR, keyboard-input name signature (handwritten-style signature SN), keyboard-input name text (name data NM), or approval mark MK, and it is possible to prevent the approver from making a mistake in entering information into the approval field.

[0087] In addition, in the document file approval function screen 112 for the scribble user terminal 110, which is the first user terminal, the signature (handwritten signature HR, handwritten-style signature SN, etc.) and seal (seal impression SP) presence setting check box 116, which is a setting field for whether or not the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required, if the signature (handwritten signature HR, handwritten-style signature SN, etc.) and seal (seal impression SP) are required, when the browser 121 of the approver terminal 120, which is the second user terminal, displays the contents of the document file DF on the approver document file approval function screen 122, the seal impression location display button 1 24 is displayed, and when the stamp location display button 124 is operated, the browser 121 of the approver terminal 120, which is the second user terminal, is configured to highlight the approval stamp field SA1 and approval signature field SA2, which are examples of approval fields for the approver, which is the second user, on the layout of the document file DF on the approver document file approval function screen 122, so that the second user approver can easily understand which part to operate to enter either the stamp (seal impression SP), handwritten signature HR, keyboard-input name signature (handwritten-style signature SN), keyboard-input name text (name data NM), or approval mark MK.

[0088] Furthermore, the program of the document file approval system 100 according to the embodiment of the present invention is such that the scribing person terminal 110, which is the first user terminal, accesses the server 130, and the browser 111 of the scribing person terminal 110, which is the first user terminal, displays a drag-and-drop area 113a as a setting field for the document file DF, a setting and display area 114 for the approver information GT as a setting field for the approver information GT, and a signature (handwritten signature HR, handwritten-like signature SN, etc.) as a setting field for whether or not the approver's signature or seal (seal impression SP) is required. Steps S1 and S2 of displaying a document approval setting screen include steps S1 and S2 of displaying a document file approval function screen 112 for a configurator, which is a document approval setting screen provided with a check box 116 for setting whether or not to affix a signature (handwritten signature HR, handwritten-style signature SN, etc.) and a seal (seal impression SP), and steps S3 and S4 of displaying a document file approval function screen 112 for a configurator, which is a document approval setting screen provided with a check box 116 for setting whether or not to affix a signature (handwritten signature HR, handwritten-style signature SN, etc.) and a seal (seal impression SP). In the document file approval function screen 112 for a configurator terminal 110, which is a first user terminal, a document file DF is specified and an upload operation is performed, a setting operation for the approver information GT is performed, and a setting for whether or not to affix the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or a seal (seal impression SP) is required is performed. The operation includes operation determination steps S3 and S4 in which it is determined whether or not a setting is selected and a transmission operation is performed; a notification step S5 in which the server 130 transmits a notification of the approval request to the approver terminal 120, which is the second user terminal of the approver; document file content display steps S6 and S7 in which the approver terminal 120, which is the second user terminal, accesses the server 130 based on the access operation of the approver, which is the second user terminal, and the browser 121 of the approver terminal 120, which is the second user terminal, displays the contents of the document file DF on the approver document file approval function screen 122; The server 130 changes the status to approved based on an approval operation including a signing operation or a sealing operation according to a setting of whether or not the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required, and the server 130 changes the status to completed based on the approval operations of all approvers. By causing the computer to execute status change steps S8 and S9, the setting person can easily set whether or not the approver's signature (handwritten signature HR, handwritten-style signature SN, etc.) or seal (seal impression SP) is required as needed.The effect is enormous. [Explanation of symbols]

[0089] 100 ··· Document file approval system 110: Setter terminal (first user terminal) 111 ··· Browser (on the user's device) 112 Document file approval function screen for configurator (prescribed document approval setting screen) 113 "Create a new document" button 113a Drag and drop area (document file settings) 113b··· Project title input field 113c··· "Create Document" button 114 Approver information setting display area (approver information setting field) 114a··· "Add New User" button 114b "Add from Address Book" button 115 Add User Settings Window 115a··· Email address input field 115b··· Name entry field 115c··· Company name input field 116 ··· Signature / Seal Setting Checkbox (Setting field for whether or not the approver's signature or seal is required) 116a··· Stamping items 116b··· Handwritten signature item 116c··· Keyboard input name sign item 116d··· Keyboard input name text item 116e··· Approval mark items 117 Document display area (of the document file approval function screen for the configurator) 117a Allocation setting window 118a··· "Save" button 118b··· "Send" button 119 ··· Comment Addition / Deletion Setting Window (for the user) 119a Comment input field (on the document file approval function screen for the configurator) 120 ··· Approver terminal (second user terminal) 121 ··· Browser (on the approver's device) 122 Document file approval function screen for approvers 123 Approver information display area 124 ··· Stamp location display button 125 Document display area (of the approver's document file approval function screen) 126 ··· Mark creation window 126a··· Name input field 126b "Create Seal Image" button 126c··· Seal image display field 126d··· "Stamp" button 127 "I agree to the contents of this document" button 128 ··· Comment Addition Window (for approvers) 128a... Comment input field (on the approver's document file approval function screen) 130 Server DF Document file SA1: Approval stamp field (for the approver's signature or stamp, etc.) SA2: Approval signature field (for the approver's signature or seal, etc.) GT ··· Approver information ST Status information ST1: Approval date and time information RM ··· "Remind me" button SP ··· Impression SN ··· (handwritten style) signature HR ··· Handwritten signature NM... Named data MK ··· Approval Mark ML1 Request notification email ML1a... "Check documents" button (in the request notification email) LW ··· Login window ML2... Completion notification email ML2a... "Check documents" button (in the completion notification email) FL Display switching filter items AN ··· Project information list

Claims

1. A document file approval system that includes a plurality of user terminals and a server and approves the contents of a document file, A first user terminal accesses the server, and a browser on the first user terminal displays a predetermined document approval setting screen, and the predetermined document approval setting screen has a setting field for the document file, a setting field for approver information, and a setting field for whether the approver's signature or seal is required, When a document file is designated and an upload operation is performed on a predetermined document approval setting screen of the first user terminal, an operation for setting approver information is performed, a setting for whether or not the approver's signature or seal is required is selected, and a transmission operation is performed, the server transmits a notification of an approval request to the second user terminal that is the approver, According to the access operation of the second user, the second user terminal accesses the server, and the browser of the second user terminal displays the contents of the document file; A document file approval system characterized in that the server changes the status to approved based on an approval operation that includes a signing operation or a stamping operation depending on whether a second user's signature or stamping is required, and the server changes the status to completed based on the approval operations of all approvers.

2. In a setting field for determining whether or not the approver's signature or seal is required on a predetermined document approval setting screen of the first user terminal, if the setting field indicates that the approver's signature or seal is required, one of the following items is selectably displayed: seal, handwritten signature, keyboard-input name signature, keyboard-input name text, and approval mark; The document file approval system of claim 1, wherein the browser of the second user terminal displays the contents of the document file, and the server changes the status to approved based on an approval operation by the second user including an input operation by the first user according to any of the following settings: a seal by the first user, a handwritten signature, a keyboard-input name signature, a keyboard-input name text, or a selected approval mark.

3. In a setting field for determining whether or not the approver's signature or seal is required, if required, one of the following items is displayed for selection: seal, handwritten signature, keyboard-input name signature, keyboard-input name text, and approval mark, and the selected item is displayed for free placement and setting by drag-and-drop operation on the layout of the document file displayed on a predetermined document approval setting screen; 3. The document file approval system according to claim 2, wherein when the sending operation is performed, the server sends a notification of an approval request to a second user terminal that is the approver.

4. On the predetermined document approval setting screen, there is a setting operation for multiple approver information, The document file approval system of claim 3, characterized in that when any of the items of the seal, handwritten signature, keyboard-input name signature, keyboard-input name text, and approval mark are arranged and set by drag-and-drop operation on the layout of the document file displayed on a specified document approval setting screen, when one arranged field is selected for each arrangement, the browser of the first user terminal displays one of the multiple approver information items and allows for flexible assignment and setting.

5. In a setting field for whether or not the approver's signature or seal is required on a predetermined document approval setting screen of the first user terminal, if the setting field is set to "yes," a seal location display button is displayed when the browser of the second user terminal displays the contents of the document file; A document file approval system as described in any one of claims 1 to 4, characterized in that when the stamp location display button is operated, the browser of the second user terminal highlights the approval column for the second user on the layout of the document file.

6. A document file approval system program for approving the contents of a document file, a predetermined document approval setting screen display step in which the first user terminal accesses the server and the browser of the first user terminal displays a predetermined document approval setting screen having a setting field for the document file, a setting field for approver information, and a setting field for whether or not the approver's signature or seal is required; an operation determination step of determining whether or not a document file is designated and an upload operation is performed on a predetermined document approval setting screen of the first user terminal, an operation for setting approver information is performed, a setting for whether or not the approver's signature or seal is required is selected, and a transmission operation is performed; a notification step in which the server sends a notification of an approval request to a second user terminal that is the approver; a document file content display step in which the second user terminal accesses the server based on the access operation of the second user, and the browser of the second user terminal displays the content of the document file; A program for a document file approval system, characterized in that the program causes a computer to execute a status change step in which the server changes the status to approved based on an approval operation including a signing operation or a stamping operation according to a setting as to whether or not a signature or stamping by a second user is required, and the server changes the status to completed based on the approval operations of all approvers.

Images