A processing method and device for switching between different workflow engines

By pre-stored business engine configuration information and establishing work plans in the configuration center, free switching between different workflow engines is achieved, the problem of difficulty and high cost of switching workflow engines is solved, the difficulty and cost of system maintenance is reduced, and a one-stop service is achieved. Process processing.

CN115098188BActive Publication Date: 2024-11-22YANTAI HAIYI SOFTWARE
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202210725506.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-06-23
Publication Date
2024-11-22
Estimated Expiration
2042-06-23

AI Technical Summary

Technical Problem

In the prior art, the workflow engine switching is difficult and costly, which leads to difficult system reconstruction and maintenance. The design ideas and data storage logic of different workflow engines lead to adaptation problems.

Method used

Prestore multiple business engine configuration information in the configuration center, including workflow API, input parameters, output parameters and workflow link parameter configuration modules, establish a work plan and assign a unique solution number to the workflow engine instance number, and use the configuration center to configure the workflow engine to create a work plan and assign a unique solution number corresponding to the workflow engine instance number. Configure the workflow API and parameters to enable switching of the workflow engine.

Benefits of technology

It realizes free switching between different workflow engines, reduces the problems caused by system reconstruction, reduces maintenance difficulty and cost, reduces the coupling between the business system and the workflow engine, and achieves one-stop process processing.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115098188B_ABST
    Figure CN115098188B_ABST
Patent Text Reader

Abstract

The present invention relates to a processing method and device for switching between different workflow engines. The device includes a configuration center, one or more business systems, a workflow engine, a work plan establishment module, and a work plan operation module, wherein: the configuration center includes a workflow API configuration module, an input parameter configuration module, an output parameter configuration module, a workflow link parameter configuration module, and a plurality of pre-stored business engine configuration information, each business engine configuration information is composed of a business system and a workflow engine corresponding to the business system; the business system is used to connect to a work order API through an interface call; the work plan establishment module is used to establish a work plan, and the calling sequence of the corresponding workflow engine is pre-configured in the work plan; the work plan operation module is used to start the work plan.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of computer software technology, and more specifically, to a processing method and device for switching between different workflow engines. Background Art

[0002] Workflow refers to the automation of part or all of a business process in a computer application environment. It is an abstract and general description of the business rules between the workflow and its various operation steps. Workflow is a common software application technology in various information management systems. One of its main uses is to use computer software programs to automatically transfer documents, information or tasks between multiple participants according to certain predetermined rules in order to achieve a certain business goal.

[0003] It is often very difficult to switch workflow engines for management information systems of the same business type, because different workflow engines have different design concepts, and the data storage logic may also affect the business design, database table design, etc. in the business system. If the workflow engine is switched, it may lead to the reconstruction of the entire system, wasting a lot of manpower, financial resources, and material resources, and it is likely to bring all kinds of unimaginable problems.

[0004] In view of the current problems of great difficulty and high cost in switching workflow engines, it is necessary to develop a universal technical solution to solve the above technical problems. Summary of the invention

[0005] In order to solve the above problem, the present invention provides a processing method and device for switching between different workflow engines.

[0006] A first embodiment of the present invention provides a processing method for switching between different workflow engines, which includes:

[0007] Pre-store multiple business engine configuration information in the configuration center, each business engine configuration information is composed of a business system and a workflow engine corresponding to the business system, wherein the workflow engine includes the name and type of the workflow engine, and multiple pre-configured workflow templates for the business system;

[0008] The configuration center is provided with a workflow API configuration module, an input parameter configuration module, an output parameter configuration module, and a workflow link parameter configuration module, wherein: the workflow API configuration module is used to configure at least the following items: the name of the workflow engine, the type of the process engine, the start process API, various work order APIs, and the input parameters and output parameters required by the API; the input parameter configuration module is used to convert the currently used input parameters into the input parameters of the workflow engine and / or API to be called according to preset rules; the output parameter configuration module is used to convert the output parameters of the currently called workflow engine and / or API into the result set to be used in the current interface according to preset rules; the workflow link parameter configuration module is used to configure the parameters to be transmitted to the business system;

