Business process item analysis method and device, equipment and storage medium
By receiving change signals and converting them into standardized events, processing them according to priority, querying and evaluating connection lines, and creating target event instances, the problem of business process flow interruption without human intervention is solved, and the continuity and efficiency of business processes are achieved.
Patent Information
- Application Number
- CN202510631654.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-16
- Publication Date
- 2025-09-19
AI Technical Summary
Existing business processes are prone to flow interruptions without human intervention, resulting in inefficiency and increased risk of errors. Traditional workflow systems are difficult to effectively integrate in scenarios of multi-department collaboration and multiple matters in series.
By receiving change signals, the state change signals are converted into standardized events according to predefined event mapping rules, stored in the priority event queue, and events are processed in order of priority. The event flow configuration library is queried based on the event type and attributes, the connection lines are identified, the conditional expressions are evaluated, the target event instances are created, and the state is initialized to trigger the flow.
It achieves the continuity and flexibility of business processes without human intervention, dynamically adjusts event processing priorities, reduces flow interruptions, and improves the efficiency and reliability of business processes.
Smart Images
Figure CN120672018A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of business process item design, and in particular to a business process item analysis method, device, equipment and storage medium. Background Art
[0002] In the daily operations of businesses and institutions, various business processes often have long cycles, involve numerous items, and are complex to manage. Traditional workflow systems perform well when handling single items, but they struggle when faced with complex business scenarios that require multi-departmental collaboration and the chaining of multiple items. These complex businesses often require organizing multiple independent items according to a specific sequence and conditions to form a complete business chain.
[0003] However, existing technologies are unable to effectively integrate these independent tasks into a coherent business process. When companies attempt to solve this problem with a single workflow, the process configuration often becomes overly complex and difficult to maintain and adjust. The independent operation of multiple processes makes it impossible to directly track the entire business process, making it impossible to achieve refined, phased management. More importantly, the completion of one task cannot automatically trigger the start of the next task, resulting in interrupted business flow and the need for manual intervention, which reduces efficiency and increases the risk of errors.
[0004] In view of this, this application is filed. Summary of the Invention
[0005] The present invention discloses a method, device, equipment and storage medium for analyzing business process matters, aiming to solve the problem that business flow interruption may occur in existing business processes without human intervention.
[0006] A first embodiment of the present invention provides a method for parsing business process items, including: receiving a change signal, and converting the state change signal into a standardized event according to a predefined event mapping rule, wherein the change signal includes a matter state change signal or a workflow state change signal; Storing the standardized events in a priority event queue, and processing the events in the event queue in order of priority; Querying the event flow configuration library according to the type and attributes of the event to identify all connection lines associated with the event; Evaluate the conditional expression of each connection line and determine the connection lines that meet the conditions. For the connection lines that meet the conditions, pass in the source event data and create a target event instance. Initialize the state of the target event instance to detect whether the creation is successful. If so, trigger the target event creation success event and continue the event flow.
[0007] Preferably, before receiving the change signal and converting the state change signal into a standardized event according to a predefined event mapping rule, the method further includes: Receive the matter flow design instruction input by the user and generate a matter flow chart, wherein the matter flow chart includes: multi-level matter nodes, adaptive gateway nodes and intelligent connection lines.
[0008] Preferably, the adaptive gateway node includes: Parallel gateway, used to trigger multiple subsequent events in parallel based on the completion event of an event node; Conditional gateway, used to dynamically select the path for subsequent matters based on business rules; An event gateway is used to wait for one of several possible events to occur before continuing the flow; Composite gateway, used to automatically switch gateway types based on business scenarios.
[0009] Preferably, the conditional expression for evaluating each connecting line is specifically: Load the conditional script associated with the connection line, build the script execution environment and inject the attribute data of the items in the current workflow. The script engine is called to execute the conditional script in the script execution environment, and the script execution result is converted into a Boolean value, wherein the Boolean value is used to determine whether to continue along the current connection.
[0010] Preferably, the method further includes: when an exception occurs during the execution process, recording error information and generating a default configuration failure strategy.
[0011] Preferably, the method further includes: constructing a historical log of event flow, analyzing the historical log of event flow at each preset time period to generate analysis results, and dynamically adjusting event processing priorities and resource allocation strategies according to the analysis results; The event flow history log is used to record the occurrence time, source, impact scope and processing results of each event. The analysis results include frequently occurring flow paths and abnormal patterns.
[0012] Preferably, it also includes: based on the historical logs, using supervised learning to predict future flow paths and dynamically adjusting event priorities.
[0013] A second embodiment of the present invention provides a business process item parsing device, comprising: A mapping unit, configured to receive a change signal and convert the state change signal into a standardized event according to a predefined event mapping rule, wherein the change signal includes a matter state change signal or a workflow state change signal; An event processing unit, configured to store the standardized events in a priority event queue and process the events in the event queue in order of priority; A connection line identification unit, configured to query a transaction flow configuration library according to the type and attributes of the event and identify all connection lines associated with the event; The instance creation unit is used to evaluate the conditional expression of each connection line, determine the connection lines that meet the conditions, and for the connection lines that meet the conditions, pass in the source event data and create the target event instance. The state of the target event instance is initialized to detect whether the creation is successful. If so, trigger the target event creation success event and continue the event flow.
[0014] A third embodiment of the present invention provides a business process item analysis assisting device, comprising a memory and a processor, wherein the memory stores a computer program, and the computer program can be executed by the processor to implement a business process item analysis method as described in any one of the above items.
[0015] The fourth embodiment of the present invention provides a computer-readable storage medium, characterized in that it stores a computer program, and the computer program can be executed by a processor of the device where the computer-readable storage medium is located to implement a method for parsing business process matters as described in any one of the above items.
[0016] Based on the business process item parsing method, device, equipment and storage medium provided by the present invention, by receiving a change signal, the state change signal is converted into a standardized event according to a predefined event mapping rule, then the standardized event is stored in a priority event queue, and the events in the event queue are processed in order of priority; then, the item flow configuration library is queried according to the type and attributes of the event, and all connection lines associated with the event are identified; finally, the conditional expression of each connection line is evaluated to determine the connection line that meets the condition, for the connection line that meets the condition, the source item data is passed in and a target item instance is created, the state of the target item instance is initialized to detect whether the creation is successful, and if so, the target item creation success event is triggered and the item flow continues, which solves the problem of business flow interruption in the existing business process without human intervention. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] Figure 1 This is a flowchart of a method for analyzing business process items provided by the first embodiment of the present invention; Figure 2 This is a module diagram of a business process item analysis device provided by the second embodiment of the present invention. DETAILED DESCRIPTION
[0018] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.
[0019] In order to better understand the technical solution of the present invention, the embodiments of the present invention are described in detail below with reference to the accompanying drawings.
[0020] It should be understood that the embodiments described are only a portion of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative work are within the scope of protection of the present invention.
[0021] The terms used in the embodiments of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. The singular forms "a", "an", "the" and "the" used in the embodiments of the present invention and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise.
[0022] It should be understood that the term "and / or" as used herein is merely a description of the relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.
[0023] The word "if," as used herein, may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to the determination" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)," depending on the context.
[0024] The "first" and "second" mentioned in the embodiments are merely used to distinguish similar objects and do not represent a specific ordering of the objects. It is understood that the specific order or precedence of "first" and "second" can be interchanged where appropriate. It should be understood that the objects distinguished by "first" and "second" can be interchanged where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein.
[0025] The specific embodiments of the present invention are described in detail below with reference to the accompanying drawings.
[0026] The present invention discloses a method, device, equipment and storage medium for analyzing business process matters, aiming to solve the problem that business flow interruption may occur in existing business processes without human intervention.
[0027] See also Figure 1 A first embodiment of the present invention provides a method for parsing business process items, which can be executed by a business process item parsing device (hereinafter referred to as the parsing device), and in particular, by one or more processors within the parsing device, to implement at least the following steps: S101, receiving a change signal, and converting the state change signal into a standardized event according to a predefined event mapping rule, wherein the change signal includes a matter state change signal or a workflow state change signal; In this embodiment, the analysis device can be a terminal with data processing capabilities such as a desktop computer, laptop computer, server, workstation, etc. The analysis device can be installed with a corresponding operating system and application software, and the functions required by this embodiment can be realized through the combination of the operating system and application software.
[0028] It's important to note that the event-driven engine within the parsing device first listens for state change signals from each item node and the external workflow engine. These signals, whether built-in signals like "item creation," "start," "suspend," "resume," "complete," or "cancel," as well as custom events defined by users within item nodes via Groovy scripts, are all captured and consolidated into the message bus. Upon startup, the engine loads a set of extensible "event mapping rules" from the item flow configuration library. Each rule is described in the form of a script or JSON configuration: When a source signal of a certain type (such as a workflow approval notification) is received and additional conditions are met (such as a contract value greater than 1 million), the original signal is converted into a predefined standardized event object with an item identifier, timestamp, and contextual attributes. This mapping process occurs within a dedicated, isolated script execution environment.
[0029] S102, storing the standardized event in a priority event queue, and processing the events in the event queue in order of priority; In this implementation, state change signals issued by each item node or external workflow are mapped into standardized events. The event-driven engine then encapsulates these events according to pre-configured priority rules and enqueues them in a priority event queue. This queue uses multi-dimensional priority calculations, such as factoring in event type, source system, urgency, and historical processing latency, to sort all pending events and ensure that the most important or urgent events are always prioritized when dequeuing. The queue processing module sequentially extracts events from the head of the queue, calls a dynamic parser to load associated connections, and evaluates conditions to create corresponding target item instances. For example, in a project approval scenario, the "application approval" event typically has a higher business priority than the "project termination" event. By enqueuing the "application approval" event first and dequeuing it first, the system can promptly trigger the "project preliminary review" step, ensuring the continuity of the approval process. Furthermore, for low-priority events that accumulate due to network fluctuations or sudden increases in backend service pressure, they can be flexibly deferred or batched together to avoid performance bottlenecks caused by resource competition.
[0030] S103, querying the event flow configuration library according to the type and attributes of the event, and identifying all connection lines associated with the event; In this embodiment, after receiving a standardized event, the dynamic parser first performs a matching query based on the event type and attributes in the event flow configuration library. During the design phase, this configuration library stores metadata for each smart connection (including source node identifiers, target node identifiers, trigger event type, and event attribute filtering conditions) in a graph database or relational table. When the parser receives a standardized event (e.g., an "Expert Review Passed" event with type "Review Passed" and attributes including the event ID, approver, and review opinion), the parser constructs a query statement or graph traversal operation to filter out all connection records that match the event type and meet attribute conditions (such as monetary threshold, department affiliation, and priority tag). For example, in a project approval scenario, when the "Expert Review Passed" process node issues a "Review Passed" event with a "Qualified" review opinion, the parser queries the configuration library for all connections with "Trigger Event = Review Passed AND Review Result = Qualified" and identifies the connection leading to the "Project Incoming" node. The parser then returns these connections to the process engine, allowing subsequent steps to execute conditional scripts and create target instances.
[0031] S104, evaluate the conditional expression of each connection line, determine the connection lines that meet the conditions, for the connection lines that meet the conditions, pass in the source matter data and create a target matter instance, initialize the state of the target matter instance to detect whether the creation is successful, if so, trigger the target matter creation success event and continue the matter flow.
[0032] The parsing device first loads the conditional scripts associated with the connection lines from the data store. These scripts can be written in business rule expressions using scripting languages such as Groovy and JavaScript. In a project approval business scenario, for example, the connection line from the initial project review to the expert review process might include a condition: "The project score is greater than 75 points and the project budget is within an acceptable range." These conditions are stored as scripts for dynamic parsing at runtime.
[0033] After loading the script, the parser constructs a dedicated script execution environment—an isolated context space—to ensure that script execution does not affect other parts of the system. Within this environment, the parser injects various attribute data for items in the current workflow, making this data accessible to the script. For example, the system might inject all field values from a project application form, the current project status, historical approval records, and other information. This data injection mechanism enables conditional scripts to make decisions based on the complete business context, rather than being limited to simple fixed conditions.
[0034] Next, the parsing device invokes the script engine to run the conditional script within the constructed execution environment. The script engine parses and executes the script code, calculating a result based on the injected data. For example, the script might check whether the project score exceeds a threshold, whether the project type meets specific conditions, or perform more complex business rule calculations. The result of the script execution is ultimately converted into a Boolean value (true or false), which is used to determine whether to continue the transaction along the current connection line.
[0035] Furthermore, this embodiment can support complex business rule expressions and can handle complex judgment logic involving multiple variables and multiple conditions; secondly, the conditional script can be modified and updated while the system is running, and can adapt to changes in business rules without changing the system architecture; for the connecting lines where the conditional expression evaluates to true, the system will enter the next stage of processing: creating a target item instance. The system first extracts the necessary data from the source item as input parameters for creating the target item. During the data transmission process, the system may also perform necessary data conversion and mapping to ensure compatibility of data formats between different items. For example, when creating an expert review item after the initial review of the project is completed, the system will convert the initial review results, basic project information and other data into the format required for the expert review.
[0036] After the target event instance is created, the system immediately initializes its state and performs a series of checks to confirm its success. These checks may include verifying that required fields are correctly filled, that associated data is established, and that permissions are assigned. If the creation is successful, the system triggers a special "Create Success" event, which can serve as the trigger for other connections, thereby ensuring the continued progress of the event flow.
[0037] In a complete project approval process, this mechanism operates as follows: When a project application form is submitted, the system issues a "Form Submission Completed" event; a connector conditional evaluation checks whether the form meets the preliminary review criteria, and if so, a preliminary project review item is created; after the preliminary review is complete, the results determine whether the application will proceed to expert review or be returned to the applicant for revision; if the application proceeds to expert review, the system then determines whether the application will proceed to the project repository based on the review results. Throughout this process, the dynamic evaluation of connector conditional expressions ensures that the business process can flexibly adapt to actual circumstances, rather than following a fixed, pre-set path.
[0038] In a possible implementation of the present invention, before receiving the change signal and converting the state change signal into a standardized event according to a predefined event mapping rule, the method further includes: Receive the matter flow design instruction input by the user and generate a matter flow chart, wherein the matter flow chart includes: multi-level matter nodes, adaptive gateway nodes and intelligent connection lines.
[0039] It's important to note that the parsing device first receives the business person's event flow design instructions in the visual designer. These instructions can be implemented by dragging "event nodes," "gateway nodes," and "smart connectors" onto the canvas and filling in metadata such as the name, approver, and form template in the property panel. The corresponding nodes can also be automatically generated using simple scripts or natural language descriptions. Each event node embeds basic information, a processing form, event definitions, and configuration for integration with external workflows. Adaptive gateway nodes are pre-configured with four operating modes: parallel, conditional, event, and composite. Branching logic is dynamically switched based on context during subsequent process execution. Smart connectors allow for the writing of Groovy or JavaScript conditional scripts during design, as well as the configuration of timeout handling and backtracking strategies. After the user completes the design of all these elements, the parsing device automatically performs topology and rule verification, generating a structured flow chart data file, which is stored in JSON or a graph database.
[0040] It should be noted that the introduction of multi-level nodes, adaptive gateways, and intelligent connections during the design phase eliminates the tedious manual coding required in traditional process definitions and improves the system's flexibility through dynamic switching and scripted conditional judgments at runtime. For example, in a project approval scenario, designers only need to sequentially configure nodes such as "Project Application," "Project Preliminary Review," and "Expert Review" on the canvas, connect them with conditional gateways to distinguish between "Review Passed" and "Review Failed" paths, and set the connection line to "Go to the warning branch if no review has been conducted for more than three days." The system will then automatically generate a complete, executable process upon completion of the design.
[0041] In a possible implementation of the present invention, the adaptive gateway nodes include four types: parallel gateway, conditional gateway, event gateway and composite gateway, each type is optimized for a specific business scenario.
[0042] After receiving a completion event for an event node, the parallel gateway can simultaneously trigger the initiation of multiple subsequent events. For example, in project approval, after the project warehousing event is completed, it may be necessary to simultaneously initiate funding confirmation and project publicity. The system uses the parallel gateway to convert a single completion signal into multiple initiation signals, ensuring that related events can proceed simultaneously. Specifically, the parallel gateway maintains a list of output connection lines. When a trigger event is received, the system traverses this list and executes the same event processing flow for each connection line, thus achieving a parallel triggering effect.
[0043] The conditional gateway is responsible for dynamically selecting the path for subsequent matters based on preset business rules. This gateway type uses a script engine to parse conditional expressions, and combines the status and attribute data of the source matter to calculate the connection line path that meets the conditions. For example, after the expert review of the matter is completed, the system can automatically decide whether the process will enter the project warehousing stage or return to the project application stage based on the review score. The implementation of the conditional gateway relies on an efficient scripting engine and data injection mechanism. When the conditional gateway receives an event, the system will evaluate the conditional expression of each exit connection line in turn, and select the first connection line that returns true as the path for the process to continue. If multiple conditions are met at the same time, the system will make a selection based on the preset priority rules.
[0044] An event gateway is a wait-based gateway that listens for multiple possible events. Once any of these events occurs, the corresponding process path is triggered. This type of gateway is particularly suitable for business scenarios that require external interaction or time triggering. For example, in a project application, the system can simultaneously wait for both the "Applicant Withdraws" event and the "Review Timeout" event. Whichever event occurs first will direct the process to the corresponding processing path. The event gateway implements its functionality by maintaining an event subscription table that records the processing path for each possible event and dynamically registering and deregistering event listeners at runtime.
[0045] The composite gateway can automatically switch gateway types based on changes in business scenarios. By analyzing the historical data and current context of the event flow, the system intelligently determines the gateway type that best suits the current business situation and automatically converts it. For example, when resources are limited, multiple events originally designed for parallel processing may need to be changed to conditional priority processing; when the data required for condition evaluation is incomplete, the system may need to temporarily convert the conditional gateway to an event gateway to wait for more information to arrive. The implementation of the composite gateway is based on a complex combination of state machines and strategy patterns. It maintains the basic behavioral models of various gateway types and dynamically selects the most appropriate processing strategy through real-time analysis of the trigger context.
[0046] In practice, these four gateway types can be flexibly combined to form complex business flow networks. For example, a complete project management process begins with a project application. Conditional gateways determine the project type and initiate different approval paths. Key nodes along each path may employ event gateways to await external approval. Once approved, resource allocation and team formation are simultaneously initiated via parallel gateways. Finally, during the project implementation phase, composite gateways are used to dynamically adjust subsequent approval processes based on project progress. This flexible combination enables the system to cope with a variety of complex and ever-changing business scenarios.
[0047] In a possible embodiment of the present invention, the method further includes: when an exception occurs during the execution process, recording error information and generating a default configuration failure strategy.
[0048] It's important to note that when the system encounters an exception while executing a conditional script or processing an item, it first captures the exception and logs it in detail. This log includes details such as the timestamp of the exception, the exception type, the source (e.g., the script execution engine, the item creation service), related item information, and the exception stack trace. These records are stored in the system's log library. For example, in project approval, if a syntax error or reference to a non-existent data field occurs during the execution of a conditional script connecting the project's initial review to the expert review, the system will record the specific error location and cause, rather than simply reporting a "script execution failure."
[0049] After the error information is recorded, the system will determine the next action based on the pre-configured failure strategy. The failure strategy is a set of rules pre-defined during the event flow design phase that guides the system on how to continue running when encountering an exception. This embodiment can configure multiple types of failure strategies, which can be flexibly configured according to business needs: The default failure strategy is "safe mode," which assumes the condition is not met and does not trigger subsequent transactions if a conditional script executes abnormally. This strategy is suitable for most business scenarios and ensures that the system does not mistakenly initiate subsequent transactions in uncertain situations.
[0050] The "downgrade processing" strategy allows the system to switch to a predefined, simplified process when an anomaly occurs in the main process. For example, in an expert review, if the automated scoring system fails, the system can switch to a manual review path to ensure that business is not completely interrupted.
[0051] The "Retry Mechanism" policy allows the system to automatically retry failed operations under specific conditions. The system will retry failed scripts or event creation operations according to the configured retry interval and maximum number of retries. This policy is particularly effective for occasional failures caused by temporary network issues or excessive system load.
[0052] The "Rollback Operation" strategy is used to automatically roll back some completed operations when a serious error occurs during the event creation process, restoring the system state to the state before the exception occurred.
[0053] In a possible embodiment of the present invention, the method further includes: constructing a historical log of event flow, analyzing the historical log of event flow at each preset time period to generate an analysis result, and dynamically adjusting the event processing priority and resource allocation strategy according to the analysis result; The event flow history log is used to record the occurrence time, source, impact scope and processing results of each event; The analysis results include frequently occurring flow paths and abnormal patterns.
[0054] It should be noted that after each event is processed, the parsing device persistently stores the event object (including information such as event type, trigger time, source node identifier, impact scope, and processing results) in a "matter flow history log" storage. This storage can utilize a time-series database or a relational database combined with log middleware for efficient writing and querying. The parsing device automatically initiates a log analysis process based on a preset time window (e.g., hourly or daily), mining the accumulated historical logs for flow paths and detecting anomalies. For example, it utilizes graph analysis algorithms or frequent subgraph mining techniques to identify high-frequency flow sequences such as "project application → preliminary review → expert review." It also uses statistics and anomaly detection algorithms to identify unusual patterns that deviate from the normal path, such as "approval timeouts" and "node jumps." The analysis results are fed back to the event dispatch center. Based on the frequency of "critical paths" and the processing time of each node, the system automatically prioritizes the corresponding event, dynamically reserves additional computing and network resources during peak periods to avoid bottlenecks, and triggers alerts or fallback policies for nodes with frequent anomalies. This ensures smooth and low latency for core business operations while continuously optimizing the intelligent allocation of system resources.
[0055] In a possible embodiment of the present invention, the method further includes: using supervised learning to predict future flow paths based on the historical logs, and dynamically adjusting event priorities.
[0056] In this embodiment, a complete historical log system for event flow is established to record the occurrence time, trigger source, impact scope, processing results and related business data of each event in the business process. These logs not only contain information on successful flows, but also record the detailed process of abnormal situations and manual intervention. For example, in the project establishment business, the system will record the status changes, event triggers, condition evaluation results and other information of each event node in the entire process from project application to final funding, forming a complete business flow track. These refined log data constitute the basic training set of the supervised learning model.
[0057] The system uses a multi-layered machine learning architecture to process this historical log data. During the data preprocessing phase, the system first cleans and standardizes the raw logs, converting logs from different transaction types and business scenarios into a unified structured format. Feature engineering techniques are then used to extract key features from the logs, such as transaction type, business attributes, transaction time patterns, and conditional branch selection. These features, along with process outcomes (such as transaction paths, completion times, and exceptions), form the input-output pairs for training supervised learning models.
[0058] In terms of model selection and training, a variety of machine learning algorithms can be employed depending on the prediction task. For path prediction, the system primarily uses time series models such as long short-term memory (LSTM) or conditional random fields (CRF). These models effectively capture the temporal dependencies of event flows. For priority adjustment, reinforcement learning algorithms can be employed to optimize event handling strategies through reward mechanisms. For anomaly warnings, the system uses anomaly detection algorithms such as isolation forests or autoencoders to identify potential process anomalies. After training, these models are regularly updated with new log data to ensure that their predictive capabilities remain synchronized with business changes.
[0059] The analysis device can predict the most likely future process paths based on the current status of ongoing projects and historical patterns. For example, when a project application enters the preliminary review stage, the analysis device can predict the likely review stages, the time required for completion, and the potential bottlenecks it may encounter based on the project's characteristics and the historical progress of similar projects.
[0060] More importantly, the parsing device will dynamically adjust the priority of event processing based on the prediction results. Traditional workflow systems usually adopt fixed event processing strategies, such as first-in-first-out or priorities based on simple rules. However, this embodiment analyzes historical data through machine learning models to identify critical paths and events that have a greater impact on business processes and are highly time-sensitive. The parsing device dynamically adjusts the processing priority of each event in the event queue based on this to ensure that key processes are given priority. For example, if the prediction shows that a project review is about to time out, the system will automatically increase the processing priority of related events; if a certain type of project has often encountered problems in a specific link in the history, the system will allocate more processing resources to the related events.
[0061] This embodiment also configures an abnormal warning and automatic intervention mechanism. By analyzing historical abnormal patterns, the parsing device can issue an early warning before potential problems occur. For example, if the parsing device detects that the review time of the current project is significantly longer than the historical average, it may notify the business management personnel in advance; if the selection of a certain conditional branch is significantly inconsistent with the historical pattern, the parsing device will mark it as a potential abnormality and recommend a review. In some cases, the parsing device can even automatically perform intervention measures according to preset policies, such as adjusting resource allocation, triggering alternative process paths, etc.
[0062] In the actual application of a large-scale project approval system, the parsing device handles thousands of different types of project applications involving multiple departments and approval links. By analyzing historical approval logs, the system learns the best processing paths and common bottlenecks for different types of projects. When a new project enters the system, the intelligent prediction function can estimate its completion time and identify the links that may cause delays. The parsing device automatically adjusts the processing priority of events related to these key links to ensure that they are handled in a timely manner. In addition, the system can automatically adjust resource allocation strategies based on seasonal changes (such as a surge in projects before the end of the fiscal year).
[0063] See also Figure 2 The second embodiment of the present invention provides a business process item parsing device, comprising: A mapping unit 201 is configured to receive a change signal and convert the state change signal into a standardized event according to a predefined event mapping rule, wherein the change signal includes a matter state change signal or a workflow state change signal; An event processing unit 202 is configured to store the standardized event into a priority event queue and process the events in the event queue in order of priority; A connection line identification unit 203 is configured to query a transaction flow configuration library according to the type and attributes of the event and identify all connection lines associated with the event; The instance creation unit 204 is used to evaluate the conditional expression of each connection line, determine the connection lines that meet the conditions, and for the connection lines that meet the conditions, input the source event data and create a target event instance, initialize the state of the target event instance to detect whether the creation is successful. If so, trigger the target event creation success event and continue the event flow.
[0064] A third embodiment of the present invention provides a business process item analysis assisting device, comprising a memory and a processor, wherein the memory stores a computer program, and the computer program can be executed by the processor to implement a business process item analysis method as described in any one of the above items.
[0065] The fourth embodiment of the present invention provides a computer-readable storage medium, characterized in that it stores a computer program, and the computer program can be executed by a processor of the device where the computer-readable storage medium is located to implement a method for parsing business process matters as described in any one of the above items.
[0066] Based on the business process item parsing method, device, equipment and storage medium provided by the present invention, by receiving a change signal, the state change signal is converted into a standardized event according to a predefined event mapping rule, then the standardized event is stored in a priority event queue, and the events in the event queue are processed in order of priority; then, the item flow configuration library is queried according to the type and attributes of the event, and all connection lines associated with the event are identified; finally, the conditional expression of each connection line is evaluated to determine the connection line that meets the condition, for the connection line that meets the condition, the source item data is passed in and a target item instance is created, the state of the target item instance is initialized to detect whether the creation is successful, and if so, the target item creation success event is triggered and the item flow continues, which solves the problem of business flow interruption in the existing business process without human intervention.
[0067] For example, the computer program described in the third and fourth embodiments of the present invention can be divided into one or more modules, which are stored in the memory and executed by the processor to implement the present invention. The one or more modules can be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution process of the computer program in the parsing device for implementing a business process item. For example, the device described in the second embodiment of the present invention.
[0068] The processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc. The processor is the control center of the method for parsing a business process item, and utilizes various interfaces and lines to connect the various parts of the method for parsing a business process item.
[0069] The memory can be used to store the computer program and / or module. The processor implements the various functions of a business process item parsing method by running or executing the computer program and / or module stored in the memory and accessing the data stored in the memory. The memory may primarily include a program storage area and a data storage area. The program storage area may store an operating system and at least one application required for a function (such as a sound playback function, a text conversion function, etc.); the data storage area may store data generated based on the use of the mobile phone (such as audio data, text message data, etc.). In addition, the memory may include high-speed random access memory and non-volatile memory, such as a hard disk, internal memory, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, at least one disk storage device, a flash memory device, or other volatile solid-state storage device.
[0070] If the implemented module is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present invention can implement all or part of the process steps in the above-mentioned method embodiments by using a computer program to instruct the relevant hardware. The computer program can be stored in a computer-readable storage medium. When executed by a processor, the computer program can implement the steps of each of the above-mentioned method embodiments. The computer program includes computer program code, which can be in source code form, object code form, executable file, or some intermediate form. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal, and software distribution medium. It should be noted that the content of the computer-readable medium can be appropriately increased or decreased based on the requirements of legislation and patent practice in a jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media does not include electric carrier signals and telecommunication signals.
[0071] It should be noted that the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed across multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment. In addition, in the drawings of the device embodiments provided by the present invention, the connection relationship between the modules indicates that there is a communication connection between them, which may be specifically implemented as one or more communication buses or signal lines. A person of ordinary skill in the art can understand and implement the present invention without inventive effort.
[0072] The above description is merely a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present invention should be included in the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.
Claims
1. A method for analyzing business process matters, characterized in that: include: receiving a change signal, and converting the state change signal into a standardized event according to a predefined event mapping rule, wherein the change signal includes a matter state change signal or a workflow state change signal; Storing the standardized events in a priority event queue, and processing the events in the event queue in order of priority; Querying the event flow configuration library according to the type and attributes of the event to identify all connection lines associated with the event; Evaluate the conditional expression of each connection line and determine the connection lines that meet the conditions. For the connection lines that meet the conditions, pass in the source event data and create a target event instance. Initialize the state of the target event instance to detect whether the creation is successful. If so, trigger the target event creation success event and continue the event flow.
2. A method for analyzing business process items according to claim 1, characterized in that: Before receiving the change signal and converting the state change signal into a standardized event according to the predefined event mapping rules, it also includes: Receive the matter flow design instruction input by the user and generate a matter flow chart, wherein the matter flow chart includes: multi-level matter nodes, adaptive gateway nodes and intelligent connection lines.
3. A method for analyzing business process items according to claim 1, characterized in that: The adaptive gateway node includes: Parallel gateway, used to trigger multiple subsequent events in parallel based on the completion event of an event node; Conditional gateway, used to dynamically select the path for subsequent matters based on business rules; An event gateway is used to wait for one of several possible events to occur before continuing the flow; Composite gateway, used to automatically switch gateway types based on business scenarios.
4. A method for analyzing business process items according to claim 1, characterized in that: The conditional expression for evaluating each connecting line is specifically: Load the conditional script associated with the connection line, build the script execution environment and inject the attribute data of the items in the current workflow. The script engine is called to execute the conditional script in the script execution environment, and the script execution result is converted into a Boolean value, wherein the Boolean value is used to determine whether to continue along the current connection.
5. A method for analyzing business process items according to claim 4, characterized in that: Also includes: When an exception occurs during execution, the error information is recorded and a default failure strategy is generated.
6. A method for analyzing business process items according to claim 1, characterized in that: Also includes: Construct a historical log of event flows, analyze the log at preset intervals to generate analysis results, and dynamically adjust event processing priorities and resource allocation strategies based on the analysis results; The event flow history log is used to record the occurrence time, source, impact scope and processing results of each event; The analysis results include frequently occurring flow paths and abnormal patterns.
7. A method for analyzing business process items according to claim 1, characterized in that: Also includes: Based on the historical logs, supervised learning is used to predict future flow paths and dynamically adjust event priorities.
8. A business process item analysis device, characterized in that: include: A mapping unit, configured to receive a change signal and convert the state change signal into a standardized event according to a predefined event mapping rule, wherein the change signal includes a matter state change signal or a workflow state change signal; An event processing unit, configured to store the standardized events in a priority event queue and process the events in the event queue in order of priority; A connection line identification unit, configured to query a transaction flow configuration library according to the type and attributes of the event and identify all connection lines associated with the event; The instance creation unit is used to evaluate the conditional expression of each connection line, determine the connection lines that meet the conditions, and for the connection lines that meet the conditions, pass in the source event data and create the target event instance. The state of the target event instance is initialized to detect whether the creation is successful. If so, trigger the target event creation success event and continue the event flow.
9. A business process analysis assistance device, characterized in that: It includes a memory and a processor, wherein the memory stores a computer program, and the computer program can be executed by the processor to implement a business process item parsing method as described in any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that A computer program is stored, and the computer program can be executed by a processor of the device where the computer-readable storage medium is located to implement a method for parsing business process matters as described in any one of claims 1 to 7.