JP6042477B2 - Circulation management system, circulation management method and circulation management program - Google Patents

Description

  The present invention relates to a circulation management system for distributing an application to a circulation destination, a circulation management method, and a circulation management program.

  An electronic workflow system may be used in an approval process in an organization such as a company. In this electronic workflow system, various applications created by the applicant are electronically distributed via a network, and confirmation work for approval is performed.

  An approval management system for efficiently realizing circulation management for approval for an application has been studied (for example, see Patent Document 1). The approval management server described in this document registers a business step included in a business process in the system setting process. Further, user registration processing and circulation route registration processing are executed. When an application is registered by specifying a business process in the approval management server, a circulation process is performed for the business steps constituting the business process. Based on the registered circulation route, when the circulation process in the preceding business step is completed, the processing is expanded to the subsequent business step. When all the business steps are completed and finally approved, the business process is terminated.

JP 2013-246523 A

  Here, when the application contents are confirmed step by step in a predetermined order, circulation is performed with the circulation destinations arranged in series. On the other hand, when having multiple people confirm the application contents at the same time, the circulation destinations are arranged in parallel. However, the distribution route of applications varies depending on the application contents. In some cases, it may be partially circulated in series or in parallel. If it takes time to set up such a circulation route, it is difficult to apply efficiently.

  Usually, departments constituting the organization are set as the circulation destination, but it is the person in charge of the circulation destination department that confirms the application contents. Therefore, in the circulation of the application, it is necessary to set a circulation destination having a different granularity like a department or a person in charge, and it takes time and effort to set a circulation route. In addition, after setting the circulation route, it may be necessary to change the circulation route such as changing or adding a circulation destination. If this change takes time, smooth circulation is difficult.

  The present invention has been made to solve the above problems, and provides a circulation management system, a circulation management method, and a circulation management program for efficiently distributing an application to a circulation destination. is there.

(1) A circulation management system that solves the above-mentioned problem is a system in which serial / parallel identification information is given to an application information storage unit that stores application contents and a circulation destination department that is given serial / parallel identification information. A distribution route information storage unit for storing a distribution destination information for specifying a confirmation status in the distribution destination person in charge, and managing a distribution of applications. A control unit is provided. And the said control part acquires the information regarding a division and a circulation destination department with a circulation application from a user terminal, and identifies line number, serial information, or parallel information with respect to a division and a circulation destination department A table format in which serial / parallel identification information is given and recorded as circulation destination information in the circulation route information storage unit, and the line number is used as a column item for the series / parallel identification information, classification, and circulation destination department And displaying the routing route confirmation screen in which the routing destination is grouped and the hierarchy is generated using the column item and the row number to the user terminal, and in the table format, a plurality of the same hierarchy When the group including the department is selected and the instruction to change the circulation order of the group is acquired, the circulation destination information is generated by changing the circulation order of a plurality of departments included in the group, Selected in the department to distribute In this department, a person in charge of circulation is selected, and in the department to which the circulation is made, serial number identification information for identifying a line number, serial information or parallel information of the person in charge of circulation is given, and the circulation The circulatory contact person in the circulatory destination department confirmed in the circulatory route confirmation screen is recorded in the circulatory route information storage unit as the circulatory destination information in association with the predecessor, As for the distribution destination associated with the same parallel information as the series-parallel identification information, the application contents stored in the application information storage unit are distributed at the same time and the distribution destination associated with the serial information. Is distributed on the condition that the confirmation status of the preceding circulation destination is confirmed according to the line number. Thereby, it is possible to distribute the application using the circulation route created in the form of a table constituted by a matrix.

(2) In the circulation management system, further, in the circulation route confirmation screen, serial / parallel identification information, division, and circulation destination are output as column items, and the column item and the row number are used to A circulation route in which circulation destinations are grouped is generated . This ensures that it is possible to use the tabular column items, by grouping circulation destination, it generates efficiently circulated path.

(3) The distribution management system further generates a group of the grouped distribution destinations using the column item, and includes the grouped distribution destination using the hierarchy. Generate an attached route . This ensures that it is possible to use a hierarchy, to produce efficiently circulated path.

  (4) In the circulation management system, it is preferable to acquire a line number designated on the circulation path confirmation screen and generate a circulation path to which a new circulation destination is added based on the line number. . Thereby, a new circulation destination can be added efficiently.

  (5) In the circulation management system, when adding the new circulation destination, the serial / parallel identification information of the circulation destination of the line number designated on the circulation route confirmation screen is changed to the new circulation destination. It is preferable to set in the circulation destination information and record in the circulation route information storage unit. As a result, the subsequent circulation destination can be set using the information of the preceding circulation destination.

  (6) In the circulation management system, for a department set as a circulation destination, a member list screen of a person in charge belonging to the department is output to the user terminal and selected on the member list screen. It is preferable to record the person in charge in the circulation route information storage unit as circulation destination information. As a result, the person in charge in the organization can be designated as the circulation destination.

  (7) In the circulation management system, when a plurality of persons in charge are selected on the member list screen, line numbers are assigned according to the attributes of the persons in charge, and the circulation is made as distribution destination information. It is preferable to record in the route information storage unit. Thereby, the circulation order different from an organization structure can be set efficiently. For example, in the organizational structure, the order of senior positions can be circulated later.

  (8) In the circulation management system, in the circulation route recorded in the circulation route information storage unit, the circulation destination is a subsequent circulation destination of the preceding circulation destination to which the application has been distributed, and has not been distributed It is preferable that the subsequent circulation destination is specified and the change of the subsequent circulation destination is permitted in the preceding circulation destination. Thereby, the subsequent circulation destination can be changed in the circulation destination.

  (9) In the circulation management system, in the circulation path recorded in the circulation path information storage unit, when the preceding circulation destination and the subsequent circulation destination are arranged in series information, It is preferable to allow the change of the subsequent circulation destination. Accordingly, it is possible to allow the subsequent change of the circulation destination in consideration of the series-parallel relationship.

  (10) In the circulation management system, it is preferable that the attribute of the preceding circulation destination is specified and the change of the subsequent circulation destination is permitted based on the attribute. Thereby, it is possible to allow the subsequent circulation destination to be changed in consideration of the attribute of the circulation destination.

  According to the present invention, it is possible to efficiently distribute an application to a circulation destination.

The system schematic of this embodiment. It is explanatory drawing of the data used by this embodiment, (a) is a department information storage part, (b) is a user information storage part, (c) is an application information storage part, (d) is an attachment file storage part, ( e) Explanatory drawing of the data recorded on the circulation path | route information storage part. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the department setting screen used by this embodiment. It is explanatory drawing of the department setting screen used by this embodiment, Comprising: (a) is a distribution destination department display column, (b) is explanatory drawing of a department circulation path | route. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. It is explanatory drawing of the process sequence of this embodiment, (a) is a serial-parallel change process of a circulation destination department, (b) is a deletion process of a circulation destination department, (c) is a movement of a circulation destination department. Explanatory drawing of a process. It is explanatory drawing of the addition process of the distribution destination department of this embodiment, (a) is the department setting screen before a process, (b) is the department circulation route before a process, (c) is the department setting after a process Screen, (d) is an explanatory diagram of a department circulation route after processing. It is explanatory drawing of the parallelization process of the distribution destination of this embodiment, (a) is the department setting screen before a process, (b) is the department circulation route before a process, (c) is the department setting after a process Screen, (d) is an explanatory diagram of a department circulation route after processing. It is explanatory drawing of serialization of the circulation destination of this embodiment, (a) is a department setting screen before processing, (b) is a department circulation path before processing, (c) is a department setting screen after processing. , (D) is an explanatory diagram of a department circulation route after processing. It is explanatory drawing of the deletion process of the transmission destination department of this embodiment, (a) is the department setting screen before a process, (b) is the department circulation route before a process, (c) is the department setting after a process Screen, (d) is an explanatory diagram of a department circulation route after processing. It is explanatory drawing of the transfer process of the transfer destination department of this embodiment, (a) is the department setting screen before a process, (b) is the transfer destination department display column after a carry-over process, (c) is a carry-down process. Explanatory drawing of the subsequent distribution destination department display column. It is explanatory drawing of the change process of the circulation destination department of this embodiment, (a) is a change rule, (b) is a process sequence, (c) is explanatory drawing of a department circulation path | route. Explanatory drawing of the process sequence of this embodiment. It is explanatory drawing of the process sequence of this embodiment, (a) is a parallel process of a person in charge of distribution, (b) is a serialization process of a person in charge of distribution, (c) is a person in charge of distribution (D) is an explanatory view of a transfer destination person in charge movement process. It is explanatory drawing of the department setting screen used by this embodiment, Comprising: (a) is a department selection screen, (b) is explanatory drawing of a person in charge setting screen. It is explanatory drawing of the addition process of the circulation destination of this embodiment, (a) is a person-in-charge setting screen before processing, (b) is a person-in-charge circulation route before processing, and (c) is in charge after processing. The person setting screen, (d) is an explanatory diagram of the person-in-charge circulation route after processing. It is explanatory drawing of the parallel process of a circulation person in charge of this embodiment, (a) is a person-in-charge setting screen before processing, (b) is a person-in-charge circulation route before processing, and (c) is processing. The person-in-charge setting screen in the middle, (d) is an explanatory diagram of the person-in-charge circulation route in the middle of processing. It is explanatory drawing of the parallelization process of the circulation person in charge of this embodiment, Comprising: (a) is a person-in-charge setting screen in the middle of processing, (b) is explanatory drawing of the person-in-charge circulation path in the middle of processing. It is explanatory drawing of the parallelization process of the person in charge of circulation of this embodiment, Comprising: (a) is a person-in-charge setting screen after processing, (b) is explanatory drawing of the person-in-charge circulation path after processing. It is explanatory drawing of the parallel process of a circulation person in charge of this embodiment, (a) is a person-in-charge setting screen before processing, (b) is a person-in-charge circulation route before processing, and (c) is processing. The person-in-charge setting screen in the middle, (d) is an explanatory diagram of the person-in-charge circulation route in the middle of processing. It is explanatory drawing of the parallel process of a circulation person in charge of this embodiment, (a) is a person-in-charge setting screen in the middle of processing, (b) is a person-in-charge circulation route in the middle of processing, (c) is a process The person-in-charge setting screen after, (d) is an explanatory diagram of the person-in-charge circulation route after processing. It is explanatory drawing of the change process of the person in charge of circulation of this embodiment, Comprising: (a) is a change rule, (b) is explanatory drawing of a process sequence. It is explanatory drawing of the change process of the person in charge of distribution of this embodiment, (a) is a person in charge circulation route, (b) is the changeable range of the person in charge A, (c) is a change in person in charge B Possible range, (d) is changeable range of person in charge C, (e) is changeable range of person in charge D, (f) is changeable range of person in charge F, (g) is change of person in charge E or G The possible range, (h) is an explanatory diagram of the changeable range of the person in charge H. It is explanatory drawing of the circulation confirmation process of this embodiment, (a) is a process sequence, (b) is explanatory drawing of an application content display screen.

  Hereinafter, an embodiment embodying the present invention will be described with reference to FIGS. In the present embodiment, the application drafted by the applicant will be described as a circulation management system, a circulation management method, and a circulation management program for supporting circulation to a circulation destination (department or person in charge).

  In the present embodiment, as shown in FIG. 1, a circulation management server 20 as a circulation management system is used to support circulation of an application. The circulation management server 20 is connected to the user terminal 10 and the directory management server 40 via a network.

  The user terminal 10 is a computer terminal used by an applicant or a user in charge of circulation. The applicant makes various applications using the user terminal 10. The user who is the circulation destination of the confirmer who performs approval or the like confirms the application content using the user terminal 10. Then, the confirmer confirms the contents of the application and inputs “approval / circulation”, “send back”, “denial”, and the like. The user terminal 10 includes a display unit such as a display (not shown) and an input unit such as a keyboard and a pointing device.

  The directory management server 40 is a computer system that provides a directory service that collectively manages users and network resources. For this reason, a user database storing information on users and organizations using the network is provided.

  In the user database, a user management record for managing users who use the circulation management server 20 is recorded. This user management record is recorded when user registration is performed. In the user management record, data relating to the user ID, name, contact information, affiliation, job title, and authentication code is recorded.

