JP2017199075A - Business process management system, client, server, and business process management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable the setting such as input or layout of a form in accordance with a role.SOLUTION: In a business management system comprising: a client; and a server connected via a network to the client, and associated with a database in which various data tables are stored, that is, a server having a table management part for managing the various data tables stored in the database, the client comprises a form edition processing part for creating layout information of a form, and the server is characterized to store the layout information received from the client as well as a form ID for uniquely identifying the form in the database. The form edition processing part is characterized to perform the setting of the form in association with attributes of a login user to the client or a node of a business process by an input operation by the client.SELECTED DRAWING: Figure 23

Description

  The present invention relates to a business process management technique, and more particularly to a business process management technique capable of constructing an input display control function according to the role of a business process.

  Business systems with processes that span user departments (such as sub-organizations such as “departments” and “sections”) have traditionally been IT systems departments (such as IT organizations that develop and operate business systems). Developed and improved by an organization) (see, for example, Patent Documents 1 and 2).

Japanese Patent Laid-Open No. 10-105623 JP 2007-299340 A

  If the development and improvement of all business systems are entrusted to the higher level organization, it is difficult to improve the single lower level organization alone in order to achieve improvements specific to a specific user department. There is a problem that it becomes a large-scale work because cooperation is required.

  In particular, in the management of business information input forms and business process management, it is necessary to design and program control processes and management methods in order to develop input forms that satisfy the following business requirements. There was a problem that engineers with specialized knowledge of system construction were necessary.

(Business requirements)
In the business system input form,
1) I want to change the display items and layout of the form by role (approver, department, etc.).
2) I want to set or change the display / input permission independently for each display item in the form by role (approver, department, etc.).
3) We want to make associations between items on the form, for example, whether the second item is an essential input or an optional input depending on the input state of the first item.
An object of the present invention is to enable setting according to a role in settings such as form input and layout as in 1) to 3) above.

According to an aspect of the present invention, a client is a server that is connected to a network with the client and is associated with a database that stores various data tables, and manages the various data tables stored in the database. And a server having a table management unit, wherein the client has a form editing processing unit that creates form layout information, and the server receives the layout information received from the client as the form Is stored in the database together with a form ID that uniquely identifies the log, and the form edit processing unit is configured to log in to the server from the client by an input operation on the client. Business management system in association with the attribute of the user and performs setting of the form is provided.

  The above form ID is an ID that is uniquely set for each form editing process, and is unique in the system. Thereby, in the form setting by the client, for example, a unique form obtained by editing a common form can be set.

  When logging in to the server from the client, it is possible to set the form according to the attribute of the logged-in user, more specifically, the role when using the business management system.

  The database includes a table in which the ID of the login user and the form ID, which are created by the server based on an operation of a form creation request from the client, are associated with each other.

  The form editing processing unit can set display / non-display of an item in association with an attribute of a login user to the client for each item of the form.

  The form editing processing unit can arbitrarily set a form for each node of a business process.

  The form ID that can be presented is limited by the attribute of the logged-in user.

  Since the layout information edited by each client is identified for each client by the form ID associated with the server, a plurality of users can input data without being influenced by the form changes of other users. In addition, it is possible to switch forms according to business.

  The client (developer in the user department) can arbitrarily define a unique form for each node in the subordinate organization of the business process.

  The database is provided with a node definition table that defines the form ID corresponding to a node ID that identifies each node of the business process, created by the server based on an operation of a business process creation request from the client. It is characterized by.

  The form editing processing unit can set, for each node, whether or not the item is required to be input and whether or not editing is prohibited as an item attribute by an input operation in the client. .