[0009] Establishing a work plan including one or more business systems and their workflows and assigning a unique plan number, wherein in the process of establishing the work plan, based on the workflows of the one or more business systems and the pre-stored business engine configuration information, the calling sequence of the corresponding workflow engines is pre-configured in the work plan, and a unique instance number is assigned to each workflow engine, thereby establishing a corresponding relationship between the plan number and the instance number of one or more workflow engines;

[0010] When starting a work plan, the corresponding work plan is found by entering the plan number and the first-ranked workflow engine is read based on the calling order and its pre-configured workflow is executed; when switching to the next workflow engine based on the calling order of the pre-configured workflow engine, the workflow API configuration, input parameter configuration, output parameter configuration, and workflow link parameter configuration are configured in the configuration center respectively, so that the next workflow engine can work normally.

[0011] Among them, the work order API includes but is not limited to: process query API, handling query API, transfer API, and reassignment API; the work plan also includes: plan name, plan type, plan version, process template number, process template sequence, workflow engine instance number to which the process template belongs, and work order number generation rules.

[0012] Among them, the step of reading the first-ranked workflow engine based on the calling order and executing its pre-configured workflow includes: reading the name and type of the workflow engine, finding and starting the start process API of the workflow engine through the workflow engine name and process engine type in the workflow API configuration, and executing the corresponding workflow according to the process template number and process template order pre-configured in the workflow engine.

[0013] Among them, the step of switching to the next workflow engine based on the calling sequence of the pre-configured workflow engines includes: returning information indicating the end of the current workflow engine after the last process template in the current workflow engine is executed, calling the next workflow engine through the calling sequence of the pre-configured workflow engines, and realizing the switching to the next workflow engine.

[0014] Among them, the work order number generation rules include: defining a prefix, suffix, minimum value, maximum value, step size, and current value, wherein the values ​​of the prefix and suffix are set as required, the minimum value is the starting value of the work order number; the maximum value is the ending value of the work order number; the current value is the value of the work order number generated this time; and the step size is the growth value.

[0015] The second embodiment of the present invention provides a processing device for switching between different workflow engines, which includes: a configuration center, one or more business systems, a workflow engine, a work plan establishment module, and a work plan operation module, wherein:

[0016] The configuration center includes a workflow API configuration module, an input parameter configuration module, an output parameter configuration module, a workflow link parameter configuration module, and a plurality of pre-stored business engine configuration information, each business engine configuration information is composed of a business system and a workflow engine corresponding to the business system, the workflow API configuration module is used to configure at least the following items: workflow engine name, process engine type, start process API, various work order APIs, and input parameters and output parameters required by the API; the input parameter configuration module is used to convert the currently used input parameters into input parameters of the workflow engine and / or API to be called according to preset rules; the output parameter configuration module is used to convert the output parameters of the currently called workflow engine and / or API into the result set to be used by the current interface according to preset rules; the workflow link parameter configuration module is used to configure the parameters to be transmitted to the business system;

[0017] The business system is used to connect to the work order API through an interface call;

[0018] The workflow engine includes the name and type of the workflow engine, and a plurality of pre-configured workflow templates for the business system, and can call a start process API;

[0019] The work plan establishment module is used to establish a work plan including one or more business systems and their workflows and assign a unique plan number, wherein in the process of establishing the work plan, based on the workflows of the one or more business systems and the pre-stored business engine configuration information, the calling sequence of the corresponding workflow engines is pre-configured in the work plan, and a unique instance number is assigned to each workflow engine, thereby establishing a corresponding relationship between the plan number and the instance number of one or more workflow engines;

[0020] The work plan running module is used to start the work plan, find the corresponding work plan by inputting the plan number, read the first-ranked workflow engine based on the calling order, and execute its pre-configured workflow; when switching to the next workflow engine based on the calling order of the pre-configured workflow engine, the workflow API configuration, input parameter configuration, output parameter configuration, and workflow link parameter configuration are configured in the configuration center respectively, so that the next workflow engine can work normally.

[0021] The work order API includes but is not limited to: process query API, handling query API, transfer API, and reassignment API.

[0022] The work plan also includes: plan name, plan type, plan version, process template number, process template sequence, workflow engine instance number to which the process template belongs, and work order number generation rules.

