CN115098078A - Processing method of flow service, electronic equipment and storage medium - Google Patents
Processing method of flow service, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN115098078A CN115098078A CN202211022431.9A CN202211022431A CN115098078A CN 115098078 A CN115098078 A CN 115098078A CN 202211022431 A CN202211022431 A CN 202211022431A CN 115098078 A CN115098078 A CN 115098078A
- Authority
- CN
- China
- Prior art keywords
- flow
- engine
- application program
- component
- item
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/24—Object-oriented
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The present disclosure relates to the field of computer technologies, and in particular, to a processing method of a flow service, an electronic device, and a storage medium. The method is realized by an application program and a micro service platform, wherein a standardized flow component provided by the micro service platform is packaged in the application program, and a flow engine is deployed in the micro service platform, and the method comprises the following steps: the method comprises the steps that a flow component of an application program receives flow form information submitted by a user, a flow request is triggered, the flow request contains a flow item identifier, the flow component of the application program submits the flow request to a flow engine through an API gateway, the flow engine acquires flow item information according to the flow item identifier in the flow request, a flow instance is created according to the flow item information, the flow engine runs the flow instance, and a running result is sent to the flow component of the application program through the API gateway.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a processing method of a flow service, an electronic device, and a storage medium.
Background
At present, workflow (workflow) is to perform automated execution management on a business process through a computer, mainly solving the problem of automatically transferring documents, information or tasks among a plurality of participants according to a certain predetermined rule, and realizing an expected business target or promoting the realization of the business target. The workflow software is widely applied to the fields of administration, personnel finance, key business and the like, enables the business to be visualized and plays an important role in a standardized business process.
However, most of the current deployment modes of workflow software are deployed together with or separately from service systems or applications, and the service systems in different fields cannot share the workflow function, which causes various wastes of resources and higher development cost.
Disclosure of Invention
The embodiment of the disclosure provides a processing method of a process service, an electronic device and a storage medium, which can solve the problem of sharing workflow functions among business systems in different fields.
In a first aspect, an embodiment of the present application provides a method for processing a flow service, which is implemented by an application program and a micro service platform, wherein a standardized flow component provided by the micro service platform is encapsulated in the application program, and a flow engine is deployed in the micro service platform. The method comprises the following steps: the method comprises the steps that a process component of an application program receives process form information submitted by a user and triggers a process request, the process request contains a process item identifier, the process component of the application program submits the process request to a process engine through an API gateway, the process engine obtains the process item information according to the process item identifier in the process request and creates a process instance according to the process item information, the process engine operates the process instance and sends an operation result to the process component of the application program through the API gateway.
Optionally, a rule engine and organization structure information are deployed in the microservice platform, and the flow engine is invoked to determine a flow node variable according to the flow project information, the flow form information, and the organization structure information in the process of running the flow instance.
Optionally, a message manager is deployed in the micro service platform, and when the process engine runs to the process node of the process instance, the message manager is called to issue a to-be-handled process task to a process to-be-handled person according to the process node variable.
Optionally, a flow designer is deployed in the microservice platform, and before the flow component of the application program triggers the flow request, the method further includes: the flow designer receives a flow design instruction of a user to generate a flow project, the flow project comprises a flow project identifier and flow project information, and the flow designer issues the flow project to the flow engine.
Optionally, the process designer provides a visualized process design interface for a user to design a process on the process design interface.
Optionally, after the flow designer issues the flow item to the flow engine, the method further includes: and the micro service platform generates a flow component corresponding to the flow item according to the flow item information, and encapsulates the flow component into the standardized flow component.
Optionally, the application updates the standardized flow components provided by the microservice platform through the API gateway.
Optionally, the process engine is a flowable process engine.
In a second aspect, an embodiment of the present application provides an electronic device, which has a processor and a memory, where the memory stores computer instructions, and when the computer instructions are executed by the processor, the electronic device implements the steps of the method described in any one of the first aspect.
In a third aspect, an embodiment of the present application provides a storage medium, on which computer instructions are stored, and when executed by a processor, the computer instructions implement the steps of the method according to any one of the first aspect.
The method and the device for processing the flow have the advantages that the standardized flow components are packaged in the multiple application programs, a user can trigger the flow request by submitting the form information in the components, the flow request is submitted to the micro service platform flow engine through the API gateway, the flow engine acquires the flow item information according to the flow item identification in the flow request, creates the flow instance, runs the flow, and sends the running result to the flow components of the application programs through the API gateway. By the method, the shared API gateway is provided, so that a plurality of application programs share one process engine, the reusability of codes is improved, the resource waste caused by repeated deployment of the process engine is avoided, and the development cost is reduced.
Other features of embodiments of the present disclosure and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, which is to be read in connection with the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the disclosure and together with the description, serve to explain the principles of the embodiments of the disclosure.
Fig. 1 shows a flowchart of a processing method of a flow service according to an embodiment of the present disclosure.
Fig. 2 shows a block diagram of an electronic device of an embodiment of the disclosure.
Detailed Description
Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, the numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present invention unless specifically stated otherwise.
The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the invention, its application, or uses.
Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.
In all examples shown and discussed herein, any particular value should be construed as merely illustrative, and not limiting. Thus, other examples of the exemplary embodiments may have different values.
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, further discussion thereof is not required in subsequent figures.
The embodiment of the application discloses a processing method of flow service, which is realized through an application program and a micro service platform, wherein a standardized flow component provided by the micro service platform is packaged in the application program, and a flow engine is deployed in the micro service platform. As shown in FIG. 1, the method includes steps S11-S14.
In an example of this embodiment, the micro service platform may be a distributed micro service architecture based on SpringCloud, and provide workflow-related services and functions for the application program through the form of micro service. For example, the functions used by the workflow complete flow, such as flow design, approver and approval rule configuration, flow variable configuration, flow and example data storage, flow operation and the like, are provided for the application program.
In an example of this embodiment, the micro service platform is deployed with a Flowable business process engine, and the Flowable business process engine provides functions used by a workflow for an application. The Flowable is a lightweight Business Process engine written by Java, and can be used for deploying BPMN2.0 (Business Process Modeling Notation) Process definitions, and creating or running Process instances of the Process definitions.
In one example of this embodiment, the application may be any application or system that has a process service requirement. The mobile phone can be mounted on a user terminal such as a mobile phone, a computer, a tablet computer, and the like. The micro service platform can provide a standard and unified UI user interface and an API gateway, and different application programs can interact with the service platform through the standard and unified API gateway.
In an example of this embodiment, the application program may obtain the standardized flow components provided by the micro service platform in advance through the API gateway, or update the standardized flow components provided by the micro service platform through the API gateway. By utilizing the standardized process components, the application program can carry out the operation related to the process service through the micro service platform. Specifically, the standardized flow components may include operation components, flow charts, buttons, forms, and the like of some common flow services, for example, an operation component of a leave asking flow, an operation component of an reimbursement flow, and the like, and a user may start and perform flow operations such as leave asking and reimbursement, for example, filling a leave asking sheet and an reimbursement sheet, by using the flow components on an application program.
In another example of this embodiment, the process components may further include a development component, and a user may perform secondary development and modification on a specific process project according to the requirements of its own system or application program through the development component in the process components to meet actual requirements.
In step S11, the flow component of the application receives the flow form information submitted by the user, and triggers a flow request, where the flow request includes a flow item identifier.
In an example of this embodiment, a user may fill in flow form information corresponding to a relevant flow on a flow component in an application program. For example, taking the leave asking process as an example, the user may fill in specific leave asking days, leave asking reasons and leave asking types on a process component, such as a leave asking form component, where the leave asking days are 1 day, the leave asking reasons are a doctor and the leave asking types are a sick and fake. After the user fills in and submits the flow form information on the flow components of the application program, the flow components generate and trigger flow requests, and the flow requests are submitted to a flow engine through an API gateway, so that the flow can be smoothly carried out. And, the flow request also contains a flow item identifier, which is an identifier of a specific flow item type corresponding to the flow request, for example, the item identifier of the leave-asking flow is 1, and the item identifier of the reimbursement flow is 2, when the flow request generated by the flow component is the leave-asking flow request, the flow request will have the item identifier of the leave-asking flow 1, so that when the micro service platform receives the request, the type of the specific flow item to be executed is identified.
It should be noted that, although the examples describe specific examples of the flow type, the flow form information and the flow item identifier, those skilled in the art should understand that the present disclosure is not limited thereto, and those skilled in the art can flexibly set the specific flow type, the flow form information and the flow item identifier according to actual needs or personal preferences.
In step S12, the process component of the application submits the process request to the process engine through the API gateway.
In step S13, the process engine obtains the process item information according to the process item identifier in the process request, and creates a process instance according to the process item information.
In an example of this embodiment, after a flow component in an application triggers a flow request, the flow request may be submitted to a flow engine of the microservices platform through an API gateway. The flow engine may determine, according to the flow item identifier in the flow request, a specific flow item corresponding to the flow request, for example, the flow item identifier in the flow request is 1, and after identifying the flow item identifier, the flow engine may determine the specific flow item corresponding to the identifier, for example, it is determined that the flow item identifier 1 corresponds to a leave-requesting flow item, and obtain flow item information of the corresponding flow item. The flow project information can be information of some basic flow projects provided by the microservice platform, and can also be information of flow projects designed by the user. Specifically, the process item information may be information of the process itself. Taking the leave asking process as an example, the information of the process itself may include that when the leave asking date is less than 3 days, the leave asking staff leads the head to approve, when the leave asking date is more than or equal to 3 days, the leave asking staff leads the head to approve after the head to approve, and after the approval, the leave asking process is completed. After the flow item information is acquired, a flow instance can be created according to the flow item information. The flow example is a specific actual flow needing to be operated, and when the micro service platform receives a flow request, a specific flow example is correspondingly generated and operated.
It should be noted that, although the example describes a specific example of the flow item information, those skilled in the art should understand that the present disclosure is not limited thereto, and those skilled in the art can flexibly set the flow item information according to actual needs or personal preferences.
And step S14, the process engine runs the process instance and sends the running result to the process component of the application program through the API gateway.
In an example of this embodiment, after the process engine creates a specific process instance, the process instance may be further run, and the process instance may be sequentially run according to specific process steps, and the running result may be sent to a process component required by the application program through the API gateway. The operation result of the flow instance includes not only the final operation result at the end of the flow but also the operation result of each flow step. Specifically, for example, taking a leave asking process as an example, a user a triggers a leave asking process through a process component of an application program, the specific number of days of leave asking is 1 day, a leave asking process instance of the user a is created by a process engine, the leave asking process requires a leader B of the user a to approve the leave asking process one day, the process engine can send a leave asking approval form of the user a to the process component of the application program of the user B through an API gateway when the process engine runs to an approval step, the process engine can continue to run after approval is carried out through the process component, and a next step after approval is executed, and an approval result is sent to the process component of the application program of the user a through the API gateway.
In an example of this embodiment, the application program of which specific user is identified by the account numbers of different users in the application program.
In this example, the application program is packaged with a standardized flow component, a user can trigger a flow request by submitting form information in the component, and submit the flow request to the micro service platform flow engine through the API gateway, and the flow engine acquires flow item information according to a flow item identifier in the flow request, creates the flow instance, runs the flow, and sends a running result to the flow component of the application program through the API gateway. By the method, the shared API gateway is provided, so that a plurality of application programs share one process engine, the reusability of codes is improved, the resource waste caused by repeated deployment of the process engine is avoided, and the development cost is reduced.
In an example of this embodiment, a rule engine and organization architecture information are deployed in a micro service platform, and in a process of running a process instance, the process engine calls the rule engine to determine a process node variable according to process item information, process form information, and organization architecture information.
In one example of the embodiment, a rule engine and organization architecture information are also deployed in the microservice platform. The organization architecture information may be pre-stored in a database of the microservices platform. The rule engine provides support for decision information required in the process of running the process, and determines branch flow variables in the process of running the process, such as an approver and the like, and the variables are determined by the rule engine.
In an example of this embodiment, in the process of running an instance by the flow engine, when some node steps need to determine a variable, the rule engine may be called to determine the variable of the flow node. For example, taking the leave asking process as an example, the process item information is that "when the leave asking date is less than 3 days, the leave asking person leads the head to approve, when the leave asking date is greater than or equal to 3 days, the head further leads the head to approve, and after the approval, the leave asking process is completed. The flow form information submitted by the user A is' leave request days are 1 day, the leave request reason is to see a doctor, and the leave request type is to be sick and fake. In the organization structure information, the leader of the previous level of the user A is B, the leader of the previous level is C, and the rule engine can determine the variable of the examination and approval node in the false process of the user A according to the process project information, the process form information and the organization structure information, namely the examination and approval person is B.
It should be noted that, although the examples describe specific examples of the rule engine, those skilled in the art should understand that the present disclosure is not limited thereto, and those skilled in the art can flexibly set the rules according to actual needs or personal preferences.
In this example, the micro service platform further deploys a rule engine and organization architecture information, and the flow engine can determine the variables of the flow nodes by calling the rule engine when running, so that the flow can run accurately and intelligently, and the user experience is improved.
In an example of this embodiment, a message manager is deployed in the micro service platform, and when the flow engine runs to a flow node of the flow instance, the message manager is called to issue a to-do flow task to a flow to-do person according to a flow node variable.
In an example of this embodiment, the micro service platform is further deployed with a message manager, and when the process engine runs to some nodes of the process instance, the process engine may determine a node variable of the node, and a person to be handled of the node sends a proxy process task to the person. Specifically, the to-do message may be sent to the application of the person through the message manager. For example, when the leave asking process runs to the approval node and B is required to approve, the message manager may send a message to the application program of B through the API interface to notify B that there is a backlog to be processed, and a process component in the application program of B may display a further approval task for approval by B.
In an example of this embodiment, a flow designer is deployed in the micro service platform, and before a flow component of the application triggers a flow request, the method further includes: the flow designer receives a flow design instruction of a user to generate a flow project, the flow project comprises a flow project identifier and flow project information, and the flow designer issues the flow project to the flow engine.
In one example of this embodiment, a flow designer provides a visualized flow design interface for a user to design a flow on the flow design interface.
The process designer can provide a standard and unified UI interface for the application program through the API gateway, wherein the interface comprises a process design interface, a user can send a design instruction to the process designer through a process component on the interface, and specifically, the design instruction can comprise instructions for configuring an approver, determining an approval rule, configuring variable information required in process operation and the like. And the flow designer generates a corresponding flow project according to the instruction, wherein the flow project comprises a flow project identifier, flow project information and the like. After the process item is generated, the process item can be released to a process engine for use.
In an example of this embodiment, after the flow item is generated, the flow item may be further stored in a database of the microservice platform for later use.
In this example, the micro service platform is also provided with a flow designer, so that a user can design a flow project by himself or change the flow project through the flow designer, and the micro service platform can provide more and more flexible flow services, thereby improving the experience of the user.
In one example of this embodiment, after the flow designer issues the flow item to the flow engine, the method further comprises: and the micro service platform generates a flow component corresponding to the flow project according to the flow project information, and encapsulates the flow component into a standardized flow component.
In an example of this embodiment, after the flow designer issues the flow designed by the user to the flow engine, the micro service platform may further generate a flow control, such as a flow form, corresponding to the flow item according to the flow item information, so that the user may trigger to execute the corresponding flow item through the flow control in the following process. For example, the flow project designed by the user is a leave asking flow project, and the micro service platform is used for carrying out approval by the leader of the last stage of the leave asking personnel according to the requirements of the flow project, for example, when the leave asking date is less than 3 days, and when the leave asking date is more than or equal to 3 days, the leave asking personnel carries out approval by the leader of the last stage. At this time, according to the flow item information, a corresponding flow component, such as a leave-asking flow form, may be generated, and the form may include the number of days of leave-asking, the reason for leave-asking, and the like. After the corresponding process components are generated, the process components can be packaged into standardized process components, so that a user can trigger and run the designed process items.
The present embodiment provides an electronic device 100, where the electronic device 100 has a processor 101 and a memory 102, and the memory 102 stores computer instructions, and the computer instructions, when executed by the processor 101, implement each process of the processing method embodiment of the flow service, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.
The present embodiment provides a computer-readable storage medium, where an executable command is stored in the storage medium, and when the executable command is executed by a processor, the process of the embodiment of the processing method for flow service is implemented, and the same technical effect can be achieved, and details are not described here to avoid repetition.
It should be noted that all actions of acquiring signals, information or data in the present application are performed under the premise of complying with the corresponding data protection regulation policy of the country of the location and obtaining the authorization given by the corresponding device/account owner.
The embodiments in the disclosure are described in a progressive manner, and the same and similar parts among the embodiments can be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the device and apparatus embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference may be made to some descriptions of the method embodiments for relevant points.
The foregoing description of specific embodiments of the present disclosure has been described. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
Embodiments of the present disclosure may be systems, methods, and/or computer program products. The computer program product may include a computer-readable storage medium having computer-readable program instructions embodied thereon for causing a processor to implement aspects of embodiments of the disclosure.
The computer-readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a Static Random Access Memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, a mechanical encoding device, such as punch cards or in-groove raised structures having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or electrical signals transmitted through electrical wires.
The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing/processing device, or to an external computer or external storage device via a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing/processing device.
The computer program instructions for carrying out operations for embodiments of the present disclosure may be assembly instructions, Instruction Set Architecture (ISA) instructions, machine related instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, the electronic circuitry may execute computer-readable program instructions to implement aspects of embodiments of the present disclosure by utilizing state information of the computer-readable program instructions to personalize the electronic circuitry, such as a programmable logic circuit, a Field Programmable Gate Array (FPGA), or a Programmable Logic Array (PLA).
Various aspects of embodiments of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.
These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable medium storing the instructions comprises an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). 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. It is well known to those skilled in the art that implementation by hardware, by software, and by a combination of software and hardware are equivalent.
Having described embodiments of the present disclosure, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope of the described embodiments. The terminology used herein is chosen in order to best explain the principles of the embodiments, the practical application, or improvements made to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
Claims (10)
1. A processing method of a flow service is realized by an application program and a micro service platform, wherein a standardized flow component provided by the micro service platform is encapsulated in the application program, and a flow engine is deployed in the micro service platform, and the method comprises the following steps:
a flow component of the application program receives flow form information submitted by a user and triggers a flow request, wherein the flow request contains a flow item identifier;
the flow component of the application program submits the flow request to the flow engine through an API gateway;
the process engine acquires process item information according to the process item identifier in the process request, and creates a process instance according to the process item information;
and the process engine operates the process instance and sends an operation result to the process component of the application program through the API gateway.
2. The method of claim 1, wherein a rule engine and organizational schema information are deployed in the microservices platform;
and in the process of running the process instance, the process engine is called to determine process node variables according to the process project information, the process form information and the organization architecture information.
3. The method of claim 2, wherein a message manager is deployed in the microservices platform;
and when the process engine runs to the process node of the process instance, calling the message manager to issue the to-be-handled process task to the process to-be-handled personnel according to the process node variable.
4. The method of claim 1, wherein a flow designer is deployed in the microservices platform;
before the flow component of the application triggers the flow request, the method further comprises:
the flow designer receives a flow design instruction of a user to generate a flow project, wherein the flow project comprises a flow project identifier and flow project information;
the flow designer issues the flow item to the flow engine.
5. The method of claim 4, wherein the flow designer provides a visualized flow design interface for a user to design a flow on the flow design interface.
6. The method of claim 4, wherein after the flow designer issues the flow item to the flow engine, the method further comprises:
and the micro service platform generates a flow component corresponding to the flow item according to the flow item information, and encapsulates the flow component into the standardized flow component.
7. The method of claim 6, wherein the application updates the standardized flow components provided by the microservice platform through the API gateway.
8. The method of claim 1, wherein the flow engine is a flowable flow engine.
9. An electronic device having a processor and a memory, the memory having stored therein computer instructions which, when executed by the processor, implement the steps of the method of any one of claims 1-8.
10. A storage medium having stored thereon computer instructions which, when executed by a processor, carry out the steps of the method of any one of claims 1 to 8.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202211022431.9A CN115098078A (en) | 2022-08-25 | 2022-08-25 | Processing method of flow service, electronic equipment and storage medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202211022431.9A CN115098078A (en) | 2022-08-25 | 2022-08-25 | Processing method of flow service, electronic equipment and storage medium |
Publications (1)
Publication Number | Publication Date |
---|---|
CN115098078A true CN115098078A (en) | 2022-09-23 |
Family
ID=83299995
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202211022431.9A Pending CN115098078A (en) | 2022-08-25 | 2022-08-25 | Processing method of flow service, electronic equipment and storage medium |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN115098078A (en) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20180139109A1 (en) * | 2016-11-15 | 2018-05-17 | Verizon Deutschland Gmbh | Sdn-based api controller |
CN112269572A (en) * | 2020-10-26 | 2021-01-26 | 北京知道未来信息技术有限公司 | Flow processing method, device, server and computer readable storage medium |
CN112465448A (en) * | 2020-11-11 | 2021-03-09 | 中国人民大学 | Cross-organization workflow operation method and system based on block chain |
CN113094037A (en) * | 2021-04-20 | 2021-07-09 | 上海携宁计算机科技股份有限公司 | Interaction method, development platform, equipment and storage medium for forms and workflows |
CN114691115A (en) * | 2022-03-30 | 2022-07-01 | 深圳市商汤科技有限公司 | Business process system generation method and device, electronic equipment and storage medium |
-
2022
- 2022-08-25 CN CN202211022431.9A patent/CN115098078A/en active Pending
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20180139109A1 (en) * | 2016-11-15 | 2018-05-17 | Verizon Deutschland Gmbh | Sdn-based api controller |
CN112269572A (en) * | 2020-10-26 | 2021-01-26 | 北京知道未来信息技术有限公司 | Flow processing method, device, server and computer readable storage medium |
CN112465448A (en) * | 2020-11-11 | 2021-03-09 | 中国人民大学 | Cross-organization workflow operation method and system based on block chain |
CN113094037A (en) * | 2021-04-20 | 2021-07-09 | 上海携宁计算机科技股份有限公司 | Interaction method, development platform, equipment and storage medium for forms and workflows |
CN114691115A (en) * | 2022-03-30 | 2022-07-01 | 深圳市商汤科技有限公司 | Business process system generation method and device, electronic equipment and storage medium |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8918709B2 (en) | Object templates for data-driven applications | |
CN103854168A (en) | Heterogeneous process to-do task centralized processing method and device | |
CN113377348A (en) | Task adjustment method applied to task engine, related device and storage medium | |
US11474842B2 (en) | Integration application creator design | |
CN111090423A (en) | Webhook framework system and method for realizing active calling and event triggering | |
CN111126948A (en) | Processing method and device for approval process | |
CN114399292A (en) | Method, computing device and medium for controlling business approval process | |
CN111752587A (en) | Batch processing method and device of small programs, electronic equipment and readable storage medium | |
CN114493185A (en) | Approval processing method, device, system, electronic equipment, storage medium and product | |
WO2022159080A1 (en) | Asynchronous distributed modular function calling | |
CN113076153A (en) | Interface calling method and device | |
CN109683992B (en) | Method and apparatus for managing objects | |
CN114443076A (en) | Mirror image construction method, device, equipment and storage medium | |
KR20150133902A (en) | System and method for developing of service based on software product line | |
CN113254825A (en) | Page generation method and device, electronic equipment and storage medium | |
CN113448570A (en) | Data processing method and device, electronic equipment and storage medium | |
Mohamed et al. | SaaS dynamic evolution based on model-driven software product lines | |
EP2810179B1 (en) | Method and system for implementing a common data interface to web services | |
CN113032004B (en) | Method, apparatus and program product for managing development jobs in a development environment | |
CN115098078A (en) | Processing method of flow service, electronic equipment and storage medium | |
CN108804442B (en) | Serial number generation method and device | |
CN111124523A (en) | Method and apparatus for initializing applications | |
CN112799699B (en) | Method and device for updating server | |
CN113296829A (en) | Method, device, equipment and computer readable medium for processing service | |
CN113592646A (en) | Intelligent contract execution method, device and system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
RJ01 | Rejection of invention patent application after publication | ||
RJ01 | Rejection of invention patent application after publication |
Application publication date: 20220923 |