JP5499388B2 - Compiler for document, validation check and development document creation and deliberation system using it - Google Patents

Description

  The present invention relates to an approval system.

In recent years, digitalization of documents exchanged in the company and organizations has progressed, and there are many cases where documents are approved and approved electronically.
It is necessary to pre-determine what format the document should follow and what route should be approved and approved for each document format when digitizing and electronically approving and finalizing the document. Become.

  In the conventional technology, middleware for document digitization was introduced to define the format of documents, and system administrators etc. designed database definitions and input screens using a dedicated graphical design tool attached to the middleware. .

  The approval / decision path is graphically described by BPEL or a business process description language having the same ability. This description is generally described for each document format by the system administrator, or is generally selected by a general user when creating the document.

JP 2004-246516 A JP 2007-072692 A

  The definition of document formats is usually realized by creating individual formats using a dedicated graphical tool. For this reason, the user has to define a large number of styles, and even if minor styles are modified, some of the graphical dedicated tools do not take the effort of modification into account, and all applicable All the forms had to be individually corrected, and it was difficult for the users to reuse the data by correction.

  In addition, when adding requirements necessary for use in a company such as wanting to embed check logic of the company's own numbering system in the screen, such a screen cannot be created because it is not normally assumed by dedicated tools The problem was that it was difficult to define even if possible. For this reason, it has been a common practice for users to make large-scale modifications called customizations and use them at great cost for practical use. When such modifications are made, if there is an organizational change or a member change, and if the customized part does not take such changes into account, it will not be possible to respond adequately or even more As a result, it is necessary to spend a lot of time and time, and as a result, the operation cost further increases, or in some cases, it has become a factor that hinders organizational modification.

  Next, in the method of describing the approval route using a language such as BPEL, if all routes that can include exceptional routes such as skipping and proxy approval are not described for each style, it is operated. However, the cost of description is high because enormous work is required to describe all the exceptional paths in advance. In addition, when a change occurs in the organizational structure or members, the approval path defined for each form is reviewed. Even when a part of the organizational structure is modified, it is a method to describe an exceptional route. Therefore, a review of the entire approval route occurs, and the confirmation work after the modification must be performed over the entire approval route. Therefore, the problem is that the amount of confirmation work is enormous.

  As used herein, the term “decision” refers to the approval of a higher-level approver when the approver cannot be approved due to absence or the like. In addition, proxy approval refers to a case where a user in the same organization performs approval instead when approval cannot be performed due to the absence of an approver.

  In particular, when the system is large-scale, even a small specification change has a large range of influence, and the cost of system renovation increases exponentially.

  It is an object of the present invention to facilitate system development and modification by minimizing the creation and change of such document formats and approval paths.

  The present invention comprises means for storing organization information, means for storing a form, means for storing a deliberation document, and means for providing an input screen to a user, which is input to the input screen by the user. A request document is generated from the information and stored in the means for storing the request document.

  In this deliberation system, the form is defined by a form description language, includes a description of how to follow the organization information, and determines the approval route of the document based on the description of the way of tracing the organization chart included in the form. decide.

  In the organization information, the affiliation and the name are configured as separate records, and the organization information has an organization chart with a link to the affiliation in the name record. (Figure 2)

The format may include a definition of a new type combining existing types, and a program for displaying an item input by the user and a user input based on the definition of the existing type and the new type Automatically generate a program to check the values.
Here, the type is a data type for a value input by the user. For example, data types corresponding to “name” and “gender” are also a type. A type can be used in a document by defining the type in the document definition.

  The approval route is determined using an item input by the user or a plurality of items as parameters.

  The automatically generated program further generates a description of the style.

  The new type can set a domain.

  The new type defines the domain by defining the domain within the style or by querying an external database.

  The program for performing the check provides auxiliary data for user input to items input by the user.

  The format can further define a display method of items input by the user.

  As explained in the problem to be solved by the invention, the input screen is defined by defining the new type using the existing type as the basis, and using the existing type only when necessary, and describing the document structure. And check logic can be automatically generated, and the approval route can be automatically generated by defining only the minimum necessary changes based on the organization chart for the approval route. Compared with this workflow engine, the amount of program description is greatly reduced, so that the system construction cost is reduced and the construction speed is improved.

  In addition, by describing the type and approval path using a language, it is possible to make changes related to a number of styles at the same time as compared to the one realized using a graphical user interface when a large number of styles are prepared. This can reduce the maintenance time and costs associated with the change.

  In addition, since the organization chart has separate records for affiliation and name, it is only necessary to change the record of the name when there is a change in personnel, which has the effect of reducing correction work at the time of change. The affiliation has a link to another affiliation in the affiliation record and a link to the affiliation in the name record in order to represent the hierarchical structure of the affiliation.

  In addition, the knowledge of documents and workflows can be described in a form that is almost different from the terms and knowledge used in the company or organization by using the language, and the user can easily check the form, so the user's confirmation work effort This has the effect that it can be reduced.

  Further, the use of the language has the effect of reducing the cost of system construction, which requires no knowledge about advanced RDB or the like and enables system construction from the user's perspective.

  In addition, since the validation check logic for the new type is automatically generated from the definition of the new type, it is not necessary to write a validation servlet, and the development cost can be reduced.

  In addition, since it is possible to operate the determination of the entire approval route by the organization chart and the policy, it is possible to cope with various approval systems.

  Here, a policy is a kind of rule that is taken into consideration in determining an approval route, and is defined in an organization chart or style.

  In the organization chart, a policy for operating the determination of the approval route of the document can be defined. This policy is taken into account when determining the approval path of a document according to the language. The language can also change the policy.

  In addition, since the organization chart, document format, new type definition, approval policy, individual input screens for each format, and check logic are automatically generated and used, the dependency of information used when creating documents There is an effect that the system is easily scaled out according to the scale.

  In order to realize the present invention, an organization chart that is organization information and a language having the ability to describe a format are prepared. Here, the format is defined as a basis for the user to create a document as a final product. A style is sometimes called a template.

  Any language can be used for describing the organization chart, but XML is used in this embodiment. In the XML describing this organization chart, the root element is an organization chart element 301, the organization chart element 301 has one or more organization elements 302, and the organization element 302 has zero or more organization elements 302 and one or more job titles. The element 304 has one or more user elements 305. At this time, if the post element 304 is a representative of the organization to which the post element 304 belongs, the post element has a representative attribute 306. As described above, the organization chart is expressed by XML corresponding to the hierarchical structure of the actual organization. (Figure 3)

  As an attribute 303 of the organization element 302 of the organization chart, whether or not compulsory approval and proxy approval are possible is described with a true / false value (FIG. 3). This is the approval policy for the entire organization.

  Any language may be used to describe the style, but in this embodiment, a dedicated language (style description language) is used. As the format, an approval route definition 402, a new type definition 403, and a document structure definition 404 can be described. The approval path definition 402 can describe whether or not compulsory approval and proxy approval can be made as the approval policy definition 401. The approval route definition 402 can describe delegation of authority and addition of a route to the organization chart. New type definition 403 defines a new type using an existing type or a new type already defined. The document structure definition 404 describes a hierarchical structure of items constituting the document, and an existing type or a new type defined is applied to the item. The initial input value can be specified for the items constituting the document. (Fig. 4)

  A new type can limit the range of values for an existing type, combine the types into a new type, and change only the name without changing the type definition. There are two ways to limit the range: the regular expression and the enumeration value when the text type is used. For numeric types, there are a method of specifying enumerated values and a method of specifying a domain.

  The generated input screen is HTML, and the check logic is a servlet that can be executed by the application server.

  In addition, a device 501 that interprets this language and generates an HTML that is an input screen and a servlet that is a check logic, a server 502 that stores an organization chart and a format, a Web server 503 that distributes the generated HTML, and a servlet An application server 504 that executes and returns a result, a Web browser 505 that displays HTML, and a device 506 that stores documents are prepared (FIG. 5). Existing types are defined within device 501.

  In addition, the logic 201 called when the contents of the input form of the input screen HTML are changed and the logic 202 called when the document is submitted from the input screen HTML are stored in the Web server 503 that distributes the generated HTML. The logic 201 has a function of detecting a change in the content of the input form, asynchronously transmitting the content of the input form at that time to the application server 504 that executes the servlet and returns the result, and reflects the result on the input screen. The logic 202 has a function of creating XML representing a document from the contents of the input form on the input screen HTML and transmitting it to the device 506 for storing the document.

When the user saves the organization chart and the form in the organization chart and the server 502 for saving the form, the apparatus 501 is activated. (Fig. 5 ( 1 ))

  If there is a new type in the style, the device 501 decomposes it into the existing type and generates a new check logic corresponding to the new type using the check logic prepared for the existing type and the added restrictions. Create an executable servlet.

  The device 501 replaces the format definition with an HTML block element 601 and includes the format name in the attribute value of the block element 601. The document structure of the form is interpreted and replaced with a predetermined HTML block element 602. At this time, the item name is included in the attribute 603 of the block element 602. If the type assigned to the item of the document structure is an existing type, it is replaced with an HTML input form element 604 prepared for the existing type. If the type is a new type, it is decomposed into an existing type and similarly replaced with an HTML element 604. (Fig. 6)

  If the approval policy is described in the form, the apparatus 501 takes precedence over the approval policy of the organization chart and sets it as the approval policy of the form.

  If there is a statement that authority is delegated in the form, the device 501 assigns an attribute for delegating authority to the corresponding position, and creates a new organization chart of the form. For example, if the president's authority is delegated to the business manager, an attribute for delegating the president's authority is assigned to all business managers in the organization chart. This definition is valid for documents created based on this form.

  The apparatus 501 changes the tree structure of the organization chart if the form indicates that approval by another department is required. For example, if approval by the accounting manager and the accounting section manager is required before the approval of the department manager, an approval path by the accounting staff and the accounting section manager is added to the hierarchy immediately below all department managers in the organization chart.

  The apparatus 501 replaces the changed organization chart with an HTML block element 701. At this time, the element name of each element constituting the organization chart is described in the attribute 702 of the block element 701. All the attributes of each element constituting the organization chart are replaced with the attributes of the block element 701. (Fig. 7)

  The apparatus 501 generates an input screen HTML from an element 602 whose document structure is replaced and an element 701 whose organization chart is converted. Also, a logic 201 called when the contents of the input form are changed and a link to the logic 202 called when the document is submitted are output together.

The apparatus 501 stores the generated input screen HTML in the Web server 503 and the generated servlet in the application server 504. ( Fig.5 ( 2 ) , ( 3 ))

When the user accesses the Web server 503 using the Web browser 505 and acquires the input screen HTML and the logic 201 and the logic 202, the input screen HTML acquired by the Web browser 505 is displayed. (Figure 4 ( 4 ))

The user inputs necessary information on the input screen. (Figure 5 ▲ 5 ▼)

When the input value is changed, the Web browser 505 asynchronously transmits the changed input value to the check logic servlet of the application server 504 using the logic 201 implemented in the XML_Http_Request of Javascript, and checks the input value. . (Fig. 5 ( 6 )) If there is a problem with the value, an error is displayed. At this time, the type name is used as a key for specifying the check logic. As a form of error display, a warning is given using a dialog box, a warning is given by changing the color of the element of the form for the input value, or a warning is given by changing attribute values such as the color and shape of the block element.

  When the user inputs all necessary items and clicks the submit button, the Web browser 505 executes the logic 202 linked from the input screen HTML.

  The logic 202 converts an HTML block element 602 representing a document structure into an XML element 801. At this time, the attribute 603 of the block element 602 is used as the element name of the XML element 801. Also, the input form element 604 converts to an XML element 802 and uses the value input to the input form element 604 as the content 803 of the XML element 802. (Fig. 8)

  The logic 202 searches the block element 701 representing the organization chart in the input screen HTML for a user having the same user id of the user, and sets a route traced higher from the user along the hierarchical structure of the tree as an approval route. The position and user to which the organization and representative attributes are assigned are respectively replaced with the XML approval-scheduled person element 901, the position element 902, and the user element 903, and XML representing the approval route is generated. XML representing a document is generated according to the above rules. (Fig. 9)

  The logic 202 creates a scheduled creator element 905 with the user as a scheduled creator, and describes a job title element and a user element below the scheduled creator element 905. In addition, the user who has been created is described as a creator element 906, and the date and time of creation is described as a creation date and time element 907 below the planned creator element 905.

The logic 202 generates a document XML from the XML representing the document and the XML representing the approval path, and transmits the document XML to the device 506 for storing the document. (Fig. 5 ▲ 7 ▼ )

The device 506 calls the check logic servlet of the server 104 and checks the document XML. ( Fig.5 ▲ 8 ▼ )

If there is no problem with the document XML, the document is saved. (Figure 5 ( 9 ))

  The hardware configuration is described as a plurality of servers, but of course, it may be implemented as a single server, and it is not denied that the server is configured with a plurality of housings.

  In Example 1, the detailed method of calculating | requiring an approval path | route from an organization chart is shown.

  If no approval route setting is described in the form, the route from the organization to which the user creating the document belongs to the highest organization is the approval route, and the representative of each organization on this route is the approver. Become. (Fig. 10)

  The representative may be an attribute value indicated by a length, or another attribute value that is a representative may be determined.

  In the first embodiment, a detailed method for obtaining an approval route from an organization chart when authority is delegated will be described.

  If it is described in the form that the authority of the user A is transferred to the user B as the setting of the approval route, if the user B approves, it is considered that the user A has also been approved. When user A is an intermediate approver, from the organization that belongs to user B to the organization to which user A belongs in the route traced from the organization to which the user creating the document belongs to the highest organization Routes other than are approved routes. When the user A is the final approver, that is, the head of all organizations, the route traced from the organization to which the user creating the document belongs to the organization to which the user B belongs is set as the approval route. The representative of each organization on this approval path becomes the approver. (Fig. 11)

  In Example 1, when the approval of another organization is required, the detailed method of calculating | requiring an approval path | route from an organization chart is shown.

  If the approval path is set in the form and it is described that the approval of another organization WW is necessary before the post J approves, the approval path including the organization K is added to the organization chart. First, a route traced from the organization K to the highest organization is defined as a route L. At this time, if there is authority delegation setting on the path L, the delegator is removed from the path as shown in the third embodiment. A route L is added in front of the organization to which the post J belongs, and a route traced from the organization to which the user creating the document belongs to the highest organization is set as the approval route. The representative of each organization on this route becomes the approver. (Fig. 12)

  In the first embodiment, a method for searching a stored document and identifying a document that the user must approve will be described.

  In addition to the apparatus defined in the first embodiment, an apparatus 507 for retrieving documents is prepared.

  The user uses the Web browser 505 to search for a document 507, and the user element of the user element that is a descendant of the approver element that does not have an approver element exists. A request is made to search for a document having an approver element having an approver element or a creator element having an author element at a lower level. The document search device 507 performs a search under the requested conditions and returns a list of documents that meet the conditions.

  In Example 1, a method for performing approval will be described.

  In addition to the devices defined in the first and fifth embodiments, a device 512 for approval is prepared. A screen 2701 for performing approval is prepared and stored in the Web server 503. The approval screen 2701 has a function of acquiring and displaying a document, a button for the user to approve, and a function of transmitting to the device 512 for approving the user's approval.

  The user acquires a list of documents to be approved by the method described in the fifth embodiment, and selects a document to be approved. The user passes the identifier of the document to be approved to the screen 2701 for approval, and displays the document to be approved on the screen 2701 for approval. When the user presses the approval button, the approval screen 2701 transmits the identifier and the user id to the device 512 for approval. The approving apparatus 512 specifies the document to be changed by the identifier, and searches for the user from the document. If the user exists as an approval candidate, an approver element 1302 and an approval date / time element 1303 are added below the approval candidate element 1301. (Fig. 13)

  In the first embodiment, a method for performing return sending will be described. Send back means that the approver does not approve the document but instructs the document creator to re-create the document.

  In addition to the devices defined in the first and fifth embodiments, a device 513 for changing the approval route is prepared. Also, a screen 2702 for sending back is prepared and stored in the Web server 503. A screen 2702 for sending back a document includes a function for acquiring and displaying a document, a button for the user to send back, a function for changing the approval route of the document by the user's return, and a device 513 for changing the approval route of the changed approval route. With the ability to send to.

  The user acquires a list of documents that can be approved by the method described in the fifth embodiment, and selects a document to be sent back. The user passes the identifier of the document to be sent back to the screen 2702 for sending back, and displays the document on the screen 2702 for sending back. When the user presses the send back button, the send back screen 2702 searches the document for the user. If the user exists as a prospective approval person, a return person element 1402 and a return date / time element 1403 are added below the approval person element 1401. The screen 2702 for performing the return search searches the approver element, the approval date / time element, the creator element, and the creator date / time from the document, and deletes them if they exist (FIG. 14). The return screen 2702 transmits the identifier and the changed approval route to the device 513 for changing the approval route. The device 513 for changing the approval path specifies the document to be changed by the identifier, and changes the current approval path element described in the document to the approval path history element. Next, a new approval route changed to the document is added.

  The creator of a document can identify the returned document by searching for a document for which the author is a creator and who does not have a creator element below the planned creator.

  In the first embodiment, a method of changing the approval route at the time of approval will be described.

  In addition to the devices defined in the first and fifth embodiments, a device 513 for changing the approval route is prepared. A screen 2703 for changing the approval route is prepared and stored in the Web server 503. A screen 2703 for changing the approval path is a function for acquiring and displaying a document, a function for displaying the approval path of the document, a function for adding a path to the displayed approval path, and the user confirming the change of the approval path. A button and a function of transmitting the changed approval route to the device 513 for changing the approval route.

  The user obtains a list of documents that can be approved by the method described in the fifth embodiment, and selects a document whose approval route is to be changed. The user passes the identifier of the document for selecting the approval path to the screen 2703 for changing the approval path, and displays the document and the approval path on the screen 2703 for changing the approval path. When the user adds an approval route on the screen, the screen 2703 for changing the approval route also changes the approval route of the document. When the user presses the button for confirming the change of the approval route, the screen 2703 for changing the approval route transmits the identifier and the changed approval route to the device 513 for changing the approval route. The device 513 for changing the approval path specifies the document to be changed by the identifier, and changes the current approval path element described in the document to the approval path history element. Next, a new approval route changed to the document is added.

  In the first embodiment, a method for performing forced approval will be described. Forced approval refers to the approval of a document even if there is an unapproved user by the approval of a superior.

  In addition to the devices defined in the first embodiment, a device 507 for retrieving documents and a device 512 for approving documents are prepared. A screen 2701 for performing approval is prepared and stored in the Web server 503. The approval screen 2701 has a function of acquiring and displaying a document, a button for the user to approve, and a function of transmitting to the device 512 for approving the user's approval.

  The user is set to be able to forcibly approve the approval policy for the device 506 for searching for documents using the Web browser 505, and the user exists as a person who is scheduled to be approved. Request to search for documents with no elements. The document search device 506 performs a search under the requested conditions and returns a list of documents that meet the conditions.

  The user selects a document to be forcedly approved, passes an identifier of the document to be forcedly approved to a screen 2701 for approval, and displays the document to be approved on a screen 2701 for approval. When the user presses the approval button, the approval screen 2701 transmits the identifier and the user Id to the device 512 for approval. The approving apparatus 512 specifies the document to be changed by the identifier, and searches for the user from the document. If the user exists as an approval candidate, an approver element and an approval date / time element are added below the approval candidate element. Also, if there is an unapproved approval planner element between the user's approval planner element and the creator, an approver element and an approval date / time element are added under the approval planner element.

  In the first embodiment, a method for performing proxy approval will be described. Proxy approval means that if an approver cannot be approved due to absence or the like, a user in the same organization performs approval instead.

  In addition to the apparatus defined in the first embodiment, an apparatus 507 for retrieving documents, an apparatus 511 for referring to an organization chart, and an apparatus 512 for approval are prepared. A screen 2701 for performing approval is prepared and stored in the Web server 503. The approval screen 2701 has a function of acquiring and displaying a document, a button for the user to approve, and a function of transmitting to the device 512 for approving the user's approval.

  The user makes an inquiry to the device 511 that refers to the organization chart, and acquires his or her belonging name. The user uses the Web browser 505 to set the approval policy proxy approval to the device 507 for searching for documents, and his / her affiliation name matches the affiliation person's affiliation name. Request to search for documents whose approver element does not have an approver element. The document search device 507 performs a search under the requested conditions and returns a list of documents that meet the conditions.

  The user selects a document to be subjected to proxy approval, passes the identifier of the document to be proxy approved to the screen 2701 for approval, and displays the document to be approved on the screen 2701 for approval. When the user presses the approval button, the approval screen 2701 transmits the identifier, the affiliation name, and the user id to the device 512 that performs the approval. The approving apparatus 512 specifies the document to be changed by the identifier, and searches for the affiliation name from the document. If the affiliation name exists as a prospective approver, an approver element and an approval date / time element are added below the approval candidate element.

  In the first embodiment, a method of delegating authority when creating a document will be described.

  When the device 501 generates the input screen HTML, in addition to the logic 201 that is called when the contents of the input form are changed and the link to the logic 202 that is called when the document is submitted, logic for setting delegation of authority The link to 203 is output. The logic 203 stores the generated HTML in the Web server 503 that distributes the generated HTML. The logic 203 has a function of displaying the approval path of the input screen HTML and a function of setting authority delegation to the approval path of the input screen HTML.

  The user displays the input screen HTML on the Web browser 505. The user calls the logic 203 to display the approval path of the document, and sets delegation of authority for the displayed approval path. The logic 203 changes the organization chart of the input screen HTML. Thereafter, a document is generated and stored by the method of the first embodiment. Since an approval path for a document is created based on the organization chart in which authority delegation is set, authority delegation can be set only for the document.

  Example 1 shows the detailed method of defining the format.

The format is defined by the following grammar.
docdef style name 2101 = {
Definition 2102
}

  The style name 2101 becomes a style identifier.

  The definition 2102 describes the type definition, document structure definition, item definition, and approval route definition shown in the thirteenth, fourteenth and fifteenth embodiments.

  Example 1 shows a detailed method for defining a type.

A new type is defined by the following grammar type type name 2102 = type description 2103

  The type name 2102 becomes an identifier of a new type, and the type description 2103 has four types: alias, alternative, multiple selection, and container. (Fig. 21)

An alias is the name of an existing type or the name of a new type that has been defined. If the name of an existing type is described as an alias, a new type with the same function as the existing type can be defined. When the name of a new type that has been defined is described, a new type with the same function as the new type that has been defined can be defined. (Fig. 21)

  An alternative is a type in which only one of a plurality of values can be selected. List strings enclosed in numbers or double quotes, separated by commas. (Fig. 21)

  The multiple selection is a type in which an arbitrary number of values can be selected from a plurality. List strings enclosed in numbers or double quotes in parentheses, separated by commas. (Fig. 21)

  A container is a type that can define a new one that combines existing types. List type names separated by commas between vertical bars. (Fig. 21)

A grammar called annotation is used to add restrictions such as required conditions to the type. Annotations can be written on the line before the type definition or after the type names listed when defining the container. Annotations are described as follows.
@Annotation name (argument 1, ..., argument n)

  Annotations with no arguments can be omitted after the curly braces.

Multiple annotations can be described. In such a case, describe as follows.
@ [Annotation name 1 (), ... Annotation name n ()]

There are the following annotations:
・ Required If this annotation is assigned, the input is required.
• Within a domain (domain) This type can only describe values within a domain.
-Enumeration (enumeration value) Only enumerated values can be described.
-Regular expression (regular expression) This type can only describe values that match the regular expression. (Fig. 22)

  Existing types include not only primitive types such as text types and numerical types, but also types that are normally used in the request document. Next, the types prepared as existing types are listed.

・ Text ・ Number ・ Selection ・ Select multiple ・ Price ・ Address ・ Address reading ・ Name ・ Name reading ・ Age ・ Gender ・ Date ・ Date ・ Period ・ Expense ・ Location ・ Station name ・ Card number ・ Account number ・ Phone number・ Number of people ・ Quantity ・ Department ・ Title ・ Corporate name

In Example 1, it shows a detailed method to define the field and document structure.

Items and document structure can be defined in braces that define the form. Items are defined using the following grammar.
Item name 2104: Model name 2105 = initial value 2106

  The item name 2104 is an item identifier.

  The type name 2105 describes the type name of an existing type or a new type that has been defined.

  The initial value 2106 is an initial value displayed on the input screen. You can write a string enclosed in numbers or double quotes. The initial value can be omitted.

The document structure is defined by the following grammar.
def structure name 2107 = {
Definition 2108
}

  The structure name 2107 is a structure identifier.

  A definition 2108 describes a type definition, a document structure definition, and an item definition. (Fig. 21)

  In the first embodiment, a detailed method for defining an approval route will be described.

  The approval route can be defined by defining a new approval route, defining an approval policy, defining authority delegation, and adding a route.

The new approval path definition is described as follows.
routedef approved route name 2301 = {
Definition 2302
}

  The approval path name is an identifier of the approval path.

  The definition 2302 can define a new approval route definition, approval policy definition, authority delegation definition, and route addition. (Fig. 23)

  When changing the approval route, be sure to write one approval route definition immediately below the format definition.

  If the definition of the approval route is not described, the route from the organization to which the user creating the document belongs to the highest organization is defined as the approval route, and the representative of each organization on this route is the approver. It becomes.

When defining an approved route for adding a route by adding a route to be described later, the start of the route is specified. In that case, write as follows.
begin organization [organization name 2303 in the organization chart] or
begin post [title 2304 in the organization chart] or
begin user [user name 2305 in the organization chart]

  If specified in this way, the route that follows from the specified element to the highest level along the hierarchical structure of the organization chart becomes the approval route.

The definition of the approval policy is described as follows.
policydef organization [organization name 2306] = {
Policy name 2307 = setting value}

  The organization name 2306 describes the name of the organization in the organization chart. For example, if the name of the organization element at the top of the organization chart is “Corporation XXX” and the name is designated, the company-wide policy is changed.

  The policy name 2307 specifies the name of the policy. In the first embodiment, whether or not compulsory approval is possible and whether or not proxy approval is possible can be specified. (Fig. 23)

The definition of authority delegation is described as follows.
delegation title [title 2308 in the organization chart] = title [title 2309 in the organization chart]

  The left side is the side to which authority is delegated, and the right side is the side to which authority is delegated.

The title 2308 in the organization chart and the title 2309 in the chart describe the title in the organization chart.
For example, when delegating the authority of the president to the general manager, the president is described in the job title 2309 in the organization chart, and the business manager is described in the job title 2308 in the organization chart. (Fig. 23)

The route addition is described as follows.
addroute title [title name 2309 in the organization chart] = predefined approval path name 2310

  The place on the approval route added to the left side is indicated by the post name 2309 in the organization chart, and the approval route to be added to the right side is designated by the defined approval route name 2310. (Fig. 23)

  A method for facilitating the search of the fifth embodiment will be described.

  In the fifth embodiment, since the search must be performed by looking at the hierarchical structure of elements and before and after, a search language having a capability equivalent to XPath or XPath is required.

  In addition to the devices defined in the first embodiment, a device 513 for creating a document index and a device 514 for retrieving a document index are prepared. The index includes fields for document identifiers, all approval candidates, all approval approval organizations, current approval candidates, current approval approval organizations, and approvers.

  When a document is created or approved, a document indexing device 513 is activated to analyze the document and update the index field. When a document is created, a document identifier, all approval candidates, all approval planned organizations, current approval planned users, and current approval planned organizations are generated. When approving a document, record the approver in the approver field, delete the approver and organization that performed the approval from all planned approvers and all planned approvals, and the current approver and the current approver Update approved approval organization to the next approval candidate and approval approval organization.

  When searching for documents, instead of searching for documents directly, the index is searched to obtain the document identifier. As in the fifth embodiment, when searching for a document that must be approved by itself, a search is made for a document that is included in the current approval candidate. When searching for documents that can be compulsoryly settled as in the ninth embodiment, search is made for items that are included in all prospective approval persons. When searching for documents that can be delegated in the same manner as in the tenth embodiment, search is made for documents in which the organization to which the user belongs is included in the organization to be approved at present.

  Based on the first embodiment, a method of changing the appearance of the screen such as the character size, color, and arrangement with respect to the generated screen will be described.

  When the device 501 interprets the document structure of the format and replaces it with a predetermined HTML block element 602, the item name is described in the class attribute 1003 of the block element 602. Similarly, when the type is replaced with the HTML input form element 604, the type name is described in the class attribute 1004 of the input form element 604. At this time, if the type is a new type, the existing existing type name and the new type name are described by separating them with a space. (Fig. 15)

  A CSS file having a CSS definition corresponding to an existing model name is prepared in advance in the Web server 503, and when the device 501 generates an input screen HTML, a description 1001 for linking this CSS file is added.

  In order to be able to describe a new type of CSS, when the device 501 generates the input screen HTML, a description 1002 for linking the CSS file of the format name is added. Since both the new type name and the existing type name are described in the class attribute, if the CSS definition of the new type name is not performed, the CSS definition of the existing type is adopted, and the CSS definition of the new type is changed to the existing type name. If it is done below the mold, the new type of CSS is given priority.

  When displaying the input screen HTML, the Web browser 505 performs rendering according to the CSS definition.

  In this way, CSS can be described using the model name as a key, so that the appearance of the input screen can be easily changed.

  Although the item name and type name are directly described in the class attribute of the element of the input screen HTML and a CSS file corresponding to the item name is prepared, an ID associated with the item name and type name is separately assigned, and this ID You may make it prepare the CSS file corresponding to.

  A method for performing authorization control based on the first embodiment will be described.

  An apparatus 501 that interprets this language and generates a servlet that is an input screen and a servlet that is a check logic, a server 502 that stores an organization chart and a format, and a Web server that distributes the generated HTML, as defined in the first embodiment 503, an application server 504 that executes a servlet and returns a result, a Web browser 505 that displays HTML, a device 506 that stores documents, a device 508 that performs authentication, a device 509 that performs authorization, and a document And a device 511 for referring to the organization chart are prepared. The device 508 that performs authentication and the device 509 that performs authorization are arranged between the Web browser 505 and the device 510 that refers to the document. A request from the Web browser 505 passes through the authentication device 508 and the authorization device 509 in this order, and is sent to the device 510 that refers to the document. The response to the request passes from the device 510 that refers to the document to the device 509 that performs authorization and then the device 508 that performs authentication, and is sent to the Web browser 505. (Fig. 16)

  In addition, a new policy regarding authorization can be set for the organization chart. The policy regarding authorization refers to whether or not users of the same organization can be referred to and whether or not to refer to after the organization is changed, and is described as a true / false value as an attribute of the organization element of the organization chart. (Fig. 17)

  In order to use this system, the user accesses the device 508 that performs authentication from the Web browser 505. The authentication device 508 prompts the user for a user ID and password. If the combination of the user ID and the password is correct, the authentication is successful, and thereafter the user ID is included in communication from the Web browser 505 to the system.

  Upon receiving the request, the device 509 that performs authorization extracts the user ID assigned by the device 508 that performs authentication from the request, inquires of the device 511 that refers to the organization chart, and identifies the user's job title and organization to which the user ID belongs. Ask. The authorizing device 509 forwards the request to the device that references the document.

  The device 510 that refers to the document responds with the document corresponding to the request. Upon receiving the response, the authorization device 509 confirms the contents of the document and determines whether the document can be referred to. When users of the same organization can refer, if there is an organization to which the user belongs in the document approval route, the reference is permitted. When users of the same organization cannot refer to and can be referred after the organization is changed, the reference is permitted if the user ID exists in the approval path of the document. If the user of the same organization cannot refer, and the reference after the organization change is also impossible, the reference is permitted when the user ID exists in the approval route of the document and the department to which the user belongs is also the same. In other cases, reference is not permitted.

  If the reference is permitted, the device 509 that performs authorization and the device 508 that performs authentication transfer the response to the Web browser 505. If not authorized, the authorizing device 509 responds with an authorization error.

  In this way, authorization control can be performed using the information on the approval path described in the document.

  Based on the first embodiment, a method for enabling the display / non-display of the components of the input screen to be freely changed according to the input value of the screen will be described.

  The style description language defined in the first embodiment is expanded and a selected sentence 1801 is introduced as a new grammar. A selection statement 1801 can give a conditional expression 1802 and can enclose items of the document structure in curly braces. If the value of conditional expression 1802 is TRUE, the part enclosed in braces is valid, and if it is FALSE, it means invalid. The conditional expression 1802 can describe an expression 1803 indicating the following comparison operators (=,>, <, =>, = <), a truth value, a numerical value, a character string, and an item position. An expression 1803 indicating the position of an item is described by a PATH expression in which item names are connected by “/”. (Fig. 18)

  When the device 501 converts the format to the input screen HTML, if there is a selection statement 1801 in the format, the device 501 converts the format to the block element 1804. The conditional expression 1802 is described in the attribute 1805 of the block element 1804.

  If the result of evaluating the conditional expression is TRUE, the logic 201 prepares a function for changing the style of the corresponding element to display, and when the result is FALSE, the function for changing the style of the corresponding element to non-display. For example, the display / non-display of the corresponding element can be changed by changing the visibility property of the style attribute of the corresponding element.

  When the input value is changed, the web browser 505 calls the logic 201 and switches between displaying and hiding the corresponding element.

  Based on the first embodiment, a method for changing the approval route according to the input value on the screen will be described.

  The style description language defined in the first embodiment is expanded and a selected sentence 1901 is introduced as a new grammar. The selection statement 1901 can give a conditional expression 1902 and can enclose the definition of the approval route in braces. If the value of the conditional expression 1902 is TRUE, the part enclosed in braces is valid, and if it is FALSE, it means invalid. The conditional expression 1902 can describe an expression 1903 indicating the following comparison operators (=,>, <, =>, = <), a truth value, a numerical value, a character string, and an item position. An expression 1903 indicating the position of an item is described by a PATH expression in which item names are connected by “/”. (Fig. 19)

  When the apparatus 501 reflects the approval path setting of the format in the organization chart, the apparatus 501 creates an organization chart of all possible combinations for the case where the value of each conditional expression is TRUE and FALSE. Each organization chart is surrounded by an HTML block element 1904, and a conditional expression 1902 is described in an attribute 1905 of the block element 1904.

  If the result of evaluating the conditional expression is TRUE, the logic 201 prepares a function that enables the corresponding element, and when the result is FALSE, a function that disables the corresponding element.

  When there is a change in the input value, the Web browser 505 calls the logic 201 and switches between valid and invalid of the corresponding element.

  Based on the first embodiment, a method for outputting a description of the program from a language in which a format is defined will be described.