[0023] Among them, the work order number generation rules include: defining a prefix, suffix, minimum value, maximum value, step size, and current value, wherein the values ​​of the prefix and suffix are set as required, the minimum value is the starting value of the work order number; the maximum value is the ending value of the work order number; the current value is the value of the work order number generated this time; and the step size is the growth value.

[0024] Compared with the prior art, the beneficial effect of the present invention is that it solves the adaptation problem of switching between multiple different workflow engines in the prior art. When switching between different workflow engines, it is only necessary to configure the required various APIs, API parameters, and workflow link parameters in the configuration center, without intruding into the code or making any modifications to the business code, and the process scheduling can be carried out according to the new plan, reducing various problems caused by system reconstruction, achieving one-stop process processing, reducing the maintenance difficulty and cost between various systems, realizing the free switching of different workflow engines, and reducing the coupling between the business system and the workflow engine.

[0025] Since the present invention realizes the free switching of different workflow engines, each business system using workflow needs to have various common modules such as job to-do, personal to-do, work order details, work order summary, etc. The method and device provided by the present invention can reduce the work of separate development for each business system and reduce the cost consumption caused by the separate development of each business system. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 It is a flow chart of a processing method for switching between different workflow engines provided by the present invention;

[0027] Figure 2 It is a structural schematic diagram of a processing device for switching between different workflow engines provided by the present invention. DETAILED DESCRIPTION

[0028] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0029] like Figure 1 As shown, the first embodiment of the present invention provides a processing method for switching between different workflow engines, which includes:

[0030] S1: Pre-store multiple business engine configuration information, each business engine configuration information is composed of a business system and a workflow engine corresponding to the business system.

[0031] Usually, since each workflow engine has different internal implementation logic, library tables, etc., one business system corresponds to only one workflow engine. In this way, a business system and the workflow engine corresponding to the business system can constitute a business engine configuration. The term "tenant" can be used to vividly represent the pairing relationship between the business system and the workflow engine.

[0032] The workflow engine includes the name and type of the workflow engine, as well as multiple workflow templates, workflow template numbers and workflow template sequences pre-configured for the business system, that is, the sequence in which the multiple workflow templates are executed.

[0033] In the present invention, the configuration information of the multiple business engines is pre-stored in a configuration center module. The configuration center module is a software program module for executing the processing method for switching between different workflow engines of the present invention. The configuration center module is provided with a workflow API configuration module, an input parameter configuration module, an output parameter configuration module, and a workflow link parameter configuration module.

[0034] Among them: the workflow API configuration module is used to configure at least the following items: the workflow engine name, the process engine type, the startup process API, various work order APIs, and the input parameters and output parameters required by the API; the input parameter configuration module is used to convert the currently used input parameters into the input parameters of the workflow engine and / or API that needs to be called according to preset rules; the output parameter configuration module is used to convert the output parameters of the currently called workflow engine and / or API into the result set that needs to be used in the current interface according to preset rules; the workflow link parameter configuration module is used to configure the parameters that need to be passed to the business system, and the workflow link parameters are passed to the business page via a URL for use by the functions on the business page.

[0035] The work order API includes but is not limited to: process query API, handling query API, transfer API, and reassignment API.

[0036] For example, the input parameters required by the process query API are: process instance number, remarks, incoming organization, etc., and the returned output parameters are: the result set of the process instance.

[0037] The process instance number is generated by each process template. Each time a process template generates a new application instance, a process instance number will be generated. For example, a leave process template will generate a process instance number when it is started once (for example, someone initiates a leave process), and a new process instance number will be generated when it is started again (for example, another person initiates a leave process).

[0038] The work plan also includes: plan name, plan type, plan version, process template number, workflow engine instance number to which the process template belongs, and work order number generation rules.

[0039] Since the workflow engine includes a plurality of workflow templates, process template numbers and workflow template sequences pre-configured for the business system, each workflow engine internally manages its own process template number and the execution sequence of the workflow template. In order to clarify which process template belongs to which workflow engine, when assigning a process template number to a workflow template, a mapping relationship can be established between the workflow engine instance number of the workflow engine to which the workflow template belongs and the process template number, so that the workflow engine to which the workflow template belongs can be quickly found through the process template number and the workflow engine instance number.

