WO2021139778A1

WO2021139778A1 - System scheduling workflow generation method, system, apparatus, and computer readable storage medium

Info

Publication number: WO2021139778A1
Application number: PCT/CN2021/070904
Authority: WO
Inventors: 刘振涛; 方思行
Original assignee: 深圳壹账通智能科技有限公司
Priority date: 2020-01-10
Filing date: 2021-01-08
Publication date: 2021-07-15
Also published as: CN111208992A

Abstract

A system scheduling workflow generation method, a system, an apparatus, and a computer readable storage medium. The method comprises: providing a configuration interface to a user for configuring various service modules required to be scheduled to carry out a financial service, parameters of the various service modules, and a connection relationship between the various service modules (S100); after the user has completed a configuration operation, generating, according to the configuration operation, a configuration file used to carry out the financial service, the configuration file comprising the various service modules required to be scheduled for carrying out the financial service, parameter configuration information of the various service modules, and the connection relationship between the various service modules (S102); and converting the configuration file into an XML file executable by a workflow engine (S104). The method saves development time required for achieving a service objective, reduces costs, and improves flexibility.

Description

System scheduling workflow generation method, system, equipment and computer readable storage medium

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on January 10, 2020, the application number is CN202010027930.1, and the invention title is "System Scheduling Workflow Generation Method and System", the entire content of which is incorporated by reference In this application.

Technical field

The embodiments of the present application relate to the field of cloud technology, and in particular, to a method, system, device, and computer-readable storage medium for generating a system scheduling workflow.

Background technique

Workflow technology is the core technology for realizing business process automation. The main problem that the workflow solves is to use computers to automatically transfer documents, information or tasks among multiple participants in accordance with predetermined rules in order to achieve a certain business goal.

technical problem

The inventor realizes that traditional workflow technology can only connect different functional interfaces in a separate system to achieve a certain business goal. If you need to connect an external system to achieve business goals, you need to develop customized code, which is costly. And the flexibility is poor.

Technical solutions

A method for generating a system scheduling workflow. The method for generating a system scheduling workflow includes: providing a configuration interface for users to configure various business modules that are required to implement financial services, the parameters of the various business modules, and all The connection relationship between the various service modules; after the user completes the configuration operation, a configuration file for realizing financial services is generated according to the configuration operation, and the configuration file includes the various service modules that need to be called to realize the financial service , The parameter configuration information of each service module, and the connection relationship between the various service modules; and converting the configuration file into an XML file executable by the workflow engine, wherein the parameter configuration information includes the various The invocation type information of the business module, said converting the configuration file into an XML file executable by the workflow engine includes: converting each business module that needs to be invoked into a corresponding process according to the invocation type information of each business module An activity node, wherein the process activity node is an executable XML fragment; adding parameter configuration information of the parameter configuration information of each service module except the call type information to the process activity node; The obtained process activity nodes are connected in series according to the connection relationship to obtain the final executable XML file.

A system scheduling workflow generating device. The system scheduling workflow generating device includes: a providing module for providing a configuration interface for a user to configure various business modules required to implement financial services. The various business modules And the connection relationship between the various service modules; the generating module is used to generate a configuration file for realizing financial services according to the configuration operation after the user completes the configuration operation, and the configuration file includes the realization of all The various business modules that need to be called by the financial business, the parameter configuration information of the various business modules, and the connection relationship between the various business modules; and a conversion module for converting the configuration file into a workflow engine executable XML file, wherein the parameter configuration information includes the call type information of each service module, and the conversion module is also used to convert each service module that needs to be called into The corresponding process activity node, where the process activity node is an executable XML fragment; the parameter configuration information of each service module except the call type information is added to the process activity node In; the obtained process activity nodes are concatenated according to the connection relationship, and the final executable XML file is obtained.

A computer device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processor is used to implement the following steps when the computer program is executed:

Provide a configuration interface for the user to configure the various business modules required to implement financial services, the parameters of the various business modules, and the connection relationship between the various business modules;

After the user completes the configuration operation, a configuration file for realizing financial services is generated according to the configuration operation. The configuration file includes various business modules that are required to implement the financial services, and the parameter configuration of each business module Information, and the connection relationship between the various business modules; and

The configuration file is converted into an XML file executable by the workflow engine, wherein the parameter configuration information includes the invocation type information of each service module, and the configuration file is converted into an XML file executable by the workflow engine Documents, including:

Converting each business module that needs to be called into a corresponding process activity node according to the call type information of each business module, where the process activity node is an executable XML fragment;

Adding parameter configuration information of the parameter configuration information of each service module other than the call type information to the process activity node;

The obtained process activity nodes are connected in series according to the connection relationship to obtain the final executable XML file.

A computer-readable storage medium in which a computer program is stored, and the computer program can be executed by at least one processor, so that the at least one processor executes the following steps:

This application can obtain a configuration file for realizing financial services, and then can convert the obtained configuration file into an XML file executable by the workflow engine. There is no need for developers to develop code, which saves the development time needed to achieve business goals, reduces costs, and has high flexibility.

Description of the drawings

FIG. 1 schematically shows a flowchart of a method for generating a system scheduling workflow according to Embodiment 1 of the present application;

Fig. 2 schematically shows a detailed flow chart of the steps of converting the configuration file into an XML file executable by the workflow engine in this application;

FIG. 3 schematically shows a detailed flow chart of the steps of connecting each process activity node obtained in this application according to the connection relationship to obtain a final executable XML file;

Fig. 4 schematically shows a block diagram of an apparatus for generating a system scheduling workflow according to a second embodiment of the present application; and

FIG. 5 schematically shows a schematic diagram of the hardware architecture of a computer device suitable for implementing the method for generating a system scheduling workflow according to the third embodiment of the present application.

Embodiments of the present invention

In order to make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the following further describes the embodiments of the present application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the embodiments of the present application, and are not used to limit the embodiments of the present application. Based on the embodiments in the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of the embodiments of the present application.

It should be noted that the descriptions related to "first", "second", etc. in the embodiments of this application are only for descriptive purposes, and cannot be understood as indicating or implying their relative importance or implicitly specifying the indicated technical features quantity. Therefore, the features defined with "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but it must be based on what can be achieved by a person of ordinary skill in the art. When the combination of technical solutions is contradictory or cannot be achieved, it should be considered that this combination of technical solutions does not exist. , Also does not fall within the scope of protection required by the embodiments of this application.

Example one

Fig. 1 schematically shows a flowchart of a method for generating a system scheduling workflow according to Embodiment 1 of the present application. It can be understood that the flowchart in this method embodiment is not used to limit the order of execution of the steps. The following exemplarily describes the computer device 2 as the execution subject.

As shown in Figure 1, the system scheduling workflow generation method may include steps S100 to S102, where:

In step S100, a configuration interface is provided for the user to configure various service modules required to implement financial services, the parameters of the various service modules, and the connection relationship between the various service modules.

Step S102: After the user completes the configuration operation, generate a configuration file for realizing financial services according to the configuration operation. The configuration file includes various business modules that need to be called to implement the financial business. Parameter configuration information of and the connection relationship between the various service modules.

The financial services in this embodiment may be services such as internal monitoring, approval, and operation of the enterprise, such as loan approval services, credit card application services, loan lending services, and so on. The realization of each financial business needs to be processed in accordance with a specific process through multiple business modules in the internal management process of the financial business to realize the financial business. Among them, each business module (or business system) can implement a business function.

For example, when realizing the loan lending business, the following business modules are generally required to complete the loan lending business according to the following process: 1) The quota system needs to be transferred to verify the lender’s quota; 2) if the quota system checks the lender After successfully completing the verification of the loan amount, the loan system needs to be called for loan; 3) After the loan system has released the loan, the loan system needs to call back the loan result; 4) When the loan system’s loan result is successful, the loan needs to be called again The system deducts the lender’s limit; 5) After the limit deduction is completed, the system needs to call the order system to record the lender’s loan order to update the loan order; 6) Finally, it needs to call the SMS system to send SMS to notify the lender to complete the loan disbursement.

In order to realize the financial service, a configuration interface can be provided on the computer device 2. The user (which can be a non-developer, such as a product manager) can configure various business modules that need to be called to realize the financial service through the configuration interface, and configure each business module Configure the parameters of, and configure the connection relationship between the various business modules. After the user completes the above configuration operation, a configuration file for realizing the financial service is generated, and the configuration file is stored, so that the computer device 2 can obtain the configuration file. Correspondingly, the configuration file includes various service modules that are required to implement the financial service, the parameter configuration information of each service module, and the connection relationship between the various service modules. Wherein, the parameter configuration information may include invocation type information of the service module, logical judgment information, interface invocation address information, interface invocation method information, and in and out parameter configuration information of the service module.

