JP2008310710A - Information processor, workflow control method, program, and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To attain coexistence of workflow of systems of a plurality of new and old versions and to freely change the system version of workflow in progress to the new or old version. <P>SOLUTION: A system information registering section 304 registers system information 316 of the plurality of versions in coexistence, and registers date and time information 312 specifying a valid period for every version. When a job is created, a workflow progress section 302 determines a version number of system information based on specification in creating the job, to associate with the job, and a person-in-charge discriminating section 303 determines a transition place of the job based on the version number associated with the job and proceeds with the workflow. When there is a replacement request of system information for the job, a system replacing section 305 changes the transition destination of the job by redetermining the version number of the system information associating with the job based on specification in the replacement request. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to workflow control of a job whose transition route is defined by the organization information.

Patent Document 1 registers both the old and new organizations before and after the organization change, and executes a workflow process when a certain user belongs to (or belongs to) an organization designated at present or in the past. A workflow for determining whether there is authority is disclosed.
JP 2006-195812 A

  However, in Patent Document 1, it is possible to determine whether or not the user has execution authority. However, in the case of a workflow across organizational changes, there is a problem that the next person in charge (transition destination) cannot be automatically determined. was there.

  For example, if the manager who is the supervisor is changed while a user belongs to the same department, it is not possible to automatically determine which manager should approve the slip that the user has applied for. Therefore, there is a problem in that the user makes a complicated work such as making a decision and requesting approval from either section manager.

  In addition, since the organization is determined from the present to the past, the future organization cannot be distinguished from the current organization, so that it is not possible to register the future organization in advance.

  In addition, since the organization to be referred to is determined based on the organization code specified at the start of the workflow, there is a problem that it is not possible to deal with the case where it is desired to operate the current organization only for the progress of individual workflows.

  The present invention has been made to solve the above problems. An object of the present invention is to provide a mechanism capable of coexisting workflows in a plurality of versions of an organization including old and new and processing them without contradiction.

  The present invention is an information processing apparatus that controls a workflow of a job whose transition path is defined by organization information, and version identification information that can specify one or more versions for which the record is valid for each record of organization information A plurality of versions of organization information that can be stored in a coexisting manner, and a version validity period information storage unit that stores date and time information that specifies a period of validity for each version; Version identification means for determining version identification information and associating it with the job based on information for determining the version of organization information associated with the job specified when the job is created, and version identification associated with the job Based on the information, determine the transition destination of the job, and transition the job to the determined transition destination Information for determining the version of the organization information associated with the job specified in the replacement request when the organization information replacement request is made for the job. And reconfirming means for reconfirming the version identification information associated with the job based on the information.

  According to the present invention, a plurality of versions of organization information used for a workflow can be registered, and the workflow proceeds according to the organization of the version specified at the start, that is, each person in charge in the specified version of the organization is determined. Therefore, for example, even if an organizational change is made at the beginning of the month, the liquidation process for the previous month and the application process for the current month can be processed simultaneously without contradiction.

  Further, future organization information can be registered regardless of the state of the workflow. Also, it cannot be used until it is activated.

  In addition, even a workflow in progress in an old version organization can be switched to operation in the current version organization. And it is possible to suppress redoing of a conference that may occur due to such switching.

  In addition, although a plurality of versions of an organization are managed, the number of data records can be reduced by efficiently managing the portion of data that is not changed. In addition, it is possible to suppress the occurrence of a situation in which the number of data records becomes enormous even if editing is performed by batch processing that does not consider differences.

  Therefore, there is an effect that workflows progressing in a plurality of versions of the organization including new and old can coexist and can be processed without contradiction. That is, the workflow that progresses in the old organization and the workflow that progresses in the new organization can coexist. That is, the organization version of the ongoing workflow can be changed freely.