[0040] The work order number generation rules are as follows: prefix, suffix, minimum value, maximum value, step length, and current value can be defined. The values ​​of the prefix and suffix can be set as required, for example, they can be fixed strings, or information such as the current date. The minimum value is the starting value of the work order number; the maximum value is the ending value of the work order number; the current value is the value of the work order number generated this time; the step length can be an increasing value, and the next current value = current value + step length, that is, the next work order number is the current work order number + step length.

[0041] The work order number is the instance number of the work plan. For example, if the work plan includes two aspects of work, leave and finance, and someone initiates the leave process, the work order number generated at this time is 1. Another person initiates the leave process, and the work order number generated is 2. The work order number is generated by the work plan, and the work order number is used as the instance number of the work plan. When the work order number is generated, a mapping relationship is established between the work order number and the plan number of the work plan to which it belongs, so that an association is established between the work order number, the plan number and the workflow engine instance number.

[0042] The definition of the work order here includes but is not limited to the drawing of flow charts, the definition of links, the definition of variables, etc.

[0043] For all the work order API instances mentioned above, such as the process query API, the input parameters of the work order API involved in different workflow engines are inconsistent. For example, the input parameter of the process query work order API in the Activity workflow is ReturnVOSearchWorkorder(SearchVOvo); the input parameter of the process query work order API in the HYFlow workflow is List <string>LoadJOB(String orderNo). Therefore, when calling different work order APIs of different workflow engines, it is necessary to convert input parameters and output parameters, that is, convert the data collected by the query interface on the software program that executes this method into the input parameters required by different workflow engines, and convert the output parameters of the workflow engine into the result set that needs to be displayed on the program interface. For example, the information collected by the program interface is TODOVO (id, creatorId, departmentid, remark, todoid). For the query work order API of the Activity workflow engine, it is necessary to convert each field in the TODOVO into different fields of SerarchVO. For the query work order API of the HYFlow workflow engine, it is necessary to convert a certain field in TODOVO into orderNo. The conversion of these input parameters and output parameters illustrated by examples can be completed through the workflow API configuration module, input parameter configuration module, and output parameter configuration module in the above-mentioned configuration center module, wherein the input parameter configuration module and the output parameter configuration module can be listed separately or integrated in the workflow API configuration module.

[0044] The following content will talk about how the implementation of the work plan involves the execution of the business system, that is, entering each link of the process, that is, completing the work plan through the various functional pages of the business system. Since different business systems are developed by different workflow engines, there will be differences in the parameters passed to the functional pages of different business systems. For example, the parameters that need to be passed to the marketing business system include: the instance number (InstanceID) of the plan, whether it can be edited (Disable), etc., but the parameters that need to be passed to the financial business system include: the instance number (SN) of the plan, the processing personnel (UserID), etc. Here, the instance number of the plan refers to the work order number. For different business systems, the corresponding work order number is expressed differently. In other words, the expression of the instance number of the plan passed to the marketing business system is different from the expression of the instance number of the plan passed to the financial business system.

[0045] Since different business systems are developed by different workflow engines, there are fixed parameter mapping rules between the business system and the workflow engine. When the executed process needs to switch to a different workflow engine, the parameter mapping rules are replaced by another set of rules. The purpose of setting the workflow link parameter configuration module is to configure the parameters that need to be passed to the business system, that is, to configure a rule for configuring the passed parameters so as to map them into the parameters required in different business systems. The parameters configured through the workflow link parameter configuration module can pass all the configuration parameters to the business page through the URL, such as instanceid=500000123123, editable flag, task number, etc.

[0046] The present invention relates to the field of computer software technology. Therefore, a processing method for switching between different workflow engines of the present invention is implemented based on a software program, and in particular involves establishing a work plan through a software program, executing different business systems based on workflow technology, and the execution of various processes is realized through various business interfaces. The various modules and functions mentioned above can present the operation interface in a window manner, and the various parameter configurations involved in the switching of different workflow engines can be completed through the operation interface window, including the parameter configuration of the work order API, the input parameter configuration, the output parameter configuration, the workflow link parameter configuration, etc. The configuration of the parameters can be completed manually by the user. When some functions require repeated manual operations, the data to be entered can be pre-recorded in an Excel file, and automatic form filling can be realized through Excel import.

[0047] S2: Establish a work plan including one or more business systems and their workflows and assign a unique plan number, wherein in the process of establishing the work plan, based on the workflows of the one or more business systems contained therein and the pre-stored business engine configuration information, the calling sequence of the workflow engines corresponding to the workflows of the business systems is pre-configured in the work plan, and a unique instance number is assigned to each workflow engine, thereby establishing a correspondence between the plan number and the instance number of one or more workflow engines.

[0048] The workflow of the work plan can be implemented based on workflow technology. Since the business engine configuration information records the "tenant" information of the paired business system and workflow engine, it is possible to pre-configure the calling sequence of the workflow engine corresponding to the workflow of the business system in the work plan. The plan number of the work plan can be set at will, as long as the plan number of each work plan is unique and non-repetitive; of course, it is preferred to set the plan number of the work plan according to certain rules. The workflow engine instance number that forms a corresponding relationship with the plan number can be established by a pre-set numbering rule.

[0049] S3: Find the corresponding work plan by inputting the plan number and read the first-ranked workflow engine based on the calling order and execute its pre-configured workflow.

[0050] Among them, the step of reading the first-ranked workflow engine based on the calling order and executing its pre-configured workflow specifically includes: reading the name and type of the workflow engine, finding and starting the start process API of the workflow engine through the workflow engine name and process engine type in the workflow API configuration, and executing the corresponding workflow according to the process template number and process template order pre-configured in the workflow engine.

[0051] The start process API of the workflow engine can be configured through the workflow API configuration module, and the start process API of the workflow engine of the first workflow engine can be called according to the workflow of the work plan. The corresponding work tasks are executed through the start process API according to the workflow pre-configured in the workflow engine, such as the process template number and the process template sequence. During this process, the necessary input parameters and output parameters can be converted through the input parameter configuration module and the output parameter configuration module. The returned parameters include the instance number generated by the workflow engine, and additional attributes such as the workflow engine type can also be recorded. Finally, the plan number of the work plan is returned to the business system, thereby realizing the original return of parameters.

[0052] S4: When switching to the next workflow engine based on the calling sequence of the pre-configured workflow engine, the workflow API configuration, input parameter configuration, output parameter configuration, and workflow link parameter configuration are configured in the configuration center respectively so that the next workflow engine can work normally.

[0053] The step of switching to the next workflow engine based on the calling sequence of the pre-configured workflow engine includes: returning information indicating the end of the current workflow engine after the last process template in the current workflow engine is executed, calling the next workflow engine through the calling sequence of the pre-configured workflow engine, and switching to the next workflow engine. Then, repeat the implementation process of step 3, such as starting the process API of the new workflow engine, and configuring the necessary input parameters and output parameters through the workflow API configuration module.

[0054] The creation and initiation of a work plan is briefly described below. First, a work plan is established based on workflow software application technology and a unique plan number is assigned to it. The work plan may include one or more business systems, such as a marketing business system, a financial business system, and an engineering business system. A work plan may include only one financial business system, or may include three business systems, namely, a marketing business system, a financial business system, and an engineering business system. For example, a project installation contract is signed in the marketing business system, the financial business system monitors the capital flow of the project installation contract, and the engineering business system monitors the progress of the project. Since workflow software technology is used in the process of establishing a work plan, the work plan includes the workflow of the one or more business systems, and based on the pre-stored business engine configuration information, the calling sequence of the workflow engine corresponding to the workflow sequence of the business system can be pre-configured in the work plan, and each workflow engine is assigned a unique instance number, thereby establishing a corresponding relationship between the plan number of the work plan and the instance number of one or more workflow engines.

[0055] When starting a work plan, the corresponding work plan is found by entering the plan number and the first-ranked workflow engine is read based on the calling order and its pre-configured workflow is executed; when switching to the next workflow engine based on the calling order of the pre-configured workflow engine, the workflow API configuration, input parameter configuration, output parameter configuration, and workflow link parameter configuration are configured in the configuration center respectively, so that the next workflow engine can work normally.

[0056] In addition, in order to better implement the scheduling of workflows, the present invention can also provide a unified workflow scheduling interface, and operations such as workflow transfer, rollback, and reassignment can be processed in this interface.

