Business processing method, device, equipment and program product

Abstract

The invention provides a business processing method and device, equipment and a program product. The method comprises the following steps: acquiring a business flow chart provided by a client, wherein the business flow chart comprises at least two pre-configured images and a directed connection line between the at least two pre-configured images; wherein each pre-configured image represents one business process node and presents a corresponding execution rule and a rule parameter; the direction of the directed connecting line represents the direction of the execution path. And traversing the pre-configured images in the business flow chart according to the direction of the directed connecting line in the business flow chart, so as to construct a corresponding executable statement according to the execution rule and the rule parameter of each traversed pre-configured image. And combining all the executable statements obtained by construction according to the direction of the directed connection line in the business flow chart to obtain an executable statement list. And executing the executable statement list, and feeding back a corresponding output result to the client.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a business processing method, apparatus, device, and program product. Background Technology

[0002] A rule engine is a software system used to process and execute decision logic based on predefined rules. Its core function is to automatically execute corresponding operations or decisions based on input data and conditions. By separating business logic from code, it significantly improves the system's flexibility, scalability, and efficiency, and is widely used in automation, data analysis, and intelligent systems. However, current rule engine technology still has some limitations: First, the rule language is complex, making it difficult for non-technical personnel to directly participate in rule design and maintenance, leading to a disconnect between business needs and the development team; second, the generated code has a weak correlation with business logic, requiring developers to spend a significant amount of time parsing rule statements to understand business intent, increasing collaboration costs. Therefore, there is an urgent need for a rule engine implementation method that is low-threshold and highly relevant to business operations. Summary of the Invention

[0003] To address the aforementioned problems, this application provides a business processing method, apparatus, equipment, and program product, the technical solution of which is as follows: Firstly, a business processing method is provided, including: Obtain a business process diagram provided by the client, the business process diagram containing at least two pre-configured images and directed lines connecting the at least two pre-configured images; wherein each pre-configured image represents a business process node and presents corresponding execution rules and rule parameters; the direction of the directed lines indicates the direction of the execution path; According to the direction of the directed connection in the business process diagram, the pre-configured images in the business process diagram are traversed to construct corresponding executable statements based on the execution rules and rule parameters of each traversed pre-configured image. According to the direction of the directed connection in the business process diagram, all the constructed executable statements are combined to obtain a list of executable statements; The executable statement list is executed, and the corresponding output results are fed back to the client.

[0004] Secondly, a business processing apparatus is provided, comprising: The acquisition module is used to acquire a business process diagram provided by the client. The business process diagram includes at least two pre-configured images and directed lines between the at least two pre-configured images. Each pre-configured image represents a business process node and presents corresponding execution rules and rule parameters. The direction of the directed lines indicates the direction of the execution path. A module is created to traverse the pre-configured images in the business process diagram according to the direction of the directed connection in the business process diagram, so as to construct corresponding executable statements based on the execution rules and rule parameters of each traversed pre-configured image. The combination module is used to combine all the constructed executable statements according to the direction of the directed connection in the business process diagram to obtain a list of executable statements; The execution module is used to execute the list of executable statements and return the corresponding output results to the client.

[0005] Thirdly, embodiments of this application provide an electronic device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to perform the method described in the first aspect.

[0006] Fourthly, a computer-readable storage medium is provided for storing computer-executable instructions that, when executed by a processor, implement the method described in the first aspect.

[0007] This application implements a rule engine that can convert user-provided business process diagrams into executable statements and automatically execute them to form a closed-loop feedback. Specifically, the business process diagram is configured to include at least two pre-configured images and directed connections between them; each image type pre-configured image represents a business process node and presents corresponding execution rules and rule parameters, with the direction of the directed connections indicating the execution path direction. After the user submits the business process diagram through the client, the business requirements are first abstracted into a machine-resolvable topological relationship through the structured representation (including execution rules, rule parameters, and path direction) of each pre-configured image and directed connection in the business process diagram; then, according to the direction of the valid connections in the business process diagram, the pre-configured images are traversed, and corresponding executable statements are constructed based on the execution rules and rule parameters of each pre-configured image, combined into a linear list of executable statements; finally, the list of executable statements is executed sequentially, and the output results are fed back to the client. For users using the client, the entire solution only requires graphical configuration of the business process diagram, without requiring in-depth knowledge of the underlying code's coding language, which not only lowers the operational threshold but also improves the correlation between rule execution and business. Attached Figure Description

[0008] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0009] Figure 1 This is a schematic diagram of the first type of business processing method according to an embodiment of this application.

[0010] Figure 2 This is a schematic diagram of the first business process of the business processing method according to an embodiment of this application.

[0011] Figure 3 This is a logical diagram illustrating the conversion rule statements of the business processing method in an embodiment of this application. Figure 4 A logical diagram illustrating the execution of rule statements in the business processing method of this application embodiment; Figure 5 This is a schematic diagram of a second business process of the business processing method according to an embodiment of this application.

[0012] Figure 6 This is a schematic diagram of the structure of the service processing device according to an embodiment of this application.

[0013] Figure 7 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0014] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this specification, and not all embodiments. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this specification.

[0015] One embodiment of this application provides a business processing method for implementing a rule engine in a business system. Figure 1 This is a flowchart illustrating the business processing method, including: S101, Obtain the business process diagram provided by the client. The business process diagram contains at least two pre-configured images and directed lines between at least two pre-configured images. Each pre-configured image represents a business process node and presents corresponding execution rules and rule parameters. The direction of the directed lines indicates the direction of the execution path.

[0016] This embodiment decouples the upper-layer business logic from the lower-layer code, allowing non-professional users to simply edit a visual business process diagram when they need to perform business operations, without having to consider how to write rule statements using a coding language.

[0017] A business process diagram can include the following elements: At least two pre-configured images: each pre-configured image represents a business process node and presents the corresponding execution rules and rule parameters.

[0018] Directed connections between different pre-configured images: indicate the direction of the execution path and may include jump conditions.

[0019] It should be understood that through the mutual coordination of pre-configured images and directed connections, machines can parse out the corresponding business topology relationships, thereby generating executable statements written in a code language that conforms to the business process.

[0020] As a feasible approach, this embodiment can divide the pre-configured images into different image types, with each image type representing a corresponding execution rule. For example: Data image type, used for data selection (such as selecting fields from a dataset); The image type is assigned for external input assignment (such as parameter assignment). Determine the image type for use in conditional branches; Database image type, used for database queries (such as executing SQL statements).

[0021] In addition, each pre-configured image also presents text content to describe the corresponding rule logic. For example, the text content of a pre-configured image for determining the image type records the specific judgment conditions; the text content of a pre-configured image for assigning the image type records the assignment call address or specific assignment parameters, etc.

[0022] Based on the above business process diagram design, the machine only needs to identify the image type of each pre-configured image to match the corresponding execution rules, extract the rule parameters from the text content, and import them into the execution rules to generate the corresponding executable statements.

[0023] In practical applications, this embodiment can characterize the image type to the machine by using the image shape of a pre-configured image. For example, a rhombus can represent the image type for judgment, and a cylinder can represent the image type for database. Alternatively, a type field can be marked on each pre-configured image for machine recognition.

[0024] S102, according to the direction of the directed connection in the business process diagram, traverse the pre-configured images in the business process diagram to construct corresponding executable statements based on the execution rules and rule parameters of each traversed pre-configured image.

[0025] Taking data image type, assignment image type, determination image type, and database image type as examples, this embodiment traverses the pre-configured images in the business process diagram according to the direction of the directed lines in the business process diagram: If a pre-configured image of the data image type is encountered during the traversal, an executable statement is constructed with the corresponding rule parameters (text content) as the selection objects; If a pre-configured image of the assigned image type is encountered, an executable statement is constructed with the corresponding rule parameter (text content) as external input. If a pre-configured image for determining the image type is encountered during iteration, an executable statement is constructed that uses the corresponding rule parameters (text content) as the determination condition. If a pre-configured image of the database image type is encountered, an executable statement is constructed that uses the corresponding rule parameters (text content) as query conditions to retrieve data.

[0026] It should be understood that the above executable statements do not require manual completion, thus avoiding errors that may occur during human coding; at the same time, the executable statements written are consistent with the direction of the directed connections, strictly adhering to the execution order of the business process.

