JP5493565B2 - Information processing apparatus, information processing system, information processing method, program, and recording medium - Google Patents

Description

  The present invention relates to a workflow system that manages a workflow according to a version-managed business design.

  In recent years, various business processes have been systemized in a company, but functions for managing changes to an IT system and preventing falsification are becoming indispensable depending on social IT control needs.

  In the normal workflow system, in order to prevent data tampering, the already created matter data is not allowed to be involved by anyone other than those authorized for processing in the business design, and it is modified to be an exception in some cases as an administrator. Not allowed to do.

  Also, for the purpose of preventing tampering, it is not allowed to modify a business design created in a certain version.

  Patent Document 1 discloses a workflow system that operates a plurality of workflows in parallel.

  Further, Patent Document 2 discloses a workflow system that makes it possible to freely change an organization of an ongoing workflow by coexisting workflows of a plurality of versions including old and new.

JP 2005-92544 A JP 2008-310710 A

  However, the technique described in Patent Document 1 allows a plurality of workflows to be operated in parallel, and can be operated as a workflow system capable of version management by handling each workflow as a version. However, if you notice a mistake in the created workflow design, you cannot continue to operate with the new workflow.

  In such a workflow system, if there is an error in the input check on the application screen, or if there is an error in the condition judgment for advancing the workflow, the job design will not be able to be corrected and the matter data will not be retained. Resulting in. In order to eliminate the stagnation, it is necessary to re-apply for all the remaining projects after creating and correcting a new version of the business design, which is problematic. In addition to the above-mentioned mistakes in business design, correction of the form text and change of layout may occur due to external factors (company name change, legal system revision), and the like. When long-term business operation is assumed, it is necessary to change the business design, and a mechanism is required to continuously operate the ongoing workflow with the changed business design.

  Further, although the technique described in Patent Document 2 allows the organization of an ongoing workflow to be freely changed, the work design of the ongoing workflow cannot be changed. For this reason, the design information of an ongoing project cannot be changed.

  The present invention solves the above-described problems, and an object of the present invention is to make it possible to change the design information of an ongoing item without re-applying the item in the workflow system.

The present invention is an information processing apparatus that can change a version of a business design that holds data definition information of data constituting the item as an item definition, which is a basis of the item in progress in a workflow procedure. A matter accepting means for accepting selection of a product, a storage means for storing a plurality of versions of the work design, and an instruction to change the version of the work design that is the basis of the ongoing work accepted by the matter accepting means to another version a changing instruction receiving means, before Symbol pre-change items defined in the pre-change operations design selection of which is accepted by the projects receiving unit, not removed in the item definitions of the changed operational design after the change, or the change by previous item definition to verify that the changes of attributes in the item definition after change is not performed, re-monkey the matter And confirmation means for performing the confirmation of being a possible replacement is to the change before the business design business design after the change without the need for, the replacement is possible without requiring a re-application of the project by the confirmation means If the confirmation of were taken at the operational design version as the projects based ongoing accepted by the project receiving means, and changing means for changing to a different version of the business design the change instruction has been made It is characterized by having.

  According to the present invention, in the workflow system, it is possible to change the design information of an ongoing case without re-applying the case.

System configuration diagram showing the configuration of the workflow system Diagram showing hardware configuration of various terminals The figure which shows an example of the function structure in a workflow server Diagram showing the data structure of business design and matter information Sample screen for registering a business design Examples of various editor screens An example of a stagnant project that has been reassigned when a stagnancy occurs Example of item information (item knowledge blank) Example of project information (V1) Example of business design (add V2) Example of form editor (example of adding items) Example of business maintenance screen Example of project information (V2) Flow chart showing the flow of business version replacement processing Flow chart showing the flow of consistency check processing

  Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a system configuration diagram showing a configuration of a workflow system (information processing system) according to the present invention.

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

  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 according to the request, and transmits a result 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. Further, the workflow server 101 is connected to the DB server 103 via the network, and the processing history data 104 is held in the DB server 103.

  FIG. 2 is a diagram showing a hardware configuration of various terminals according to the embodiment of the present invention.

  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. Moreover, in a printing apparatus etc., a touch panel, a button, a switch, etc. are mentioned.

  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, various tables and parameters for realizing various functions of each server or each client are stored. 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.

  A program 212 for realizing the present invention 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 showing an example of a functional configuration in the workflow server (information processing apparatus) of the present invention.

  The workflow processing unit 301 receives a request from the workflow client 102 operated by a general user, creates item information based on the business design information stored in the business design storage unit 310, and stores the item information in the case information storage unit 320. Is stored. Further, the workflow processing unit 301 receives a request from the workflow client 102 operated by a general user, extracts the case information from the case information storage unit 320, and advances the workflow and updates the case information. When the workflow processing unit 301 updates the workflow and the item information, the workflow processing unit 301 performs processing according to the definition set in the business design information stored in the business design storage unit 310.

