Task process constructing and driving device

Abstract

The invention provides a task flow construction and driving device, and relates to the technical field of task driving and task flow splicing, and the device comprises a flow link creation module which is used for providing creation functions of different types of flow links and at least comprises a self-defined link creation sub-module, and the flow links at least comprise self-defined links so as to process self-defined business logic; the process template configuration module is used for splicing and combining the created process links into a process template and defining a dependency relationship between the process links; the process driving module is used for creating a process instance according to the process template and the parameters and data of the to-be-processed task, and driving a process link in the process instance to execute a task process; the process state monitoring module is used for monitoring and visually displaying the execution condition of the process instance according to the execution data and state of the process link; and the data sharing unit module is used for storing and managing data of the process links in the task execution process, so that the process links share the data.

Description

Technical Field

[0001] The present invention relates to the technical field of task drive and task process assembly, and in particular to a task process construction and driving device that supports data interaction and user-defined logic processing. Background Art

[0002] At present, most traditional task-driven systems are the practice of the concept of Business Process Management (BPM). Based on various workflow engines, such as jBPM and NetBPM, workflow management systems (WFMS) are built to model, implement, monitor and manage business processes. These task-driven systems usually abstract business processes into multiple business links that are executed in sequence. Each link has a corresponding executor or execution system. The executor / execution system interacts with the task-driven system through a pre-set formatted form. The task-driven system parses the form according to the pre-customized form parser, analyzes the execution status of the link, and decides whether to enter the next link. Then, the form for starting execution is sent to the executor / system corresponding to the next link, and the above process is executed repeatedly, thereby driving the task process to execute in sequence.

[0003] However, this traditional task-driven system has the following disadvantages:

[0004] 1. The business systems under management have not been completely decoupled. Each business system still needs to interact with the task-driven system for data and information exchange independently.

[0005] 2. It can only parse and process formatted forms, but cannot implement complex business logic;

[0006] 3. Once the process is put into operation, it cannot be flexibly adjusted online.

[0007] Therefore, when facing business application scenarios such as large-scale data processing, it is necessary to design a new task-driven system to at least partially solve the above-mentioned drawbacks. Summary of the invention

[0008] In view of this, the present invention provides a task process construction and driving device, which has the ability to efficiently transfer and interact data and information between systems, has the ability to model and execute custom business logic, and can adapt to business scenarios of large-scale data processing.

[0009] The task process construction and driving device provided by the embodiment of the present invention includes: a process link creation module, which is used to provide a creation function of different types of process links, the process link creation module at least includes a custom link creation submodule, and the process link includes at least a custom link, wherein the custom link creation submodule processes the custom business logic by creating a custom link; a process template configuration module, which is used to splice and combine the created process links into a process template with specific logic in the process canvas; a process driving module, which is used to create a process instance according to the process template and the parameters and data of the task to be processed, and drive the process links in the process instance to execute the task process; a process status monitoring module, which is used to monitor and visualize the execution status of the process instance according to the execution data and execution status of the process link; and a data sharing unit module, including a data storage management submodule, the data sharing unit module is used to store and manage all data generated by the process link in the execution of the task process, and enable the process link to share data through the data storage management submodule.

[0010] According to an embodiment of the present invention, the process link creation module further includes: an interface link creation submodule for creating an interface link; and / or a file link creation submodule for creating a file link.

[0011] According to an embodiment of the present invention, the process link creation module is also used to set the attributes of the process link and store the attributes of the process link in the data storage management submodule; wherein the custom link, interface link and file link have different attributes.

[0012] According to an embodiment of the present invention, the custom link processes the custom business logic through a custom groovy script.

[0013] According to an embodiment of the present invention, the process template configuration module includes a process template creation submodule and a process template management submodule, wherein the process template creation submodule is used to create a process template in a process canvas, and the process template management submodule is used to set the properties of the process template and define the strong and weak dependencies between process links, and store the properties and strong and weak dependencies of the process template in the data storage management submodule.

[0014] According to an embodiment of the present invention, the process driving module includes a process instantiation sub-module and a process driving engine sub-module, wherein the process instantiation sub-module is used to call the process initiation interface, pass in the process template number and the initialization business parameters and data of the task to be processed to create a corresponding process instance, and the process driving engine sub-module is used to execute the task process according to the operation logic of the process template during the operation of the process instance.

[0015] According to an embodiment of the present invention, the process driving module also includes a process adjustment sub-module, which is used to adjust the number of process links and / or the dependencies between process links during the process of executing the task process in the process links; the process driving engine sub-module is also used to set and debug the adjusted process links, and re-drive and execute the adjusted task process.