The style description language defined in the first embodiment is extended so that a comment sentence can be input by describing a comment symbol at the beginning of a line. Furthermore, an explanatory text to be output can be specified by describing an explanatory text symbol in the comment text .

  After interpreting the format, the device 501 takes out the explanatory text in the comment together with the unique type definition and document structure defined in the format, converts them into a highly readable format as a design document, and outputs them.

  Based on the first embodiment, a method of performing a check using a value of an external database by a check logic will be described.

  An apparatus 501 that interprets this language and generates a servlet that is an input screen and a servlet that is a check logic, a server 502 that stores an organization chart and a format, and a Web server that distributes the generated HTML, as defined in the first embodiment An external database 515 is prepared in addition to an application server 504 that executes a servlet and returns a result, a Web browser 505 that displays HTML, and a device 506 that stores documents. The external database 515 stores a list of possible values of the new type, and can be retrieved by specifying a data name.

  When enumerating values as type restrictions in the definition of a new type, the data name of the external database 515 is described.

  When the data name of the external database 515 is described as the type limit value, the device 501 checks the external database 515 for an argument to check the existence of the value. Generate the provided servlet.

  Based on the twenty-second embodiment, a method for adding not only an error check but also an input assist function to the check logic will be described.

  In order to enable input assistance, the specification of the servlet generated by the device 501 is changed as follows. In the twenty-second embodiment, an error occurs if the input value does not exist in the external database 515. However, if the input value partially matches the data in the external database 515, a list of partially matched values is returned.

  The Web browser 505 calls the check logic servlet of the application server 504 asynchronously using the logic 201 and checks the input value every time a value is input to the input form of the input screen HTML. At this time, if a list of values is returned, input candidates are displayed as a selection list, and if an error is returned, an error is displayed.

  Based on the first embodiment, a method in which the definition language of the organization chart is not an XML but a dedicated language will be described.

  In the first embodiment, the language for describing the organization chart is XML. However, in this embodiment, the language is a dedicated language and has the same grammar as the document structure. (Fig. 20)

  In addition, a new organization chart itself can be described in the approval route setting of the form.

  This makes it possible to easily define an organizational hierarchy dedicated to that style.

  A method for allowing a plurality of parallel approval paths to be added based on the first embodiment will be described.

  A parallel approval route can be added by specifying the same place on the left side and adding a plurality of routes in the method of adding an approval route shown in the fifteenth embodiment. At this time, the definition language of the approval route is extended so that the parallel condition can be specified, and the following description is possible.

addroute title [title name 2401 in the organization chart] = defined approval route name 2402 additional condition 2403
The additional condition 2403 designates “And” or “Or”.

  If this definition exists in the format, an approval group element 2404 is added below the organization element having the title 2401 in the organization chart, a parallel element 2405 is added below the approval group element, and the condition of the parallel element 2405 The attribute 2406 is set as an additional condition 2403. The approval path indicated by the defined approval path 2402 is added in parallel below the parallel element. The organization element that is in the lower level of the organization element having the job title 2401 in the organization chart moves to the lower level of the approval group element 2404. (Fig. 24)

  When the format in which the definition is described is stored in the organization chart and the server 502 that stores the format, the apparatus 501 converts the format into an input screen HTML by the method described in the first embodiment. An example of the converted input screen HTML is shown in FIG.

  Next, when the user creates a document from the input screen HTML, the document is converted to document XML by the method described in the first embodiment. An example of the converted document XML is shown in FIG.

  By changing the search conditions as follows among the methods for identifying the documents that must be approved by the embodiment 5 shown in FIG. Search is possible even if there are parallel approval paths.

  The user element of the user who is a descendant of the approver element that does not have an approver element has its own userID, and if there is an approver element with an approver element one level below the approver element, the author element Either there is a scheduled creation element, or there is an approval planned group where all the approval plan elements below the parallel element whose attribute is AND have an approver element, or any subordinate level of the parallel element whose attribute is OR There is an approval plan group whose approver element has an approver element, or there is an approver element with an approver element, or has an author element, one level below the approver group to which it belongs Either there is a prospective creation element, or there is a planned approval group where all the prospective approval elements below the parallel element whose attribute is AND have an approver element, or any of the subordinate elements of the parallel element whose attribute is OR Search for documents certified prospective element is approved plans group with the approver element.

  A method for enabling selection of a plurality of modes based on the first embodiment will be described. (Fig. 27)

  A style selection screen is prepared so that a user can select a document to be created. The form selection screen acquires a list of all forms from the server 502 that stores the organization chart and form, and displays it in a tabular form. The list of styles displays the style ID and style name. Further, the number of submissions of each form is retrieved and displayed from the device 507 for retrieving documents.

  By inputting form IDs and form names as keywords in the search box in the upper right of the screen, it is possible to narrow down the list of displayed forms.

  In addition, display contents can be sorted by clicking each title item (style name, number of submissions, etc.) in the list.

  When the number of displayed items exceeds a certain number, the next page button can be pressed, and when the next page button is pressed, a document list of the next page is displayed. Similarly, when returning to the previous page, when the previous page button is pressed, a document list of the previous page is displayed.

  By pressing the new creation button for the selected style, an input screen for the style is displayed.