[0027] In practical applications, this embodiment can add start and end node labels to the business process diagram to help the machine determine the start and end positions of traversal. For example, a start image and an end image can be set separately in the business process diagram. The start image is connected to the first pre-configured image, and the last pre-configured image is connected to the end image. During traversal, the machine first finds the start image in the business process diagram, and uses the pre-configured image connected after the start image as the starting point for traversal and creates executable statements; then, when the end image is reached, all created executable statements are output.

[0028] S103. According to the direction of the directed lines in the business process diagram, combine all the constructed executable statements to obtain a list of executable statements.

[0029] In this embodiment, if the directed lines in the business process diagram are marked with jump conditions, the execution path of all constructed executable statements can be determined according to the direction of the directed lines and the jump conditions in the business process diagram. Then, all constructed executable statements are sorted and combined according to the execution path to obtain a list of executable statements.

[0030] S104 executes the list of executable statements and sends the corresponding output results back to the client.

[0031] Specifically, this embodiment employs a loop mechanism to execute each executable statement in the list of executable statements one by one. In two consecutively executed executable statements, the output of the former is used as the input parameter for the latter, ensuring data continuity. After executing the last executable statement, all output results are fed back to the client.

[0032] If the user is not satisfied with the output, they only need to adjust the pre-configured images of the business process diagram, regenerate the list of executable statements, and execute them. This change is accomplished through more intuitive image modifications, such as adding or deleting pre-configured images, changing the image shape and text content of pre-configured images, etc. Since it does not involve writing code, it eliminates the process of "bit code location → modifying code logic → recompiling and deploying → verifying code correctness", thus greatly improving the efficiency of modification.

[0033] In summary, this embodiment provides a rule engine capable of converting user-provided business process diagrams into executable statements and automating their execution to form a closed-loop feedback. Specifically, the business process diagram is configured to include at least two pre-configured images and directed connections between them; each image type pre-configured image represents a business process node and presents corresponding execution rules and rule parameters, with the direction of the directed connections indicating the execution path direction. After the user submits the business process diagram through the client, the business requirements are first abstracted into a machine-resolvable topological relationship through the structured representation (including execution rules, rule parameters, and path direction) of each pre-configured image and directed connection in the business process diagram; then, according to the direction of the valid connections in the business process diagram, the pre-configured images are traversed, and corresponding executable statements are constructed based on the execution rules and rule parameters of each pre-configured image, combined into a linear list of executable statements; finally, the list of executable statements is executed sequentially, and the output results are fed back to the client. For users on the client side, the entire solution only requires graphical configuration of the business process diagram, without the need for in-depth knowledge of the underlying code's coding language. This not only lowers the operational threshold but also improves the correlation between rule execution and business operations.

[0034] The specific application of the business processing method in this embodiment will be described exemplarily below.

[0035] This embodiment defines the pre-configured images for the business process diagram, which include the image types shown in the table below:

[0036] The data structure for each pre-configured image may include the following fields: 1) id Function: A unique identifier for nodes, used for front-end and back-end data binding.

[0037] 2) ports.items[{group, id}] Function: Defines the four connection stubs (top, right, bottom, left) of a node, supporting connections in multiple directions.

[0038] Example: group: "top" indicates the top connection stub, used to receive output from the upstream node.

[0039] 3) attrs.text.text Function: Stores a fixed name for the image type (such as "determine image type" or "database image type").

[0040] 4) attrs.label.text Function: Displays user-defined label content (such as "User Identity Verification").

[0041] 5) attrs.label.ruleContent Purpose: To store execution rules, such as database operation statements or API call parameters.

[0042] Technology mapping: Triggering specific business logic by combining keywords such as query and api.

[0043] Correspondingly, the field structure of a directed connection can include the following fields: 1) id Function: Uniquely identifies the connection line, used for backend process tracking.

[0044] 2) source.cell and target.cell Function: Identifies the start and end point graphical node IDs of directed connections, used to construct business process topology relationships.

[0045] Example: source.cell="node_1" means that the connection starts from node 1.

[0046] 3) source.port and target.port Function: Defines the positions of connection stubs (e.g., top, bottom) to ensure aligned directed lines during graphics rendering. Technical implementation: ports.items predefines connection stub IDs for four directions (up, down, left, and right).

[0047] 4) labels[0].attrs.labelText.text Purpose: Stores the content of the directed connection tag (such as the jump condition status == "success"). This attribute is omitted when there is no content.

[0048] Based on the above data structure design, during the mapping of pre-configured images to code: each pre-configured image is bound to specific business logic through the `shape` field, such as diamond nodes triggering condition judgments and rectangular nodes performing data processing. Directed connections construct the process topology through the `source` and `target` fields to ensure the correct execution order. During dynamic rule parsing: keywords (such as `query`, `api`) are combined with the knowledge table to dynamically generate executable code, achieving zero-code configuration. Furthermore, `ports` supports multi-directional connections to adapt to complex process branches; `ruleContent` supports custom rules, compatible with various business scenarios.

[0049] Based on the above, assuming the rules engine is used to implement the business requirement of users making reservations for meals (users can select meals to place an order), then the user provides the following through the rules engine's client: Figure 2 The business process diagram shown is illustrated. Correspondingly, the rule engine follows... Figure 3 The processing logic shown will Figure 2 The business process diagram shown is parsed into corresponding executable statements. The specific steps include: Step 1: Image Classification and Initialization Graphic grouping: Divide the image elements in the flowchart into two arrays—shape graphic array (pre-configured images) and connector graphic array (directed connections).

[0050] Locate the starting point: Traverse the array of shapes and find the shape marked "start" as the starting node for parsing.

[0051] Step 2: Construct the execution path topology Parse the connection relationships: Traverse the array of connection line graphics, and filter out all connection lines originating from the starting node based on the connection stub ID (source.port) of the starting graphic. Based on the target node ID (target.cell) of the connection line, locate the next node it points to in the shape graphic array (such as a data graphic).

[0052] Step 3: Node Traversal and Rule Generation Data image type processing: If the current node is a data image, parse its text field (such as User), generate a data input statement (such as EXTERNAL INPUT: User), and cache it in the memory context.

[0053] Image type assignment processing: If the node is an assigned graph (such as a database operation), extract the rule parameters (such as query(User)) and map them to the knowledge table to generate an executable statement: 1: execute("query(User) FROM t_user BY user_id=${userId}")->User.

[0054] If a node has multiple outgoing connections (such as those pointing to both database graphs and data graphs), the main path (such as database operations) should be processed first, followed by the data output path.

[0055] Step 4: Conditional Branch Processing Image type determination processing: If the node is for determining the image type (e.g., User != null), generate the following conditional statement: 2: IF ("User != null") THEN 3 ELSE 7.

[0056] Add the node whose image type is determined to the parsing queue, and process the branch paths according to the connector label (Y / N): True branch: points to the assignment graph (such as querying food inventory), generating the statement: 3: execute("query(Meal) FROM t_meal BY meal_id=${mealId}") ->Meal.

[0057] False branch: points to the end graphic, generating the statement: 7: return("Invalid User").

[0058] Recursive processing of nested branches: Repeat the above logic for subsequent nodes that determine the image type (e.g., Meal != null) to generate nested condition chains: 4: IF ("Meal != null") THEN 5 ELSE 7 5: execute("api(createOrder)") ->Order 6: execute("add(Order) TO t_order") ->Result Step 5: Termination and Result Return End node processing: When traversing to the end node, generate a return statement: 7: return(Result), and terminate the parsing of the current branch.

[0059] Step 6: Merge execution statements Execution path integration: Backtrack unprocessed branches (such as path N) from the queue of unparsed branches and complete the conditional logic. 4: IF ("Meal != null") THEN 5 ELSE 7 2: IF ("User != null") THEN 3 ELSE 7 .

[0060] The final list of executable statements generated is as follows:

[0061] The code represented by the above list of executable statements is: "1: execute("query(User) FROM t_user BY user_id=${userId}") ->User 2: IF ("User != null") THEN 3 ELSE 7 3: execute("query(Meal) FROM t_meal BY meal_id=${mealId}") ->Meal 4: IF ("Meal != null") THEN 5 ELSE 7 5: execute("api(createOrder)") ->Order 6: execute("add(Order) TO t_order") ->Result 7: return(Result) .

