CN116009938A - Dynamically configurable flow item pushing method and system for flow engine - Google Patents

Abstract

The invention provides a method and a system for pushing flow events which act on a flow engine and can be dynamically configured, wherein the method comprises the following steps: integrating a process item pushing system into a process engine to provide service; when asynchronous pushing is performed, channel management to be pushed is put into a pushing queue for storage; managing a push channel list; assembling and pushing data to a target channel; the configuration data is persisted to adapt the database. The invention acts the pushing related logic in the flow engine in a systematic way and provides a configuration entry, and an enterprise developer completes data pushing by configuring and selecting one or more different pushing strategies so as to replace code writing, solve the problem that different protocols need to develop different codes and multiple channels to develop multiple sets of codes, and reduce repeated development work.

Description

Dynamically configurable flow item pushing method and system for flow engine

Technical Field

The present invention relates to the technical field of flow engines, and in particular, to a method and a system for pushing dynamically configurable flow events acting on a flow engine.

Background

In the development process of enterprise-level application systems, as the business is continuously complex, a process engine is often required to be introduced to complete various complex applications and approval businesses. The flow engine generates various channel management in the flow circulation process, and the channel management is generated along with the flow and also dies along with the flow, so that the flow engine is not only an entrance for processing the flow, but also an important reminding information for guiding a user to process the flow.

Patent document CN104281906a discloses a process engine implementation method and a process engine system in a business process, including: s1, constructing a graphical flow node; s2, designing a flow chart, connecting flow nodes with guide lines with conditions and directions according to service requirements to form the service flow chart; s3, storing and releasing the designed flow chart to a flow engine; s4, the flow engine automatically transfers the task flow to the corresponding node according to the operation of the service system.

However, in order to split and refine various complex services, a large enterprise usually adopts a scheme of developing and deploying multiple application systems, and in order to avoid frequent switching between systems, each system channel management is usually pushed to a unified portal for processing by the user.

The problem is that different enterprise push protocols are different, such as push OA office system (WebService protocol), push enterprise message software (MQ protocol), push WeChat public number (HTTP protocol), etc., even some enterprises push channel management to multiple channels, each flow system will develop a set of codes for each channel, and the codes cannot be universal.

Disclosure of Invention

In view of the drawbacks of the prior art, an object of the present invention is to provide a method and system for dynamically configurable flow item pushing for a flow engine.

The invention provides a dynamically configurable flow item pushing system acting on a flow engine, which comprises:

the process engine adaptation module: integrating a process item pushing system into a process engine to provide service;

push queue module: when asynchronous pushing is performed, channel management to be pushed is put into a pushing queue for storage;

channel management module: managing a push channel list;

and the pushing module is used for: assembling and pushing data to a target channel;

and a data source adapting module: the configuration data is persisted to adapt the database.

Preferably, the system further comprises a configuration module;

the configuration module comprises a configuration page integration module and a configuration API module;

the configuration page integration module integrates the page of the application into a web application framework, and provides services with the application at the same time;

the configuration API provides a programmatic configuration scheme for applications without pages.

Preferably, the pushing module comprises a message parser and a pushing thread pool; the message parser converts the channel management data into a push message; the pushing thread pool runs the pushing threads; the pushing module regularly checks whether data need to be pushed in a pushing queue, and when the data need to be pushed is detected, all pushing channels are read from the channel management module, wherein the pushing channels are used as downstream system adapters to encapsulate logic of pushing downstream systems, if no pushing channels exist, pushing threads are started to conduct pushing processing, in the pushing threads, pushing data are firstly analyzed into message formats needed by corresponding channels, and then the data are pushed into the downstream systems through pushing logic of executing channels.

Preferably, a plurality of agreements are encapsulated in the channel management module, and the agreements are designated when the channels are configured by the configuration module, and the number of push channel lists created by the channel management module is determined according to the number of the configured channels.