The version information replacement processing unit 302 receives a job design version replacement request (or replacement instruction, change request, change instruction) of a case from the workflow client 102 operated by the management user, and is stored in the case information storage unit 320. A process is performed in which a reference to a specific version of business information referred to by one item information is replaced with another version of business information. (Replacement is also called change. The same shall apply hereinafter.)
FIG. 4 is a diagram illustrating a data structure of business design and item information.

  The business design 311 is information stored in the business design storage unit 310, and includes a business definition 401, a path definition 402, a form definition 403, and an item definition 404 as actual data. It also contains multiple versions of business design information. When a replacement instruction, which will be described later, is given, the definition information of the version before change and the version after change is used from the business design information of multiple versions.

  In this business design 311, an administrative user uses the workflow client 102 to perform registration before starting a workflow.

  The business definition 401 holds definition information for specifying the business design 311. The business definition 401 holds a business ID and a business version number as information for identifying one of the business designs. The business definition 401 holds a business name, a valid period From, and a valid period To. The effective period From and the effective period To indicate the effective period of the business definition 401 in combination, and are used to specify the effective business definition at the time of drafting the case.

  The route definition 402 holds workflow flow (procedure) definition information. The route definition 402 holds a business ID and a business version number as information for indicating a relation to the business definition 401, and specifies one route definition by combining the business ID, the business version number, and the route ID. It is held as information for The route definition 402 holds a route name and route data definition information. The route data holds definition information such as “who can apply / approve” and “which form definition is used in the application”.

  The form definition 403 holds screen definition information directly operated by a user who operates the workflow. The form definition 403 holds a business ID and a business version number as information for indicating a relation to the business definition 401, and specifies one form definition by combining the business ID, the business version number, and the form ID. It is held as information for The form definition 403 holds definition information such as a form name and form data. Form data not only includes "form layout definition used for application and approval", but also processing logic such as "input content check logic when approval button is pressed" and "initial value display logic when screen is opened" doing.

  The item definition 404 holds data definition information such as the type and length of data that the case information 321 should hold. The item definition 404 holds a business ID and a business version number as information for indicating a relation to the business definition 401, and specifies one item definition by combining the business ID, the business version number, and the item ID. It is held as information for The item definition 404 holds definition information such as an item name, a type, and a length.

  As described above, the business design 311 is for the management user to register using the workflow client 102 before starting the workflow.

  Although the valid business design 311 cannot be corrected after reaching the effective period From, according to the present embodiment, a new version of the business design 311 is created and the business design 311 is changed. Therefore, the management user can perform maintenance of the business design without any time constraints.

  Next, the item information 321 is information stored in the item information storage unit 320 and includes item data 405 and item child data 406 as actual data.

  This item information 321 is data created when a user starts a workflow using the workflow client 102.

  The case data 405 holds data information for specifying the case information 321. Further, the case data 405 holds a business ID and a business version number as information for indicating a relation to the business definition 401, and information for specifying one piece of business data by combining the business ID and the business ID. Hold as. The item data 405 also holds a business version number, a workflow progress status, and the like.

  The case child data 406 holds actual data of the case information 321. Further, the case child data 406 holds a business ID and a case ID as information for indicating a relation to the case data 405, and specifies one case child data by combining the business ID, the case ID, and the item ID. To keep as information. The business ID, business version number, and item ID are also used as information for specifying the item definition 404 that is the definition information of the case child data 406. The case child data 406 holds a business version number and item value as actual data information of the case.

  By the way, normally, the business design 311 that is effective at the time of project creation is used to create a business case. However, depending on the workflow system, the past and future time points are specified, and the business design that is effective at the specified time point. It is also possible to construct a system that can create a case using 311.

  The item data 405 shown in FIG. 4 is associated with only one business definition 401. However, according to the present embodiment, it is possible to hold a plurality of business definitions at the time of drafting and a plurality of business definitions after replacement processing. It is.

  On the other hand, in a workflow system that has only one relationship to the business definition, for example, there is an item waiting for approval in the final approval process, and in the post-replacement business design route definition, there is no final approval process, Options such as whether it should be judged that the final approval has been made, whether it should be rejected as unsuccessful, whether it should be returned to the previous process, or whether an appropriate process should be selected and the flow continued from there It is necessary to choose.

  However, in the workflow system that holds multiple relations to the business design in the case in this embodiment, the change of the route definition is not a change that is performed more frequently than the change of the layout such as the form definition. Rather than complicating the process at the time of reassignment, even if the route definition is reassigned, it continues to use the one at the time of drafting and restricts only the form definition and item definition to be associated with the new business design. Thus, it is possible to reduce the burden of the replacement process.

  FIG. 5 is an example of a screen for registering a business design.

  The business design is edited and registered by the management user by operating the workflow client 102.

  Specifically, using the item editor 501, the route editor 502, and the form editor 503, the business design 311 is edited and registered.

  The item editor 501 is a screen for registering the definition information of the business definition 401 and the item definition 404 shown in FIG. In this example, values entered in the fields of “business ID”, “business version”, “business name”, and “validity period” are registered in the business definition 401, and “item ID”, “item name”, “ Values entered in “type”, “character”, etc. are registered in the item definition 404.

  The route editor 502 is a screen for registering the definition information of the route definition 402 shown in FIG. In this example, a route along which the workflow proceeds is defined in the order of “application”, “approval”, and “final approval”.

  The form editor 503 is a screen for registering definition information of the form definition 403 shown in FIG. The form editor 503 can register not only the form layout but also processing logic such as processing contents when a button is pressed on the form and initial display when the form is opened. In this example, “Click [FORM_SYONIN] _approval” 5031 describes an input check and a call for an approval request to the workflow server as processing when the approval button of the FORM_SYONIN form is clicked. As a specific example, the input check includes an error (“input check for non-existing item ITEM_SYONINSYA” is performed) in order to explain the replacement of the work described later.

  FIG. 6 shows a specific example of the business design 311 edited and registered through the various editors.

  Next, with reference to FIGS. 7 to 13, a specific example will be described in which the drafted case stays and the case flows safely by changing the business.

  FIG. 7 is a diagram illustrating an example in which a staying matter is advanced by changing work when the staying occurs.