[0062] The data structure of each rule statement may include the following fields: 1) Execution Index: Defines the order in which rules are executed.

[0063] 2) Type: Divided into two categories: 3) Execution classes (such as EXECUTE): directly manipulate data or call interfaces; 4) Decision-based (e.g., IF): The branch direction is determined based on the condition.

[0064] 5) Content: Specific operation instructions (e.g., query(User) means querying the user table).

[0065] 6) Input parameters (ruleParam): Externally imported business data (such as user ID, order amount).

[0066] 7) Additional parameters (extraParam): Output of the previous step (such as user information retrieved and passed to the next step).

[0067] 8) Output (result): The processing result of the current step (such as query results, interface response).

[0068] Afterwards, the rule engine can refer to the list of executable statements when executing the rule list. Figure 4 As shown: First, the execution environment is started by calling the `run` method of the rule session (`RuleSession`). Then, the first rule is retrieved from the rule queue and a `while(true)` loop is entered. In each iteration, the corresponding logic processor (such as database operation, condition judgment, result return) is instantiated according to the type of the current rule (such as `EXECUTE`, `IF`, `RETURN`). After execution, the output result (such as query result, judgment status) is obtained and passed to subsequent rule statements. This process specifically determines the execution order by activating the next rule (such as jumping by sequence number or conditional branch). If the next rule statement exists, the loop continues; otherwise, the process terminates and the final output result is returned. This process, through loop-driven and context-passing mechanisms, ensures that rules are executed according to the business process and maintains data continuity, achieving automated and efficient processing of complex business logic.

[0069] Correspondingly, the execution flow of the above list of executable statements includes the following steps: 1) Execute sequence number 1 (execute) Operation: Query the user table t_user based on user_id, and generate SQL using predefined fields in the knowledge table: "SELECT * FROM t_user WHERE user_id = ${user_id}"; Output: User object (if it exists).

[0070] Passing logic: The User object is stored in the context for use by subsequent statements.

[0071] 2) Execute sequence number 2 (if) Conditional check: Check if User is null.

[0072] Branch jump: If User != null → Jump to execution sequence number 3 (continue querying for meals); If User == null → jump to execution sequence number 7 (directly return an error).

[0073] 3) Execution sequence number (execute) Operation: Query the meal table t_meal based on User.meal_id, and generate the SQL: "SELECT * FROM t_meal WHERE meal_id = ${User.meal_id}"; Output: Meal object (if it exists).

[0074] Passing logic: The Meal object is stored in the context.

[0075] 4) Execute sequence number 4 (if) Conditional check: Check if Meal is null.

[0076] Branch jump: If Meal != null → jump to execution sequence number 5 (create order); If Meal == null → jump to execution sequence number 7 (returns an error).

[0077] 5) Execute sequence number 5 (execute) Operation: Call the external API (createOrder), pass in the User and Meal parameters, and generate an order object (order).

[0078] Output: The order object returned by the interface.

[0079] Knowledge table mapping: The interface address and parameter format are configured through the knowledge table (e.g., POST / api / order).

[0080] 6) Execute sequence number 6 (execute) Operation: Insert `order` into the `t_order` table and generate SQL: "INSERT INTO t_order (order_id, user_id, meal_id) VALUES (${order.id}, ${User.id}, ${Meal.id})" Output: Database operation result.

[0081] 7) Execute sequence number 7 (return) Result returned: Successful execution path (after execution sequence number 6): Returned order details (order); Failed execution path (condition not met): Returns an error message (e.g., {"code": 404, "msg": "User / Meal not found"}).

[0082] The corresponding execution path is: ① Successful execution path (both user and food item exist): 1 → 2 → 3 → 4 → 5 → 6 → 7 The final return value is an order object.

[0083] ② The user does not exist in the path: 1 → 2 → 7 The system returned an error: User not found.

[0084] ③ The path for the food item does not exist: 1 → 2 → 3 → 4 → 7 Error returned: Food not found.