[0057] Furthermore, each link in multiple business systems can be displayed in the form of a hyperlink list, and the hyperlink contains the page corresponding to the target link, which makes it easy to implement RPA recording. When some functions require repeated manual operations, they can be recorded on the screen and the data to be entered can be imported through Excel to achieve automatic form filling.

[0058] After the work plan is created and some work plans have been started, you can query the work order. You can use common query conditions as input parameters, such as plan number, work order number, work order status, pending department, pending person, etc., to call the query process instance API of the configuration center to obtain the query results. The output parameters of this API may include the process instance number, description, and the above query conditions; then this result set needs to be converted into the final solution query result set through the mapping relationship between the process instance number and the plan number. The query process instance API will call the "query API" of all configured workflow engines to achieve global query. When performing a global query, you do not need to know which specific workflow engine to select, because you can find the workflow engine corresponding to the work plan through the configuration by knowing the work plan corresponding to the work order.

[0059] The above-mentioned processing method for switching different workflow engines provided by the present invention solves the adaptation problem of switching between multiple different workflow engines existing in the prior art. When switching different workflow engines, it is only necessary to configure the required various APIs, API parameters, and workflow link parameters in the configuration center, without intruding into the code or making any modifications to the business code, and the process scheduling can be carried out according to the new plan, reducing various problems caused by system reconstruction, achieving one-stop process processing, reducing the maintenance difficulty and cost between various systems, realizing the free switching of different workflow engines, and reducing the coupling between the business system and the workflow engine.

[0060] like Figure 2 As shown, the second embodiment of the present invention provides a processing device for switching between different workflow engines, which includes: a configuration center, one or more business systems, a workflow engine, a work plan establishment module, and a work plan operation module, wherein:

[0061] The configuration center includes a workflow API configuration module, an input parameter configuration module, an output parameter configuration module, a workflow link parameter configuration module, and a plurality of pre-stored business engine configuration information, each business engine configuration information is composed of a business system and a workflow engine corresponding to the business system, the workflow API configuration module is used to configure at least the following items: workflow engine name, process engine type, start process API, various work order APIs, and input parameters and output parameters required by the API; the input parameter configuration module is used to convert the currently used input parameters into input parameters of the workflow engine and / or API to be called according to preset rules; the output parameter configuration module is used to convert the output parameters of the currently called workflow engine and / or API into the result set to be used by the current interface according to preset rules; the workflow link parameter configuration module is used to configure the parameters to be transmitted to the business system;

[0062] The business system is used to connect to the work order API through an interface call;

[0063] The workflow engine includes the name and type of the workflow engine, and a plurality of pre-configured workflow templates for the business system, and can call a start process API;

[0064] The work plan establishment module is used to establish a work plan including one or more business systems and their workflows and assign a unique plan number, wherein in the process of establishing the work plan, based on the workflows of the one or more business systems and the pre-stored business engine configuration information, the calling sequence of the corresponding workflow engines is pre-configured in the work plan, and a unique instance number is assigned to each workflow engine, thereby establishing a corresponding relationship between the plan number and the instance number of one or more workflow engines;

[0065] The work plan running module is used to start the work plan, find the corresponding work plan by inputting the plan number, read the first-ranked workflow engine based on the calling order, and execute its pre-configured workflow; when switching to the next workflow engine based on the calling order of the pre-configured workflow engine, the workflow API configuration, input parameter configuration, output parameter configuration, and workflow link parameter configuration are configured in the configuration center respectively, so that the next workflow engine can work normally.

[0066] The work order API includes but is not limited to: process query API, handling query API, transfer API, and reassignment API.

[0067] The work plan also includes: plan name, plan type, plan version, process template number, process template sequence, workflow engine instance number to which the process template belongs, and work order number generation rules.

[0068] Among them, the work order number generation rules include: defining a prefix, suffix, minimum value, maximum value, step size, and current value, wherein the values ​​of the prefix and suffix are set as required, the minimum value is the starting value of the work order number; the maximum value is the ending value of the work order number; the current value is the value of the work order number generated this time; the step size is the growth value, and the next current value = current value + step size.