[First Embodiment]
Embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 is a diagram illustrating an example of a workflow system to which an embodiment of the present invention can be applied.

  In FIG. 1, in the workflow system, at least one workflow server 101 and a workflow client 102 are connected via a network 100.

  The user makes a workflow progress request or the like from the workflow client 102 to the workflow server 101 using, for example, a web browser or client software.

  The workflow server 101 performs processing and management in response to a request from the workflow client 102, and transmits a result or the like to the workflow client 102 if necessary.

  The communication between the workflow server 101 and the workflow client 102 may be a normal HTTP request or a web service request using SOAP or the like.

  FIG. 2 is a block diagram illustrating an example of a hardware configuration of the workflow server 101 and the workflow client 102 illustrated in FIG.

  In FIG. 2, the CPU 201 comprehensively controls each device connected to the system bus 204. The ROM 203 or the external memory 211 stores an operating system (OS) that is a control program of the CPU 201 and programs for realizing various functions described later of each server or each client.

  The RAM 202 functions as a main memory, work area, temporary save area, and the like for the CPU 201.

  The input controller 205 controls input from the input unit 209. Examples of the input unit 209 include a pointing device such as a keyboard and a mouse in a terminal such as a server or a client. In a printing apparatus or the like, examples of the input unit 209 include a touch panel, buttons, and switches.

  The output controller 206 controls the display of the output unit 210. Examples of the output unit 210 include a CRT and a liquid crystal.

  The external memory controller 207 controls access to the external memory 211 that stores a boot program, various applications, font data, user files, edit files, printer drivers, and the like. In addition, the external memory controller 207 stores various tables and parameters for realizing various functions of each server or each client.

  Examples of the external memory 211 include a hard disk (HD), a floppy (registered trademark) disk (FD), a compact flash (registered trademark) connected to a PCMCIA card slot via an adapter, and smart media.

  The communication I / F controller 208 executes communication control processing with an external device via the network 214.

  Although 212 is illustrated as hardware, it is not hardware but a program for realizing the present invention. The program 212 is recorded in the external memory 211 and is executed by the CPU 201 by being loaded into the RAM 202 as necessary.

  FIG. 3 is a diagram illustrating an example of a functional configuration realized in the workflow server 101 illustrated in FIG.

  As shown in FIG. 3, the workflow server 101 includes, as its functional configuration, an input / output processing unit 301, a workflow progression unit 302, a person-in-charge determination unit 303, an organization information registration unit 304, and an organization replacement unit 305. , Process definition information storage unit 310, job information storage unit 311, version validity period information storage unit 312, organization information storage unit 316 (department information storage unit 313, role information storage unit 314, user position information storage unit 315).

  The input / output processing unit 301 performs processing for receiving input information from the input controller 205 or the communication I / F controller 208 of the workflow server 101. Further, the input / output processing unit 301 converts the received input information into a request to the workflow progression unit 302 or the organization information registration unit 304 according to the content. Further, when a result corresponding to the request is returned, the input / output processing unit 301 outputs the result to the output controller 206 or the communication I / F controller 208.

  The workflow progression unit 302 controls the progression (circulation) of the workflow in response to a request from the input / output processing unit 301. Specifically, the workflow progression unit 302 refers to the process definition information stored in the process definition information storage unit 310 to create or progress a job, and stores the created or advanced job in the job information storage unit 311. And refer to it at the next progress. When creating a job, the workflow progression unit 302 stores the version number determined by the version number determination process shown in FIG. 12 described later together with the job information storage unit 311. Further, when the job progresses, the workflow progression unit 302 stores the person in charge determined by the person-in-charge determination unit 303 as the person in charge of the job together with the job information storage unit 311.

  In response to a request from the workflow progression unit 302 or the like, the person-in-charge determination unit 303 receives department information stored in the department information storage unit 313, role information stored in the role information storage unit 314, and user position information. The person in charge of the department and role specified by referring to the user position information stored in the storage unit 315 and the version effective period information stored in the version effective period information storage unit 312 is specified. To determine which user position in the version.

  The organization distribution unit 305 stores job information stored in the job information storage unit 311, department information stored in the department information storage unit 313, and role information storage in response to a request from the workflow progression unit 302 and the like. The job by referring to the role information stored in the section 314, the user position information stored in the user position information storage section 315, and the version validity period information stored in the version validity period information storage section 312. The reference organization version is replaced (details will be described later).

  The organization information registration unit 304 processes the organization registration request requested from the input / output processing unit 301, stores the department information in the department information storage unit 313, the role information in the role information storage unit 314, and the user position information in the user position information. The version valid period information is stored in the storage unit 315 in the version valid period information storage unit 312.

  The process definition information storage unit 310 is a storage unit that stores process definition information. Details of the process definition information stored in the process definition information storage unit are shown in FIG.

  The job information storage unit 311 is a storage unit that stores job information. The job information storage unit 311 includes, as items, job identification information, reference process definition identification information, reference organization version identification information, current activity identification information, assignee identification information, and the like.

  The department information storage unit 313 is a storage unit that stores department information. Details of the department information stored in the department information storage unit 313 are shown in FIG.

  The role information storage unit 314 is a storage unit that stores role information (role information). Details of the role information stored in the role information storage unit 314 are shown in FIG.

  The user position information storage unit 315 is a storage unit that stores user position information (affiliation information). Details of the user position information stored in the user position information storage unit 315 are shown in FIG.

  The version validity period information storage unit 312 is a storage unit that stores version validity period information. The details of the version validity period information stored in the version validity period information storage unit 312 are shown in FIG.

  The input / output processing unit 301, the workflow progress unit 302, the person-in-charge determination unit 303, the organization information registration unit 304, and the organization replacement unit 305 are programs in which the CPU 101 of the workflow server 101 is stored in the external memory 211. This corresponds to a function realized by loading 212 to the RAM 202 and executing it.

  In addition, the process definition information storage unit 310, the job information storage unit 311, the version validity period information storage unit 312, the organization information storage unit 316 (the department information storage unit 313, the role information storage unit 314, and the user position information storage The unit 315) is realized as a storage area in the external memory 211.

  Hereinafter, the process definition, organization, department information, role information, user position information, version valid period information, and the like used in the description of the present embodiment will be described with reference to FIGS.

  FIG. 4 is a diagram illustrating an example of process definition information stored in the process definition information storage unit 310 illustrated in FIG. 3.

  As shown in FIG. 4, when the applicant makes an application in activity 501, the process definition information transitions to the next activity 502, and the section manager of the application department becomes the person in charge. When a section manager of an application department approves, the process transitions to the next activity 503, where the department manager of the application department and the department manager of the business department become coordinators, and in activity 503, the manager of the application department department who is the coordinator When the general manager performs approval processing for approval, it corresponds to information indicating that a transition is made to a completion activity.

  The application department indicates a department to which the applicant belongs. In addition, the person in charge of the council refers to a person in charge in the case of an activity that decides whether or not to approve one activity by voting by a plurality of people. For example, when the sales section member C applies, the person in charge of the activity 502 is the section manager B of the sales section that is the application department, and in the conference activity 503, the manager A of the sales department that is the application section, The business department manager D becomes the person in charge of the conference, and the workflow proceeds.

  The process definition shown in Fig. 4 is a simple example, but even if it is a complex process definition with branching and parallel processing, the activity in which the department in charge and the role in charge are defined, and the transition indicating the transition destination are defined. There is no substitute for being. In this example, the department is designated as the application department, but can be designated using actual department identification information.

  As described above, the workflow server 101 according to the present embodiment controls the workflow of a job whose transition path is defined by the process definition defined by the organization information (department, role) as shown in FIG. It has a configuration.

  FIG. 5 is a diagram showing an example of an organization used for explaining the present embodiment.

  For example, as shown in FIG. 5, the organization of the V2 version 601 is effective from March 1, 2007 to April 1, 2007. The organization of the V2 version 601 includes, for example, a sales department 610, a sales section 611, and a business section 612, and indicates that the sales section 611 and the business section 612 are under the sales department 610. .

  In addition, the user A belongs to the sales department 610 as the general manager 620, the user B belongs to the sales department 611 as the manager 621, the user C belongs to the staff 622, and the business department 612 includes the user D as user D. It shows a situation where the user 623 belongs as the section manager and the user E belongs 624 as the section manager.

  In addition, the organization of V3 version 602 is effective from April 1, 2007 to April 10, 2007. In this V3 version 602 organization, a business unit 613 is newly established, and the business unit 612 undergoes an organizational change that is transferred to the business unit 613, and the user E is assigned to the business unit 613 as a general manager 625 (concurrent). Indicates that a transfer has been made.

  Further, in the organization of V4 version 603, it is effective from April 10, 2007 to July 1, 2007. In this V4 version 603 organization, the user B621 who belonged to the sales section 611 as the section manager is assigned, and the user G who newly became the section 627 as the section manager and the user D who concurrently served as the section manager of the business section 612 User E who was assigned as a member of the business section 612 became a member 626 as the section manager of the business section 612, and a new personnel change was made in which the user F belonged as a section 628. Is shown.

  FIG. 6 is a diagram showing an example of department information stored in the department information storage unit 313 shown in FIG.

  As shown in FIG. 6, the department information includes, as items, a department ID 701, a department name 702, a parent department ID 703, a start version number 704 (start information), and an end version number 705 (end information). ).

  For example, identification information for identifying a department is set in the department ID 701. In the department name 702, the name of the department is set. In the parent department ID 703, identification information of a department to which the department belongs is set.

  In the start version number 704, the version number of the organization in which the department is newly established is set. In addition, the end version number 705 is set with a version number of the organization in which the department is discarded, or a value indicating, for example, “HV” when the organization exists in the version of the most future organization. Yes.

  The example illustrated in FIG. 6 corresponds to the example in which the organization change illustrated in FIG. 5 is performed. For example, the parent department 703 of the business section 612 whose department ID 701 is D3 is D1 (sales department) from version V1 to V3, but is D4 (business department) after version V3. ing. Further, it is shown that a business department whose department ID 701 is D4 is newly established after version V3.

  FIG. 7 is a diagram illustrating an example of role information stored in the role information storage unit 314 illustrated in FIG.

  As illustrated in FIG. 7, the role information includes, as items, a role ID 801, a role name 802, a start version number 803, and an end version number 804 for each role (role).

  For example, identification information for identifying a role is set in the role ID 801. In the role name 802, the name of the role is set.

  In the start version number 804, the version number of the organization in which the role is newly established is set. In the end version number 805, a version number of the organization in which the role is discarded, or a value indicating the role if the role exists in the future organization version, for example, “HV” is set. Yes.

  FIG. 8 is a diagram illustrating an example of user position information stored in the user position information storage unit 315 illustrated in FIG.

  As shown in FIG. 8, the user position information includes, as items for each user position, a user ID 901, a department ID 902, a role ID 903, a user position name 904, a start version number 905, and an end version number 906. including.

  For example, identification information for identifying a user is set in the user ID 901. In the department ID 902, identification information of the department to which the user belongs is set.

  In the role ID 903, role identification information when the user belongs to the department is set. In the user position name 904, a user name when the user belongs to the department with the role is set. In the start version number 905, the version number of the organization in which the user starts to belong to the department with the role is set.

  The end version number 906 includes a version number of the organization that the user no longer belongs to the department in the role, or a value indicating the role if the role belongs to the most future organization version, for example, “HV” is set.

  The example illustrated in FIG. 8 corresponds to the example in which the personnel change illustrated in FIG. 5 is performed. For example, for a user whose user ID 901 is D, from version V1 to version V4, the department ID 902 belongs to D3 (business section) and the role ID 903 belongs to R2 (section manager). For version V3 and later, the department ID 902 belongs to D4 (business department) and the role ID 903 belongs to R1 (department manager).

  FIG. 9 is a diagram illustrating an example of version validity period information stored in the version validity period information storage unit 312 illustrated in FIG.

  As shown in FIG. 9, the version validity period information includes a version number 1001, a valid start date / time 1002, and a valid end date / time 1003 as items for each version.

  For example, an identification number for identifying the version of the organization is set in the version number 1001.

  Also, information about the date and time when the version becomes valid is set in the valid start date and time 1002, and information about the date and time when the version becomes invalid or the version is the most future version. If it is valid for the future, a value indicating it, for example, “HV” is set.

  Therefore, it is possible to operate so that future organization information is registered regardless of the state of the workflow and is not used until the valid start date and time.

  As described above, as shown in FIGS. 6 to 8, the organization information composed of department information, role information, user position information, etc. is a version that can specify one or a plurality of versions for which the record is valid for each record. Holds identification information (start version number, end version number) and stores multiple versions of organization information in the external memory 211 (department information storage unit 313, role information storage unit 314, user position information storage unit 315) It has a possible configuration.

  Also, as shown in FIG. 9, version valid period information having date / time information (valid start date / time, valid end date / time) for specifying a valid period for each version is stored in the external memory 211 (version valid period information storage unit 312). Is remembered.

  Hereinafter, with reference to FIGS. 10 to 17, the workflow progress process in the present invention will be described.

  FIG. 10 is a flowchart illustrating an example of a first control processing procedure according to the present invention, and corresponds to the workflow progress process executed by the workflow progress unit 302 and the like. That is, the processing of this flowchart is realized by the CPU 101 of the workflow server 101 loading the program 212 stored in the external memory 211 into the RAM 202 and executing it.

  When a workflow start request is made via the input / output processing unit 301, the workflow progression unit 202 performs job start processing (S401), and creates and starts a job. At the start of the job, the version of the organization referred to by the job is determined based on the date or the version number. Details of the job start process in S401 are shown in FIG.

  Next, in step S402, the workflow progression unit 202 determines whether or not the transition destination activity indicates a process completion.

  If it is determined in step S402 that the transition destination activity indicates process completion, the workflow progression unit 202 performs job end processing in step S409 and completes the job.

  On the other hand, if it is determined in step S402 that the transition destination activity does not indicate process completion, the workflow progression unit 202 advances the processing to the person-in-charge assignment process in step S403.

  In the person-in-charge assignment process in step S403, the workflow progression unit 202 requests the person-in-charge determination unit 303 to determine the person in charge in the activity. The person-in-charge determination unit 303 determines the person in charge using the organization version referred to by the job. Details of the person-in-charge assignment process in step S403 are shown in FIG.

  Next, in step S404, the workflow progression unit 202 executes a request waiting process. Specifically, the workflow progression unit 202 waits until an approval request from the person in charge of the activity or an organization reassignment request from the administrator is made via the input / output processing unit 301. Is performed, the process proceeds to step S405. Details of the request waiting process in step S404 are shown in FIG.

  In step S405, the workflow progression unit 202 determines whether the request received in the request waiting process in step S404 is an “approval request”. In the case of a consultation as shown at 503 in FIG. 4, it is determined that there is an “approval request” when there is an approval request in the consultation.

  If it is determined in step S405 that the request received in step S404 is an “approval request” (Yes), the workflow progression unit 202 advances the process to the work item approval process in step S407.

  In the work item approval process in step S407, the workflow progression unit 202 performs an approval process according to the content of the approval request, determines the transition destination activity, and returns the process to the determination in step 402. Details of the work item approval process in step S407 are shown in FIG.

  On the other hand, if it is determined in step S405 that the request received in step S404 is not an “approval request” (No), the workflow progression unit 202 advances the process to step S406.

  In step S406, the workflow progression unit 202 determines whether the request received in the request waiting process in step S404 is an “organization replacement request”.

  If it is determined in step S405 that the request received in step S404 is not an “approval request” (No), the workflow progression unit 202 returns to the request waiting process in step S404 and waits for the request again. Do. Note that when processing corresponding to another request is performed, processing corresponding to the other request may be performed before returning to the request waiting processing of S404.

  On the other hand, when it is determined in step S406 that the request received in step S404 is an “organization replacement request” (Yes), the workflow progression unit 202 transfers the organization to the organization replacement unit 305 in step S408. Execute the process.

  In the organization replacement process in step S408, the organization replacement unit 305 performs processing to replace the organization version referred to by the job with a newly designated one in accordance with the contents of the organization replacement request, and the process proceeds to S404. return. Details of the organization replacement process in step S408 are shown in FIG.

  As described above, by performing the process as shown in FIG. 10, the person who is the workflow entity determines the person in charge of the transition destination activity according to the referred organization version specified at the start (when creating the job). However, the workflow can be advanced and processed.

  Therefore, by executing the process as shown in FIG. 10, the past, present, and future organizations can coexist even on the single workflow system of the single workflow server 101, and the workflow proceeds without contradiction. can do.

  In addition, if necessary, for each job that is the entity of each workflow, refer to a version different from the organization that was previously referenced, so that jobs from the old organization can be smoothly transferred to the new organization. Can do.

  Hereinafter, the job creation process shown in step S401 of FIG. 10 will be described with reference to FIG.

  FIG. 11 is a flowchart showing an example of the second control processing procedure in the present invention, and corresponds to the job creation processing shown in step S401 of FIG. That is, the processing of this flowchart is realized by the CPU 101 of the workflow server 101 loading the program 212 stored in the external memory 211 into the RAM 202 and executing it.

  As shown in FIG. 11, when the job creation process is started, in step S1101, the workflow progression unit 302 uses the input information passed from the input / output processing unit 301 to perform a version determination process. Details of the version confirmation process in step S1101 are shown in FIG.

  When the version number of the organization referred to by the job is confirmed in the version confirmation process in step S1101, the process proceeds to step S1102.

  In step S1102, the workflow progression unit 302 refers to the process definition information stored in the process definition storage unit 310 corresponding to the process definition identification information included in the input information passed from the input / output processing unit 301, and determines the workflow. Create a real job. Further, the workflow progression unit 302 associates the version number of the organization determined by the version determination process of S1101 with the job related information, stores it in the job information storage unit 311 together with other attributes of the job, and advances the process to step S1103.

  In step S1103, the workflow progression unit 302 starts the job by setting the state of the process definition job to the start state, stores the state in the job information storage unit 311, and advances the process to step S1104. .

  In step S <b> 1104, the workflow progression unit 302 refers to the process definition stored in the process definition storage unit 310, sets the first activity as the transition destination activity in the job information, and stores it in the job information storage unit 311.

  As described above, by performing the processing as shown in FIG. 11, a job based on the process definition corresponding to the input information is created and started in a state where the version of the organization corresponding to the input information is referred to.

  Hereinafter, the version determination process shown in step S1101 of FIG. 11 will be described with reference to FIG.

  FIG. 12 is a flowchart showing an example of a third control processing procedure in the present invention, and corresponds to the version confirmation processing shown in step S1101 of FIG. That is, the processing of this flowchart is realized by the CPU 101 of the workflow server 101 loading the program 212 stored in the external memory 211 into the RAM 202 and executing it.

  As shown in FIG. 12, when the version confirmation process is started, in step S1201, the workflow progression unit 302 determines the organization version designation method. As the organization version designation method, there are a designation method by date and time, a designation method by version number, and no designation. This organization version designation method is input from the input unit of the workflow client 102 by the applicant at the time of application, and is included in the workflow start request.

  If the organization version designation method is the designation method based on “date and time”, the workflow progression unit 302 advances the processing to step S1203 using the designated date and time as the designated date and time.

  If the organization version designation method is the designation method based on “version number”, the workflow progression unit 302 advances the processing to step S1204 using the version number as the designated version number.

  If the organization version designation method is “undesignated”, the workflow progression unit 302 advances the process to step S1202.

  In step 1202, the person-in-charge determination unit 303 acquires the current date and time, regards it as the specified date and time, and advances the processing to step S1203.

  In step 1203, the person-in-charge determination unit 303 refers to the version effective period information stored in the version effective period information storage unit 312, the specified date is after the effective start date 1002, and the specified date is A version number 1001 satisfying that it is before the valid end date and time 1003 is acquired, and the designated version number is set as the version number, and the process proceeds to step 1204.

  In step 1204, the person-in-charge determination unit 303 determines the specified version number as the version number of the organization corresponding to the input information, and returns it to the caller (the process of FIG. 11) as a result of the version determination process. End the process.

  As described above, by performing the processing as shown in FIG. 12, not only the version of the organization that is valid at the present time, but also the version number of the target organization can be determined by a designation method such as date and version number. As a result, it is possible to flexibly specify not only the current organization but also the previous month's organization version or the next month's organization version depending on the type of business corresponding to the job.

  Hereinafter, the person-in-charge assignment process shown in step S403 of FIG. 10 will be described with reference to FIG.

  FIG. 13 is a flowchart showing an example of a fourth control processing procedure in the present invention, and corresponds to the person-in-charge assignment processing shown in step S403 of FIG. That is, the processing of this flowchart is realized by the CPU 101 of the workflow server 101 loading the program 212 stored in the external memory 211 into the RAM 202 and executing it.

  As illustrated in FIG. 13, the person-in-charge determination unit 303 refers to the job information of the job stored in the job information storage unit 311 in step S <b> 1301, transition destination activity information, and the version number of the referring organization. And proceeds to step S1302.

  In step S1302, the person-in-charge determination unit 303 refers to the process definition information associated with the job stored in the process definition information storage unit 310, and is defined in the definition information of the transition destination activity. The department identification information and the role identification information of the person in charge are acquired, and the process proceeds to the person-in-charge search process in S1303. Details of the person-in-charge search process in step S1303 are shown in FIG. 14 to be described later. At least one or more of the organization version number, department information of the person in charge, and role information of the person in charge is included. The user position information is retrieved, and the process proceeds to step 1304.

  Next, in step S1304, the person-in-charge determination unit 303 allocates part or all of the user position information searched in the person-in-charge search process in S1303 as a person in charge of the transition destination activity of the job, and a job information storage unit The job information is stored in 311 as part of the job information, and the process proceeds to step S1305.

  In step S1305, the person-in-charge determination unit 303 refers to the user position information, notifies the corresponding user by e-mail or the like, and ends the process of this flowchart. Note that the notification processing in S1305 is not essential.

  As described above, by performing the processing as shown in FIG. 13, it is possible to search for and assign the person in charge at the job transition destination activity in the version of the organization referred to by the job.

  Hereinafter, the person-in-charge search process shown in step S1303 of FIG. 13 will be described with reference to FIG.

  FIG. 14 is a flowchart showing an example of a fifth control processing procedure in the present invention, and corresponds to the person-in-charge search processing shown in step S1303 of FIG. That is, the processing of this flowchart is realized by the CPU 101 of the workflow server 101 loading the program 212 stored in the external memory 211 into the RAM 202 and executing it.

  First, the person-in-charge determination unit 303 is given the department identification information of the person in charge, the role identification information of the person in charge, and the version number of the organization. In step S1401, the person-in-charge determination unit 303 receives the user position information. With reference to the user position information stored in the storage unit 315, the department identification information of the person in charge matches the department ID 902, the role identification information of the person in charge matches the role ID 903, and the version of the organization User position information satisfying all that the number is greater than or equal to the start version number 905 and that the version number of the organization is less than the end version number 906 is searched, and the process proceeds to step S1402.

  In step S1402, the person-in-charge determination unit 303 determines whether at least one corresponding user position information is searched in step S1401.

  In step S1402, if it is determined in step S1401 that one corresponding user position information does not exist (No), the person-in-charge determination unit 303 advances the process to step S1403.

  In step S1403, the person-in-charge determination unit 303 refers to the department information stored in the department information storage unit 313, the department identification information of the person in charge matches the department ID 701, and the version number of the organization is the start version. The user position information satisfying all that the number 704 and the organization version number are the end version number 705 are searched, and the value of the department identification information of the parent department ID 703 that is the department information item is used to search for the person in charge. The department identification information is rewritten, and the process returns to step 1401.

  On the other hand, in step S1402, if it is determined in step S1401 that at least one corresponding user position information has been searched (exists) (Yes), the person-in-charge determination unit 303 advances the process to step S1404.

  In step 1404, the person-in-charge determination unit 303 returns at least one user position information searched in step 1401 to the caller (the process in FIG. 13) as a result of the person-in-charge search process, and ends the process of this flowchart. .

  As described above, by performing the processing shown in FIG. 14, the department hierarchy is moved up based on the department identification information and role identification information defined in the activity, particularly when the user position of the corresponding role does not exist in the department. It is possible to search for a corresponding user position while climbing.

  Hereinafter, with reference to FIG. 15, the request waiting process shown in step S404 of FIG. 10 will be described.

  FIG. 15 is a flowchart showing an example of a sixth control processing procedure according to the present invention, and corresponds to the request wait processing shown in step S404 of FIG. That is, the processing of this flowchart is realized by the CPU 101 of the workflow server 101 loading the program 212 stored in the external memory 211 into the RAM 202 and executing it.

  As shown in FIG. 15, in step S1501, the input / output processing unit 301 waits for input of some input information from the input controller 205 or the communication I / F controller 208 of the workflow server 101. When the input is received, the input / output processing unit 301 proceeds to step S1502. Proceed with the process.

  In step S1502, the input / output processing unit 301 determines whether the input is a “workflow execution request”.

  If it is determined in step S1502 that the input is not “workflow execution request” (that is, “organization registration request” or “other workflow server 101 corresponds”), the input / output processing unit 301 is not illustrated. In step, the request is processed, and the process returns to step S1501.

  On the other hand, if it is determined in step S1502 that the input is “workflow execution request”, the input / output processing unit 301 ends the processing of this flowchart.

  Hereinafter, the work item approval process shown in step S407 of FIG. 10 will be described with reference to FIG.

  FIG. 16 is a flowchart showing an example of the seventh control processing procedure in the present invention, and corresponds to the work item approval processing shown in step S407 of FIG. That is, the processing of this flowchart is realized by the CPU 101 of the workflow server 101 loading the program 212 stored in the external memory 211 into the RAM 202 and executing it.

  As shown in FIG. 16, first, in step 1601, the workflow progression unit 302 acquires the work item approval request received by the input / output processing unit 301, and advances the process to step S <b> 1602.

  In step S1602, it is determined whether the work item approval request acquired in S1601 is to “approve” the activity, or to reject the activity and “send back”. This determination is performed by referring to a flag or the like included in the work item approval request.

  If it is determined in step S1602 that the work item approval request acquired in S1601 is to “approve” the activity, the workflow progression unit 302 advances the process to step S1603.

  In step S <b> 1603, the workflow progression unit 302 refers to the job information stored in the job information storage unit 311, acquires information about the current transition destination activity, and stores the process definition stored in the process definition information storage unit 310. Information is acquired, the next activity information of the current transition destination activity is acquired, the next activity is newly set as the transition destination activity, the job information is stored in the job information storage unit 311, and this work item approval process Exit.

  On the other hand, if it is determined in step S1602 that the work item approval request acquired in S1601 denies the activity and “sends back”, the workflow progression unit 302 advances the process to step S1604.

  In step 1604, the workflow progression unit 302 refers to the job information stored in the job information storage unit 311, acquires information about the current transition destination activity, and stores the process definition stored in the process definition information storage unit 310. Information is acquired, activity information at least one current transition destination activity is acquired, the next activity is newly set as a transition destination activity, job information is stored in the job information storage unit 311, Finish the work item approval process.

  As described above, by performing the processing as shown in FIG. 16, it is possible to determine the transition destination activity for each work item approval request and advance the workflow to the next person in charge.

  Hereinafter, with reference to FIG. 17, the organization replacement process shown in step S408 of FIG. 10 will be described.

  FIG. 17 is a flowchart showing an example of the eighth control processing procedure in the present invention, and corresponds to the organization replacement processing shown in step S408 of FIG. That is, the processing of this flowchart is realized by the CPU 101 of the workflow server 101 loading the program 212 stored in the external memory 211 into the RAM 202 and executing it.

  As shown in FIG. 17, in step S1701, the organization reassigning unit 305 receives a job to be reassigned and the designation of the version of the organization to be reassigned via the input / output processing unit 301, and reconfirms the version in S1702. Proceed to the process.

    In the version reconfirmation process in step S1702, the organization reassigning unit 305 requests the person-in-charge determination unit 303 to reconfirm the version number of the organization to be reassigned, with the designation of the version of the organization to be reconstituted. The received version number of the organization is received, and the process proceeds to step S1703. The details of the version number reconfirmation process are as shown in FIG.

  Next, in step S1703, the organization replacement unit 305 refers to the job information stored in the job information storage unit 311, acquires the version number of the organization currently referred to by the job to be replaced, The process proceeds to the person-in-charge search process in S1704.

  In the person-in-charge search process in step S1704, the organization distribution unit 305 determines, based on the job information referenced in step S1703, the department identification information in charge of the current transition destination activity, the role identification information in charge of the current transition destination activity, Along with the version number of the organization that the job is currently referring to, the person-in-charge determination unit 303 is requested to search for user position information to be the person in charge, the result is received, and the process proceeds to the person-in-charge search process in S1705. The details of the person-in-charge search process are as shown in FIG.

  Next, in the person searching process in step S1705, the organization distribution unit 305 determines the department identification information in charge of the current transition destination activity and the role identification information in charge of the current transition destination activity from the job information referenced in step S1703. Then, with the version number of the organization to be replaced determined in the version determination process S1702, the person-in-charge determination unit 303 is requested to search for user position information to be a person in charge, the result is received, and the process proceeds to step S1706. The details of the person-in-charge search process are as shown in FIG.

  In step S1706, the organization distribution unit 305 compares the user position information searched in S1704 with the user position information searched in S1705.

  If it is determined in step S1706 that there is a difference between the user position information searched in step S1704 and the user position information searched in step S1705, the organization distribution unit 305 advances the process to step S1708.

  In step S1708, the organization distribution unit 305 refers to the user position searched in the person-in-charge search process S1704, notifies the corresponding user by mail or the like, and advances the process to step S1709. Note that the notification processing in S1708 is not essential.

  In step S1709, the organization distribution unit 303 discards any information related to the assignment from the job information stored in the job information storage unit 311 and advances the process to step S1710.

  In step S <b> 1710, the organization replacement unit 303 stores the version number of the organization to be replaced as job related information in the job information storage unit 311 together with other attributes of the job, and advances the processing to the person-in-charge assignment processing in step S <b> 1711.

  In the person-in-charge assignment process in step S1711, the organization assignment unit 303 requests the person-in-charge determination unit 303 to perform person-in-charge assignment processing, and ends the organization assignment process. The details of the person-in-charge assignment process are as shown in FIG. 13 described above. However, since the version of the organization referred to by the job has been changed to the version of the organization to be replaced in step S1710, The result of (S1711) is the person in charge in the version of the organization to be replaced.

  On the other hand, in step S1706, as a result of the comparison, if both the user position information searched in S1704 and the user position information searched in S1705 are the same, the organization assigning unit 305 advances the process to step S1707.

  In step S1707, the organization replacement unit 305 stores the version number of the organization to be replaced as job related information in the job information storage unit 311 together with other attributes of the job, and ends the organization replacement processing. In step S1707, processing similar to that in step S1710 is performed, but the person-in-charge assignment processing is not requested. This is because it has been determined that there is no change in the person in charge as a result of the determination in step 1706.

  If the version number reconfirmed in step S1702 matches the version identification information associated with the job acquired in step S1702 (that is, version identification information before reconfirmation), the processes in and after step S1704 are performed. You may comprise so that this organization distribution process may be complete | finished as it is, without performing.

  As described above, by performing the process shown in FIG. 17, it is possible to specify a specific job and change the version of the organization. At that time, if there is no change in the person in charge, an unnecessary user It is possible to suppress the occurrence of notification, reassignment processing, and re-approval of approval accompanying this.

  By having the above-mentioned form, for example, even if a manager is changed while a user belongs to the same department, based on the organization version to which the job confirmed at the time of application is related It is possible to automatically determine that the section manager in the version of the organization should approve and notify the section manager to be approved.

  In addition, since the version of the organization to which a job refers is specified by having the above-described form, the version of the future organization is registered in advance, and the current job does not refer to the version of the organization. However, it is possible to refer to the organization's version for jobs after that point in the future, and it is not necessary to stop the system due to the switching of the organization, which helps to improve the availability of the workflow system. .

  In addition, by having the form as described above, it is possible to switch the version of the organization to be referred to according to the type of business, etc., or to change the version of the organization even if it is an ongoing job. It is possible to cope with the case where only the progress of the workflow is desired to be operated in the current organization, and the workflow can be performed flexibly.

  Usually, in a company, personnel information is snapshot information at that time, and there are often cases where there is no difference information from the previous organization or it is complicated to create difference information.

  In the present invention, as shown in FIGS. 6, 7, and 8, the organization information is composed of a range of version numbers in which each organization element continues. Difference information, that is, additional information, change information, and deletion information are required.

  However, as mentioned above, many companies do not maintain the difference information and its creation is complicated, so it is possible to delete all organizational elements and then add all existing elements. Many.

  However, when this method is used, as shown in FIG. 18, since the organization elements that continue to exist are once deleted for each version, there is a problem that the data amount of the organization information is greatly increased. It was.

  FIG. 18 is an image diagram for explaining problems in conventional organization registration.

  In order to prevent this, the organization information registration unit 304 shown in FIG. 3 performs the organization registration method as shown in FIG.

  Hereinafter, the organization information update process in the organization information registration unit 304 shown in FIG. 3 will be described with reference to FIG.

  FIG. 19 is a diagram showing an example of organization information update processing in the workflow server 101 to which the present invention is applicable.

  FIG. 19 is a flowchart showing an example of a ninth control processing procedure according to the present invention, and corresponds to the organization registration processing executed by the organization information registration unit 304 and the like shown in FIG. That is, the processing of this flowchart is realized by the CPU 101 of the workflow server 101 loading the program 212 stored in the external memory 211 into the RAM 202 and executing it.

  As illustrated in FIG. 19, when the input / output processing unit 301 waits for input of an organization editing (update) command from the input controller 205 or the communication I / F controller 208 of the workflow server 101 and receives the input in step S2001. Then, the process proceeds to step S2002. The organization editing command includes a command type and element data as items. The command type includes “clear”, “add”, “change”, “delete”, and the like, and the element data includes data such as element identification information corresponding to each command. Note that the organization editing command can be used to input a plurality of commands together. In that case, the organization registration unit 305 repeats the processes in steps S2002 to S2013 for the organization editing command. That is, the processes in steps S2002 to S2013 are executed for each organization editing command.

  In step S2003, the organization registration unit 305 determines whether the command type of the organization editing command to be processed is “clear”. If it is determined that it is “clear” (Yes), the organization registration unit 305 proceeds to step S2004. Proceed with the process.

  In step S2004, the organization registration unit 305 acquires all the elements existing in the previous version from the department information storage unit 313, for example, all the end version numbers are “HV”, and performs the process in step S2005. Proceed.

  In step S2005, the organization registration unit 305 sets the current version as the end version of the element acquired in step S2004, stores the current version in, for example, the department information storage unit 313, and advances the process to step S2013. It should be noted that all elements are once deleted in the current version by the processing in step S2005.

  On the other hand, if it is determined in step S2003 that the command type of the organization editing command to be processed is not “clear” (No), the process proceeds to step S2006.

  In step 2006, the organization registration unit 305 acquires information on the corresponding element from, for example, the department information storage unit 313 based on the identification information included in the element data of the organization editing command, and advances the process to step S2007.

  In step S2007, the organization registration unit 305 determines the command type of the organization editing command to be processed.

  If it is determined in step S2007 that the command type is “delete”, the organization registration unit 305 advances the process to step S2012.

  In step S2012, the organization registration unit 305 sets the current version as the end version number of the corresponding element acquired in step S2006, stores the current version in, for example, the department information storage unit 313, and advances the process to step S2013. By this processing, the information of the element designated by the identification information is in a state deleted in the current version.

  If it is determined in step S2007 that the command type is “change”, the organization registration unit 305 advances the process to step S2011.

  In step S2011, the organization registration unit 305 sets the current version as the end version number of the corresponding element acquired in step S2006, stores the current version in, for example, the department information storage unit 313, and advances the process to step S2010.

  In step S2010, a new element is created based on the element data of the organization editing command to be processed, the start version number (start information) is set to the current version, and the end version (end information) is set to “HV”. For example, information on the corresponding element is added to the department information storage unit 313, and the process proceeds to step S2013. As a result of the processing of step S2011 and step S2010, the organization element identified by the identification information included in the element data of the organization editing command has been changed in the current version.

  If it is determined in step S2007 that the command type is “addition”, the organization registration unit 305 advances the process to step S2008.

  In step S2008, the organization registration unit 305 determines whether the version number set in the end version number of the corresponding element acquired in step S2006 is equal to the version number of the current version.

  If it is determined in step S2008 that the version number set in the end version number of the corresponding element acquired in step S2006 is not equal to the version number of the current version (No), the organization registration unit 305 determines whether the version number is the same as in step S2010. Is executed, and the process proceeds to step S2013. Through the processing of step S2008 and step S2010, the organization element identified by the identification information included in the element data of the organization editing command is added in the current version.

  On the other hand, if it is determined in step S2008 that the version number set in the end version number of the corresponding element acquired in step S2006 is equal to the version number of the current version (Yes), the organization registration unit 305 proceeds to step S2009. Proceed with the process.

  In step S2009, the version number set in the end version number of the corresponding element acquired in step S2006 is changed to “HV” and set, for example, stored in the department information storage unit 313, and the process proceeds to step S2013. . As a result of the processing in steps S2008 and S2009, the organization element identified by the identification information included in the element data of the organization editing command has been continued from the previous version.

  In step S2013, if the organization registration unit 305 determines that the processing in steps S2002 to S2013 has not been completed for all the commands that have been input, the next command is transferred to the processing target. The process returns to S2002.

  On the other hand, in step S2013, if the organization registration unit 305 determines that the processing in steps S2002 to S2013 has been completed for all input commands, the organization editing processing ends.

  Here, the registration process of the department information storage unit 313 is given as an example, but the same applies to the registration process of other information. The department information registration unit 312 is a storage destination when registering department information, the role information storage unit 314 is a storage destination when registering role information, and the user position information 314 is a storage destination when registering user position information. Needless to say.

  As described above, by performing the processing as shown in FIG. 19, even if the organization is registered by a method of clearing once and adding the whole, the amount of data increases due to being shredded as shown in FIG. And can be managed as a continuous organization element as shown in FIG. That is, even if editing is performed by batch processing that does not take into account the difference, if the version number set in the end version number of the element corresponding to the command is equal to the version number of the current version in the processing of steps S2008 and S2009, By changing the version number set to the end version number of the element corresponding to the command to “HV” and setting it, the occurrence of the situation that the number of data records becomes enormous (FIG. 18) is suppressed. (FIG. 20).

  FIG. 20 is an image diagram at the time of organization registration in the organization registration processing of the present invention.

  As described above, according to the present invention, it is possible to register a plurality of versions of organization information used for a workflow, and the workflow proceeds according to the version of the organization designated at the start, that is, each person in charge in the designated version of the organization. Therefore, even if the organization is changed at the beginning of the month, for example, the liquidation process for the previous month and the application process for the current month can be processed at the same time without contradiction. That is, it is possible to make the job proceed according to the snapshot of the organization information at the start of the workflow and not be affected by the organization change.

  Further, future organization information can be registered regardless of the state of the workflow. Also, it cannot be used until it is activated.

  In addition, even a workflow in progress in an old version organization can be switched to operation in the current version organization. And it is possible to suppress redoing of a conference that may occur due to such switching.

  In addition, although a plurality of versions of an organization are managed, the number of data records can be reduced by efficiently managing the portion of data that is not changed. In addition, it is possible to suppress the occurrence of a situation in which the number of data records becomes enormous even if editing is performed by batch processing that does not consider differences.

  Therefore, there is an effect that workflows progressing in a plurality of versions of the organization including new and old can coexist and can be processed without contradiction. That is, the workflow that progresses in the old organization and the workflow that progresses in the new organization can coexist without contradiction. Furthermore, the workflow that progresses in the old organization can be changed to progress in the new organization.

  It should be noted that the configuration and contents of the various data described above are not limited to this, and it goes without saying that the various data and configurations are configured according to the application and purpose.

  Although one embodiment has been described above, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or recording medium, and specifically includes a plurality of devices. The present invention may be applied to a system including a single device.

  The configuration of the data processing program that can be read by the workflow server according to the present invention will be described below with reference to the memory map shown in FIG.

  FIG. 21 is a diagram illustrating a memory map of a recording medium (storage medium) that stores various data processing programs readable by the workflow server according to the present invention.

  Although not specifically shown, information for managing a program group stored in the recording medium, for example, version information, creator, etc. is also stored, and information depending on the OS on the program reading side, for example, a program is identified and displayed. Icons may also be stored.

  Further, data depending on various programs is also managed in the directory. In addition, when a program or data to be installed is compressed, a program to be decompressed may be stored.

  The functions shown in FIGS. 10, 11, 12, 13, 14, 15, 16, 17, and 19 in this embodiment may be executed by a host computer by a program installed from the outside. Good. In this case, the present invention is applied even when an information group including a program is supplied to the output device from a recording medium such as a CD-ROM, a flash memory, or an FD, or from an external recording medium via a network. Is.

  As described above, a recording medium in which a program code of software for realizing the functions of the above-described embodiments is recorded is supplied to the system or apparatus, and the computer (or CPU or MPU) of the system or apparatus is stored in the recording medium. It goes without saying that the object of the present invention can also be achieved by reading and executing the program code.

  In this case, the program code itself read from the recording medium realizes the novel function of the present invention, and the recording medium storing the program code constitutes the present invention.

  As a recording medium for supplying the program code, for example, a flexible disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD-R, DVD-ROM, magnetic tape, nonvolatile memory card, ROM, EEPROM, A silicon disk or the like can be used.

  Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (operating system) or the like running on the computer based on the instruction of the program code. It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the actual processing and the processing is included.

  Furthermore, after the program code read from the recording medium is written in a memory provided in a function expansion board inserted in the computer or a function expansion unit connected to the computer, the function expansion is performed based on the instruction of the program code. It goes without saying that the case where the CPU or the like provided in the board or the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

  Further, the present invention may be applied to a system composed of a plurality of devices or an apparatus composed of a single device. Needless to say, the present invention can be applied to a case where the present invention is achieved by supplying a program to a system or apparatus. In this case, by reading a recording medium storing a program represented by software for achieving the present invention into the system or apparatus, the system or apparatus can enjoy the effects of the present invention.

  Furthermore, by downloading and reading out a program represented by software for achieving the present invention from a server, database, etc. on a network using a communication program, the system or apparatus can enjoy the effects of the present invention. It becomes.

  In addition, all the structures which combined each embodiment mentioned above and its modification are also included in this invention.