A method for inputting a document based on the first embodiment will be described. (Fig. 28)

This screen is a screen in which the input screen HTML generated by the apparatus 501 is displayed by the WEB browser 505.

The input form is formatted and displayed according to the CSS definition by the method shown in the seventeenth embodiment.

The Print, Submit, Temporary Save, and Discard buttons are displayed on all input screens regardless of the format definition.

When a user inputs a value in the input form, as shown in the first embodiment, the input is changed and the logic 201 is used when the input value is changed, and the type name and the changed input are input to the check logic servlet of the application server 504 asynchronously. Send the value and check the input value. If the check result is an error, the color of the input form is changed to red or the like and a warning is given to the user.

At this time, the input candidates can be displayed in the select box format by the method of the twenty-third embodiment. In addition to the apparatus defined in the first embodiment, an apparatus 516 for temporarily storing a document can be prepared to store a document being created. Saving of documents in the process of creation is automatically performed at regular intervals, but can be saved at the user's will by pressing the temporary save button.

When the print button is pressed, printing can be performed with the function of the WEB browser 505.

  Pressing the discard button deletes the temporarily stored document and closes the screen.

When the user's input is completed and the submit button is pressed, the logic 201 checks input values for all items in the document. At this time, if the result of the check logic is an error, a detailed error message is displayed on the screen. If there is no error, a confirmation screen is displayed. After the user performs visual confirmation, when the submit button on the confirmation screen is pressed, the check logic 202 is called and converted into document XML by the method described in the first embodiment. And transmitted to the server 505 for storing the document. The server 505 for saving the document checks the document XML again by the application server 504, and if there is no problem, the server 505 saves it. Usually, there will be no errors because documents are checked in advance and there are no problems. If saving is completed normally, the server that saves the document returns a normal response, and the input screen displays on the screen that the data has been saved normally and notifies the user.

Based on the first embodiment, a method for enabling input of a temporarily saved document to be resumed will be described. (Fig. 29)
Prepare a temporary save selection screen so that users can re-edit documents temporarily saved. When the temporary save selection screen is displayed, the device 516 for temporarily saving documents is searched using the userid as a key, and a list of documents temporarily saved by the user is displayed in a table format. The tabular list displays the serial number, document name, and save date.

  It is possible to narrow down the list of displayed documents by entering the document name and save date and time as keywords in the search box in the upper right of the screen.

  In addition, display contents can be sorted by clicking each title item (document name, saved date, etc.) in the list.

  When the user presses the resume button of the selected document, an input screen is displayed on which the temporarily stored contents of the document are input.

  When the delete button of the document selected by the user is pressed, the document can be deleted.

  When the user checks the check box of the document to be deleted and presses the batch delete button, the selected documents can be deleted at once.

  A method of displaying an unsettled document among documents prepared by a user based on the first embodiment will be described. (Fig. 30)

  In order to be able to select an unsettled document among the documents created by the user, a submitted unsettled screen is prepared. In the submitted unsettled screen, a document search device 507 retrieves a document in which the userid attribute of the user element that is a descendant of the creator element matches its own userid, and the highest-level approval candidate element has no approver element. Search, obtain a list of documents that meet the conditions, and display the document ID, form name, and submission date in tabular form.

  By inputting form IDs and form names as keywords in the search box on the upper right of the screen, it is possible to narrow down the list of displayed documents.

  It is possible to sort the displayed contents by clicking each title item (form name and submission date) in the list.

  When the number of displayed items exceeds a certain number, the next page button can be pressed, and when the next page button is pressed, a document list of the next page is displayed. Similarly, when returning to the previous page, when the previous page button is pressed, a document list of the previous page is displayed.

  By pressing the display button of the selected document, a reference screen for the document is displayed.

  Documents that are not approved by any approver can be retrieved. Recovering means canceling the submission of an unapproved document and returning it to the state in which the document is being created. Whether or not the document is retrievable is determined from the device 507 for searching for a document by using a user element whose userid attribute that is a descendant of the creator element matches its own userid, and all of the prospective approval element have no approver element. Find by searching. If the condition is met, the return button can be pressed.

  A method for displaying a document that can be approved by the user based on the first embodiment will be described. (Fig. 31)

  In order to allow the user to select documents that can be approved, a screen for waiting for approval is prepared. The approval waiting screen is displayed from the device 507 for searching for documents. The approval policy is compulsory and proxy approval is not possible, and the document having its own userID in the user element that is a descendant of the approval candidate element that does not have the authorizer element , Approval policy is not compulsory and can be approved on behalf of the document Approval element that does not have an approver element is the name of the organization to which the organization belongs, and the approval policy is compulsory and can not be approved The user element that is the descendant of the approver element that does not have the approver element has its own userID, and if there is an approver element that has the approver element in the lower level of the approver element A document with a creator element that has an approver element, and a set of approver elements that have an approval policy that cannot be compulsory and can be approved on behalf of an applicant, and that do not have an approver element Search for documents that have the name of the organization to which their name belongs, and that have an approver element with an approver element or an author element with an author element below the approver element. , Get a list of documents that meet the conditions, and display the document ID, form name, and submission date in tabular form.

  By inputting form IDs and form names as keywords in the search box on the upper right of the screen, it is possible to narrow down the list of displayed documents.

  It is possible to sort the displayed contents by clicking each title item (form name and submission date) in the list.

  When the number of displayed items exceeds a certain number, the next page button can be pressed, and when the next page button is pressed, a document list of the next page is displayed. Similarly, when returning to the previous page, when the previous page button is pressed, a document list of the previous page is displayed.

  By pressing the display button of the selected document, a reference screen for the document is displayed.

  By pressing the approval button for the selected document, an approval screen for the document is displayed.

  If you want to approve all at once, you can approve all selected documents by selecting the document with the check box on the left of the list and clicking the collective approval button.

  Moreover, it can be set as another approval screen by changing search conditions with the same screen configuration. For example, when the screen corresponding to the fifth embodiment is used to specify a document that must be approved by the user, the search policy is not approved by the approval policy, and the descendant of the approval candidate element that does not have the approver element. The user element has its own userID, and there is an approval planner element that has an approver element or a document that has a planner element that has a creator element and an approval policy in one subordinate to the approval planner element. Approval approval is possible, and the organization name of the prospective approver element that does not have the approver element is the name of the organization to which it belongs, and the prospective approver element having the approver element is one level below the prospective approver element. It may be a document that has a creator element that has a creator element or a creator element.