The service call type information is information used to characterize whether the service interface provided to the service module is a synchronous interface call or an asynchronous interface call.

The logical judgment information is information used to set different return results of business modules to go through different process branches. Specifically, the logical judgment information is generally an IF logical judgment statement. For example, the IF logical judgment statement can be used to set if the business module A’s If the return value contained in the return result is 1, the calling process is ended, and if the return value contained in the return result of business module A is 0, then the process of calling business module B is followed. For another example, if the business module A does not return a result within 10 hours, the calling process is ended. If the business module A returns a result within 10 hours, the process of calling business module C is followed.

The interface calling address information is the address to be pointed to when calling the business interface provided by the business module, for example, the identification code ID of the external system module.

The interface invocation mode information is whether the service interface provided by the invoking service module is invoked in an http request method or in a cloud transmission method.

The input and output parameter configuration information of the business module is the configuration information of the output and input parameters of the business module, including the field type conversion, field format conversion, parameter assignment, etc. of the output parameter and the input parameter.

Step S104: Convert the configuration file into an XML file executable by the workflow engine.

When the computer device 2 obtains the configuration file, it can convert the configuration file into an XML (Extensible Markup Language) file executable by the workflow engine, where XML can be used to mark data and define data. Type is a source language that allows users to define their own markup language.

The workflow engine may be a jbpm workflow engine, an Activiti workflow engine, and the like. Among them, jBpm is a flexible and extensible workflow engine system. The business process input by the server as jBpm runtime is expressed in a simple and powerful language and packaged in the process archive. jBmp combines the convenience of workflow application development with outstanding enterprise application integration (EAI) capabilities. jBmp includes a web application and a scheduler. jBmp is a set of J2SE components that can be deployed as a J2EE application cluster. Activiti is a lightweight, embeddable BPM engine, and it is also designed for a scalable cloud architecture.

Since the call conversion of each service module is performed according to the call type information of each service module included in the parameter configuration information, the call type information includes synchronous interface call and asynchronous interface call. In an exemplary embodiment, referring to FIG. 2, the step S104 may include the following steps:

Step S200: Convert each business module to be called into a corresponding process activity node according to the call type information of each business module, where the process activity node is an executable XML fragment.

Each business module has corresponding call type information. The call type information of different business modules can be the same or different. For example, the call type information of business module A is synchronous interface call, and the call type information of business module B is synchronous Interface call, the call type information of service module C is asynchronous interface call.