FIG. 1 is a diagram illustrating an example of a workflow system to which an embodiment of the present invention can be applied. It is a block diagram which shows an example of the hardware constitutions of the workflow server 101 and the workflow client 102 as an information processing apparatus applicable to this invention shown in FIG. It is a figure which shows an example of the function structure implement | achieved in the workflow server 101 shown in FIG. It is a figure which shows an example of the process definition information stored in the process definition information storage part 310 shown in FIG. It is a figure which shows an example of the structure | tissue used for description of this embodiment. It is a figure which shows an example of the department information stored in the department information storage part 313 shown in FIG. It is a figure which shows an example of the role information stored in the role information storage part 314 shown in FIG. It is a figure which shows an example of the user position information stored in the user position information storage part 315 shown in FIG. It is a figure which shows an example of the version effective period information stored in the version effective period information storage part 312 shown in FIG. It is a flowchart which shows an example of the 1st control processing procedure in this invention. It is a flowchart which shows an example of the 2nd control processing procedure in this invention. It is a flowchart which shows an example of the 3rd control processing procedure in this invention. It is a flowchart which shows an example of the 4th control processing procedure in this invention. It is a flowchart which shows an example of the 5th control processing procedure in this invention. It is a flowchart which shows an example of the 6th control processing procedure in this invention. It is a flowchart which shows an example of the 7th control processing procedure in this invention. It is a flowchart which shows an example of the 8th control processing procedure in this invention. It is an image figure for demonstrating the problem at the time of the conventional organization registration. It is a flowchart which shows an example of the 9th control processing procedure in this invention. It is an image figure at the time of the organization registration in the organization registration process of this invention. It is a figure explaining the memory map of the recording medium (storage medium) which stores the various data processing program which can be read by the workflow server which concerns on this invention.