Preferably, the flow engine adapter module realizes the triggering of the flow engine through the trigger of the flow engine, and presets various adaptation schemes to match the use modes of different flow engine triggers; for the flow engine without trigger function, the flow engine adapter module triggers by burying the point.

Preferably, the message parser is a character string template parser, parses and outputs channel management according to a designated template, and supports multiple message parsing; the push thread pool is used for executing push tasks, and the size of the thread pool is specified through configuration. The configuration process comprises the following steps:

integrating a configuration module with an application to provide access to a configuration page; accessing a configuration page address, adding a pushing channel, and setting pushing agreements of the channel, the channel address and information of a message template; the method for integrating the configuration module and the application comprises the following steps: directly registering the page of the configuration module into the application; calling a configuration module API, and developing a customized page program in an application system; the pushing channel is a list, allows the list to be added, deleted and modified and takes effect in real time; each channel is configured with a push protocol, and different configuration information is set according to different protocols;

configuring the size of a thread pool, and configuring the number of threads for executing push tasks simultaneously;

and (3) performing configuration persistence, namely performing data persistence through calling the data source adaptation block, and enabling the push queue to be a persistent data queue.

Preferably, according to the configuration information of the push channel, a corresponding message parser is called to convert the channel management taken out from the push channel list into a message format under the configuration strategy, and push protocol logic under the strategy is executed.

The flow item pushing method based on the dynamically configurable flow item pushing system acting on the flow engine provided by the invention comprises the following steps:

step S1: integrating the process item pushing system into a process engine through a process engine adapter module;

step S2: initiating a new flow through a flow engine, giving the new flow to an auditor for auditing, and sending channel management for the auditor by the flow engine after the flow engine is checked to be successful in initiating the flow;

step S3: the method comprises the steps that generation of new channel management is perceived through a trigger of a flow engine, and the channel management is put into a push queue maintained by a push queue module;

step S4: detecting that a pushing queue has a pushing task, starting a thread to execute step S5;

step S5: calling a channel management module to acquire a push channel list;

step S6: taking out a channel management in the push queue;

step S7: traversing the pushing channel list generated in the step S5, calling a corresponding message analyzer according to configuration information of the pushing channels, converting the channel management extracted in the step S6 into a message format of the quota of the configuration strategy, and executing pushing protocol logic under the strategy;

step S8: the pushing is completed and the log is recorded.

According to the invention, a computer readable storage medium is provided, in which a computer program is stored, the computer program, when being executed by a processor, implements the steps of the procedure item pushing method.

The electronic equipment provided by the invention comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the computer program realizes the steps of the process item pushing method when being executed by the processor.

Compared with the prior art, the invention has the following beneficial effects:

1. the invention provides a configuration type pushing scheme, which comprises the steps of writing a flow engine device, packaging pushing protocols as many as possible, hiding pushing implementation details, and enabling enterprise developers to complete data pushing by configuring and selecting one or more different pushing strategies so as to replace code writing, thereby solving the problems that different protocols need to develop different codes and multiple channels develop multiple sets of codes.

2. The invention applies the pushing related logic to the flow engine in a systematic way, encapsulates and embeds the pushing logic to provide a set of general pushing components and provides a configuration entry, and a developer can complete pushing work of flow channel management only by a small amount of configuration, thereby reducing repeated development work.

3. The invention is based on dynamic configuration technology, can change the pushing strategy at any time, and is friendly to the operation of business personnel.

Drawings

Other features, objects and advantages of the present invention will become more apparent upon reading of the detailed description of non-limiting embodiments, given with reference to the accompanying drawings in which:

fig. 1 is a schematic diagram of the flow steps of the flow item pushing method provided by the present invention.

FIG. 2 is a schematic block diagram of the present invention showing the basic components and upstream-downstream relationship of the present invention.

FIG. 3 is a sequence diagram of a flow engine pushing a flow item to a queue, illustrating the entire flow from the flow engine generating the flow item to persistence to the push queue.