In the user ID data area, data relating to an identifier (for example, an employee number in a company) for specifying a user of the circulation management server 20 is recorded.
Data relating to the name of the user is recorded in the name data area.
In the contact data area, data related to the user's contact information (for example, mail address or telephone number) is recorded.

In the affiliation data area, data relating to an identifier (department ID) for specifying the department to which the user belongs is recorded.
In the post data area, data relating to an identifier for specifying the post of the user is recorded. With this position, the authorization authority can be specified.
In the authentication code data area, data related to authentication information (for example, a password) when performing user authentication is recorded.

  The circulation management server 20 is a server computer for managing circulation of an application drafted by an applicant. As shown in FIG. 1, the circulation management server 20 includes a control unit 21, a department information storage unit 22, a user information storage unit 23, an application information storage unit 24, an attached file storage unit 25, and a circulation route information storage unit 26. It has.

  The control unit 21 includes a control unit including a CPU, a RAM, a ROM (not shown), and the like, and processes described later (a user authentication stage, a department path management stage, a person-in-charge path management stage, an application management stage, Each process such as the circulation management stage). The control unit 21 functions as a user authentication unit 211, an application management unit 212, a department route management unit 213, a person-in-charge route management unit 214, and a circulation management unit 215 by executing the circulation management program.

  The user authentication unit 211 executes processing for authenticating the user of the user terminal 10. The user authentication unit 211 acquires user authentication information (user ID and authentication code) from the user terminal 10. Further, the user authentication unit 211 uses the directory management server 40 to specify the accessed user. If the user authentication cannot be performed, an error message is transmitted to the user terminal 10. When user authentication is successful, the use of the circulation management server 20 is permitted.

In response to a request from the user terminal 10, the application management unit 212 executes processing for managing application drafting and circulation.
The department route management unit 213 executes processing for managing the circulation route for the circulation destination department of the application. The department route management unit 213 includes a memory that temporarily stores items selected on a department setting screen to be described later.

The person-in-charge route management unit 214 executes processing for managing the circulation route for the person in charge who confirms the application in the circulation destination department. The person-in-charge route management unit 214 includes a memory that temporarily stores items selected on a person-in-charge setting screen described later.
The distribution management unit 215 executes processing for supporting confirmation work (browsing, approval, etc.) at the distribution destination for the application.

  As shown in FIG. 2A, a department management record 220 for managing each department is recorded in the department information storage unit 22. This department management record 220 is recorded when a department is registered by an administrator. The department management record 220 includes data related to a department ID, a department name, a higher department ID, and a lower department ID.

In the department ID data area, data relating to an identifier for identifying each department is recorded.
Data related to the name of the department is recorded in the department name data area.
In the upper department ID data area, data relating to an identifier (department ID) for specifying the department of the upper organization of this department is recorded.
In the lower department ID data area, data relating to an identifier (department ID) for specifying a department of a subordinate organization of this department is recorded.

  As shown in FIG. 2B, a user management record 230 for managing users of the circulation management server 20 is recorded in the user information storage unit 23. This user management record 230 is recorded when user information is acquired from the directory management server 40. The user management record 230 includes data related to the user ID, name, affiliation, title, and role name.

Data relating to an identifier for identifying each user is recorded in the user ID data area.
Data relating to the name of the user is recorded in the name data area.
In the affiliation data area, data relating to an identifier (department ID) for specifying the department to which the user belongs is recorded. In the present embodiment, organization names are recorded in each data area in order from the upper organization to the lower organization. In the present embodiment, a department name (eg, “A department”), a team name belonging to this department (eg, “B team”), and the like are recorded.

In the post data area, data relating to the post of the user is recorded. In the present embodiment, for example, “Investigator”, “Counselor”, “Deputy Director”, etc. are recorded as positions. If there is no title, this data area is left blank.
In the role name data area, data relating to an identifier for specifying the role of the user is recorded. By this role name, a specific authorized person having a predetermined authority can be specified.

  As shown in FIG. 2C, the application information storage unit 24 records an application management record 240 for managing the proposed application. The application management record 240 is recorded when an application drafted by the applicant is registered. The application management record 240 includes data relating to an application ID, an applicant, an application date, contents, and a status.

Data relating to an identifier for identifying each application is recorded in the application ID data area.
In the applicant data area, data relating to an identifier (user ID) for identifying the user who has made this application is recorded.

In the application date data area, data relating to the date on which this application was drafted is recorded.
In the content data area, data relating to the content of this application is recorded.
In the status data area, a flag for specifying the confirmation status of the application is recorded. In this embodiment, a flag indicating “currently distributed” or “approved”, “send back”, “denied”, etc. set by the confirmer is recorded in this data area.

  As shown in FIG. 2D, the attached file storage unit 25 records supplementary material attached to the drafted application. This supplementary material is recorded when an attached file related to the application is registered. The supplementary material includes an attachment file 250 and a conversion file 251 associated with the application ID.

Data relating to an identifier for identifying each application is recorded in the application ID data area.
The attached file is a supplementary file attached by each applicant at the time of application.
The converted file is a file obtained by converting the attached file into a predetermined data format (for example, PDF format). Thereby, the file attached to the application can be browsed only with the commonly used PDF file browsing software.

  As shown in FIG. 2 (e), in the circulation route information storage unit 26, circulation route management data 260 relating to a route to which each application is circulated is recorded. This circulation route management data 260 is recorded when an application is registered by the applicant. Also, it is updated when it is corrected at the distribution destination. The circulation route management data 260 includes a department circulation route record 261 and a person-in-charge circulation route record 262. In the present embodiment, the circulation destination is recorded in a table format composed of a two-dimensional matrix. In the tabular form, an early circulation order is set for a circulation destination having a small line number. In addition, each item described later is set in correspondence with the column number. Using the items set for the respective column numbers, a group in which the circulation destinations are hierarchized is formed.

  This department circulation route record 261 includes data relating to an application ID, a line number, a task (serial parallel identifier, category), a department ID, and a status. Here, the task (series-parallel identifier), task (section), and department ID are items representing the first to third hierarchies, respectively. As will be described later, the first hierarchy includes the second hierarchy, and the second hierarchy includes the third hierarchy.

Data relating to an identifier for identifying each application is recorded in the application ID data area.
In the line number data area, data relating to an identifier for specifying the circulation order in the circulation route of this application is recorded.

In the task data area, data relating to the series-parallel identifier and the classification is recorded.
In the serial / parallel identifier data area, a flag relating to an identifier for specifying the relationship (serial or parallel) with the department of the subsequent row number is recorded. A group based on the first hierarchy is formed by the series-parallel identifier. When series is set, it is circulated to the succeeding department after completion of confirmation in the preceding department, and when parallel is set, it is circulated at the same time.

  In the division data area, data relating to the role of the department in circulation is recorded. This category includes, for example, drafting / application department, jurisdiction department, circulation department, and related department. By this division, a group based on the first hierarchy is formed.

In the department ID data area, data relating to an identifier for identifying the department to which the information is distributed is recorded. This department ID constitutes the third hierarchy.
In the status data area, a flag for specifying the confirmation status of this department in this circulation route is recorded. When the department circulation route record 261 is registered, it is blank at the beginning, and a confirmation flag is recorded when the circulation confirmation of all circulation destination persons belonging to this department is completed.

  The person-in-charge circulation route record 262 includes data on application ID, department ID, line number, task (serial parallel identifier, individual serial identifier), team, user ID, name, title, role name, and status. Is done. Here, the task (series-parallel identifier), the task (individual serial identifier), and the user ID are items representing the first to third layers, respectively. Also in this person-in-charge circulation route record 262, the first hierarchy includes the second hierarchy, and the second hierarchy includes the third hierarchy.

The person-in-charge circulation route record 262 is associated with the application ID and department ID of the department circulation route record 261.
In the line number data area, data relating to the circulation order in the department circulation route of the application is recorded.

In the task data area, data related to the serial / parallel identifier and the individual serial identifier is recorded.
In the serial / parallel identifier data area, data relating to an identifier for specifying the relationship (serial or parallel) with the person in charge of the subsequent row number is recorded. A group based on the first hierarchy is formed by the series-parallel identifier. When series is set, it is circulated to the subsequent person in charge after completion of confirmation by the preceding person in charge, and when parallel is set together, it is circulated at the same time.

  In the individual serial identifier data area, data relating to an identifier for specifying a group constituting a series in parallel is recorded. A group based on the second hierarchy is configured by the individual serial identifier.

  In the team data area, data relating to an identifier (team name) for identifying a team to which the person in charge of circulation belongs belongs and constitutes the department of circulation destination is recorded. The third level is composed of items below this team.

In the user ID data area, data relating to an identifier for identifying the person in charge of circulation is recorded.
In the name data area, data related to the name of the person in charge of distribution is recorded.
In the post data area, data relating to the post of the person in charge of distribution is recorded.
In the role name data area, data for specifying the role of the person in charge of distribution is recorded.

  In the status data area, a flag for specifying the confirmation status of the person in charge of circulation at this circulation route is recorded. When the person-in-charge circulation route record 262 is registered, it is blank at the beginning. When the person-in-charge completes circulation confirmation, a confirmed flag is recorded.

(Outline of drafting and circulation)
Next, the outline of drafting / circulation will be described with reference to FIG.
First, the control unit 21 of the circulation management server 20 executes a login process (step S1-1). Specifically, the applicant accesses the circulation management server 20 using the user terminal 10. In this case, the user authentication unit 211 of the control unit 21 of the circulation management server 20 outputs a login screen on the display of the user terminal 10. This login screen is provided with an input field for inputting a user ID and an authentication code. Then, the user authentication unit 211 uses the directory management server 40 to authenticate the user ID and authentication code acquired from the user terminal 10. If user authentication is not possible, the user authentication unit 211 transmits an error message to the user terminal 10 and rejects login to the circulation management server 20.

  When the user authentication is successful, the control unit 21 of the routing management server 20 executes a top screen display process (step S1-2). Specifically, the user authentication unit 211 of the control unit 21 outputs a top screen on the display of the user terminal 10. This top screen includes a draft application button, a circulation destination change button, a circulation confirmation button, and the like. Here, when drafting a new application, the draft application button is selected.

  In this case, the control unit 21 of the circulation management server 20 executes drafting application information acquisition processing (step S1-3). Specifically, the application management unit 212 of the control unit 21 outputs an application input screen on the display of the user terminal 10. Then, the applicant inputs the application content on this application input screen. When the application management unit 212 detects the completion of the input to the application input screen, the application management unit 212 generates an application management record 240 to which an application ID is assigned and records it in the application information storage unit 24. In this case, the application management unit 212 of the control unit 21 executes drafting department setting processing described later. Further, the application management unit 212 acquires the current date and time from the system timer, records it in the application date data area of the application management record 240, and stores the application content input on the application input screen in the content data area of the application management record 240. Record.

  Next, the control unit 21 of the circulation management server 20 executes an attachment file acquisition process (step S1-4). Specifically, the application management unit 212 of the control unit 21 outputs an attached file designation screen on the display of the user terminal 10. Here, when setting an attached file, the applicant designates the attached file using the user terminal 10. In this case, the application management unit 212 acquires the attached file specified in the user terminal 10 and registers it in the attached file storage unit 25 in association with the application ID.

  Next, the control unit 21 of the circulation management server 20 executes a file conversion process (step S1-5). Specifically, the application management unit 212 of the control unit 21 generates a converted file obtained by converting the acquired attached file into a predetermined data format. Then, the application management unit 212 registers the converted file associated with the application ID in the attached file storage unit 25.

Next, the control unit 21 of the circulation management server 20 executes an approval / circulation route setting process. In the approval / circulation route setting process, the distribution destination department and the circulation destination person in charge are set.
First, the control unit 21 of the circulation management server 20 executes a department circulation route setting process (step S1-6). Specifically, the department route management unit 213 of the control unit 21 registers the designated circulation destination department in the circulation route information storage unit 26. Details will be described later with reference to FIGS.

Next, the control unit 21 of the circulation management server 20 executes a person-in-charge circulation route setting process (step S1-7). Specifically, the person in charge route management unit 214 of the control unit 21 registers the person in charge of the designated circulation destination in the circulation route information storage unit 26. Details will be described later with reference to FIGS.
Then, when the setting of the circulation route is completed, the circulation of the application is started. In this case, the circulation management unit 215 of the control unit 21 records a flag indicating “in circulation” in the status data area of the application management record 240 of the application information storage unit 24.

When confirming the contents of circulation, the circulation confirmation button is selected on the top screen.
In this case, the control unit 21 of the circulation management server 20 executes a circulation confirmation process (step S1-8). Specifically, the circulation management unit 215 of the control unit 21 supports the confirmation work at the circulation destination. In this confirmation work, “approval / circulation”, “return”, and “denial” are selected. When the confirmation is completed, the circulation management unit 215 records a confirmed flag in the status data area of the person-in-charge circulation route record 262. Details will be described later with reference to FIG. As will be described later, when a predetermined condition is satisfied, the department circulation route setting process (step S1-6) and the person-in-charge circulation path setting process (step S1-7) are also performed at the circulation destination. be able to.

(Department circulation route setting process)
The department circulation route setting process will be described with reference to FIG.
When the circulation route setting is selected on the draft application screen, the department route management unit 213 outputs the department setting screen to the display of the user terminal 10.

  As shown in FIG. 4, the department setting screen 500 includes a department display field 501 and a circulation destination department display field 502. Furthermore, the department setting screen 500 includes an add button 503, a parallel button 504, a series button 505, a delete button 506, and an order change button 507.

In the department display column 501, a category selection column 511, a search column 512, and a list display column 513 are provided.
In the category selection field 511, categories of departments registered as circulation destinations are displayed in a pull-down menu format. Use this pull-down menu to specify the division of the department to which you want to distribute.

The search field 512 is provided with a keyword input field and a search button for searching for a department.
The list display field 513 displays a list of departments identified by the search. A check box for selecting a department is provided in the department list.

In the distribution destination department display field 502, a selection field 521, a task field 522, a selection field 523, and a department field 524 are provided.
In the selection column 521, a check box for selecting departments (first hierarchy) grouped in series and parallel in a task is displayed.

  In the task column 522, series-parallel identifiers and classifications are displayed. In a section including a plurality of departments, a check box for selecting departments (second hierarchy) belonging to the same section together is displayed.

In the selection column 523, check boxes for selecting each department (third hierarchy) are displayed.
In the department column 524, the name of the department to be distributed is displayed.
The add button 503 is an icon for adding the department selected using the check box in the department display field 501 to the circulation destination department display field 502. In the present embodiment, when the add button 503 is selected, it is inserted below the activated display line in the circulation destination department display field 502.

The parallel button 504 is an icon for changing in parallel the circulation destination selected using the checkbox in the circulation destination department display field 502.
The serial button 505 is an icon for canceling the parallel of the circulation destination selected using the check box in the circulation destination department display field 502 and changing it to the serial.

The delete button 506 is an icon for deleting the circulation destination selected using the check box in the circulation destination department display field 502.
The order change button 507 is an icon for changing the circulation order of the circulation destinations activated by selecting the display line in the circulation destination department display field 502. The order change button 507 includes an up arrow button and a down arrow button.

  As shown in FIG. 5A, in the circulation destination department display column 502, each hierarchy is shown for each display line. In the present embodiment, by designating each display line, selection (activation) for changing the addition destination and order of departments can be performed. FIG. 5B schematically shows the department circulation route shown in FIG.

  In FIG. 5A, when “serial” is recorded in the serial parallel identifier data area of the department circulation route record 261, the department circulation route record 261 of the department circulation route record 261 is displayed on the display line displaying “serial”. Displays the category and department. For example, for “A part” and “G part” for which “series” is set, the category and department are displayed in one display line.

  On the other hand, when “Parallel” is recorded in the serial / parallel identifier data area of the department circulation route record 261, the division of the department circulation route record 261 is displayed on the line next to the display line displaying “Parallel”. Is displayed. Further, the department of the department circulation route record 261 is displayed in the lower display line. When a plurality of departments are assigned to the same category, the departments of the department circulation route record 261 are displayed on successive display lines. For example, “B part” and “C part” for which “parallel” is set are continuously displayed as the jurisdiction part. In addition, “E part” and “F part” for which subsequent “parallel” is set are continuously displayed as related parts. When departments of different divisions are included, a division display line and a department display line are sequentially displayed. For example, the “part D” for which “parallel”, which is the same as the “part B”, “part C”, has a different classification from the jurisdiction part (part B, part C). Is displayed next to

  Then, check boxes for selecting groups (G1 to G11) for each layer are displayed in the selection column 521, the task column 522, and the selection column 523 according to the layer. Here, the groups (G01, G02, G07, G11) are grouped in the first hierarchy. Groups (G03, G06, G08) are grouped in the second hierarchy. Further, the group (G04, G05, G09, G10) is the third hierarchy (for each department).

(Draft department setting process)
The drafting department setting process will be described with reference to FIG.
First, the control unit 21 of the circulation management server 20 executes classification specifying processing (step S2-1). Specifically, the user (applicant) selects “draft / application section” in the category selection field 511 of the department display field 501 of the department setting screen 500. In this case, the application management unit 212 of the control unit 21 specifies the affiliation of the logged-in applicant.

  Next, the control unit 21 of the circulation management server 20 executes drafting department registration processing (step S2-2). Specifically, the application management unit 212 of the control unit 21 sets “draft / application unit” and line number “1” as classifications in the department circulation route record 261 registered in the circulation route information storage unit 26. To do. Further, the application management unit 212 specifies the affiliation (department ID) of the applicant in the user information storage unit 23 and records it in the department ID data area of the department circulation route record 261.

(Additional processing of circulation destination department)
With reference to FIG. 7, the process of adding a circulation destination department will be described. This process can be executed not only by the applicant but also by the person in charge of circulation.

  Here, the control unit 21 of the circulation management server 20 executes classification specifying processing (step S3-1). Specifically, when the user selects a distribution destination category, the category in the department display column 501 of the department setting screen 500 is designated. In this case, the department path management unit 213 temporarily stores the category selected in the category selection field 511 in the memory.

  Next, the control unit 21 of the circulation management server 20 executes an additional department specifying process (step S3-2). Specifically, when searching for a department to be added by a user, a keyword for specifying a circulation destination department is entered in the search field 512 and a search button is selected. In this case, the department route management unit 213 of the control unit 21 uses the department information storage unit 22 to search for a department management record 220 in which the input keyword is included in the department name. Then, the department path management unit 213 displays the department name of the extracted department management record 220 in the list display field 513. In this case, the department path management unit 213 displays related departments (upper department, lower department) of the identified department in a tree structure. Furthermore, the department route management unit 213 sets a check box for selecting each department. When the check box of the department displayed in the list display field 513 is selected, the department path management unit 213 temporarily stores the department ID of the circulation destination department to be added in the memory. Here, it is also possible to select a plurality of check boxes.

  Next, the control unit 21 of the circulation management server 20 executes an addition destination hierarchy designation process (step S3-3). Specifically, when the user designates an addition destination, a display line desired to be added is selected in the circulation destination department display field 502. In this case, the department route management unit 213 of the control unit 21 changes the display color of the hierarchy including the selected display line (activation).

  Next, the control unit 21 of the circulation management server 20 executes a distribution destination addition process (step S3-4). Specifically, when the user adds, the add button 503 on the department setting screen 500 is selected. In this case, the department route management unit 213 of the control unit 21 specifies the immediately under the activated hierarchy as an addition destination.

  And the control part 21 of the circulation management server 20 performs an addition process in the same hierarchy as an addition destination (step S3-5). Specifically, the department route management unit 213 of the control unit 21 generates a department circulation route record 261 in which the addition destination is recorded and records it in the circulation route information storage unit 26. In this case, the division designated in the department display column 501 is recorded in the division data area of the department circulation route record 261. Furthermore, the department ID of the additional department is recorded in the department ID data area. In the present embodiment, the same series / parallel identifier as that of the addition destination hierarchy is recorded in the series / parallel identifier data area.

  Next, the control unit 21 of the circulation management server 20 executes a circulation route display process (step S3-6). Specifically, the department route management unit 213 of the control unit 21 decrements the line number of each subsequent circulation destination according to the number of display lines corresponding to the added number of departments. Then, a display line is added to the addition destination according to the series-parallel identifier and the classification. Furthermore, the department route management unit 213 sets a check box for each group in each hierarchy.

Here, a specific example of adding a circulation destination will be described with reference to FIG.
Assume that a circulation destination is added to the circulation destination department display field 502 of the department setting screen 530 shown in FIG. FIG. 9B schematically shows the department circulation route shown in FIG.

  In FIG. 9A, in the department display column 501, “related part” is selected as a category, and “E part” and “F part” are selected using check boxes. Further, in the circulation destination department display field 502, the first hierarchy 532 including “B part” and “C part” is activated. Then, an add button 503 is selected.

  In this case, a circulation destination 542 including “E part” and “F part” is added in the circulation destination department display field 502 of the department setting screen 540 shown in FIG. 9C. Here, FIG. 9D schematically shows the department circulation route shown in FIG.

(Series / Parallel change processing of the distribution destination department)
With reference to FIG. 8A, the serial / parallel change process of the circulation destination department will be described.
Here, the control unit 21 of the circulation management server 20 executes a change target specifying process (step S4-1). Specifically, when the user changes the series / parallel, the check box of the change target department is selected in the circulation destination department display field 502. In this case, the department route management unit 213 of the control unit 21 specifies the department circulation route record 261 of the department selected by the check box in the circulation route information storage unit 26.

  Next, the control unit 21 of the circulation management server 20 executes a series-parallel instruction specifying process (step S4-2). Specifically, the selected circulation destination departments are connected in series, and the parallel button 504 is selected when these are changed in parallel. On the other hand, the selected distribution destination departments are connected in “parallel”, and when these are changed in series, the series button 505 is selected. In this case, the department path management unit 213 of the control unit 21 specifies a series / parallel instruction according to the selected button.

  When the parallel button 504 is selected and the parallel instruction is determined (in the case of “parallel” in step S4-3), the control unit 21 of the circulation management server 20 executes parallelization processing (step S4-4). Specifically, the department route management unit 213 of the control unit 21 overwrites the “parallel” flag in the serial / parallel identifier data area of the department circulation route record 261 of the change target department.

  If the division of the department circulation route record 261 of the department to be changed is the same, the department path management unit 213 generates a display line for each department after the “parallel” display line and the “classification” display line. To do. On the other hand, if the division of the department circulation route record 261 of the department to be changed is different, the department route management unit 213 generates a display line of “Parallel” in the distribution destination department display column and displays “Division”. A department display line is generated for each line.

  On the other hand, when the serial button 505 is selected and it is determined that the serial instruction has been made (in the case of “serial” in step S4-3), the control unit 21 of the routing management server 20 executes the parallel release process (step S4-5). ). Specifically, the selected circulation destination departments are connected in “parallel”, and when these are changed in series, the series button 505 is selected. In this case, the department route management unit 213 of the control unit 21 overwrites the “serial” flag in the serial / parallel identifier data area of the department circulation route record 261 of the change target department. Then, the department path management unit 213 generates a display line including the task (“series”, category) and department for each department to be changed in the circulation destination department display field 502.

Here, a specific example of parallelization of circulation destinations will be described with reference to FIG.
Assume that the circulation destinations displayed in the circulation destination department display field 502 of the department setting screen 550 shown in FIG. FIG. 10B schematically shows the department circulation route shown in FIG.

In FIG. 10A, “E part” and “F part” are selected using the check boxes displayed in the circulation destination department display field 502. Then, the parallel button 504 is selected.
In this case, in the circulation destination department display field 502 of the department setting screen 560 shown in FIG. 10C, a first hierarchy 562 that includes “E part” and “F part” in parallel is generated. Here, FIG. 10D schematically shows the department circulation route shown in FIG.

Here, with reference to FIG. 11, a specific example of serialization (parallel release) of the circulation destination will be described.
A case is assumed in which parallelization of the distribution destinations displayed in the distribution destination department display field 502 of the department setting screen 570 shown in FIG. Here, FIG. 11B schematically shows the department circulation route shown in FIG.

In FIG. 11A, a first hierarchy 572 in which “E part” and “F part” are arranged in parallel is selected using a check box. Then, the serial button 505 is selected.
In this case, “E part” and “F part” are serialized in the first hierarchy in the circulation destination department display field 502 of the department setting screen 580 shown in FIG. Here, FIG. 11D schematically shows the department circulation route shown in FIG.

(Deletion processing of the circulation destination department)
With reference to FIG. 8B, the process of deleting the circulation destination department will be described.
Here, the control unit 21 of the circulation management server 20 executes a deletion target selection process (step S5-1). Specifically, when a user deletes a circulation destination department, a check box of a department to be deleted is selected in the circulation destination department display field 502. In this case, the department route management unit 213 of the control unit 21 specifies the department circulation route record 261 of the department selected by the check box in the circulation route information storage unit 26. Here, it is also possible to select a plurality of check boxes.

  Next, the control unit 21 of the circulation management server 20 executes a deletion target deletion process (step S5-2). Specifically, when the department route management unit 213 of the control unit 21 detects selection of the delete button 506, the department route management unit 213 deletes the identified department circulation route record 261. In this case, the department route management unit 213 deletes the display line corresponding to the department circulation route record 261 in the circulation destination department display field.

  Next, the control unit 21 of the circulation management server 20 executes a lower order advance process (step S5-3). Specifically, the department route management unit 213 of the control unit 21 specifies a department circulation route record 261 in which a line number later than the deleted department line number is recorded. The department route management unit 213 then increments the line number of the identified department circulation route record 261 by the number of display lines corresponding to the number of deleted departments.

Here, a specific example of the deletion of the circulation destination will be described with reference to FIG.
A case is assumed where the circulation destination displayed in the circulation destination department display column 502 of the department setting screen 590 shown in FIG. Here, FIG. 12B schematically shows the department circulation route shown in FIG.

  In FIG. 12A, the first hierarchy 592 including “E part” and “F part” and the first hierarchy 593 including “D part” are selected by using check boxes. Then, the delete button 506 is selected.

  In this case, “E part”, “F part”, and “D part” are deleted in the circulation destination department display field 502 of the department setting screen 600 shown in FIG. Here, FIG. 12D schematically shows the department circulation route shown in FIG.

(Transfer processing of the sending department)
With reference to FIG. 8C, the process of moving the circulation destination department will be described.
Here, the control unit 21 of the circulation management server 20 executes a movement target selection process (step S6-1). Specifically, when the user changes the circulation destination line number, the display line of the movement target department is selected in the circulation destination department display field 502. In this case, the department route management unit 213 of the control unit 21 changes the display color of the hierarchy including the selected display line (activation).

  Next, the control unit 21 of the circulation management server 20 executes a movement direction instruction process (step S6-2). Specifically, when changing the order, the order change button 507 is pressed. Select the up button to move forward in the activated hierarchy, and select the down button to slow down the activated display destination. select. In this case, the department route management unit 213 of the control unit 21 detects pressing of the order change button 507 (the advance button or the advance button).

  Next, the control unit 21 of the circulation management server 20 executes the movement process in the same hierarchy (step S6-3). Specifically, the department route management unit 213 of the control unit 21 changes the row number of the activated hierarchy in the same hierarchy. In this case, the department route management unit 213 records the line number that has been moved up or down in the department circulation route record 261. If the order change button 507 is pressed a plurality of times, the department route management unit 213 repeats the movement process according to the number of times the button is pressed.

Here, a specific example of movement of the circulation destination department will be described with reference to FIG.
A case is assumed where the circulation destination displayed in the circulation destination department display column 502 of the department setting screen 610 shown in FIG. In this case, the display line of the circulation destination to be moved is selected and activated. Here, the first hierarchy 612 including “B part” and “C part” is selected. Then, the order change button 507 is selected.

  FIG. 13B shows a circulation destination department display field 502 when the up button with the upward arrow is selected. FIG. 13C shows the circulation destination department display field 502 when the carry button of the downward arrow is selected.

(Changing the department to which to send)
Next, a case where the circulation destination department is changed during circulation will be described with reference to FIG. Here, it is assumed that the subsequent distribution destination is changed in a department (changer: preceding distribution destination) that confirms the application.

  In the present embodiment, it is assumed that the change rule 640 illustrated in FIG. In this change rule 640, “◯” indicates that the department route can be changed. “X” indicates that the department route cannot be changed. “-” Indicates that the corresponding state does not exist.

With reference to FIG. 14B, the process of changing the distribution destination department will be described.
Here, the control unit 21 of the circulation management server 20 executes an uncirculated department specifying process (step S7-1). Specifically, when the user changes the circulation route in the middle of circulation, the user selects a department circulation destination change button on the top screen. In this case, the department route management unit 213 of the control unit 21 specifies a circulation destination department for which no confirmed flag is recorded in the status data area of the department circulation route record 261 in the circulation route information storage unit 26.

  Next, the control unit 21 of the circulation management server 20 executes identification processing of the division of the department to which the changer belongs (step S7-2). Specifically, the department route management unit 213 of the control unit 21 specifies the department to which the user authenticated by the user belongs. Then, the department route management unit 213 uses the department circulation route record 261 to specify the division of the department to which the department belongs.

  Next, the control unit 21 of the circulation management server 20 executes the identification process of the serial / parallel relationship between the department to which the circulation management server 20 belongs and the circulation destination (step S7-3). Specifically, the department route management unit 213 of the control unit 21 uses the department circulation route record 261 to specify the series-parallel relationship between the user's department and the undelivered subsequent department.

  Next, the control unit 21 of the circulation management server 20 executes the changeable range specifying process based on the classification and the series-parallel relationship (step S7-4). Specifically, the department route management unit 213 of the control unit 21 identifies a department that can be changed at an uncirculated circulation destination based on the division of the department to which the department belongs and the series-parallel relationship based on the change rule 640. To do.

  Here, a specific example of the change range will be described with reference to FIG. In this specific example, it is assumed that a department circulation route from A part to J part is set. It is assumed that the applicant is drafted in the part A to which the applicant belongs, and further drafting / application is performed in the parts B and C. The application is circulated to the E part to the G part as the jurisdiction. In addition, the case where the G part is divided as a representative jurisdiction part is assumed. Furthermore, the case where it circulates to a related part (H part), a prior browsing part (I part), and an executive room (J part) is assumed.

  In this case, according to the change rule 640, the A part can change the circulation to the B part to the J part. On the other hand, the part B and the part C cannot change the route. In addition, the E part and the F part cannot change the route. G part can change circulation to H part-J part. Part H cannot change the route, and part I can change the circulation to part J. And the part J cannot change the route.

  Next, the control unit 21 of the circulation management server 20 executes a distribution destination change process (step S7-5). Specifically, the user changes the circulation destination (addition, deletion, serial / parallel change, order change) within the changeable range. In this case, the department route management unit 213 of the control unit 21 updates the department circulation route record 261. Further, when the department route management unit 213 detects the deleted department, the department route management unit 213 deletes the department circulation route record 261 of this department from the circulation route information storage unit 26.