[0069] By using the processing device for switching different workflow engines, the processing method for switching different workflow engines described in the first embodiment and the preferred embodiment can be executed, such as establishing a work plan including one or more business systems and their workflows and assigning a unique plan number, wherein in the process of establishing the work plan, based on the workflows of the one or more business systems contained therein and the pre-stored business engine configuration information, the calling order of the corresponding workflow engines is pre-configured in the work plan, and a unique instance number is assigned to each workflow engine, thereby establishing a correspondence between the plan number and the instance number of one or more workflow engines; when starting the work plan, the corresponding work plan is found by inputting the plan number and the first-ranked workflow engine is read based on the calling order and its pre-configured workflow is executed; when switching to the next workflow engine based on the calling order of the pre-configured workflow engine, the workflow API configuration, input parameter configuration, output parameter configuration, and workflow link parameter configuration are respectively configured in the configuration center to enable the next workflow engine to work normally.

[0070] Among them, the process of reading the first-ranked workflow engine based on the calling order and executing its pre-configured workflow includes: reading the name and type of the workflow engine, finding and starting the start process API of the workflow engine through the workflow engine name and process engine type in the workflow API configuration, and executing the corresponding workflow according to the process template number and process template order pre-configured in the workflow engine.

[0071] Among them, the process of switching to the next workflow engine based on the calling sequence of the pre-configured workflow engine includes: after the last process template in the current workflow engine is executed, returning information indicating the end of the current workflow engine, calling the next workflow engine through the calling sequence of the pre-configured workflow engine, and realizing the switching to the next workflow engine.

[0072] Therefore, those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the processing device for switching between different workflow engines described in the above-mentioned second embodiment can refer to the corresponding implementation process in the above-mentioned first embodiment. The examples and related descriptions listed in the above-mentioned first embodiment and the corresponding preferred embodiments are also applicable to explaining the working process of the processing device described in the second embodiment, and will not be repeated here.

[0073] The use of the processing device for switching between different workflow engines provided by the present invention solves the adaptation problem of switching between multiple different workflow engines in the prior art. When switching between different workflow engines, it is only necessary to configure the required various APIs, API parameters, and workflow link parameters in the configuration center, without intruding into the code or making any modifications to the business code, and the process scheduling can be carried out according to the new plan, reducing various problems caused by system reconstruction, achieving one-stop process processing, reducing the maintenance difficulty and cost between various systems, realizing the free switching of different workflow engines, and reducing the coupling between the business system and the workflow engine.

[0074] The above content is a further detailed description of the present invention in combination with specific implementation methods. It cannot be determined that the specific implementation of the present invention is limited to these descriptions. For ordinary technicians in the technical field to which the present invention belongs, some simple deductions or substitutions can be made without departing from the concept of the present invention, which should be regarded as belonging to the scope of protection determined by the claims submitted for the present invention.< / string>

Claims

1. A processing method for switching between different workflow engines, characterized in that: include: Pre-store multiple business engine configuration information in the configuration center, each business engine configuration information is composed of a business system and a workflow engine corresponding to the business system, wherein the workflow engine includes the name and type of the workflow engine, and multiple pre-configured workflow templates for the business system; The configuration center is provided with a workflow API configuration module, an input parameter configuration module, an output parameter configuration module, and a workflow link parameter configuration module, wherein: the workflow API configuration module is used to configure at least the following items: the name of the workflow engine, the type of the process engine, the start process API, various work order APIs, and the input parameters and output parameters required by the API; the input parameter configuration module is used to convert the currently used input parameters into the input parameters of the workflow engine and / or API to be called according to preset rules; the output parameter configuration module is used to convert the output parameters of the currently called workflow engine and / or API into the result set to be used in the current interface according to preset rules; the workflow link parameter configuration module is used to configure the parameters to be transmitted to the business system; Establishing a work plan including one or more business systems and their workflows and assigning a unique plan number, wherein in the process of establishing the work plan, based on the workflows of the one or more business systems and the pre-stored business engine configuration information, the calling sequence of the corresponding workflow engines is pre-configured in the work plan, and a unique instance number is assigned to each workflow engine, thereby establishing a corresponding relationship between the plan number and the instance number of one or more workflow engines; When starting a work plan, the corresponding work plan is found by inputting the plan number and the first-ranked workflow engine is read based on the calling order and its pre-configured workflow is executed; when switching to the next workflow engine based on the calling order of the pre-configured workflow engine, the workflow API configuration, input parameter configuration, output parameter configuration, and workflow link parameter configuration are configured in the configuration center respectively, so that the next workflow engine can work normally; The step of reading the first-ranked workflow engine based on the calling order and executing its pre-configured workflow includes: reading the name and type of the workflow engine, finding the start process API of the workflow engine through the workflow engine name and process engine type in the workflow API configuration and starting it, and executing the corresponding workflow according to the process template number and process template sequence pre-configured in the workflow engine; The step of switching to the next workflow engine based on the calling sequence of the pre-configured workflow engines includes: returning information indicating the end of the current workflow engine after the last process template in the current workflow engine is executed, calling the next workflow engine through the calling sequence of the pre-configured workflow engines, and realizing the switching to the next workflow engine.

