JP2015170263A - workflow integration system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve efficiency of setup of an approval authority and authentication processing for an approver by absorbing differences in managerial positions for each company when integrating workflow systems of a plurality of companies.SOLUTION: A duty position information management DB 1023 that stores duty position information in which a plurality of duty positions as a category of managerial positions are presented, the plurality of duty positions include an approval authority duty position to which a written application approval authority is approved, and the managerial positions used in each company are associated with any duty positions of the plurality of duty positions. When a membership of A company is selected as an approver of written applications created in the A company, a workflow processing unit 1013 determines whether or not the duty position of the membership matches the duty position of the A company associated with the approval authority duty position in the duty position information.

Description

  The present invention relates to a workflow system.

Companies and the like use a workflow system to generate application forms and to approve generated application forms.
There exists a thing of patent document 1 as such a workflow system.

JP 2005-38172 A

It is assumed that the workflow system of Patent Document 1 is used for each company.
For this reason, it is necessary to prepare a workflow system for each company. However, the workflow systems operated by each company often have similar configurations and functions. In particular, the workflow systems of multiple companies are integrated among affiliated companies. An environment that can be operated is desired.
When the workflow systems of multiple companies are integrated, it is necessary to set the approval authority for the application form based on the title of each company.
However, the hierarchical structure of job titles and job titles differ from company to company, and even when the workflow systems of multiple companies are integrated, there is a problem in that approval authority setting and authentication processing for the approver are complicated.

  The present invention has been made in view of such circumstances, and, when integrating a plurality of workflow systems, absorbs the difference in position for each company and makes the setting of approval authority and the authentication process for the approver efficient. Is the main purpose.

The workflow integration system according to the present invention includes:
A workflow integration system that integrates the workflow systems of multiple companies,
Multiple job categories that are categories of job titles are shown, and multiple job categories include approval authority job categories that allow application approval rights, and job titles used by each company are the above job category categories A job category information storage unit that stores job category information associated with any job category, and
When a member of any company is selected as an approver of an application generated by the company, the company whose position is associated with the approval authority position category in the position category information And an approver job title determination unit that determines whether or not the job title matches the current job title.

  According to the present invention, by consolidating the positions used in each company into the position categories, it is possible to absorb the difference in position for each company and to make the approval authority setting and the authentication process for the approver more efficient. .

FIG. 3 is a diagram illustrating an example of a system configuration according to the first embodiment. FIG. 5 is a diagram showing an example of company information according to the first embodiment. FIG. 4 is a diagram illustrating an example of user information according to the first embodiment. FIG. 4 shows an example of position information according to the first embodiment. The figure which shows the example of the application authority person information which concerns on Embodiment 1. FIG. The figure which shows the example of the proxy authorization authority information which concerns on Embodiment 1. FIG. FIG. 5 is a diagram showing an example of notification mail setting information according to the first embodiment. The flowchart figure which shows the production | generation procedure of the application form which concerns on Embodiment 1. FIG. The flowchart figure which shows the approver selection procedure of the application which concerns on Embodiment 1. FIG. The flowchart figure which shows the transmission procedure of the notification mail which concerns on Embodiment 1. FIG. FIG. 3 is a diagram illustrating a hardware configuration example of the workflow integration system according to the first embodiment.

Embodiment 1 FIG.
FIG. 1 shows a system configuration example including a workflow integration system 100 according to the present embodiment.

In FIG. 1, a workflow integration system 100 includes a company A workflow system 101a for company A, a company B workflow system 101b for company B, and the like, and a DB system 102.
The company A workflow system 101a, the company B workflow system 101b, etc. are collectively referred to as the workflow system 101.
In FIG. 1, only the company A workflow system 101a and the company B workflow system 101b are shown, but the workflow system 101 for other companies may be implemented.

The workflow integration system 100 is connected to a company A user terminal device 200, a company B user terminal device 300, a system administrator terminal device 400, and an ID registration revision authority user terminal device 500.
The company A user terminal device 200 is a terminal device used by a user of company A.
The company B user terminal device 300 is a terminal device used by a user of company B.
In FIG. 1, only one company A user terminal device 200 and one company B user terminal device 300 are illustrated, but it is assumed that there are a plurality of each.
The system administrator terminal device 400 is a terminal device used by a system administrator who manages the workflow integration system 100.
The ID registration amendment authority terminal device 500 is a terminal device used by an ID registration amendment authority authorized to modify or abolish user ID (Identifier) registration.
In FIG. 1, only one ID registration revision authority user terminal device 500 is illustrated, but it is assumed that there is an ID registration revision authority user terminal device 500 for each company.

Next, the internal configuration of the workflow integration system 100 will be described.
First, a configuration example of the workflow system 101 will be described.
Here, the configuration example of the company A workflow system 101a will be described as a representative, but the configuration of the company B workflow system 101b is assumed to be the same.

