CN112068936A - Workflow management platform and workflow management system - Google Patents
Workflow management platform and workflow management system Download PDFInfo
- Publication number
- CN112068936A CN112068936A CN202010686756.1A CN202010686756A CN112068936A CN 112068936 A CN112068936 A CN 112068936A CN 202010686756 A CN202010686756 A CN 202010686756A CN 112068936 A CN112068936 A CN 112068936A
- Authority
- CN
- China
- Prior art keywords
- instance
- instruction
- layer
- flow
- service
- 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
- 238000000034 method Methods 0.000 claims abstract description 382
- 230000008569 process Effects 0.000 claims abstract description 369
- 238000010586 diagram Methods 0.000 claims description 11
- 238000011112 process operation Methods 0.000 claims description 3
- 238000007726 management method Methods 0.000 description 58
- 230000006870 function Effects 0.000 description 26
- 238000012544 monitoring process Methods 0.000 description 12
- 238000005516 engineering process Methods 0.000 description 11
- 230000000694 effects Effects 0.000 description 9
- 238000012545 processing Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 238000000638 solvent extraction Methods 0.000 description 4
- 230000010354 integration Effects 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
- 230000008901 benefit Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 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
- 230000006872 improvement Effects 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000002955 isolation 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
- 238000011084 recovery Methods 0.000 description 1
- 238000005096 rolling process Methods 0.000 description 1
- 238000013515 script Methods 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 238000000844 transformation Methods 0.000 description 1
- 230000003245 working effect Effects 0.000 description 1
Images
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, wherein a presentation layer in the workflow management platform calls an API interface of an access layer to generate a flow instantiation instruction based on the flow instantiation operation of a user, 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 used for reading stored flow definition data and running configuration data corresponding to the flow template from a storage layer, and the flow instance is generated according to the business ID, the flow template, the flow definition data corresponding to the flow template and the running configuration data, so as to create a plurality of flow instances, and when the flow instances are started by the flow engine, the flow instance is executed by using a thread to which a thread identifier corresponding to the instance identifier of each flow instance belongs according to the corresponding relationship between the instance identifier of each flow instance and the thread identifier of the thread, the dirty data phenomenon can be effectively avoided, and the execution performance of the process instance 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 technologies, Web-based workflow technologies have been developed sufficiently. Workflows can be extended to multiple enterprises over the Web and will enable collaborative work among multiple Web-based workflow servers. Through the development of many years, the structure of the workflow management system has been developed from the original structure which can only support a single working group environment to the structure which can support the workflow environment of an enterprise level (even among enterprises). A workflow instance may be distributed across different servers and clients via local area networks, wide area networks, and the impact of a server failure will be minimized. Therefore, the expandability, the practicability and the management capability of the system are greatly improved.
For example, in the enterprise application, the workflow management system usually has the condition that workflow services are concurrent, but when a plurality of workflow services are executed in parallel in the workflow management system, because each workflow service has data intersection during execution, a dirty data phenomenon may exist, and the system performance is poor during execution.
In the invention
The workflow management platform and the workflow management system provided by the embodiment of the invention can effectively avoid the dirty data phenomenon and effectively improve the performance of the process instance in 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, 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 programming interface) interface of the access layer to generate a process instantiation instruction based on process instantiation operation of a user, wherein the process instantiation instruction comprises a service ID (identity);
the access layer is used for issuing a process instantiation instruction generated by the presentation layer;
the business logic layer is used for acquiring a business ID of the process instantiation instruction and a process template corresponding to the process instantiation instruction when the process instantiation instruction issued by the presentation layer is monitored, reading stored process definition data and operation configuration data corresponding to the process template from the storage layer by using a process engine, and generating a process instance according to the business ID, the process template and the process definition data and the operation configuration data corresponding to the process template, thereby creating a plurality of process instances;
and the business logic layer is also used for executing the process instance by utilizing the thread which the thread identifier corresponding to the instance identifier of each process instance belongs to according to the corresponding relation between the instance identifier of each process instance and the thread identifier of the thread when the process engine is utilized to start the plurality of process instances.
Optionally, in the workflow management platform, for each process instance, the process instance includes at least one process node, and when the at least one process node includes a process execution operation node, the service logic layer sends a process execution operation interface to the presentation layer when executing the process operation node of the process instance by using a thread to which a thread identifier corresponding to the instance identifier of the process instance belongs;
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 (application programming interface) of the access layer to generate an execution instruction based on the flow execution operation, wherein the execution instruction comprises a service ID (identity) and a tenant ID;
the access layer is further configured to issue the execution instruction, obtain a target process instance corresponding to the service ID based on the service ID in the execution instruction, and obtain a process node corresponding to the tenant ID in the execution instruction in the target process instance;
the business logic layer is further configured to search a thread identifier corresponding to the instance identifier of the target process instance when the execution instruction issued by the presentation layer is monitored, and execute the execution instruction by using the thread to which the thread identifier belongs, so as to adjust the working state of the process node flow corresponding to the tenant ID in the execution instruction.
Optionally, in the above workflow management platform, the execution instruction includes a pass instruction, a reject instruction, a select instruction, a return instruction, or a tag instruction.
Optionally, in the workflow management platform, for each process instance, the process instance includes at least one process node, and when the at least one process node includes a callback node, the presentation layer is further configured to invoke an API interface of the access layer to generate a callback instruction based on a process 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 process instance corresponding to the service ID based on the service ID in the callback instruction;
and the service logic layer is further used for acquiring a target process instance corresponding to the service ID based on the service ID in the callback instruction when the callback instruction issued by the presentation layer is monitored, and calling a callback function corresponding to the callback instruction at the callback node by using a thread corresponding to the target process instance and executing the callback function.
Optionally, in the workflow management platform, for each process instance, the process instance includes at least one process node, and when the at least one process node includes an event node, 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 a user, where the event instruction includes a service ID;
the access layer is also used for issuing the event instruction and acquiring a target process instance corresponding to the service ID based on the service ID in the event instruction;
and the service logic layer is further configured to, when the event instruction issued by the presentation layer is monitored, obtain a target process instance corresponding to the service ID based on the service ID in the event instruction, and process the event instruction at the event node by using a thread corresponding to the target process instance.
Optionally, in the above workflow management platform, the storage layer is further configured to store the stored data after performing library division and table division by using a distributed database technology when storing the data.
Optionally, in the above workflow management platform, the service logic layer is further configured to create a plurality of threads when the plurality of process instances are started by using the process engine, allocate a thread identifier to each thread, allocate an instance identifier to each process instance, 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 the 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 diagram by using an SVG technology and a flow instance.
Optionally, in the above workflow management platform, the service logic layer includes at least one of an Spr i ng component, an 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 boottrap component.
In a second aspect, the present application further provides a workflow management system, including an electronic device and the above workflow management platform, where the electronic device is configured to operate the workflow management platform.
Compared with the prior art, the embodiment in the scheme has the following advantages or beneficial effects:
the embodiment of the invention discloses a flow workflow management platform and a workflow management system, wherein a presentation layer in the workflow management platform calls an API (application program interface) interface of an access layer to generate a flow instantiation instruction based on flow instantiation operation of a user, a service logic layer acquires a service ID (identity) of the flow instantiation instruction and a flow template corresponding to the flow instantiation instruction, a flow engine is used for reading stored flow definition data and running configuration data corresponding to the flow template from a storage layer, and the flow definition data and the running configuration data corresponding to the flow template generate a flow instance according to the service ID, the flow template and the flow definition data and the running configuration data corresponding to the flow template, so that a plurality of flow instances are created, and when the flow instances are started by the flow engine, the flow instance is executed by using a thread to which a thread identifier corresponding to the instance identifier of each flow instance belongs according to the corresponding relationship between the instance identifier of each flow instance and the thread identifier of each, the dirty data phenomenon can be effectively avoided, and the performance of the process instance in execution 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 required to be used 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 therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
FIG. 1 is a functional architecture diagram of a workflow management platform according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a process industrial application software development method according to an embodiment of the present invention.
Icon: 100-a workflow management platform; 110-a presentation layer; 120-access stratum; 130-service logic layer; 140-storage layer.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the following will describe in detail an implementation method of the present invention with reference to the accompanying drawings and embodiments, so that how to apply technical means to solve the technical problems and achieve the technical effects can be fully understood and implemented.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
Example one
Referring to fig. 1, fig. 1 is a functional architecture diagram of a workflow management platform 100 provided in this embodiment, where the workflow management platform 100 can be operated in an electronic device.
The workflow management platform 100 comprises an access layer 120, a presentation layer 110, a service logic layer 130 and a storage layer 140 which are sequentially arranged from top to bottom.
In this embodiment, the storage layer 140 is used 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 invoke an API interface of the access layer 120 to generate a process instantiation instruction based on a process instantiation operation of a user, where the process instantiation instruction includes a service ID.
The access layer 120 is configured to issue a process instantiation instruction generated by the presentation layer 110.
The business logic layer 130 is configured to, when monitoring the process instantiation instruction issued by the presentation layer 110, obtain a business ID of the process instantiation instruction and a process template corresponding to the process instantiation instruction, read, by using a process engine, stored process definition data and operation configuration data corresponding to the process template from the storage layer 140, and generate a process instance according to the business ID, the process template, and the process definition data and the operation configuration data corresponding to the process template, thereby creating a plurality of process instances.
The service logic layer 130 is further configured to execute the process instance 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 above workflow management platform 100, the thread corresponding to the process instance is acquired by using the thread identifier and the instance identifier, so that all operations of the corresponding process instance are executed on the thread, thereby effectively preventing the generation of 'dirty data', and meanwhile, when a plurality of process instances need to be executed simultaneously, each process instance is executed on the corresponding thread according to the established corresponding relationship between each thread and each process instance, so as to achieve the purpose of quickly executing all operations on the process instance, and further effectively improving the execution performance of the workflow management platform 100.
In this embodiment, the access stratum 120 includes a load balancing component SLB/Nginx, where load balancing is a basic network service, and is mainly used to solve company service concurrent pressure, enhance network processing capability, reduce resource pressure of a single device, and improve overall service performance.
The access layer 120 is also used to provide an API interface, wherein the API interface is some predefined function or convention for linking different components of the software system. The purpose is to provide applications and developers the ability to access a set of routines based on certain software or hardware without having to access native code or understand the details of the internal workings.
The access layer 120 provides an API interface to enable the generated process instances to have a uniform process integration specification, so as to better specify when executing the process instances, such as implementing the standardization of the approval business process, and in addition, since the process instances have a uniform process integration specification, when the workflow management platform 100 is applied to a system, the rapid integration and upgrade are implemented, thereby reducing the system maintenance cost.
The presentation layer 110 calls an API interface of the access layer 120 based on a process instantiation operation of a user to access data in the storage layer 140 by using the API interface when generating a process instantiation instruction, thereby generating a process instantiation instruction corresponding to the instantiation operation from the instantiation operation and the data or instruction corresponding to the operation stored in the storage layer 140.
It should be noted that the service ID in the instantiation instruction is the unique identifier of the process instance corresponding to the instantiation instruction, the process template, the process definition data and the operation configuration data corresponding to different service IDs are different, and the correspondingly generated process instances are also different, for example, the service IDs corresponding to the reimbursement approval process instance, the leave approval process instance, the approval process instance, and the seal approval process instance are different.
It is to be understood that the process instantiation instruction may further include an initiator or an initiating mechanism, etc.
The presentation layer 110 may generate a graphical interface, which may then be presented to a user. The presentation layer may also be used to obtain user input, for example, obtain user input based on the presented graphical interface.
The procedure instantiation instruction generated by the presentation layer 110 based on the procedure instantiation operation of the user and calling the API interface of the access layer 120 may specifically be: the presentation layer 110 presents a process instance generation interface to a user, and receives a process instantiation operation input by the user based on the process instance generation interface, so as to invoke an API interface of the access layer 120 to generate a process instantiation instruction based on the process instantiation operation.
It is to be appreciated that the process instantiation generation interface presented to the user by the presentation layer 110 can be generated based on the user's operation.
Specifically, when the workflow management platform 100 is applied to an electronic device, the presentation layer 110 is configured to generate a process instance generation interface based on an operation of a user and display the interface on the electronic device, and obtain a process instantiation instruction, which is generated by invoking an API interface of the access layer 120 by a process instantiation operation that is input by the user based on the process instance generation interface and received by the electronic device, where the process instantiation operation may be an operation of selecting a process instantiation operation option displayed on the electronic device by the user, or may be a gesture operation that is input to the electronic device by the user and corresponds to the process instantiation operation, for example, a gesture operation such as sliding in a preset direction or drawing a circle on a touch screen of the electronic device is performed, and the setting is performed according to an actual requirement, which is not specifically limited herein.
In order to enable the presentation layer 110 to generate an interface, for example, a process instance generates an interface, in this embodiment, the presentation layer 110 further includes an html component, a css component, a jquery component, and a boottrap component.
The html component can be composed of other common components: icons, a toolbar, a slider, and an image display area.
It should be noted that the html component can use the html language description file to display the effect through the WWW browser when it needs to be exposed.
html language is a language for creating web page files, and displays contents such as images, sounds, pictures, characters, animations, videos and the like through a mark type instruction (Tag). And the common application of html language is to bring the technology of hypertext-jump from one topic to another topic by clicking a mouse, jump from one page to another page, and the file link hypertext transfer protocol with hosts around the world prescribes the rules and operations followed by a browser when running html documents.
The css component is a DOM structure + component class according to convention, and the component display effect can be realized, for example: grid layout, navigation, breadlines, tabs, forms, buttons, badges, reference blocks, etc.
The cs component can be used for accurately controlling the typesetting of element positions in an interface to be displayed in a pixel level, supports almost all font and font styles and has the capability of editing webpage objects and model styles. And by utilizing cs components, the format code can be simplified.
A jquery component which can realize plug-in effects with functions of mouse rolling zooming and dragging in items like a map application, and can add mark points with callback functions. It contains a large number of predefined widgets, and a set of tools for building high-level elements (e.g., draggable, dragged, ordered).
The Bootstrap component is a component that includes a number of re-usable components for creating images, drop-down menus, navigation, warning boxes, pop-up boxes, modal dialog boxes, tabbed 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 the user to select corresponding options. The realization effect is similar to the function of the confirm in js, and the judgment of determining and canceling is provided for the user.
Because the presentation layer 110 has the html component, the css component, the jquery component, and the boottrap component, it can generate an interface and present it to a user, and obtain an interface input operation based on the presentation by the user, thereby achieving the purpose of interaction.
The process engine in the business logic layer 130 is the core of the workflow management platform 100, and is oriented to a service administrator (super administrator), and mainly functions to receive instructions, process instructions, monitor services, and manage services. The flow engine can be deployed in multiple numbers as required, the queue configuration of each tenant is read according to the flow configuration after the engine is started, instructions (an instantiation instruction, an execution instruction, a callback instruction and an event instruction) in the queue are loaded according to the period, and then the instruction processor is respectively executed to process business logic.
The instantiation instruction is responsible for loading the template startup flow instance.
The execution instruction is responsible for business approval and process circulation such as process passing, rejection, signature adding, return and the like.
The callback instruction is responsible for calling a callback function configured by the service system, and if a task to be handled is generated, the service system is called to send a mail callback, and a target user is informed of the fact that the task to be handled is unprocessed in a mail mode.
The process definition data acquired by the business logic layer 130 may include a process template corresponding to the business ID and a process instance name, activity information, participant information, and the like corresponding to the process template.
The operation configuration data acquired by the service logic layer 130 may include configuration data, such as routing information, routing rule information, and the like, required by the process instance corresponding to the service ID during operation.
As can be seen from the above, the storage layer 140 should store the process definition data and the operation configuration data corresponding to different service IDs.
After the business 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 flow instances according to the business ID, the flow template, and the flow definition data and operation configuration data corresponding to the flow template, for facilitating the subsequent execution of each flow instance, a queue may be created for each flow instance, and the flow instance, the flow definition data and operation configuration data corresponding to the flow instance, and other data related to the flow instance may be stored in the queue. It is possible to further avoid a phenomenon that dirty data is generated due to data of a plurality of process instances overlapping each other when there are a plurality of process instances executed at the same time.
In addition, since the flow engine can simultaneously execute and process multiple instantiation instructions or perform multiple instantiation operations and dynamically allocate the number of threads, when the flow engine is used to generate a flow instance, the business logic layer 130 can 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 business logic layer 130 monitors only one process instantiation instruction each time, and when the business logic layer 130 starts a plurality of process instances by using the process engine, a plurality of threads are created, a thread identifier is assigned to each thread, an instance identifier is assigned to each process instance, and a corresponding relationship between the instance identifier of each process instance and the thread identifier of each thread is established, so that the thread to which the thread identifier corresponding to the instance identifier of each process instance belongs is used to execute the process instance, thereby implementing a technique of multi-thread technology isolation, and ensuring that the start and execution of each process instance are executed on different threads.
When the business logic layer 130 monitors a plurality of process instantiation instructions issued by the presentation layer 110 at the same time, a plurality of threads may also be created, so that when the business logic layer 130 acquires the business ID of each process instantiation instruction and the process template corresponding to each process instantiation instruction, one thread is correspondingly allocated to each process instantiation instruction, and the thread corresponding to each process instantiation instruction is used to generate a process instance according to the business ID of the process instance, the process template, and the process definition data and the operation configuration data corresponding to the process template.
When executing the generated multiple process instances simultaneously, executing the process instance by utilizing the thread to which the thread identifier corresponding to the instance identifier of each process instance belongs according to the corresponding relation between the instance identifier of each process instance and the thread identifier of the thread.
Through the arrangement, the processes of the process instances in the process instantiation and operation of the processes are decoupled and asynchronous by using the distributed queue technology, the efficiency of the workflow engine for executing the instructions is improved, and the workflow engine can be used for remedying when the process instances are abnormally interrupted, so that the data can be correctly recovered.
It should be noted that the process instance is a business process, and the process instance generally includes a plurality of process nodes, which may include, but are not limited to, one or more of a process execution operation node, a call-back node, and an event node. Each process node is respectively corresponding to participator and routing information
When a process instance includes a process execution operation node and is executed to the process execution operation node at business logic layer 130, a process execution operation interface may be sent to the user so that the user inputs the process execution operation to generate an execution instruction (e.g., pass, reject, select, return, tag, etc.), to change the state of the process node to execute the next node or stop execution, etc.
When the process instance includes a callback node or an event node, the presentation layer 110 may call the API interface of the access layer 120 to generate a callback instruction based on a process callback operation of the user, or generate an event instruction based on an API interface of the access layer 120 of an event execution operation of the user, so that the business logic layer 130 executes the callback instruction or executes the event instruction when it listens for 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 unstructured data.
When the data is stored in a structured data storage manner, the data may be stored by using a Relational Database (RDS), or may be stored by using a Distributed Relational Database Service (DRDS).
The relational database is a stable, reliable and elastically-telescopic online database service, the RDS supports MySQL, SQL Server, PostgreSQL and PPAS (Postgre Plus Advanced Server), and a complete solution scheme in the aspects of disaster tolerance, backup, recovery, monitoring, migration and the like is provided.
The distributed relational database service is a distributed database product which is developed and released independently aiming at solving the bottleneck problem of the stand-alone database service. The DRDS is highly compatible with the MySQL protocol and grammar, supports automatic horizontal splitting, online smooth expansion and contraction capacity, elastic expansion and transparent read-write separation, and has the full-life-cycle operation and maintenance control capability of the database.
When the data is stored in the unstructured data Storage mode, the data can be stored in an Object Storage Service (OSS) mode, the Object Storage Service is a cloud Storage Service which is high in mass, safe, low in cost and high in reliability, the cloud Storage Service is suitable for storing files of any type, the capacity and the processing capacity are flexibly expanded, multiple Storage types are selected, and the Storage cost is comprehensively optimized.
Optionally, in this embodiment, the storage layer 140 is further configured to, when storing data, store the stored data after performing library partitioning and table partitioning by using a distributed database technology.
The data stored in the storage layer 140 is subjected to database partitioning and table partitioning by using a distributed database technology, so that the service data is uniformly partitioned on different database nodes, high concurrency pressure is effectively dispersed, and the service throughput is improved.
In this embodiment, to further avoid the phenomenon of dirty data and improve the efficiency of the process engine to run the process instance, for each process instance, the process instance includes at least one process node, and when the at least one process node includes a process execution operation node, the business logic layer 130 sends a process execution operation interface to the presentation layer 110 when executing the process operation node of the process instance by using the thread to which the thread identifier corresponding to the instance identifier of the process instance belongs.
The presentation layer 110 is further configured to obtain a flow execution operation input by the user based on the flow execution operation interface, and call the 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 process instance corresponding to the service ID based on the service ID in the execution instruction, and obtain a process node corresponding to the tenant ID in the execution instruction in the target process instance.
The business logic layer 130 is further configured to search a thread identifier corresponding to the instance identifier of the target process instance when monitoring the execution instruction issued by the presentation layer 110, and execute the execution instruction by using the thread to which the thread identifier belongs, so as to adjust the working state of the process node flow corresponding to the tenant ID in the execution instruction.
Through the arrangement, the instantiation operation and the execution operation of the same process instance are executed in the thread corresponding to the process instance, so that the 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 a tag instruction.
In order to facilitate the execution of the callback operation during the execution of the process instance and further avoid the occurrence of the dirty data phenomenon, in this embodiment, for each process instance, the process instance includes at least one process node, and when the at least one process node includes the callback node, the presentation layer 110 is further configured to invoke the API interface of the access layer 120 to generate a callback instruction based on the process callback operation of the user, where the callback instruction includes the service ID.
The access layer 120 is further configured to issue the callback instruction, and obtain a target process 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 the callback instruction issued by the presentation layer 110, obtain a target process 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 process instance.
The callback function is a function called by a function pointer. If a pointer (address) to a function is passed as a parameter to another function, the function pointed to by the pointer is called a callback function. 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 process instance are executed in the thread corresponding to the process instance, so that the dirty data phenomenon can be further avoided.
To facilitate executing the event instruction during the process instance execution process, in this embodiment, for each process instance, the process instance includes at least one process node, and when the at least one process node includes the event node, the presentation layer 110 is further configured to invoke an API interface of the access layer 120 to generate the event instruction based on the event execution operation of the user, where the event instruction includes the service ID.
The access layer 120 is further configured to issue the event instruction, and obtain a target process instance corresponding to the service ID based on the service ID in the event instruction.
The service logic layer 130 is further configured to, when monitoring the event instruction issued by the presentation layer 110, obtain a target process instance corresponding to the service ID based on the service ID in the event instruction, and process 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 instruction of the same process instance are executed in the thread corresponding to the process instance, so that the dirty data phenomenon can be further avoided.
In order to allow the user to view each flow node in the flow instance, in this embodiment, the presentation layer 110 is further configured to generate a workflow diagram by using SVG technology and the flow instance.
It should be noted that SVG is an open-standard vector graphics language, which uses XML defined language to describe two-dimensional vector and vector/raster graphics, and provides 3 types of graphics objects, including: vector graphics (for example: a path consisting of straight lines and curved lines), images (images), text (text). The graphic objects can also be grouped, added with styles, transformed, combined and the like, and the feature set comprises nested transformations (nestdtransformations), clipping paths (clippingpaths), alpha masks (alphamasks), filter effects (filterartifacts), template objects (templateobjects) and other extensions (extensions).
SVG can be used to design high-resolution Web graphics pages, i.e., SVG images are interactive and dynamic, animation elements can be embedded in SVG files or animations can be defined by scripts. The user can directly draw the image with the code, open the SVG image with any word processing tool, make the image have interactive function by changing part of the code, and can insert into HTML at any time to watch through a browser.
The SVG technology is utilized to generate the work flow chart, so that a user can conveniently check the work flow chart, a flow prejudging function of the flow example can be provided for the user, and the trend of the flow in the flow example can be conveniently prejudged according to the business data of the user and the flow template.
The process engine also has an effect of providing an engine management and control console, and a service administrator can check the process execution state through the engine management and control console, for example, check the workflow diagram and the execution state of each process node in the workflow diagram, so that monitoring of abnormal processes and processing as required can be realized.
Example two
The embodiment of the present application provides a workflow management system, which includes an electronic device and the workflow management platform 100 in the first embodiment, where the electronic device is configured to operate 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 and the memory are electrically connected directly or indirectly to enable data transmission or interaction, for example, the components 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 (DSP), an Application Specific Integrated Circuit (ASIC), a discrete gate or transistor logic device, a discrete hardware component, and may implement or execute the methods, steps, and logic blocks disclosed in the embodiments of the present Application. Further, a 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 (RAM), Read Only Memory (ROM), Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), and electrically 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 devices provided by the embodiments of the present application may also have fewer or more components described above, or the same configuration.
In addition, each component may be implemented by software, hardware, or a combination thereof, for example, each component may further include a communication component or a multimedia component, which is not specifically limited herein and may be set according to an actual requirement.
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, a KONG service gateway, a Web application server, and an ElasticSearch server, etc. The workflow management platform may be run on one or more of the servers described above.
EXAMPLE III
Referring to fig. 2, 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 operate the workflow management platform 100, the user terminal may be one or multiple user terminals, and the one or multiple user terminals are in communication connection with the server.
The user terminal can be a mobile phone, a computer or a tablet computer, and is not particularly limited herein, and may 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 operating the workflow management platform 100, when the access layer 120 in the workflow management platform 100 receives the process instantiation operation, the access layer 120 invokes an API interface of the access layer 120 to generate a process instantiation instruction based on the process instantiation operation, where the process instantiation instruction includes a service ID.
The access layer 120 obtains and issues a process instantiation instruction generated by the presentation layer 110.
The business logic layer 130 is configured to monitor whether the access layer 120 issues an instruction in real time, and when a process instantiation instruction issued by the presentation layer 110 is monitored, obtain a business ID of the process instantiation instruction and a process template corresponding to the process instantiation instruction, read, by using a process engine, stored process definition data and running configuration data corresponding to the process template from the storage layer 140, and generate a process instance according to the business ID, the process template, and the process definition data and the running configuration data corresponding to the process template, thereby creating a plurality of process instances.
The process instance created by the business logic layer 130 includes: instance name, activity information (e.g., approval, reimbursement, application, etc.), routing information, participant information, and routing rule information, etc.
The process instance may generally include a plurality of process nodes, which may include one or more of an execution node, a callback node, or an event node.
When the process engine is used to start the multiple process instances, the business logic layer 130 executes the process instance 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 interaction between the user terminal and the server is utilized to realize the acquisition of the thread corresponding to the process instance by utilizing the thread identification and the instance identification, and the thread executes all operations on the corresponding process instance, thereby effectively preventing the generation of 'dirty data'.
Meanwhile, when a plurality of process instances need to be executed simultaneously, a plurality of threads are created, and the corresponding relation between each thread and each process instance is established, so that all operations on the process instances can be executed quickly, and the execution performance of the workflow management system can be effectively improved.
To further avoid the phenomenon of dirty data and improve the efficiency of the process engine running the process instance, optionally, in this embodiment:
for each process instance, the business logic layer 130 sends a process execution operation interface to the presentation layer 110 when executing the corresponding process instance by using a thread and executing the process execution operation node to the process instance.
The presentation layer 110 sends the process execution operation interface to the corresponding user terminal based on the participant information and the routing rule information of the process instance corresponding to the process execution operation node to display the process execution operation interface on the user terminal, thereby facilitating the user to input the process execution operation based on the process execution operation interface.
And the user terminal sends the flow execution operation to the server when receiving the flow execution operation input by the user based on the flow execution operation interface displayed on the user terminal. It is understood that the flow execution operation sent by the server should be understood as operation information.
When acquiring a process execution operation input by a user based on a process execution operation interface, the presentation layer 110 invokes an API interface of the access layer 120 to generate an execution instruction based on the process 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, a tag instruction, or the like.
The access layer 120 obtains and issues the execution instruction generated by the presentation layer 110, obtains a target process instance corresponding to the service ID based on the service ID in the execution instruction, and obtains a process node corresponding to the tenant ID in the execution instruction in the target process instance.
In the process of monitoring the instruction issued by the access layer 120 in real time, the service logic layer 130 searches for a thread identifier corresponding to the instance identifier of the target process 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 process node flow corresponding to the tenant ID in the execution instruction. For example, the flow node is adjusted to a pass, reject, return, add, or select state.
Through the arrangement, the instantiation operation and the execution operation of the same process instance are executed in the thread corresponding to the process instance, so that the dirty data phenomenon can be further avoided.
It can be understood that, when the process instance includes a plurality of process execution operation nodes, in the process of executing the corresponding process instance by the thread, each process execution operation node should be executed in sequence, and when each process execution operation node is executed, the execution process is the same as or similar to the execution process of executing the process execution operation node of the corresponding process instance by the thread for each process instance, and therefore, the description is omitted here.
In order to facilitate the execution of the callback operation during the execution of the process instance and further avoid the occurrence of the dirty data phenomenon, in this embodiment, for each process instance, the process instance includes at least one process node, and when the at least one process node includes the callback node, the user terminal may further receive the callback operation input by the user, and when receiving the callback operation, send the callback operation to the server. It is understood that the callback operation should be the corresponding operation information of the callback operation.
When the server operates the workflow management platform 100, the presentation layer 110 of the workflow management platform 100 receives the callback operation, and invokes the API interface of the access layer 120 to generate a callback instruction based on the flow callback operation, where 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 a target process instance corresponding to the service ID based on the service ID in the callback instruction.
In the process of monitoring the instruction issued by the access layer 120 in real time, when monitoring the callback instruction issued by the presentation layer 110, the service logic layer 130 acquires a target process instance corresponding to the service ID based on the service ID in the callback instruction, and calls a callback function corresponding to the callback instruction at the callback node by using a thread corresponding to the target process instance and executes the callback function.
Through the setting, the instantiation operation and the callback operation of the same process instance are executed in the thread corresponding to the process instance, so that the dirty data phenomenon can be further avoided.
In order to facilitate the execution of the event instruction in the process of executing the process instance, in this embodiment, for each process instance, the process instance includes at least one process node, when the event node is included in the at least one process 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 performing operation should be operation information corresponding to the event performing operation. For example, the event operation information such as mail or short message is sent to the user.
When the server runs the workflow management platform 100, the presentation layer 110 of the workflow management platform 100 receives the event execution operation, and invokes an API interface of the access layer 120 to generate an event instruction based on the event execution operation, where the event instruction includes a service ID.
When the access layer 120 acquires the event instruction generated by the presentation layer 110, the access layer issues the event instruction, and acquires the target process instance corresponding to the service ID based on the service ID in the event instruction.
When the service logic layer 130 monitors 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, a target process instance corresponding to the service ID is obtained based on the service ID in the event instruction, and the event instruction is processed 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 process instance are executed in the thread corresponding to the process instance, so that the dirty data phenomenon can be further avoided.
To sum up, the embodiment of the present invention provides a workflow management platform 100 and a workflow management system, wherein a presentation layer 110 in the workflow management platform 100 invokes an API interface of an access layer 120 to generate a flow instantiation instruction based on a flow instantiation operation of a user, a business logic layer 130 obtains a business ID of the flow instantiation instruction and a flow template corresponding to the flow instantiation instruction, reads stored flow definition data and running configuration data corresponding to the flow template from a storage layer 140 by using a flow engine, and generates a flow instance according to the business ID, the flow template, and the flow definition data and the running configuration data corresponding to the flow template, thereby creating a plurality of flow instances, and when starting the plurality of flow instances by using the flow engine, executes the flow instance by using a thread to which a thread identifier corresponding to the instance identifier of each flow instance belongs according to a correspondence relationship between the instance identifier of each flow instance and the thread identifier of the thread, the dirty data phenomenon can be effectively avoided, and the performance of the process instance in execution can be effectively improved.
In the several embodiments provided in the present application, it should be understood that the disclosed system and method may be implemented in other ways. The embodiments described above are merely illustrative, and the flowcharts and block diagrams in the figures, for example, 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 an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent 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 such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The 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 changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
It is to 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 above description is only an embodiment adopted for facilitating understanding of the present invention, and is not intended to limit the present invention. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure, and it is intended that all such changes and modifications as fall within the true spirit and scope of the disclosure be embraced therein. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (11)
1. A 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 programming interface) interface of the access layer to generate a process instantiation instruction based on process instantiation operation of a user, wherein the process instantiation instruction comprises a service ID (identity);
the access layer is used for issuing a process instantiation instruction generated by the presentation layer;
the business logic layer is used for acquiring a business ID of the process instantiation instruction and a process template corresponding to the process instantiation instruction when the process instantiation instruction issued by the presentation layer is monitored, reading stored process definition data and operation configuration data corresponding to the process template from the storage layer by using a process engine, and generating a process instance according to the business ID, the process template and the process definition data and the operation configuration data corresponding to the process template, thereby creating a plurality of process instances;
and the business logic layer is also used for executing the process instance by utilizing the thread which the thread identifier corresponding to the instance identifier of each process instance belongs to according to the corresponding relation between the instance identifier of each process instance and the thread identifier of the thread when the process engine is utilized to start the plurality of process instances.
2. The workflow management platform of claim 1, wherein for each process instance, the process instance comprises at least one process node, and when the at least one process node comprises a process execution operation node, the business logic layer sends a process execution operation interface to the presentation layer when executing the process operation node of the process instance by using a thread to which a thread identifier corresponding to the instance identifier of the process instance belongs;
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 (application programming interface) of the access layer to generate an execution instruction based on the flow execution operation, wherein the execution instruction comprises a service ID (identity) and a tenant ID;
the access layer is further configured to issue the execution instruction, obtain a target process instance corresponding to the service ID based on the service ID in the execution instruction, and obtain a process node corresponding to the tenant ID in the execution instruction in the target process instance;
the business logic layer is further configured to search a thread identifier corresponding to the instance identifier of the target process instance when the execution instruction issued by the presentation layer is monitored, and execute the execution instruction by using the thread to which the thread identifier belongs, so as to adjust the working state of the process node flow corresponding to the tenant ID in the execution instruction.
3. The workflow management platform of claim 2 wherein the execution directive comprises a pass directive, a reject directive, a select directive, a return directive, or a tag directive.
4. The workflow management platform of claim 1, wherein for each process instance, the process instance includes at least one process node, and when a callback node is included in the at least one process node, the presentation layer is further configured to invoke an API interface of the access layer to generate a callback directive based on a process callback operation of the user, wherein the callback directive includes a service ID;
the access layer is also used for issuing the callback instruction and acquiring a target process instance corresponding to the service ID based on the service ID in the callback instruction;
and the service logic layer is further used for acquiring a target process instance corresponding to the service ID based on the service ID in the callback instruction when the callback instruction issued by the presentation layer is monitored, and calling a callback function corresponding to the callback instruction at the callback node by using a thread corresponding to the target process instance and executing the callback function.
5. The workflow management platform of claim 1, wherein for each process instance, the process instance comprises at least one process node, and when the at least one process node comprises an event node, the presentation layer is further configured to invoke an API interface of the access layer to generate an event directive based on an event execution operation of the user, wherein the event directive comprises a service ID;
the access layer is also used for issuing the event instruction and acquiring a target process instance corresponding to the service ID based on the service ID in the event instruction;
and the service logic layer is further configured to, when the event instruction issued by the presentation layer is monitored, obtain a target process instance corresponding to the service ID based on the service ID in the event instruction, and process the event instruction at the event node by using a thread corresponding to the target process instance.
6. The workflow management platform of claim 1, wherein the storage layer is further configured to, when storing the data, perform banking and post-tabulation storage of the stored data using distributed database techniques.
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 process instances are started by the process engine, assign a thread identifier to each of the threads, assign an instance identifier to each of the process instances, establish a correspondence between the instance identifier of each of the process instances and the thread identifier of each of the threads, and execute the process instance by using the thread to which the thread identifier corresponding to the instance identifier of each of the process instances belongs.
8. The workflow management platform of claim 1, wherein the presentation layer is further configured to generate a workflow diagram utilizing SVG techniques and process instances.
9. The workflow management platform of claim 1 wherein said business logic layer comprises at least one of a Spring component, a SpringMVC component, a MyBatis component and a 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 boottrap component.
11. A workflow management system comprising an electronic device and a workflow management platform of any one of claims 1 to 10, the electronic device being adapted to operate 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 true CN112068936A (en) | 2020-12-11 |
| CN112068936B 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) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112700310A (en) * | 2021-01-19 | 2021-04-23 | 汇通数科智能科技有限公司 | Transaction order data optimization processing method based on E-commerce platform |
| CN112799646A (en) * | 2021-02-09 | 2021-05-14 | 北京字节跳动网络技术有限公司 | Task running method and device |
| CN112883697A (en) * | 2021-03-17 | 2021-06-01 | 新奥数能科技有限公司 | Workflow list generation method and device, electronic equipment and computer readable medium |
| CN112905270A (en) * | 2021-02-19 | 2021-06-04 | 北京百度网讯科技有限公司 | Workflow implementation method, device, platform, electronic equipment and storage medium |
| CN113283730A (en) * | 2021-05-17 | 2021-08-20 | 鲁班(北京)电子商务科技有限公司 | Universal approval process application method and device |
| CN113504955A (en) * | 2021-07-16 | 2021-10-15 | 航天中认软件测评科技（北京）有限责任公司 | BPMN-based aerospace workflow management system |
| CN114936245A (en) * | 2022-04-28 | 2022-08-23 | 北京远舢智能科技有限公司 | Method and device for integrating and processing multi-source heterogeneous data |
| CN116308148A (en) * | 2023-03-02 | 2023-06-23 | 中电金信软件有限公司 | Activity flow processing method and device and electronic equipment |
| CN116306591A (en) * | 2023-05-18 | 2023-06-23 | 深圳市东信时代信息技术有限公司 | Flow form generation method, device, equipment and medium |
Citations (12)
| 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 |
| US20140040903A1 (en) * | 2012-07-31 | 2014-02-06 | Meichun Hsu | Queue and operator instance threads to losslessly process online input streams events |
| US20150006468A1 (en) * | 2013-06-27 | 2015-01-01 | International Business Machines Corporation | Parallelization of data processing |
| 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 |
| CN107451766A (en) * | 2016-05-31 | 2017-12-08 | 上海仪美信息科技有限公司 | A kind of transport power transportation management system |
| CN107451789A (en) * | 2016-05-31 | 2017-12-08 | 北京京东尚科信息技术有限公司 | Business flow processing method and 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 |
-
2020
- 2020-07-16 CN CN202010686756.1A patent/CN112068936B/en active Active
Patent Citations (12)
| 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 |
| US20140040903A1 (en) * | 2012-07-31 | 2014-02-06 | Meichun Hsu | Queue and operator instance threads to losslessly process online input streams events |
| US20150006468A1 (en) * | 2013-06-27 | 2015-01-01 | International Business Machines Corporation | Parallelization of data processing |
| CN106055316A (en) * | 2016-05-19 | 2016-10-26 | 四川物联亿达科技有限公司 | Supply chain finance engine system, system establishment method and server |
| CN107451766A (en) * | 2016-05-31 | 2017-12-08 | 上海仪美信息科技有限公司 | A kind of transport power transportation management system |
| CN107451789A (en) * | 2016-05-31 | 2017-12-08 | 北京京东尚科信息技术有限公司 | Business flow processing method and 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 |
Cited By (14)
| 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 |
| CN112700310A (en) * | 2021-01-19 | 2021-04-23 | 汇通数科智能科技有限公司 | Transaction order data optimization processing method based on E-commerce platform |
| CN112799646A (en) * | 2021-02-09 | 2021-05-14 | 北京字节跳动网络技术有限公司 | Task running method and device |
| CN112905270A (en) * | 2021-02-19 | 2021-06-04 | 北京百度网讯科技有限公司 | Workflow implementation method, device, platform, electronic equipment and storage medium |
| 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 |
| CN112883697A (en) * | 2021-03-17 | 2021-06-01 | 新奥数能科技有限公司 | Workflow list generation method and device, electronic equipment and computer readable medium |
| CN113283730A (en) * | 2021-05-17 | 2021-08-20 | 鲁班(北京)电子商务科技有限公司 | 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 |
| CN114936245A (en) * | 2022-04-28 | 2022-08-23 | 北京远舢智能科技有限公司 | Method and device for integrating and processing multi-source heterogeneous data |
| CN116308148A (en) * | 2023-03-02 | 2023-06-23 | 中电金信软件有限公司 | Activity flow processing method and device and electronic equipment |
| CN116306591A (en) * | 2023-05-18 | 2023-06-23 | 深圳市东信时代信息技术有限公司 | Flow form generation method, device, equipment and medium |
| CN116306591B (en) * | 2023-05-18 | 2023-10-03 | 深圳市东信时代信息技术有限公司 | Flow form generation method, device, equipment and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112068936B (en) | 2024-05-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112068936B (en) | Workflow management platform and workflow management system | |
| US10762277B2 (en) | Optimization schemes for controlling user interfaces through gesture or touch | |
| CN107515776A (en) | The uninterrupted upgrade method of business, node to be upgraded and readable storage medium storing program for executing | |
| JP2021064353A (en) | Long-running workflows for document processing using robotic process automation | |
| US8898178B2 (en) | Solution monitoring system | |
| US8166491B2 (en) | Method and system for providing a configurable action launchpad | |
| US20210304142A1 (en) | End-user feedback reporting framework for collaborative software development environments | |
| US20150261832A1 (en) | Storing service items in association with views | |
| JP6817253B2 (en) | Display control device, display control method, and display control program | |
| US11150919B2 (en) | Logging of scripts executed in an information technology workflow orchestration system | |
| US10951486B2 (en) | Terminal device, UI expansion method, and UI expansion program | |
| US20120151311A1 (en) | System and method for generating a customized task list | |
| US11271881B2 (en) | Integration of an email client with hosted applications | |
| CN110599112A (en) | Method and device for developing and maintaining network page | |
| CN113835835A (en) | Method and device for creating consistency group and computer-readable storage medium | |
| CN115390720A (en) | Robotic Process Automation (RPA) including automatic document scrolling | |
| CN113656041A (en) | Data processing method, device, equipment and storage medium | |
| EP2988469A1 (en) | A method and apparatus for updating a user interface of one program unit in response to an interaction with a user interface of another program unit | |
| CN114791984B (en) | Navigation tree display method, navigation tree display device and electronic equipment | |
| US20240111504A1 (en) | Automatic Generation of Chat Applications from No-Code Application Development Platforms | |
| US11704014B1 (en) | Supporting micro swipes for generating custom user interface responses | |
| CN116432618A (en) | Form generation method and system | |
| CN110765098B (en) | Flow operation prediction system and method | |
| JP7021990B2 (en) | Source creator | |
| US8250195B2 (en) | Leveraging synchronous communication protocols to enable asynchronous application and line-of-business behaviors |
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 |