[0085] Furthermore, if users later find that improvements to the food reservation system are needed, such as setting reservation time limits to prevent situations where users reserve in advance but the restaurant is unable to prepare the food, this can be achieved by setting start and end times for each food item. In this case, simply... Figure 2 The business process diagram shown is modified as follows: Figure 5 The business process diagram shown (shaded areas indicate modification points) can be regenerated by creating a new list of executable statements. For operators, this modification process is simple, requires no complex coding knowledge, and does not affect the original business logic.

[0086] In summary, the rule engine in this embodiment has the following characteristics: 1) Logical coherence of execution sequence numbers: By using a context-based passing mechanism (such as the path from user to food to order), redundant queries and calculations are reduced, improving execution efficiency. At the same time, this mechanism ensures data consistency, avoids redundant database access, and further optimizes the performance of the business system.

[0087] 2) Parameter passing and context management: Reduce redundant queries and calculations, and improve execution efficiency. Context passing (e.g., User→Meal→order) ensures data consistency and avoids redundant database access.

[0088] 3) Branch jump and condition handling: The then / else jump instructions of the if statement clearly express the branch path of complex business logic, solving the problem of difficult maintenance of multi-branch processes in traditional rule engines.

[0089] Corresponding to Figure 1 In addition to the method shown, another embodiment of this example also provides a business processing device. Figure 6 This is a structural diagram of the service processing device 600, including: The acquisition module 610 is used to acquire a business process diagram provided by the client. The business process diagram includes at least two pre-configured images and directed lines between the at least two pre-configured images. Each pre-configured image represents a business process node and presents corresponding execution rules and rule parameters. The direction of the directed lines indicates the direction of the execution path.

[0090] A creation module 620 is used to traverse the pre-configured images in the business process diagram according to the direction of the directed connection in the business process diagram, so as to construct corresponding executable statements based on the execution rules and rule parameters of each traversed pre-configured image.

[0091] The combination module 630 is used to combine all the constructed executable statements according to the direction of the directed connection in the business process diagram to obtain a list of executable statements.

[0092] The execution module 640 is used to execute the list of executable statements and return the corresponding output results to the user.

[0093] The device in this embodiment implements a rule engine that can convert user-provided business process diagrams into executable statements and automatically execute them to form a closed-loop feedback. Specifically, the business process diagram is configured to include at least two pre-configured images and directed connections between them; each image type pre-configured image represents a business process node and presents corresponding execution rules and rule parameters, with the direction of the directed connections indicating the execution path direction. After the user submits the business process diagram through the client, the business requirements are first abstracted into a machine-resolvable topological relationship through the structured representation (including execution rules, rule parameters, and path direction) of each pre-configured image and directed connection in the business process diagram; then, according to the direction of the valid connections in the business process diagram, the pre-configured images are traversed, and corresponding executable statements are constructed based on the execution rules and rule parameters of each pre-configured image, combined into a linear list of executable statements; finally, the list of executable statements is executed sequentially, and the output results are fed back to the client. For users using the client, the entire solution only requires graphical configuration of the business process diagram, without requiring in-depth knowledge of the underlying code's coding language, which not only lowers the operational threshold but also improves the correlation between rule execution and business.

[0094] Optionally, the business process diagram includes pre-configured images of at least two image types, and each pre-configured image presents execution rules corresponding to its respective image type.

[0095] Optionally, the at least two image types include at least one of: data image type, assignment image type, decision image type, and database image type; The creation module 620 traverses the pre-configured images in the business process diagram according to the direction of the directed connections in the business process diagram, and constructs corresponding executable statements based on the execution rules and rule parameters of each traversed pre-configured image. This includes: when traversing a pre-configured image of the data image type, constructing an executable statement using the corresponding rule parameters as the selection object; when traversing a pre-configured image of the assignment image type, constructing an executable statement using the corresponding rule parameters as external input for assignment; when traversing a pre-configured image of the judgment image type, constructing an executable statement using the corresponding rule parameters as the judgment condition for judgment; and when traversing a pre-configured image of the database image type, constructing an executable statement using the corresponding rule parameters as the query condition for data query.

[0096] Optionally, each of the pre-configured images in the business process diagram represents the image type with an image shape and contains text content describing the corresponding rule parameters.

[0097] Optionally, the directed lines in the business process diagram are further marked with jump conditions; the combination module 630 combines all the constructed executable statements according to the direction of the directed lines in the business process diagram to obtain a list of executable statements, including: sorting the execution paths of all the constructed executable statements according to the direction of the directed lines and jump conditions in the business process diagram to obtain a list of executable statements.