The application information management DB 1011 manages application forms generated by the company A.
The application / approval history management DB 1012 manages application / approval history information indicating application creation history and application approval history in the company A.

The workflow processing unit 1013 performs processing related to the workflow.
For example, the workflow processing unit 1013 determines whether the applicant who intends to create an application has the authority to create an application (application authority).
Further, the workflow processing unit 1013 determines whether or not the approver designated by the application authority has the authority to approve the application form (approval authority).
The workflow processing unit 1013 corresponds to an example of an approver position determination unit and an application authority attribute determination unit.

A person who has application authority is called an application authority.
The applicant is a person who wants to generate an application, and the applicant is not necessarily an authorized person.
An applicant who has no application authority (an applicant who is not an application authority) is prohibited from generating an application by the workflow processing unit 1013.
A person with approval authority is called an approval authority.
A person who is designated as a person to be approved by the application authority is called an approver.
An approver is not necessarily an approval authority.
An approver without approval authority (an approver who is not an approval authority) is prohibited from approving the application by the workflow processing unit 1013.
Further, a person who has the authority to approve on behalf of the approval authority (proxy approval authority) is called a proxy approval authority.

  The application / approval history management unit 1014 updates the application / approval history information in the application / approval history management DB 1012 when an application is generated or when the application is approved or denied.

  The notification mail transmission unit 1015 generates a notification mail notifying that an application form that requires approval has been generated, and transmits the notification mail to the terminal device used by the approval authority (and the proxy approval authority).

The company information management DB 1021 manages company information that is information about a company that uses the workflow integration system 100.
The company information is information shown in FIG. 2, for example, and includes a company ID, a company name, an address, and a telephone number.

The user information management DB 1022 manages user information that is information of users belonging to each company.
The user information is, for example, information shown in FIG. 3 and includes a company ID, a user ID, a user name, a user affiliation, a user title, a mail address, and a password.

The position information management DB 1023 manages position information.
The position information is, for example, information shown in FIG.
In the position information, a plurality of positions (position categories) that are categories of positions are indicated, and positions corresponding to the positions are indicated for each company.
In the example of FIG. 4, officers, department heads, and organization heads are shown as positions.
In Company A (Company ID: 001), there are presidents, vice presidents, general managers, and section managers as titles. being classified.
In Company B (Company ID: 002), there are presidents, vice presidents, managing directors, general managers, general managers, general managers, section managers, general managers. Section managers are classified as department heads, and section managers are classified as organization heads.
Further, the position includes an approval authority position (approval authority position category) in which the application authority is approved. In the example of FIG. 4, the department manager is granted the approval authority.
The position information corresponds to an example of position category information, and the position information management DB 1023 corresponds to an example of a position category information storage unit.

The application authority information management DB 1024 manages application authority information.
Application authority information is, for example, information shown in FIG.
In the application authority information, the attributes of the application authority are shown for each company and each application.
In the example of FIG. 5, the affiliation is described as the attribute of the application authority.
The application authority information management DB 1024 corresponds to an example of an application authority information storage unit.

The proxy approval authority information management DB 1025 manages proxy approval authority information.
The proxy approval authority information is, for example, information shown in FIG.
In the proxy approval authority information, the position (proxy approval authority position) in which the proxy approval authority is permitted is indicated for each company.
In the example of FIG. 6, the proxy approval authority is given to a person whose position is classified as position: organization head for both company A (company ID: 001) and company B (company ID: 002).

The notification mail setting information management DB 1026 manages the notification mail setting information.
The notification mail setting information is, for example, information shown in FIG.
The notification mail setting information indicates the transmission destination of the notification mail for each department of the company.
In the example of FIG. 7, the planning department of company A defines an approval authority and a proxy approval authority as destinations for notification mail, and the accounting department defines only an approval authority as a notification mail destination. .
In FIG. 7, a notification mail transmission destination is defined for each company department, but a notification mail transmission destination may be defined for each company.
The notification mail setting information management DB 1026 corresponds to an example of a notification mail setting information storage unit.

User information in the user information management DB 1022 is registered / updated by an ID registration revision authority.
The system administrator registers / updates other DB information.

Next, an operation example of the workflow integration system 100 according to the present embodiment will be described with reference to FIGS.
FIG. 8 is a flowchart showing an application form generation procedure.
FIG. 9 is a flowchart showing a procedure for selecting an approver of the application form.
FIG. 10 is a flowchart showing a notification mail transmission procedure.
Hereinafter, an example in which a user of company A accesses the workflow system 101a using the company A user terminal device 200 will be described.

In FIG. 8, when an applicant who is a user of company A accesses the workflow system 101a using the company A user terminal device 200, the workflow processing unit 1013 performs login authentication (S801).
For example, the company A user terminal device 200 transmits the user ID and password of the applicant to the workflow processing unit 1013, and the workflow processing unit 1013 performs login authentication using the user ID and password.
Here, it is assumed that there is an access from a user whose user ID is “001-34567” (FIG. 3).