The present invention is a server and a server that is connected to a network with the client and is associated with a database that stores various data tables, and includes a table management unit that manages the various data tables stored in the database The client includes a form editing processing unit that creates form layout information, and the server uniquely identifies the form from the layout information received from the client. A client in a business management system, wherein the form editing processing unit logs in to the server from the client by an input operation in the client Guin in association with the attribute of the user is a client and performs setting of the foam.

  In addition, the present invention provides a client and a server connected to the client via a network and associated with a database that stores various data tables, and a table management unit that manages the various data tables stored in the database The client includes a form editing processing unit that creates form layout information, and the server uniquely identifies the form from the layout information received from the client. A server in the business management system, which is stored in the database together with a form ID to be identified, and is associated with an attribute of a login user who logs in to the server from the client by an input operation in the client The server is characterized in that a form ID corresponding to a task for uniquely identifying the form is selected from the client and the layout information requested to be transmitted is transmitted to the client to prompt display of the form. .

  According to another aspect of the present invention, a client is a server that is connected to a network with the client and is associated with a database that stores various data tables, and manages the various data tables stored in the database. And a server having a table management unit, wherein the client executes a form editing process step for creating form layout information, and the server receives the layout information received from the client as the layout information. A business management method in a business management system, wherein a step of storing in a database together with a form ID for uniquely identifying a form is executed, wherein the form editing processing step is performed by an input operation in the client. , Business management method, which is a step for setting said foam in association with an attribute of the login user to log in to the server from the client is provided.

  According to the present invention, in form management of business information and business process management, settings according to roles can be made in settings such as form input and layout.

It is a functional block diagram which shows the example of 1 structure of the business process management system by one embodiment of this invention. It is a functional block diagram which shows one structural example of a client among business process management systems. It is a figure which shows an example of the image of the business management system by this Embodiment. It is a flowchart figure which shows the flow of a process at the time of creating a form newly. It is a figure which shows an example of the item and data (table) which are stored in database DB21. It is a figure which shows an example of form control. FIG. 10 is a flowchart showing a flow of form layout editing (creation) processing on the client side. It is a figure which shows an example of the item group variable in operation etc. which used GUI of the display part of a client. It is a figure which shows operation etc. which used GUI of the display part of a client. It is a figure which shows operation etc. which used GUI of the display part of a client. It is a figure which shows operation etc. which used GUI of the display part of a client. It is a figure which shows the example of the attribute of a department and a user at the time of performing operation etc. which used GUI of the display part of a client. It is a figure which shows the example of a setting of the attribute of an item, the attribute of a user, etc. at the time of performing operation etc. which used GUI of the display part of a client. It is a figure which shows operation etc. which used GUI of the display part of a client. It is a figure which shows operation etc. which used GUI of the display part of a client. It is a figure which shows the example of data of layout information. It is a figure which shows the correspondence of the word of FIG. It is a figure which shows an example of the JSON character string which showed the layout information of the form with the character string. It is a figure which shows the more detailed structural example of layout information. It is a flowchart figure which shows the flow of the preservation | save process of the form by the server side. It is a figure which shows an example of the item and data (table) which are stored in database DB. It is a figure which shows an example of the item and data (table) which are stored in database DB. It is a flowchart figure which shows an example of the flow of the display process of the form for every role. It is a figure which shows the structural example of the table relevant to a process. It is a flowchart figure which shows the details by the side of the client after the process of FIG. It is a flowchart figure which shows the details by the side of the client after the process of FIG. It is a flowchart figure which shows the details by the side of the client after the process of FIG. It is the figure which showed the example of a display along the display process of the form for every role, and the example of a display according to a related input restriction | limiting process. It is an image figure which shows the example which sets the form called drafting to a node. It is a flowchart figure which shows an example of the flow of the process of FIG. It is a figure which shows the structure of each table along a process. It is a flowchart figure which shows an example of the flow of a process which defines a form in each node of a process. It is a figure which shows the structural example of the various tables along the process of FIG. It is a figure which shows the detailed example of the layout of an answer form. It is a figure which shows the detailed example of the layout of an answer confirmation form. It is a figure which shows an example of the state at the time of setting a form to each node of a process. It is a figure which shows an answer form and an answer confirmation form.

  In this specification, a business process refers to, for example, the order of a series of business flows (processes) indicated by arrows between nodes for the business indicated by a node. It is also possible to cope with complicated business processes including sub-nodes indicating the flow of work performed in other departments.

  The business form (form) is a document designed by a form for managing business information in a predetermined format, and can be managed in units of BOX including items and a plurality of items, for example.

In this specification, the rough unit of the business to handle when managing the business in the form is a BOX.
In the BOX, a plurality of items to be input and displayed are arranged in association with the item title and the item content. With such a form, detailed form design and authority management can be performed in one's own department.

For example, in the following example, an upper organization is an upper organization such as a system development department, for example, an organization that manages an entire business system by an in-house (department, company, etc.) server, etc. For example, in the following example, an organization that manages work by a client (a department, a section terminal, etc.) that can access a server.
A role refers to an approver, a department, or its authority.

