CN111339186A - Workflow engine data synchronization method, device, medium and electronic equipment - Google Patents
Workflow engine data synchronization method, device, medium and electronic equipment Download PDFInfo
- Publication number
- CN111339186A CN111339186A CN202010103182.0A CN202010103182A CN111339186A CN 111339186 A CN111339186 A CN 111339186A CN 202010103182 A CN202010103182 A CN 202010103182A CN 111339186 A CN111339186 A CN 111339186A
- Authority
- CN
- China
- Prior art keywords
- data
- flow
- queue
- identifier
- theme
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F16/275—Synchronous replication
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Entrepreneurship & Innovation (AREA)
- Databases & Information Systems (AREA)
- General Physics & Mathematics (AREA)
- Operations Research (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Quality & Reliability (AREA)
- Marketing (AREA)
- Computing Systems (AREA)
- Economics (AREA)
- General Engineering & Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The disclosure relates to the field of data synchronization, and discloses a workflow engine data synchronization method, a workflow engine data synchronization device, a workflow engine data synchronization medium and electronic equipment. The method is performed by a workflow engine, the method comprising: acquiring a process definition identifier after acquiring registration information sent by a service system; determining whether a subject queue corresponding to the process definition identification exists in the message queue; if the topic queue does not exist, the process definition identifier and the service system identifier are sent to a message queue, so that after the message queue creates the topic queue corresponding to the process definition identifier, a subscription relation of the topic queue corresponding to the service system identifier and the process definition identifier is established; after the workflow engine generates the process flow data, the process flow data are sent to the theme queue corresponding to the process definition identification, and the theme queue sends the process flow data to the business system corresponding to the subscription relationship. Under the method, the possibility of abnormity of the workflow engine is reduced, and the robustness and the reliability of the workflow engine are improved.
Description
Technical Field
The present disclosure relates to the field of data synchronization technologies, and in particular, to a method, an apparatus, a medium, and an electronic device for workflow engine data synchronization.
Background
With the development of information technology, the workflow products have more and more functions in the fields of enterprise office and the like. However, as the business scale is enlarged, more and more data are generated by the workflow product, and the data generated by the workflow product are often recorded in the table, so that the data recorded in the table of the workflow product at present are often massive. However, the data recorded in the table still needs to be utilized finally, for example, the business system needs to acquire some data in the table, and therefore, the business system needs to consume huge resources to acquire the required data in the table of the workflow product, which may cause the workflow product to work abnormally or be unavailable.
Disclosure of Invention
In the technical field of data synchronization, to solve the technical problem, an object of the present disclosure is to provide a method, an apparatus, a medium, and an electronic device for workflow engine data synchronization.
According to an aspect of the present disclosure, there is provided a workflow engine data synchronization method, the method being performed by a workflow engine, the method comprising:
after acquiring registration information sent by a service system, acquiring a process definition identifier in the registration information, wherein the registration information comprises the process definition identifier and a service system identifier of the service system;
determining whether a theme queue corresponding to the process definition identifier exists in a preset message queue;
if the preset message queue does not have the theme queue corresponding to the process definition identification, sending the process definition identification and the business system identification to the preset message queue, so that the preset message queue establishes a subscription relationship between the business system identification and the theme queue corresponding to the process definition identification after the theme queue corresponding to the process definition identification is created;
after the workflow engine generates at least one flow circulation data, the generated flow circulation data are sent to a theme queue corresponding to a flow definition identifier of each flow circulation data in the preset message queue, and the flow circulation data contained in each theme queue are sent to a service system which establishes a subscription relationship correspondingly by each theme queue, wherein the flow circulation data correspond to the flow definition identifier.
According to another aspect of the present disclosure, there is provided a workflow engine data synchronization apparatus, the apparatus being located at a workflow engine, the apparatus comprising:
the acquisition module is configured to acquire a process definition identifier in registration information after acquiring the registration information sent by a service system, wherein the registration information comprises the process definition identifier and a service system identifier of the service system;
the determining module is configured to determine whether a theme queue corresponding to the flow definition identifier exists in preset message queues or not;
the first sending module is configured to send the process definition identifier and the service system identifier to a preset message queue if the preset message queue does not have a theme queue corresponding to the process definition identifier, so that after the preset message queue creates the theme queue corresponding to the process definition identifier, a subscription relationship between the service system identifier and the theme queue corresponding to the process definition identifier is established;
and the second sending module is configured to send each generated flow circulation data to a topic queue corresponding to a flow definition identifier of each flow circulation data in the preset message queue after the workflow engine generates at least one flow circulation data, and send the flow circulation data contained in each topic queue to a service system corresponding to the subscription relationship established by each topic queue, wherein the flow circulation data correspond to the flow definition identifiers.
According to another aspect of the present disclosure, there is provided a computer readable program medium storing computer program instructions which, when executed by a computer, cause the computer to perform the method as previously described.
According to another aspect of the present disclosure, there is provided an electronic apparatus including:
a processor;
a memory having computer readable instructions stored thereon which, when executed by the processor, implement the method as previously described.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects:
the workflow engine data synchronization method provided by the present disclosure is executed by a workflow engine, and includes the following steps: after acquiring registration information sent by a service system, acquiring a process definition identifier in the registration information, wherein the registration information comprises the process definition identifier and a service system identifier of the service system; determining whether a theme queue corresponding to the process definition identifier exists in a preset message queue; if the preset message queue does not have the theme queue corresponding to the process definition identification, sending the process definition identification and the business system identification to the preset message queue, so that the preset message queue establishes a subscription relationship between the business system identification and the theme queue corresponding to the process definition identification after the theme queue corresponding to the process definition identification is created; after the workflow engine generates at least one flow circulation data, the generated flow circulation data are sent to a theme queue corresponding to a flow definition identifier of each flow circulation data in the preset message queue, and the flow circulation data contained in each theme queue are sent to a service system which establishes a subscription relationship correspondingly by each theme queue, wherein the flow circulation data correspond to the flow definition identifier.
Under the method, the traditional mode of directly synchronizing data by the workflow engine is changed into the mode that the workflow engine transmits data to the message queue, then the message queue performs data synchronization, and the functional module for synchronizing data to the service system is removed from the workflow engine, so that asynchronous decoupling between the workflow engine and the data synchronization function is realized, the possibility of abnormity of the workflow engine can be reduced, and the robustness and the reliability of the workflow engine are improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
FIG. 1 is a system architecture diagram illustrating the application of a workflow engine data synchronization method in accordance with an exemplary embodiment;
FIG. 2 is a flow diagram illustrating a method for workflow engine data synchronization in accordance with an exemplary embodiment;
FIG. 3 is a detailed flow diagram of step 240 according to one embodiment shown in a corresponding embodiment of FIG. 2;
FIG. 4 is a flowchart detailing step 242 according to one embodiment shown in a corresponding embodiment of FIG. 3;
FIG. 5 is a block diagram illustrating a workflow engine data synchronization apparatus in accordance with an exemplary embodiment;
FIG. 6 is a block diagram illustrating an example of an electronic device implementing the workflow engine data synchronization method described above, according to an example embodiment;
fig. 7 is a computer-readable storage medium for implementing the workflow engine data synchronization method according to an exemplary embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the invention, as detailed in the appended claims.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities.
The present disclosure first provides a workflow engine data synchronization method. The workflow engine is used as a part of the application system and provides core solutions for determining information transfer routing, content level and the like according to different roles, division and conditions which are determinative to each application system. The workflow engine may include important functions of node management, flow direction management, process sample management, etc. of the process. The workflow engine provides core logic support for the normal flow of business states. The workflow engine data is various data generated when the workflow engine runs, such as node data, process instance data, and the like. Synchronizing the workflow engine data refers to synchronizing the workflow engine data to other entities that need to use the workflow engine data, such as business systems.
The implementation terminal of the present disclosure may be any device having an operation processing and communication function, which may be connected to an external device for receiving or sending data, and specifically may be a portable mobile device, such as a smart phone, a tablet computer, a notebook computer, a pda (personal Digital assistant), or the like, or may be a fixed device, such as a computer device, a field terminal, a desktop computer, a server, a workstation, or the like, or may be a set of multiple devices, such as a physical infrastructure of cloud computing or a server cluster.
Preferably, the implementation terminal of the present disclosure may be a physical infrastructure of a server or cloud computing.
FIG. 1 is a system architecture diagram illustrating the application of a workflow engine data synchronization method in accordance with an exemplary embodiment. As shown in fig. 1, the system architecture includes a workflow engine 110, a first database 120, a business system 130, a second database 140, a database log scanning plug-in 150, and a message queue 160, wherein the workflow engine 110 includes a workflow management system 111, the first database 120 has a database archive log, and the message queue 160 includes a plurality of topic queues 161, wherein each topic queue is a queue for sending a class of data, and the class of data can be divided in various ways, such as by using a flow definition identifier as a dividing basis. When the workflow engine data synchronization method provided by the present disclosure is applied to the system architecture shown in fig. 1, one process may be such that: the business system firstly registers to the workflow engine and sends registration information to the workflow engine, the workflow engine can obtain a process definition identifier in the registration information after obtaining the registration information, and the registration information comprises the process definition identifier and a business system identifier of the business system; next, the workflow engine determines whether a theme queue corresponding to the process definition identifier exists in the message queue, wherein, when the theme queue corresponding to the process definition identifier does not exist in the message queue, the workflow engine sends the process definition identifier and the business system identifier to the message queue, the message queue creates the theme queue corresponding to the process definition identifier, and establishes a subscription relationship between the business system identifier and the theme queue; after the workflow engine generates at least one process flow data, the generated process flow data can be persisted to a first database; next, the workflow engine acquires operation records in a database filing log of the first database and sends the operation records to the database log scanning plug-in, the database log scanning plug-in can analyze the operation records to determine and acquire process flow data to be synchronized, then the process flow data to be synchronized are forwarded to a theme queue corresponding to a process definition identifier of each process flow data, and the theme queue sends the process flow data contained in the theme queue to a service system corresponding to the theme queue and establishing a subscription relationship, so that the whole synchronization process of the workflow engine data to the service system is realized. Therefore, in the system architecture shown in fig. 1, asynchronous decoupling of data synchronization tasks is achieved, and a data synchronization function is not reserved in the workflow engine, so that the workflow engine can be more stable.
FIG. 2 is a flow diagram illustrating a method for workflow engine data synchronization in accordance with an exemplary embodiment. The workflow engine data synchronization method of the embodiment is executed by a workflow engine, and the workflow engine may run on a server, as shown in fig. 2, and includes the following steps:
The registration information includes a process definition identifier and a service system identifier of the service system.
The business system identification is a business system-specific identification that uniquely corresponds to the business system. The service system identifier may be a character string, the character string may be any combination of symbols such as letters, numbers, and the like, the service system identifier itself may also correspond to a name, and the name may also be any combination of symbols such as letters, numbers, and the like. For example, the name corresponding to the identifier of the service system may be service _ id, where the relationship between the name corresponding to the identifier of the service system and the identifier of the service system is a key-value relationship.
The process is a complete or partially continuous process of a service processed by the workflow engine, a series of process data can be generated in the process of circulation, and one process is uniquely identified by a process definition identifier. One business system identifier may correspond to a plurality of process definition identifiers.
In one embodiment, the registration information further includes a task definition and a message type.
In one embodiment, the workflow engine further comprises a workflow management system, and the workflow management system in the workflow engine acquires the registration information sent by the business system.
In one embodiment, the service system is a financial service system, the preset Message queue is a Message middleware FMQ (fast Message queue), and the financial service system usually needs higher reliability, so that messages in the Message queue are not allowed to be lost, and the reliability of the Message middleware FMQ is very high, so that the method is suitable for the financial field with high requirement on reliability.
The topic (topic) queue is a sub-queue in a plurality of queues contained in a preset message queue, and the preset message queue comprises at least one topic queue. Each topic queue is a queue for sending a type of data.
In one embodiment, the workflow engine stores all target process definition identifiers corresponding to the topic queue identifier, and the determining whether a topic queue corresponding to the process definition identifier exists in a preset message queue includes:
determining whether a target process definition identifier consistent with the process definition identifier exists in all target process definition identifiers corresponding to the subject queue identifier;
if so, determining that a theme queue corresponding to the flow definition identifier exists in a preset message queue, otherwise, determining that the theme queue corresponding to the flow definition identifier does not exist in the preset message queue.
In one embodiment, the workflow engine stores all target process definition identifiers having corresponding topic queues, and the determining whether a topic queue corresponding to the process definition identifier exists in a preset message queue includes:
determining whether a target process definition identifier consistent with the process definition identifier exists in all target process definition identifiers;
if so, determining that a theme queue corresponding to the flow definition identifier exists in a preset message queue, otherwise, determining that the theme queue corresponding to the flow definition identifier does not exist in the preset message queue.
In one embodiment, the determining whether a topic queue corresponding to the flow definition identifier exists in a preset message queue includes:
sending a flow definition identification acquisition request to a preset message queue to acquire flow definition identifications corresponding to each subject queue in the preset message queue as second flow definition identifications;
when a second flow definition identifier is acquired, judging whether the second flow definition identifier is consistent with the first flow definition identifier or not;
if so, determining that a theme queue corresponding to the flow definition identifier exists in a preset message queue, otherwise, determining that the theme queue corresponding to the flow definition identifier does not exist in the preset message queue.
The subscription relationship refers to a mapping relationship between the service system identifier and the corresponding topic queue, that is, a binding relationship between the service system and the topic queue, and after the subscription relationship is established, the service system corresponding to the service system identifier can obtain a message corresponding to the subscribed topic queue.
The preset message queue can create a corresponding theme queue according to the process definition identifier, and the process can involve a plurality of links including applying for memory.
In an embodiment, if there is no topic queue corresponding to the process definition identifier in a preset message queue, sending the process definition identifier and the service system identifier to the preset message queue, so that after the preset message queue creates a topic queue corresponding to the process definition identifier, a subscription relationship between the service system identifier and the topic queue corresponding to the process definition identifier is established, including:
if the theme queue corresponding to the process definition identifier does not exist in the preset message queue, the process definition identifier and the business system identifier are sent to the preset message queue, so that after the preset message queue creates the theme queue corresponding to the process definition identifier, the reminding information about the created theme queue corresponding to the process definition identifier is sent to the business system corresponding to the business system identifier, and the subscription relationship between the business system identifier and the theme queue corresponding to the process definition identifier is established.
After receiving the reminding information of the theme queue corresponding to the flow definition identifier, the service system can determine that the theme queue corresponding to the flow definition identifier is established and can know which theme queue to go to acquire data, so that corresponding data can be pulled from the corresponding theme queue when synchronous data needs to be acquired.
In the embodiment, the message queue only supports message persistence, the consumption end is a pull model, and the consumption state and the subscription relationship are maintained by the service system, so that the service system can determine whether to pull data from the corresponding topic queue according to the consumption capacity of the service system, and the stability of the operation of the service system is ensured.
In one embodiment, step 230 may comprise:
if the theme queue corresponding to the process definition identifier does not exist in the preset message queue, the process definition identifier and the business system identifier are sent to the preset message queue, so that the business system identifier is associated with the theme queue corresponding to the process definition identifier after the preset message queue creates the theme queue corresponding to the process definition identifier, and the subscription relationship between the business system identifier and the theme queue corresponding to the process definition identifier is established.
Because the service system identification is uniquely corresponding to the service system, once the subscription relationship between the service system identification and the topic queue is established, the subscription relationship between the service system corresponding to the service system identification and the topic queue is established, so that the topic queue can determine which service system the message is to be sent to.
In this embodiment, the topic queue supports the memory queue and the persistent queue, the consumption end is a push model, the consumption state and the subscription relationship are maintained by the topic queue, and the topic queue can immediately send the message to the service system subscribed to the topic queue after receiving the message, thereby improving the real-time performance of the service system for obtaining the message.
In one embodiment, after step 220, the method may further comprise:
if a theme queue corresponding to the process definition identifier exists in a preset message queue, the process definition identifier and the service system identifier are sent to the preset message queue, so that the preset message queue establishes a subscription relationship between the service system identifier and the theme queue corresponding to the process definition identifier.
And under the condition that the theme queue corresponding to the process definition identifier exists in the preset message queue, the preset message queue is not required to be created again, and the subscription relationship of the theme queue corresponding to the service system identifier and the process definition identifier can be directly established by sending the process definition identifier and the service system identifier to the preset message queue.
And the flow circulation data corresponds to the flow definition identification.
The workflow engine can generate corresponding flow circulation data according to the flow of the flow in the operation process.
In one embodiment, the workflow engine includes a buffer, and the buffer stores the workflow flow data generated by the workflow engine and not transmitted, and step 240 may include:
judging whether the size of flow circulation data stored in a cache region of the workflow engine reaches a preset threshold value every other preset time period;
if yes, sending each flow stream data in the buffer area to a subject queue corresponding to the flow definition identification of each flow stream data in the preset message queue, and sending the flow stream data contained in each subject queue to a service system which establishes a subscription relationship correspondingly through each subject queue.
In an embodiment, after the workflow engine generates at least one flow circulation data, the generated flow circulation data is sent to a topic queue corresponding to a flow definition identifier of each flow circulation data in the preset message queue, and each topic queue sends the flow circulation data contained in each topic queue to a service system corresponding to the service system with a subscription relationship established, where the method includes:
after the workflow engine generates at least one process flow data, persisting each generated process flow data to a first database connected with the workflow engine, wherein the first database comprises a database archiving log, and the database archiving log comprises operation records of the first database;
the method comprises the steps of obtaining operation records in a database filing log of a first database and sending the operation records to a database log scanning plug-in, so that after the database log scanning plug-in analyzes the operation records, the database log scanning plug-in obtains process flow data needing to be synchronized in the first database and sends the process flow data needing to be synchronized to a theme queue corresponding to process definition marks of the process flow data, the theme queues send the process flow data contained in the theme queues to service systems corresponding to subscription relations, and the service systems store the received process flow data to a second database, wherein the process flow data correspond to the process definition marks.
In this embodiment, the workflow engine obtains the operation record in the database archive log of the first database, and sends the operation record to the database log scanning plug-in, so that the database log scanning plug-in is located outside the workflow engine. Therefore, the present embodiment can be applied to the system architecture shown in fig. 1.
In one embodiment, the workflow engine includes a database log scanning plug-in, and the specific steps of step 240 may be as shown in FIG. 3. Fig. 3 is a detailed flowchart of step 240 according to one embodiment shown in a corresponding embodiment of fig. 2. As shown in fig. 3, step 240 may include the steps of:
Wherein the first database comprises a database archive log comprising operational records for the first database.
The operation records refer to records of the workflow engine changing the process flow data in the first database, the records are stored in the database in the form of logs, and the changing operation can include adding, deleting, changing and the like.
The process of persisting the process flow data to the database is the process of fixedly storing the process flow data to the database.
The database log scanning plug-in analyzes the operation records to obtain an analysis result, and based on the analysis result, the flow circulation data needing to be synchronized can be obtained from the first database.
In an embodiment, the analyzing, by the database log scanning plug-in, the operation record in the database archive log of the first database to obtain the flow stream data that needs to be synchronized in the first database includes:
and analyzing the operation records in the database filing log of the first database by using a database log scanning plug-in every preset time period so as to acquire the flow circulation data needing to be synchronized in the first database.
The method has the advantages that the database log scanning plug-in is used regularly to obtain the flow circulation data needing synchronization and synchronize the message queues, so that the synchronization regularity of the flow circulation data is improved, and the unstable factors caused by the irregularity of the flow circulation data when the flow circulation data are synchronized are reduced.
In one embodiment, the specific steps of step 242 may be as shown in FIG. 4. Fig. 4 is a flowchart illustrating details of step 242 according to one embodiment illustrated in a corresponding embodiment of fig. 3. As shown in fig. 4, the following steps may be included:
step 242', the database log scanning plug-in is used to obtain the flow circulation data with the corresponding operation record, and obtain the flow circulation data with the corresponding flow definition identifier consistent with the registered flow definition identifier from the flow circulation data with the corresponding operation record, as the flow circulation data to be synchronized.
The process flow data is stored in the first database, and the operation on one or more process flow data generates corresponding operation records in the database archive log, and the operation records mean that the corresponding process flow data is changed. In this embodiment, by obtaining the flow circulation data having the corresponding operation record and the flow definition identifier being consistent with the registered flow definition identifier, the flow circulation data that needs to be synchronized most can be synchronized in time.
And the flow circulation data corresponds to the flow definition identification.
Different process definition identifiers correspond to different theme queues, and process definition identifiers of different process flow data may be the same or different, so that different process flow data need to be sent to the theme queues corresponding to the process definition identifiers, and different process flow data need to be sent to different theme queues.
In one embodiment, the registration information includes a plurality of process definition identifiers, the operation record in the database archive log of the first database includes an identifier of process flow data and a corresponding process definition identifier, the process flow data persisted to the first database is stored in correspondence with the identifier of the corresponding process flow data, and the analyzing, by the database log scanning plug-in, the operation record in the database archive log of the first database to obtain the process flow data that needs to be synchronized in the first database includes:
determining a process definition identifier consistent with the process definition identifier in the registration information from the process definition identifiers in the operation records of the database filing log of the first database by using a database log scanning plug-in;
acquiring an identifier of the process flow data corresponding to the determined process definition identifier from an operation record of a database filing log of the first database;
acquiring process flow data with the identification consistent with the identification of the acquired process flow data from the first database as the process flow data needing synchronization;
the sending the flow circulation data to be synchronized to the theme queues corresponding to the flow definition identifiers of the flow circulation data, and the sending, by the theme queues, the flow circulation data contained in the theme queues to the service system corresponding to the established subscription relationship, includes:
and sending the flow circulation data to be synchronized to the theme queues corresponding to the flow definition identifications of the flow circulation data, and sending the flow circulation data contained in the theme queues to the service systems including the service systems and correspondingly establishing subscription relationships.
In the embodiment shown in fig. 3, the process flow data generated by the workflow engine is transmitted to the database for persistence, then the process flow data to be synchronized is determined according to the database filing log of the database, and finally the determined process flow data is transmitted to the corresponding topic queue and is forwarded to the corresponding service system by the topic queue, so that the pressure of the workflow engine and the message queue is reduced, the stable operation of the message queue and the workflow engine is ensured, and meanwhile, the reliable backup of the process flow data is realized by using the database.
In one embodiment, the registration information further includes at least one data type requiring synchronization, the process flow data includes data items corresponding to the at least one data type,
if the preset message queue does not have the theme queue corresponding to the process definition identifier, sending the process definition identifier and the service system identifier to the preset message queue, so that after the preset message queue creates the theme queue corresponding to the process definition identifier, a subscription relationship between the service system identifier and the theme queue corresponding to the process definition identifier is established, including:
if the theme queue corresponding to the process definition identification does not exist in the preset message queue, sending the process definition identification, the business system identification and the data type needing to be synchronized to the preset message queue, so that after the preset message queue creates the theme queue corresponding to the process definition identification, a label corresponding to each data type needing to be synchronized corresponding to the theme queue is created, and a subscription relationship between the business system identification and the theme queue corresponding to the process definition identification is established;
after the workflow engine generates at least one flow circulation data, the generated flow circulation data are sent to the theme queues corresponding to the flow definition identifications of the flow circulation data in the preset message queues, and the flow circulation data contained in the theme queues are sent to the service systems corresponding to the established subscription relationship by the theme queues, wherein the method comprises the following steps:
after the workflow engine generates at least one flow circulation data, the generated flow circulation data are sent to a theme queue corresponding to a flow definition identifier of the flow circulation data in the preset message queue, corresponding labels are marked on the data items by the theme queues according to data types corresponding to the data items included in the flow circulation data in the theme queues, the flow circulation data included in the theme queues are sent to business systems which establish subscription relations correspondingly, the business systems acquire the data items corresponding to the configured labels in the received flow circulation data according to the configured labels, and the business systems write the data items into a table structure defined in advance by the business systems.
The data type is the kind of data needed by the business system, the workflow engine can correspondingly generate the data of corresponding kind, the data type can be node data, process example data or task example data, wherein the process example data is data related to a specific process, the node data is data corresponding to a node in the process, and the task example data is data generated by a manually operated task in the process.
Tags (tag) are further subdivisions of data items of the flowstream data by corresponding data types.
In this embodiment, by tagging data items in the process flow data, the service system can select data items to be stored as needed by using a pre-configured tag, so that customization of a table structure can be achieved, personalized requirements of the service system can be met, and data storage pressure can be reduced by selecting data to be stored as needed by the service system.
The present disclosure also provides a workflow engine data synchronization apparatus, and the following is an apparatus embodiment of the present disclosure.
Fig. 5 is a block diagram illustrating a workflow engine data synchronization apparatus located at a workflow engine according to an exemplary embodiment, and as shown in fig. 5, the apparatus 500 includes:
an obtaining module 510, configured to obtain a process definition identifier in registration information after obtaining the registration information sent by a service system, where the registration information includes the process definition identifier and a service system identifier of the service system;
a determining module 520 configured to determine whether a topic queue corresponding to the flow definition identifier exists in a preset message queue;
a first sending module 530, configured to send the process definition identifier and the service system identifier to a preset message queue if there is no theme queue corresponding to the process definition identifier in a preset message queue, so that after the preset message queue creates the theme queue corresponding to the process definition identifier, a subscription relationship between the service system identifier and the theme queue corresponding to the process definition identifier is established;
a second sending module 540, configured to, after the workflow engine generates at least one flow circulation data, send each generated flow circulation data to a topic queue corresponding to a flow definition identifier of each flow circulation data in the preset message queue, and send, by each topic queue, the flow circulation data included in each topic queue to a service system that establishes a subscription relationship correspondingly, where the flow circulation data corresponds to the flow definition identifier.
According to a third aspect of the present disclosure, there is also provided an electronic device capable of implementing the above method.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.
An electronic device 600 according to this embodiment of the invention is described below with reference to fig. 6. The electronic device 600 shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 6, the electronic device 600 is embodied in the form of a general purpose computing device. The components of the electronic device 600 may include, but are not limited to: the at least one processing unit 610, the at least one memory unit 620, and a bus 630 that couples the various system components including the memory unit 620 and the processing unit 610.
Wherein the storage unit stores program code that is executable by the processing unit 610 such that the processing unit 610 performs the steps according to various exemplary embodiments of the present invention as described in the section "example methods" above in this specification.
The storage unit 620 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM)621 and/or a cache memory unit 622, and may further include a read only memory unit (ROM) 623.
The storage unit 620 may also include a program/utility 624 having a set (at least one) of program modules 625, such program modules 625 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
The electronic device 600 may also communicate with one or more external devices 800 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 600, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 600 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 650. Also, the electronic device 600 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the Internet) via the network adapter 660. As shown, the network adapter 660 communicates with the other modules of the electronic device 600 over the bus 630. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.
According to a fourth aspect of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-mentioned method of the present specification. In some possible embodiments, aspects of the invention may also be implemented in the form of a program product comprising program code means for causing a terminal device to carry out the steps according to various exemplary embodiments of the invention described in the above section "exemplary methods" of the present description, when said program product is run on the terminal device.
Referring to fig. 7, a program product 700 for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
Furthermore, the above-described figures are merely schematic illustrations of processes involved in methods according to exemplary embodiments of the invention, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.
It will be understood that the invention is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the invention is limited only by the appended claims.
Claims (10)
1. A workflow engine data synchronization method, the method being performed by a workflow engine, the method comprising:
after acquiring registration information sent by a service system, acquiring a process definition identifier in the registration information, wherein the registration information comprises the process definition identifier and a service system identifier of the service system;
determining whether a theme queue corresponding to the process definition identifier exists in a preset message queue;
if the preset message queue does not have the theme queue corresponding to the process definition identification, sending the process definition identification and the business system identification to the preset message queue, so that the preset message queue establishes a subscription relationship between the business system identification and the theme queue corresponding to the process definition identification after the theme queue corresponding to the process definition identification is created;
after the workflow engine generates at least one flow circulation data, the generated flow circulation data are sent to a theme queue corresponding to a flow definition identifier of each flow circulation data in the preset message queue, and the flow circulation data contained in each theme queue are sent to a service system which establishes a subscription relationship correspondingly by each theme queue, wherein the flow circulation data correspond to the flow definition identifier.
2. The method according to claim 1, wherein if there is no topic queue corresponding to the process definition identifier in a preset message queue, sending the process definition identifier and the service system identifier to the preset message queue, so that after the preset message queue creates a topic queue corresponding to the process definition identifier, a subscription relationship between the service system identifier and the topic queue corresponding to the process definition identifier is established, including:
if the theme queue corresponding to the process definition identifier does not exist in the preset message queue, the process definition identifier and the business system identifier are sent to the preset message queue, so that after the preset message queue creates the theme queue corresponding to the process definition identifier, the reminding information about the created theme queue corresponding to the process definition identifier is sent to the business system corresponding to the business system identifier, and the subscription relationship between the business system identifier and the theme queue corresponding to the process definition identifier is established.
3. The method according to claim 1, wherein the workflow engine includes a database log scanning plug-in, and after the workflow engine generates at least one flow stream data, the workflow engine sends each generated flow stream data to a topic queue corresponding to a flow definition identifier of each flow stream data in the preset message queue, and each topic queue sends the flow stream data included in each topic queue to a service system that has established a subscription relationship, including:
after the workflow engine generates at least one process flow data, persisting each generated process flow data to a first database connected with the workflow engine, wherein the first database comprises a database archiving log, and the database archiving log comprises operation records of the first database;
analyzing operation records in a database filing log of the first database by using a database log scanning plug-in to acquire flow circulation data needing to be synchronized in the first database;
and sending the flow circulation data to be synchronized to a theme queue corresponding to the flow definition identifier of each flow circulation data in the preset message queue, and sending the flow circulation data contained in each theme queue to a service system which establishes a subscription relationship correspondingly by each theme queue, wherein the flow circulation data correspond to the flow definition identifier.
4. The method of claim 3, wherein the registration information includes a plurality of process definition identifiers, the operation records in the database archive log of the first database include an identifier of process flow data and a corresponding process definition identifier, the process flow data persisted to the first database is stored in correspondence with the identifier of the corresponding process flow data, and the analyzing the operation records in the database archive log of the first database by using the database log scanning plug-in to obtain the process flow data needing to be synchronized in the first database comprises:
determining a process definition identifier consistent with the process definition identifier in the registration information from the process definition identifiers in the operation records of the database filing log of the first database by using a database log scanning plug-in;
acquiring an identifier of the process flow data corresponding to the determined process definition identifier from an operation record of a database filing log of the first database;
acquiring process flow data with the identification consistent with the identification of the acquired process flow data from the first database as the process flow data needing synchronization;
the sending the flow circulation data to be synchronized to the theme queues corresponding to the flow definition identifiers of the flow circulation data, and the sending, by the theme queues, the flow circulation data contained in the theme queues to the service system corresponding to the established subscription relationship, includes:
and sending the flow circulation data to be synchronized to the theme queues corresponding to the flow definition identifications of the flow circulation data, and sending the flow circulation data contained in the theme queues to the service systems including the service systems and correspondingly establishing subscription relationships.
5. The method of claim 3, wherein the analyzing, by the database log scanning plug-in, the operation records in the database archive log of the first database to obtain the process flow data required to be synchronized in the first database comprises:
and acquiring the flow circulation data with the corresponding operation records by using the database log scanning plug-in, and acquiring the flow circulation data with the corresponding flow definition identification consistent with the registered flow definition identification in the flow circulation data with the corresponding operation records as the flow circulation data needing synchronization.
6. The method of claim 1, wherein the registration information further includes at least one data type to be synchronized, wherein the process flow data includes data items corresponding to the at least one data type,
if the preset message queue does not have the theme queue corresponding to the process definition identifier, sending the process definition identifier and the service system identifier to the preset message queue, so that after the preset message queue creates the theme queue corresponding to the process definition identifier, a subscription relationship between the service system identifier and the theme queue corresponding to the process definition identifier is established, including:
if the theme queue corresponding to the process definition identification does not exist in the preset message queue, sending the process definition identification, the business system identification and the data type needing to be synchronized to the preset message queue, so that after the preset message queue creates the theme queue corresponding to the process definition identification, a label corresponding to each data type needing to be synchronized corresponding to the theme queue is created, and a subscription relationship between the business system identification and the theme queue corresponding to the process definition identification is established;
after the workflow engine generates at least one flow circulation data, the generated flow circulation data are sent to the theme queues corresponding to the flow definition identifications of the flow circulation data in the preset message queues, and the flow circulation data contained in the theme queues are sent to the service systems corresponding to the established subscription relationship by the theme queues, wherein the method comprises the following steps:
after the workflow engine generates at least one flow circulation data, the generated flow circulation data are sent to a theme queue corresponding to a flow definition identifier of the flow circulation data in the preset message queue, corresponding labels are marked on the data items by the theme queues according to data types corresponding to the data items included in the flow circulation data in the theme queues, the flow circulation data included in the theme queues are sent to business systems which establish subscription relations correspondingly, the business systems acquire the data items corresponding to the configured labels in the received flow circulation data according to the configured labels, and the business systems write the data items into a table structure defined in advance by the business systems.
7. The method according to claim 1, wherein after the workflow engine generates at least one flow circulation data, the generated flow circulation data is sent to a topic queue corresponding to a flow definition identifier of each flow circulation data in the preset message queue, and each topic queue sends the flow circulation data contained in each topic queue to a service system corresponding to which a subscription relationship is established, the method comprising:
after the workflow engine generates at least one process flow data, persisting each generated process flow data to a first database connected with the workflow engine, wherein the first database comprises a database archiving log, and the database archiving log comprises operation records of the first database;
the method comprises the steps of obtaining operation records in a database filing log of a first database and sending the operation records to a database log scanning plug-in, so that after the database log scanning plug-in analyzes the operation records, the database log scanning plug-in obtains process flow data needing to be synchronized in the first database and sends the process flow data needing to be synchronized to a theme queue corresponding to process definition marks of the process flow data, the theme queues send the process flow data contained in the theme queues to service systems corresponding to subscription relations, and the service systems store the received process flow data to a second database, wherein the process flow data correspond to the process definition marks.
8. A workflow engine data synchronization apparatus, wherein the apparatus is located in a workflow engine, the apparatus comprising:
the acquisition module is configured to acquire a process definition identifier in registration information after acquiring the registration information sent by a service system, wherein the registration information comprises the process definition identifier and a service system identifier of the service system;
the determining module is configured to determine whether a theme queue corresponding to the flow definition identifier exists in preset message queues or not;
the first sending module is configured to send the process definition identifier and the service system identifier to a preset message queue if the preset message queue does not have a theme queue corresponding to the process definition identifier, so that after the preset message queue creates the theme queue corresponding to the process definition identifier, a subscription relationship between the service system identifier and the theme queue corresponding to the process definition identifier is established;
and the second sending module is configured to send each generated flow circulation data to a topic queue corresponding to a flow definition identifier of each flow circulation data in the preset message queue after the workflow engine generates at least one flow circulation data, and send the flow circulation data contained in each topic queue to a service system corresponding to the subscription relationship established by each topic queue, wherein the flow circulation data correspond to the flow definition identifiers.
9. A computer-readable program medium, characterized in that it stores computer program instructions which, when executed by a computer, cause the computer to perform the method according to any one of claims 1 to 7.
10. An electronic device, characterized in that the electronic device comprises:
a processor;
a memory having stored thereon computer readable instructions which, when executed by the processor, implement the method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010103182.0A CN111339186B (en) | 2020-02-19 | 2020-02-19 | Workflow engine data synchronization method, device, medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010103182.0A CN111339186B (en) | 2020-02-19 | 2020-02-19 | Workflow engine data synchronization method, device, medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111339186A true CN111339186A (en) | 2020-06-26 |
| CN111339186B CN111339186B (en) | 2022-09-30 |
Family
ID=71181720
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010103182.0A Active CN111339186B (en) | 2020-02-19 | 2020-02-19 | Workflow engine data synchronization method, device, medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111339186B (en) |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111930836A (en) * | 2020-07-16 | 2020-11-13 | 北京首汽智行科技有限公司 | Data synchronization method based on workflow platform |
| CN112069265A (en) * | 2020-09-11 | 2020-12-11 | 中国工商银行股份有限公司 | Configuration data synchronization method, service data system, computer system and medium |
| CN112364163A (en) * | 2020-11-10 | 2021-02-12 | 平安普惠企业管理有限公司 | Log caching method and device and computer equipment |
| CN113220791A (en) * | 2021-06-03 | 2021-08-06 | 西安热工研究院有限公司 | Data cascade synchronization system and method |
| CN113342484A (en) * | 2021-05-14 | 2021-09-03 | 深圳奥哲网络科技有限公司 | Process engine method, system, device and storage medium |
| CN114051055A (en) * | 2022-01-12 | 2022-02-15 | 江苏银承网络科技股份有限公司 | Data transmission method and device in different systems |
| CN114217875A (en) * | 2021-12-17 | 2022-03-22 | 平安壹钱包电子商务有限公司 | Method, device and equipment for processing order and storage medium |
| CN114331391A (en) * | 2022-03-09 | 2022-04-12 | 北京有生博大软件股份有限公司 | Workflow synchronous updating method and workflow synchronous updating system based on global state updating |
| CN114358748A (en) * | 2022-03-17 | 2022-04-15 | 武汉法正信信息技术有限公司 | BIM-based engineering construction informatization management method and device |
| CN114647703A (en) * | 2022-05-23 | 2022-06-21 | 武汉中科通达高新技术股份有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN116521630A (en) * | 2023-06-30 | 2023-08-01 | 深圳复临科技有限公司 | Task progress real-time display method and device, computer equipment and storage medium |
| CN117875299A (en) * | 2024-03-13 | 2024-04-12 | 南京智握信息技术有限公司 | Electronic file integrated processing method and system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107783975A (en) * | 2016-08-24 | 2018-03-09 | 北京京东尚科信息技术有限公司 | The method and apparatus of distributed data base synchronization process |
| WO2018130066A1 (en) * | 2017-01-11 | 2018-07-19 | 腾讯科技（深圳）有限公司 | Data migration method, computer device, and storage medium |
| CN109815028A (en) * | 2018-12-27 | 2019-05-28 | 北京摩拜科技有限公司 | Data synchronous system, method, apparatus and computer storage medium |
| CN110069670A (en) * | 2019-04-30 | 2019-07-30 | 深圳前海微众银行股份有限公司 | Purpose data classifying method, device, equipment and computer readable storage medium |
| CN110110006A (en) * | 2019-04-15 | 2019-08-09 | 平安普惠企业管理有限公司 | Data managing method and Related product |
| CN110717073A (en) * | 2019-10-08 | 2020-01-21 | 普元信息技术股份有限公司 | System and method for realizing process query processing by combining service data in cloud process platform |
-
2020
- 2020-02-19 CN CN202010103182.0A patent/CN111339186B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107783975A (en) * | 2016-08-24 | 2018-03-09 | 北京京东尚科信息技术有限公司 | The method and apparatus of distributed data base synchronization process |
| WO2018130066A1 (en) * | 2017-01-11 | 2018-07-19 | 腾讯科技（深圳）有限公司 | Data migration method, computer device, and storage medium |
| CN109815028A (en) * | 2018-12-27 | 2019-05-28 | 北京摩拜科技有限公司 | Data synchronous system, method, apparatus and computer storage medium |
| CN110110006A (en) * | 2019-04-15 | 2019-08-09 | 平安普惠企业管理有限公司 | Data managing method and Related product |
| CN110069670A (en) * | 2019-04-30 | 2019-07-30 | 深圳前海微众银行股份有限公司 | Purpose data classifying method, device, equipment and computer readable storage medium |
| CN110717073A (en) * | 2019-10-08 | 2020-01-21 | 普元信息技术股份有限公司 | System and method for realizing process query processing by combining service data in cloud process platform |
Non-Patent Citations (1)
| Title |
|---|
| 杨海涛: "大规模云同步归集数据系统的异步并行优化", 《计算机工程与应用》 * |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111930836A (en) * | 2020-07-16 | 2020-11-13 | 北京首汽智行科技有限公司 | Data synchronization method based on workflow platform |
| CN112069265A (en) * | 2020-09-11 | 2020-12-11 | 中国工商银行股份有限公司 | Configuration data synchronization method, service data system, computer system and medium |
| CN112069265B (en) * | 2020-09-11 | 2024-01-30 | 中国工商银行股份有限公司 | Synchronization method of configuration data, business data system, computer system and medium |
| CN112364163A (en) * | 2020-11-10 | 2021-02-12 | 平安普惠企业管理有限公司 | Log caching method and device and computer equipment |
| CN113342484A (en) * | 2021-05-14 | 2021-09-03 | 深圳奥哲网络科技有限公司 | Process engine method, system, device and storage medium |
| CN113220791A (en) * | 2021-06-03 | 2021-08-06 | 西安热工研究院有限公司 | Data cascade synchronization system and method |
| CN113220791B (en) * | 2021-06-03 | 2023-07-28 | 西安热工研究院有限公司 | Data cascading synchronization system and method |
| CN114217875A (en) * | 2021-12-17 | 2022-03-22 | 平安壹钱包电子商务有限公司 | Method, device and equipment for processing order and storage medium |
| CN114051055A (en) * | 2022-01-12 | 2022-02-15 | 江苏银承网络科技股份有限公司 | Data transmission method and device in different systems |
| CN114331391B (en) * | 2022-03-09 | 2022-08-19 | 北京有生博大软件股份有限公司 | Workflow synchronous updating method and workflow synchronous updating system based on global state updating |
| CN114331391A (en) * | 2022-03-09 | 2022-04-12 | 北京有生博大软件股份有限公司 | Workflow synchronous updating method and workflow synchronous updating system based on global state updating |
| CN114358748A (en) * | 2022-03-17 | 2022-04-15 | 武汉法正信信息技术有限公司 | BIM-based engineering construction informatization management method and device |
| CN114358748B (en) * | 2022-03-17 | 2022-06-03 | 武汉法正信信息技术有限公司 | BIM-based engineering construction informatization management method and device |
| CN114647703B (en) * | 2022-05-23 | 2022-08-30 | 武汉中科通达高新技术股份有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN114647703A (en) * | 2022-05-23 | 2022-06-21 | 武汉中科通达高新技术股份有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN116521630A (en) * | 2023-06-30 | 2023-08-01 | 深圳复临科技有限公司 | Task progress real-time display method and device, computer equipment and storage medium |
| CN116521630B (en) * | 2023-06-30 | 2024-01-02 | 深圳复临科技有限公司 | Task progress real-time display method and device, computer equipment and storage medium |
| CN117875299A (en) * | 2024-03-13 | 2024-04-12 | 南京智握信息技术有限公司 | Electronic file integrated processing method and system |
| CN117875299B (en) * | 2024-03-13 | 2024-05-24 | 南京智握信息技术有限公司 | Electronic file integrated processing method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111339186B (en) | 2022-09-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111339186B (en) | Workflow engine data synchronization method, device, medium and electronic equipment | |
| CN109254733B (en) | Method, device and system for storing data | |
| US11561972B2 (en) | Query conversion for querying disparate data sources | |
| CN111190888A (en) | Method and device for managing graph database cluster | |
| CN112162965B (en) | Log data processing method, device, computer equipment and storage medium | |
| CN110263277B (en) | Page data display method, page data updating device, page data equipment and storage medium | |
| CN112765152B (en) | Method and apparatus for merging data tables | |
| CN110119386B (en) | Data processing method, data processing apparatus, medium, and computing device | |
| US20170060861A1 (en) | File creation through virtual containers | |
| CN110688096B (en) | Method and device for constructing application program containing plug-in, medium and electronic equipment | |
| CN111679892A (en) | Distributed transaction processing method, device, equipment and medium | |
| CN113342450B (en) | Page processing method, device, electronic equipment and computer readable medium | |
| CN111338834A (en) | Data storage method and device | |
| CN110716804A (en) | Method and device for automatically deleting useless resources, storage medium and electronic equipment | |
| CN110224921B (en) | Method, device, medium and electronic equipment for sending mail containing recruitment information | |
| WO2024001240A1 (en) | Task integration method and apparatus for multiple technology stacks | |
| US10956413B2 (en) | Action set translation | |
| CN112148705A (en) | Data migration method and device | |
| CN115454971A (en) | Data migration method and device, electronic equipment and storage medium | |
| CN113760920B (en) | Data synchronization method and device, electronic equipment and storage medium | |
| CN113672685A (en) | Information processing method, apparatus, and medium | |
| CN113360558A (en) | Data processing method, data processing device, electronic device, and storage medium | |
| CN113743842A (en) | Multi-source data difference warning method and device | |
| CN111444200A (en) | Data updating method and storage medium | |
| CN109710673B (en) | Work processing method, device, equipment and medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |