CN113504955A - BPMN-based aerospace workflow management system - Google Patents
BPMN-based aerospace workflow management system Download PDFInfo
- Publication number
- CN113504955A CN113504955A CN202110808863.1A CN202110808863A CN113504955A CN 113504955 A CN113504955 A CN 113504955A CN 202110808863 A CN202110808863 A CN 202110808863A CN 113504955 A CN113504955 A CN 113504955A
- Authority
- CN
- China
- Prior art keywords
- command
- service instance
- management system
- bpmn
- workflow management
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
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/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4482—Procedural
- G06F9/4484—Executing subprograms
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- 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/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
- G06F9/449—Object-oriented method invocation or resolution
-
- 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/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- 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
Abstract
The utility model relates to an aerospace workflow management system based on BPMN relates to computer technology field, and wherein, aerospace workflow management system based on BPMN includes: a process engine object and a command interceptor; the process engine object is used for receiving the configuration file, acquiring the service instance set according to the configuration file, receiving the processing request sent by the client, and determining a target service instance from the service instance set according to the processing request; the flow engine object is also used for determining a command calling request according to the target service instance and sending the command calling request to the command interceptor; the command interceptor is used for processing the command calling request, determining a command object so that the command object determines a command receiver, and generating a flow processing result and sending the flow processing result to the flow engine object after the command receiver executes; and the process engine object is used for sending the process processing result to a display interface corresponding to the client for display. Therefore, operations such as flow chart construction, form drawing and the like can be quickly carried out, and the operation efficiency is improved.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to an aerospace workflow management system based on BPMN (Business Process Modeling and labeling).
Background
With the popularization of the internet, enterprises urgently need to build a flexible workflow mechanism. Most software adopts JBPM workflow engine, which is called Java Business Process Management, namely Business Process Management. Starting from JBPM5, the stove is restarted, the code base of JBMP4 is completely abandoned, and the implementation is carried out again based on drools. JBPM5 and JBPM6 seem to lack a qualified system architect, and the interface design thereof is quite thought, and basically a set of JBPM interfaces and interfaces with the same name are provided according to the interfaces of drools (an open source business rule engine which is easy to access enterprise strategies, adjust and manage), so that the realization class is continuously and repeatedly appeared, and the code system is quite disordered.
However, the JBPM workflow engine is not flexible and convenient enough, resulting in low operation efficiency.
Disclosure of Invention
To solve the above technical problem or at least partially solve the above technical problem, the present disclosure provides a BPMN-based aerospace workflow management system.
The present disclosure provides a BPMN-based aerospace workflow management system, comprising:
a process engine object and a command interceptor;
the process engine object is used for receiving a configuration file, acquiring a service instance set according to the configuration file, receiving a processing request sent by a client, and determining a target service instance from the service instance set according to the processing request;
the process engine object is also used for determining a command calling request according to the target service instance and sending the command calling request to the command interceptor;
the command interceptor is used for processing the command calling request and determining a command object so that the command object determines a command receiver, and the command receiver generates a flow processing result after executing the command and sends the flow processing result to the flow engine object;
and the process engine object is used for sending the process processing result to a display interface corresponding to the client for display.
In an embodiment of the present disclosure, the process engine object is specifically configured to:
acquiring an operation service instance, a task service instance, a warehouse service instance, a characteristic service instance, a form service instance, a management service instance and a historical service instance according to the configuration file;
and generating the service instance set according to the running service instance, the task service instance, the warehouse service instance, the characteristic service instance, the form service instance, the management service instance and the historical service instance.
In an embodiment of the present disclosure, the process engine object is specifically configured to:
analyzing the processing request to determine a target service;
and matching a target business instance corresponding to the target business from the business instance set.
In an embodiment of the present disclosure, the command interceptor is specifically configured to:
determining a command type according to the command calling request, and determining the command object according to the command type.
In an embodiment of the present disclosure, the BPMN-based aerospace workflow management system further includes: a context component;
the context component is used for storing one or more of command context information, configuration information related to the process engine and execution context information.
In an embodiment of the present disclosure, the BPMN-based aerospace workflow management system further includes: an event listener;
the event listener is used for executing specific operation at specific time so as to enable the client code to intervene in the execution of the flow; and the specific operation comprises reminding the client in a preset mode.
In an embodiment of the present disclosure, the BPMN-based aerospace workflow management system further includes: the system comprises a cache component, an asynchronous execution component and a process virtual machine;
the cache component is used for storing common information, when the information needs to be obtained, the common information is obtained from the cache component, and if the common information is not obtained, the common information is obtained from the persistent layer;
the asynchronous execution component is used for simultaneously executing multiple tasks;
the process virtual machine is used for managing all processes in the aerospace workflow management system.
In one embodiment of the present disclosure, the processing request is a flow configuration request;
the process engine object is also used for determining a plurality of process nodes according to the process configuration request;
the command interceptor is further used for establishing the connection relation of each process node and generating an approval process diagram; determining the approval authority of the process node according to the position identifier;
and the process engine object is also used for sending the examination and approval process chart to a display interface corresponding to the client for display.
In one embodiment of the present disclosure, the processing request is a form configuration request;
the flow engine object is also used for acquiring a form component and a corresponding position identifier according to the form configuration request;
the command interceptor is further used for completing addition of the form component at the position corresponding to the position identifier to generate a target form;
the command interceptor is further used for identifying the content to be filled of the target form and acquiring data corresponding to the content to be filled from a target process to complete filling of the target form;
and the process engine object is also used for sending the target form to a display interface corresponding to the client for display.
In one embodiment of the present disclosure, in the process of processing the flow processing request, reading file format data at runtime, and when history file format data is needed, reading the history file format data from a history data table; wherein the runtime file format data and the historical file format data are stored separately.
Compared with the prior art, the technical scheme provided by the embodiment of the disclosure has the following advantages:
the flow engine object is used for receiving the configuration file, acquiring a service instance set according to the configuration file, receiving a processing request sent by a client, and determining a target service instance from the service instance set according to the processing request; the flow engine object is also used for determining a command calling request according to the target service instance and sending the command calling request to the command interceptor; the command interceptor is used for processing the command calling request, determining a command object so that the command object determines a command receiver, and generating a flow processing result and sending the flow processing result to the flow engine object after the command receiver executes; and the process engine object is used for sending the process processing result to a display interface corresponding to the client for display. Therefore, operations such as flow chart construction, form drawing and the like can be quickly carried out, and the operation efficiency is improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
In order to more clearly illustrate the embodiments or technical solutions in the prior art of the present disclosure, the drawings used in the description of the embodiments or prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
Fig. 1 is a schematic structural diagram of a BPMN-based aerospace workflow management system according to an embodiment of the present disclosure;
fig. 2 is a schematic structural diagram of another BPMN-based aerospace workflow management system according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of another BPMN-based aerospace workflow management system according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of a BPMN-based aerospace workflow management system according to another embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of a BPMN-based aerospace workflow management system according to an embodiment of the present disclosure;
FIG. 6 is an exemplary diagram of a form rendering according to an embodiment of the disclosure;
FIG. 7 is an exemplary diagram illustrating a flowchart according to an embodiment of the disclosure;
FIG. 8 is a diagram illustrating an exemplary scenario of a BPMN-based aerospace workflow management system according to an embodiment of the present disclosure;
FIG. 9 is an exemplary diagram of a privilege configuration according to an embodiment of the disclosure;
FIG. 10 is an exemplary diagram of a process configuration according to an embodiment of the disclosure;
fig. 11 is an exemplary diagram of drawing a form according to an embodiment of the disclosure.
Detailed Description
In order that the above objects, features and advantages of the present disclosure may be more clearly understood, aspects of the present disclosure will be further described below. It should be noted that the embodiments and features of the embodiments of the present disclosure may be combined with each other without conflict.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure, but the present disclosure may be practiced in other ways than those described herein; it is to be understood that the embodiments disclosed in the specification are only a few embodiments of the present disclosure, and not all embodiments.
The invention provides a BPMN-based aerospace workflow management system, which avoids the low expansibility of a traditional workflow engine, realizes flexible adaptation of a flow chart and a form, can be maintained on line and provides better experience for users.
Fig. 1 is a schematic structural diagram of a BPMN-based aerospace workflow management system according to an embodiment of the present disclosure.
As shown in fig. 1, the BPMN-based aerospace workflow management system includes: a process engine object 100 and a command interceptor 200.
The process engine object 100 is configured to receive a configuration file, obtain a service instance set according to the configuration file, receive a processing request sent by a client, and determine a target service instance from the service instance set according to the processing request.
The process engine object 100 is further configured to determine a command call request according to the target service instance and send the command call request to the command interceptor 200.
The command interceptor 200 is configured to process the command call request, determine a command object, so that the command object determines a command receiver, and generate a flow processing result after the command receiver executes the command object and send the flow processing result to the flow engine object 100.
And the process engine object 100 is used for sending the process processing result to a display interface corresponding to the client for display.
In the embodiment of the present disclosure, the flow engine object 100 is specifically configured to: acquiring an operation service instance, a task service instance, a warehouse service instance, a characteristic service instance, a form service instance, a management service instance and a historical service instance according to the configuration file; and generating a service instance set according to the operation service instance, the task service instance, the warehouse service instance, the characteristic service instance, the form service instance, the management service instance and the historical service instance.
Specifically, the configuration file is integrated into the Spring IOC (IOC is an important object-oriented programming rule that can guide how to design a loosely-coupled, better program, IoC is the core content of the Spring framework) container, the Spring container reads the configuration file during initialization, creates and organizes objects according to the configuration file or metadata and stores the objects into the container, and the required objects are taken out from the IOC container during program use, i.e. the configuration objects of the process engine can be generated. The process engine object 100 is the core of the workflow business system, and all business operations are implemented by objects derived from the process engine object 100.
Specifically, the BPMN-based space workflow management system provides seven large service interfaces, which can be obtained by the process engine object 100. And when the user interacts, calling the corresponding service class according to different requirements.
In the embodiment of the present disclosure, the flow engine object 100 is specifically configured to: analyzing the processing request to determine a target service; and matching the target business instance corresponding to the target business from the business instance set.
Specifically, the user may send a processing request, such as a flow configuration request, a form configuration request, and the like, according to the actual application requirement, and select different service instances for processing according to different processing requests.
As an example, the processing request is a process configuration request, the process engine object 100 is further configured to determine a plurality of process nodes according to the process configuration request, instruct the interceptor 200, and establish a connection relationship between each process node to generate an approval process diagram; and the process engine object is also used for sending the examination and approval process chart to a display interface corresponding to the client for display. The workflow customization can be realized flexibly and conveniently, and the task flow can be modified according to the actual requirement. No code development is needed, and the configuration process only needs a few minutes.
As another example, the processing request is a form configuration request, the process engine object 100 is further configured to obtain a form component and a corresponding location identifier according to the form configuration request, instruct an interceptor, further configured to complete adding of the form component at a location corresponding to the location identifier, generate a target form, instruct the interceptor 200, further configured to identify content to be filled in the target form, and obtain data corresponding to the content to be filled from the target process to complete filling of the target form, and the process engine object 100 is further configured to send the target form to a display interface corresponding to the client for display.
In the embodiment of the present disclosure, the command interceptor 200 is specifically configured to: and determining a command type according to the command calling request, and determining a command object according to the command type.
Specifically, the BPMN-based aerospace workflow management system uses a command mode as a basic development mode, each method defined in the business class corresponds to a corresponding command object, the business class delegates various requests to the command object, the command object determines a receiver of the command, and the receiver returns a result after execution.
In one possible implementation manner of the present disclosure, as shown in fig. 2, on the basis of fig. 1, the BPMN-based aerospace workflow management system further includes: context component 300.
The context component 300 is configured to store one or more of command context information, configuration information related to the process engine, and execution context information.
In particular, context component 300 is used to store long-lived, global information. Including command context information, configuration information associated with the process engine, and execution context information.
In one possible implementation manner of the present disclosure, as shown in fig. 3, on the basis of fig. 1, the BPMN-based aerospace workflow management system further includes: an event listener 400.
An event listener 400 for performing a specific operation at a specific time to cause client code to intervene in the execution of the flow; wherein the specific operation comprises reminding the client in a preset mode.
In one possible implementation manner of the present disclosure, as shown in fig. 4, on the basis of fig. 1, the BPMN-based aerospace workflow management system further includes: cache component 500, asynchronous execution component 600, and process virtual machine 700.
The cache component 500 is configured to store common information, and when information needs to be obtained, the common information is obtained from the cache component 500 first, and if the common information is not obtained, the common information is obtained from the persistent layer.
Specifically, asynchronous execution component 600 is configured for simultaneous multitasking, and tasks that are more important need not wait for tasks that are less important to complete before they are executed, but rather are executed together.
And the process virtual machine 700 is used for managing all processes in the aerospace workflow management system.
Specifically, the process virtual machine 700 is mainly responsible for all the operation processes of the execution, circulation, and the like of the whole operation period of the process.
In one possible implementation manner of the present disclosure, in the process of processing the flow processing request, reading file format data during running, and when history file format data is needed, reading history file format data from the history data table; wherein the runtime file format data and the historical file format data are stored separately.
In particular, the separation of runtime and historical data is also followed in terms of table structure design, such design can quickly read runtime file format data, and only read from a special historical data table when the historical file format data needs to be queried. The design mode can greatly improve the data access efficiency, and particularly, the data can still quickly react when the data is accumulated in a month and a month.
Thus, the modeled flow is stored in a file format. The method has a simpler and more robust interface, is more friendly to user experience, supports the hot deployment at any time after the BPMN-based aerospace workflow management system is started, has more friendly and easy-to-use editing plug-ins and online plug-ins, and depends on fewer computer file format packages.
It should be noted that the BPMN-based aerospace workflow management system of the present disclosure may further include a persistence framework, which is a very critical and important component in the application architecture, and functions to hide the underlying complexity of application data persistence, help manage object relational mapping and data persistence requirements, serve as an "intermediary" layer to provide automatic persistence, and load objects from Java applications to database tables.
The disclosed BPMN-based aerospace workflow management system can execute commands through optimal query statements to maintain maximum performance in speed.
The BPMN-based space workflow management system of the present disclosure natively supports the Spring framework (created due to the complexity of software development), which is particularly important for enterprise applications: spring framework integration can be easily carried out, and transaction management and expression analysis are very convenient.
Therefore, the business process management application program with rich functions, light weight and high efficiency can be constructed through a plurality of business services provided by the BPMN-based aerospace workflow management system.
In a possible implementation manner of the present disclosure, the process engine object 100 is further configured to obtain a form component and a corresponding location identifier according to the form configuration request, instruct the interceptor, further configured to add the form component to the location corresponding to the location identifier to generate a target form, instruct the interceptor 200, further configured to identify content to be filled in the target form, and obtain data corresponding to the content to be filled from the target process to complete filling of the target form, and the process engine object 100 is further configured to send the target form to a display interface corresponding to the client for display.
Specifically, a large number of composite form assemblies can be developed according to project experience and market research results, and the variable requirements of users are met. Through algorithms such as a coordinate moving algorithm, table nesting and the like, a user is allowed to add form components in a dragging mode, and operation complexity is reduced.
As an example of a scenario, as shown in fig. 5, the space workflow management system based on BPMN may receive a request sent by a client for performing corresponding processing, such as form configuration and flowchart configuration.
For example, as shown in a form drawing scenario of fig. 6, a BPMN-based space workflow management system has a dynamic form function, and besides a self-contained basic component, the form component can be re-developed according to project experience and market research results, so that a large number of composite form components are provided, for example, data of other processes (which require a user to have a corresponding process viewing right) are automatically filled, other functional modules and even other system data are obtained, a designated file is downloaded, and various complex requirements of the user can be met, and the filling difficulty of the user is reduced.
The form component applies algorithms such as an element moving algorithm, a table nesting algorithm, a hypertext markup language text conversion algorithm, component coverage and the like, so that a user can complete component addition in a mouse dragging mode: the left component is selected by the mouse, the left component is pressed and dragged to the position to be added on the right side, when the mouse is loosened, the component is automatically added, the operation is simple and visual, time and labor are saved, and errors can be avoided; the front-end and back-end communication and parameter transmission are carried out through Hypertext Transfer Protocol (HTTP) and Hypertext Transfer Protocol (Http), the adaptability of the component is improved by matching with a data dictionary configuration function, and a user can adapt to different form requirements by only changing parameters filled in the component configuration.
For example, the flow chart drawing scenario shown in fig. 7 and the flow node configuration scenario shown in fig. 8 are the same page, and in the page, operations such as drawing the flow chart, adding a flow node, setting a gateway, and setting flow conditions, and information such as an identifier, an auditor, and a monitoring event of the flow node may be set. The flow is executed to each node, and the judgment is carried out according to the configuration, and the flow branches are moved to different flow branches to execute various flow conditions.
The present disclosure also develops a complete set of organizational structure setup modules and permission modules to combine with. The configuration of each department, each person and the configuration of the authority are more convenient. As shown in the organizational structure and authority configuration scenario of fig. 9, a user inputs information of organizational structures such as departments and personnel of using units in an organizational structure management module, and assigns roles (such as "general manager", "division leader", "staff", and the like), when configuring a flow node auditor in the flow chart drawing scenario shown in fig. 7 and the flow node configuration scenario shown in fig. 8, the system pushes a flow audit task to a user of a specified position for approval according to the information in the organizational structure when the flow reaches the specified node, and therefore problems of flow reconfiguration, flow interruption and the like caused by personnel change, division reorganization and the like are avoided, and resource waste, time loss and property loss are avoided.
More specifically, as shown in fig. 10, the contents of the flowchart drawing picture, the flow node configuration, and the form drawing are all combined, the flow nodes, the form, and the reviewer are associated with each other, the flow can be released for use, in this page, a monitoring event and a reminding content can be configured, and when the flow reaches a designated node, other functions or operations can be triggered; according to the configured reminding mode, the user can be approved and reminded in the modes of mails, short messages, in-station mails and the like, and the process approval efficiency is improved.
As an example of a scenario, as shown in fig. 11, there are many application scenarios of the BPMN-based aerospace workflow management system of the present disclosure, such as process application, process monitoring, process approval, interface service, business modeling, and solution, and thus, the system has good extensibility and flexibility.
Therefore, support for different process languages can be flexibly realized through adaptation of an Application Programming Interface (API), and rapid development support can be performed if customization operation is required for the process specification in a specific field at the later stage of a product.
And, through the basic service support that the unpacking is available, it is simpler to deploy and integrate, the basic function is more complete, it is stable to operate in the actual application environment, the ORM (Object Relational Mapping) framework used at the same time, and it is Mybatis (a persistent layer framework based on Java) to store in the special Object-Mapping file, the optimization space to the performance is relatively larger, the visual designer based on web page rather than installing application, it is available to cross-platform multi-terminal, convenient and fast.
In addition, the intuitive dragging type form and flow design interface is simpler and more understandable when being applied and accords with the operation habit of ordinary people.
The aerospace workflow management system based on the BPMN is used for receiving a configuration file through a process engine object, acquiring a service instance set according to the configuration file, receiving a processing request sent by a client, and determining a target service instance from the service instance set according to the processing request; the flow engine object is also used for determining a command calling request according to the target service instance and sending the command calling request to the command interceptor; the command interceptor is used for processing the command calling request, determining a command object so that the command object determines a command receiver, and generating a flow processing result and sending the flow processing result to the flow engine object after the command receiver executes; and the process engine object is used for sending the process processing result to a display interface corresponding to the client for display. Therefore, through the visual layout system, the flow chart is quickly constructed, the form is drawn, the flow event is configured, the automation of the work flow is realized, the enterprise operation efficiency is improved, the flexible flow configuration and the dynamic form editing are realized, the flow can adapt to the change of various flow personnel departments, the system structure is flexible, and the plug-and-play hot plug function can be realized with various plug-ins and systems.
It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The foregoing are merely exemplary embodiments of the present disclosure, which enable those skilled in the art to understand or practice the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. An aerospace workflow management system based on business process modeling and labeling BPMN, characterized by comprising: a process engine object and a command interceptor;
the process engine object is used for receiving a configuration file, acquiring a service instance set according to the configuration file, receiving a processing request sent by a client, and determining a target service instance from the service instance set according to the processing request;
the process engine object is also used for determining a command calling request according to the target service instance and sending the command calling request to the command interceptor;
the command interceptor is used for processing the command calling request and determining a command object so that the command object determines a command receiver, and the command receiver generates a flow processing result after executing the command and sends the flow processing result to the flow engine object;
and the process engine object is used for sending the process processing result to a display interface corresponding to the client for display.
2. The BPMN-based aerospace workflow management system of claim 1, wherein the process engine object is specifically configured to:
acquiring an operation service instance, a task service instance, a warehouse service instance, a characteristic service instance, a form service instance, a management service instance and a historical service instance according to the configuration file;
and generating the service instance set according to the running service instance, the task service instance, the warehouse service instance, the characteristic service instance, the form service instance, the management service instance and the historical service instance.
3. The BPMN-based aerospace workflow management system of claim 1, wherein the process engine object is specifically configured to:
analyzing the processing request to determine a target service;
and matching a target business instance corresponding to the target business from the business instance set.
4. The BPMN-based aerospace workflow management system of claim 1, wherein the command interceptor is specifically configured to:
determining a command type according to the command calling request, and determining the command object according to the command type.
5. The BPMN-based aerospace workflow management system of claim 1, further comprising: a context component;
the context component is used for storing one or more of command context information, configuration information related to the process engine and execution context information.
6. The BPMN-based aerospace workflow management system of claim 1, further comprising: an event listener;
the event listener is used for executing specific operation at specific time so as to enable the client code to intervene in the execution of the flow; and the specific operation comprises reminding the client in a preset mode.
7. The BPMN-based aerospace workflow management system of claim 1, further comprising: the system comprises a cache component, an asynchronous execution component and a process virtual machine;
the cache component is used for storing common information, when the information needs to be obtained, the common information is obtained from the cache component, and if the common information is not obtained, the common information is obtained from the persistent layer;
the asynchronous execution component is used for simultaneously executing multiple tasks;
the process virtual machine is used for managing all processes in the aerospace workflow management system.
8. The BPMN-based aerospace workflow management system of claim 1, wherein the processing request is a flow configuration request;
the process engine object is also used for determining a plurality of process nodes according to the process configuration request;
the command interceptor is further used for establishing the connection relation of each process node and generating an approval process diagram; determining the approval authority of the process node according to the position identifier;
and the process engine object is also used for sending the examination and approval process chart to a display interface corresponding to the client for display.
9. The BPMN-based aerospace workflow management system of claim 1, wherein the processing request is a form configuration request;
the flow engine object is also used for acquiring a form component and a corresponding position identifier according to the form configuration request;
the command interceptor is further used for completing addition of the form component at the position corresponding to the position identifier to generate a target form;
the command interceptor is further used for identifying the content to be filled of the target form and acquiring data corresponding to the content to be filled from a target process to complete filling of the target form;
and the process engine object is also used for sending the target form to a display interface corresponding to the client for display.
10. The BPMN-based aerospace workflow management system of claim 1,
reading file format data during operation in the process of processing the flow processing request, and reading the historical file format data from a historical data table when the historical file format data is needed; wherein the runtime file format data and the historical file format data are stored separately.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110808863.1A CN113504955A (en) | 2021-07-16 | 2021-07-16 | BPMN-based aerospace workflow management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110808863.1A CN113504955A (en) | 2021-07-16 | 2021-07-16 | BPMN-based aerospace workflow management system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113504955A true CN113504955A (en) | 2021-10-15 |
Family
ID=78013041
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110808863.1A Pending CN113504955A (en) | 2021-07-16 | 2021-07-16 | BPMN-based aerospace workflow management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113504955A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103279840A (en) * | 2013-06-08 | 2013-09-04 | 北京首钢自动化信息技术有限公司 | Workflow engine implement method based on dynamic language and event processing mechanism |
| CN105046408A (en) * | 2015-06-25 | 2015-11-11 | 国网山东省电力公司 | Configurable workflow realization method and system |
| CN111724144A (en) * | 2020-07-17 | 2020-09-29 | 江苏苏宁银行股份有限公司 | Bank transaction workflow engine system |
| CN112068936A (en) * | 2020-07-16 | 2020-12-11 | 石化盈科信息技术有限责任公司 | Workflow management platform and workflow management system |
| CN112101895A (en) * | 2020-08-24 | 2020-12-18 | 中国电子科技集团公司第三十八研究所 | Establishment method and system supporting adaptation of workflow client and workflow engine |
| CN112465448A (en) * | 2020-11-11 | 2021-03-09 | 中国人民大学 | Cross-organization workflow operation method and system based on block chain |
-
2021
- 2021-07-16 CN CN202110808863.1A patent/CN113504955A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103279840A (en) * | 2013-06-08 | 2013-09-04 | 北京首钢自动化信息技术有限公司 | Workflow engine implement method based on dynamic language and event processing mechanism |
| CN105046408A (en) * | 2015-06-25 | 2015-11-11 | 国网山东省电力公司 | Configurable workflow realization method and system |
| CN112068936A (en) * | 2020-07-16 | 2020-12-11 | 石化盈科信息技术有限责任公司 | Workflow management platform and workflow management system |
| CN111724144A (en) * | 2020-07-17 | 2020-09-29 | 江苏苏宁银行股份有限公司 | Bank transaction workflow engine system |
| CN112101895A (en) * | 2020-08-24 | 2020-12-18 | 中国电子科技集团公司第三十八研究所 | Establishment method and system supporting adaptation of workflow client and workflow engine |
| CN112465448A (en) * | 2020-11-11 | 2021-03-09 | 中国人民大学 | Cross-organization workflow operation method and system based on block chain |
Non-Patent Citations (1)
| Title |
|---|
| 郭煜昆: "基于工作流的可定制政务系统的设计与实现", 《中国优秀硕士学位论文全文数据库 信息科技辑》 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9800675B2 (en) | Methods for dynamically generating an application interface for a modeled entity and devices thereof | |
| Zimmermann | Architectural decisions as reusable design assets | |
| US10635408B2 (en) | Method and apparatus for enabling agile development of services in cloud computing and traditional environments | |
| JP5031819B2 (en) | Declarations for transformations in service sequences | |
| US20130067456A1 (en) | Application configuration framework for enterprise resource planning application installation | |
| US11557088B2 (en) | Generating space models from map files | |
| WO2016165321A1 (en) | Method and apparatus for establishing requirement meta model for high-speed train | |
| US8978041B2 (en) | Service virtualization container | |
| US8694559B2 (en) | Using database content for multiple business data systems connected to one database | |
| CN113504955A (en) | BPMN-based aerospace workflow management system | |
| US9059992B2 (en) | Distributed mobile enterprise application platform | |
| CN115543428A (en) | Simulated data generation method and device based on strategy template | |
| EP4198713A1 (en) | A method for handling and processing executable data flows based on design of a process | |
| US10417051B2 (en) | Synchronizing shared resources in an order processing environment using a synchronization component | |
| US20210398079A1 (en) | Workflow management and interaction between reference software and visual collaboration software | |
| CN114661851A (en) | Online lightweight quick response natural resource space information processing method | |
| Wieland et al. | Context model for representation of business process management artifacts | |
| US20140047459A1 (en) | Integrating software solution units | |
| US20180349823A1 (en) | Systems and methods for generating and managing service appointments | |
| US11880342B2 (en) | Embedded reference object and interaction within a visual collaboration system | |
| CN113486024B (en) | Data dictionary information transmission method and device, storage medium and electronic equipment | |
| Ghosal et al. | Agent based Simulation for Intelligent Manufacturing Integration | |
| US10203984B2 (en) | Data structure for multiple executable tasks | |
| Jablonski et al. | Deriving biological applications from domain specific process models | |
| CN116127213A (en) | Label management method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20211015 |