In the technology described below, the development department can be a department that uses the business process management system according to this embodiment as well as an IT specialist department.
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1A is a functional block diagram showing a configuration example of a business process management system according to an embodiment of the present invention. FIG. 1B is a functional block diagram illustrating a configuration example of a client in the business process management system.

  The business process management system A according to the present embodiment includes a server 1 that functions as a business process management apparatus and a plurality of clients 23 (23-1, 23-2,... n) and a database DB21 connected to the server 1 by the network NT, for example.

  The server 1 includes a control unit 3 that controls the overall functional units, a document management unit 5 that manages documents and the like, a table management unit 7 that manages tables in the DB 21, and communications that communicate with clients via a network. Unit 11, a memory 17 that stores a program for causing the control unit (CPU) 3 to execute processing of each functional unit, and a storage control unit 15 that controls storage in the memory 17. . The server 1 is common to each department or section, and shows an example managed by a department that is a higher organization.

  FIG. 1B is a diagram illustrating a configuration example of the client 23-1. The client 23-1 individually used in each unit and section includes, for example, a control unit 31 that controls each functional unit, a communication unit 33 that communicates with the server 1, and an input unit 35 such as an input key or a touch panel. And a display unit 37 such as a display, and a memory 41 for storing programs and data for causing the computer to execute each function. As the client 23-1, a terminal such as a personal computer or a smartphone can be used. At least one client is arranged in each department which is a subordinate organization. Therefore, in the following description, it is assumed that each client functions as an information processing apparatus for performing business management in different departments.

  FIG. 2 is a diagram illustrating an example of an image of the business management system according to the present embodiment. The process 51 has a hierarchical structure, and the processes 51-1 to 51-4 of the lower organization are set for the nodes of the processes of the upper organization. That is, the business management process (process) 51 includes, for example, a start node 51-1, an answer node 51-2, an answer confirmation node 51-3, and an end node 51-4 for one node.

  The business management system according to the present embodiment is configured such that different forms can be set for each node, for example. For example, a form 53 is set for the node 51-2 and a form 55 is set for the node 51-3, so that different forms can be set depending on the node.

  In addition, for example, in the form 53, when an item A is input, the item C becomes an essential input item. For example, it is possible to control whether the input is an essential input or an arbitrary input depending on the input state.

  Further, for example, when a non-employee refers to this form in the form 55, the display / input permission can be changed for each display item of the form by role, such as hiding the item N.

This point will be described in detail below.
Hereinafter, the flow of processing in the business management system according to the embodiment of the present invention will be described in detail.

1) Processing when creating a new form on the server side:
First, a process for creating a new form on the server side will be described. FIG. 3 is a flowchart showing the flow of processing when creating a new form. FIG. 4 is a diagram illustrating an example of items and data (tables) stored in the database DB21. FIG. 5 is a diagram illustrating an example of the form control.

  First, in step S1, for example, the client 23-1 sends a form creation request, for example, a reply form creation request (signal) to the server 1 by the input from the input unit 35, and the server 1 receives the request.

  In step S2, the server 1 registers a form name (in this example, an answer) in the form definition table shown in FIG. Here, the form definition table has a form ID field, a form data storage table name field, a form name field, and a layout field. The form format, for example, input area layout, label layout, button layout, etc. It is a table that defines the location.

  In step S3, the server 1 creates a form data storage table shown in FIG. The form data storage table has a data ID column, a form ID column, a process ID column, and a preset column surrounded by a thick line. Here, data is a value and information, a form is a form, and a process is a process. A preset is a value that has been adjusted in advance, such as a set value, or a preset value that has been adjusted in advance, or a combination thereof. It is synonymous with so-called “initial setting”, “default setting” and the like. In other words, data can be displayed in the input area on the form, or the process can be advanced by pressing a button.

In step S4, the server 1 registers the column definition information (FIG. 4C) of the form data storage table. The preset column definition information of the form storage table includes a form ID column, a form data storage table name, a column name, a column display name, a data type, a form control, and a use / non-use column in the form. doing.
The information of the preset column in FIG. 4B is linked to the column name in FIG.

  These tables are automatically created by the server 1 and automatically stored in the database DB21. If the form control is a text box, items of a text box (item 1), a text area (item 2), and rich text (item 3) are created as shown in FIG. In the text area, a form having various items and tails shown in the example as shown in the right figure is created.

  As described above, 1) the table shown in FIG. 4 is created by the processing when creating a new form.