Explanation of symbols

100 Network 101 Workflow Server 102 Workflow Client 201 CPU
202 RAM
211 External Memory 212 Program 301 Input / Output Processing Unit 302 Workflow Progression Unit 303 Personnel Determination Unit 304 Organization Information Registration Unit 305 Organization Replacement Unit 310 Process Definition Information Storage Unit 311 Job Information Storage Unit 313 Department Information Storage Unit 314 Role Information Storage Unit 315 User position information storage unit 312 Version validity period information storage unit 312

Claims (8)

An information processing apparatus that controls a workflow of a job whose transition path is defined by organization information,
Organization information storage means that can store and store multiple versions of organization information by holding version identification information that can identify one or more versions for which the record is valid for each record of organization information;
Version validity period information storage means for storing date and time information for specifying a period of validity for each version;
Version confirmation means for confirming version identification information and associating it with the job based on information for confirming a version of organization information associated with the job specified when the job is created;
Workflow progress means for determining a transition destination of the job based on the version identification information associated with the job, causing the job to transition to the determined transition destination, and progressing the workflow;
When an organization information reassignment request is made for the job, version identification information associated with the job based on information for determining the version of the organization information associated with the job specified in the reassignment request. A reconfirmation means for reconfirmation;
An information processing apparatus comprising:   The information for determining the version of organization information associated with the job is date information of organization information associated with the job or version identification information of organization information associated with the job. The information processing apparatus described. An organization distribution unit that changes a transition destination of the job according to the version identification information reconfirmed by the reconfirmation unit;
When the job transition destination based on the version identification information reconfirmed by the reconfirmation means matches the job transition destination based on the version identification information before reconfirmation, the organization distribution means matches the job The information processing apparatus according to claim 1, wherein the transition destination is not changed.   The reconfirmation means does not reassociate the version identification information when the reconfirmed version identification information matches the version identification information before the reconfirmation. 2. The information processing apparatus according to 2. The organization information storage means holds, for each record of the organization information, version identification information from which the record is validly started as start information and version identification information from which the record is validly ended as end information. ,
Providing an organization information updating means for updating the organization information;
The organization information update means adds a new record corresponding to the element when adding a new element to the organization information, and records corresponding to the element when deleting an element. The updated version identification information is set in the end information of the file, and when the element is changed, the updated version identification information is set in the end information of the record corresponding to the element and the new information corresponding to the element is set. Adding a record to the organization information,
Further, the organization information update means adds an element to the organization information when an existing record corresponding to the element exists and the end information of the existing record matches the updated version identification information. The information processing apparatus according to claim 1, wherein, instead of adding a new record, the end information of the existing record is invalidated. A workflow control method for controlling a workflow of a job whose transition route is defined by organization information,
Organization information registration for registering multiple versions of organization information together in the storage means by holding version identification information that can identify one or more versions for which the record is valid for each organization information record Steps,
A version validity period information storing step for storing date and time information for specifying a period of validity for each version;
A version confirmation step for confirming version identification information based on information for confirming a version of organization information associated with the job specified when the job is created and associating with the job;
A workflow progress step for determining a transition destination of the job based on the version identification information associated with the job, causing the job to transition to the determined transition destination, and advancing the workflow;
When an organization information reassignment request is made for the job, version identification information associated with the job based on information for determining the version of the organization information associated with the job specified in the reassignment request. A reconfirmation step to reconfirm,
A workflow control method characterized by comprising: A computer that controls the workflow of the job whose transition route is defined by the organization information,
Organization information registration for registering multiple versions of organization information together in the storage means by holding version identification information that can identify one or more versions for which the record is valid for each organization information record Step,
A version validity period information storage step for storing date and time information for specifying a validity period for each version;
A version confirmation step for confirming version identification information and associating it with the job based on information for confirming a version of organization information associated with the job specified when the job is created;
A workflow progress step for determining a transition destination of the job based on the version identification information associated with the job, and causing the job to transition to the determined transition destination to advance the workflow;
When an organization information reassignment request is made for the job, version identification information associated with the job based on information for determining the version of the organization information associated with the job specified in the reassignment request. A reconfirmation step to reconfirm,
A program for running A computer that controls the workflow of the job whose transition route is defined by the organization information,
Organization information registration for registering multiple versions of organization information together in the storage means by holding version identification information that can identify one or more versions for which the record is valid for each organization information record Step,
A version validity period information storage step for storing date and time information for specifying a validity period for each version;
A version confirming step for confirming version identification information based on information for confirming a version of organization information associated with the job specified when the job is created and associating with the job;
A workflow progress step for determining a transition destination of the job based on the version identification information associated with the job, and causing the job to transition to the determined transition destination to advance the workflow;
When an organization information reassignment request is made for the job, version identification information associated with the job based on information for determining the version of the organization information associated with the job specified in the reassignment request. A reconfirmation step to reconfirm,
The computer-readable recording medium which recorded the program for performing this.

Images