2. The processing method for switching between different workflow engines according to claim 1, characterized in that: The work order API includes: process query API, handling query API, transfer API, and reassignment API; the work plan also includes: plan name, plan type, plan version, process template number, process template sequence, workflow engine instance number to which the process template belongs, and work order number generation rules.

3. The processing method for switching between different workflow engines according to claim 2, characterized in that: The work order number generation rules include: defining a prefix, a suffix, a minimum value, a maximum value, a step size, and a current value, wherein the values ​​of the prefix and the suffix are set as required, the minimum value is the starting value of the work order number; the maximum value is the ending value of the work order number; the current value is the value of the work order number generated this time; and the step size is the growth value.

4. A processing device for switching between different workflow engines using the processing method according to any one of claims 1 to 3, characterized in that: include: Configuration center, one or more business systems, workflow engine, work plan creation module, work plan operation module, including: The configuration center includes a workflow API configuration module, an input parameter configuration module, an output parameter configuration module, a workflow link parameter configuration module, and a plurality of pre-stored business engine configuration information, each business engine configuration information is composed of a business system and a workflow engine corresponding to the business system, the workflow API configuration module is used to configure at least the following items: workflow engine name, process engine type, start process API, various work order APIs, and input parameters and output parameters required by the API; the input parameter configuration module is used to convert the currently used input parameters into input parameters of the workflow engine and / or API to be called according to preset rules; the output parameter configuration module is used to convert the output parameters of the currently called workflow engine and / or API into the result set to be used by the current interface according to preset rules; the workflow link parameter configuration module is used to configure the parameters to be transmitted to the business system; The business system is used to connect to the work order API through an interface call; The workflow engine includes the name and type of the workflow engine, and a plurality of pre-configured workflow templates for the business system, and can call a start process API; The work plan establishment module is used to establish a work plan including one or more business systems and their workflows and assign a unique plan number, wherein in the process of establishing the work plan, based on the workflows of the one or more business systems and the pre-stored business engine configuration information, the calling sequence of the corresponding workflow engines is pre-configured in the work plan, and a unique instance number is assigned to each workflow engine, thereby establishing a corresponding relationship between the plan number and the instance number of one or more workflow engines; The work plan running module is used to start the work plan, find the corresponding work plan by inputting the plan number, read the first-ranked workflow engine based on the calling order, and execute its pre-configured workflow; when switching to the next workflow engine based on the calling order of the pre-configured workflow engine, the workflow API configuration, input parameter configuration, output parameter configuration, and workflow link parameter configuration are configured in the configuration center respectively, so that the next workflow engine can work normally.

5. The processing device for switching between different workflow engines according to claim 4, characterized in that: The work order API includes: process query API, handling query API, transfer API, and reassignment API.

6. The processing device for switching between different workflow engines according to claim 4, characterized in that: The work plan also includes: plan name, plan type, plan version, process template number, process template sequence, workflow engine instance number to which the process template belongs, and work order number generation rules.

7. The processing device for switching between different workflow engines according to claim 6, characterized in that: The work order number generation rules include: defining a prefix, a suffix, a minimum value, a maximum value, a step size, and a current value, wherein the values ​​of the prefix and the suffix are set as required, the minimum value is the starting value of the work order number; the maximum value is the ending value of the work order number; the current value is the value of the work order number generated this time; and the step size is the growth value.