"Step 1"
This indicates that the workflow server has generated a matter and a workflow in response to a request from the workflow client operated by the user. It is assumed that the generated case is set to refer to the work definition V1 that is valid at this time. An example of item information (including item data 405 and item child data 406) at this time is shown in FIG. The combination of the business ID and the business version number registered in the case data indicates a reference to the business design 311 that is the business definition V1 shown in FIG.

"Step 2"
This indicates that the workflow server has advanced the flow of the matter to the approval process in response to an application request from the workflow client operated by the user. An example of item information (including item data 405 and item child data 406) at this time is shown in FIG. The application contents are registered as item values in the item child data.

"Step 3"
A case will be described as an example where there is an error in the registered contents in the form editor 503 that “the item ITEM_SYONINSYA is being checked for input”.

  In this case, even if the approval instruction is given by the workflow client operated by the approval user, the registered content in the form editor 503 contains an error “the input check of the non-existing item ITEM_SYONINSYA” is performed. The server cannot perform the approval process, and the matter stays.

  Therefore, the management user operates the workflow client terminal, creates the business definition V2 using the item editor 501, and registers the item ITEM_SYONINSYA. Further, the form editor 503 is used to design the approver field on the approval form.

  The newly designed content is recorded in addition to the work design 311. An example of the additionally designed work design is shown in FIG. In FIG. 10, it can be seen that V2 records are additionally recorded in the “business version number” of the business definition 401, the form definition 403, and the item definition 404.

  Here, ITEM_SYONINSYA is registered in the last line of the item definition 404. It can also be seen that the form data of the form definition 403 has been changed (1001). FIG. 11 shows an example in which an “authorizer field” 1101 is arranged in the form editor 503. As a result, the approver inputs the name of the approver in the “approver field” when approving.

  Subsequently, the management user operates the workflow client, searches for a case via the case maintenance screen 1200 shown in FIG. 12, selects a line of the search result, and requests the workflow server to change the job. To do. The workflow server checks whether or not business replacement can be performed. If the workflow server determines that replacement is possible, the workflow server replaces the reference to the business definition V1 of the matter with the reference to the business definition V2 that is the currently active business definition. Do it. The case at this time is registered as shown in FIG. 13, the business version of the case data is corrected (1301), and ITEM_SYONINSYA is registered without item value in the case child data (1302).

  Note that since the workflow server checks whether business replacement can be performed, the administrative user who performs the replacement does not need to access the data portion of the matter. Therefore, it is possible to prevent risks such as data leakage and falsification by the administrator user. The replacement process and check performed by the workflow server will be described in detail with reference to FIGS.