FIG. 4 is a sequence diagram of a push module pushing push queue data to a third party system, illustrating the push module pushing the data from the push queue to a downstream system.

FIG. 5 is a channel management interface of the configuration module, which can add, modify and delete channels and take effect in real time.

FIG. 6 is a channel configuration interface, with parameters that may be configured being different depending on the protocol chosen.

The database configuration interface of fig. 7 may select different data source types.

FIG. 8 illustrates other configuration items such as thread pool size, empty queue detection time interval, etc.

Detailed Description

The present invention will be described in detail with reference to specific examples. The following examples will assist those skilled in the art in further understanding the present invention, but are not intended to limit the invention in any way. It should be noted that variations and modifications could be made by those skilled in the art without departing from the inventive concept. These are all within the scope of the present invention.

The invention relates to a channel management pushing method capable of being dynamically configured, which is characterized in that implementation details are hidden by packaging bottom pushing logic, so that a developer does not need to care how to write pushing codes, a pushing effect can be realized by carrying out configuration management on pushing, the development workload of a system is greatly reduced, and the developer can put the center of gravity on service implementation. The integration of multiple protocols enables the system to quickly respond to the change of service demands, and the problem of pushing and pushing in places can be solved only through one management interface, so that the hands of a developer are liberated, and the digital transformation of an enterprise is assisted. The invention takes the event of the flow engine, trigger devices such as a trigger source, acquires newly generated flow matters through the trigger source, persists the flow matters into a queue for pushing, and the detection thread scans data in the queue at regular time, and the pushing thread invokes the pushing logic of the pushing channel to push the data to a downstream system.

The invention provides a dynamically configurable process item pushing system acting on a process engine, comprising: the system comprises a flow engine adaptation module, a push queue module, a channel management module, a configuration module, a push module and a data source adaptation module. The flow engine adaptation module is used for integrating various flow engines, the push queue module is used for persistence push data, the configuration module is used for configuring push parameters, the channel management module is used for adding and deleting channel information, the push module is used for detecting and executing push tasks, and the data source adaptation module is used for integrating various types of databases.

The process engine adapting module can be easily integrated into various existing process engines to provide services; as shown in fig. 2, after the push system integrates the flow engine, when the flow engine processes the flow, the flow engine transmits the generated flow item information to the push system, and the push system is used as a push plug-in, and through mutual cooperation among the modules, data is pushed to each downstream system finally. The process engine adaptation module realizes the perception of new process matters through events or triggers of each process engine; for example, the integration is realized by integrating jar package + configuration or Sprint Boot Starter mode, the specific integration process is realized by the inside of the device, and a user does not need to care how the device is realized, and only needs to carry out a small amount of configuration.

The pushing queue module is used for storing channel management to be pushed when asynchronous pushing is performed, realizing lasting pushing data through a database, and ensuring that the pushing data is not lost through database transactions; the configuration module carries out related configuration of the pushing system through a background management page, can manage related information of pushing channels, such as inquiring to add modification channels and delete channels, and can also configure global parameters, and all modifications take effect. The push module realizes detection and push through one detection thread and a plurality of push threads, the detection stage only needs to start the detection thread to regularly scan whether new matters need to be pushed or not in the queue, if no new matters exist, the detection is delayed for a period of time and then scanning is performed (the specific delay time configuration module is used for configuration), if the new matters exist, the push thread is started (the specific thread number is configured by the configuration module) to sequentially push the matters in the queue to a downstream system, and besides the delay brought by an instruction or a database, no delay time exists in the middle of the push process.