If the login authentication of S801 is successful, the workflow processing unit 1013 transmits an application form generation screen to the company A user terminal device 200, and the applicant generates an application form ID of the application form to be generated. To enter.
Thereby, the application form ID is transmitted from the A company user terminal device 200, and the workflow processing unit 1013 receives the application form ID transmitted from the A company user terminal device 200 (S802).
Here, it is assumed that “JKL-001” is received as the application form ID.

Next, the workflow processing unit 1013 specifies the affiliation location of the applicant from the user ID received in S801 (S803).
Since the user ID received in S801 is “001-34567”, the workflow processing unit 1013 searches the record including the user ID in FIG. 3 and sets the applicant's affiliation as “Planning Department 1st Section”. Identify.

Next, the workflow processing unit 1013 identifies the application authority attribute for the application form ID received in S802 (S804).
Since the application form ID received in S802 is “JKL-001”, the workflow processing unit 1013 specifies the application authority attribute for the application form ID received in S802 as “planning department” from FIG.

Next, the workflow processing unit 1013 determines whether the applicant satisfies the application authority attribute (S805).
If the applicant satisfies the application authority attribute, the workflow processing unit 1013 permits the application to generate an application form (S806). If the application authority attribute is not satisfied, the workflow processing unit 1013 The generation of the application form by the applicant is prohibited (S807).
Since the affiliation specified in S803 is “Planning Department 1st Section” and the application authority attribute specified in S804 is “Planning Department”, in this case, the application authority attribute is satisfied and the application is generated. Allowed.

In FIG. 9, when the applicant generates an application, the workflow processing unit 1013 receives the approver's user ID from the company A user terminal device 200 (S901).
Here, for example, it is assumed that “001-12345” (FIG. 3) is transmitted as the user ID of the approver.

Next, the workflow processing unit 1013 identifies the affiliation and position of the approver from the user ID received in S901 (S902).
Since the user ID received in S901 is “001-12345”, the workflow processing unit 1013 searches the record including the user ID in FIG. 3 and identifies the approver's affiliation as “planning department”. Also, the position of the approver is identified as “Planning Department”.

Next, the workflow processing unit 1013 identifies a post having an approval authority (S903).
Specifically, the workflow processing unit 1013 specifies from FIG. 4 that the position belonging to the department head who has the approval authority position is “Department Manager” in Company A.

Next, the workflow processing unit 1013 determines whether the approver has the approval authority (S904).
If the approver has the authorization authority, the workflow processing unit 1013 permits the application form to be transmitted to the workflow processing unit 1013 (S905).
On the other hand, if the approver has no approval authority, the workflow processing unit 1013 prohibits the application form from being transmitted to the workflow processing unit 1013 (S906).
Since the position specified in S902 and the position specified in S903 are both “department managers” and the approver is the same affiliation (planning department) as the applicant, the approver is authorized to approve.

  When the transmission of the application form is permitted in S905, the application form is transmitted from the company A user terminal device 200, and in the company A workflow system 101a, the workflow processing unit 1013 registers the application form in the company information management DB 1021, and The application / approval history management unit 1014 updates the application / approval history information in the application / approval history management DB 1012.

In FIG. 10, the notification mail transmitting unit 1015 specifies the transmission destination of the notification mail with reference to FIG. 7 (S1001).
In the example of FIG. 7, an approval authority and a proxy approval authority are defined as the transmission destination of the notification mail for company A.
For this reason, the notification mail transmitting unit 1015 identifies the transmission destination of the notification mail as an approval authority and proxy approval.

When a proxy authority is included in the destination of the notification mail (YES in S1002), the notification mail transmission unit 1015 transmits a notification mail to the approval authority and the proxy approval authority (S1003).
Specifically, the notification mail transmission unit 1015 recognizes from FIG. 6 that the authorized approval authority of company A is “organization manager”, and from FIG. 4, “organization manager” is “section manager” in company A. Is identified.
Furthermore, since the applicant's affiliation is “Planning Department 1st Section”, the notification mail transmission unit 1015 displays a record in which the affiliation is “Planning Department 1st Section” and the title is “section manager”. Search in 3.
As a result, the notification mail transmission unit 1015 searches for a record having the user ID “001-23456”, and sets the mail address included in this record as the mail address of the proxy approval authority.
Further, the notification mail transmitting unit 1015 sets the mail address included in the record searched in S902 of FIG. 9 as the mail address of the authorized person.
The notification mail transmission unit 1015 transmits a notification mail including the mail address specified in this way.

  When the proxy authority is not included in the destination of the notification mail (NO in S1002), the notification mail transmission unit 1015 transmits the notification mail only to the approval authority (S1004).

  As described above, according to the present embodiment, in the workflow integrated system in which the workflow systems of a plurality of companies are integrated, the positions used in each company are aggregated into positions, thereby absorbing the differences in the positions of each company. Thus, it is possible to streamline the setting of approval authority and the authentication process for the approver.

  In this embodiment, the attributes of the application authority are defined for each company and for each application. Therefore, even if the workflow system of multiple companies is integrated, the application is applied for each company and for each application. It is possible to accurately determine whether a person has application authority.

  Further, in the present embodiment, since the transmission destination of the notification mail is defined for each company or for each department of the company, the notification mail can be transmitted according to the actual state of the organization.

  In addition, this invention is not limited to this Embodiment, A various change is possible as needed.