After obtaining the invocation type information of each business module, the invocation process of the business module can be converted into the corresponding process activity node (Task). For example, the call to business module A is converted to Task1, the call to business module B is converted to Task2, and the call to business module C is converted to Task3. It should be noted that, in order to distinguish different process activity nodes, different process activity nodes have different node identifiers (IDs). The transformed process activity node conforms to the BPMN standard. Among them, the BPMN standard is defined by BPMI (The Business Process Management Initiative has developed a set of standards called Business Process Modeling Notation (BPMN-Business Process Modeling Notation).

Because of different call types, the process activity nodes of the conversion are different. In an exemplary embodiment, the step S200 may include the following steps: if the call type of the business module that needs to be called currently is a synchronous interface call, then the business module that needs to be called currently is converted into an atomic process activity Node (serviceTask0); if the call type of the business module that needs to be called currently is asynchronous interface call, then the business module that needs to be called currently is converted into three atomic process activity nodes, each of which is a call-out process activity node ( serviceTask1), a process activity node waiting for the callback (receiveTask), and a process activity node (serviceTask2) for processing the callback result.

In this embodiment, the process of calling out the process activity node (serviceTask1) is the same as the process of invoking the corresponding process activity node (serviceTask0) of the synchronization interface. If the process activity node (serviceTask1) is called successfully to call the business module, By waiting for the callback process activity node (receiveTask) to be in the waiting state, waiting to be awakened, and waiting for the callback process activity node (receiveTask) to receive interface callback information, and after receiving the interface callback information, the callback parameters are passed to the callback result processing process The activity node (serviceTask2) performs processing, and after the callback result processing flow activity node (serviceTask2) processes the callback result, the processed result is carried by the process and passed to the next process activity node.

Step S202: Add parameter configuration information of the parameter configuration information of each service module other than the call type information to the process activity node.

After the computer device 2 converts each business module that needs to be called into the corresponding process activity node, it needs to add the parameter configuration information of each business module except the call type information to the process activity. In the node, so that when the workflow engine executes the process activity node, it can correspondingly convert the output and input parameters of the business module according to the parameter configuration information to convert them into parameters that meet the system specifications.

Since scheduling exceptions may occur in the process of invoking service modules, in order to deal with the scheduling exceptions, in an exemplary embodiment, after the step S200, the following steps may be further included: adding to the process activity node The transaction rollback operation that needs to be executed when the call to each service module fails.

By adding a transaction rollback operation to the process activity node, the workflow engine can capture the call failure/abnormal message when executing the process activity node, and call back according to the provided failure rollback interface, and the process activity node itself Things are also rolled back to the state before the execution of this process activity node.

Because when the parameter configuration information includes logical judgment information, different return results of the business modules will follow different process branches. In order to take different process branches according to different return results after invoking the business module, in an exemplary embodiment, after the step S200, the following step may be further included: generating branch judgments according to the logical judgment information Condition, and add the branch judgment condition to the process activity node.

By adding the branch judgment condition (exclusiveGateway) to the process activity node, the workflow engine can decide which process branch to execute afterwards according to different return results when executing the process activity node, so that the return result can be transferred to The next process activity node.

Because when the parameter configuration information includes timeout processing information, the service module scheduling can be configured according to the timeout period. Wherein, the timeout processing information includes the specific time for the service module to process the timeout, such as 5 days, and the service module scheduled after the service module processing timeout, for example, after the service module A processes the timeout, the call to the service module B is executed. Therefore, in order to implement the configuration of the service module scheduling according to the timeout period, in an exemplary embodiment, after the step S200, the following steps may be further included: generating a timed task according to the timeout processing information, and combining the timed task The task is added to the process activity node.

By adding a timed task to the process node, the workflow engine can determine whether the processing of the business module has timed out according to the timed task when executing the process activity node, and execute the next process activity node after the timeout.

In step S204, the obtained process activity nodes are concatenated according to the connection relationship to obtain a final executable XML file.

Since each process activity node is an XML fragment, a complete XML file can be obtained by splicing each XML fragment according to the connection relationship. Wherein, the connection relationship is the calling sequence of each service module.

The computer equipment 2 can connect various process activity nodes in series in various ways. In an exemplary embodiment, referring to FIG. 3, the step S204 includes:

S300: According to the connection relationship, each obtained process activity node is divided into multiple groups of process activity node pairs to be connected, wherein each group of process activity node pairs includes a source node and a target node.

S302: Connect the source node of each group of process activity node pairs to the target node through a preset function.

It should be noted that each process activity node in each process activity node except the start activity node and the end activity node will exist in two pairs of process activity nodes to be connected, and in one of the process activity nodes to be connected The pair of activity nodes act as the source node, and the pair of process activity nodes to be connected acts as the target node. Therefore, the source node in each group of process activity node pairs can be connected to the target node through a preset function. In an exemplary embodiment, the source node of each set of process activity node pairs can be connected to the target node through the SourceRef function and the TargetRef function.

For example, if the first process activity node (serviceTask1), the second process activity node (serviceTask2), and the third process activity node (receiveTask1) need to be connected in series, this can be achieved through the following function:

sourceRef="serviceTask1" targetRef "serviceTask2"

sourceRef="serviceTask2" targetRef "receiveTask1"

In the above-mentioned function realization process, the first process activity node and the second process activity node are connected in series. Then the second process activity node and the third process activity node are connected in series to obtain a complete XML file.

In an exemplary embodiment, after the step S102, the method further includes:

The XML file is executed to realize the financial service.

The computer device 2 is converting the configuration file into an XML file executable by the workflow engine, that is, the XML file can be executed by the workflow engine to realize the financial service.

In an exemplary embodiment, in the process of executing the XML file, the workflow engine can record the time spent in the process of invoking each business module, and record the parameters in the invoking process, so that the system can perform the invoking process monitor.

In the embodiment of the present application, a configuration file used to implement financial services can be obtained, and the obtained configuration file can be converted into an XML file executable by the workflow engine. Compared with the traditional method that requires customized code development, the embodiments of the present application do not require developers to perform code development, which saves development time required to achieve business goals, reduces costs, and has higher flexibility.

Example two

Figure 4 schematically shows a block diagram of a system scheduling workflow generation device according to the second embodiment of the present application. The system scheduling workflow generation device can be divided into one or more program modules, and one or more program modules are stored in In a storage medium, and executed by one or more processors, to complete the embodiments of the present application. The program module referred to in the embodiment of the present application refers to a series of computer program instruction segments that can complete specific functions. The following description will specifically introduce the function of each program module in this embodiment.

As shown in FIG. 4, the system scheduling workflow generating device 400 may include a providing module 410, a generating module 420, and a conversion module 430, where:

The providing module 410 is configured to provide a configuration interface for the user to configure various service modules required to implement financial services, the parameters of the various service modules, and the connection relationship between the various service modules.

The generating module 420 is configured to generate a configuration file for realizing financial services according to the configuration operation after the user completes the configuration operation, and the configuration file includes various business modules that need to be called to realize the financial service. Parameter configuration information of each service module, and the connection relationship between the various service modules

The conversion module 430 is used to convert the configuration file into an XML file executable by the workflow engine, wherein the parameter configuration information includes the invocation type information of each service module, and the conversion module is also used to The call type information of each business module converts each business module that needs to be called into a corresponding process activity node, where the process activity node is an executable XML fragment; the parameter configuration information of each business module is divided by Parameter configuration information other than the call type information is added to the process activity node; each obtained process activity node is connected in series according to the connection relationship to obtain a final executable XML file.

In an exemplary embodiment, when the invocation type information includes synchronous interface invocation and asynchronous interface invocation, the conversion module 430 is also used to: if the invocation type of the service module that needs to be invoked is synchronous interface invocation, then The current business module that needs to be called is converted into an atomic process activity node; if the calling type of the current business module that needs to be called is asynchronous interface calling, then the current business module that needs to be called is converted into three atomic processes The activity nodes are respectively a callout process activity node, a waiting callback process activity node, and a callback result processing process activity node.

In an exemplary embodiment, the conversion module 430 is further configured to: add a transaction rollback operation that needs to be performed when invoking the various business modules fails in the process activity node.

In an exemplary embodiment, the conversion module 430 is further configured to: generate a branch judgment condition according to the logical judgment information, and add the branch judgment condition to the process activity node.

In an exemplary embodiment, when the parameter configuration information includes timeout processing information, the conversion module 430 is further configured to: generate a timed task according to the timeout processing information, and add the timed task to the process activity Node.

In an exemplary embodiment, the conversion module 420 is further configured to: divide the obtained process activity nodes into multiple groups of process activity node pairs to be connected according to the connection relationship, wherein each group of process activity node pairs includes a source Nodes and target nodes; the source node in each pair of process activity nodes is connected to the target node through a preset function.

In an exemplary embodiment, the preset functions are SourceRef function and TargetRef function.

In an exemplary embodiment, the system scheduling workflow generation device 400 further includes:

The execution module is used to execute the XML file to realize the financial service.

Example three

FIG. 5 schematically shows a schematic diagram of the hardware architecture of a computer device 2 suitable for implementing the method for generating a system scheduling workflow according to the third embodiment of the present application. In this embodiment, the computer device 2 is a device that can automatically perform numerical calculation and/or information processing in accordance with pre-set or stored instructions. For example, it can be a rack server, a blade server, a tower server, or a cabinet server (including an independent server or a server cluster composed of multiple servers) with a gateway function. As shown in FIG. 5, the computer device 6 at least includes but is not limited to: a memory 510, a processor 520, and a network interface 530 that can communicate with each other through a system bus. among them:

The memory 510 includes at least one type of computer-readable storage medium. The readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), and static random access memory. (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disks, optical disks, etc. In some embodiments, the memory 510 may be an internal storage module of the computer device 2, for example, the hard disk or memory of the computer device 2. In other embodiments, the memory 510 may also be an external storage device of the computer device 2, for example, a plug-in hard disk equipped on the computer device 2, a smart memory card (Smart Media Card, referred to as SMC), and a secure digital (Secure Digital). Digital, abbreviated as SD) card, flash card (Flash Card), etc. Of course, the memory 510 may also include both the internal storage module of the computer device 2 and its external storage device. In this embodiment, the memory 510 is generally used to store the operating system and various application software installed in the computer device 2, such as the program code of the system scheduling workflow generation method. In addition, the memory 510 may also be used to temporarily store various types of data that have been output or will be output.

