CN112068936B - Workflow management platform and workflow management system - Google Patents
Workflow management platform and workflow management system Download PDFInfo
- Publication number
- CN112068936B CN112068936B CN202010686756.1A CN202010686756A CN112068936B CN 112068936 B CN112068936 B CN 112068936B CN 202010686756 A CN202010686756 A CN 202010686756A CN 112068936 B CN112068936 B CN 112068936B
- Authority
- CN
- China
- Prior art keywords
- flow
- instance
- instruction
- layer
- workflow management
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 claims description 99
- 230000008569 process Effects 0.000 claims description 89
- 238000005516 engineering process Methods 0.000 claims description 13
- 238000012545 processing Methods 0.000 claims description 9
- 238000010586 diagram Methods 0.000 claims description 8
- 238000007726 management method Methods 0.000 description 58
- 230000006870 function Effects 0.000 description 23
- 238000012544 monitoring process Methods 0.000 description 13
- 230000000694 effects Effects 0.000 description 7
- 239000013598 vector Substances 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 238000011084 recovery Methods 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 101100310856 Drosophila melanogaster spri gene Proteins 0.000 description 1
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 235000008429 bread Nutrition 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000008602 contraction Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 230000009191 jumping Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000013515 script Methods 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- 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/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority 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
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Strategic Management (AREA)
- Human Resources & Organizations (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Software Systems (AREA)
- Entrepreneurship & Innovation (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a workflow management platform and a workflow management system.A presentation layer in the workflow management platform generates a flow instantiation instruction based on an API interface of an access layer for user flow instantiation operation, a business logic layer acquires a business ID of the flow instantiation instruction and a flow template corresponding to the flow instantiation instruction, a flow engine is utilized to read stored flow definition data and operation configuration data corresponding to the flow template from a storage layer, flow instances are generated according to the business ID, the flow template and the flow definition data and the operation configuration data corresponding to the flow template, thereby creating a plurality of flow instances, and when the plurality of flow instances are started by the flow engine, the flow instances are executed by threads corresponding to the instance identifications of each flow instance according to the corresponding relation between the instance identifications of the flow instances and the thread identifications of the threads, so that dirty data phenomenon can be effectively avoided, and the performance of the flow instances during execution can be effectively improved.
Description
Technical Field
The invention relates to the technical field of communication, in particular to a workflow management platform and a workflow management system.
Background
With the popularization of Web technology, web-based workflow technology has been fully developed. The workflow may extend through the Web to multiple enterprises and will enable collaborative work among multiple Web-based workflow servers. Through years of development, the structure of the workflow management system has evolved from an original environment capable of supporting only a single workgroup to a workflow environment capable of supporting enterprise-level (even inter-enterprise). One workflow instance may be distributed across different servers and clients via local area networks, wide area networks, and the impact of server failure is minimized. Thus, the expandability, practicability and management capability of the system are greatly improved.
In a workflow management system for complex enterprise applications, early workflow technologies and products are difficult to support complex enterprise applications, and the integration capability of the existing enterprise applications is obviously insufficient, for example, in the enterprise applications, workflow services are generally concurrent in the workflow management system, but when a plurality of workflow services are executed in parallel in the workflow management system, dirty data phenomenon may exist due to the fact that data of each workflow service are crossed when the workflow services are executed, and the performance of the system is poor when the workflow services are executed.
Within the invention
The workflow management platform and the workflow management system provided by the embodiment of the invention can effectively avoid dirty data phenomenon and can effectively improve the performance of the process instance during execution.
In a first aspect, an embodiment of the present invention provides a workflow management platform, where the workflow management platform includes an access layer, a presentation layer, a service logic layer, and a storage layer that are sequentially set from top to bottom;
the storage layer is used for storing data, wherein the data comprises flow definition data and operation configuration data;
The presentation layer is used for calling an API (application program interface) of the access layer to generate a flow instantiation instruction based on the flow instantiation operation of the user, wherein the flow instantiation instruction comprises a service ID;
the access layer is used for issuing a flow instantiation instruction generated by the presentation layer;
the business logic layer is used for acquiring a business ID of the flow instantiation instruction and a flow template corresponding to the flow instantiation instruction when the flow instantiation instruction issued by the presentation layer is monitored, reading stored flow definition data and operation configuration data corresponding to the flow template from the storage layer by using a flow engine, and generating a flow instance according to the business ID, the flow template and the flow definition data and the operation configuration data corresponding to the flow template, so as to create a plurality of flow instances;
The business logic layer is further configured to execute the process instance by using the thread identifier corresponding to the instance identifier of each process instance according to the correspondence between the instance identifier of each process instance and the thread identifier of the thread when the process engine is used to start the plurality of process instances.
Optionally, in the workflow management platform, for each flow instance, the flow instance includes at least one flow node, and when the at least one flow node includes a flow execution operation node, the service logic layer sends a flow execution operation interface to the presentation layer when executing the flow operation node of the flow instance by using a thread identifier corresponding to the instance identifier of the flow instance;
the presentation layer is further used for acquiring a flow execution operation input by a user based on a flow execution operation interface, and calling an API interface of the access layer to generate an execution instruction based on the flow execution operation, wherein the execution instruction comprises a service ID and a tenant ID;
the access layer is further configured to issue the execution instruction, obtain a target flow instance corresponding to the service ID based on the service ID in the execution instruction, and obtain a flow node corresponding to the tenant ID in the execution instruction in the target flow instance;
The business logic layer is further used for searching a thread identifier corresponding to the instance identifier of the target flow instance when the execution instruction issued by the presentation layer is monitored, and executing the execution instruction by utilizing a thread to which the thread identifier belongs so as to adjust the working state of the flow node flow corresponding to the tenant ID in the execution instruction.
Optionally, in the workflow management platform, the execution instruction includes a pass instruction, a reject instruction, a select instruction, a retract instruction, or an add instruction.
Optionally, in the workflow management platform, for each flow instance, the flow instance includes at least one flow node, and when the at least one flow node includes a callback node, the presentation layer is further configured to call an API interface of the access layer to generate a callback instruction based on a flow callback operation of a user, where the callback instruction includes a service ID;
The access layer is also used for issuing the callback instruction and acquiring a target flow instance corresponding to the service ID based on the service ID in the callback instruction;
And the business logic layer is also used for acquiring a target flow instance corresponding to the business ID based on the business ID in the callback instruction when the callback instruction issued by the presentation layer is monitored, and calling and executing a callback function corresponding to the callback instruction at the callback node by using a thread corresponding to the target flow instance.
Optionally, in the above workflow management platform, for each flow instance, the flow instance includes at least one flow node, and when the at least one flow node includes an event node, the presentation layer is further configured to call an API interface of the access layer to generate an event instruction based on an event execution operation of the user, where the event instruction includes a service ID;
the access layer is also used for issuing the event instruction and acquiring a target flow instance corresponding to the service ID based on the service ID in the event instruction;
the business logic layer is further used for acquiring a target flow instance corresponding to the business ID based on the business ID in the event instruction when the event instruction issued by the presentation layer is monitored, and processing the event instruction at the event node by utilizing a thread corresponding to the target flow instance.
Optionally, in the workflow management platform, the storage layer is further configured to store the stored data after performing database splitting and table splitting by using a distributed database technology when the data is stored.
Optionally, in the above workflow management platform, the business logic layer is further configured to create a plurality of threads when the process engine is used to start the plurality of process instances, allocate a thread identifier to each thread, allocate an instance identifier to each process instance, and establish a correspondence between the instance identifier of each process instance and the thread identifier of each thread, and execute the process instance by using a thread to which the thread identifier corresponding to the instance identifier of each process instance belongs.
Optionally, in the above workflow management platform, the presentation layer is further configured to generate a workflow chart using SVG technology and flow instances.
Optionally, in the workflow management platform, the business logic layer includes at least one of a spri ng component, a SPR I NGMVC component, a MyBat i s component and a queue component.
Optionally, in the workflow management platform, the presentation layer includes an html component, a css component, a jquery component, and a Bootstrap component.
In a second aspect, the application further provides a workflow management system, which comprises the electronic equipment and the workflow management platform, wherein the electronic equipment is used for running the workflow management platform.
Compared with the prior art, the embodiment in the scheme can have the following advantages or beneficial effects:
The embodiment of the invention discloses a workflow management platform and a workflow management system, wherein a presentation layer in the workflow management platform generates a flow instantiation instruction based on an API interface of an access layer for calling a user's flow instantiation operation, a business logic layer acquires a business ID of the flow instantiation instruction and a flow template corresponding to the flow instantiation instruction, a flow engine is utilized to read stored flow definition data and operation configuration data corresponding to the flow template from a storage layer, and flow instances are generated according to the business ID, the flow template and the flow definition data and the operation configuration data corresponding to the flow template, so that a plurality of flow instances are created, and when the plurality of flow instances are started by utilizing the flow engine, the flow instances are executed by utilizing threads to which the instance identifications of each flow instance belong according to the corresponding relation between the instance identifications of the flow instances and the thread identifications of the threads, so that dirty data phenomenon can be effectively avoided, and the performance of executing the flow instances can be effectively improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and should not be considered as limiting the scope, and other related drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a functional architecture diagram of a workflow management platform provided by an embodiment of the present application;
Fig. 2 is a schematic flow chart of a method for developing industrial application software according to an embodiment of the present application.
Icon: 100-workflow management platform; 110-a presentation layer; 120-access stratum; 130-business logic layer; 140-storage layer.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the following detailed description of the implementation method of the present invention will be given with reference to the accompanying drawings and examples, by which the technical means are applied to solve the technical problems, and the implementation process for achieving the technical effects can be fully understood and implemented accordingly.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures.
Example 1
Referring to fig. 1, fig. 1 is a functional architecture diagram of a workflow management platform 100 according to the present embodiment, where the workflow management platform 100 may operate on an electronic device.
The workflow management platform 100 includes an access layer 120, a presentation layer 110, a service logic layer 130, and a storage layer 140 sequentially disposed from top to bottom.
In this embodiment, the storage layer 140 is configured to store data, and the data stored in the storage layer 140 may include flow definition data and operation configuration data.
The presentation layer 110 is configured to call an API interface of the access layer 120 to generate a flow instantiation instruction based on a flow instantiation operation of a user, where the flow instantiation instruction includes a service ID.
The access layer 120 is configured to issue a flow instantiation instruction generated by the presentation layer 110.
The business logic layer 130 is configured to, when monitoring a flow instantiation instruction issued by the presentation layer 110, obtain a business ID of the flow instantiation instruction and a flow template corresponding to the flow instantiation instruction, read, by using a flow engine, stored flow definition data and operation configuration data corresponding to the flow template from the storage layer 140, and generate a flow instance according to the business ID, the flow template, and the flow definition data and the operation configuration data corresponding to the flow template, so as to create a plurality of flow instances.
The business logic layer 130 is further configured to execute each process instance by using the thread to which the thread identifier corresponding to the instance identifier of the process instance belongs according to the correspondence between the instance identifier of the process instance and the thread identifier of the thread.
By adopting the workflow management platform 100, the thread identification and the instance identification are utilized to obtain the thread corresponding to the flow instance, so that all operations of the corresponding flow instance are executed on the thread, thereby effectively preventing dirty data from being generated.
In this embodiment, the access layer 120 includes a load balancing component SLB/Nginx, where load balancing is a basic network service, mainly for solving the problem of concurrent pressure of company services, enhancing the network processing capability, reducing the resource pressure of a single device, and improving the overall service performance.
The access layer 120 is further configured to provide an API interface, where the API interface is a predefined function or refers to a convention in which different components of the software system are joined. The purpose is to provide the application and developer with the ability to access a set of routines based on certain software or hardware without having to access the native code or understand the details of the internal operating mechanisms.
The access layer 120 provides an API interface to enable the generated flow instance to have a uniform flow integration specification, so that the generated flow instance is better specified when the flow instance is executed, and the standardization of the approval business flow is realized.
The presentation layer 110 calls an API interface of the access layer 120 based on the user's process instantiation operation, so as to generate a process instantiation instruction corresponding to the instantiation operation according to the instantiation operation and the data or instruction corresponding to the operation stored in the storage layer 140 by accessing the data in the storage layer 140 using the API interface when generating the process instantiation instruction.
It should be noted that, the service ID in the instantiation instruction is a unique identifier of a flow instance corresponding to the instantiation instruction, different flow templates, flow definition data and operation configuration data corresponding to different service IDs are different, and correspondingly generated flow instances are different, for example, service IDs corresponding to a reimbursement approval flow instance, a leave examination approval flow instance, a seal examination approval flow instance and the like are different.
It will be appreciated that the flow instantiation instructions may also include an initiator or initiating institution, etc.
The presentation layer 110 may generate a graphical interface, which may in turn be presented to a user. The presentation layer may also be used to obtain operations entered by a user, for example, operations entered by a user based on a presented graphical interface.
The flow instantiation instruction generated by the presentation layer 110 based on the API interface of the access layer 120 by the user's flow instantiation operation may specifically be: the presentation layer 110 presents a flow instance generation interface to a user, and receives a flow instantiation operation input by the user based on the flow instance generation interface, so as to invoke an API interface of the access layer 120 to generate a flow instantiation instruction based on the flow instantiation operation.
It is to be appreciated that the flow instantiation generation interface presented to the user by the presentation layer 110 can be generated based on user operations.
Specifically, when the workflow management platform 100 is applied to an electronic device, the presentation layer 110 is configured to generate a flow instance generating interface based on an operation of a user, display the flow instance generating interface on the electronic device, and obtain a flow instance instruction generated by calling an API interface of the access layer 120 by a flow instance operation input by the user based on the flow instance generating interface and received by the electronic device, where the flow instance operation may be an operation of selecting a flow instance operation option displayed on the electronic device by the user, or may be an operation of inputting a gesture operation corresponding to the flow instance operation by the user to the electronic device, for example, an operation of sliding or circling the touch screen of the electronic device in a preset direction, and the like, and the configuration may be performed according to actual requirements, which is not limited herein.
In order to enable the presentation layer 110 to generate an interface, for example, a flow instance generates an interface, in this embodiment, the presentation layer 110 further includes an html component, a css component, a jquery component, and a Bootstrap component.
Wherein, the html component can be composed of other more common components: icons, a toolbar, a slider, and an image display area.
It should be noted that, when the html component needs to be displayed, the html component can use the file described by the html language to display the effect through the WWW browser.
The html language is a language for creating a web page file, and displays contents such as images, sounds, pictures, text animations, movies and the like through a Tag type instruction (Tag). And the common application of html language is to bring about hypertext technology-jumping from one theme to another theme by clicking a mouse, jumping from one page to another, the file-linked hypertext transfer protocol with hosts around the world prescribes the rules and actions that the browser follows when running html documents.
The css component can realize the component display effect according to the agreed DOM structure and component class, for example, the realization: grid layout, navigation, bread line, tab, form, button, badge, reference block, etc.
The css component can be used for precisely controlling the typesetting of element positions in an interface to be displayed at a pixel level, supports almost all font size styles and has the capability of editing webpage objects and model styles. And by utilizing css components, the format code can be simplified.
Jquery component that enables plug-in effects like map applications with mouse scroll zoom and drag functions in the project, and can add mark-up points with callback functions. It contains a large number of predefined parts (widgets) and a set of tools for building high-level elements (e.g., draggable, ordered).
Bootstrap components are components that include multiple reusability components for creating images, drop-down menus, navigation, alert boxes, pop-up boxes, modal dialog boxes, tab pages, scroll bars, pop-up boxes, and the like. And can also be used as a button prompt component for generating a prompt box comprising option buttons for a user to select corresponding options. The implementation effect is similar to the function of confirm in js, and a definite and canceling judgment is given to the user.
Because the presentation layer 110 has the html component, the css component, the jquery component, and the Bootstrap component, the presentation layer can generate an interface and present the interface to a user, and acquire the interface input operation based on the presentation, so as to achieve the interaction purpose.
The flow engine in the business logic layer 130 is the core of the workflow management platform 100, and faces to a service manager (super manager), and is mainly used for receiving instructions, processing instructions, monitoring services and managing services. The flow engine can be deployed in a plurality of ways according to the needs, the queue configuration of each tenant is read according to the flow configuration after the engine is started, instructions (four types of instantiation instructions, execution instructions, callback instructions and event instructions) in the queue are loaded according to the cycles, and then the instruction processor is executed to process business logic respectively.
The instantiation instruction is responsible for loading the template initiation flow instance.
The execution instruction is responsible for business approval and flow circulation such as flow passing, rejecting, signing, returning and the like.
The callback instruction is responsible for calling a callback function configured by the service system, for example, when a task to be handled is generated, the service system is called to send a mail callback, and a target user is notified of unprocessed task to be handled in a mail mode.
The process definition data acquired by the service logic layer 130 may include a process template corresponding to the service ID, a process instance name corresponding to the process template, activity information, participant information, and the like.
The operation configuration data acquired by the service logic layer 130 may include configuration data, such as routing information, routing rule information, etc., required by the flow instance corresponding to the service ID at runtime.
Based on the foregoing, the storage layer 140 should store flow definition data and operation configuration data corresponding to different service IDs.
After the service logic layer 130 reads the stored flow definition data and operation configuration data corresponding to the flow template from the storage layer 140 by using the flow engine, and generates a flow instance according to the service ID, the flow template, and the flow definition data and operation configuration data corresponding to the flow template, when each flow instance is conveniently executed subsequently, a queue may be created for each flow instance, and the flow definition data, the operation configuration data, and other data related to the flow instance corresponding to the flow instance may be stored in the queue. It is possible to further avoid a phenomenon in which dirty data is generated due to overlapping of data of a plurality of flow instances when the plurality of flow instances are executed simultaneously.
In addition, since the flow engine may perform processing multiple instantiation instructions or perform multiple instantiation operations at the same time, and dynamically allocate the number of threads, when the flow engine is used to generate a flow instance, the business logic layer 130 may dynamically create the number of threads according to the monitored number of flow instructions when monitoring the flow instructions issued by the access layer 120.
Specifically, when the service logic layer 130 monitors only one process instantiation instruction at a time, and when the service logic layer 130 starts a plurality of process instances by using a process engine, a plurality of threads are created, a thread identifier is allocated to each thread, an instance identifier is allocated to each process instance, and a corresponding relation between the instance identifier of each process instance and the thread identifier of each thread is established, so that the process instance is executed by using the thread to which the thread identifier corresponding to the instance identifier of each process instance belongs, thereby realizing the technology of isolation by using a multi-thread technology, and ensuring that the starting and execution of each process instance are executed on different threads.
When the service logic layer 130 monitors multiple process instantiation instructions issued by the presentation layer 110 at the same time, multiple threads may also be created, so that when the service logic layer 130 obtains a service ID of each process instantiation instruction and a process template corresponding to each process instantiation instruction, a thread is allocated for each process instantiation instruction, so that a process instance is generated according to the service ID of the process instance, the process template, the process definition data corresponding to the process template, and the operation configuration data by using the thread corresponding to each process instantiation instruction.
When the generated multiple flow instances are executed simultaneously, executing the flow instance by using the thread to which the thread identifier corresponding to the instance identifier of each flow instance belongs according to the corresponding relation between the instance identifier of each flow instance and the thread identifier of the thread.
Through the arrangement, decoupling and asynchronization of each process instance and processing among each process instance in running are realized by using a distributed queue technology, meanwhile, the efficiency of the workflow engine for executing instructions is improved, and meanwhile, when the process instance is abnormally interrupted, a mode of remedying by using the workflow engine can be used, so that correct recovery of data is ensured.
It should be noted that the flow instance is a business flow, and the flow instance generally includes a plurality of flow nodes, where the plurality of flow nodes may include, but are not limited to, one or more of a flow execution operation node, a callback node, and an event node. Each flow node is respectively corresponding to the participant and the route information
When the flow instance includes a flow execution operation node and when the business logic layer 130 executes to the flow execution operation node, a flow execution operation interface may be sent to the user, so that the user inputs a flow execution operation to generate an execution instruction (e.g., pass, reject, select, retract, sign, etc.) to change the state of the flow node to execute the next node or stop executing, etc.
When the flow instance includes a callback node or an event node, the presentation layer 110 may call an API interface of the access layer 120 to generate a callback instruction based on a flow callback operation of a user, or call an API interface of the access layer 120 to generate an event instruction based on an event execution operation of a user, so that the service logic layer 130 executes the callback instruction or the execution event instruction when monitoring the event instruction or the callback instruction issued by the access layer 120.
The storage layer 140 may store the flow definition data and the operation configuration data by using structured data or by using unstructured data.
When the data is stored by using the structured data storage method, the data may be stored by using a relational database (Relational Database Service, abbreviated as RDS) or may be stored by using a distributed relational database service (Distributed Relational Database Service, abbreviated as DRDS).
The relational database is a stable, reliable and elastically telescopic online database service, RDS supports MySQL, SQL SERVER, postgreSQL and PPAS (Postgre Plus ADVANCED SERVER, a highly compatible Oracle database) engines, and provides a complete set of solutions in disaster recovery, backup, recovery, monitoring, migration and the like.
The distributed relational database service is a distributed database product which is developed independently and developed in an effort to solve the bottleneck problem of the stand-alone database service. The DRDS is highly compatible with MySQL protocol and grammar, supports automatic horizontal splitting, online smooth expansion and contraction, elastic expansion and transparent read-write separation, and has the full life cycle operation and maintenance management and control capability of a database.
When the unstructured data storage mode is used for storing data, the unstructured data can be stored in a mode of using an object storage service (Object Storage Service, OSS), and the object storage service is a cloud storage service which is massive, safe, low in cost and high in reliability, is suitable for storing any type of files, is elastically expanded in capacity and processing capacity, is selected from multiple storage types, and comprehensively optimizes storage cost.
Optionally, in this embodiment, the storage layer 140 is further configured to store the stored data after performing the database splitting and the table splitting by using a distributed database technology when storing the data.
The data stored in the storage layer 140 is subjected to library and table division by using a distributed database technology, so that service data are uniformly distributed on different database nodes, high concurrency pressure is effectively dispersed, and service throughput is improved.
In this embodiment, to further avoid the dirty data phenomenon and improve the efficiency of the flow engine running the flow instance, for each flow instance, at least one flow node is included in the flow instance, and when the at least one flow node includes a flow execution operation node, the business logic layer 130 sends a flow execution operation interface to the presentation layer 110 when executing the flow operation node of the flow instance by using the thread identifier corresponding to the instance identifier of the flow instance.
The presentation layer 110 is further configured to obtain a flow execution operation input by a user based on a flow execution operation interface, and call an API interface of the access layer 120 to generate an execution instruction based on the flow execution operation, where the execution instruction includes a service ID and a tenant ID.
The access layer 120 is further configured to issue the execution instruction, obtain a target flow instance corresponding to the service ID based on the service ID in the execution instruction, and obtain a flow node corresponding to the tenant ID in the execution instruction in the target flow instance.
The business logic layer 130 is further configured to search, when an execution instruction issued by the presentation layer 110 is monitored, a thread identifier corresponding to an instance identifier of a target flow instance, and execute the execution instruction by using a thread to which the thread identifier belongs, so as to adjust a working state of a flow node flow corresponding to a tenant ID in the execution instruction.
Through the arrangement, the instantiation operation and the execution operation of the same flow instance are executed in the thread corresponding to the flow instance, so that the occurrence of dirty data phenomenon can be further avoided.
In this embodiment, the execution instruction may be, but is not limited to, a pass instruction, a reject instruction, a select instruction, a retract instruction, or an add instruction.
In order to facilitate the execution of callback operations during the execution of the flow instances and further avoid occurrence of dirty data phenomena, in this embodiment, for each flow instance, at least one flow node is included in the flow instance, and when the at least one flow node includes a callback node, the presentation layer 110 is further configured to generate a callback instruction based on the user's flow callback operation by calling an API interface of the access layer 120, where the callback instruction includes a service ID.
The access layer 120 is further configured to issue the callback instruction, and obtain a target flow instance corresponding to the service ID based on the service ID in the callback instruction.
The service logic layer 130 is further configured to, when monitoring a callback instruction issued by the presentation layer 110, obtain a target flow instance corresponding to the service ID based on the service ID in the callback instruction, and call and execute a callback function corresponding to the callback instruction at the callback node by using a thread corresponding to the target flow instance.
The callback function is a function called by a function pointer. If a pointer (address) of a function is passed as a parameter to another function, this pointer is a callback function when it is used to call the function to which it points. The callback function is not directly called by the implementer of the function, but is called by another party when a specific event or condition occurs, for responding to the event or condition.
Through the setting, the instantiation operation and the callback operation of the same flow instance are executed in the thread corresponding to the flow instance, so that the occurrence of dirty data phenomenon can be further avoided.
To facilitate executing the event instruction during execution of the flow instance, in this embodiment, for each flow instance, at least one flow node is included in the flow instance, and when the at least one flow node includes an event node, the presentation layer 110 is further configured to generate an event instruction based on an event execution operation of the user by calling an API interface of the access layer 120, where the event instruction includes a service ID.
The access layer 120 is further configured to issue the event instruction, and obtain a target flow instance corresponding to the service ID based on the service ID in the event instruction.
The business logic layer 130 is further configured to, when an event instruction issued by the presentation layer 110 is monitored, obtain a target flow instance corresponding to the business ID based on the business ID in the event instruction, and process the event instruction at the event node by using a thread corresponding to the target flow instance.
By the arrangement, the instantiation operation and the event instruction of the same flow instance are executed in the thread corresponding to the flow instance, so that the occurrence of dirty data phenomenon can be further avoided.
To facilitate the user's view of the process nodes in the process instance, in this embodiment, the presentation layer 110 is further configured to generate a workflow diagram using SVG techniques and the process instance.
It should be noted that SVG is an open standard vector graphics language, describing two-dimensional vectors and vector/grid graphics in XML-defined language, and provides 3 types of graphics objects, including: vector graphics (vectorgraphicshape, for example, a path consisting of straight lines and curved lines), images (images), text (text). The graphical objects may also be grouped, styled, transformed, combined, etc., with feature sets including nested transforms (nestedtransformations), cut paths (CLIPPINGPATHS), alpha masks (alphamasks), filter effects (FILTEREFFECTS), template objects (templateobjects), and other extensions (extensibility).
SVG can be used to design high resolution Web graphics pages, i.e., SVG images can be interactive and dynamic, and animation elements can be embedded in SVG files or defined by scripts. The user can directly trace the image with code, can turn on the SVG image with any word processing tool, can make the image interactive by changing part of the code, and can insert the image into HTML at any time to view through a browser.
The work flow chart is generated by utilizing the SVG technology so as to be convenient for a user to check, thereby providing a flow prejudging function of a flow instance for the user and further facilitating prejudging the trend of the flow in the flow instance according to the business data of the user and the flow template.
The process engine has the other function of providing an engine management console, and a service manager can check the execution state of the process through the engine management console, such as checking the execution state of each process node in a workflow chart and a workflow chart, so that abnormal processes can be monitored and processed as required.
Example two
The embodiment of the application provides a workflow management system, which comprises an electronic device and a workflow management platform 100 in the first embodiment, wherein the electronic device is used for running the workflow management platform 100.
In this embodiment, the electronic device may be a server.
The server may include a processor and a memory. The processor is electrically connected to the memory, either directly or indirectly, to enable transmission or interaction of data, for example, the elements may be electrically connected to each other via one or more communication buses or signal lines.
The processor may be an integrated circuit chip having signal processing capabilities. The Processor 110 may also be a general purpose Processor, for example, a digital signal Processor (DIGITAL SIGNAL Processor, DSP), application SPECIFIC INTEGRATED Circuit (ASIC), discrete gate or transistor logic, discrete hardware components, and may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present application. Further, the general purpose processor may be a microprocessor or any conventional processor or the like.
The Memory may be, but is not limited to, random access Memory (Random Access Memory, RAM), read Only Memory (ROM), programmable Read Only Memory (Programmable Read-Only Memory, PROM), erasable programmable Read Only Memory (Erasable Programmable Read-Only Memory, EPROM), and electrically erasable programmable Read Only Memory (Electric Erasable Programmable Read-Only Memory, EEPROM). The memory is used for storing a program, and the processor executes the program after receiving the execution instruction.
It should be understood that the electronic device provided by the embodiment of the present application may also have fewer or more components than those described above, or the same configuration.
In addition, each component may be implemented by software, hardware, or a combination thereof, for example, may further include a communication component or a multimedia component, which is not specifically limited herein, and may be set according to actual needs.
When the electronic device is a server, the server may be a single server or a cluster server.
When the server is a cluster server, it may include one or more of a DNS server, KONG service gateway, web application server, and elastic search server, etc. The workflow management platform may run on one or more of the servers described above.
Example III
Referring to fig. 2 in combination, an embodiment of the present application provides a workflow management system, where the workflow management system includes a server, a user terminal, and the workflow management platform 100 in the first embodiment, where the server is configured to run the workflow management platform 100, where the user terminal may be one or multiple, and the one or multiple terminals are communicatively connected to the server.
The user terminal can be a mobile phone, a computer or a tablet personal computer, is not particularly limited herein, and can be set according to actual requirements.
The user can input the process instantiation operation through the user terminal, and the user terminal sends the process instantiation operation to the server when acquiring the process instantiation operation.
In the process of running the workflow management platform 100, when the server receives the flow instantiation operation, the access layer 120 in the workflow management platform 100 calls an API interface of the access layer 120 to generate a flow instantiation instruction based on the flow instantiation operation, wherein the flow instantiation instruction comprises a service ID.
The access layer 120 obtains and issues the flow instantiation instruction generated by the presentation layer 110.
The service logic layer 130 is configured to monitor in real time whether the access layer 120 issues an instruction, and when monitoring a flow instantiation instruction issued by the presentation layer 110, acquire a service ID of the flow instantiation instruction and a flow template corresponding to the flow instantiation instruction, read, by using a flow engine, stored flow definition data and operation configuration data corresponding to the flow template from the storage layer 140, and generate a flow instance according to the service ID, the flow template, and the flow definition data and the operation configuration data corresponding to the flow template, so as to create a plurality of flow instances.
The process instance created by the service logic layer 130 includes: instance name, campaign information (e.g., approval, reimbursement, application, etc.), routing information, participant information, routing rule information, etc.
The flow instance may generally include a plurality of flow nodes, which may include one or more of an execution node, a callback node, or an event node.
When the service logic layer 130 starts the plurality of process instances by using the process engine, the process instance is executed by using the thread to which the thread identifier corresponding to the instance identifier of each process instance belongs according to the correspondence between the instance identifier of each process instance and the thread identifier of the thread.
By adopting the workflow management system, the thread corresponding to the flow instance is obtained by utilizing the thread identifier and the instance identifier through interaction between the user terminal and the server, and the thread executes all operations on the corresponding flow instance, so that dirty data is effectively prevented from being generated.
Meanwhile, when a plurality of flow instances need to be executed at the same time, a plurality of threads are created, and the corresponding relation between each thread and each flow instance is established, so that all operations on the flow instance can be executed quickly, and further the execution performance of the workflow management system can be improved effectively.
To further avoid dirty data and improve the efficiency of the process engine to run the process instance, in this embodiment, optionally:
For each flow instance, the business logic layer 130 sends a flow execution operation interface to the presentation layer 110 when executing the corresponding flow instance by using a thread and when executing a flow execution operation node to the flow instance.
The presentation layer 110 sends the flow execution operation interface to the corresponding user terminal based on the participant information and the routing rule information corresponding to the flow execution operation node of the flow instance, so as to display the flow execution operation interface on the user terminal, thereby facilitating the user to input the flow execution operation based on the flow execution operation interface.
And when receiving a flow execution operation input by a user based on a flow execution operation interface displayed on the user terminal, the user terminal sends the flow execution operation to the server. It will be appreciated that the flow execution operations sent by the server should be understood as operation information.
When obtaining a flow execution operation input by a user based on a flow execution operation interface, the presentation layer 110 calls an API interface of the access layer 120 to generate an execution instruction based on the flow execution operation, where the execution instruction includes a service ID and a tenant ID.
The execution instruction may be a pass instruction, a reject instruction, a select instruction, a retract instruction, or an add instruction, etc.
The access layer 120 obtains and issues the execution instruction generated by the presentation layer 110, obtains a target flow instance corresponding to the service ID based on the service ID in the execution instruction, and obtains a flow node corresponding to the tenant ID in the execution instruction in the target flow instance.
In the process of monitoring the instruction issued by the access layer 120 in real time, the service logic layer 130 searches the thread identifier corresponding to the instance identifier of the target flow instance when monitoring the execution instruction issued by the presentation layer 110, and executes the execution instruction by using the thread to which the thread identifier belongs, so as to adjust the working state of the flow node flow corresponding to the tenant ID in the execution instruction. For example, the flow node is adjusted to pass, reject, return, sign-on or select, etc.
Through the arrangement, the instantiation operation and the execution operation of the same flow instance are executed in the thread corresponding to the flow instance, so that the occurrence of dirty data phenomenon can be further avoided.
It may be understood that, when the flow instance includes a plurality of flow execution operation nodes, during execution of the corresponding flow instance by the thread, each flow execution operation node should be executed sequentially, and when each flow execution operation node is executed, the execution process is the same as or similar to the execution process described above for each flow instance when the corresponding flow execution operation node is executed by the thread, and therefore, a detailed description is omitted herein.
In order to facilitate the execution of callback operations during the execution of the flow instances and further avoid occurrence of dirty data phenomena, in this embodiment, for each flow instance, at least one flow node is included in the flow instance, where when the at least one flow node includes a callback node, the user terminal may further receive a callback operation input by a user, and send the callback operation to the server when receiving the callback operation. It is understood that the callback operation should be operation information corresponding to the callback operation.
When the server runs the workflow management platform 100, the workflow management platform 100 presents the layer 110 to receive the callback operation, and calls an API interface of the access layer 120 to generate a callback instruction based on the callback operation, wherein the callback instruction includes a service ID.
The access layer 120 obtains the callback instruction generated by the presentation layer 110, issues the callback instruction, and obtains the target flow instance corresponding to the service ID based on the service ID in the callback instruction.
The service logic layer 130 acquires a target flow instance corresponding to the service ID based on the service ID in the callback instruction when monitoring the callback instruction issued by the presentation layer 110 in the process of monitoring the instruction issued by the access layer 120 in real time, and invokes and executes a callback function corresponding to the callback instruction at the callback node by using a thread corresponding to the target flow instance.
Through the setting, the instantiation operation and the callback operation of the same flow instance are executed in the thread corresponding to the flow instance, so that the occurrence of dirty data phenomenon can be further avoided.
In order to facilitate the execution of event instructions during the execution of the process instances, in this embodiment, for each process instance, at least one process node is included in the process instance, where when the at least one process node includes an event node, the user terminal may further receive an event execution operation input by a user, and when the event execution operation is received, send the event execution operation to the server. It is understood that the event execution operation should be operation information corresponding to the event execution operation. For example, sending event operation information such as mail or short message to the user.
When the server runs the workflow management platform 100, the workflow management platform 100 presents the layer 110 to receive the event execution operation, and calls an API interface of the access layer 120 to generate an event instruction based on the event execution operation, wherein the event instruction includes a service ID.
When the access layer 120 obtains the event instruction generated by the presentation layer 110, it issues the event instruction, and obtains the target flow instance corresponding to the service ID based on the service ID in the event instruction.
The service logic layer 130 acquires a target process instance corresponding to the service ID based on the service ID in the event instruction when monitoring the event instruction issued by the presentation layer 110 in the process of monitoring the instruction issued by the access layer 120 in real time, and processes the event instruction at the event node by using a thread corresponding to the target process instance.
Through the arrangement, the instantiation operation and the event operation of the same flow instance are executed in the thread corresponding to the flow instance, so that the occurrence of dirty data phenomenon can be further avoided.
In summary, the embodiment of the present invention provides a workflow management platform 100 and a workflow management system, where a presentation layer 110 in the workflow management platform 100 generates a flow instantiation instruction based on an API interface of a user's flow instantiation operation call access layer 120, a service logic layer 130 obtains a service ID of the flow instantiation instruction and a flow template corresponding to the flow instantiation instruction, reads stored flow definition data and operation configuration data corresponding to the flow template from a storage layer 140 by using a flow engine, generates a flow instance according to the service ID, the flow template and the flow definition data and the operation configuration data corresponding to the flow template, thereby creating a plurality of flow instances, and when the flow engine is used to start the plurality of flow instances, executes the flow instance by using a thread to which a thread identifier corresponding to the instance identifier of each flow instance belongs, so as to effectively avoid dirty data phenomenon and effectively improve performance when executing the flow instance.
In the several embodiments provided in the present application, it should be understood that the disclosed system and method may be implemented in other manners as well. The above-described embodiments are merely illustrative, for example, of the flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present application may be integrated together to form a single part, or each module may exist alone, or two or more modules may be integrated to form a single part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The above description is only an example of the present application and is not intended to limit the scope of the present application, and various modifications and variations will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application. It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures.
It should be noted that 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.
It should be noted that the above description is only a specific embodiment of the present application, but the description is only an embodiment adopted for the purpose of facilitating understanding of the present application, and is not intended to limit the present application. It will be understood by those skilled in the art that various changes and modifications in form and detail may be made therein without departing from the spirit and scope of the application as defined by the appended claims, and that various changes and substitutions may be readily made therein without departing from the spirit and scope of the application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (11)
1. The workflow management platform is characterized by comprising an access layer, a presentation layer, a service logic layer and a storage layer which are sequentially arranged from top to bottom;
the storage layer is used for storing data, wherein the data comprises flow definition data and operation configuration data;
The presentation layer is used for calling an API (application program interface) of the access layer to generate a flow instantiation instruction based on the flow instantiation operation of the user, wherein the flow instantiation instruction comprises a service ID;
the access layer is used for issuing a flow instantiation instruction generated by the presentation layer;
the business logic layer is used for acquiring a business ID of the flow instantiation instruction and a flow template corresponding to the flow instantiation instruction when the flow instantiation instruction issued by the presentation layer is monitored, reading stored flow definition data and operation configuration data corresponding to the flow template from the storage layer by using a flow engine, and generating a flow instance according to the business ID, the flow template and the flow definition data and the operation configuration data corresponding to the flow template, so as to create a plurality of flow instances;
The business logic layer is further configured to execute the process instance by using a thread to which the thread identifier corresponding to the instance identifier of each process instance belongs according to a correspondence between the instance identifier of each process instance and the thread identifier of the thread when the process instance is started by using the process engine, and execute each process instance on the corresponding thread by according to the established correspondence between each thread and each process instance when the process instances need to be executed simultaneously.
2. The workflow management platform of claim 1, wherein for each flow instance, the flow instance includes at least one flow node, and when the at least one flow node includes a flow execution operation node, the business logic layer sends a flow execution operation interface to the presentation layer when executing the flow operation node of the flow instance with a thread identifier corresponding to the instance identifier of the flow instance;
the presentation layer is further used for acquiring a flow execution operation input by a user based on a flow execution operation interface, and calling an API interface of the access layer to generate an execution instruction based on the flow execution operation, wherein the execution instruction comprises a service ID and a tenant ID;
the access layer is further configured to issue the execution instruction, obtain a target flow instance corresponding to the service ID based on the service ID in the execution instruction, and obtain a flow node corresponding to the tenant ID in the execution instruction in the target flow instance;
The business logic layer is further used for searching a thread identifier corresponding to the instance identifier of the target flow instance when the execution instruction issued by the presentation layer is monitored, and executing the execution instruction by utilizing a thread to which the thread identifier belongs so as to adjust the working state of the flow node flow corresponding to the tenant ID in the execution instruction.
3. The workflow management platform of claim 2, wherein the execution instructions comprise pass-through instructions, reject instructions, select instructions, retract instructions, or add-sign instructions.
4. The workflow management platform of claim 1, wherein for each flow instance, the flow instance includes at least one flow node, and when the at least one flow node includes a callback node, the presentation layer is further configured to generate a callback instruction based on the API interface of the access layer for the user's flow callback operation, wherein the callback instruction includes a service ID;
The access layer is also used for issuing the callback instruction and acquiring a target flow instance corresponding to the service ID based on the service ID in the callback instruction;
And the business logic layer is also used for acquiring a target flow instance corresponding to the business ID based on the business ID in the callback instruction when the callback instruction issued by the presentation layer is monitored, and calling and executing a callback function corresponding to the callback instruction at the callback node by using a thread corresponding to the target flow instance.
5. The workflow management platform of claim 1, wherein for each flow instance, the flow instance includes at least one flow node therein, and when the at least one flow node includes an event node therein, the presentation layer is further configured to invoke an API interface of the access layer to generate an event instruction based on an event execution operation of the user, wherein the event instruction includes a service ID;
the access layer is also used for issuing the event instruction and acquiring a target flow instance corresponding to the service ID based on the service ID in the event instruction;
the business logic layer is further used for acquiring a target flow instance corresponding to the business ID based on the business ID in the event instruction when the event instruction issued by the presentation layer is monitored, and processing the event instruction at the event node by utilizing a thread corresponding to the target flow instance.
6. The workflow management platform of claim 1, wherein the storage layer is further configured to store the stored data after being subjected to a database splitting and table splitting using a distributed database technology when storing the data.
7. The workflow management platform of claim 1, wherein the business logic layer is further configured to create a plurality of threads when the plurality of flow instances are started by the flow engine, assign a thread identifier to each of the threads, assign an instance identifier to each of the flow instances, and establish a correspondence between the instance identifier of each of the flow instances and the thread identifier of each of the threads, and execute the flow instance by using the thread to which the thread identifier corresponding to the instance identifier of each of the flow instances belongs.
8. The workflow management platform of claim 1, wherein the presentation layer is further configured to generate a workflow diagram using SVG technology and flow instances.
9. The workflow management platform of claim 1, wherein the business logic layer comprises at least one of a Spring component, SPRINGMVC component, myBatis component, and queue component.
10. The workflow management platform of claim 1, wherein the presentation layer comprises an html component, a css component, a jquery component, and a Bootstrap component.
11. A workflow management system comprising an electronic device and the workflow management platform of any one of claims 1-10, the electronic device being configured to run the workflow management platform.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010686756.1A CN112068936B (en) | 2020-07-16 | 2020-07-16 | Workflow management platform and workflow management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010686756.1A CN112068936B (en) | 2020-07-16 | 2020-07-16 | Workflow management platform and workflow management system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112068936A CN112068936A (en) | 2020-12-11 |
| CN112068936B true CN112068936B (en) | 2024-05-31 |
Family
ID=73657443
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010686756.1A Active CN112068936B (en) | 2020-07-16 | 2020-07-16 | Workflow management platform and workflow management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112068936B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112700310B (en) * | 2021-01-19 | 2021-09-07 | 汇通数科智能科技有限公司 | Transaction order data optimization processing method based on E-commerce platform |
| CN112799646B (en) * | 2021-02-09 | 2024-09-06 | 北京字节跳动网络技术有限公司 | Task operation method and device |
| CN112905270B (en) * | 2021-02-19 | 2024-05-07 | 北京百度网讯科技有限公司 | Workflow realization method, device, platform, electronic equipment and storage medium |
| CN112883697B (en) * | 2021-03-17 | 2024-04-16 | 新奥数能科技有限公司 | Workflow form generation method, device, electronic equipment and computer readable medium |
| CN113283730B (en) * | 2021-05-17 | 2024-07-02 | 鲁班(北京)电子商务科技有限公司 | Universal approval process application method and device |
| CN113504955A (en) * | 2021-07-16 | 2021-10-15 | 航天中认软件测评科技（北京）有限责任公司 | BPMN-based aerospace workflow management system |
| CN114936245B (en) * | 2022-04-28 | 2023-04-14 | 北京远舢智能科技有限公司 | Method and device for integrating and processing multi-source heterogeneous data |
| CN116308148B (en) * | 2023-03-02 | 2024-08-30 | 中电金信软件有限公司 | Activity flow processing method and device and electronic equipment |
| CN116306591B (en) * | 2023-05-18 | 2023-10-03 | 深圳市东信时代信息技术有限公司 | Flow form generation method, device, equipment and medium |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6804711B1 (en) * | 1997-10-06 | 2004-10-12 | Mci, Inc. | Method and apparatus for managing call processing services in an intelligent telecommunication network |
| CN101866460A (en) * | 2010-06-28 | 2010-10-20 | 中国烟草总公司湖南省公司 | Application platform system of tobacco commercial system |
| CN102043625A (en) * | 2010-12-22 | 2011-05-04 | 中国农业银行股份有限公司 | Workflow operation method and system |
| CN106055316A (en) * | 2016-05-19 | 2016-10-26 | 四川物联亿达科技有限公司 | Supply chain finance engine system, system establishment method and server |
| CN106357724A (en) * | 2016-08-18 | 2017-01-25 | 广州市利迪网络科技有限公司 | Uniformly integrated information management platform system |
| CN107451789A (en) * | 2016-05-31 | 2017-12-08 | 北京京东尚科信息技术有限公司 | Business flow processing method and system |
| CN107451766A (en) * | 2016-05-31 | 2017-12-08 | 上海仪美信息科技有限公司 | A kind of transport power transportation management system |
| CN110738389A (en) * | 2019-09-03 | 2020-01-31 | 深圳壹账通智能科技有限公司 | Workflow processing method and device, computer equipment and storage medium |
| CN111027921A (en) * | 2019-11-19 | 2020-04-17 | 山东中创软件商用中间件股份有限公司 | Business processing method and device, electronic equipment and storage medium |
| CN111258773A (en) * | 2018-12-01 | 2020-06-09 | 阿里巴巴集团控股有限公司 | Service call flow information processing method and device and electronic equipment |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140040903A1 (en) * | 2012-07-31 | 2014-02-06 | Meichun Hsu | Queue and operator instance threads to losslessly process online input streams events |
| CN104252472B (en) * | 2013-06-27 | 2018-01-23 | 国际商业机器公司 | Method and apparatus for parallelization data processing |
-
2020
- 2020-07-16 CN CN202010686756.1A patent/CN112068936B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6804711B1 (en) * | 1997-10-06 | 2004-10-12 | Mci, Inc. | Method and apparatus for managing call processing services in an intelligent telecommunication network |
| CN101866460A (en) * | 2010-06-28 | 2010-10-20 | 中国烟草总公司湖南省公司 | Application platform system of tobacco commercial system |
| CN102043625A (en) * | 2010-12-22 | 2011-05-04 | 中国农业银行股份有限公司 | Workflow operation method and system |
| CN106055316A (en) * | 2016-05-19 | 2016-10-26 | 四川物联亿达科技有限公司 | Supply chain finance engine system, system establishment method and server |
| CN107451789A (en) * | 2016-05-31 | 2017-12-08 | 北京京东尚科信息技术有限公司 | Business flow processing method and system |
| CN107451766A (en) * | 2016-05-31 | 2017-12-08 | 上海仪美信息科技有限公司 | A kind of transport power transportation management system |
| CN106357724A (en) * | 2016-08-18 | 2017-01-25 | 广州市利迪网络科技有限公司 | Uniformly integrated information management platform system |
| CN111258773A (en) * | 2018-12-01 | 2020-06-09 | 阿里巴巴集团控股有限公司 | Service call flow information processing method and device and electronic equipment |
| CN110738389A (en) * | 2019-09-03 | 2020-01-31 | 深圳壹账通智能科技有限公司 | Workflow processing method and device, computer equipment and storage medium |
| CN111027921A (en) * | 2019-11-19 | 2020-04-17 | 山东中创软件商用中间件股份有限公司 | Business processing method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112068936A (en) | 2020-12-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112068936B (en) | Workflow management platform and workflow management system | |
| US10346143B2 (en) | Systems and methods for transforming service definitions in a multi-service containerized application | |
| CN107515776A (en) | The uninterrupted upgrade method of business, node to be upgraded and readable storage medium storing program for executing | |
| US10366359B2 (en) | Automatic extraction and completion of tasks associated with communications | |
| CN113010827B (en) | Page rendering method and device, electronic equipment and storage medium | |
| US10951486B2 (en) | Terminal device, UI expansion method, and UI expansion program | |
| US20210224084A1 (en) | Logging of scripts executed in an information technology workflow orchestration system | |
| US11775322B2 (en) | Combining computer applications | |
| US11042390B2 (en) | Replaying operations on widgets in a graphical user interface | |
| JP2019509567A (en) | Resource loading method, service function implementing method and apparatus for application (APP) | |
| US11323526B2 (en) | Analysis and visualization of session paths | |
| Chen et al. | Survivability modeling and analysis of cloud service in distributed data centers | |
| CN110908644B (en) | Configuration method and device of state node, computer equipment and storage medium | |
| US20170011322A1 (en) | Business process managment | |
| CN111399928B (en) | Application program starting method and device, electronic equipment and readable storage medium | |
| US9971978B2 (en) | Event-based data management method and device | |
| US10462237B1 (en) | Browser-based workflows | |
| JP7201098B2 (en) | Information linkage system and information linkage method | |
| CN111506340B (en) | Business rule information processing method, device and system | |
| JP2018205843A (en) | Information processing apparatus, information processing system and information processing method | |
| US20210141562A1 (en) | Output management in command line interface | |
| CN106201776A (en) | The backup method of bag configuration file and terminal | |
| US20240211161A1 (en) | Data processing method and apparatus, electronic device, storage medium, and program product | |
| US20240346102A1 (en) | Detachable browser interface for context-aware web services | |
| US20230359952A1 (en) | Distributed Actor-Based Information System and Method |
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 |