[0016] According to an embodiment of the present invention, the process status monitoring module includes a process monitoring sub-module and a process visualization sub-module, wherein the process monitoring sub-module is used to monitor the execution time of the process links and send an alarm message when the execution time exceeds the preset time; the process visualization sub-module is used to visually display the execution status of the process instance during the monitoring process.

[0017] According to an embodiment of the present invention, the data storage management submodule includes a non-relational database and a standard data storage interface, and the data sharing unit module also includes a data access submodule, and the data access submodule includes a standard data access interface; wherein, data is shared between process links through the non-relational database, the standard data access interface and the data storage interface.

[0018] According to an embodiment of the present invention, the non-relational database includes a key-value storage structure.

[0019] The task process construction and driving device provided in accordance with the embodiment of the present invention has the function of creating different types of process links. By creating process links such as custom links and using custom scripts to process custom business logic, the device can process non-formatted forms and implement complex business logic. All data generated by the process links are managed through the data sharing unit module, and data sharing is achieved between each process link through this module, that is, each process link is independent of each other but data is shared between each process link, which can completely decouple the managed business system and realize data and information interaction between business systems as tasks are executed, thereby improving the stability and reliability of the overall business operation. In addition, the link status information during the operation of the task process instance can be monitored through the process status monitoring module for visual display. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The above and other objects, features and advantages of the present invention will become more apparent through the following description of the embodiments of the present invention with reference to the accompanying drawings, in which:

[0021] Figure 1 Schematically shows a structural block diagram of a task flow construction and driving device according to some embodiments of the present invention;

[0022] Figure 2 Schematically shows a task flow construction and operation flow chart of a driving device according to some embodiments of the present invention;

[0023] Figure 3 Schematically showing a state transition path diagram of process links of different link types according to some embodiments of the present invention;

[0024] Figure 4 Schematically illustrates a process template for a satellite to perform a task according to some embodiments of the present invention;

[0025] Figure 5 Schematically showing a flowchart of a driver execution task process according to some embodiments of the present invention;

[0026] Figure 6 Schematically shows Figure 4 The task flow corresponding to the process template shown. DETAILED DESCRIPTION

[0027] Below, embodiments of the present invention will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present invention. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of embodiments of the present invention. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of concepts of the present invention.

[0028] The terms used herein are only for describing specific embodiments and are not intended to limit the present invention. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0029] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0030] In the case of using expressions such as "at least one of A, B, and C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.). In the case of using expressions such as "at least one of A, B, or C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B, or C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0031] Figure 1 The structure block diagram of the task flow construction and driving device according to some embodiments of the present invention is schematically shown. Figure 1 As shown, in some embodiments, the task process construction and driving device 100 may include a process link creation module 110, a process template configuration module 120, a process driving module 130, a process status monitoring module 140 and a data sharing unit module 150.

[0032] The process link creation module 110 can be used to provide the creation function of different types of process links. The process link creation module at least includes a custom link creation submodule 111, and the process link at least includes a custom link, wherein the custom link creation submodule 111 processes the custom business logic by creating a custom link.

[0033] The process template configuration module 120 can be used to combine the created process links into a process template in the process canvas according to specific logic.

[0034] The process driving module 130 can be used to create a process instance according to the process template and the parameters and data of the task to be processed, and drive the process links in the process instance to execute the task process;

[0035] The process status monitoring module 140 can be used to monitor and visualize the execution status of the process instance based on the execution data and execution status of the process link.

[0036] The data sharing unit module 150 may include a data storage management submodule 151 . The data sharing unit module 150 is used to store and manage all data generated by process links in the execution of task processes, and to enable data sharing between process links through the data storage management submodule 151 .

[0037] The task process construction and driving device provided in the embodiment of the present invention has the function of creating different types of process links. By creating process links such as custom links and custom scripts to process custom business logic, the device can process non-formatted forms and implement complex business logic. All data generated by the process links are managed through the data sharing unit module, and data sharing is achieved between each process link through this module, that is, each process link is independent of each other but shares data, which can completely decouple the managed business system and realize data and information interaction between business systems as tasks are executed, thereby improving the stability and reliability of the overall business operation. In addition, the task process monitoring module can also monitor the link status information during the operation of the task process instance for visual display.