In some embodiments, the processor 520 may be a central processing unit (Central Processing Unit, CPU for short), a controller, a microcontroller, a microprocessor, or other data processing chips. The processor 520 is generally used to control the overall operation of the computer device 2, for example, to perform data interaction or communication-related control and processing with the computer device 2. In this embodiment, the processor 520 is configured to run program codes stored in the memory 510 or process data.

The network interface 530 may include a wireless network interface or a wired network interface, and the network interface 530 is generally used to establish a communication link between the computer device 2 and other computer devices. For example, the network interface 530 is used to connect the computer device 2 to an external terminal through a network, and to establish a data transmission channel and a communication link between the computer device 2 and the external terminal. The network can be Intranet, Internet, Global System of Mobile communication, GSM for short), Wideband Code Division Multiple Access (Wideband Code Division Multiple Access) Access, referred to as WCDMA for short), 4G network, 5G network, Bluetooth (Bluetooth), Wi-Fi and other wireless or wired networks.

It should be pointed out that FIG. 5 only shows a computer device with components 510-530, but it should be understood that it is not required to implement all the components shown, and more or fewer components may be implemented instead.

In this embodiment, the system scheduling workflow generation method stored in the memory 510 can also be divided into one or more program modules and executed by one or more processors (in this embodiment, the processor 520). To achieve the following steps:

The specific implementation of the computer device of the present application is substantially the same as the specific implementation of the foregoing system scheduling workflow generation method, and will not be repeated here.

Example four

This embodiment also provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

Obtaining a configuration file for realizing the financial service, the configuration file including the various service modules that need to be called to realize the financial service, the parameter configuration information of the various service modules, and the connection relationship between the various service modules; and

The configuration file is converted into an XML file executable by the workflow engine.

In this embodiment, the computer-readable storage medium may be volatile or non-volatile. The computer-readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.) , Random Access Memory (RAM), Static Random Access Memory (SRAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), Programmable Read Only Memory (PROM), Magnetic Memory, Disk, CD etc. In some embodiments, the computer-readable storage medium may be an internal storage unit of a computer device, such as a hard disk or memory of the computer device. In other embodiments, the computer-readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, a smart memory card (Smart Media Card, referred to as SMC), a secure digital ( Secure Digital, abbreviated as SD) card, flash card (Flash Card), etc. Of course, the computer-readable storage medium may also include both the internal storage unit and the external storage device of the computer device. In this embodiment, the computer-readable storage medium is generally used to store the operating system and various application software installed in the computer device, such as the program code of the system scheduling workflow generation method in the embodiment. In addition, the computer-readable storage medium can also be used to temporarily store various types of data that have been output or will be output.

In another embodiment, in the system scheduling workflow generation method provided by the present application, in order to further ensure the privacy and security of all the above-mentioned data, all the above-mentioned data can also be stored in a node of a blockchain. For example, the parameters of each business module, XML files, etc., these data can be stored in the blockchain node.

It should be noted that the blockchain referred to in this application is a new application mode of computer technology such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm. Blockchain, essentially a decentralized database, is a series of data blocks associated with cryptographic methods. Each data block contains a batch of network transaction information for verification. The validity of the information (anti-counterfeiting) and generation of the next block. The blockchain can include the underlying platform of the blockchain, the platform product service layer, and the application service layer.

Obviously, those skilled in the art should understand that the modules or steps of the embodiments of the present application described above can be implemented by a general computing device, and they can be concentrated on a single computing device or distributed among multiple computing devices. Optionally, they can be implemented by the program code executable by the computing device, so that they can be stored in the storage device for execution by the computing device, and in some cases, they can be different from here The steps shown or described are executed in the order of, or they are respectively fabricated into individual integrated circuit modules, or multiple modules or steps of them are fabricated into a single integrated circuit module to achieve. In this way, the embodiments of the present application are not limited to any specific combination of hardware and software.

The above are only the preferred embodiments of the embodiments of the application, and do not limit the scope of the patents of the embodiments of the application. Any equivalent structure or equivalent process transformation made by using the description and drawings of the embodiments of the application, or directly or indirectly used In other related technical fields, the same is included in the scope of patent protection of the embodiments of this application.

Claims

A method for generating system scheduling workflow, wherein the method includes:

Provide a configuration interface for the user to configure the various business modules required to implement financial services, the parameters of the various business modules, and the connection relationship between the various business modules;

After the user completes the configuration operation, a configuration file for realizing financial services is generated according to the configuration operation. The configuration file includes various business modules that are required to implement the financial services, and the parameter configuration of each business module Information, and the connection relationship between the various business modules; and