2) Processing when saving the form layout:
Next, processing at the time of saving a form layout will be described. In this process, a form layout creation (editing) process is performed on the client 23-1, and a form storage process is received on the server 1 side in response to the result of the form layout editing process from the client 23-1. Is what you do.

(Client-side new form creation process)
6A shows a flow of form layout editing (creation) processing that can be performed for each node shown in FIG. 2, for example, by the form editing processing unit 31-1 (in the control unit 31) on the client 23-1. FIG. 6B to 6I are diagrams showing operations using the GUI of the display unit 37 of the client 23-1, etc., FIG. 6J is an example of layout information data, and FIG. 6K is the wording of FIG. Therefore, it is a diagram showing a correspondence relationship between a word expressed in an easy-to-understand manner) and a character string actually used. This editing process is executed in the editing processing unit in the control unit.

  FIG. 7 is a diagram illustrating an example of a JSON character string in which form layout information is represented by a character string, and FIG. 8 is a diagram illustrating a more detailed configuration example of layout information.

  FIG. 9A is a flowchart showing a flow of a saving process for saving a form newly created on the client side on the server side. 9B and 9C are diagrams illustrating examples of items and data (tables) stored in the database DB21.

  The form layout editing (creating) process on the client 23-1 side will be described in detail with reference to the flowchart in FIG. 6A, GUI explanation layout information, and explanation thereof. The form layout editing (creating) process on the client 23-1 side is performed mainly by executing a program stored in the memory 41 by the control unit (CPU) 31. Processing by dedicated hardware may be used. That is, the following processing is executed by each functional unit described as processing steps below.

  Processing is started in response to an operation on the input unit 35 of the client 23-1 (Start). First, in step S11, a layout information variable is prepared. The layout information variables are, for example, labels, fields, controls, etc. in FIG.

  In step S12, a unique identifier such as “Form001” is set as the form ID of the layout information (see also the description of S12 in FIG. 6J).

  In step S13, an “item group” variable is prepared (see also the description of S13 in FIG. 6J). The “item group” variable is, for example, a title, a person in charge of answering, a reply, a reply date, etc., as shown in FIG. 6B.

  In step S14, the number of items arranged on the display screen of the display unit 37 of the client 23-1, for example, the target control is selected from the control pane in the control arrangement of FIG. 6B, and as shown in FIG. 6C, Variables corresponding to the number of items to be displayed (5 in FIG. 6C) for the number of items indicated by the symbol L1 displayed by dragging and dropping in the center area of the screen are prepared, and the processing from S14 to S25 is performed for each item group variable. Perform the procedure. One paragraph in FIG. 6J corresponds to one of these processing procedures. In steps S15 to S24, “title” is used as an example for easy understanding.

  Thereafter, the processes from S14 to S25 are repeated in the order of the person in charge of reply, reply, and reply date after the title.

(Example of repeated processing)
Here, one of the iterative processes is shown by taking the title as an example. The following processing corresponds to each row of the first paragraph (field ID is Title) in FIG. 6J.

In step S15, an “item” variable is prepared.
First, in step S16, for example, “Title” is set in the “item” field ID.
In step S17, for example, “text (one line)” is set in the “item” control.
In step S18, for example, “title” is set in the “item” label.
In step S19, for example, “” is set as the “item” default value.
In step S20, for example, “Yes” is set in the “item” input mandatory.
In step S21, for example, “0” is set as the “item” minimum value.
In step S22, for example, “1000” is set as the “item” maximum value.
In step S23, for example, “display for all users” is set as the “item” display condition.
In step S24, an item is added to the item group, and the process returns to step S14 until the processing for all items is completed in step S25.

  FIG. 6D is a diagram illustrating an example of a GUI for setting attributes (input required, edit prohibited, etc.) of each item related to step S20.

  First, the title attribute is selected from the part attribute and field attribute value of the screen in the upper right area with respect to the title column in the center display area in FIG. 6D displayed on the display unit 37 of the client 23-1. The item selected by the user can be set (T1, T2).

  Furthermore, as shown in T3, when the check box (displayed by all users) in the lower right corner of the screen in the upper right area is checked, for example, a dialog as shown in FIG. 6E is displayed. In other words, 1) display for all users, 2) specific (input possible) user selection, 3) specific (input possible) department selection, 4) display only users whose user attributes match the following values (For example, the display condition can be set such that “employee type” matches “regular employee” (T3). Note that the user attribute can be selected as in 4) (T4). ) And preferred.

  Here, as shown in FIG. 6F, the department attribute and the user attribute can be set in association with the department ID. For example, if this information is stored in the DB 21, the information can be appropriately referred to on the client 23-1 side by appropriately contacting the server 1.

  In this way, as shown in FIG. 6G, item attributes and user attributes can be set in the form. The attribute of each item as shown in FIG. 6G may be stored in the memory 41 of the client 23-1.