(Distribution contact person setting process)
Next, the setting process of the person in charge of distribution will be described with reference to FIG. Here, the person in charge of confirming the application (the person in charge of distribution) is set for the person in charge belonging to the department of distribution destination.

  First, the control unit 21 of the circulation management server 20 executes department selection processing (step S8-1). Specifically, when a user sets a person in charge of circulation, the person in charge setting button is selected on the department circulation route screen. In this case, the person-in-charge route management unit 214 of the control unit 21 outputs a department selection screen on the display of the user terminal 10.

  In the present embodiment, it is assumed that a department selection screen 650 shown in FIG. The department selection screen 650 displays the department ID of the department ID recorded in the department circulation route record 261 of the circulation route information storage unit 26.

  Then, when the department for setting the person in charge of distribution is specified on the department selection screen 650, the person-in-charge route management unit 214 identifies the department ID of the department selected on the department selection screen.

  Next, the control unit 21 of the circulation management server 20 executes a user list display process for the selected department (step S8-2). Specifically, the person-in-charge route management unit 214 of the control unit 21 extracts from the user information storage unit 23 the user management record 230 in which the department ID selected on the department selection screen is recorded in the affiliation data area. Then, the person-in-charge route management unit 214 outputs a person-in-charge setting screen that displays a list of users in the extracted user management record 230.

  As shown in FIG. 17B, the person-in-charge setting screen 700 includes a person-in-charge display field 701 and a circulation destination person-in-charge display field 702. Further, the person-in-charge setting screen 700 includes an add button 703, a parallel button 704, a series button 705, a delete button 706, and an order change button 707.

In the person-in-charge display column 701, a search column 712 and a list display column 713 are provided.
The search field 712 is provided with a keyword input field and a search button for searching for a person in charge. In the search field 712, a search can be performed using the user's name, team name, and title.

  The list display field 713 displays a list of persons in charge who belong to the department. This list display field 713 displays for each team to which the person in charge belongs. A check box for selecting a team or a person in charge is provided. In the list display field 713, the titles recorded in the user management record 230 are specified, and the superiors of the titles are displayed in the order in which they are arranged upward.

In the distribution destination person-in-charge display column 702, a selection column 721, a task column 722, a selection column 723, a team column 724, a name column 725, a title column 726, and a role name column 727 are provided.
In the selection column 721, a check box for selecting the persons in charge (first hierarchy) grouped in series and parallel in the task is displayed.

  In the task column 722, a serial / parallel identifier is displayed. Furthermore, when “parallel” is set as the serial-parallel identifier, the series (individual serial identifier) provided in the parallel is displayed. In the individual series identifier, a check box for selecting the persons in charge (second hierarchy) belonging to the series together is displayed.

In the selection field 723, a check box for selecting each person in charge (third layer) is displayed.
In the team column 724, an identifier (team name) for specifying the team to which the person in charge belongs is displayed.

In the name column 725, the title column 726, and the role name column 727, the name, title, and role name of the person in charge are displayed.
In this embodiment, by designating each display line, selection (activation) for changing a person in charge and changing the order can be performed.

  The add button 703 is an icon for adding the person in charge selected using the check box in the person-in-charge display column 701 to the circulation destination person-in-charge display column 702. In the present embodiment, when the add button 703 is selected, the display line of the person in charge selected in the circulation person-in-charge person display column 702 is inserted below the activated display line.

The parallel button 704 is an icon for changing in parallel the circulation destination selected using the check box in the circulation destination person-in-charge display column 702.
The serial button 705 is an icon for canceling the parallel of the circulation destination selected using the check box in the circulation destination person-in-charge display column 702 and changing it to the serial.

The delete button 706 is an icon for deleting the circulation destination selected using the check box in the circulation destination person-in-charge display field 702.
The order change button 707 is an icon for changing a circulation order of circulation destinations activated by selection of a display line in the circulation destination person-in-charge display field 702. The order change button 707 includes an up arrow button and a down arrow button.

  Next, the control unit 21 of the circulation management server 20 executes a process for identifying a person in charge of circulation (step S8-3). Specifically, when searching for a person in charge to be added by a user, a keyword for specifying a person in charge of circulation is entered in the search field 712 and a search button is selected. In this case, the person-in-charge route management unit 214 of the control unit 21 uses the user information storage unit 23 to search for a user management record 230 in which the input keyword is included in the name and affiliation. Then, the person-in-charge route management unit 214 displays the department name of the extracted user management record 230 in the list display field 713. In this case, the person-in-charge route management unit 214 displays users in a tree structure for each affiliation (team). Furthermore, the person-in-charge route management unit 214 sets a check box for selecting each department. When the department check box displayed in the list display field 713 is selected, the person-in-charge route management unit 214 temporarily stores the user ID of the person in charge of the circulation target to be added in the memory. Here, it is also possible to select a plurality of check boxes.

  Next, the control unit 21 of the circulation management server 20 executes an addition destination hierarchy designation process (step S8-4). Specifically, when the user designates an addition destination, a display line desired to be added is selected in the circulation destination person-in-charge display field 702. In this case, the person-in-charge route management unit 214 of the control unit 21 changes the display color of the hierarchy including the selected display line (activation).

  Next, the control unit 21 of the circulation management server 20 executes a distribution destination addition process (step S8-5). Specifically, when the user performs addition, an add button 703 on the person-in-charge setting screen 700 is selected. In this case, the person-in-charge route management unit 214 of the control unit 21 specifies a position immediately below the activated hierarchy as an addition destination.

  Next, the control unit 21 of the circulation management server 20 executes a determination process as to whether or not a plurality of persons in charge are selected (step S8-6). Specifically, the person-in-charge route management unit 214 of the control unit 21 determines whether or not a plurality of persons in charge are selected based on the number of selected check boxes.

  When a plurality of check boxes are selected and it is determined that a plurality of persons in charge are selected (in the case of “YES” in step S8-6), the control unit 21 of the routing management server 20 performs the process of reversing the arrangement order. Execute (Step S8-7). Specifically, the person-in-charge route management unit 214 of the control unit 21 determines the row number by reversing the arrangement order of the selected circulation destination person-in-charge for each team.

  On the other hand, when it is determined that a single person in charge is selected for each team (in the case of “NO” in step S8-6), the control unit 21 of the circulation management server 20 reverses the arrangement order (step S8-7). To skip.

  Here, the control unit 21 of the circulation management server 20 executes an addition process to the same layer as the addition destination (step S8-8). Specifically, the person-in-charge route management unit 214 of the control unit 21 generates a person-in-charge circulation route record 262 in which the line number of the addition destination is recorded, and records it in the circulation route information storage unit 26. In this case, the same task (serial parallel identifier, individual serial identifier) as the addition destination hierarchy is recorded in the task data area of the person-in-charge circulation route record 262. Further, the user ID of the additional person in charge is recorded in the user ID data area.

  Next, the control unit 21 of the circulation management server 20 executes a circulation route display process (step S8-9). Specifically, the person-in-charge route management unit 214 of the control unit 21 decrements the line number of each subsequent circulation destination according to the number of display lines corresponding to the number of persons in charge added. And a display line is added to an addition destination according to a serial parallel identifier and a team. In this case, the person-in-charge route management unit 214 outputs the name, title, and role name recorded in the user management record 230 of the user information storage unit 23 to the display column of each user. Furthermore, the department route management unit 213 sets a check box for each group in each hierarchy.

Here, a specific example of adding a circulation destination will be described with reference to FIG.
It is assumed that a circulation destination is added to the circulation destination person-in-charge display field 702 of the person-in-charge setting screen 730 shown in FIG. Here, FIG. 18B schematically shows the person-in-charge circulation route shown in FIG.

  In FIG. 18A, “D01” is selected in the person-in-charge display column 701 using a check box. Further, in the circulation destination person-in-charge display column 702, the first hierarchy 732 including “C01” to “C03” is activated. Then, an add button 703 is selected.

  In this case, a circulation destination 742 including “D01” is added in the circulation destination person-in-charge display field 702 of the person-in-charge setting screen 740 shown in FIG. Here, FIG. 18D schematically illustrates the person-in-charge circulation route illustrated in FIG.

(Parallelization process for circulation person in charge)
The parallel processing of the person in charge of circulation will be described with reference to FIG.
Here, the control unit 21 of the circulation management server 20 executes a person-in-charge identification process (step S9-1). Specifically, when the user performs parallelization of the person in charge of circulation, the check box of the person in charge to be parallelized is selected in the circulation person-in-charge display field 702 of the person-in-charge setting screen 700. In this case, the person-in-charge route management unit 214 of the control unit 21 identifies the person-in-charge circulation route record 262 of the person in charge selected by the check box in the circulation route information storage unit 26.

  Next, the control unit 21 of the circulation management server 20 executes parallel instruction acquisition processing (step S9-2). Specifically, the parallel button 704 is selected when the user changes the designated person in charge in parallel. In this case, the person-in-charge route management unit 214 of the control unit 21 acquires a parallel instruction.

  Next, the control unit 21 of the circulation management server 20 executes a determination process as to whether or not a plurality of persons are selected (step S9-3). Specifically, the person-in-charge route management unit 214 of the control unit 21 determines whether or not a plurality of persons are selected based on the number of selected check boxes.

  When it is determined that the number of selected check boxes is “1” and the selection is not made by a plurality of persons (“NO” in step S9-3), the control unit 21 of the routing management server 20 performs serial connection in parallel. Generation processing is executed (step S9-4). Specifically, the person-in-charge route management unit 214 of the control unit 21 assigns “parallel” as the serial / parallel identifier of the task data area and “serial” as the individual serial identifier in the person-in-charge route record 262.

  When there are a plurality of selected check boxes and it is determined that a plurality of persons are selected (“YES” in step S9-3), the control unit 21 of the routing management server 20 determines whether the task has been parallelized. The determination process is executed (step S9-5). Specifically, the person-in-charge route management unit 214 of the control unit 21 specifies the serial / parallel identifier in the person-in-charge circulation route record 262 of the selected person in charge. In the person-in-charge circulation route record 262 of all persons in charge, when “parallel” is recorded in the serial-parallel identifier data area, it is determined that the parallelization has been completed.

  When it determines with having completed parallelization (in the case of "YES" in step S9-5), the control part 21 of the circulation management server 20 performs a parallel production | generation process (step S9-6). Specifically, the person-in-charge route management unit 214 of the control unit 21 sets “parallel” as the serial-parallel identifier in the first hierarchy. And the person in charge to whom the individual serial identifier was individually given in the 2nd hierarchy is connected by "parallel" in this 1st hierarchy. Thereby, each person in charge is put together in parallel, and circulation is performed at the same time.

  On the other hand, when it is determined that the processing has not been parallelized (in the case of “NO” in step S9-5), the control unit 21 of the circulation management server 20 executes serial generation processing that can be parallelized (step S9-7). ). Specifically, the person-in-charge route management unit 214 of the control unit 21 sets “parallel” as the serial-parallel identifier in the first hierarchy. Then, in the "parallel" of the first hierarchy, each person in charge is connected by the individual serial identifier of the second hierarchy.

Here, a specific example of parallelization of the person in charge of distribution will be described with reference to FIGS.
It is assumed that the circulation destinations displayed in the circulation destination person-in-charge display column 702 of the person-in-charge setting screen 750 shown in FIG. Here, FIG. 19B schematically shows the person-in-charge circulation route shown in FIG.

In FIG. 19A, the person in charge “C01” is selected using a check box in the circulation destination person in charge display field 702. Then, the parallel button 704 is selected.
In this case, the first level 762 including the person in charge “C01” is generated in the circulation person-in-charge person display column 702 of the person in charge setting screen 760 shown in FIG. The first hierarchy 762 is assigned an individual serial identifier “series 1”. Here, FIG. 19D schematically shows the person-in-charge circulation route shown in FIG. At this stage, for the person in charge “C01”, the second hierarchy is generated in the first hierarchy, but the serial relationship is maintained.

The above process is repeated for the persons in charge “C02” to “C06”.
In this case, as shown in FIG. 20A, a circulation destination person in charge display field 702 is displayed on the person in charge setting screen 770. Here, FIG. 20B schematically represents the person-in-charge circulation route illustrated in FIG. Here, for each person in charge, a second hierarchy is generated in the first hierarchy. When all the persons in charge are parallelized, the check box of the first layer of each person in charge is selected, and the parallel button 704 is selected.

  In this case, as shown in FIG. 21A, a circulation destination person-in-charge display field 702 is displayed on the person-in-charge setting screen 780. Here, FIG. 21B schematically represents the person-in-charge circulation route illustrated in FIG. Here, for each person in charge, the persons in charge “C02” to “C06” are grouped in “Parallel” in the first hierarchy.

Next, another specific example will be described with reference to FIGS.
Assume that the circulation destinations displayed in the circulation destination person-in-charge display column 702 of the person-in-charge setting screen 790 shown in FIG. Here, FIG. 22B schematically illustrates the person-in-charge circulation route illustrated in FIG.

In FIG. 22A, the persons in charge “C01” to “C03” are selected using check boxes in the circulation destination person in charge display field 702. Then, the parallel button 704 is selected.
In this case, the first hierarchy 802 including the persons in charge “C01” to “C03” is generated in the circulation destination person in charge display field 702 of the person in charge setting screen 800 shown in FIG. The first hierarchy 802 is assigned the individual serial identifier “serial 1”. Here, FIG. 22D schematically represents the person-in-charge circulation route illustrated in FIG. At this stage, for the persons in charge “C01” to “C03”, the second hierarchy is generated in the first hierarchy, but the serial relationship is maintained.

Next, the person in charge “C04” to “C06” is selected using check boxes in the circulation destination person in charge display field 702 of the person in charge setting screen 800. Then, the parallel button 704 is selected.
In this case, the first hierarchy 813 including the persons in charge “C04” to “C06” is generated in the circulation destination person in charge display field 702 of the person in charge setting screen 810 shown in FIG. The first hierarchy 813 is assigned the individual serial identifier “series 1”. Here, FIG. 23B schematically represents the person-in-charge circulation route illustrated in FIG. At this stage, the first level 812 of the persons in charge “C01” to “C03” and the first level 813 of the persons in charge “C04” to “C06” are in a serial relationship.

  Next, the first hierarchy 812 and the first hierarchy 813 are selected using check boxes in the circulation destination person in charge display field 702 of the person in charge setting screen 810. Then, the parallel button 704 is selected.

  In this case, the first level 812 of persons in charge “C01” to “C03” and the first level 813 of persons in charge “C04” to “C06” shown in FIG. 23A are grouped in “parallel”. The Then, the first hierarchy 822 is generated in the circulation destination person in charge display column 702 of the person in charge setting screen 820 shown in FIG. Here, FIG. 23D schematically shows the person-in-charge circulation route shown in FIG.

(Serialization process for person in charge of circulation)
The serialization process of the person in charge of circulation will be described with reference to FIG.
Here, the control unit 21 of the circulation management server 20 executes a change target selection process (step S10-1). Specifically, when the user changes the series / parallel, the check box of the department to be changed is selected in the circulation person-in-charge display column 702. In this case, the person-in-charge route management unit 214 of the control unit 21 identifies the person-in-charge circulation route record 262 of the person in charge selected by the check box in the circulation route information storage unit 26.

  Next, the control unit 21 of the circulation management server 20 executes serial instruction acquisition processing (step S10-2). Specifically, the selected person in charge of circulation is connected in “parallel”, and when these are changed in series, the series button 705 is selected. In this case, the person-in-charge route management unit 214 of the control unit 21 acquires a serial instruction.

  Next, the control unit 21 of the circulation management server 20 executes parallel release processing (step S10-3). Specifically, the person-in-charge route management unit 214 of the control unit 21 overwrites the “serial” flag in the serial / parallel identifier data area of the person-in-charge circulation route record 262 of the person in charge of change. Then, the person-in-charge route management unit 214 generates a display line including a task (“series”), a team, a name, a title, and a role name for each person to be changed in the circulation destination person-in-charge display field 702. .

(Deleting person in charge of distribution)
With reference to FIG. 16C, the process of deleting the person in charge of distribution will be described.
Here, the control unit 21 of the circulation management server 20 executes a deletion target selection process (step S11-1). Specifically, when a user deletes a circulation destination person in charge, a check box of a person in charge of deletion is selected in a circulation destination person in charge display field 702. In this case, the person-in-charge route management unit 214 of the control unit 21 identifies the person-in-charge circulation route record 262 of the person in charge selected by the check box in the circulation route information storage unit 26. Here, it is also possible to select a plurality of check boxes.

  Next, the control unit 21 of the circulation management server 20 executes a deletion target deletion process (step S11-2). Specifically, when the person-in-charge route management unit 214 of the control unit 21 detects selection of the delete button 706, the person-in-charge route record 262 is deleted. In this case, the person-in-charge route management unit 214 deletes the display line corresponding to the person-in-charge circulation route record 262 in the circulation destination person-in-charge display field.

  Next, the control unit 21 of the circulation management server 20 executes a lower order advance process (step S11-3). Specifically, the person-in-charge route management unit 214 of the control unit 21 specifies a person-in-charge circulation route record 262 in which a line number later than the line number of the deleted person in charge is recorded. Then, the person-in-charge route management unit 214 increments the line number of the specified person-in-charge circulation route record 262 by the number of display lines corresponding to the number of persons in charge deleted.

(Moving process for the person in charge of circulation)
With reference to FIG. 16D, the process of moving the person in charge of circulation will be described.
Here, the control unit 21 of the circulation management server 20 executes a movement target selection process (step S12-1). Specifically, when the user changes the line number of the circulation destination, the display line of the person to be moved is selected in the circulation destination person display column 702. In this case, the person-in-charge route management unit 214 of the control unit 21 changes the display color of the hierarchy including the selected display line (activation).

  Next, the control unit 21 of the circulation management server 20 executes a movement direction instruction process (step S12-2). Specifically, when changing the order, the order change button 707 is selected. Select the up button to increase the circulation order of the activated hierarchy, and select the down button to decrease the circulation order of the activated display line. select. In this case, the person-in-charge route management unit 214 of the control unit 21 detects pressing of the order change button 707 (the advance button, the advance button).

  Next, the control unit 21 of the circulation management server 20 executes a movement process in the same hierarchy (step S12-3). Specifically, the person-in-charge route management unit 214 of the control unit 21 changes the circulation order of the activated layers in the same layer. In this case, the person-in-charge route management unit 214 records the carried-up or lowered line number in the person-in-charge circulation route record 262. If the order change button 707 is pressed a plurality of times, the person-in-charge route management unit 214 repeats the movement process according to the number of times the button is pressed.

(Change processing of the person in charge of circulation)
Next, with reference to FIG. 24, a case where the person in charge of distribution is changed during circulation will be described. Here, it is assumed that the person in charge who confirms the application (changer: preceding circulation destination) changes the subsequent circulation destination.

  In the present embodiment, it is assumed that the change rule 840 illustrated in FIG. In this change rule 840, “◯” indicates that the person-in-charge route can be changed. Further, “Δ” indicates that a change can be made when a predetermined condition is satisfied.