The configuration file is converted into an XML file executable by the workflow engine, wherein the parameter configuration information includes the invocation type information of each service module, and the configuration file is converted into an XML file executable by the workflow engine Documents, including:

Converting each business module that needs to be called into a corresponding process activity node according to the call type information of each business module, where the process activity node is an executable XML fragment;

Adding parameter configuration information of the parameter configuration information of each service module other than the call type information to the process activity node;

The obtained process activity nodes are connected in series according to the connection relationship to obtain the final executable XML file.
The method for generating a system scheduling workflow according to claim 1, wherein the invocation type information includes synchronous interface invocation and asynchronous interface invocation, and according to the invocation type information of each service module, the various service modules that need to be invoked are The conversion to the corresponding process activity node includes:

If the call type of the currently required business module is a synchronous interface call, then the currently required business module is converted into an atomic process activity node;

If the call type of the business module that needs to be called is asynchronous interface call, the business module that needs to be called currently is converted into three atomic process activity nodes, which are respectively a call-out process activity node and a waiting callback process activity Node, and a callback result processing flow activity node.
The system scheduling workflow generation method according to claim 1, wherein after the step of converting each business module to be called into a corresponding process activity node according to the calling type information of each business module, the method further comprises:

In the process activity node, a transaction rollback operation that needs to be executed when the call to each service module fails is added.
The method for generating a system scheduling workflow according to claim 1, wherein the parameter configuration information includes logical judgment information, and the various business modules that need to be called are converted into corresponding ones according to the calling type information of the various business modules. After the steps of the process activity node, it also includes:

A branch judgment condition is generated according to the logical judgment information, and the branch judgment condition is added to the process activity node.
The method for generating a system scheduling workflow according to claim 1, wherein the parameter configuration information includes timeout processing information, and the various business modules that need to be called are converted into corresponding ones according to the calling type information of the various business modules. After the steps of the process activity node, it also includes:

Generate a timed task according to the timeout processing information, and add the timed task to the process activity node.
The method for generating a system scheduling workflow according to any one of claims 1 to 5, wherein said concatenating the obtained process activity nodes according to the connection relationship to obtain the final executable XML file comprises:

Dividing each obtained process activity node into multiple groups of process activity node pairs to be connected according to the connection relationship, wherein each group of process activity node pairs includes a source node and a target node;

The source node in each pair of process activity nodes is connected to the target node through a preset function.
The method for generating a system scheduling workflow according to claim 6, wherein the preset function is a SourceRef function and a TargetRef function.
A system scheduling workflow generating device, which includes:

A providing module is used to provide a configuration interface for the user to configure the various business modules required to implement financial services, the parameters of the various business modules, and the connection relationship between the various business modules;

The generating module is used to generate a configuration file for realizing financial services according to the configuration operation after the user completes the configuration operation, and the configuration file includes various business modules called for realizing the financial service. Parameter configuration information of the service modules, and the connection relationship between the various service modules; and

The conversion module is used to convert the configuration file into an XML file executable by the workflow engine, wherein the parameter configuration information includes the invocation type information of each service module, and the conversion module is also used to convert the configuration file according to the The call type information of each business module converts each business module that needs to be called into a corresponding process activity node, where the process activity node is an executable XML fragment; the parameter configuration information of each business module is divided by The parameter configuration information other than the call type information is added to the process activity node; the obtained process activity nodes are connected in series according to the connection relationship to obtain the final executable XML file.
A computer device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processor is used to implement the following steps when the computer program is executed:

Provide a configuration interface for the user to configure the various business modules required to implement financial services, the parameters of the various business modules, and the connection relationship between the various business modules;

After the user completes the configuration operation, a configuration file for realizing financial services is generated according to the configuration operation. The configuration file includes various business modules that are required to implement the financial services, and the parameter configuration of each business module Information, and the connection relationship between the various business modules; and

The configuration file is converted into an XML file executable by the workflow engine, wherein the parameter configuration information includes the invocation type information of each service module, and the configuration file is converted into an XML file executable by the workflow engine Documents, including:

Converting each business module that needs to be called into a corresponding process activity node according to the call type information of each business module, where the process activity node is an executable XML fragment;

Adding parameter configuration information of the parameter configuration information of each service module other than the call type information to the process activity node;