It is also conceivable to provide a search box in which such a search expression is defined in advance and selected with a select box so that the type of document to be displayed on the list can be changed.
The following items can be considered as selection items of the select box.
・ All unapproved items (this example)
・ Documents that should be approved (Example 5)
・ All ・ Approved ・ Approved ・ Available

  Note that it is possible to configure the system by combining some or all of the above-described embodiments. In addition, although an embodiment in the web system is mainly described, it is also possible to implement by an applet by Java, a native application by C language or the like, instead of the configuration of the browser and the servlet. Furthermore, it is possible to apply not only HTTP but also various protocols as communication protocols.

  Furthermore, this can be used for a questionnaire conducted by a large number of people as a form of deliberation.

It is the block diagram which showed the relationship between an organization chart, a style, and a request for approval. It is the block diagram which showed the tree structure of the organization chart. This is an example in which a tree structure of an organization chart is expressed in XML. It is a description example of a format description language. It is a block diagram of a component required in order to implement | achieve this invention. It is an example of the document structure converted into the input screen HTML. It is an example of the organization chart converted into input screen HTML. It is an example of the document structure converted into XML representing a document. It is an example of an approval route described in XML representing a document. It is an example of an approval route when there is no setting of an approval route in the form. It is an example of an approval route when authority delegation is set in the form. It is an example of an approval route when route addition is set in the format. This is an example of approval for a document. This is an example of sending back a document. It is an example of the input screen HTML at the time of extending Example 1 and changing the appearance of a type | mold. It is a block diagram of the component required in order to implement | achieve authorization. It is a description example of XML representing an organization chart when an authorization policy is expanded to be settable. It is a description example when changing the constituent elements of a document according to conditions. It is a description example in the case of changing an approval route according to a condition. It is a description example when the description language of the organization chart is a dedicated language and is described in the form. It is a description example of a type and a document structure. It is a description example of annotation. It is a description example of approval route setting. It is an additional example of a parallel approval route. It is an example of the approval path | route converted into the input screen HTML when there exists a parallel approval path | route. It is an example of the approval path | route converted into document XML when there exists a parallel approval path | route. It is an example of a style selection screen. It is an example of the input screen of documents. It is an example of a temporary save selection screen. It is an example of the selection screen of an unsettled document among the documents which the user created. It is an example of the selection screen of the document which can be approved.

501 Device for generating HTML as input screen and servlet as check logic 502 Server for storing organization chart and format 503 Web server for distributing generated HTML 504 Application server for executing servlet and returning result 505 Display HTML Web browser 506 Document storage device 507 Document search device 508 Authentication device 509 Approval device 510 Document reference device 511 Organization chart reference device 512 Approval device 513 Approval route change device 514 Device for creating document index 515 Device for retrieving document index 516 External database 517 Device for temporarily storing document 201 Logic called when content of input form is changed 202 Submitting document Logic called sometimes 203 Logic to set authority delegation

Claims (8)

Means for storing organization information expressed by a tree-structured data structure corresponding to the organization structure;
Means for storing a format that is data including a definition of a document structure including a description of a correspondence relationship between items constituting a document and a type, a definition of an approval route, and a type definition ;
Means for memorizing the approval documents;
Means for providing an input screen to the user based on the format ;
Means for generating an input screen and a check program ,
The means for generating the input screen and the check program generates the input screen based on a format, and checks the input value input to the input screen based on the definition of the type included in the format Produces
The check program is called from the input screen and returns input candidates,
The input screen provides input assistance by displaying the input candidates returned from the check program,
Determine an approval route for the document based on the organization information and the definition of the approval route included in the format;
A deliberation system that generates a deliberation document including an input value input on the input screen by a user and an approval path of the document, and stores the generated deliberation document in a means for storing the deliberation document. The input screen is composed of a plurality of input elements corresponding to items constituting the document,
The approval system according to claim 1, wherein the approval route is determined based on an input value to an item input by the user or an input value to a plurality of items. 2. The approval system according to claim 1 , wherein the input screen and the means for generating the check program further generate a description of the format based on the format. The modalities approval system according to any one of claims 1 to 3, characterized in that it comprises a description of domain for said type. The approval system further includes an external database,
5. The approval system according to claim 4 , wherein the format includes information for querying the external database as a description of the domain. The means for providing the input screen further stores a definition file including a definition of a display method on the input screen for a type assigned to the item of the form or the document structure. 5. The approval system according to 5 . Means for storing organization information expressed by a tree-structured data structure corresponding to the organization structure;
Means for storing a format that is data including a definition of a document structure including a description of a correspondence relationship between items constituting a document and a type, a definition of an approval route, and a type definition ;
Means for memorizing the approval documents;
Means for providing an input screen to the user based on the format ;
A program executed in a deliberation system comprising an input screen and a means for generating a check program ,
The means for generating the input screen and the check program generates the input screen based on a format, and checks the input value input to the input screen based on the definition of the type included in the format Including the step of generating
The check program includes a step of being called from an input screen and returning input candidates,
The input screen provides input assistance by displaying the input candidates returned from the check program,
Determining the approval path of the document based on the definition of the included approval route on the manner and the organization information,
A program characterized by comprising the step of storing in the means for generating the approval documents, storing said approval documents including the approval path of the document and the input value that is input to the input screen by the user. Means for storing organization information expressed by a tree-structured data structure corresponding to the organization structure;
Means for storing a format that is data including a definition of a document structure including a description of a correspondence relationship between items constituting a document and a type, a definition of an approval route, and a type definition ;
Means for memorizing the approval documents;
Means for providing an input screen to the user based on the format ;
A method for controlling a deliberation system executed in a deliberation system comprising means for generating an input screen and a check program ,
A check program in which the means for generating the input screen and the check program generates the input screen based on a format and checks an input value input to the input screen based on the definition of the type included in the format Including the step of generating
The check program includes a step of returning input candidates that are called from the input screen, and the input screen performs input assistance by displaying the input candidates returned from the check program,
Determining the approval path of the document based on the definition of the included approval route on the manner and the organization information,
The method of approval system generates approval documents including the approval path of the document and the input value that is input to the input screen by the user, characterized in that it comprises a step of storing in the means for storing the approval documents .

Images