Finally, a hardware configuration example of the workflow integration system 100 shown in the present embodiment will be described with reference to FIG.
The workflow integration system 100 is a computer, and each element of the workflow integration system 100 can be realized by a program.
As a hardware configuration of the workflow integrated system 100, an arithmetic device 901, an external storage device 902, a main storage device 903, a communication device 904, and an input / output device 905 are connected to a bus.

The arithmetic device 901 is a CPU (Central Processing Unit) that executes a program.
The external storage device 902 is, for example, a ROM (Read Only Memory), a flash memory, or a hard disk device.
The main storage device 903 is a RAM (Random Access Memory).
The communication device 904 is, for example, a NIC (Network Interface Card).
The input / output device 905 is, for example, a mouse, a keyboard, a display device, or the like.

The program is normally stored in the external storage device 902, and is loaded into the main storage device 903 and sequentially read into the arithmetic device 901 and executed.
The program is a program that realizes a function described as “unit” shown in FIG.
Further, an operating system (OS) is also stored in the external storage device 902. At least a part of the OS is loaded into the main storage device 903. ”Is executed.
In the description of the present embodiment, “determining”, “determining”, “extracting”, “specifying”, “setting of”, “registering”, “selecting” ”,“ Generate ”,“ Received ”, etc., information, data, signal values, and variable values indicating the results of the processing are stored in the main storage device 903 as files.

  Note that the configuration in FIG. 11 is merely an example of the hardware configuration of the workflow integration system 100, and the hardware configuration of the workflow integration system 100 is not limited to the configuration described in FIG. Also good.

  DESCRIPTION OF SYMBOLS 100 Workflow integrated system, 101 Workflow system, 102 DB system, 200 A company user terminal device, 300 B company user terminal device, 400 System administrator terminal device, 500 ID registration revision authority person terminal device, 1011 Application information management DB, 1012 Application / approval history management DB, 1013 Workflow processing unit, 1014 Application / approval history management unit, 1015 Notification mail transmission unit, 1021 Company information management DB, 1022 User information management DB, 1023 Position information management DB, 1024 Application authority information management DB, 1025 Proxy approval authority information management DB, 1026 Notification mail setting information management DB.

Claims (5)

A workflow integration system that integrates the workflow systems of multiple companies,
Multiple job categories that are categories of job titles are shown, and multiple job categories include approval authority job categories that allow application approval rights, and job titles used by each company are the above job category categories A job category information storage unit that stores job category information associated with any job category, and
When a member of any company is selected as an approver of an application generated by the company, the company whose position is associated with the approval authority position category in the position category information And an approver job title determination unit for determining whether or not the job title matches the current job title. The approver title determination unit
Claims characterized by not permitting approval of the application by the member when the position of the member selected as the approver of the application form does not match the position associated with the approval authority position category. Item 4. The workflow integration system according to item 1. The workflow integration system further includes:
For each company and for each application, an application authority information storage unit that stores application authority information indicating the attributes of the application authority,
When a member of any company tries to generate any application, whether or not the attribute of the member matches the attribute of the application authority of the application of the company in the application authority information The workflow integration system according to claim 1, further comprising an application authority attribute determination unit that determines whether or not. The application authority attribute determination unit
4. The generation of the application by the member is not permitted when the attribute of the member who is to generate the application does not match the attribute of the application authority of the application of the company. The workflow integration system described in 1. The workflow integration system includes:
A notification email sending unit for sending a notification email, which is an email notifying that an application requiring approval has been generated;
Whether to include, in addition to an approval authority having approval authority, a proxy approval authority having proxy approval authority for performing approval on behalf of the approval authority, in addition to the approval authority having approval authority, in the transmission destination of the notification mail for each company or each department of the company A notification mail setting information storage unit for storing notification mail setting information indicating whether or not,
The notification mail sending unit
When an application form is generated by a company or department whose inclusion of a proxy approval authority is included in the notification mail destination, the notification mail is sent to the terminal device used by the proxy approval authority. The workflow integrated system according to claim 1, wherein the workflow is integrated.

Images