"Step 4"
Since the “input check logic when the approval button is pressed” of the business definition V2 is used, it is possible to perform normal approval and the retention is eliminated.

  Specifically, when the approver displays the screen for approving the staying matter again, a newly designed approver column 1101 is displayed on the approval screen. When the approver inputs the approver name in this field and then presses the approval button, an approval request is made from the workflow line to the workflow server. Then, the input check logic operates on the workflow server, and authentication processing can be normally performed. The project proceeds to the next, and the final approver performs the approval work.

  As mentioned above, although an example was given and demonstrated in step 1-step 4, the method of "correcting a form and removing the check logic at the time of pressing an approval button" is also considered, for example.

  Further, in the present embodiment, the business design data in which the administrative user has created the business definition V2 is described as if it was re-created as shown in FIG. 10, but there is a difference (added item ITEM_SYONINSYA) It is also possible to register only the corrected form FORM_SYONIN) so that the data amount does not increase too much.

  Furthermore, the business version of the business replacement destination can be selected and replaced with a specific business version or a past version without selecting a business version that is currently valid.

  FIG. 14 is a flowchart showing the flow of the business version replacement process in the workflow server.

  This business version reassignment process is the process in the workflow server shown in “Step 3” in FIG. 7 when the administrative user operates the workflow client to instruct the workflow server to reassign the business. It describes the flow. Specifically, the processing is started when a “business reassignment” button 1201 shown in FIG. 12 is pressed.

  In step S601, a business version replacement process request is received from the management client 103, and the process is started.

  In step S602, in order to avoid a conflict between the case update and another user, the case information 321 (including the case data 405 and the case child data 406) to be replaced is acquired, and the acquired case is locked ( Restrict. In other words, the progress of the workflow is limited by locking the case.

  In step S603, a business design 311 (including a business definition 401, a path definition 402, a form definition 403, and an item definition 404) associated with the item to be replaced is acquired.

  Hereinafter, the business design 311 acquired here is a pre-replacement business design, and the item definition 404 is a pre-replacement item definition. As an example, each data registered with the business version “1” is acquired as the business design before replacement.

  In step S604, a newly associated business definition 311 (including a business definition 401, a path definition 402, a form definition 403, and an item definition 404) is acquired.

  Hereinafter, the business design 311 acquired here is the post-replacement business design, and the item definition 404 is the post-replacement item definition. As an example, as the post-replacement business design, each data registered with the business version “2” is acquired.

  Then, from step S605 to step S608, it repeats by the number of cases of the item definition before replacement and the item definition after replacement.

  In step S607, a consistency check is performed to determine whether replacement can be performed. Details of the consistency check will be described with reference to the flowchart of FIG.

  Steps S612 to S615 are processed continuously from step S607.

  In step S613, it is confirmed that the item definition existing in the pre-replacement item definition has not been deleted in the post-replacement item definition. If it has been deleted, the subsequent processing is interrupted as a replacement error, and the workflow server notifies the replacement error to the workflow client operated by the management user.

  An example is shown below. In the item information shown in FIG. 9, one item definition of the item definition job version “1” is taken out, and the item definition also exists in the job version “2” with reference to the job design 311 shown in FIG. To confirm. In this example, there is no error.

  First loop: “ITEM_SHINSEIBI” of the business version “1” exists even in the business version “2”. Loop second time: “ITEM_SHINSEIYA” of business version “1” exists also in business version “2”. The following is omitted.

  Here, although a replacement error is assumed, the workflow server re-creates the deleted item definition 404 in the post-replacement item definition without deleting the replacement error, or deletes the item definition from the item child data 406. Data matching the definition 404 may be deleted from the case information 321 to maintain the consistency of the case information, and the subsequent processing may be continued.

  In step S614, it is confirmed that the item definition before replacement is not changed in the attribute (type and length) in the item definition after replacement. If it has been changed, the subsequent processing is interrupted as a replacement error, and the workflow server notifies the replacement error to the workflow client operated by the management user.

  An example is shown below. In the case information shown in FIG. 9, one item definition of the item definition business version “1” is extracted, and the item type and length of the item definition are the same for the business version “2”. Confirm with reference to the business design 311 shown. In this example, there is no error.

  First loop: “Item type = date and time, length = none” of “ITEM_SHINSEIBI” of business version “1”, “item type = date and time, length of none” of “ITEM_SHINSEIBI” of business version “2” It can be seen that the same is true.

  Second loop: “ITEM_SHINSEIYA” of business version “1” has “item type = character, length = 20”, and “item type = character, length of business item“ 2 ”has“ item type = character, length = 20 ” It can be seen that the same is true. The following is omitted.

  Here, although a replacement error is assumed, the workflow server changes the attribute of the changed item definition 404 or changes the item value of the matter child data 406 to the attribute of the post-replacement item definition without generating a replacement error. May be changed so as to match, so that the consistency of the case information is maintained, and the subsequent processing may be continued.

  In step S615, the result of the consistency check is returned to the caller step S607, and step S608 is continued.

  By the way, in step S613, deletion of an item is prohibited. However, if item definition is not necessary, the item definition may not be arranged from the form data of the form definition 403. Further, in step S614, the item definition attribute change is prohibited. However, if the item definition attribute is to be changed, the item definition can be changed by leaving the old item definition and creating a new item definition. It is only necessary to change the attribute. By taking such alternative measures of item definition deletion and item definition attribute change, it is possible to perform a business design replacement process without missing data from the case information 321.

  Next, in step S609, the relationship of the project information 321 acquired in step S602 (including the project data 405 and the project child data 406 included in the project information 321) to the business design 311 is determined from the pre-replacement business design. Change to business design after replacement. More specifically, the business version number of the project data 405 is changed from “1” to “2”, the project child data 406 is extracted from the business design 321 and the item definition of V2 is extracted, and the newly defined item is displayed. to add. Specifically, the configuration is changed from FIG. 9 to FIG.

  In step S610, the information of the case information 321 changed in step S609 is stored in the case information storage unit 320, and the lock of the case information 321 executed in step S602 is released. By canceling the case information, the workflow of this case is resumed.

  At this time, as the post-processing of the case update, it is also possible to record the case last update date and the case last updater.

  In step S611, the business version replacement process is completed, the workflow server notifies the workflow client operated by the management user of the replacement completion, and the process ends.

  As described above, according to the present invention, in the workflow system, it is possible to change the design information of an ongoing case without re-applying the case.

  In addition, a plurality of versions of business design workflows including new and old can coexist, and new design information can be reflected even in an ongoing project. For example, if there is an error in the condition judgment for advancing the workflow and the matter stays, register a new version of the business design, correct the condition judgment, and replace the business design version. Retention can be eliminated, and the trouble of re-application can be suppressed.

  In addition, it is possible to check whether or not replacement is possible before replacement so that the data of the case is not lost by changing the work design of the case.

  In addition, since the management user who performs the replacement does not need to access the data portion of the matter, it is possible to prevent risks such as data leakage and falsification by the administrator user.

  In addition, instead of changing to the latest design information at once, you can select the case and reflect the design information, so one case works with the design information before correction, and another case, It can operate with design information after correction.

  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.

101 Workflow server 102 Workflow client 103 DB server 104 Circulation history

Claims (8)

In the information processing apparatus capable of changing the version of the business design that holds the data definition information of the data constituting the matter as an item definition, which is the basis of the matter in progress in the workflow procedure,
A matter acceptance means for accepting selection of an ongoing matter;
Storage means for storing multiple versions of the business design;
Change instruction accepting means for accepting an instruction to change the version of the business design that is the basis of the ongoing matter accepted by the matter accepting means to another version;
Changing the previous item defined in the pre-change operations design selection of which is accepted by the previous SL projects receiving means has not been removed in the item definitions of the changed operational design after the change, or the pre-change items defined above By confirming that the attribute has not been changed in the item definition after the change, it is possible to replace the business design before the change with the business design after the change without requiring reapplication of the matter. and confirmation means for performing a confirmation of that,
When the confirmation means confirms that the replacement is possible without requiring reapplication of the case, the change is made to the version of the business design that is the basis of the ongoing case accepted by the case acceptance means. An information processing apparatus comprising: changing means for changing to another version of the business design for which an instruction has been given. As a result of checking the consistency as to whether or not the item definition before the change and the item definition after the change can be replaced by the checking means, an error is notified when the consistency cannot be confirmed. The information processing apparatus according to claim 1 , further comprising an error notification unit. In the case to be notified of the error by the error notification unit, it has the consistency processing means for processing for maintaining the integrity,
The error notification unit, when the process for maintaining the integrity by the integrity processing unit is made, the information processing apparatus according to claim 2, characterized in that it does not signal the error. When the change instruction is accepted by the change instruction accepting means, it has a matter restricting means for restricting the progress of the matter accepted by the matter accepting means,
The information processing apparatus according to any one of claims 1 to 3 , wherein the case restricting unit releases the restriction on the progress of the case after the change work of the changing unit is completed . Information that can be communicated between the client and the information processing device that can change the version of the business design that holds the data definition information of the data that constitutes the matter as an item definition, which is the basis of the matter in progress in the workflow procedure In the processing system,
The information processing apparatus is
A matter acceptance means for accepting selection of an ongoing matter;
Storage means for storing multiple versions of the business design;
Change instruction accepting means for accepting an instruction to change the version of the business design that is the basis of the ongoing matter accepted by the matter accepting means to another version;
Changing the previous item defined in the pre-change operations design selection of which is accepted by the previous SL projects receiving means has not been removed in the item definitions of the changed operational design after the change, or the pre-change items defined above By confirming that the attribute has not been changed in the item definition after the change, it is possible to replace the business design before the change with the business design after the change without requiring reapplication of the matter. and confirmation means for performing a confirmation of that,
When the confirmation means confirms that the replacement is possible without requiring reapplication of the case, the change is made to the version of the business design that is the basis of the ongoing case accepted by the case acceptance means. An information processing system comprising: changing means for changing to a business design of another version for which an instruction has been given. Storage means for storing a plurality of versions of the business design capable of changing the version of the business design that holds the data definition information of the data constituting the case as an item definition, which is the basis of the case in progress in the workflow procedure In an information processing method in an information processing apparatus comprising:
A matter acceptance step for accepting selection of an ongoing matter;
A change instruction accepting step for accepting an instruction to change the version of the business design that is the basis of the ongoing matter accepted by the matter accepting step;
Changing the previous item defined in the pre-change operations design selection of which is accepted by the previous SL projects receiving step has not been removed in the item definitions of the changed operational design after the change, or the pre-change items defined above By confirming that the attribute has not been changed in the item definition after the change, it is possible to replace the business design before the change with the business design after the change without requiring reapplication of the matter. A confirmation step to confirm that
If the confirmation step confirms that the replacement is possible without requiring reapplication of the case, the change is made to the version of the business design that is the basis of the ongoing case accepted by the matter acceptance step. And a change step for changing to another version of the business design for which an instruction has been given. Storage means for storing a plurality of versions of the business design capable of changing the version of the business design that holds the data definition information of the data constituting the case as an item definition, which is the basis of the case in progress in the workflow procedure a program executable in an information processing apparatus including a
A matter acceptance means for accepting selection of ongoing matters,
Change instruction accepting means for accepting an instruction to change the version of the business design that is the basis of the ongoing matter accepted by the matter accepting means, to another version;
Changing the previous item defined in the pre-change operations design selection of which is accepted by the previous SL projects receiving means has not been removed in the item definitions of the changed operational design after the change, or the pre-change items defined above By confirming that the attribute has not been changed in the item definition after the change, it is possible to replace the business design before the change with the business design after the change without requiring reapplication of the matter. confirmation means for performing a confirmation of that,
When the confirmation means confirms that the replacement is possible without requiring reapplication of the case, the change is made to the version of the business design that is the basis of the ongoing case accepted by the case acceptance means. A program for causing the information processing apparatus to function as changing means for changing to another version of the business design for which an instruction has been given. A recording medium storing the program according to claim 7 in a computer-readable manner.

Images