The obtained process activity nodes are connected in series according to the connection relationship to obtain the final executable XML file.
The computer device according to claim 9, wherein the call type information includes synchronous interface call and asynchronous interface call, and the call type information of each service module converts each service module that needs to be called into a corresponding Process activity nodes include:

If the call type of the currently required business module is a synchronous interface call, then the currently required business module is converted into an atomic process activity node;

If the call type of the business module that needs to be called is asynchronous interface call, the business module that needs to be called currently is converted into three atomic process activity nodes, which are respectively a call-out process activity node and a waiting callback process activity Node, and a callback result processing flow activity node.
The computer device according to claim 9, wherein after the step of converting each business module to be called into a corresponding process activity node according to the calling type information of each business module, the processor executes the The computer program also implements the following steps:

In the process activity node, a transaction rollback operation that needs to be executed when the call to each service module fails is added.
The computer device according to claim 9, wherein the parameter configuration information includes logical judgment information, and the various business modules that need to be called are converted into corresponding process activity nodes according to the calling type information of the various business modules. After the steps, the processor further implements the following steps when executing the computer program:

A branch judgment condition is generated according to the logical judgment information, and the branch judgment condition is added to the process activity node.
The computer device according to claim 9, wherein the parameter configuration information includes timeout processing information, and the various service modules that need to be called are converted into corresponding process activity nodes according to the invocation type information of the various service modules. After the steps, the processor further implements the following steps when executing the computer program:

Generate a timed task according to the timeout processing information, and add the timed task to the process activity node.
The computer device according to any one of claims 9 to 13, wherein said concatenating the obtained process activity nodes according to the connection relationship to obtain the final executable XML file comprises:

Dividing each obtained process activity node into multiple groups of process activity node pairs to be connected according to the connection relationship, wherein each group of process activity node pairs includes a source node and a target node;

The source node in each pair of process activity nodes is connected to the target node through a preset function.
The computer device according to claim 14, wherein the preset function is a SourceRef function and a TargetRef function.
A computer-readable storage medium in which a computer program is stored, and the computer program can be executed by at least one processor, so that the at least one processor executes the following steps:

Provide a configuration interface for the user to configure the various business modules required to implement financial services, the parameters of the various business modules, and the connection relationship between the various business modules;

After the user completes the configuration operation, a configuration file for realizing financial services is generated according to the configuration operation. The configuration file includes various business modules that are required to implement the financial services, and the parameter configuration of each business module Information, and the connection relationship between the various business modules; and

The configuration file is converted into an XML file executable by the workflow engine, wherein the parameter configuration information includes the invocation type information of each service module, and the configuration file is converted into an XML file executable by the workflow engine Documents, including:

Converting each business module that needs to be called into a corresponding process activity node according to the call type information of each business module, where the process activity node is an executable XML fragment;

Adding parameter configuration information of the parameter configuration information of each service module other than the call type information to the process activity node;

The obtained process activity nodes are connected in series according to the connection relationship to obtain the final executable XML file.
The computer-readable storage medium according to claim 16, wherein the call type information includes synchronous interface call and asynchronous interface call, and the various service modules to be called are converted according to the call type information of the various service modules The corresponding process activity nodes include:

If the call type of the currently required business module is a synchronous interface call, then the currently required business module is converted into an atomic process activity node;

If the call type of the business module that needs to be called is asynchronous interface call, the business module that needs to be called currently is converted into three atomic process activity nodes, which are respectively a call-out process activity node and a waiting callback process activity Node, and a callback result processing flow activity node.
The computer-readable storage medium according to claim 16, wherein after the step of converting each business module to be called into a corresponding process activity node according to the calling type information of each business module, the at least one The processor also performs the following steps:

In the process activity node, a transaction rollback operation that needs to be executed when the call to each service module fails is added.
The computer-readable storage medium according to claim 16, wherein the parameter configuration information includes logical judgment information, and the respective service modules that need to be called are converted into corresponding processes according to the calling type information of the respective service modules After the step of the active node, the at least one processor further executes the following steps:

A branch judgment condition is generated according to the logical judgment information, and the branch judgment condition is added to the process activity node.
The computer-readable storage medium according to claim 16, wherein the parameter configuration information includes timeout processing information, and each service module to be called is converted into a corresponding process according to the call type information of each service module After the step of the active node, the at least one processor further executes the following steps:

Generate a timed task according to the timeout processing information, and add the timed task to the process activity node.