The channel management module is used for managing the push channel list; the channel management module is packaged with various agreements, such as HTTP, RPC, webService, ESB, and the agreements can be appointed when channels are configured through the configuration module, and the channel management module is mainly used for creating push channel lists, wherein the number of the lists is determined according to the number of the configured channels; as shown in FIG. 5, the channel management interface provided by the channel management module displays information such as channel names, channel agreements, channel states and the like, a plurality of channels can be added, and the channels can be modified and deleted. When clicking the add button, the display interface is shown in fig. 6, the channel name needs to be filled in, the push protocol is selected, and different protocols have different filling contents, such as the http+json protocol needs to fill in the information of request address, timeout time, retry times, token refresh, request header and message template, wherein the request address fills in the downstream system interface address; the request header may be used to send specified header information, such as interface authorization information, etc.; the message template can be filled in a character template in a JSON format, and EL expression analysis item data is supported, such as { "id": $ { id }. The saved page jumps to the list page of fig. 5. Clicking the modify button, the page will be presented again to fig. 6, and the information filled in before the page backfills, can be modified and saved. Clicking the delete button, deleting the channel after the second confirmation, and pushing the channel can not be performed any more. More specifically, the channel management module provides APIs for the configuration module and the push queue module, the specific implementation is completed by the channel management module, and the configuration module and the push queue module which are called by an upper layer only need to call the related APIs of the channel management module.

The configuration module comprises a configuration page integration module and a configuration API module; the configuration page integration module can integrate the page into various Web application frameworks such as Spring MVC, struts, net Web and the like, and provide services with the application at the same time, and the configuration API provides a programming configuration scheme for the application without the page;

the pushing module is used for assembling and pushing data to a target channel and is divided into a message parser and a pushing thread pool, wherein the message parser converts channel management data into pushing messages, and the pushing thread pool runs pushing threads; in a preferred embodiment, as shown in fig. 4, the push module periodically checks whether there is data in the push queue to be pushed, and when it is detected that there is data to be pushed, reads all push channels from the channel management module, where the channels can be regarded as downstream system adapters, and is used to encapsulate logic of pushing downstream systems, such as push protocols, push addresses, push message formats, etc., if there is no push channel, the push process is not executed, otherwise, a push thread is started to perform push processing, in the push thread, the push data is first parsed into the message format required by the corresponding channel, and then the data is pushed to the downstream system by executing the push logic of the channel.

The data source adaptation module is used for persisting configuration data and can adapt to databases such as REDIS, MYSQL, ORACLE, SQLITE. The present invention requires database support and therefore requires data source configuration, as shown in FIG. 7, requiring selection of the database type, database url, database user name and password. The data source adapter module completes database connection through configuration, and the pushing system is internally provided with various data source connection adaptation logics, so that the data source configuration of the main stream can be completed through configuration. The push system also opens a custom adapter interface to allow developers to customize the adapter. The relevant configuration of the adapter is configured by the configuration module.

As shown in fig. 5, the process engine generates a process item, the process engine may be activity, flowable, camunda, jbpm, and the event function of the process engine may capture process item data when the item is generated, and transfer the data into the push system through the interface of the process engine adapting module, where the push system temporarily stores the data into the push queue for storage, the push queue stores the data based on the database, and the data may be stored into any type of data source through the data source adapting module, where the data may be permanently stored until the consumption is completed.

The invention can configure some global parameters, such as the size of the push thread pool, the empty queue detection time interval and the like. The push thread pool defaults to 2 threads and can be configured according to the machine configuration condition. The empty queue detection time interval is used for configuring how long the push module sleeps to detect data once more when the queue is empty, and the sleep is not performed when the queue is not empty.

The invention provides a dynamically configurable process item pushing method acting on a process engine, which comprises the following steps:

step S1: integrating a dynamically configurable process item pushing system acting on a process engine into the process engine through a process engine adapter module;

step S2: initiating a new process, such as a leave application process about Zhang III, by a process engine, giving the process to a project manager for verification, and after the process is initiated successfully, sending channel management for the project manager by the process engine;

step S3: the new channel management is perceived to be generated through a trigger of the flow engine and the like, and the channel management is put into a push queue maintained by a push queue module;

step S4: detecting that a pushing queue has a pushing task, starting a thread to execute step S5;

step S5: calling a channel management module to acquire a push channel list;

step S6: taking out a channel management in the push queue;

step S7: traversing the pushing channel list generated in the step S5, calling a corresponding message analyzer according to configuration information of the pushing channels, converting channel management extracted in the step S6 into a message format under the configuration strategy, and executing pushing protocol logic under the strategy;

step S8: finishing pushing and recording logs;

the process engine adapter module in step S1 is implemented by the process engine triggers, and different process engine triggers are used in different manners, so that multiple adapting schemes are preset to adapt to almost all the process engines in the market. For the flow engine without trigger function, triggering is performed by a buried point mode.

The push queue in step S3 is a persistent data queue, and data persistence is performed by default through the data source adaptation module, or may be modified into MQ through configuration.

The push module in the step S4 is provided with a message parser and a push thread pool, wherein the message parser is a character string template parser, can parse and output channel management according to a specified template, and can support multiple message parsing, such as JSON, XML and the like; the push thread pool is used to perform push tasks, and the thread pool size may be specified by configuration.

The following is a configuration procedure:

step A: integrating a configuration module with the application to access a configuration page;

and (B) step (B): accessing a configuration page address;

step C: adding a pushing channel, and setting information such as pushing agreements, channel addresses, message templates and the like of the channel;

step D: configuring the size of a thread pool;

step E: configuration persistence;

in the step a, the configuration module is integrated with the application in two ways, one is to directly register the page of the configuration module into the application, for example, register in the ways of Servlet, spring Controller and the like; the other is to call the configuration module API, and the method can be adopted when the customized page program is developed in the application system, such as integration in a desktop application or when the application system has particularly high requirement on page customization.

In the step B, the pushing channel is a list, and the list can be added, deleted and modified and is effective in real time. Each channel can be configured with a push protocol, and different protocols have different configuration information, for example, the http+json protocol contains URL addresses, HTTP header information, JSON messages Wen Moban, and the like, and for example, the webservice+xml protocol contains URL addresses, password information, XML templates, and the like. In summary, different configuration information may be set according to different protocols.

C, configuring the size of a thread pool, and configuring the number of threads for simultaneously executing push tasks, wherein 2 threads are defaulted;

the persistence in step D is performed by calling a data source module, which also needs to be configured, for example, as MYSQL, ORACLE, etc., and may also be configured as an application public data source.

Those skilled in the art will appreciate that the systems, apparatus, and their respective modules provided herein may be implemented entirely by logic programming of method steps such that the systems, apparatus, and their respective modules are implemented as logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc., in addition to the systems, apparatus, and their respective modules being implemented as pure computer readable program code. Therefore, the system, the apparatus, and the respective modules thereof provided by the present invention may be regarded as one hardware component, and the modules included therein for implementing various programs may also be regarded as structures within the hardware component; modules for implementing various functions may also be regarded as being either software programs for implementing the methods or structures within hardware components.

The foregoing describes specific embodiments of the present invention. It is to be understood that the invention is not limited to the particular embodiments described above, and that various changes or modifications may be made by those skilled in the art within the scope of the appended claims without affecting the spirit of the invention. The embodiments of the present application and features in the embodiments may be combined with each other arbitrarily without conflict.

Claims (10)

1. A dynamically configurable flow item pushing system for a flow engine, comprising:

the process engine adaptation module: integrating a process item pushing system into a process engine to provide service;

push queue module: when asynchronous pushing is performed, channel management to be pushed is put into a pushing queue for storage;

channel management module: managing a push channel list;

and the pushing module is used for: assembling and pushing data to a target channel;

and a data source adapting module: the configuration data is persisted to adapt the database.

2. The dynamically configurable flow item pushing system for a flow engine of claim 1, further comprising a configuration module;

the configuration module comprises a configuration page integration module and a configuration API module;

the configuration page integration module integrates the page of the application into a web application framework, and provides services with the application at the same time;

the configuration API provides a programmatic configuration scheme for applications without pages.

3. The dynamically configurable flow item pushing system for a flow engine of claim 1, wherein the pushing module comprises a message parser, a push thread pool; the message parser converts the channel management data into a push message; the pushing thread pool runs the pushing threads; the pushing module regularly checks whether data need to be pushed in a pushing queue, and when the data need to be pushed is detected, all pushing channels are read from the channel management module, wherein the pushing channels are used as downstream system adapters to encapsulate logic of pushing downstream systems, if no pushing channels exist, pushing threads are started to conduct pushing processing, in the pushing threads, pushing data are firstly analyzed into message formats needed by corresponding channels, and then the data are pushed into the downstream systems through pushing logic of executing channels.

4. The dynamically configurable flow item pushing system for a flow engine of claim 2 wherein a plurality of agreements are encapsulated in the channel management module, the agreements being specified when channels are configured by the configuration module, the number of pushed channel lists created by the channel management module being determined based on the number of channels configured.

5. The dynamically configurable flow transaction pushing system for a flow engine of claim 1, wherein the flow engine adapter module triggers the flow engine by a trigger of the flow engine, the flow engine adapter module presets a plurality of adaptation schemes to match usage patterns of different flow engine triggers; for the flow engine without trigger function, the flow engine adapter module triggers by burying the point.

6. The dynamically configurable flow item pushing system acting on a flow engine of claim 3, wherein the message parser is a string template parser, parses and outputs channel management according to a specified template, and supports multiple message parsing; the push thread pool is used for executing push tasks, and the size of the thread pool is specified through configuration. The configuration process comprises the following steps:

integrating a configuration module with an application to provide access to a configuration page; accessing a configuration page address, adding a pushing channel, and setting pushing agreements of the channel, the channel address and information of a message template; the method for integrating the configuration module and the application comprises the following steps: directly registering the page of the configuration module into the application; calling a configuration module API, and developing a customized page program in an application system; the pushing channel is a list, allows the list to be added, deleted and modified and takes effect in real time; each channel is configured with a push protocol, and different configuration information is set according to different protocols;

configuring the size of a thread pool, and configuring the number of threads for executing push tasks simultaneously;

and (3) performing configuration persistence, namely performing data persistence through calling the data source adaptation block, and enabling the push queue to be a persistent data queue.

7. The dynamically configurable flow transaction pushing system for a flow engine of claim 6 wherein, based on configuration information for a push channel, a corresponding message parser is invoked to convert channel management retrieved from a push channel list into a message format under the configuration policy and to execute push protocol logic under the policy.

8. A flow item pushing method based on the dynamically configurable flow item pushing system acting on a flow engine according to any one of claims 1 to 7, characterized by comprising:

step S1: integrating the process item pushing system into a process engine through a process engine adapter module;

step S2: initiating a new flow through a flow engine, giving the new flow to an auditor for auditing, and sending channel management for the auditor by the flow engine after the flow engine is checked to be successful in initiating the flow;

step S3: the method comprises the steps that generation of new channel management is perceived through a trigger of a flow engine, and the channel management is put into a push queue maintained by a push queue module;

step S4: detecting that a pushing queue has a pushing task, starting a thread to execute step S5;

step S5: calling a channel management module to acquire a push channel list;

step S6: taking out a channel management in the push queue;

step S7: traversing the pushing channel list generated in the step S5, calling a corresponding message analyzer according to configuration information of the pushing channels, converting the channel management extracted in the step S6 into a message format of the quota of the configuration strategy, and executing pushing protocol logic under the strategy;

step S8: the pushing is completed and the log is recorded.

9. A computer readable storage medium storing a computer program, wherein the computer program when executed by a processor implements the steps of the flow item pushing method of claim 8.

10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the computer program when executed by the processor implements the steps of the flow item pushing method of claim 8.

Images