[0098] Optionally, the execution module 640 executes the list of executable statements, including: executing each executable statement in the list of executable statements in sequence, wherein, in two consecutively executed executable statements, the output result of the former is used as the input parameter of the latter.

[0099] Optionally, the business process diagram may also include annotations for the pre-configured image at the beginning of the traversal and / or annotations for the pre-configured image at the end of the traversal.

[0100] It should be noted that the service processing device in this embodiment can be used as... Figure 1 The execution body of the method shown is therefore able to achieve... Figure 1 The steps and functions of the method shown are illustrated.

[0101] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Please refer to it. Figure 7At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and memory. The memory may include main memory, such as high-speed random-access memory (RAM), or non-volatile memory, such as at least one disk drive. Of course, the electronic device may also include other hardware required for other business operations.

[0102] The processor, network interface, and memory can be interconnected via an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 7 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0103] Memory is used to store computer programs. Specifically, a computer program may include program code, which includes computer operation instructions. Memory may include main memory and non-volatile memory, and provides the computer program to the processor.

[0104] Specifically, the processor reads the corresponding computer program from non-volatile memory into memory and then runs it, forming the above-mentioned logical structure. Figure 6 The illustrated business processing apparatus. Correspondingly, the processor executes the program stored in the memory and specifically performs the following operations: Obtain a business process diagram provided by the client, the business process diagram containing at least two pre-configured images and directed lines between the pre-configured images; wherein each pre-configured image contains corresponding execution rules and rule parameters; the direction of the directed lines indicates the direction of the execution path; According to the direction of the directed connection in the business process diagram, the pre-configured images in the business process diagram are traversed to construct corresponding executable statements based on the execution rules and rule parameters of each traversed pre-configured image. According to the direction of the directed connection in the business process diagram, all the constructed executable statements are combined to obtain a list of executable statements; The executable statement list is executed, and the corresponding output results are returned to the user.

[0105] This embodiment of the electronic device specifically implements a rule engine that can convert user-provided business process diagrams into executable statements and automatically execute them to form a closed-loop feedback. Specifically, the business process diagram is configured to include at least two pre-configured images and directed connections between them. Each image type represents a business process node and presents corresponding execution rules and rule parameters. The direction of the directed connections indicates the execution path direction. After the user submits the business process diagram through the client, the business requirements are first abstracted into a machine-resolvable topological relationship through the structured representation (including execution rules, rule parameters, and path direction) of each pre-configured image and directed connection in the business process diagram. Then, according to the direction of the valid connections in the business process diagram, the pre-configured images are traversed, and corresponding executable statements are constructed based on the execution rules and rule parameters of each pre-configured image, combined into a linear list of executable statements. Finally, the list of executable statements is executed sequentially, and the output results are fed back to the client. For users using the client, the entire solution only requires graphical configuration of the business process diagram, without requiring in-depth knowledge of the underlying code's coding language. This not only lowers the operational threshold but also improves the correlation between rule execution and business operations.

[0106] The above is as described in this instruction manual. Figure 1The business processing method disclosed in the illustrated embodiments can be applied to a processor and implemented by the processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit in the processor or by instructions in the form of software. The processor mentioned above can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this application can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0107] Of course, in addition to software implementation, the electronic device described in this specification does not exclude other implementation methods, such as logic devices or a combination of hardware and software. In other words, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0108] Furthermore, embodiments of this application also propose a computer-readable storage medium that stores one or more computer programs, the one or more computer programs including instructions.

[0109] When the aforementioned instructions are executed by a portable electronic device that includes multiple applications, they enable the portable electronic device to perform... Figure 1 The steps in the method shown include: Obtain a business process diagram provided by the client, the business process diagram containing at least two pre-configured images and directed lines between the pre-configured images; wherein each pre-configured image contains corresponding execution rules and rule parameters; the direction of the directed lines indicates the direction of the execution path; According to the direction of the directed connection in the business process diagram, the pre-configured images in the business process diagram are traversed to construct corresponding executable statements based on the execution rules and rule parameters of each traversed pre-configured image. According to the direction of the directed connection in the business process diagram, all the constructed executable statements are combined to obtain a list of executable statements; The executable statement list is executed, and the corresponding output results are returned to the user.

