CN112488462A - Unified pushing method, device and medium for workflow data - Google Patents
Unified pushing method, device and medium for workflow data Download PDFInfo
- Publication number
- CN112488462A CN112488462A CN202011268864.3A CN202011268864A CN112488462A CN 112488462 A CN112488462 A CN 112488462A CN 202011268864 A CN202011268864 A CN 202011268864A CN 112488462 A CN112488462 A CN 112488462A
- Authority
- CN
- China
- Prior art keywords
- data
- workflow
- instance
- message middleware
- monitoring
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 59
- 230000000694 effects Effects 0.000 claims abstract description 86
- 238000012544 monitoring process Methods 0.000 claims abstract description 64
- 238000004590 computer program Methods 0.000 claims description 14
- 230000008569 process Effects 0.000 claims description 9
- 238000011084 recovery Methods 0.000 claims description 6
- 239000000725 suspension Substances 0.000 claims description 6
- 230000002159 abnormal effect Effects 0.000 claims description 5
- 238000012216 screening Methods 0.000 claims description 3
- 230000004927 fusion Effects 0.000 abstract description 5
- 238000012545 processing Methods 0.000 description 10
- 230000005540 biological transmission Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000013473 artificial intelligence Methods 0.000 description 2
- 238000004422 calculation algorithm Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/547—Messaging middleware
Abstract
The application discloses a unified pushing method, a unified pushing device and a unified pushing medium of workflow data, wherein the method comprises the following steps: pre-configuring configuration parameters required in the data monitoring process and monitoring types to be monitored; starting message middleware; starting monitoring when detecting that the current activity state of the workflow instance object is changed into a target activity state in the monitoring type, and reading data obtained by monitoring; the data is sent to the message middleware so that the recipient retrieves the data from the message middleware. Therefore, the data obtained by different workflow engines are managed in a unified mode through the function of the message middleware, the required data do not need to be called from a plurality of different databases, and the working efficiency is improved. And the message middleware can realize one-to-one and one-to-many service providing, so the method is suitable for data fusion of a plurality of different application systems. In addition, the unified pushing device and the medium for the workflow data have the same effects as the method.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a unified pushing method, an apparatus, and a medium for workflow data.
Background
In the existing informatization system of an enterprise, an own engine and a relatively mature application system exist. If the engine switching and modification are relatively difficult, different application systems adopt different development platforms and different engines, and tasks to be handled are distributed in different system platforms and are not connected with each other.
When a user processes production and operation activities, tasks to be handled need to be processed in different application systems, that is, workflow data involved in processing the tasks to be handled are stored in respective databases, and required data need to be called from different databases, so that the working efficiency is low, and unified management cannot be achieved.
Therefore, when facing a plurality of different application systems, how to improve the speed of processing the tasks to be handled and to uniformly manage the tasks is a problem to be solved urgently by those skilled in the art.
Disclosure of Invention
The application aims to provide a unified pushing method, a unified pushing device and a unified pushing medium of workflow data, which are used for improving the speed of processing tasks to be handled and realizing unified management when facing a plurality of different application systems.
In order to solve the above technical problem, the present application provides a unified pushing method for workflow data, including:
pre-configuring configuration parameters required in the data monitoring process and monitoring types to be monitored;
starting message middleware;
starting monitoring when detecting that the current activity state of the workflow instance object is changed into a target activity state in the monitoring type, and reading data obtained by monitoring;
sending the data to the message middleware so that a receiver acquires the data from the message middleware.
Preferably, the sending the data to the message middleware comprises:
screening required data from the data according to a preset requirement;
and sending the screened data to the message middleware.
Preferably, the sending the screened data to the message middleware comprises:
and encrypting the screened data and sending the encrypted data to the message middleware.
Preferably, the receiving party is a plurality of receiving parties.
Preferably, the method further comprises the following steps:
and in the case that the data of the message middleware is abnormal, sending the data to the message middleware again.
Preferably, the workflow instance object comprises a process instance and an activity instance.
Preferably, the workflow instance object is an active instance, and the listening type includes:
before the creation of an activity instance, after the creation of an activity instance, before the start of an activity instance, after the start of an activity instance, before the termination of an activity instance, after the termination of an activity instance, before the suspension of an activity instance, after the suspension of an activity instance, before the reply of an activity instance, after the reply of an activity instance, before the completion of an activity instance, before the jump of an activity instance, after the jump of an activity instance, before the rollback of an activity instance, after the rollback of an activity instance, before the release of an activity instance, after the release of an activity instance, before the recovery of an activity instance, and after the recovery of an activity instance.
In order to solve the above technical problem, the present application further provides a unified pushing device for workflow data, which includes:
the configuration module is used for pre-configuring configuration parameters required in the data monitoring process and the monitoring type to be monitored;
the starting module is used for starting message middleware;
the monitoring module is used for starting monitoring when detecting that the current activity state of the workflow instance object is changed into a target activity state in the monitoring type, and reading data obtained by monitoring;
and the sending module is used for sending the data to the message middleware so that a receiving party can acquire the data from the message middleware.
In order to solve the above technical problem, the present application further provides a unified pushing device for workflow data, including a memory for storing a computer program;
a processor for implementing the steps of the unified push method of workflow data as described when executing the computer program.
In order to solve the above technical problem, the present application further provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the unified pushing method for workflow data as described above.
The unified pushing method for the workflow data comprises the following steps: pre-configuring configuration parameters required in the data monitoring process and monitoring types to be monitored; starting message middleware; starting monitoring when detecting that the current activity state of the workflow instance object is changed into a target activity state in the monitoring type, and reading data obtained by monitoring; the data is sent to the message middleware so that the recipient retrieves the data from the message middleware. The technical scheme is applied, data obtained by different workflow engines can be managed in a unified mode through the function of the message middleware, required data do not need to be called from a plurality of different databases, and working efficiency is improved. And the message middleware can realize one-to-one and one-to-many service providing, so the method is suitable for data fusion of a plurality of different application systems.
In addition, the unified pushing device and the medium for the workflow data correspond to the method, and the effect is the same as that of the unified pushing device and the medium for the workflow data.
Drawings
In order to more clearly illustrate the embodiments of the present application, the drawings needed for the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings can be obtained by those skilled in the art without inventive effort.
Fig. 1 is a flowchart of a unified pushing method of workflow data according to an embodiment of the present application;
fig. 2 is a structural diagram of a unified pushing apparatus for workflow data according to an embodiment of the present application;
fig. 3 is a structural diagram of another unified pushing apparatus for workflow data according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without any creative effort belong to the protection scope of the present application.
The core of the application is to provide a unified pushing method, a unified pushing device and a unified pushing medium of workflow data.
In order that those skilled in the art will better understand the disclosure, the following detailed description will be given with reference to the accompanying drawings.
The unified pushing method of the workflow data can be realized by one server, the mentioned receiver can be other devices such as the server, and after the message middleware obtains the data, the receiver can read the data of the message middleware, so that the data acquisition is realized.
Fig. 1 is a flowchart of a unified pushing method of workflow data according to an embodiment of the present application. As shown in fig. 1, the method includes:
s10: the configuration parameters needed in the data monitoring process and the monitoring type to be monitored are configured in advance.
In a specific implementation, relevant configuration parameters, such as the configuration for an active node, need to be configured at the flow designer according to actual requirements. It is to be understood that the type of monitoring is not particularly limited, and may be set according to different workflow instance objects, for example, a workflow instance object is an active instance, and the type of monitoring includes: before the creation of an activity instance, after the creation of an activity instance, before the start of an activity instance, after the start of an activity instance, before the termination of an activity instance, after the termination of an activity instance, before the suspension of an activity instance, after the suspension of an activity instance, before the reply of an activity instance, after the reply of an activity instance, before the completion of an activity instance, before the jump of an activity instance, after the jump of an activity instance, before the rollback of an activity instance, after the rollback of an activity instance, before the release of an activity instance, after the release of an activity instance, before the recovery of an activity instance, and after the recovery of an activity instance.
S11: message middleware is initiated.
It should be noted that, in general, steps S10 and S11 are not sequential, and preferably, after S10, the message middleware is restarted. It will be appreciated that the workflow engine also needs to be started since the engine is necessarily needed in the process of executing the task to be handled. When the state of the workflow instance object (such as a process instance and an activity instance) is changed, the workflow engine monitors the workflow instance object and discloses an event interface before and after the change. After the workflow engine is started, the tasks to be handled are executed according to the existing flow.
The message middleware is a supporting software system based on queue and message transfer technology and used for providing asynchronous or synchronous and reliable message transmission for an application system in a network environment.
S12: and starting monitoring when the current activity state of the workflow instance object is detected to be changed into a target activity state in the monitoring type, and reading data obtained by monitoring.
In the process of executing the task to be handled, the current state of the workflow instance object changes accordingly, and if the current state is changed to the target activity state set in S10, a monitoring mechanism is triggered, and corresponding data can be acquired in the monitoring process.
S13: the data is sent to the message middleware so that the recipient retrieves the data from the message middleware.
In specific implementation, in order to facilitate receiving and rapidly acquiring useful data, a data flag may be added to the acquired data in advance, so that a receiver may rapidly find data to be acquired according to the data flag. In addition, in order to achieve security of data transmission and prevent data from being tampered, data may be encrypted, and a symmetric encryption algorithm or an asymmetric encryption algorithm is used, which is not limited in this embodiment.
The receiver may be one or more, and it is possible for the message middleware to receive access requests of multiple receivers. After the message middleware obtains the data, the receiver can automatically access the data to obtain the data, if the receiver is not started, the data in the message middleware is not consumed, and the receiver can obtain the data from the message middleware after being started.
The unified pushing method for workflow data provided by this embodiment includes: pre-configuring configuration parameters required in the data monitoring process and monitoring types to be monitored; starting message middleware; starting monitoring when detecting that the current activity state of the workflow instance object is changed into a target activity state in the monitoring type, and reading data obtained by monitoring; the data is sent to the message middleware so that the recipient retrieves the data from the message middleware. The technical scheme is applied, data obtained by different workflow engines can be managed in a unified mode through the function of the message middleware, required data do not need to be called from a plurality of different databases, and working efficiency is improved. And the message middleware can realize one-to-one and one-to-many service providing, so the method is suitable for data fusion of a plurality of different application systems.
On the basis of the above embodiment, as a preferred implementation, sending data to the message middleware includes:
screening required data from the data according to a preset requirement;
and sending the screened data to the message middleware.
In a specific implementation, the data obtained by listening and speaking is usually all data before and after the state change, and the data includes data required by the user and data not required by the user, so that if all the data is sent to the receiving party through the message middleware, resource waste is caused. In this embodiment, the data obtained by monitoring is screened, and only the data corresponding to the preset requirement is reserved. It is to be understood that the preset requirements are not limited and may be modified.
On the basis of the above embodiment, the method further includes:
and in the case that the data of the message middleware is abnormal, sending the data to the message middleware again.
In the specific implementation, data transmission errors are inevitably encountered in the data transmission, for example, the data itself is in error, or the data loss is all abnormal. By sending the data again to the message middleware, it can be guaranteed that the data acquired by the receiving side is normal data.
In the foregoing embodiments, a detailed description is given of a unified pushing method of workflow data, and the present application also provides embodiments corresponding to a unified pushing apparatus of workflow data. It should be noted that the present application describes the embodiments of the apparatus portion from two perspectives, one is based on the functional module, and the other is based on the hardware structure.
Fig. 2 is a structural diagram of a unified pushing apparatus for workflow data according to an embodiment of the present application. As shown in fig. 2, the apparatus includes:
a configuration module 10, configured to pre-configure configuration parameters and a monitoring type to be monitored in the data monitoring process;
the starting module 11 is used for starting message middleware;
the monitoring module 12 is configured to start monitoring when detecting that the current activity state of the workflow instance object is changed to a target activity state in a monitoring type, and read data obtained by monitoring;
and a sending module 13, configured to send the data to the message middleware so that the receiving party obtains the data from the message middleware.
As a preferred embodiment, the method further comprises the following steps:
and the detection module is used for sending the data to the message middleware again under the condition that the data of the message middleware is abnormal.
Since the embodiments of the apparatus portion and the method portion correspond to each other, please refer to the description of the embodiments of the method portion for the embodiments of the apparatus portion, which is not repeated here.
The unified pushing device for workflow data provided by this embodiment includes: the configuration module is used for pre-configuring configuration parameters required in the data monitoring process and the monitoring type to be monitored; the starting module is used for starting message middleware; the monitoring module is used for starting monitoring when detecting that the current activity state of the workflow instance object is changed into a target activity state in a monitoring type, and reading data obtained by monitoring; and the sending module is used for sending the data to the message middleware so that the receiver can acquire the data from the message middleware. The technical scheme is applied, data obtained by different workflow engines can be managed in a unified mode through the function of the message middleware, required data do not need to be called from a plurality of different databases, and working efficiency is improved. And the message middleware can realize one-to-one and one-to-many service providing, so the method is suitable for data fusion of a plurality of different application systems.
Fig. 3 is a structural diagram of another unified pushing apparatus for workflow data according to an embodiment of the present application. As shown in fig. 3, the apparatus comprises a memory 20 for storing a computer program;
the processor 21 is configured to implement the steps of the unified pushing method of workflow data as described in the above embodiments when executing the computer program.
The unified pushing device for workflow data provided by this embodiment may include, but is not limited to, a smart phone, a tablet computer, a notebook computer, or a desktop computer.
The processor 21 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like. The processor 21 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 21 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 21 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the display screen. In some embodiments, the processor 21 may further include an AI (Artificial Intelligence) processor for processing a calculation operation related to machine learning.
The memory 20 may include one or more computer-readable storage media, which may be non-transitory. Memory 20 may also include high speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In this embodiment, the memory 20 is at least used for storing the following computer program 201, wherein after being loaded and executed by the processor 21, the computer program can implement the relevant steps of the unified pushing method for workflow data disclosed in any of the foregoing embodiments. In addition, the resources stored in the memory 20 may also include an operating system 202, data 203, and the like, and the storage manner may be a transient storage manner or a permanent storage manner. Operating system 202 may include, among others, Windows, Unix, Linux, and the like. Data 203 may include, but is not limited to, snooped data.
In some embodiments, the unified pushing device of the workflow data may further include a display 22, an input/output interface 23, a communication interface 24, a power supply 25, and a communication bus 26.
Those skilled in the art will appreciate that the architecture shown in FIG. 3 does not constitute a limitation on the unified push approach to workflow data, and may include more or fewer components than those shown.
The unified pushing device for workflow data provided by the embodiment comprises a memory and a processor, wherein the processor is used for realizing the following method when executing a computer program stored in the memory: pre-configuring configuration parameters required in the data monitoring process and monitoring types to be monitored; starting message middleware; starting monitoring when detecting that the current activity state of the workflow instance object is changed into a target activity state in the monitoring type, and reading data obtained by monitoring; the data is sent to the message middleware so that the recipient retrieves the data from the message middleware. The technical scheme is applied, data obtained by different workflow engines can be managed in a unified mode through the function of the message middleware, required data do not need to be called from a plurality of different databases, and working efficiency is improved. And the message middleware can realize one-to-one and one-to-many service providing, so the method is suitable for data fusion of a plurality of different application systems.
Finally, the application also provides a corresponding embodiment of the computer readable storage medium. The computer-readable storage medium has stored thereon a computer program which, when being executed by a processor, carries out the steps as set forth in the above-mentioned method embodiments.
It is to be understood that if the method in the above embodiments is implemented in the form of software functional units and sold or used as a stand-alone product, it can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium and executes all or part of the steps of the methods described in the embodiments of the present application, or all or part of the technical solutions. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The method, the device and the medium for pushing the workflow data in a unified manner provided by the present application are described in detail above. The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
It is further noted that, in the present specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Claims (10)
1. A unified pushing method of workflow data is characterized by comprising the following steps:
pre-configuring configuration parameters required in the data monitoring process and monitoring types to be monitored;
starting message middleware;
starting monitoring when detecting that the current activity state of the workflow instance object is changed into a target activity state in the monitoring type, and reading data obtained by monitoring;
sending the data to the message middleware so that a receiver acquires the data from the message middleware.
2. The unified pushing method of workflow data as recited in claim 1 wherein said sending said data to said message middleware comprises:
screening required data from the data according to a preset requirement;
and sending the screened data to the message middleware.
3. The unified pushing method of workflow data as recited in claim 2, wherein said sending the screened data to the message middleware comprises:
and encrypting the screened data and sending the encrypted data to the message middleware.
4. The unified pushing method for workflow data as recited in any one of claims 1 to 3 wherein the receiving party is multiple.
5. The unified pushing method of workflow data as recited in claim 1 further comprising:
and in the case that the data of the message middleware is abnormal, sending the data to the message middleware again.
6. The unified pushing method of workflow data as recited in claim 1 wherein said workflow instance object comprises a process instance and an activity instance.
7. The unified pushing method of workflow data as recited in claim 6 wherein said workflow instance object is an active instance and said listening types include:
before the creation of an activity instance, after the creation of an activity instance, before the start of an activity instance, after the start of an activity instance, before the termination of an activity instance, after the termination of an activity instance, before the suspension of an activity instance, after the suspension of an activity instance, before the reply of an activity instance, after the reply of an activity instance, before the completion of an activity instance, before the jump of an activity instance, after the jump of an activity instance, before the rollback of an activity instance, after the rollback of an activity instance, before the release of an activity instance, after the release of an activity instance, before the recovery of an activity instance, and after the recovery of an activity instance.
8. A unified pushing device of workflow data, comprising:
the configuration module is used for pre-configuring configuration parameters required in the data monitoring process and the monitoring type to be monitored;
the starting module is used for starting message middleware;
the monitoring module is used for starting monitoring when detecting that the current activity state of the workflow instance object is changed into a target activity state in the monitoring type, and reading data obtained by monitoring;
and the sending module is used for sending the data to the message middleware so that a receiving party can acquire the data from the message middleware.
9. The unified pushing device of the workflow data is characterized by comprising a memory, a storage unit and a pushing unit, wherein the memory is used for storing a computer program;
a processor for implementing the steps of the unified push method of workflow data according to any of claims 1 to 7 when executing said computer program.
10. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, realizes the steps of the unified push method of workflow data according to any of the claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011268864.3A CN112488462A (en) | 2020-11-13 | 2020-11-13 | Unified pushing method, device and medium for workflow data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011268864.3A CN112488462A (en) | 2020-11-13 | 2020-11-13 | Unified pushing method, device and medium for workflow data |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112488462A true CN112488462A (en) | 2021-03-12 |
Family
ID=74930072
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011268864.3A Pending CN112488462A (en) | 2020-11-13 | 2020-11-13 | Unified pushing method, device and medium for workflow data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112488462A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114119019A (en) * | 2021-11-26 | 2022-03-01 | 跨境银行间支付清算有限责任公司 | Multi-channel access method and device based on cross-border payment system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108388479A (en) * | 2018-02-10 | 2018-08-10 | 深圳壹账通智能科技有限公司 | Postpone information push method, device, computer equipment and storage medium |
| CN111510474A (en) * | 2020-03-26 | 2020-08-07 | 中国平安人寿保险股份有限公司 | Data transmission method based on message middleware and related equipment |
| CN111708586A (en) * | 2020-06-22 | 2020-09-25 | 平安养老保险股份有限公司 | Application starting configuration item loading method and device, computer equipment and storage medium |
| CN111786886A (en) * | 2020-06-30 | 2020-10-16 | 京东数字科技控股有限公司 | Message processing method, device and system, electronic equipment and storage medium |
| CN111858007A (en) * | 2020-07-29 | 2020-10-30 | 广州海鹚网络科技有限公司 | Task scheduling method and device based on message middleware |
| CN111861384A (en) * | 2020-06-30 | 2020-10-30 | 深圳市中农易讯信息技术有限公司 | Method, device and medium for designing multiple workflow engines |
-
2020
- 2020-11-13 CN CN202011268864.3A patent/CN112488462A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108388479A (en) * | 2018-02-10 | 2018-08-10 | 深圳壹账通智能科技有限公司 | Postpone information push method, device, computer equipment and storage medium |
| CN111510474A (en) * | 2020-03-26 | 2020-08-07 | 中国平安人寿保险股份有限公司 | Data transmission method based on message middleware and related equipment |
| CN111708586A (en) * | 2020-06-22 | 2020-09-25 | 平安养老保险股份有限公司 | Application starting configuration item loading method and device, computer equipment and storage medium |
| CN111786886A (en) * | 2020-06-30 | 2020-10-16 | 京东数字科技控股有限公司 | Message processing method, device and system, electronic equipment and storage medium |
| CN111861384A (en) * | 2020-06-30 | 2020-10-30 | 深圳市中农易讯信息技术有限公司 | Method, device and medium for designing multiple workflow engines |
| CN111858007A (en) * | 2020-07-29 | 2020-10-30 | 广州海鹚网络科技有限公司 | Task scheduling method and device based on message middleware |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114119019A (en) * | 2021-11-26 | 2022-03-01 | 跨境银行间支付清算有限责任公司 | Multi-channel access method and device based on cross-border payment system |
| CN114119019B (en) * | 2021-11-26 | 2024-03-12 | 跨境银行间支付清算有限责任公司 | Multi-channel access method and device based on cross-border payment system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108449410B (en) | Message management method, system and related device in cloud platform | |
| US10261872B2 (en) | Multilevel disaster recovery | |
| US8375200B2 (en) | Embedded device and file change notification method of the embedded device | |
| EP2948875B1 (en) | Method and system for using a recursive event listener on a node in hierarchical data structure | |
| CN106878363B (en) | Information processing method, device and system | |
| CN108268211B (en) | Data processing method and device | |
| CN113742031B (en) | Node state information acquisition method and device, electronic equipment and readable storage medium | |
| CN111897633A (en) | Task processing method and device | |
| CN113377626B (en) | Visual unified alarm method, device, equipment and medium based on service tree | |
| CN103501237A (en) | Device management method, management platform, device and system | |
| US10331484B2 (en) | Distributed data platform resource allocator | |
| CN112328448A (en) | Zookeeper-based monitoring method, monitoring device, equipment and storage medium | |
| CN111338834B (en) | Data storage method and device | |
| CN113452774A (en) | Message pushing method, device, equipment and storage medium | |
| CN109167819B (en) | Data synchronization system, method, device and storage medium | |
| CN114625535A (en) | Service deployment method and device for multiple Kubernetes clusters | |
| CN114185734A (en) | Cluster monitoring method and device and electronic equipment | |
| CN111953569B (en) | State information reporting method, device, equipment and medium | |
| CN112488462A (en) | Unified pushing method, device and medium for workflow data | |
| CN111026794A (en) | Data management method, device, equipment and medium based on data source | |
| CN111147542A (en) | Secret-free access setting method, device, equipment and medium | |
| CN115174596A (en) | Equipment remote copying method, device and medium | |
| CN114880717A (en) | Data archiving method and device | |
| CN112463616A (en) | Chaos testing method and device for Kubernetes container platform | |
| CN112463514A (en) | Monitoring method and device for distributed cache cluster |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210312 |