[0038] The following combination Figures 2 to 6 The above task flow construction and driving device 100 are further described. Figure 2 The following schematically shows a task flow chart for constructing and driving a device according to some embodiments of the present invention. Figure 3 The state transition path diagram of the process links of different link types according to some embodiments of the present invention is schematically shown. Figure 4 The following schematically shows a process template for a satellite to perform a task according to some embodiments of the present invention. Figure 5 The flowchart schematically shows the process of driving the execution task according to some embodiments of the present invention. Figure 6 Schematically shows Figure 4 The task flow corresponding to the process template shown.

[0039] like Figure 1 and Figure 2 As shown, in some embodiments, the process link creation module 110, the process template configuration module 120, the process driving module 130, and the process status monitoring module 140 can be used to execute steps S210 to S240 respectively.

[0040] In step S210, the process link creation module 110 may first select different types of process links according to the business field. Figure 3As shown in (a), general process links can be regarded as finite state machines (FSM), and there are four states: not started, waiting for execution conditions, executing, and execution completed. Different types of process links mainly refer to the differences in turntable conversion. In this embodiment, the process link creation module 110 includes at least a custom link creation submodule 111, and the process link includes at least a custom link, wherein the custom link creation submodule 111 processes custom business logic by creating a custom link. In some embodiments, the process link creation module 110 may also include an interface link creation submodule 112 and / or a file link creation submodule 113, wherein the interface link creation submodule 112 is used to create an interface link, and the file link creation submodule 113 is used to create a file link.

[0041] Interface link: This link is usually simple and usually only involves data transmission and basic business logic processing. In the interface link, there is usually a clear input and output, and these interfaces are often predictable, that is, once the interface is defined, it can be determined what results will be produced by calling the interface. The state transfer path can be as follows: Figure 3 As shown in (b): After receiving the start instruction, the business unit is notified to execute and enter the executing state. After the business unit completes the execution, the interface link is notified to the execution completion state.

[0042] File link: focuses on monitoring file or directory changes. This link is characterized by being able to monitor file changes in a specified directory in real time, including file creation, deletion, modification, and other operations, and execute corresponding business logic accordingly. File link is usually used in scenarios that need to respond to file system changes, such as automatic backup, logging, etc. The state transfer path can be as follows: Figure 3 As shown in (c): After receiving the start instruction, it enters the waiting execution condition state and monitors the file changes in a certain directory; after the file changes in the directory, it notifies the business unit corresponding to the link to execute and enter the executing state. After the business unit is executed, it notifies the interface link to enter the execution completion state.

[0043] The above interface link or file link is mainly used to process formatted forms, but it is difficult to process some complex, non-formatted businesses. Therefore, this embodiment innovatively proposes a custom link to process custom business logic through custom scripts to support the processing of complex businesses. In other words, the task flow construction and driving device 100 has the ability to process complex business logic such as custom business logic.

[0044] In some embodiments, custom business logic can be processed through custom groovy scripts. Groovy is a dynamic language that allows classes, methods, and properties to be created at runtime, which can provide great flexibility for processing complex and dynamically changing business logic. Groovy integrates a large number of application programming interfaces (APIs) and libraries, and can seamlessly access all resources on the Java platform, including standard class libraries and third-party libraries. In short, the dynamism, flexibility, powerful API support, concise syntax, and type inference capabilities of groovy scripts enable it to handle the complex business logic of the present invention, and can effectively improve development efficiency and code quality. The state transition path of the custom link using a custom groovy script can be as follows: Figure 3 As shown in (d): After receiving the start instruction, it enters the waiting execution condition state and starts to execute the groovy script to process the custom business logic. The groovy script notifies the business unit to start execution, and the link enters the executing state; after the business unit is executed, the interface link is notified to enter the execution completion state.

[0045] In some embodiments, the process link creation module 110 can also be used to set the attributes of the process link, wherein the custom link, interface link and file link have different attributes. For example, the attributes of the process link can be divided into common attributes and unique attributes. Common attributes refer to the attributes that all process links generally have, and the common attributes include but are not limited to: name, description, unique identifier, icon, associated business unit ID, the maximum execution time of the process link, etc. Unique attributes refer to the attributes unique to the process links of different link types, which are related to the business logic executed by the process link. The custom link, interface link and file link have different attributes mainly referring to the difference in unique attributes. For example, the unique attribute of the interface link can be the URL for setting the driving business module, the unique attribute of the file link can be the monitored file directory path and the business script for driving the corresponding business module after the file changes, and the unique attribute of the custom link can be a custom business script. Then, the attributes of the set process link can be stored in the data storage management submodule 151. Specifically, it can be stored in the database of the data storage management submodule 151.