[0110] Those skilled in the art will understand that the embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0111] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0112] The above are merely embodiments of this specification and are not intended to limit the scope of this specification. Various modifications and variations can be made to this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of the claims of this specification. Furthermore, all other embodiments obtained by those skilled in the art without inventive effort should fall within the protection scope of this document.

Claims

1. A business processing method, characterized in that, include: Obtain a business process diagram provided by the client, the business process diagram containing at least two pre-configured images and directed lines connecting the at least two pre-configured images; wherein each pre-configured image represents a business process node and presents corresponding execution rules and rule parameters; the direction of the directed lines indicates the direction of the execution path; According to the direction of the directed connection in the business process diagram, the pre-configured images in the business process diagram are traversed to construct corresponding executable statements based on the execution rules and rule parameters of each traversed pre-configured image. According to the direction of the directed connection in the business process diagram, all the constructed executable statements are combined to obtain a list of executable statements; The executable statement list is executed, and the corresponding output results are fed back to the client.

2. The method according to claim 1, characterized in that, The business process diagram includes pre-configured images of at least two image types, and each pre-configured image presents execution rules corresponding to its respective image type.

3. The method according to claim 2, characterized in that, The at least two image types include at least one of the following: data image type, assignment image type, determination image type, and database image type; Following the direction of the directed connections in the business process diagram, the pre-configured images in the business process diagram are traversed to construct corresponding executable statements based on the execution rules and rule parameters of each traversed pre-configured image, including: When traversing to the pre-configured image of the data image type, construct an executable statement with the corresponding rule parameters as the selection object; When traversing to the pre-configured image of the assigned image type, construct an executable statement that assigns values ​​with the corresponding rule parameters as external input; When the pre-configured image of the image type is traversed, an executable statement is constructed to make a judgment based on the corresponding rule parameters as the judgment condition; When traversing to the pre-configured images of the database image type, an executable statement is constructed to query the data using the corresponding rule parameters as query conditions.

4. The method according to claim 2, characterized in that, Each of the pre-configured images in the business process diagram represents the image type by its image shape and contains text content describing the corresponding rule parameters.

5. The method according to any one of claims 1 to 4, characterized in that, The directed lines in the business process diagram are also marked with jump conditions. Following the direction of the directed lines in the business process diagram, all constructed executable statements are combined to obtain a list of executable statements, including: The execution paths of all constructed executable statements are sorted according to the direction and jump conditions of the directed connections in the business process diagram to obtain a list of executable statements.

6. The method according to any one of claims 1 to 4, characterized in that, The list of executable statements to be executed includes: Each executable statement in the list of executable statements is executed sequentially, wherein, in two consecutively executed executable statements, the output of the former is used as the input parameter of the latter.

7. The method according to any one of claims 1 to 4, characterized in that, The business process diagram also includes annotations for the pre-configured image at the beginning of the traversal and / or for the pre-configured image at the end of the traversal.

8. A business processing device, characterized in that, include: The acquisition module is used to acquire a business process diagram provided by the client. The business process diagram includes at least two pre-configured images and directed lines between the at least two pre-configured images. Each pre-configured image represents a business process node and presents corresponding execution rules and rule parameters. The direction of the directed lines indicates the direction of the execution path. A module is created to traverse the pre-configured images in the business process diagram according to the direction of the directed connection in the business process diagram, so as to construct corresponding executable statements based on the execution rules and rule parameters of each traversed pre-configured image. The combination module is used to combine all the constructed executable statements according to the direction of the directed connection in the business process diagram to obtain a list of executable statements; The execution module is used to execute the list of executable statements and return the corresponding output results to the client.

9. An electronic device, comprising: processor; And a memory arranged to store computer-executable instructions, characterized in that, when executed, the executable instructions cause the processor to perform the method as described in any one of claims 1 to 7.

10. A computer program product, the computer program product comprising a computer-readable storage medium storing a computer program, characterized in that, The computer program is operable to cause the computer to perform the method as described in any one of claims 1 to 7.

Images