The process returns to step S14 until the processing for all items is completed.
In step S26, item group variables are set in the layout information.
In step S 27, “required to input the answer date when answer is set” is set in the related input restriction of the layout information.

  As an example of setting related input restriction, for example, as shown in FIG. 6H, the same display as in FIG. 6D is displayed on the display unit 37 of the client 23-1, and for example, a check box for related input restriction is checked (T5). ), A dialog for adding a related input restriction is displayed. For example, when the field 1 satisfies the condition, the field 2 can arbitrarily set a condition such as input required.

In step S28, the layout information is serialized. Serialization is a well-known mechanism prepared in the JavaScript trademark.
In step S29, the communication unit 33 requests the server 1 to store data on the server 1 side in the DB 21 of the layout information serialized in step S28.

  FIG. 6I is a diagram showing an example of a GUI for performing the processing of steps S28 and S29. By pressing the save button, the layout information set by the above processing can be created as a JSON character string. it can.

  FIG. 7 is a diagram showing an example of a JSON character string created by the above processing. FIG. 8 is a diagram showing a detailed example of layout information determined by the JSON character string.

  In the JSON character string, the order of the controls for displaying the form is determined by the order of the asITEM array ([]). Further, in the related input restriction, when the item specified in field1 performs an operation of operator1 (input completed, etc.), the input restriction (essential, etc.) of the item specified in field2 is set to action.

  Thereafter, the server side processing described with reference to FIG. 9A and the like is performed, and success / failure from the server 1 is received in step S30. Thereby, the processing on the client side ends.

  However, on the client side, layout information and the like are temporarily created during the editing process, but the created layout information and the like are sent to the server and held semipermanently in the DB 21.

(Server-side processing)
FIG. 9A to FIG. 9C are diagrams for explaining server-side processing and a configuration example of a table in the database DB 21 associated therewith.
As shown in FIG. 9A, a data (layout information) storage request is received from the client side 23-1, and is received by the JSON character string shown in FIG. 7 (see FIG. 8 for the contents), and the process is started (Start).

  In step S31, the received layout information and the number of items are repeated (S31 to S35).

  First, in step S32, it is determined whether an item and a field ID exist in the column name of the column definition table of the form data storage table shown in FIG. 9B (= FIG. 4C). Here, it is determined whether or not Title (see FIGS. 7 and 8) exists in the column name.

  In Step S32, when Title exists in the column name, the process proceeds to Step S35. In Step S32, when Title does not exist in the column name, the process proceeds to Step S33.

As shown in FIG. 9B (a), since Title does not actually exist in the column name, the process proceeds to step S33, and the column (Title) of the item field ID is added to the form data storage table shown in FIG. 9B (b). To do.

  Next, in step S34, as shown in FIG. 9B (c), a new item (first row, column name Title,...) Is added to the column definition table of the form data storage table.

  In step S35, the processing from step S31 to S35 is similarly executed for the title, respondent, answer, and answer date.

  Next, in step S36, the layout information by the JSON character string created by the processing on the client 23-1 side is added to the layout of the form definition table (FIG. 4A) shown in FIG. Save in DB21.

  In step S37, the success / failure information regarding the layout storage is returned (transmitted) to the client 23-1.

  FIG. 9C is a diagram illustrating a configuration example of a table stored in the DB 21 after completion of the layout saving process on the server 1 side.

  As shown in FIG. 9C (a), the column definition table of the processed form data storage table has a configuration in which items processed on the client 23-1 side are added. Further, as shown in FIG. 9C (b), in the form data storage table, in addition to FIG. 9B (b), respondents, contents, and answer dates are added.

  Furthermore, as shown in FIG. 9C (c), the form definition table has a configuration including layout information (a JSON character string).

  The DB 21 connected to the server 1 side by associating the layout information (JSON character string) created on the client 23-1 side with the form ID created on the client terminal 23-1 side such as Form001 by the above processing. Can be stored within. That is, on the server side, layout information as shown in FIG. 8 set on the client 23-1 side can be held as shared information with the created client terminal 23-1.

  The association of the layout information between the client 23-1 and the server 1 can be performed by the form ID.

  On the client side, the form ID and information that allows the user to specify the form may be created in accordance with the exchange of information between the server and the client. This is convenient because the user can grasp which form is requested in the request for the form from the client to the server.