[0046] Please continue reading Figure 1In some embodiments, the data storage management submodule 151 may include a non-relational database and a standard data storage interface, and the data sharing unit module 150 also includes a data access submodule 152. The data access submodule 152 includes a standard data access interface. Through non-relational data, standard data access interface and data storage interface, data can be shared between various process links. A non-relational database (NoSQL) is a database management system different from a traditional relational database (RDBMS). NoSQL does not follow a fixed table structure and can adapt to the processing of large amounts of data, high concurrency and distributed deployment requirements.

[0047] In some embodiments, the non-relational database can be a key-value storage structure, that is, data is stored in the form of key-value pairs. In this storage structure, each data item has a unique key, which is used to uniquely identify the data item and is associated with a value. The key is usually a string, and the value can be any data type, such as a string, a number, a list, a set, etc. The characteristics of key-value storage include a simple data model, high performance, mode freedom, and distributed friendliness, which is suitable for fast search, insertion, and deletion operations. The following text will further illustrate it with examples. In other words, based on the storage of the key-value structure and the standard data access interface and data storage interface, data sharing between various process links is achieved through this module. At the same time, it also enables the present invention to handle large-scale, diverse data and application scenarios that require high scalability.

[0048] Please continue reading Figure 1 , Figure 2 After creating the process link in step S210, step S220 can be executed, that is, creating a process template file through the process template configuration module 120. The process template configuration module 120 is mainly used to realize the virtualization of the business process, and to create a process template file by selecting and dragging the corresponding process link to the process canvas to combine and form the corresponding process.

[0049] In step S210, the process link creation module 110 may first create a set of multiple process links according to business needs, denoted as Q={T1, T2…, T n}, where T represents a created process link, which can be a custom link, interface link or file link. Then create a process template, denoted as S, and set management attributes for the process template S. The management attributes include but are not limited to: name, description, unique identifier, icon, etc. Next, for any link T in the set Q i (from 1 to n), obtain the set of dependent links according to the business process , ,in is an element in Q, is a subset of Q. Visual configuration T i and Dependencies . Configure the category of the dependency, i.e. strong dependency or weak dependency. Strong dependency means that the relying party needs to wait for the relied party to become a completed state before execution, and weak dependency means that the relying party needs to wait for the relied party to become an executing state before execution. The dependencies of all links constitute a dependency set R. Next, the attributes of the template S, the included link set Q, and the dependency set R are stored in the non-relational database of the data storage management submodule 151.

[0050] like Figure 4 As shown in the figure, the process of creating the above process template is applied to the example of satellite mission execution, that is, the set of process links in the example is determined = {satellite shooting demand link, satellite mission planning link, plan control instruction generation link, payload control instruction link, data reception link, data processing link, data product distribution to consumer 1 link, data product distribution to consumer 2 link}, and the dependency relationship of the process links is represented by arrows. It should be noted that Figure 4 This is only an example to facilitate a better understanding of the technical content of the present invention and does not constitute a limitation of the present invention.

[0051] Then, step S230 may be executed, that is, the process template is instantiated through the process driving module 130, and the task process is driven to execute. Figure 1 and Figure 2 In some embodiments, the process driving module 130 may include a process instantiation submodule 131 and a process driving engine submodule 132, wherein the process instantiation submodule 131 is used to call the process initiation interface, pass in the process template number and the initialization business parameters and data of the task to be processed to create a corresponding process instance, and the process driving engine submodule 132 is used to execute the task process according to the operation logic of the process template during the operation of the process instance.

[0052] Use the process template created in step S220. Figure 2 and Figure 5 In step S230, a task flow Task can be created based on the template. S , configure the properties of the task flow, including but not limited to name, description, unique identifier wait.

[0053] Next, let the process link set Q of process template S = {T1, T2…, T n}Corresponding task flow Task S An example of a link is , the corresponding process link status set The value of is one of the states of the state machine corresponding to this process link.

[0054] Similarly, T i A collection of strongly dependent links , the corresponding link instance is , the corresponding link state set .akin, The value of is one of the states of the state machine corresponding to this process link.

[0055] like Figure 5 As shown, Task S Initialization or F(P Q ) becomes completed, triggering the following process (the contents of steps 1 to 4), thereby driving the task:

[0056] Step 1, from P Q Get link instance To execute, the instance of this link must meet the following conditions:

[0057] 1. Not started yet;

[0058] 2. The link strongly depends on the link instance state set The value of is Completed.

[0059] Step 2: Run according to the configuration according to the different instance types of the link.

[0060] For example, for the interface link: immediately notify the business unit to execute and enter the executing state.

[0061] For the file link: enter the waiting execution condition state and monitor the file changes in a certain directory. After the file in the directory changes, execute the business logic, notify the business unit corresponding to the link to execute, and enter the executing state.

[0062] For a custom link: it enters the waiting for execution condition state and starts to execute a custom script (such as a groovy script). The custom script notifies the business unit to start execution, and the link enters the executing state.

[0063] Step 3: The corresponding business unit is executed and the notification link is set to the completed status.

[0064] Step 4: Set the process link instance set P Q Using the data storage unit module 150 in P Q Internal shared data.

[0065] Now let's take the key-value storage structure as an example to illustrate the data access process between process links.

[0066] The steps to set the key are as follows: 1. , get the data storage unit; 2. Call the write API of the storage unit and set key and value as parameters; 3. The data storage unit saves the key and value key-value pairs in the database.

[0067] The steps to read the key are as follows: 1. , get the data storage unit; 2. Call the read API of the storage unit module and set key as the parameter; 3. The data storage unit reads the value corresponding to the key from the database and returns it to .

[0068] Please continue reading Figure 1 and Figure 2 In some embodiments, the process driving module 130 may also include a process adjustment submodule 133, which is used to adjust the number of process links and / or the dependencies between process links during the process link execution of the task process; the process driving engine submodule 132 is also used to set and debug the adjusted process links, re-drive and execute the adjusted task process. In some embodiments, the process adjustment submodule 133 can be used to execute step S231, that is, to support flexible online adjustment of business processes. In other words, the created task process supports modification, including but not limited to: supporting the addition of new process links, modifying the logic of existing process links, and adjusting the dependencies between links. Based on this, the present invention innovatively proposes that as business needs change, the process template that has been put online may need to be modified to support the addition of new links, modification of the logic of existing links, or adjustment of the relationship between links. The modified template needs to be re-pre-debugged to ensure that the modified process can still run correctly.

[0069] Specifically, in step S231, a new task flow may be set as follows: Then, refer to the above steps to build a process link set, create a new link set and merge it with the existing links to form an adjusted process link set Next, create a new link dependency for the adjusted process link set, and record the adjusted dependency as R'. Next, reset the original task flow The status of all link instances in the Completed before task flow adjustment, but middle, The dependent link is in an unfinished state, adjust The task flow is unfinished and the shared data set is revoked. The corresponding template S' and link set T' are stored in the database. Finally, refer to Figure 5 The process shown drives the execution of the task process .

[0070] Continue to execute step S230, such as the instance state set All elements are completed, marking the task process as completed.

[0071] The above step S230 is further explained using the example of a satellite performing a task. Figure 6 As shown in the figure, the mission flow of the satellite performing the photography mission is described:

[0072] 1. When the mission starts, the satellite shooting requirement link notifies the shooting requirement module to start execution. After the module is executed, the satellite shooting requirement link is notified to be completed. 2. Since the status of all links that the satellite mission planning link depends on are completed, the satellite mission planning link notifies the mission planning module to start execution. After the module is executed, the satellite mission planning link is notified to be completed. 3. Other links are similar. After the status of the link they depend on becomes completed, the relevant business modules are notified to execute. 4. Finally, the status of all links is completed, and the task process is marked as completed.

[0073] Please continue reading Figure 1 During the execution of the task process, the process status monitoring module 140 can monitor and visualize the execution status of the process instance. The process status monitoring module 140 can include a process monitoring submodule 141 and a process visualization submodule 142, wherein the process monitoring submodule 141 is used to monitor the execution time of the process link and send an alarm message when the execution time exceeds the preset time; the process visualization submodule 142 is used to visualize the execution status of the process instance during the monitoring process. Figure 2 As shown, in some embodiments, the process status monitoring module 140 can be used to execute step S240.

[0074] In step S240, monitor the task flow Specifically, the process monitoring submodule 141 can be used in the process link instance After entering the execution state, the longest execution time of the link is monitored. If the execution is not completed within the specified time, an alarm notification is issued. The alarm notification can be in the form of a pop-up message, email, text message, etc., which is not specifically limited in the present invention. The process visualization submodule 142 visualizes the task process Status can include the following two aspects: any link instance A visual display of the link instances it depends on; and / or a link instance state set F(P Q ) visual display.