With reference to FIG. 24B, the process of changing the person in charge of circulation will be described.
Here, the control unit 21 of the circulation management server 20 executes an uncirculated person identification process (step S13-1). Specifically, when the user changes the circulation route in the middle of circulation, the user selects the circulation destination change button of the person in charge on the top screen. In this case, the person-in-charge route management unit 214 of the control unit 21 is the person-in-charge person circulation route record 262 in the circulation route information storage unit 26, and no confirmed flag is recorded in the status data area. Identify the person in charge.

  Next, the control part 21 of the circulation management server 20 performs the determination process about whether it is a specific authority person (step S13-2). Specifically, the person-in-charge route management unit 214 of the control unit 21 determines whether or not the person is a specific authority in the role name recorded in the person-in-charge circulation route record 262.

  When it is determined that the user is a specific authorized person (in the case of “YES” in step S13-2), the control unit 21 of the circulation management server 20 executes a change setting process for an unapproved route in the own department (step S13). -3). Specifically, the person-in-charge route management unit 214 of the control unit 21 selects the person in charge who is the person-in-charge circulation route record 262 associated with the same department ID and for which the confirmed flag is not recorded in the status data area. Include in the changeable range.

  On the other hand, when it is determined that the person is not a specific authority (in the case of “NO” in step S13-2), the control unit 21 of the circulation management server 20 executes a determination process as to whether or not the person is in parallel (step S13-4). ). Specifically, the person-in-charge route management unit 214 of the control unit 21 determines whether or not it is in parallel based on the presence / absence of “parallel” recording in the serial / parallel identifier data area of the person-in-charge circulation route record 262 of the changer. .

  When “series” is recorded in the serial / parallel identifier of the person-in-charge circulation route record 262 of the changer and it is determined that it is not in parallel (in the case of “NO” in step S13-4), the circulation management server 20 The control unit 21 executes the subsequent range changeable setting process (step S13-5). Specifically, the person-in-charge route management unit 214 of the control unit 21 sets the person in charge of the person-in-charge circulation record 262 in which the line number later than the line number of the changer is recorded within the changeable range. include.

  On the other hand, when the parallel person identifier of the person-in-charge circulation route record 262 of the changer is recorded as “parallel” and it is determined that it is in parallel (in the case of “YES” in step S13-4), the circulation management server 20 The control unit 21 executes the changeable setting process in the parallel series (step S13-6). Specifically, the person-in-charge route management unit 214 of the control unit 21 records the line number later than the line number of the changer, and the person-in-charge circulation route record 262 in the hierarchy having the same series-parallel identifier (“parallel”). The person in charge of distribution is included in the changeable range.

  Next, the control unit 21 of the circulation management server 20 executes a determination process as to whether or not it is the last circulation destination in parallel (step S13-7). Specifically, the person-in-charge route management unit 214 of the control unit 21 checks whether or not the latest line number is recorded in the hierarchy of the same series-parallel identifier (“parallel”). Here, when the latest line number is recorded, it is determined as the last circulation destination in parallel.

When it is determined that it is the last circulation destination in parallel (in the case of “YES” in step S13-7), the control unit 21 of the circulation management server 20 executes a distribution destination changeable setting process after parallel processing. (Step S13-8). Specifically, the person-in-charge route management unit 214 of the control unit 21 sets the person in charge of the person-in-charge circulation record 262 in which the line number later than the line number of the changer is recorded within the changeable range. include.
On the other hand, when it is determined that it is not the last circulation destination in parallel (in the case of “NO” in step S13-7), the control unit 21 of the circulation management server 20 can change the distribution destination changeable setting process after parallel processing. (Step S13-8) is skipped.

  Next, the control unit 21 of the circulation management server 20 executes a circulation destination changing process (step S13-9). Specifically, the user changes the circulation destination (addition, deletion, serial / parallel change, order change) within the changeable range. In this case, the person-in-charge route management unit 214 of the control unit 21 updates the person-in-charge circulation route record 262. Furthermore, when the person-in-charge route management unit 214 detects the deleted person in charge, the person-in-charge route record 262 of the person in charge is deleted from the circulation route information storage unit 26.

  Here, a specific example of the changeable range will be described with reference to FIG. As shown in FIG. 25A, it is assumed that a person-in-charge circulation route to persons in charge (A to I) is set. Here, as shown in FIG. 25B, the person in charge A can change the circulation to the persons in charge B to I. As shown in FIG. 25C, the person in charge B can change the circulation to the persons in charge C to I. As shown in FIG. 25D, the person in charge C can change the circulation to the persons in charge D and E. As shown in FIG. 25E, the person in charge D can change the circulation to the person in charge E. As shown in FIG. 25F, the person in charge F can change the circulation to the person in charge G. As shown in FIG. 25 (g), among the persons in charge E and G, the last confirmer can change the circulation to the persons in charge H and I. As shown in FIG. 25 (h), the person in charge H can change the circulation to the person in charge I.

(Circuit confirmation process)
Next, the circulation confirmation process will be described with reference to FIG.
Here, the control unit 21 of the circulation management server 20 executes a process for identifying an application registered as a circulation destination (step S14-1). Specifically, the circulation management unit 215 of the control unit 21 specifies the person-in-charge circulation route record 262 in which the user ID that has been authenticated by the user is recorded in the circulation route information storage unit 26. Then, the circulation management unit 215 specifies a person-in-charge circulation route record 262 for which no confirmed flag is recorded in the status data area.

  Next, the control unit 21 of the circulation management server 20 executes a list screen output process (step S14-2). Specifically, the circulation management unit 215 of the control unit 21 identifies the application management record 240 based on the application ID of the identified person-in-charge circulation route record 262. And the circulation management part 215 produces | generates the application list display screen which displayed the name of the specified application management record 240 as a list.

And the control part 21 of the circulation management server 20 repeats the following processes for every application.
Here, the control unit 21 of the circulation management server 20 executes a determination process as to whether or not the preceding circulation destination has been confirmed (step S14-3). Specifically, the circulation management unit 215 of the control unit 21 has a line number preceding the person-in-charge circulation route record 262 of the person in charge of circulation in the circulation route information storage unit 26, and the serial number The latest person-in-charge circulation record 262 is specified. If the confirmed flag is not recorded in the status data area of the preceding person-in-charge circulation route record 262, it is determined that the preceding circulation destination has not been confirmed.

  When it is determined that the advance circulation destination has not been confirmed (in the case of “NO” in step S14-3), the control unit 21 of the circulation management server 20 executes a notice display process (step S14-4). Specifically, the circulation management unit 215 of the control unit 21 displays a notice about the application on the application list display screen.

On the other hand, when it is determined that the preceding circulation destination has been confirmed (in the case of “YES” in Step S14-3), the control unit 21 of the circulation management server 20 executes a confirmation possible display process (Step S14-5). . Specifically, the circulation management unit 215 of the control unit 21 sets a link to the application management record 240 for the application on the application list display screen so that the application can be selected.
The above processing is repeated for each identified application.

  Next, the control unit 21 of the circulation management server 20 executes an application selection process that can be confirmed (step S14-6). Specifically, when the circulation management unit 215 of the control unit 21 detects selection of a selectable application on the application list display screen, the application management record 240 is changed to the content of the application management record 240 using the application link. It is displayed on the display of the terminal 10.

  Next, the control unit 21 of the circulation management server 20 executes a confirmation process (step S14-7). Specifically, the circulation management unit 215 of the control unit 21 outputs an application content display screen on the display of the user terminal 10.

  As shown in FIG. 26B, the application content display screen 900 includes an application content column, a file list, and a preview screen. The circulation management unit 215 displays the content recorded in the application management record 240 in the application content column. The attached file list displays a list of file names of the attached files of this application. When an attached file is selected in the file list, the circulation management unit 215 displays the content (preview) of the converted file on the preview screen.

  Then, when the person in charge of circulation confirms the application content and the attached file, the confirmation result displayed on the application content display screen 900 is input. Specifically, buttons for selecting “approval / circulation”, “send-back”, and “denial” are displayed on the settlement application application display screen 900. The “Approve / Distribute” button is used to approve an application. The “send back” button is used to specify the return destination and send back the application. The “Decline” button is used when the requested application is rejected and the circulation ends. When the confirmation is completed and each button is selected, the circulation management unit 215 records a confirmed flag in the status data area of the person-in-charge circulation route record 262. Then, when “return” or “denial” is selected at the distribution destination having the approval authority, or when “approval / distribution” is selected at the final authority, the distribution management unit 215 The flags indicating “send back”, “denial”, and “approval” are recorded in the status data area of the application management record 240 of the application information storage unit 24, respectively. Then, the circulation management unit 215 notifies the drafter.

According to this embodiment, the following effects can be obtained.
(1) In the present embodiment, the control unit 21 of the circulation management server 20 executes a draft application information acquisition process (step S1-3). Then, the control unit 21 of the circulation management server 20 executes an attached file acquisition process (step S1-4) and a file conversion process (step S1-5). Thereby, since the conversion file is used, the supplementary material can be confirmed efficiently.

  (2) In this embodiment, the control unit 21 of the circulation management server 20 executes a department circulation route setting process (step S1-6) and a person-in-charge circulation route setting process (step S1-7). . As a result, the circulation route can be set for the person in charge who confirms the application in the circulation destination department. In this case, a circulation route can be set using a circulation route created in a table format composed of a matrix, so that a list is easy. In addition, when outputting the confirmation result in circulation, it is easy to grasp the situation by the table format.

  (3) In the drafting department setting process of the present embodiment, the control unit 21 of the circulation management server 20 executes a classification specifying process (step S2-1) and a drafting department registration process (step S2-2). . As a result, the circulation route can be generated in consideration of the role of the circulation destination department.

  (4) In the circulation destination department addition process of the present embodiment, the control unit 21 of the circulation management server 20 performs the category identification process (step S3-1) and the additional department identification process (step S3-2). Run. In this case, the control unit 21 of the circulation management server 20 executes an addition destination hierarchy designation process (step S3-3) and an addition process (step S3-5) in the same hierarchy as the addition destination. Thereby, based on the hierarchy of an addition destination, a circulation destination can be added efficiently.