3) About processing when displaying a form:
Next, processing for returning data for displaying a form on the client terminal 23-1 to the client terminal 23-1 on the server 1 side according to the layout stored in 2) will be described. Here, the form display processing for each role set on the client 23-1 side will be described as an example.

  FIG. 10 is a flowchart illustrating an example of a flow of form display processing for each role. FIG. 11 is a diagram illustrating a configuration example of a table related to processing. 12 to 14 are flowcharts showing details on the client side after the processing of FIG.

  As shown in FIG. 10, when the process is started (Start) and the process is started on the server 1 side in step S41, that is, in step S41, for example, the form name “answer” is received from the client 23-1 side. When the server 1 side receives a request for displaying a form that presents, the data (layout information) of the designated form (eg, “answer”) from the form definition table shown in FIG. ) Is acquired from the DB 21.

  In step S43, data (data to be displayed on the form) of the designated form (Form ID = form001) is created from the form data storage table shown in FIG.

  Next, in step S44, user data including the login ID of the login user is acquired from the user table shown in FIG.

  Next, in step S45, the user data is returned to the client 23-1, and the process ends (end).

4) Client side processing:
FIGS. 12 to 14 show the detailed processing flow on the client side after the processing of FIG. These processes are also performed by executing a program stored in the memory 41 by the control unit (CPU) 31.

  As shown in FIG. 12A, first, analysis processing and control drawing processing of data (layout information: see FIGS. 7 and 8) returned from the server 1 in step S45 of FIG. 12 are started (step S101 = S45).

  In step S102, loop processing is performed for the number of controls. In step S103, the control type is determined.

  If the control type is a text box as a result of the determination process in step S103 (step S104), the text box is drawn with a label on the screen in step S105. Next, control attributes are set in step S106 (see FIG. 13), and data is set in step S107. FIG. 12B is a diagram illustrating an example rendered by this processing.

  As a result of the determination process in step S103, if the control type is a text area (step S108), the text area is drawn with a screen label in step S109. Next, control attributes are set in step S110 (see FIG. 13), and data is set in step S111.

  If the control type is datetime as a result of the determination process in step S103 (step S112), the date is drawn with a label on the screen in step S113. Next, control attributes are set in step S114 (see FIG. 13), and data is set in step S115.

  The processing from step S103 to S115 is looped (step S116), and the related input restriction is set in step S117 (see FIG. 14).

As shown in FIG. 13, in the control attribute setting process (S106, S110, S114) in step S121, first, in step S122, the control height is set (H
eight). Next, in step S123, editability (FALSE) is set (Disable). Next, in step S124, display permission / inhibition is set (Visible). In step S125, an initial value is set (DefaultValue). Next, in step S126, input restrictions are set (Minlength, Maxlength). Next, in step S127, whether or not it is essential is set (Required).

  In step S124, it is determined whether or not display is possible in step S128. If display is possible or not = all (displayed by anyone) as shown in step S129, Visible = true (display) is set in step S130, as shown in step S131. If display permission = none (nobody displays), then Visible = false in step S132, and if display permission = conditional expression as in step S133, the condition is met in step S134. If the conditional expression is satisfied, Visble = true (display) is set in step S135. If the conditional expression is not satisfied, Visible = false (not displayed) is set in step S136.

  With these processes, control attributes can be set on the client 23-1 side.

FIG. 14 is a diagram showing a detailed example of the related input restriction setting process on the client side (see the related input restriction in FIG. 8). First, in the related input restriction setting process in step S141 (= S117), in step S142, the control specified in fieldId 1 is acquired and set as control 1. In step S143, fieldId
The control specified in 2 is acquired and set as control 2. In step S144, operator1 is analyzed. If operator1 = inputted as in step S145, in step S146, if the control 1 is in the input state in the control 1 focus-out event, the required input (required) of the control 2 is set to TRUE. If it is not input, the required input (Required) of control 2 is set to False.

  If operator1 = noninputted as in step S147, in step S148, if the control 1 is in an uninput state in the control 1 focus-out event, the required input (required) of the control 2 is set to TRUE. If it is in the input state, the required input (Required) of control 2 is set to False.

  As described above, for example, it is possible to set a related input restriction, which is a mutual restriction item between a plurality of input items, such as “AnswerDate (answer date) is a mandatory input if the content of the field ID has already been input. .

  FIG. 15 is a view showing a display example according to the form display process for each role and a display example according to the related input restriction process. FIG. 15A shows an answer form when the role is a regular employee. It is displayed that the customer is a corporation A. On the other hand, FIG. 15B is a display example of an answer form when the role is not a regular employee, and it is not displayed that the customer is A Co., Ltd. (not displayed). In this way, for example, information unnecessary for the role can be hidden.

  Furthermore, when the answer is in an input state, the answer date can be set to be required to be displayed, for example, a display corresponding to the related input restriction process.

(Processing example of setting a form in each node of the process)
Next, an example of processing for setting a form in each node of the process on the server 1 side will be described. FIG. 16 is an image diagram showing an example in which a form called draft is set for a node.

  FIG. 17 is a flowchart showing an example of the processing flow, and FIG. 18 is a diagram showing the configuration of each table along the processing.

  First, when processing starts (Start), a process creation request including a process name is received from the client 23-1 (step S51).

  In step S52, a process name (for example, an inquiry response) is registered in the process definition table of FIG. In step S53, the start / draft / completion node is registered in the node definition table together with the node ID and process ID (see FIG. 16). In step S54, the following processing is performed.

The node context is registered in the edge definition table of FIG. 18C (see also FIG. 18B).
-Predecessor node: Start node, Subsequent node: Draft node-Predecessor node: Draft node, Subsequent node: Completion node Next, success / failure information is transmitted to the client 23-1, and the client 23-1 receives the information. Receive.
With the above processing, a new process can be created.

  Next, processing for defining a form for each node of the process will be described in detail with reference to FIG. 2 and the description thereof.

  FIG. 19 is a flowchart showing an example of the flow of the processing. FIG. 20 is a diagram illustrating a configuration example of various tables along the processing of FIG.

  First, in step S61, for example, the client 23-1 sends a process creation request to the server 1 by the input from the input unit 35, and the server 1 receives the request.

  Next, in step S62, it is checked whether or not the designated process exists in the process definition table shown in FIG. If the specified process does not exist, an error notification is sent to the client. When the designated process exists (Process (process) 001), the process proceeds to the next step S63.

  In step S63, it is checked whether or not the designated node (see also FIG. 2) exists in the node definition table of FIG. If the specified node does not exist, an error notification is sent to the client. If the specified node exists (for example, an answer), proceed to the next. Here, in FIG. 20B and FIG. 20C, column names and columns surrounded by a thick line are linked.

  In step S64, it is checked whether or not the designated form (form ID) exists in the form definition table of FIG. If the designated form (form ID) does not exist, an error notification is sent to the client. When the designated form (form ID) exists (for example, Form001), the process proceeds to the next. Note that a JSON character string is registered in the DB 21 in the layout of the form definition table.

In step S65, the designated form (for example, Form001) is registered in the node definition table shown in FIG.
Next, in step S66, success / failure is transmitted to the client 23-1, and the process ends (End).

FIG. 21 is a diagram showing a detailed example of a response form layout. The layout information includes a JSON character string key name and a JSON character string value.
FIG. 22 is a diagram showing a detailed example of the response confirmation form layout. The layout information includes a JSON character string key name and a JSON character string value.

FIG. 23 is a diagram illustrating an example of a state when a form is set in each node of a process.
As shown in FIG. 23, the data displayed on each form is the same. The difference is the setting value of the input mandatory item and the edit prohibited item. For example, in the answer form, the title is an indispensable input, and the confirmer / return reason is an edit prohibited item.
In the answer confirmation form, the confirmer is required input, and the title / responsible person / answer / answer date is a prohibited item.

FIG. 24 is a diagram showing an answer form and an answer confirmation form.
The field ID referred to by the answer form and the answer confirmation form are both the same. That is, the same data is displayed for each form. In the answer form and the answer confirmation form, editability and required input items can be different.

  As described above, an arbitrary form identified by the form ID can be defined in each node of the process.

  As described above, according to the present embodiment, in the management of business information forms and business processes, it is possible to uniquely set the form input, layout, etc. in the subordinate organizations.

  The server can permanently store the subordinate form created by the client based on the form ID.

  Therefore, the client can always acquire, display, input, etc. a client-specific (subordinate organization-specific) form from the server side based on the form ID.

  Since the client only needs to store formal information such as the form ID and name, even if the work becomes complicated, if the layout information is saved on the server side (DB), the memory in the client Occupying the storage area can be suppressed.

  As described above, according to the present embodiment, in the management of business information forms and business processes, settings such as form input and layout can be set in subordinate organizations (use departments).

  In other words, when developing business systems, only engineers (information system departments) that possessed IT expertise until now were able to do it, but even departments that do not possess IT expertise and actually use business systems. Development (form definition, process definition, master definition) is now possible. Form definition, process definition, and document management can be integrated to develop a business system. Among them, "form definition according to the role of the business process", "form display / input permission control processing", "between each item of the form Can now be easily defined. That is, it becomes easy for the user to edit the development environment.

  Processing and control can be performed by software processing by a CPU (Central Processing Unit) or GPU (Graphics Processing Unit), ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate) hardware hardware.

  In the above-described embodiment, the configuration and the like illustrated in the accompanying drawings are not limited to these, and can be appropriately changed within a range in which the effect of the present invention is exhibited. In addition, various modifications can be made without departing from the scope of the object of the present invention.

  Each component of the present invention can be arbitrarily selected, and an invention having a selected configuration is also included in the present invention.

  In addition, a program for realizing the functions described in the present embodiment is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read into a computer system and executed to execute processing of each unit. May be performed. The “computer system” here includes an OS and hardware such as peripheral devices.

  The present invention can be used as a business process management system.

A ... business process management system, 1 ... server, 21 ... database DB, 23 ... client, 31 ... control unit, 31-1 ... form editing (creation) processing unit, 33 ... communication unit, 35 ... input unit, 37 ... display Part, 41 ... memory.

Claims (7)

A server connected to a network with the client and associated with a database storing various data tables, the server having a table management unit for managing the various data tables stored in the database; In the business management system, the client includes a form editing processing unit that creates form layout information. The server receives the layout information received from the client together with a form ID for uniquely identifying the form. A business management system characterized by storing in a database,
The form editing processing unit
A business management system, wherein the form is set in association with an attribute of a login user who logs in to the server from the client by an input operation in the client. The form editing processing unit
The business management system according to claim 1, wherein display and non-display of items can be set for each item of the form in association with an attribute of a login user to the client. The form editing processing unit
The business management system according to claim 1, wherein a form can be arbitrarily set for each node of the business process. The form editing processing unit
4. The business according to claim 3, wherein whether or not the item is required to be input and whether or not editing is prohibited can be set for each node as an item attribute by an input operation in the client. Management system. A server connected to a network with the client and associated with a database storing various data tables, the server having a table management unit for managing the various data tables stored in the database; In the business management system, the client includes a form editing processing unit that creates form layout information. The server receives the layout information received from the client together with a form ID for uniquely identifying the form. A client in a business management system characterized by being stored in a database,
The form editing processing unit
The form is set in association with an attribute of a login user who logs in to the server from the client by an input operation in the client. A server connected to a network with the client and associated with a database storing various data tables, the server having a table management unit for managing the various data tables stored in the database; In the business management system, the client includes a form editing processing unit that creates form layout information. The server receives the layout information received from the client together with a form ID for uniquely identifying the form. A server in a business management system characterized by storing in a database,
A layout that is set in association with an attribute of a login user who logs in to the server from the client by an input operation on the client, and a form ID corresponding to a task for uniquely identifying the form is selected from the client and requested to be transmitted A server that transmits information to the client to prompt display of a form. A server connected to a network with the client and associated with a database storing various data tables, the server having a table management unit for managing the various data tables stored in the database; In the business management system of the present invention, the client executes a form editing process step of creating form layout information, and the server receives the layout information received from the client together with a form ID for uniquely identifying the form. A business management method in a business management system characterized by executing steps stored in a database,
The form editing process step includes:
A business management method comprising the steps of setting the form in association with an attribute of a login user who logs in to the server from the client by an input operation on the client.

Images