[0075] Based on the above multiple embodiments, the task process construction and driving device provided by the present invention includes a data sharing unit module, a process link creation module, a process template configuration module, a process driving module, and a process status monitoring module. All data generated by the process link are managed through the data sharing unit module, and data sharing is realized between each process link through this module; custom links, interface links, file links and other process links are created through the process link creation module, and complex business logic codes are edited through custom groovy scripts; the process links are spliced ​​into process templates according to the business operation logic through the process template configuration module; the process initiation interface is called through the process driving module to instantiate the task process instance and automatically call the process links in the process according to the execution order; the link status information of the task process instance during operation is monitored through the process status monitoring module. The task process construction and driving device provided by the present invention solves the problem that the various business systems managed in the prior art cannot be completely decoupled, and realizes the purpose of data interaction and information interaction between business systems as tasks are executed.

[0076] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the apparatus and method according to various embodiments of the present invention. In this regard, each box in the flowchart or block diagram may represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box may also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions. It will be appreciated by those skilled in the art that the features recorded in the present invention can be combined and / or combined in a variety of ways, even if such a combination or combination is not explicitly recorded in the present invention.

[0077] The embodiments of the present invention are described above. However, these embodiments are only for the purpose of illustration, and are not intended to limit the scope of the present invention. Although each embodiment is described above, it does not mean that the measures in each embodiment cannot be used in combination advantageously. Without departing from the scope of the present invention, those skilled in the art may make various substitutions and modifications, which should all fall within the scope of the present invention.

Claims

1. A task process construction and driving device, characterized in that: include: A process link creation module, configured to provide a creation function for different types of process links, wherein the process link creation module includes at least a custom link creation submodule, wherein the custom link creation submodule processes custom business logic by creating the custom link; The process template configuration module is used to combine the created process links into a process template based on specific logic in the process canvas, and define the dependency relationship between the process links; A process driving module is used to create a process instance based on the process template and the parameters and data of the task to be processed, and drive the process links in the process instance to execute the task process; A process status monitoring module, configured to monitor and visualize the execution status of the process instance based on the execution data and execution status of the process link; and The data sharing unit module includes a data storage management submodule, which is used to store and manage the data generated by the process links in executing the task process, and enable data sharing between the process links through the data storage management submodule.

2. The task process construction and driving device according to claim 1, characterized in that: The process link creation module also includes: The interface link creation submodule is used to create the interface link; And / or, a file link creation submodule is used to create a file link.

3. The task process construction and driving device according to claim 2, characterized in that: The process link creation module is further used to set the attributes of the process link and store the attributes of the process link in the data storage management submodule; Among them, the custom link, the interface link and the file link have different attributes.

4. The task process construction and driving device according to any one of claims 1 to 3, characterized in that: The custom link processes the custom business logic through a custom Groovy script.

5. The task process construction and driving device according to claim 1, characterized in that: The process template configuration module includes a process template creation submodule and a process template management submodule. Among them, the process template creation submodule is used to create the process template in the process canvas, the process template management submodule is used to set the properties of the process template and define the strong and weak dependencies between the process links, and store the properties and strong and weak dependencies of the process template in the data storage management submodule.

6. The task process construction and driving device according to claim 1, characterized in that: The process driving module includes a process instantiation submodule and a process driving engine submodule. The process instantiation submodule is used to call the process initiation interface, pass in the process template number and the initialization business parameters and data of the task to be processed to create a corresponding process instance. The process driving engine submodule is used to execute the task process according to the operation logic of the process template during the operation of the process instance.

7. The task process construction and driving device according to claim 6, characterized in that: The process driving module further includes a process adjusting submodule for adjusting the number of the process links and / or the dependency relationship between the process links during the process of executing the task process in the process links; The process driving engine submodule is also used to set and debug the adjusted process links, and re-drive and execute the adjusted task process.

8. The task process construction and driving device according to claim 1, characterized in that: The process status monitoring module includes a process monitoring submodule and a process visualization submodule. The process monitoring submodule is used to monitor the execution time of the process link and send an alarm message when the execution time exceeds a preset time; The process visualization submodule is used to visually display the execution status of the process instance during the monitoring process.

9. The task process construction and driving device according to claim 1, characterized in that: The data storage management submodule includes a non-relational database and a standard data storage interface, and the data sharing unit module also includes a data access submodule, and the data access submodule includes a standard data access interface; Among them, data is shared between the process links through the non-relational database, standard data access interface and data storage interface.

10. The task process construction and driving device according to claim 9, characterized in that: The non-relational database includes a key-value storage structure.

Images