(5) In the serial-parallel change process of the circulation destination department of the present embodiment, when it is determined that the instruction is parallel (in the case of “parallel” in step S4-3), the control unit 21 of the circulation management server 20 Is executed (step S4-4). On the other hand, when it determines with a serial instruction | indication (in the case of "serial" in step S4-3), the control part 21 of the circulation management server 20 performs a parallel cancellation | release process (step S4-5). Thereby, in the produced | generated circulation path | route, a serial-parallel relationship can be changed and a circulation path | route can be recreated.
Further, the process of deleting the circulation destination department and the movement process of the circulation destination department are executed. Thereby, in the produced | generated circulation path | route, a circulation path | route can be recreated efficiently.

  (6) In the circulation destination department change process of the present embodiment, the control unit 21 of the circulation management server 20 executes an uncirculated department identification process (step S7-1). And the control part 21 of the circulation management server 20 performs the change process specific process based on a division and a serial-parallel relationship (step S7-4). Thereby, the subsequent circulation destination can be changed in the middle of circulation by satisfying a predetermined condition. For example, it is possible to add a department that was not assumed by the drafter, or change the department to an appropriate department at the distribution destination.

  (7) In the setting process of the person in charge of circulation in this embodiment, the control unit 21 of the circulation management server 20 adds the distribution destination to the same level as the addition destination (step S8-5) (step S8-5). Step S8-8) is executed. Thereby, a circulation destination can be added efficiently. In this case, a circulation route can be set using a circulation route created in a table format composed of a matrix, so that a list is easy. When outputting the confirmation result in circulation, it is easy to grasp the situation by the table format.

  (8) In the present embodiment, when it is determined that a plurality of persons in charge are selected (in the case of “YES” in step S8-6), the control unit 21 of the routing management server 20 executes the reversal processing of the arrangement order. (Step S8-7). Thereby, the circulation order different from an organization structure can be set efficiently. For example, in the organizational structure, the senior positions are usually registered first, but in the circulation route, the circulation order can be later.

  (9) In the parallel processing of the person in charge of circulation in the present embodiment, when it is determined that the selection is not a plurality of persons (in the case of “NO” in step S9-3), the control unit 21 of the circulation management server 20 Then, serial generation processing in parallel is executed (step S9-4). Thereby, a plurality of serial circulation paths can be distributed in parallel.

  (10) In this embodiment, in the selection of a plurality of persons, when it is determined that parallelization has been completed (in the case of “YES” in step S9-5), the control unit 21 of the circulation management server 20 performs parallel generation processing. Execute (step S9-6). Thereby, it is possible to distribute to a plurality of people at the same time. On the other hand, when it is determined that the processing has not been parallelized (in the case of “NO” in step S9-5), the control unit 21 of the circulation management server 20 executes serial generation processing that can be parallelized (step S9-7). ). Thereby, the serial circulation path group for making it parallel with another circulation path group can be produced | generated.

  (11) In the present embodiment, the control unit 21 of the circulation management server 20 executes a serialization process for the circulation destination person in charge, a deletion process for the circulation person in charge, and a movement process for the circulation person in charge. Thereby, the person in charge of circulation can be edited efficiently.

  (12) In the process of changing the person in charge of circulation in the present embodiment, the control unit 21 of the circulation management server 20 executes the process of specifying the person in charge of non-circulation (step S13-1). Then, the changeable range of the circulation destination is specified based on the specific authority, the series-parallel relationship, and the position in the parallel. Thereby, the subsequent circulation destination can be changed in the middle of circulation by satisfying a predetermined condition.

In addition, you may change the said embodiment as follows.
In the above embodiment, when it is determined that a plurality of persons in charge are selected (in the case of “YES” in step S8-6), the control unit 21 of the routing management server 20 executes the reversal processing of the arrangement order (step S8-7). The method for determining the arrangement order is not limited to this. For example, the control unit 21 may acquire the position of the person in charge of distribution using the user information storage unit 23 and determine the distribution order based on the position.

  In the above embodiment, the control unit 21 of the circulation management server 20 executes the department circulation route setting process (step S1-6) and the person-in-charge circulation route setting process (step S1-7). Any route can be used as long as it sets a circulation route, and can be applied to the case where only one of the circulation route of a department or a person in charge is set.

In the above embodiment, each change rule is used in the change process of the distribution destination department and the change process of the person in charge of distribution. The content of the change rule is not limited to this. Here, you may make it change according to the division of a department, and the title of a person in charge. In this case, information on the changeable job title is recorded in the change rule. Then, the control unit 21 of the circulation management server 20 acquires the changer's post information from the directory management server 40, and permits the change of the route only when the post is a predetermined post or more.
Further, the changeable range may be determined based on the number of days elapsed from the drafting date of the application. In this case, information regarding the changeable range is recorded in the change rule according to the number of days elapsed from the draft date. Then, the control unit 21 of the routing management server 20 calculates the number of days that have elapsed since the draft date, and allows the path to be changed based on the number of days that have elapsed.
Moreover, you may make it determine the changeable range according to the kind of application. In this case, information regarding the changeable range (department, position, etc.) is recorded in the change rule according to the type of application. Then, the control unit 21 of the circulation management server 20 identifies the type of application, and allows the route to be changed based on the type of application.

  DESCRIPTION OF SYMBOLS 10 ... User terminal, 20 ... Circulation management server, 21 ... Control part, 211 ... User authentication part, 212 ... Application management part, 213 ... Department path management part, 214 ... Person in charge path management part, 215 ... Circulation management part , 22 ... department information storage unit, 23 ... user information storage unit, 24 ... application information storage unit, 25 ... attached file storage unit, 26 ... circulation route information storage unit.

Claims (10)

An application information storage unit for storing application contents;
A circulation destination person to whom the serial / parallel identification information is assigned is stored in association with the circulation destination department to which the series / parallel identification information is assigned, and the confirmation status of the circulation destination person in charge is further stored. A circulation route information storage unit for storing circulation destination information for specifying;
A circulation management system including a control unit for managing circulation of an application,
The control unit is
Acquires information related to classification and distribution destination department from user terminal, and gives serial / parallel identification information for identifying line number, serial information or parallel information to classification and distribution destination department. Recorded in the circulation route information storage unit as circulation destination information,
The line number is used to display the serial / parallel identification information, the division, and the circulation destination department in a table format as column items, and the circulation destination is grouped into a hierarchy by using the column item and the row number. the circulation path confirmation screen generated an output to the user terminal,
In the table format, when a group including a plurality of departments in the same hierarchy is selected and an instruction to change the circulation order of the group is acquired, the circulation order is changed for a plurality of departments included in the group. Generate circulation destination information,
A person in charge of distribution is selected in the department selected from among the departments of distribution destinations, and the direct identification for identifying the line number, serial information or parallel information of the persons in charge of distribution in the distribution destination department. Giving parallel identification information, associating the circulatory contact person in association with the circulatory destination department as the circulatory destination information and recording it in the circulatory path information storage unit,
For the circulatory contact person in the circulatory destination department confirmed on the circulatory route confirmation screen, the circulatory destination associated with the same parallel information as the serial / parallel identification information is stored in the application information storage unit. As long as the application details are distributed at the same time, the confirmation status of the preceding distribution destination is confirmed for the distribution destination associated with the serial information according to the line number. Circulation management system characterized by performing circulation as The circulation management according to claim 1 , wherein a line number designated on the circulation path confirmation screen is acquired, and a circulation path to which a new circulation destination is added is generated based on the line number. system. When adding the new circulation destination, the serial / parallel identification information of the circulation destination of the line number specified on the circulation route confirmation screen is set in the circulation destination information of the new circulation destination, and the circulation The circulatory management system according to claim 2 , wherein the circulatory management system records the information in a route information storage unit. For the department set as the distribution destination, the member list screen of the person in charge belonging to the department is output to the user terminal,
Circulation management system according to any one of claims 1 to 3, characterized in that to record the person selected in the member list screen, in the circulation path information storage as the circulation destination information . In the member list screen, when a plurality of persons in charge are selected, a line number is assigned according to the attribute of the person in charge, and is recorded in the circulation route information storage unit as circulation destination information. The circulation management system according to claim 4 . In the circulation route recorded in the circulation route information storage unit, it is a subsequent circulation destination of the preceding circulation destination that circulated the application, and specifies the uncirculated subsequent circulation destination,
The circulation management system according to any one of claims 1 to 5 , wherein the preceding circulation destination is allowed to change the subsequent circulation destination. In the circulation route recorded in the circulation route information storage unit, when the preceding circulation destination and the subsequent circulation destination are arranged in series information, the change of the subsequent circulation destination is allowed. The circulation management system according to claim 6 , wherein: Wherein identifying the previous circulation destination attribute, based on the attribute, circulation management system according to claim 6 or 7, characterized in that to permit a change in the subsequent circulation destination. An application information storage unit for storing application contents;
A circulation destination person to whom the serial / parallel identification information is assigned is stored in association with the circulation destination department to which the series / parallel identification information is assigned, and the confirmation status of the circulation destination person in charge is further stored. A circulation route information storage unit for storing circulation destination information for specifying;
A method for managing circulation using a circulation management system having a control unit for managing circulation of an application,
The control unit is
Acquires information related to classification and distribution destination department from user terminal, and gives serial / parallel identification information for identifying line number, serial information or parallel information to classification and distribution destination department. Recorded in the circulation route information storage unit as circulation destination information,
The line number is used to display the serial / parallel identification information, the division, and the circulation destination department in a table format as column items, and the circulation destination is grouped into a hierarchy by using the column item and the row number. the circulation path confirmation screen generated an output to the user terminal,
In the table format, when a group including a plurality of departments in the same hierarchy is selected and an instruction to change the circulation order of the group is acquired, the circulation order is changed for a plurality of departments included in the group. Generate circulation destination information,
A person in charge of distribution is selected in the department selected from among the departments of distribution destinations, and the direct identification for identifying the line number, serial information or parallel information of the persons in charge of distribution in the distribution destination department. Giving parallel identification information, associating the circulatory contact person in association with the circulatory destination department as the circulatory destination information and recording it in the circulatory path information storage unit,
About the person in charge of circulation at the department of circulation confirmed on the confirmation screen for circulation route,
As for the distribution destination associated with the same parallel information as the series-parallel identification information, the application contents stored in the application information storage unit are distributed at the same time and the distribution destination associated with the serial information. Is a circulation management method, characterized in that circulation is performed on the condition that the confirmation status of the preceding circulation destination is confirmed according to the line number. An application information storage unit for storing application contents;
A circulation destination person to whom the serial / parallel identification information is assigned is stored in association with the circulation destination department to which the series / parallel identification information is assigned, and the confirmation status of the circulation destination person in charge is further stored. A circulation route information storage unit for storing circulation destination information for specifying;
A program for managing circulation using a circulation management system having a control unit for managing circulation of an application,
The control unit
Acquires information related to classification and distribution destination department from user terminal, and gives serial / parallel identification information for identifying line number, serial information or parallel information to classification and distribution destination department. Recorded in the circulation route information storage unit as circulation destination information,
The line number is used to display the serial / parallel identification information, the division, and the circulation destination department in a table format as column items, and the circulation destination is grouped into a hierarchy by using the column item and the row number. the circulation path confirmation screen generated an output to the user terminal,
In the table format, when a group including a plurality of departments in the same hierarchy is selected and an instruction to change the circulation order of the group is acquired, the circulation order is changed for a plurality of departments included in the group. Generate circulation destination information,
A person in charge of distribution is selected in the department selected from among the departments of distribution destinations, and the direct identification for identifying the line number, serial information or parallel information of the persons in charge of distribution in the distribution destination department. Giving parallel identification information, associating the circulatory contact person in association with the circulatory destination department as the circulatory destination information and recording it in the circulatory path information storage unit,
For the circulatory contact person in the circulatory destination department confirmed on the circulatory route confirmation screen, the circulatory destination associated with the same parallel information as the serial / parallel identification information is stored in the application information storage unit. As long as the application details are distributed at the same time, the confirmation status of the preceding distribution destination is confirmed for the distribution destination associated with the serial information according to the line number. A circulation management program that functions as a circulation means.