Service processing method and apparatus, electronic device, storage medium, and program product

Abstract

A service processing method and apparatus, an electronic device, a storage medium, and a program product, which can be applied to the technical fields of computer technology and service processing. The service processing method comprises: in response to receiving trigger information for a service to be processed, using entry information obtained by means of an information entry page for a work order to be filled to process the work order to be filled to obtain a target work order, wherein the work order to be filled is obtained on the basis of a target flowchart matching the trigger information, the target flowchart comprises at least two nodes having a sequential relationship, and the nodes represent processing steps of the service to be processed; and on the basis of the sequential relationship, using the at least two nodes to process the target work order, to obtain a service processing result for the service to be processed.

Description

Business processing methods and apparatus, electronic equipment, storage media and software products Technical Field

[0001] This disclosure relates to the fields of computer technology and business processing technology, and more specifically, to a business processing method and apparatus, electronic device, storage medium and program product. Background Technology

[0002] With the development of information management, more and more enterprises are automating tasks within business processes by creating workflows. A workflow refers to the process of automatically transmitting and executing a series of tasks in a specific order; that is, by defining the relationships and rules between tasks, business processes are automated and optimized. Summary of the Invention

[0003] In view of this, the present disclosure provides a business processing method and apparatus, electronic device, storage medium and program product.

[0004] According to one aspect of this disclosure, a business processing method is provided, comprising: responding to receiving trigger information for a pending business, processing the pending work order using input information obtained via an information input page to obtain a target work order, wherein the pending work order is obtained based on a target flowchart matching the trigger information, the target flowchart including at least two nodes having a sequential relationship, the nodes representing processing steps of the pending business; and processing the target work order using the at least two nodes based on the sequential relationship to obtain a business processing result for the pending business.

[0005] According to another aspect of this disclosure, a business processing apparatus is provided, comprising: a first processing module, configured to, in response to receiving trigger information for a business to be processed, process the work order to be filled using input information obtained via an information input page to obtain a target work order, wherein the work order to be filled is obtained based on a target flowchart matching the trigger information, the target flowchart including at least two nodes having a sequential relationship, the nodes representing processing steps of the business to be processed; and a second processing module, configured to process the target work order based on the sequential relationship using the at least two nodes to obtain a business processing result for the business to be processed.

[0006] According to another aspect of this disclosure, an electronic device is provided, comprising: one or more processors; and a memory for storing one or more instructions, wherein, when executed by the one or more processors, the one or more processors cause the one or more processors to perform the method as described in this disclosure.

[0007] According to another aspect of this disclosure, a computer-readable storage medium is provided having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the methods described in this disclosure.

[0008] According to another aspect of this disclosure, a computer program product is provided, which includes computer-executable instructions that, when executed, are used to perform the methods described in this disclosure. Attached Figure Description

[0009] The above and other objects, features and advantages of this disclosure will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0010] Figure 1 schematically illustrates a system architecture to which a business processing method can be applied according to an embodiment of the present disclosure;

[0011] Figure 2 schematically illustrates a flowchart of a service processing method according to an embodiment of the present disclosure;

[0012] Figure 3 schematically illustrates an example diagram of a flowchart generation interface according to an embodiment of the present disclosure;

[0013] Figure 4A schematically illustrates an example diagram of a conventional configuration item interface according to an embodiment of the present disclosure;

[0014] Figure 4B schematically illustrates an example diagram of an object configuration item interface according to an embodiment of the present disclosure;

[0015] Figure 4C schematically illustrates an example diagram of a mode configuration item interface according to an embodiment of the present disclosure;

[0016] Figure 4D schematically illustrates an example diagram of a work order status item interface according to an embodiment of the present disclosure;

[0017] Figure 4E schematically illustrates an example diagram of a timeout control interface according to an embodiment of the present disclosure;

[0018] Figure 4F schematically illustrates an example diagram of a timeout reminder interface according to an embodiment of the present disclosure;

[0019] Figure 4G schematically illustrates an example diagram of an interactive configuration item interface according to an embodiment of the present disclosure;

[0020] Figure 4H schematically illustrates an example diagram of a message notification item interface according to an embodiment of the present disclosure;

[0021] Figure 5 schematically illustrates an example diagram of a flowchart generation interaction process according to an embodiment of the present disclosure;

[0022] Figure 6 schematically illustrates an example of a target work order generation interaction process according to an embodiment of the present disclosure;

[0023] Figure 7A schematically illustrates an example of a target work order generation interaction process according to another embodiment of the present disclosure;

[0024] Figure 7B schematically illustrates an example of a target work order generation process according to another embodiment of the present disclosure;

[0025] Figure 8A schematically illustrates an example of a target work order generation interaction process according to yet another embodiment of the present disclosure;

[0026] Figure 8B schematically illustrates an example of a target work order generation process according to yet another embodiment of the present disclosure;

[0027] Figure 9 schematically illustrates an example of a process for processing a target work order based on a sequence relationship using at least two nodes according to an embodiment of the present disclosure;

[0028] Figure 10 schematically illustrates an example of the process for determining the mapping relationship between the execution object and the identifier of the second channel according to an embodiment of the present disclosure;

[0029] Figure 11 schematically illustrates a block diagram of a service processing apparatus according to an embodiment of the present disclosure; and

[0030] Figure 12 schematically illustrates a block diagram of an electronic device suitable for implementing a business processing method according to an embodiment of the present disclosure. Detailed Implementation

[0031] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0032] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0033] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0034] When using expressions such as "at least one of A, B, and C", they should generally be interpreted in accordance with the meaning that is commonly understood by a person skilled in the art (e.g., "a system having at least one of A, B, and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B, and C, etc.).

[0035] In the technical solution of this invention, the user information (including but not limited to user personal information, user image information, user device information, such as location information) and data (including but not limited to data used for analysis, stored data, and displayed data) involved are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of related data all comply with relevant laws, regulations, and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entry points for users to choose to authorize or refuse.

[0036] The core idea of ​​workflow is to break down a business process into multiple steps, each completed by different participants, and to ensure that these steps are executed in a predetermined order through specific mechanisms. However, in the process of drawing workflows, there are still significant limitations in terms of node attribute configuration, node timeout judgment, node duration adjustment, and notification methods.

[0037] Regarding the configuration of node attributes, it is difficult to flexibly set the information of the processing personnel and to dynamically adjust the work order status according to the business scenario.

[0038] Regarding the timeout judgment of nodes, when the processing time of a node in the business process exceeds the expectation, it is impossible to automatically trigger a timely and accurate timeout warning, and it is even more difficult to automatically execute the corresponding processing measures. As a result, timeout problems are often difficult to be discovered and resolved in the first place, which may cause delays or even interruptions in the business process, affecting the timeliness and stability of the entire workflow.

[0039] Regarding the adjustment of node duration, if the expected time of a node in a business process needs to be adjusted, the inherent hard-coded logic often cannot support such changes. This not only easily leads to business process interruption, but also increases the complexity of manual intervention and management. As a result, enterprises find it difficult to optimize workflows in a timely manner when faced with dynamic changes in business processes, lacking flexibility and thus reducing the overall workflow execution efficiency.

[0040] Regarding notification methods, the inability to flexibly configure push notifications based on different business needs makes it difficult to meet the high demands of complex workflows for real-time and personalized notifications. Furthermore, commonly used node notification methods, such as email, SMS, and system notifications, each have significant drawbacks: email notifications are easily ignored or delayed in viewing; SMS notifications are expensive and have limited content length; and system messages typically require users to actively log in to view them. All of these factors contribute to the inability to deliver process information to recipients in a timely and accurate manner, thereby affecting business processing efficiency and the timeliness and transparency of processes.

[0041] To this end, this disclosure provides a business processing method and apparatus, electronic device, storage medium, and program product, which can be applied to the fields of computer technology and business processing technology. The business processing method includes: in response to receiving trigger information for a pending business, processing a work order to be filled using input information obtained via an information input page to obtain a target work order, wherein the work order to be filled is obtained based on a target flowchart matching the trigger information, the target flowchart including at least two nodes with a sequential relationship, the nodes representing processing steps of the pending business; and processing the target work order based on the sequential relationship using at least two nodes to obtain a business processing result for the pending business.

[0042] Figure 1 schematically illustrates a system architecture to which the business processing method can be applied according to embodiments of the present disclosure. It should be noted that Figure 1 is merely an example of a system architecture to which embodiments of the present disclosure can be applied, to help those skilled in the art understand the technical content of the present disclosure, but does not imply that embodiments of the present disclosure cannot be used in other devices, systems, environments, or scenarios.

[0043] As shown in Figure 1, the system architecture 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, and a server 105. The network 104 is used as a medium to provide communication links between different devices.

[0044] It should be noted that the business processing methods provided in the embodiments of this disclosure can generally be executed by the server 105. Accordingly, the business processing apparatus provided in the embodiments of this disclosure can generally be located in the server 105.

[0045] Alternatively, the service processing method provided in this embodiment of the present disclosure can also be executed by the first terminal device 101, the second terminal device 102, or the third terminal device 103. Correspondingly, the service processing apparatus provided in this embodiment of the present disclosure can also be disposed in the first terminal device 101, the second terminal device 102, or the third terminal device 103.

[0046] It should be understood that the number of terminal devices, networks, and servers shown in Figure 1 is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0047] It should be noted that the sequence numbers of the operations in the following methods are for descriptive purposes only and should not be considered as indicating the execution order of the operations. Unless explicitly stated otherwise, the method does not need to be executed in the exact order shown.

[0048] The above describes the system architecture for applying business processing methods provided in this disclosure. The following will use Figure 2 as an example to further explain the business processing process of this disclosure.

[0049] Figure 2 schematically illustrates a flowchart of a service processing method according to an embodiment of the present disclosure.

[0050] As shown in Figure 2, the business processing method 200 includes operations S210 to S220.

[0051] In operation S210, in response to receiving trigger information for a pending business, the pending work order is processed using the input information obtained via the information input page to obtain the target work order. The pending work order is obtained based on a target flowchart that matches the trigger information. The target flowchart includes at least two nodes with a sequential relationship, and the nodes represent the processing steps of the pending business.

[0052] In operation S220, based on the sequential relationship, at least two nodes are used to process the target work order to obtain the business processing result for the business to be processed.

[0053] Before executing the business processing methods provided in this disclosure, at least one candidate flowchart can be developed in advance. It should be noted that each candidate flowchart corresponds to a specific business process, and each candidate flowchart is associated with a candidate work order. Candidate work orders may include text boxes, password boxes, hidden fields, multi-line text boxes, checkboxes, radio buttons, drop-down selection boxes, date pickers, and file upload boxes, etc., used to obtain various types of input fields. After developing at least one candidate flowchart, the flowchart information and corresponding candidate work order for each candidate flowchart can be stored to facilitate subsequent data analysis and record management.

[0054] Candidate flowcharts can include at least two nodes with a sequential relationship. Nodes represent processing steps in a business process, and the sequential relationship refers to the order in which the nodes occur, determining the flow of business processes. Different candidate flowcharts are used to implement the flow of each step in a business process for different application scenarios, and different candidate work orders are used to implement data collection and recording functions in business processes for different application scenarios. In one example, the application scenario can include at least one of the following: IT operations and maintenance, customer service, equipment maintenance, project management, and order maintenance.

[0055] For example, taking the IT operations and maintenance scenario as an example, since the business process of the IT operations and maintenance scenario can include steps such as problem recording, problem classification, problem handling and problem verification, the candidate flowchart 1 corresponding to this business process can include four nodes with a sequential relationship, namely node 11 for performing the problem recording step, node 12 for performing the problem classification step, node 13 for performing the problem handling step, and node 14 for performing the problem verification step. The above nodes 11 to 14 are executed sequentially.

[0056] Alternatively, taking the equipment maintenance scenario as an example, since the business process of the equipment maintenance scenario can include steps such as equipment inspection, fault recording, fault handling and equipment testing, the candidate flowchart 2 corresponding to this business process can include four nodes with a sequential relationship, namely node 21 for performing the equipment inspection step, node 22 for performing the fault recording step, node 23 for performing the fault handling step, and node 24 for performing the equipment testing step. The above nodes 21 to 24 are executed sequentially.

[0057] Pending business refers to business matters that need to be processed or resolved. For example, in a park infrastructure scenario, pending business could be equipment repair requests. Alternatively, in an internet scenario, pending business could be order management. Trigger information refers to the signal or condition that initiates the processing flow of pending business. The specific form of trigger information can be configured according to actual business needs and is not limited here. In one example, trigger information may include at least one of the following: user interaction with the interface, user voice commands, user dialogue context, and user eye movement information.

[0058] For example, user interaction with the interface refers to users manipulating elements of the front-end interface through input devices to input trigger information, such as clicking, swiping, or entering text. For instance, the trigger information could be that the user clicks on a pre-generated candidate flowchart for processing pending business on the computer screen, which would then become the candidate work order corresponding to that flowchart, ready to be filled out.

[0059] Alternatively, a user's voice command refers to the user inputting trigger information into the voice receiving device by speaking. For example, the trigger information could be that the user says "I want to report equipment repair" to the voice receiving device, in which case the candidate work order corresponding to the candidate flowchart of the "report equipment repair" business process can be used as the work order to be filled.

[0060] Alternatively, the user's dialogue context refers to obtaining triggering information by analyzing the content and intentions expressed by the user in previous rounds of dialogue. For example, the triggering information could be that the user mentions a device malfunction in the dialogue context and then asks how to report the device for repair. The dialogue context is the background of reporting the device for repair, so the candidate work order corresponding to the candidate flowchart of the "reporting the device for repair" business process can be used as the work order to be filled.

[0061] Alternatively, user eye movement information refers to obtaining trigger information through data on user eye movements acquired via eye-tracking technology. For example, the trigger information could be that the user moves their gaze to a pre-generated candidate flowchart on the computer screen for handling pending business tasks, and then the candidate work order corresponding to that flowchart can be used as a work order to be filled out.

[0062] After identifying the work orders to be filled, they can be processed to obtain the target work order. The method for obtaining the target work order can be configured according to actual business needs and is not limited here. For example, an information entry page can be displayed, and the user's input information can be obtained through this page. This input information can then be used to process the work orders to be filled and obtain the target work order. Alternatively, a large model can be invoked by designing prompts to process the work orders to be filled and obtain the target work order. Another alternative is to combine obtaining the user's input information through the information entry page with invoking a large model through designing prompts to process the work orders to be filled and obtain the target work order.

[0063] A work order to be filled out may include at least one work order item, which is the basic element constituting the form and used to collect user input data. Each work order item may correspond to a specific data type or user interaction method. The information entered in the work order item refers to the data entered by the user in these work order items. The specific type of work order item can be configured according to actual business needs and is not limited here. For example, the type of work order item may include at least one of the following: text input box, multi-line text box, radio button, checkbox, drop-down menu, file upload, and button, etc.

[0064] For each work order item, the user can enter the corresponding information on the information entry page. This allows the server to use the information from at least one work order item to fill out the work order and obtain the target work order. For example, a text input box can be used to collect short text information. A multi-line text box can be used to collect longer text information. A radio button can be used to select one option from multiple options. A checkbox can be used to select multiple options from multiple options. A drop-down menu can be used to select one or more options from a predefined list of options. A file upload function can be used to upload files. A button can be used to submit a work order or perform other operations.

[0065] Each node in the target flowchart is obtained by configuring multiple attribute items for the target element. These attribute items may include at least one of the following: general configuration items, object configuration items, mode configuration items, work order status items, timeout control items, timeout reminder items, message reminder items, and interaction configuration items. These attribute items are used to configure content related to the processing steps performed by the node, which may include, for example, the execution object and execution mode. For each node, based on the content related to the processing steps performed by the node, configured with these attribute items, the target work order can be processed according to the corresponding processing steps.

[0066] After obtaining the target work order, at least two nodes can be used to process it based on the sequential relationship between the nodes in the target flowchart to obtain the business processing result for the pending business. The business processing result refers to the data set of the processing results of the pending business, obtained by automatically driving each node to perform specific processing steps on the target work order through the target flowchart, so that the pending business is processed sequentially by each node. Processing can be understood as the flow of the completed target work order between the nodes of the target flowchart, so that the processing personnel at each node can process the target work order. For example, taking the IT operations and maintenance scenario mentioned above, after obtaining the target work order corresponding to candidate flowchart 1, the target work order will first pass through node 11, then through node 12, then through node 13, and finally through node 14 to obtain the business processing result for the IT operations and maintenance scenario.

[0067] In some examples, for server disk expansion in IT operations and maintenance scenarios, the business processing result can be the expansion capacity and the expansion effect. For example, the expansion capacity can be expanding the disk from 200GB to 500GB, and the expansion effect can be reducing the capacity utilization rate from 95% to 30%. For virtual machine resource deployment in IT operations and maintenance scenarios, the business processing result can include the virtual machine identifier and IP address. For example, the virtual machine identifier can be virtual machine 01, and the IP address can be 10.0.0.X. For server fault handling in IT operations and maintenance scenarios, the business processing result can include the fault cause and fault resolution suggestions. For example, the fault cause is memory fault, and the fault resolution suggestion is to replace the memory module.

[0068] Alternatively, taking the above equipment maintenance scenario as an example, after obtaining the target work order corresponding to candidate flowchart 2, the target work order will first pass through node 21, then through node 22, then through node 23, and finally through node 24 to obtain the business processing result of the equipment maintenance scenario.

[0069] In some examples, for firewall upgrade services in equipment maintenance scenarios, the service processing result may include the firewall version, for example, the firewall version may be v2.0; for server anomaly handling services in equipment maintenance scenarios, the service processing result may include the cause of the anomaly and an anomaly resolution suggestion, for example, the cause of the anomaly may be excessive temperature or abnormal fan cooling, and the anomaly resolution suggestion may be to replace the fan model. According to the embodiments of this disclosure, by responding to trigger information and processing work orders to be filled using entered information, the business processing flow can be automated and standardized, which helps to improve the efficiency and accuracy of business processing. At the same time, processing target work orders based on the sequential relationship of the target flowchart ensures the logic and coherence of business processing, improving the overall business management level and user experience.

[0070] Before executing the business processing method provided in this disclosure, at least one candidate flowchart can be developed in advance. The process of generating the candidate flowchart will be further explained below with reference to Figure 3, using the flowchart generation interface as an example.

[0071] Figure 3 schematically illustrates an example diagram of a flowchart generation interface according to an embodiment of the present disclosure.

[0072] As shown in Figure 3, in 300, the flowchart generation interface can be divided into three areas: a candidate element display area 310, a preview area 320, and a configuration area 330. The candidate element display area 310 displays multiple candidate elements, the preview area 320 previews the target element dragged by the user and the resulting candidate flowchart, and the configuration area 330 configures multiple attribute items of the target element. It should be noted that the positions of these three areas in the flowchart generation interface can be configured according to actual business needs and are not limited here.

[0073] Candidate elements represent components used to implement different functions. Specific functions can be configured according to actual business needs and are not limited here. For example, multiple candidate elements may include those for enabling the flowchart function, those for submitting work orders, those for approval functions, and those for ending the flowchart function, etc.

[0074] When creating a candidate flowchart, users can specify the candidate work order associated with the flowchart and enter at least one of the process name and process code to uniquely identify the candidate flowchart. In addition, users can also enter the business type corresponding to the candidate flowchart.

[0075] In one example, the user will drag or select from multiple candidate elements displayed in the candidate element display area 310 to the preview area 320, and set the order relationship between the at least two target elements. Then, the user will configure multiple attribute items for the target elements in the configuration area 330. These attribute items can include at least one of the following: general configuration items, object configuration items, mode configuration items, work order status items, timeout control items, timeout reminder items, message reminder items, and interaction configuration items. For example, in response to a user's trigger action on a specific attribute item, a configuration page for that attribute item can be displayed.

[0076] Users can configure multiple attribute items of a target element individually through the configuration page to obtain configuration information. For example, for regular configuration items, the user can configure the node's regular information through the configuration page for regular configuration items to obtain sub-configuration information for regular configuration items; for object configuration items, the user can configure the node's execution object through the configuration page for object configuration items to obtain sub-configuration information for object configuration items; for mode configuration items, the user can configure the node's execution mode through the configuration page for mode configuration items to obtain sub-configuration information for mode configuration items; and for work order status items, the user can configure the node's work order status through the configuration page for work order status items to obtain sub-configuration information for work order status items.

[0077] For timeout control items, the preset processing time of the node can be configured through the configuration page for timeout control items, resulting in sub-configuration information for timeout control items. For timeout reminder items, the node's need for timeout reminders, the recipient of reminders, the reminder interval, and the timeout reminder channel can be configured through the configuration page for timeout reminder items, resulting in sub-configuration information for timeout reminder items. For message reminder items, the node's operation buttons can be configured through the configuration page for interaction configuration items, resulting in sub-configuration information for interaction configuration items. For message reminder items, the recipient of reminders, the message reminder channel, and the message reminder template can be configured through the configuration page for message reminder items, resulting in sub-configuration information for message reminder items.

[0078] By configuring each attribute item as described above, at least one of the following can be identified as configuration information: sub-configuration information for general configuration items, sub-configuration information for object configuration items, sub-configuration information for mode configuration items, sub-configuration information for work order status items, sub-configuration information for timeout control items, sub-configuration information for timeout reminder items, sub-configuration information for interaction configuration items, and sub-configuration information for message reminder items. It should be noted that the specific configuration process for each of the above sub-configuration information can be found in Figures 4A to 4H, and will not be elaborated upon here.

[0079] After obtaining the configuration information of the target element through the configuration page, the configuration information can be used to generate nodes corresponding to the target element. These nodes can perform processing steps on the work order to achieve the function corresponding to the candidate element. After obtaining the nodes of at least two target elements, the nodes of at least two target elements can be used as candidate flowcharts.

[0080] For example, taking the creation of a candidate flowchart for the approval process of vehicle entry and exit applications as an example, one can drag a target element 1 for enabling the flowchart function, a target element 2 for enabling the work order function, two target elements 3 and 4 for enabling the approval function, and a target element 5 for enabling the flowchart function to end from the candidate element display area 310 to the preview area 320, and set the order relationship of the above five target elements. Then, in the configuration area 330, multiple attribute items of each target element are configured to generate node 321 corresponding to target element 1, node 322 corresponding to target element 2, node 323 corresponding to target element 3, node 324 corresponding to target element 4, and node 325 corresponding to target element 5, and use the above five nodes as candidate flowcharts for the approval process of vehicle entry and exit applications.

[0081] According to embodiments of this disclosure, by allowing users to flexibly select and configure target elements and their attributes, diverse candidate flowcharts can be quickly generated. This facilitates the expansion of node attributes based on actual business needs, meeting the personalized process design requirements of different business scenarios and improving the efficiency and adaptability of process design. Furthermore, since the completed flowchart, after review and deployment, meets business usage requirements without requiring modification of hard-coded processes, it reduces the limitations and adjustment costs associated with fixed processes. Modifying the flowchart allows for dynamic updates, improving the flexibility of flowchart creation and enhancing its scalability and maintainability.

[0082] In one example, in response to a user's triggering action on a regular configuration item in configuration area 330, a configuration page 400A for the regular configuration item can be displayed. The configuration method of the regular configuration item will be explained below with reference to Figure 4A.

[0083] Figure 4A schematically illustrates an example diagram of a conventional configuration item interface according to an embodiment of the present disclosure.

[0084] As shown in Figure 4A, configuration page 400A can be used to configure the general information of nodes. For example, general information may include at least one of the following: node identifier, node name, and node description.

[0085] By configuring the general information of nodes using regular configuration items, each node can have a clear node identifier, which facilitates the subsequent differentiation of configuration information of each node based on the node identifier, thus improving the efficiency and accuracy of node management. In one example, in response to a user's trigger operation on an object configuration item in configuration area 330, a configuration page 400B for the object configuration item can be displayed. The configuration method of the object configuration item will be explained below with reference to Figure 4B.

[0086] Figure 4B schematically illustrates an example diagram of an object configuration item interface according to an embodiment of the present disclosure.

[0087] As shown in Figure 4B, configuration page 400B can be used to configure the execution object of a node. The execution object refers to the approver of that node. For example, the execution object can include at least one of the following: the first object performing the flowchart generation operation, a second object distinct from the first object, a role, an organization, and the leader of the first object, etc. Roles set the roles in the business system, supporting one or more. Organizations set the organizational structure of the business system, supporting one or more.

[0088] After setting the execution object of a node, you can represent the execution object of each node by concatenating different strings in the flowchart file using the correspondence between node identifiers and execution objects. For example, node identifier = node1, execution object = role A; node identifier = node2, execution object = first object, which means that the execution object of node1 is role A, and the execution object of node2 is the first object.

[0089] By configuring the execution objects of nodes using object configuration items, the personnel responsible for each operation step can be precisely set according to the actual business process. This not only improves the precision of management but also facilitates subsequent process adjustments and optimizations, ensuring the rationality and effectiveness of the business process. Furthermore, because it supports multiple types of execution objects, it can adapt to complex and ever-changing business scenarios, improving the flexibility and adaptability of business processing. In one example, in response to a user's trigger operation on the mode configuration item in configuration area 330, the configuration page 400C for the mode configuration item can be displayed. The configuration method of the mode configuration item will be explained below with reference to Figure 4C.

[0090] Figure 4C schematically illustrates an example diagram of a mode configuration item interface according to an embodiment of the present disclosure.

[0091] As shown in Figure 4C, configuration page 400C can be used to configure the execution mode of a node. Execution mode refers to the way a task or operation is executed, specifying how the task to be processed flows and is handled among multiple execution objects. For example, execution modes can include one of the following: countersignature mode, OR sign-on mode, and normal mode.

[0092] The "countersigning" mode means that each execution object creates a task to be processed separately, and the process moves to the next node only if all tasks are approved. The "or sign" mode means that each execution object creates a task to be processed separately, and the process moves to the next node only if any one of the tasks is approved. The "normal" mode means that a task to be processed is created, and the process moves to the next node only if any one of the execution objects approves its task.

[0093] After setting the execution mode of a node, you can represent the execution mode of each node by concatenating different strings in the flowchart file using the correspondence between node identifiers and execution modes. For example, node identifier = node1, execution mode = countersigning mode; node identifier = node2, execution mode = OR sign mode. This means that the execution mode of node1 is countersigning mode, that is, creating pending tasks for each execution object of node1, and moving to the next node if all pending tasks pass; the execution mode of node2 is OR sign mode, that is, creating pending tasks for each execution object of node2, and moving to the next node if any one of the pending tasks passes.

[0094] By configuring the execution mode of nodes using mode configuration items, the flow and processing methods of target work orders across multiple execution objects on various nodes can be flexibly selected according to different business needs and process characteristics. This improves the granularity of process management and ensures the accuracy and efficiency of business processing. Furthermore, because it supports multiple types of execution modes, it can adapt to complex and ever-changing business scenarios, improving the flexibility and adaptability of business processing. According to embodiments of this disclosure, by clearly defining multiple execution objects and flexible execution modes, process management becomes more refined and flexible, helping to improve the processing efficiency of business processes and meet the needs of different business scenarios.

[0095] In one example, in response to a user's trigger operation on a work order status item in configuration area 330, a configuration page 400D for the work order status item can be displayed. The configuration method of the work order status item will be explained below with reference to Figure 4D.

[0096] Figure 4D schematically illustrates an example diagram of a work order status item interface according to an embodiment of the present disclosure.

[0097] As shown in Figure 4D, the configuration page 400D can be used to configure the work order status of nodes. For example, the work order status can include one of the following: New, Pending, Processing, Resolved, Suspended, Cancelled, etc.

[0098] During the flow of the flowchart, the flow of nodes can be monitored. When the flowchart reaches a certain node, the work order status configured for that node can be read and set to the status of a pending task. Alternatively, if a node does not have a status set, the status assignment operation can be skipped.

[0099] By configuring the work order status of nodes using work order status items, the actual situation of tasks to be processed on different nodes can be clearly reflected. This makes the progress of tasks to be processed readily apparent to the execution objects on the corresponding nodes, which helps improve the efficiency and accuracy of task management. In one example, in response to a user's trigger operation on the timeout control item in configuration area 330, the configuration page 400E for the timeout control item can be displayed; in response to a user's trigger operation on the timeout reminder item in configuration area 330, the configuration page 400F for the timeout reminder item can be displayed. The configuration methods for the timeout control item and the timeout reminder item will be explained below with reference to Figures 4E and 4F.

[0100] Figure 4E schematically illustrates an example diagram of a timeout control interface according to an embodiment of the present disclosure.

[0101] As shown in Figure 4E, configuration page 400E can be used to configure the preset processing time for nodes. The preset processing time can be configured according to the actual needs of the business. For example, the preset processing time can be 10 minutes. If it is found that the actual processing time does not match the set preset processing time, the process model can be dynamically updated by modifying the preset processing time setting of the corresponding node and re-reviewing and deploying.

[0102] After setting the preset processing time for nodes, you can represent the preset processing time of each node by concatenating different strings in the flowchart file using the correspondence between node identifiers and preset processing times. For example, if node identifier = node1, preset processing time = 10 minutes; node identifier = node2, preset processing time = 5 minutes, this means that the preset processing time for node1 is 10 minutes, meaning that if the actual processing time of node1 exceeds 10 minutes, node1 will time out; and the preset processing time for node2 is 5 minutes, meaning that if the actual processing time of node2 exceeds 5 minutes, node2 will time out.

[0103] By configuring the preset processing time of nodes using timeout control items, a clear time standard can be provided for the processing of each node, which facilitates the monitoring and management of task progress, timely detection and resolution of problems with excessively long or short processing times, ensures the smooth operation of business processes and the reasonable allocation of resources, and helps to improve the efficiency and quality of business processing.

[0104] Figure 4F schematically illustrates an example diagram of a timeout reminder interface according to an embodiment of the present disclosure.

[0105] As shown in Figure 4F, the configuration page 400F can be used to configure whether a node needs a timeout reminder, the recipient of the reminder, the reminder interval, and the timeout reminder channel.

[0106] The recipient of the reminder is the object to which the timeout reminder message is to be sent. For example, the recipient can include at least one of the following: a first object, a second object, a role, and a combination thereof. Furthermore, the recipient can also include a specific person; for example, you can specify the recipient as Zhang San by clicking the "Add Specific Person" button.

[0107] The reminder interval refers to the time interval between sending timeout reminder messages. For example, by enabling multiple reminders and setting the reminder interval to 1 minute, a timeout reminder message can be sent every minute.

[0108] The timeout reminder channel refers to the channel through which the timeout reminder message is sent. For example, the timeout reminder channel can include at least one of the following: in-site message, SMS, and email. The message content can be "Processing has timed out. Please handle it promptly. Click to view details."

[0109] By configuring timeout reminder settings for nodes, the processing progress of each node can be effectively monitored, avoiding delays caused by excessive processing time. Furthermore, the flexibility in configuring reminder recipients, intervals, and channels enhances the flexibility of reminder configuration for each node, ensuring that relevant personnel receive reminders promptly and take action, thus improving the timeliness and efficiency of business processing.

[0110] In one example, in response to a user's triggering action on an interactive configuration item in configuration area 330, a configuration page 400G for the interactive configuration item can be displayed. The configuration method of the interactive configuration item will be explained below with reference to Figure 4G.

[0111] Figure 4G schematically illustrates an example diagram of an interactive configuration item interface according to an embodiment of the present disclosure.

[0112] As shown in Figure 4G, the configuration page 400G can be used to configure the operation buttons for nodes. After a task is transferred to this node, the configured operation buttons can be displayed for the node's execution object to select an operation. Operation buttons can include at least one of the following: Signature, Close Order, Verify, Order Acceptance, and Start Work. For example, users can configure the operation buttons by selecting whether to display each button.

[0113] After setting the operation buttons for each node, you can represent the operation buttons for each node by concatenating different strings in the flowchart file according to the correspondence between node identifiers and operation buttons. For example, if node identifier = node1, operation button = close order; or node identifier = node2, operation button = grab order, it means that node1 will display the operation button "close order" and node2 will display the operation button "grab order".

[0114] By configuring the operation buttons of nodes using interactive configuration options, diverse operation options can be provided for execution objects according to different business scenarios and needs, better handling complex and ever-changing business processes. Furthermore, intuitive operation buttons enable the corresponding execution objects of each node to perform the required operations quickly and accurately, reducing operational complexity and error rates, and improving user experience and work efficiency.

[0115] In one example, in response to a user's triggering action on a message notification item in configuration area 330, a configuration page 400H for the message notification item can be displayed. The configuration method of the message notification item will be explained below with reference to Figure 4H.

[0116] Figure 4H schematically illustrates an example diagram of a message notification item interface according to an embodiment of the present disclosure.

[0117] As shown in Figure 4H, the configuration page 400H can be used to configure the reminder objects, message reminder channels, and message reminder templates for nodes.

[0118] The recipient of the notification refers to the object to which the message notification is to be sent. For example, the recipient can include at least one of the following: a first object, a second object, a role, and a combination thereof. Furthermore, the recipient can also include a specific person; for example, you can specify the recipient as Zhang San by clicking the "Add Specific Person" button.

[0119] Message notification channels refer to the channels through which message notifications are sent. For example, message notification channels may include at least one of the following: in-app messages, SMS, email, and a second channel. It should be noted that the in-app messages, SMS, and email notification channels mentioned above can be understood as the first channel. The difference between the second channel and the first channel lies in the recipient of the message notification; it needs to be converted from the user account information in the system to the relevant personnel information for the second channel.

[0120] When sending a message reminder to the recipient through the first channel, the recipient's identifier in the first channel is known. Therefore, the reminder information generated according to the message reminder template can be sent directly to the execution object of the node via the first channel. When sending a message reminder to the recipient through the second channel, the recipient's identifier in the second channel is unknown. Therefore, it is necessary to first convert the user account information in the system into relevant personnel information in the second channel, that is, to determine the mapping relationship between the execution object and the identifier of the second channel. Then, after the pending task of the node is detected, the user identity of the execution object in the second channel is found according to the mapping relationship, and the reminder information generated according to the message reminder template is sent to the execution object based on the user identity of the execution object in the second channel. For example, the user identity of the recipient in the system and the user identity in the second channel can be bound together. Then, after the task has been transferred to this node, the user identity in the second channel can be found, the message content can be assembled, and sent through the second channel. The message content can be "Transferred to this node, please process it in time, click to view details".

[0121] By configuring message notification settings for nodes, it is possible to ensure that relevant information from each node is delivered to relevant personnel in a timely and accurate manner during business processing. This avoids delays caused by information delays or omissions, improving the efficiency and accuracy of information transmission. Furthermore, the flexibility in configuring notification methods for each node is enhanced by flexibly setting the recipients, notification channels, and notification templates.

[0122] According to embodiments of this disclosure, by providing diverse attribute configuration options, the functionality of nodes can be flexibly customized according to actual business needs, improving the adaptability and accuracy of the process. Specifically, object configuration options ensure that tasks can be accurately assigned to specified objects; mode configuration options provide different execution methods to adapt to different scenarios; timeout control and timeout reminder options ensure the timeliness of the process and promptly notify relevant personnel; message reminder options enable efficient information transmission; and interaction configuration options enrich user operation options. Overall, this enhances the controllability, flexibility, and efficiency of the process, helps optimize business process management, and thus improves work efficiency and quality.

[0123] It should be noted that the configuration process of each attribute item shown in Figures 4A to 4H can be carried out during the generation stage of the candidate flowchart, or it can be carried out for the target flowchart that has been determined and matches the trigger information during the business processing.

[0124] In one example, the target flowchart includes nodes for at least two target elements. These target elements represent components used for different functions, and the nodes perform processing steps on work orders to achieve these functions. In response to detecting an operation on any node in the target flowchart, a configuration page for the target element corresponding to that node can be displayed. Configuration information for that node can be obtained through the configuration page, allowing the node corresponding to the target element to be updated using this information, resulting in the updated node.

[0125] For example, configuration page 400A can be used to configure the node's general information, and the obtained sub-configuration information for the general configuration items can be used to update the node, resulting in an updated node. Alternatively, configuration page 400B can be used to configure the node's execution object, and the obtained sub-configuration information for the object configuration item can be used to update the node, resulting in an updated node. Alternatively, configuration page 400C can be used to configure the node's execution mode, and the obtained sub-configuration information for the mode configuration item can be used to update the node, resulting in an updated node. Alternatively, configuration page 400D can be used to configure the node's work order status, and the obtained sub-configuration information for the work order status item can be used to update the node, resulting in an updated node.

[0126] Alternatively, configuration page 400E can be used to configure the preset processing time of the node, and the node can be updated using the obtained sub-configuration information for timeout control to obtain the updated node. Alternatively, configuration page 400F can be used to configure whether the node needs timeout reminders, the recipients of the reminders, the reminder interval, and the timeout reminder channel, and the node can be updated using the obtained sub-configuration information for timeout reminders to obtain the updated node. Alternatively, configuration page 400G can be used to configure the node's operation buttons, and the node can be updated using the obtained sub-configuration information for interaction configuration items to obtain the updated node. Alternatively, configuration page 400H can be used to configure the recipients of the reminders, the message reminder channel, and the message reminder template, and the node can be updated using the obtained sub-configuration information for message reminder items to obtain the updated node.

[0127] The flowchart generation process provided in this disclosure has been described above. The interactive process of flowchart generation will be further explained below with reference to Figure 5.

[0128] Figure 5 schematically illustrates an example diagram of a flowchart generation interaction process according to an embodiment of the present disclosure.

[0129] As shown in Figure 5, in 500, the flowchart generation interaction process can include the preliminary preparation stage, the flowchart drawing stage, and the review and deployment stage.

[0130] The preliminary preparation stage can include operations S501 through S506. For example, in operation S501, the user can edit dictionary data, dynamic forms, buttons, and process types on the front-end interface. In operation S502, the user sends the dictionary data, dynamic forms, buttons, and process types to the back-end server. In operation S503, the back-end server can save the dictionary data, dynamic forms, buttons, and process types to the database. In operation S504, the user can define basic process information on the front-end node. In operation S505, the user sends the basic process information to the back-end server. In operation S506, the back-end server can save the basic process information to the database.

[0131] The flowchart drawing process can include operations S507 through S510. For example, in operation S507, the user can select and drag target elements on the front-end interface. In operation S508, the user can configure the attribute information of the target elements on the front-end interface. In operation S509, the attribute information of the target elements is sent to the back-end server. In operation S510, the back-end server can save the flowchart information to the database.

[0132] The review and deployment phase can include operations S511 through S515. For example, in operation S511, the backend server can query flowchart information from the database. In operation S512, the flowchart information is sent to the frontend interface. In operation S513, the user can review the flowchart information on the frontend interface. In operation S514, after approval, the flowchart can be deployed. In operation S515, the backend server can save the available flowchart information to the database.

[0133] In the embodiments of this disclosure, after receiving trigger information for a pending service, a work order to be filled can be determined from multiple candidate work orders based on the trigger information. The method for determining the work order to be filled can be configured according to actual business needs and is not limited here.

[0134] In one example, after receiving a trigger message for a pending business transaction, a target flowchart matching the trigger message can be determined from multiple candidate flowcharts. The method for determining the target flowchart can be configured according to actual business needs and is not limited here. For example, the method for determining the target flowchart may include at least one of the following: keyword-based matching, rule-based matching, and flowchart structure-based matching.

[0135] For example, keyword-based matching involves pre-annotating each candidate flowchart, extracting key information as tags, and extracting key entities and actions as keywords from the trigger information. A text similarity algorithm is then used to calculate the similarity between the tags of each flowchart and the keywords in the trigger information, and the target flowchart that matches the trigger information is determined based on the similarity.

[0136] The alternative, rule-based matching method, refers to pre-defining trigger rules for each candidate flowchart based on the characteristics of the business process, using a rule engine to match the trigger information according to the rules, and determining the candidate flowchart that meets the rules as the target flowchart that matches the trigger information.

[0137] An alternative, flowchart-based matching method, involves pre-analyzing the structure of each candidate flowchart, including node types, connection relationships, and hierarchical structure, and determining the target flowchart by comparing the similarity between the triggering information and the flowchart structure based on the characteristics of the triggering information.

[0138] After identifying the target flowchart that matches the trigger information, the candidate work orders associated with the target flowchart can be identified as work orders to be filled, and an information entry page for the work orders to be filled corresponding to the target flowchart can be displayed.

[0139] According to embodiments of this disclosure, by determining a target flowchart that matches the triggering information among multiple candidate flowcharts and displaying the corresponding information entry page, the automated and intelligent matching of business processes can be achieved, improving the accuracy and efficiency of flowchart selection, thereby helping to improve the efficiency of business processing.

[0140] In another example, a third prompt message can be generated based on the trigger information. This third prompt message can guide the large model to identify the work order to be filled out from multiple candidate work orders that matches the trigger information. The large model is then invoked via this third prompt message to determine if the user intends to generate a work order. In response to the user's intent, the large model is invoked via the third prompt message to identify the work order to be filled out from multiple candidate work orders.

[0141] For example, the third prompt message could be based on the user input {input}, with candidate work orders including work order 1 and work order 2. Work order 1 has function 1 and function 2, and work order 2 has function 3. Please determine whether a work order needs to be generated and determine which type of work order it is.

[0142] According to embodiments of this disclosure, by leveraging the semantic understanding and matching capabilities of large models, the user's intent to generate a work order can be accurately determined, and the most suitable target work order can be quickly identified from multiple candidate work orders. This reduces the time and operational costs for users to manually search and select from numerous candidate work orders, optimizes business processing flows, enhances user experience, and improves the efficiency and accuracy of work order generation.

[0143] After generating the candidate flowchart, in response to receiving the trigger information for the pending business, the target work order can be obtained by processing the work order to be filled. In one example, the target work order can be obtained by processing the work order to be filled using the information entered by the user through the information entry page. This will be further explained below with reference to Figure 6.

[0144] Figure 6 schematically illustrates an example of a target work order generation interaction process according to an embodiment of the present disclosure.

[0145] As shown in Figure 6, in 600, the interactive process for generating the target work order may include operations S601 to S608.

[0146] When operating S601, users can input trigger information for the pending business through the front-end interface.

[0147] When operating S602, a trigger message is sent to the backend server.

[0148] When operating S603, the backend server can determine the target flowchart that matches the trigger information.

[0149] When operating S604, send flowchart information to the front-end interface.

[0150] When operating S605, the front-end interface displays an information entry page for work orders to be filled out, corresponding to the target flowchart.

[0151] When operating the S606, users can input information through the front-end interface.

[0152] When operating S607, input information is sent to the backend server.

[0153] When operating S608, the backend server can further verify whether the entered information meets preset completeness conditions. If the entered information meets the preset completeness conditions, it can be used to process the work order to be filled and obtain the target work order. The preset completeness conditions can be configured according to actual business needs and are not limited here. For example, the preset completeness conditions can be that all required fields have been filled or the filled content meets the format requirements.

[0154] In another example, the target work order can be obtained by calling a large model through design prompt words to process the work order to be filled out, which will be further explained below with reference to Figures 7A and 7B.

[0155] Figure 7A schematically illustrates an example of a target work order generation interaction process according to another embodiment of the present disclosure.

[0156] As shown in Figure 7A, in 700A, the interactive process for generating the target work order may include operations S701 to S704.

[0157] When operating the S701, users can input trigger information for the pending business through the front-end interface.

[0158] When operating S702, a trigger message is sent to the backend server.

[0159] When operating S703, the backend server can determine the target flowchart that matches the trigger information.

[0160] When operating S704, the backend server can use the large model to fill in the work orders to be filled in corresponding to the target flowchart, and obtain the target work order.

[0161] Figure 7B schematically illustrates an example diagram of a target work order generation process according to another embodiment of the present disclosure.

[0162] As shown in Figure 7B, in 700B, in response to receiving trigger information 701 for the pending business, a target flowchart 702 matching the trigger information 701 is determined, and the candidate work order associated with the target flowchart 702 is determined as the work order to be filled 703.

[0163] After obtaining the work order 703 to be filled, the second reference information 705 corresponding to the work order 703 can be determined. The second reference information 705 refers to the reference data related to the work order 703 to be filled, which is used to assist in generating the second prompt information 709.

[0164] In one example, the second reference information 705 can be obtained by performing data analysis on the data 704 related to the work order to be filled. Data analysis refers to the method of extracting useful information from the data 704 related to the work order to be filled through statistical, mining, and analysis techniques to obtain the second reference information 705.

[0165] For example, data 704 related to the work order to be filled can include historical energy consumption data. Historical energy consumption data refers to energy consumption data recorded over a past period, which can come from the energy consumption records of various devices within the park (such as electricity meters, water meters, gas meters, etc.). The method of obtaining historical energy consumption data can be configured according to actual business needs and is not limited here. For example, historical energy consumption data can be collected in real time based on the data acquisition layer, processed by the data synchronization layer, and finally stored in the data storage layer.

[0166] The data acquisition layer can be built on an IoT platform. The data synchronization layer can be built on Flink CDC and DataX. Flink CDC can capture energy consumption data changes in the IoT platform in real time and synchronize the data to the data storage layer in real time through an efficient stream processing mechanism to achieve real-time data synchronization; DataX can synchronize non-real-time or batch-processed data to the data storage layer through periodic extraction and batch import.

[0167] The data storage layer can be built based on the duplicate, unique, and aggregate models. The duplicate model can store basic data such as electricity meter data and water meter data in the park for backup and later statistical accuracy verification.

[0168] The unique model stores energy consumption data records for individual devices within the park using a merge-on-write approach to ensure metadata uniqueness. This avoids performance issues that may arise from merge-on-read in the aggregation model, guaranteeing accurate data updates and queries. The data storage layer built on this unique model can store data in tabular form. For example, tables named water_energy_hi, electricity_energy_hi, and gas_energy_hi can be designed to store water, electricity, and gas data respectively. Each table can include fields such as device ID, device region, store to which the device belongs, all objects associated with the device, time, unit of measurement, and energy consumption value for a given period.

[0169] Aggregation models are used to perform multi-dimensional aggregation processing on historical energy consumption data. This involves summarizing and integrating data from multiple different perspectives or dimensions to obtain aggregated results. For example, for the same key column (such as date, device ID) and its corresponding value column (such as energy consumption), they can be merged according to the set aggregation type (SUM, REPLACE, MAX, MIN, etc.). This allows for the aggregation of energy consumption calculations across different time dimensions of business energy efficiency, such as device time, region, and object dimensions, thereby improving data accuracy, reducing data storage space, and increasing data query efficiency.

[0170] The aggregation results include aggregated data from at least one of the following dimensions: time, region, and object. The time dimension refers to aggregating data from a time-related perspective; for example, calculating the energy consumption values ​​of a single table by day, month, or year. The region dimension refers to aggregating data from a geographical region or spatial distribution perspective; for example, calculating the energy consumption values ​​of all tables within a single region by day, month, or year. The object dimension refers to aggregating data from the perspective of a specific object or entity; for example, calculating the energy consumption values ​​of all tables of the same type under different merchants by day, month, or year.

[0171] Based on this, and using the aggregation model, energy consumption data can be aggregated and calculated according to time dimensions (such as day, month, year), regional dimensions, and object dimensions, generating aggregation tables such as energy_d, energy_m, energy_y, area_energy_d, area_energy_m, area_energy_y, shop_energy_d, shop_energy_m, and shop_energy_y. This facilitates energy efficiency analysis and querying from different perspectives, thereby reducing data storage space, improving data query efficiency, decoupling business logic, and improving the response speed of software interfaces.

[0172] In addition, Doris's real-time computing capabilities can be utilized to calculate and store year-on-year and month-on-month data across different dimensions in the Doris library. Year-on-year data is defined as: (current period energy consumption - energy consumption in the same period last year) / energy consumption in the same period last year * 100%, and month-on-month data is defined as (current period energy consumption - energy consumption in the previous period) / energy consumption in the previous period * 100%.

[0173] After obtaining the aggregation results, prediction tools can be used to analyze and predict the aggregation results to obtain the second reference information 705. The prediction tools can be tools or models used to predict future trends, situations, etc., such as time series analysis models, machine learning models, etc.

[0174] By generating a target work order 711 guided by the second reference information 705, it is possible to predict the energy consumption related to the pending business. Thus, based on the target work order 711, the predicted amount of electricity, water, gas, etc. can be recharged. In this case, the target work order 711 can be equivalent to an energy consumption prepayment notice, that is, a reminder notice to pay water and electricity fees before a certain object in the park is short of them.

[0175] It should be noted that, in the method of obtaining the second reference information 705 by performing data analysis and processing on the data 704 related to the work order to be filled out, all data obtained during the data analysis and processing can be displayed to users through the application layer, thereby providing park managers and users with diversified energy efficiency management functions and services. The application layer may include, for example, the park business system, the IOC platform, and a mobile APP.

[0176] For example, for the park's business system, it can provide park managers with a detailed energy efficiency analysis and management interface; support data retrieval and display via SQL and HTTP calls; and support multi-dimensional queries and report export. Alternatively, for the IOC platform, it can support real-time display of the park's overall energy efficiency status on a large screen; support obtaining key indicators such as energy consumption trends, regional comparisons, and object rankings via SQL sorting and search statements; and support setting energy consumption limits to achieve energy consumption early warning and monitoring functions. Alternatively, for the mobile app, it can provide a mobile access point for merchants and staff within the park; and support viewing energy consumption data and receiving energy consumption early warning notifications anytime, anywhere.

[0177] According to embodiments of this disclosure, by performing multi-dimensional aggregation and analysis prediction on data related to the work order to be filled, valuable information in the data can be deeply mined from different angles, providing a comprehensive and accurate basis for generating second reference information, which helps to improve the pertinence and effectiveness of work order processing.

[0178] In another example, the second reference information 705 can be obtained by enhancing the content of the data 704 related to the work order to be filled. Content enhancement refers to the method of enhancing the content of the data related to the work order to be filled through supplementation, improvement, optimization, etc., to obtain the second reference information 705.

[0179] For example, data 704 related to a work order to be filled may include at least one of the following: historical dialogue context, business data standards, and business metadata. Historical dialogue context refers to the content of previous conversations and interaction records between the user and the system. Business data standards refer to the specifications and standards for business data within an enterprise or organization. Business metadata refers to data that describes the business data, such as the data's structure, relationships, and definitions.

[0180] In this case, based on the triggering information, at least one of the following can be retrieved: historical dialogue context, business data standards, and business metadata, to obtain the second reference information 705. Relationship retrieval refers to searching and finding information by establishing relationships between data.

[0181] According to embodiments of this disclosure, by performing associated retrieval of data related to the work order to be filled based on trigger information, targeted second reference information can be obtained, providing data support for the filling and processing of work orders, which helps to improve the efficiency and accuracy of work order processing, and enhances the user experience and the overall quality of business processing.

[0182] According to embodiments of this disclosure, second reference information is obtained through various methods, providing rich evidence for the subsequent generation of prompt information. This helps to better guide the large model to supplement the work order to be filled, improves the accuracy and practicality of the prompt information, and thus enhances the efficiency and quality of the entire work order processing flow.

[0183] After obtaining the second reference information 705, the second prompt information 709 can be obtained based on the second reference information 705 corresponding to the work order 703 to be filled out, according to the preset prompt word set 706. The preset prompt word set 706 refers to a predefined set of words or phrases used to guide the generation of the second prompt information 709. These prompt words can help clarify the direction and content of the work order filling.

[0184] In one example, multiple fields in the work order 703 to be filled have at least one of the following relationships: association and / or hierarchy. Association refers to the interrelationship between different fields in the work order 703 to be filled; that is, filling in one field may affect the filling in other fields. Hierarchical relationship refers to the hierarchical structure between fields in the work order 703 to be filled; that is, some fields may be subordinate to other fields.

[0185] The preset prompt word set 706 can include a work order prompt word set and a field prompt word set. The work order prompt word set is a set of prompt words for the entire work order, used to generate global prompt information 707 to guide the filling direction of the entire work order. The field prompt word set is a set of prompt words for each field, used to generate local prompt information 708 to guide the specific content to be filled in for each field.

[0186] Based on the work order prompt word set and according to the second reference information 705, global prompt information 707 is generated. For each field in the work order 703 to be filled, local prompt information 708 is generated for each field based on the field prompt word set and according to the second reference information 705. Furthermore, based on the relationships and / or hierarchical relationships between multiple fields in the work order 703 to be filled, a second prompt information 709 can be generated by concatenating the global prompt information 707 and the local prompt information 708 for each field. The second prompt information 709 can be used to guide the large model to fill in each field of the work order to be filled, so that the resulting target work order meets the preset completeness conditions.

[0187] According to embodiments of this disclosure, by comprehensively considering the field relationships and hierarchical relationships of the work order to be filled, as well as the preset set of prompt words, more accurate and comprehensive first prompt information can be generated, thereby guiding the large model to fill in the work order more effectively. This not only improves the efficiency of work order processing, but also ensures the logic and standardization of work order information, and improves the accuracy and completeness of work order filling.

[0188] During the generation of the second prompt message 709, the actual operational status and historical data related to the pending business can also be obtained. For example, the actual operational status may include whether there are any major events on the day, the corresponding person's position, the store address, the priority level of the pending business, etc., while the historical data can be the historical processing status of the pending business. In addition, it can determine whether tool functions need to be used and provide corresponding tool designs, prompting the model whether these tools need to be applied.

[0189] Based on this, the generated second prompt message 709 can be: Combining the user input {the shop is leaking}, {please help me generate the relevant fields for creating a work order}, the business fields are [{determine the work order level: orderLevel}, {generate the work order description: description}, {location: address}], the auxiliary business information is {the leak is an emergency}, other business source data [username: Zhang San, shop address: first floor of the plaza], and historical data is {a repair request was submitted yesterday}. You are required to analyze and answer in human language. At the end of the article, for my convenience, the final judgment result is provided in JSON format, starting and ending with the string "struct".

[0190] The second prompt message 709 calls the large model 710 to fill in each field of the work order 703 to be filled in, and obtains the target work order 711 that meets the preset completeness conditions.

[0191] According to embodiments of this disclosure, by utilizing the natural language understanding and generation capabilities of large models, combined with a preset set of prompt words, work orders can be filled out automatically and accurately, reducing the time and effort users spend manually filling out work orders, ensuring the standardization and completeness of work order information, improving the efficiency and completeness of work order filling, and enhancing the automation level and processing efficiency of the overall business process.

[0192] In another example, the target work order can be obtained by combining the user's input information obtained through the information entry page with the large model called by designing prompt words, and then processing the work order to be filled in. The following will be further explained with reference to Figures 8A and 8B.

[0193] Figure 8A schematically illustrates an example of a target work order generation interaction process according to yet another embodiment of the present disclosure.

[0194] As shown in Figure 8A, in 800A, the interactive process for generating the target work order may include operations S801 to S809.

[0195] When operating S801, users can input trigger information for the pending business through the front-end interface.

[0196] When operating S802, a trigger message is sent to the backend server.

[0197] When operating S803, the backend server can determine the target flowchart that matches the trigger information.

[0198] When operating S804, send flowchart information to the front-end interface.

[0199] When operating S805, the front-end interface can display a page for users to enter information for work orders that are to be filled out, corresponding to the target flowchart.

[0200] When operating the S806, users can input information through the front-end interface.

[0201] When operating S807, input information is sent to the backend server.

[0202] When operating S808, the backend server can continue to verify whether the entered information meets the preset integrity conditions. If the entered information does not meet the preset integrity conditions, the large model can be used to supplement the entered information and obtain supplementary information.

[0203] When operating S809, the backend server can use supplementary information to process the work order to be filled and obtain the target work order.

[0204] Figure 8B schematically illustrates an example diagram of a target work order generation process according to yet another embodiment of the present disclosure.

[0205] As shown in Figure 8B, in 800B, in response to receiving trigger information 801 for the pending service, a target flowchart 802 matching the trigger information 801 is determined, and the candidate work order associated with the target flowchart 802 is determined as the work order 803 to be filled.

[0206] After receiving the work order (803) to be filled, the user can enter information (804) through the front-end interface. Entered information (804) refers to the specific content entered by the user on the information entry page. The back-end server can then further verify whether the entered information (804) meets preset completeness conditions.

[0207] In one example, in response to the fact that the entered information 804 does not meet the preset completeness condition, the large model 811 can be used to supplement the entered information 804 to obtain supplementary information 812. Supplementary information 812 refers to the information obtained after supplementing the incomplete entered information 804 using the large model 811.

[0208] For example, a first reference information 806 corresponding to the work order 803 to be filled can be determined. The first reference information 806 refers to reference data related to the work order 803 to be filled, used to assist in generating the first prompt information 810.

[0209] In one example, the first reference information 806 can be obtained by performing data analysis on the data 805 related to the work order to be filled. Data analysis refers to the method of extracting useful information from the data 805 related to the work order to be filled through statistical, mining, and analysis methods to obtain the first reference information 806.

[0210] For example, data 805 related to the work order to be filled out may include historical energy consumption data. This historical energy consumption data can be collected in real-time based on the data acquisition layer, processed by the data synchronization layer, and finally stored in the data storage layer. The construction methods of the data acquisition layer, data synchronization layer, and data storage layer will not be elaborated here.

[0211] Aggregation models are used to perform multi-dimensional aggregation processing on historical energy consumption data. This involves summarizing and integrating data from multiple different perspectives or dimensions to obtain the aggregation result. The aggregation result includes aggregated data from at least one of the following dimensions: time, region, and object. The time dimension refers to aggregating data from a time-related perspective, such as calculating the energy consumption values ​​of a single table by day, month, or year. The region dimension refers to aggregating data from a geographical region or spatial distribution perspective, such as calculating the energy consumption values ​​of all tables within a single region by day, month, or year. The object dimension refers to aggregating data from the perspective of a specific object or entity, such as calculating the energy consumption values ​​of all tables of the same type under different merchants by day, month, or year.

[0212] After obtaining the aggregation results, prediction tools can be used to analyze and predict the aggregation results to obtain the first reference information 806. Prediction tools can be tools or models used to predict future trends, situations, etc., such as time series analysis models, machine learning models, etc.

[0213] By generating supplementary information 812 guided by the first reference information 806, it is possible to predict the energy consumption related to the pending business. Thus, based on the subsequently generated target work order 813, the predicted amount of electricity, water, gas, etc. can be recharged. In this case, the target work order 813 can be equivalent to an energy consumption prepayment notice, that is, a reminder notice to pay water and electricity fees before a certain object in the park is short of them.

[0214] It should be noted that, in the method of obtaining the first reference information 806 by performing data analysis and processing on the data 805 related to the work order to be filled out, all data obtained during the data analysis and processing can be displayed to users through the application layer, thereby providing park managers and users with diversified energy efficiency management functions and services. The application layer may include, for example, the park business system, the IOC platform, and a mobile APP, etc., and the description of each application layer will not be elaborated here.

[0215] According to embodiments of this disclosure, by performing multi-dimensional aggregation and analysis prediction on data related to the work order to be filled, valuable information in the data can be deeply mined from different angles, providing a comprehensive and accurate basis for generating first reference information, which helps to improve the pertinence and effectiveness of work order processing.

[0216] In another example, the first reference information 806 can be obtained by enhancing the content of the data 805 related to the work order to be filled. Content enhancement refers to the method of enhancing the content of the data related to the work order to be filled through supplementation, improvement, optimization, etc., to obtain the first reference information 806.

[0217] For example, data 805 related to the work order to be filled may include at least one of the following: historical dialogue context, business data standards, and business metadata. Historical dialogue context refers to the content of previous conversations and interaction records between the user and the system. Business data standards refer to the specifications and standards for business data within an enterprise or organization. Business metadata refers to data that describes the business data, such as the data's structure, relationships, and definitions.

[0218] In this case, based on the triggering information, at least one of the following can be retrieved: historical dialogue context, business data standards, and business metadata, to obtain the first reference information 806. Relationship retrieval refers to searching and finding information by establishing relationships between data.

[0219] According to embodiments of this disclosure, by performing associated retrieval of data related to the work order to be filled based on trigger information, targeted first reference information can be obtained, providing data support for the filling and processing of work orders, which helps to improve the efficiency and accuracy of work order processing, and enhances the user experience and the overall quality of business processing.

[0220] According to embodiments of this disclosure, obtaining first reference information through various methods provides a rich basis for generating subsequent prompt information, which helps to better guide the large model to supplement the work order to be filled, improves the accuracy and practicality of the prompt information, and thus improves the efficiency and quality of the entire work order processing flow.

[0221] After obtaining the first reference information 806, the first prompt information 810 can be obtained based on the first reference information 806 corresponding to the work order 803 to be filled out, according to the preset prompt word set 807. The preset prompt word set 807 refers to a predefined set of words or phrases used to guide the generation of the first reference information 806. These prompt words can help clarify the direction and content of the work order filling.

[0222] In one example, multiple fields in the work order 803 to be filled have at least one of the following relationships: association and / or hierarchy. Association refers to the interrelationship between different fields in the work order 803 to be filled; that is, filling in one field may affect the filling in other fields. Hierarchical relationship refers to the hierarchical structure between fields in the work order 803 to be filled; that is, some fields may be subordinate to other fields.

[0223] The preset prompt word set 807 can include a work order prompt word set and a field prompt word set. The work order prompt word set is a set of prompt words for the entire work order, used to generate global prompt information 808 to guide the filling direction of the entire work order. The field prompt word set is a set of prompt words for each field, used to generate local prompt information 809 to guide the specific content to be filled in for each field.

[0224] Based on the work order prompt word set and according to the first reference information 806, global prompt information 808 is generated. For each field in the work order 803 to be filled, local prompt information 809 for each field is generated based on the field prompt word set and according to the first reference information 806. On this basis, based on the association and / or hierarchical relationship between multiple fields in the work order 803 to be filled, and according to the global prompt information 808 and the local prompt information 809 for each field, a first prompt information 810 can be generated by concatenating the global prompt information 808 and the local prompt information 809 for each field. The second prompt information 810 can be used to guide the large model 811 to fill in each field of the work order 803 to ensure that the resulting target work order 813 meets the preset completeness conditions.

[0225] According to embodiments of this disclosure, by comprehensively considering the field relationships and hierarchical relationships of the work order to be filled, as well as the preset set of prompt words, more accurate and comprehensive first prompt information can be generated, thereby guiding the large model to fill in the work order more effectively. This not only improves the efficiency of work order processing, but also ensures the logic and standardization of work order information, and improves the accuracy and completeness of work order filling.

[0226] During the generation of the first prompt message 810, the actual operational status and historical data related to the pending business can also be obtained. For example, the actual operational status may include whether there are any major events on the day, the corresponding personnel's positions, shop addresses, and the priority level of the pending business, while the historical data may include the historical processing status of the pending business. In addition, it can determine whether tool functions need to be used and provide corresponding tool designs, prompting the model whether these tools need to be applied.

[0227] The first prompt message 810 invokes the large model 811 to obtain supplementary information 812. The first prompt message 810 guides the large model 811 to complete the content of each unfilled field in the work order 803, so that the resulting target work order 813 meets the preset completeness conditions. The supplementary information 812 is used to fill in each field of the work order 803, resulting in the target work order 813 that meets the preset completeness conditions.

[0228] According to embodiments of this disclosure, by utilizing the natural language understanding and generation capabilities of large models, combined with a preset set of prompt words, work orders can be filled out automatically and accurately, reducing the time and effort users spend manually filling out work orders, ensuring the standardization and completeness of work order information, improving the efficiency and completeness of work order filling, and enhancing the automation level and processing efficiency of the overall business process.

[0229] According to embodiments of this disclosure, by using a large model to automatically supplement incomplete input information, the problem of incomplete information filled in by users can be effectively solved, while ensuring the integrity and standardization of work order information, which helps to optimize business process management and improve the efficiency and accuracy of work order processing.

[0230] The process of obtaining the target work order in this disclosure has been explained above. The following section, in conjunction with Figure 9, will further explain the process of processing the target work order based on the sequential relationship and using at least two nodes.

[0231] Figure 9 schematically illustrates an example of a process for processing a target work order based on a sequence relationship using at least two nodes according to an embodiment of the present disclosure.

[0232] As shown in Figure 9, in 900, the process of processing the target work order using at least two nodes based on the sequential relationship may include repeating the following operations S901 to S905 until the tasks to be processed by each of the at least two nodes are completed, and then executing operation S906.

[0233] It should be noted beforehand that the business to be processed can include multiple steps for processing the target work order. A step refers to the actual stage of business processing, and each node in the target flowchart is a visual abstraction of each step. That is, each step in the business to be processed can correspond to a node in the target flowchart.

[0234] For example, equipment maintenance operations may include equipment inspection, fault recording, fault handling, and equipment testing. The target flowchart corresponding to the equipment maintenance operations may include four nodes with a sequential relationship: node 1, which is used to perform equipment inspection steps in the equipment inspection stage; node 2, which is used to perform fault recording steps in the fault recording stage; node 3, which is used to perform fault handling steps in the fault handling stage; and node 4, which is used to perform equipment testing steps in the equipment testing stage. These four nodes are executed sequentially.

[0235] When operating S901, in response to the completion of the pending task at the previous node, the backend server can generate a pending task for the node at the current location based on timeout control items, interaction configuration items, and mode configuration items, according to the target work order. Timeout control items configure the preset processing time for the node. Interaction configuration items configure the node's operation buttons. Mode configuration items configure the node's execution mode.

[0236] For example, taking the equipment maintenance business mentioned above as an example, if there is no previous step, it means that the processing needs to start from the first step of the business to be processed and the first node in the target flowchart. Therefore, it can be determined that the current step is the equipment inspection step, and the corresponding node at the current position is node 1 used to execute the equipment inspection steps.

[0237] Alternatively, if the previous stage is the equipment inspection stage, and the corresponding node at the previous location is node 1 used to perform the equipment inspection steps, and the pending tasks at node 1 have been completed, then the current stage can be determined to be the fault recording stage, and the corresponding node at the current location can be node 2 used to perform the fault recording steps.

[0238] Similarly, if the previous stage is the fault recording stage and the corresponding node at the current position is node 2 used to perform the fault recording step, and the pending task of node 2 has been completed, it can be determined that the current stage is the fault handling stage and the corresponding node at the current position is node 3 used to perform the fault handling step.

[0239] Similarly, if the previous stage is a fault handling stage, and the corresponding node at the current position is node 3 used to execute fault handling steps, and the pending tasks of node 3 have been completed, then the current stage can be determined to be a device testing stage, and the corresponding node at the current position is node 4 used to execute device testing steps.

[0240] In operation S902, based on the object configuration items, a task to be processed is sent to the target client corresponding to the node at the current location. The object configuration items are used to configure the execution object of the node. The execution object refers to the approver of the node. For example, the execution object may include at least one of the following: a first object that performs the flowchart generation operation, a second object that is different from the first object, a role, an organization, and the leader of the first object, etc.

[0241] In one example, for each node, the client corresponding to each execution object can be identified as the target client based on the execution objects configured in the object configuration items, and the task to be processed can be sent to the target client.

[0242] For example, assuming the execution object of node 1 is configured as the first object, the execution object of node 2 is configured as both the first and second objects, the execution object of node 3 is configured as a role, and the execution object of node 4 is configured as the leader of the first object: If the current stage is an equipment inspection stage, and the corresponding node at the current location is node 1 used to perform equipment inspection steps, then a task to be processed can be sent to the client corresponding to the first object; if the current stage is a fault recording stage, and the corresponding node at the current location is node 2 used to perform fault recording steps, then a task to be processed can be sent to both the client corresponding to the first object and the client corresponding to the second object; if the current stage is a fault handling stage, and the corresponding node at the current location is node 3 used to perform fault handling steps, then a task to be processed can be sent to the clients corresponding to each execution object with role A; if the current stage is an equipment testing stage, and the corresponding node at the current location is node 4 used to perform equipment testing steps, then a task to be processed can be sent to the client corresponding to the leader of the first object. In operation S903, the target client displays the tasks to be processed through the front-end interface. Simultaneously, at least one operation button configured in the interaction configuration items can be displayed to the target client, allowing the target to process the task by triggering the operation button, thus achieving precise control over the workflow approval process. For example, the target can initiate the corresponding task processing operation by clicking or selecting the operation button.

[0243] According to embodiments of this disclosure, by displaying configured operation buttons on the front-end interface of the target client, the object can intuitively and conveniently trigger the processing operation of the task to be processed, thereby improving the efficiency of task processing and user experience.

[0244] When operating S904, the user executes pending tasks through the target client.

[0245] When operating S905, the target client corresponding to the node at the current location sends the execution result to the backend server.

[0246] When operating S906, the backend server receives the business processing results for the pending business.

[0247] The following example uses a target flowchart for a pending business transaction, comprising three nodes, to illustrate the process of processing a target work order using at least two nodes based on sequential relationships. During the flowchart drawing phase, after setting the execution object, execution mode, preset processing time, and operation buttons for each node in the target flowchart, different strings can be concatenated in the flowchart file using node identifiers and the corresponding relationships between the execution object, execution mode, preset processing time, and operation buttons to represent the execution object, execution mode, preset processing time, and operation buttons for each node.

[0248] For example, the flowchart file for this target process flow can be: Node Identifier = Node 1, Execution Object = Role A, Execution Mode = OR Sign-off Mode, Preset Processing Time = 10 minutes, Operation Button = Close Order; Node Identifier = Node 2, Execution Object = First Object & Second Object, Execution Mode = Normal Mode, Preset Processing Time = 5 minutes, Operation Button = Order Grab; Node Identifier = Node 3, Execution Object = First Object, Execution Mode = Countersigning Mode, Preset Processing Time = 7 minutes, Operation Button = None. This means that Node 1's execution object is Role A, the execution mode is OR Sign-off Mode, the preset processing time is 10 minutes, and the operation button "Close Order" will be displayed; Node 2's execution objects are First Object and Second Object, the execution mode is Countersigning Mode, the preset processing time is 5 minutes, and the operation button "Grab Order" will be displayed; Node 3's execution object is First Object, the execution mode is Normal Mode, the preset processing time is 7 minutes, and no operation button will be displayed.

[0249] For node 1, the backend server can create pending tasks for each execution object belonging to role A based on the 10-minute timer and the "Close Order" button, according to the target work order. It then sends these pending tasks to the target clients corresponding to each execution object belonging to role A. Since node 1 operates in OR / OR mode, once one of the target clients corresponding to each execution object belonging to role A completes its pending task and sends the execution result to the backend server, the processing phase of node 1 is complete, and the workflow can proceed to node 2.

[0250] For node 2, the backend server can create pending tasks for the first and second objects based on the 5-minute timer and the "grab an order" button, and send the pending tasks to the target clients corresponding to the first and second objects respectively. Since node 2 is in a countersigning mode, the processing phase of node 2 is only considered complete when both the target clients corresponding to the first and second objects have completed their pending tasks and sent the execution results to the backend server, and the process can then proceed to node 3.

[0251] For node 3, the backend server can create a pending task for the first object based on the target work order every 7 minutes, and send the pending task to the target client corresponding to the first object. Since node 3 is in normal mode, the processing stage of node 3 is considered complete when the target client corresponding to the first object completes the pending task and sends the execution result to the backend server, and the business processing result for the pending business can be obtained.

[0252] According to embodiments of this disclosure, by processing target work orders using at least two nodes based on sequential relationships, business processes can be automated and standardized, ensuring that tasks at each node are completed on time and as required, thus improving the efficiency and accuracy of business processing. Simultaneously, by setting configuration items such as timeout control items and interaction configuration items, the business process becomes more flexible and controllable, adapting to different business scenarios and needs, and contributing to improved overall business management and user experience.

[0253] In one example, in response to the creation of a pending task for a node, it can be determined whether the node has timeout enabled and whether an expected processing time has been set. If the node has timeout enabled and an expected processing time has been set, the node identifier and the node's expected processing time can be added to the task listener.

[0254] A node identifier is a tag or identification code used to uniquely identify a node. The expected processing time is the estimated completion time of the node task, determined based on configuration information such as timeout control settings. A task listener is a component used to monitor task status, capable of tracking task processing progress and status changes in real time, automatically triggering timeout logic, and avoiding insufficiently timely processing methods such as hard-coded methods and scheduled task polling.

[0255] Similarly, taking the target flowchart for a certain pending business as an example, which includes 3 nodes, when the pending task at node 1 is created, node 1 and 10 minutes can be added to the task listener; when the pending task at node 2 is created, node 2 and 5 minutes can be added to the task listener; when the pending task at node 3 is created, node 3 and 7 minutes can be added to the task listener.

[0256] According to embodiments of this disclosure, by adding node identifiers and expected processing times to the task listener, real-time monitoring and effective management of pending tasks on nodes can be achieved. This helps to promptly detect and address issues such as task timeouts, improves the timeliness and reliability of business processes, and ensures that tasks on each node are properly processed within the specified time, thereby enhancing overall business efficiency and service quality.

[0257] In one example, a task listener can monitor the processing status of pending tasks on a node based on a preset processing duration. Processing status refers to the current state of the task. For example, processing status can include at least one of the following: not started, in progress, completed, and timed out.

[0258] If a preset processing time in the task listener has been reached, the node identifier corresponding to that preset processing time can be retrieved from the task listener, along with the node information and associated process information. This information can then be used to query the processing progress of that node. For example, if the tasks pending at that node have been processed before the preset processing time has been reached, then that node has not timed out.

[0259] Alternatively, if the task listener detects that a preset processing time has elapsed between the current time and the time the task was created (meaning the task has not been processed by the preset processing time), then the node times out. Timeout reminders can then be periodically sent to the recipient via a pre-defined reminder channel until the task is successfully completed. For example, timeout reminders can be periodically sent to the recipient via a pre-set reminder channel at preset intervals until the task is successfully completed.

[0260] It should be noted that if a candidate flowchart has been running for a period of time and the code needs to be modified, the preset processing time of the relevant nodes needs to be adjusted according to the actual process approval. The above solution does not require code modification. Just modify the value of the preset processing time configured through the timeout control item during the flowchart drawing stage, and then redeploy the candidate flowchart to meet the new business adjustment requirements.

[0261] According to embodiments of this disclosure, by periodically sending timeout reminder messages at preset intervals and through preset channels when a pending task approaches or reaches a preset processing time, the task executor can be effectively urged to complete the task in a timely manner, avoiding the adverse effects of task timeout and improving the timeliness and efficiency of business processes.

[0262] In one example, the message notification channel may include a first channel and a second channel. The first channel represents the same channel used to obtain the entered information, while the second channel represents a channel different from the first channel. It is understood that when sending a message notification to a recipient through the first channel, the recipient's identifier in the first channel is known; when sending a message notification to a recipient through the second channel, the recipient's identifier in the second channel is unknown. For example, the first channel may include at least one of in-app messages, SMS, and email, and the second channel may include a public WeChat account.

[0263] Using a global listener, monitor the creation events of pending tasks for nodes. In response to the creation of pending tasks for a node, parse the information related to message alert items in the flowchart file and send alert messages generated based on the message alert template to the alerted objects through the message alert channel.

[0264] Therefore, when the message notification channel includes a first channel, notification information generated according to the message notification template can be sent directly to the execution object of the node via the first channel. The message notification template refers to a predefined format and content template for notification information, used to generate specific notification information. The notification information refers to the information generated based on the message notification template, used to remind the execution object to process tasks. When the message notification channel includes a second channel, it is necessary to first determine the mapping relationship between the execution object and the identifier of the second channel, and then, based on this mapping relationship, send the notification information to the execution object via the second channel.

[0265] According to embodiments of this disclosure, sending reminder information to the execution objects of nodes through multiple message notification channels ensures that reminder information is delivered to the execution objects in a timely and accurate manner, improving the timeliness and efficiency of task processing. Simultaneously, supporting different reminder channels enhances the system's flexibility and adaptability, meeting the needs of different users and scenarios, and improving user experience and the smoothness of business processes.

[0266] The process of determining the mapping relationship between the execution object and the identifier of the second channel will be further explained below with reference to Figure 10.

[0267] Figure 10 schematically illustrates an example of the process for determining the mapping relationship between the execution object and the identifier of the second channel according to an embodiment of the present disclosure.

[0268] As shown in Figure 10, in 1000, the process of determining the mapping relationship between the execution object and the identifier of the second channel may include operations S1001 to S1009.

[0269] When operating S100l, the execution object can log in to the mini-program via mobile device.

[0270] In operation S1002, the private domain identifier of the mini-program is obtained. The private domain identifier (such as unionid) refers to the identifier of the executed object within the private domain. When a user logs into the mini-program via a mobile device, the mini-program's private domain server checks whether the user has already bound their open platform account. If already bound, the existing private domain identifier can be returned directly; if not bound, a new private domain identifier will be generated based on the user's account information and parameters such as the mini-program from the open platform, and then bound to the user's account.

[0271] When operating S1003, send the private domain identifier to the platform.

[0272] In operation S1004, the platform establishes a mapping between platform identifiers and private domain identifiers. A platform identifier is a unique identifier for an execution object within a specific platform or system, used to identify and distinguish different execution objects within that platform.

[0273] In operation S1005, the target is followed by a second channel via a mobile device.

[0274] In operation S1006, the public domain identifier of the second channel is obtained. A public domain identifier (such as an OpenID) refers to the identifier of the execution object in the public domain or a specific public channel. When a user follows a second channel via a mobile device, the public domain server generates a public domain identifier based on the second channel's AppID and the user's account information using its internal algorithm. It should be noted that different second channels will have different public domain identifiers for the same user.

[0275] When operating S1007, send the public domain identifier to the platform.

[0276] When operating S1008, the platform establishes a correspondence between private domain identifiers and public domain identifiers.

[0277] In operation S1009, the platform obtains the mapping relationship between the platform identifier and the public domain identifier. Based on this, by using the correspondence between the platform identifier and the private domain identifier of the execution object, and the correspondence between the private domain identifier and the public domain identifier of the execution object, the mapping relationship between the platform identifier and the public domain identifier of the execution object can be obtained.

[0278] For users on each platform, the mapping relationship between their platform identifier and public identifier can be obtained through operations S1001 to S1009 described above, based on the correspondence between the user's platform identifier and private identifier, and the correspondence between the user's private identifier and public identifier. This allows for the identification association between users on each platform and users on the second channel. Therefore, when the message notification channel includes a second channel, the user's public identifier on the second channel can be retrieved based on the user's platform identifier, and message notifications can be sent to the user through the second channel based on the public identifier.

[0279] According to embodiments of this disclosure, by establishing a correspondence between the platform identifier, private domain identifier, and public domain identifier of the execution object, the mapping relationship between the execution object and the identifier of the second channel can be accurately determined. This enables the sending of reminder information to the execution object through different message reminder channels, improving the accuracy and flexibility of reminder information delivery, ensuring that information can be delivered to the execution object in a timely and effective manner, and enhancing the efficiency of business processes and user experience.

[0280] The above are merely exemplary embodiments, but are not limited thereto. Other business processing methods known in the art may also be included, as long as they can improve the efficiency and accuracy of business processing.

[0281] Based on the above-described business processing method, the present invention also provides a business processing apparatus. This apparatus will be described in detail below with reference to FIG11.

[0282] Figure 11 schematically illustrates a block diagram of a service processing apparatus according to an embodiment of the present disclosure.

[0283] As shown in Figure 11, the service processing device 1100 may include a first processing module 1110 and a second processing module 1120.

[0284] The first processing module 1110 is used to respond to receiving trigger information for a pending business, and to process the pending work order using the input information obtained through the information input page to obtain the target work order. The pending work order is obtained based on a target flowchart that matches the trigger information. The target flowchart includes at least two nodes with a sequential relationship, and the nodes represent the processing steps of the pending business.

[0285] The second processing module 1120 is used to process the target work order based on the sequential relationship using at least two nodes to obtain the business processing result for the business to be processed.

[0286] Any one or more of the modules, submodules, units, and subunits according to embodiments of the present disclosure, or at least part of the functions of any one or more of them, can be implemented in one module. Any one or more of the modules, submodules, units, and subunits according to embodiments of the present disclosure can be implemented by dividing them into multiple modules. Any one or more of the modules, submodules, units, and subunits according to embodiments of the present disclosure can be at least partially implemented as hardware circuitry, such as Field Programmable Gate Arrays (FPGAs), Programmable Logic Arrays (PLAs), Systems-on-Chip, Systems-on-Substrate, Systems-on-Package, Application-Specific Integrated Circuits (ASICs), or implemented in hardware or firmware by any other reasonable means of integrating or packaging circuitry, or implemented in software, hardware, or firmware, or in any suitable combination of any of these three implementation methods. Alternatively, one or more of the modules, submodules, units, and subunits according to embodiments of the present disclosure can be at least partially implemented as computer program modules, which, when run, can perform corresponding functions.

[0287] It should be noted that the service processing device part in the embodiments of this disclosure corresponds to the service processing method part in the embodiments of this disclosure. The description of the service processing device part is specifically referred to in the service processing method part, and will not be repeated here.

[0288] Figure 12 schematically illustrates a block diagram of an electronic device suitable for implementing a business processing method according to an embodiment of the present disclosure. The electronic device shown in Figure 12 is merely an example and should not be construed as limiting the functionality and scope of the embodiments of the present disclosure.

[0289] As shown in FIG12, a computer electronic device 1200 according to an embodiment of the present disclosure includes a processor 1201, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1202 or a program loaded from a storage portion 1209 into a random access memory (RAM) 1203. The processor 1201 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 1201 may also include onboard memory for caching purposes. The processor 1201 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0290] RAM 1203 stores various programs and data required for the operation of electronic device 1200. Processor 1201, ROM 1202 and RAM 1203 are interconnected via bus 1204.

[0291] According to embodiments of this disclosure, the electronic device 1200 may further include an input / output (I / O) interface 1205, which is also connected to the bus 1204. The electronic device 1200 may also include one or more of the following components connected to the input / output (I / O) interface 1205: an input section 1206 including a keyboard, mouse, etc.; an output section 1207 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1208 including a hard disk, etc.; and a communication section 1209 including a network interface card such as a LAN card, modem, etc. The communication section 1209 performs communication processing via a network such as the Internet. A drive 1210 is also connected to the input / output (I / O) interface 1205 as needed. A removable medium 1211, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 1210 as needed so that computer programs read from it can be installed into the storage section 1208 as needed.

[0292] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs, which, when executed, implement the business processing method according to the embodiments of this disclosure.

[0293] In this disclosure, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0294] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods provided in the embodiments of this disclosure. When the computer program product is run on an electronic device, the program code is used to enable the electronic device to implement the business processing methods provided in the embodiments of this disclosure.

[0295] When the computer program is executed by the processor 1201, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0296] According to embodiments of this disclosure, program code for executing computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages.

[0297] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. It should also be noted that in some alternative implementations, the functions indicated in the boxes may occur in a different order than those shown in the drawings.

[0298] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A business processing method, comprising: In response to receiving trigger information for a pending service, the system processes the pending work order using entry information obtained via an information entry page to obtain a target work order. The pending work order is derived based on a target flowchart matching the trigger information. The target flowchart includes at least two nodes with a sequential relationship, where each node represents a processing step of the pending service. Based on the aforementioned sequence relationship, the target work order is processed using the at least two nodes to obtain the business processing result for the pending business.

2. The method according to claim 1, further comprising, after receiving trigger information for the pending service: Among multiple candidate flowcharts, a target flowchart matching the triggering information is determined; and Display the information entry page for the work order to be filled corresponding to the target flowchart.

3. The method according to claim 2, wherein, The multiple candidate flowcharts were generated in the following way: In response to detecting an operation targeting at least two target elements among a plurality of candidate elements, a configuration page for each target element is displayed, wherein the configuration page is used to configure a plurality of attribute items for the target element, and the plurality of candidate elements represent components for different functions; and For each target element, in response to the configuration information obtained via the configuration page, a node corresponding to the target element is generated using the configuration information, and the nodes of each of the at least two target elements are used as the candidate flowchart, wherein the node performs the processing steps on the work order to achieve the function.

4. The method according to claim 1, wherein, The target flowchart includes nodes for at least two target elements, each representing a component for a different function, and the nodes perform the processing steps on the work order to achieve the function. The method further includes: In response to detecting an operation on the target element, a configuration page for the target element is displayed, wherein the configuration page is used to configure multiple attribute items of the target element; and In response to the configuration information obtained via the configuration page, the node corresponding to the target element is updated using the configuration information to obtain the updated node.

5. The method according to claim 4, wherein, The plurality of attribute items include at least one of the following: object configuration item, mode configuration item, timeout control item, timeout reminder item, message reminder item, and interaction configuration item; The object configuration item is used to configure the execution object of the node; The mode configuration item is used to configure the execution mode of the node; The timeout control item is used to configure the preset processing time of the node; The timeout reminder item is used to configure the reminder target, reminder interval, and timeout reminder channel for the node; The message notification item is used to configure the message notification channels and message notification templates for the node; The interaction configuration items are used to configure the operation buttons of the node.

6. The method according to claim 5, wherein, The process of processing the target work order using the at least two nodes based on the sequential relationship includes repeating the following operation until the pending tasks of each of the at least two nodes are completed: In response to the completion of the pending task at the node located at the previous position, for the node located at the current position, a pending task is generated according to the target work order based on at least one of the timeout control item, the interaction configuration item, and the mode configuration item. as well as Based on the object configuration items, the task to be processed is pushed to the target client so that the object can process the task through the target client.

7. The method according to claim 6 further includes, after generating the task to be processed based on the target work order according to the timeout control item and the interaction configuration item: In response to the creation of a pending task for the node, the node identifier and the expected processing time of the node are added to the task listener so that the task listener can monitor the processing status of the pending task for the node based on the preset processing time.

8. The method according to claim 7, wherein, The task listener monitors the processing status of the pending tasks on the node based on the preset processing time, including: In response to the fact that the time interval between the current moment and the time when the task to be processed was created is the preset processing time, according to the reminder interval, timeout reminder information is periodically sent to the reminded object based on the timeout reminder channel until the task to be processed is completed.

9. The method of claim 6, further comprising, after pushing the task to be processed to the target client based on the object configuration item: When the message notification channel includes a first channel, notification information generated according to the message notification template is sent to the execution object of the node via the first channel, wherein... The first channel is the same channel used to obtain the entered information; as well as When the message notification channel includes a second channel, the notification information is sent to the execution object via the second channel based on the mapping relationship between the execution object and the identifier of the second channel, wherein the second channel represents a channel that is different from the first channel.

10. The method according to claim 9, wherein, The mapping relationship between the execution object and the identifier of the second channel is determined based on the correspondence between the platform identifier and the private domain identifier of the execution object, and the correspondence between the private domain identifier and the public domain identifier of the execution object in the second channel.

11. The method of claim 6, further comprising: Based on the interaction configuration items, at least one configured operation button is displayed to the object through the target client, so that the object can process the task to be processed by triggering the operation button.

12. The method according to claim 6, wherein, The execution object includes at least one of the following: a first object that performs the flowchart generation operation, a second object that is distinct from the first object, a role, and an organization; The execution mode includes one of the following: countersigning mode, independent signing mode, and normal mode; The joint signature mode means that each of the execution objects creates a task to be processed, and the process flows to the next node after all the tasks to be processed have been approved. The aforementioned sign-on mode means that each of the execution objects creates the pending task, and the process flows to the next node if any one of the pending tasks passes. The normal mode means that the pending task is created and, in the case of any of the execution objects, the process flows to the next node through the pending task.

13. The method according to any one of claims 1 to 12, wherein, The process of using the input information obtained via the information input page to process the work order to obtain the target work order includes: In response to the fact that the entered information does not meet the preset completeness condition, the entered information is supplemented using a large model to obtain supplementary information; and Using the supplementary information, the work order to be filled is processed to obtain the target work order.

14. The method according to claim 13, wherein, The process of using a large model to supplement the entered information yields supplementary information including: Based on the first reference information corresponding to the work order to be filled out, and according to a preset set of prompt words, the first prompt information is obtained; and The first prompt message is used to call the large model to obtain the supplementary information. The first prompt message is used to guide the large model to supplement the content of each field that has not been filled in in the work order to be filled in, so that the obtained target work order meets the preset completeness condition.

15. The method according to claim 14, wherein, The first reference information was obtained through at least one of the following methods: Data analysis and processing are performed on the data related to the work order to be filled out to obtain the first reference information; and The data related to the work order to be filled out is subjected to content enhancement processing to obtain the first reference information.

16. The method according to claim 15, wherein, The data related to the work order to be filled in includes historical energy consumption data; The step of performing data analysis and processing on the data related to the work order to be filled in, to obtain the first reference information, includes: The historical energy consumption data is aggregated across multiple dimensions to obtain an aggregation result, wherein the aggregation result includes aggregated data from at least one of the time dimension, region dimension, and object dimension; and The aggregation results are analyzed and predicted using a prediction tool to obtain the first reference information.

17. The method according to claim 15, wherein, The data associated with the work order to be filled includes at least one of the following: historical dialogue context, business data standards, and business metadata; The step of performing content enhancement processing on the data related to the work order to be filled in, to obtain the first reference information, includes: Based on the triggering information, at least one of the historical dialogue context, business data standards, and business metadata is retrieved to obtain the first reference information.

18. The method according to any one of claims 14 to 17, wherein, The work order to be filled includes multiple fields with at least one of the following relationships: association and hierarchy; the preset prompt word set includes a work order prompt word set and a field prompt word set. The first prompt information, obtained based on the first reference information corresponding to the work order to be filled out and according to a preset set of prompt words, includes: Based on the work order prompt word set, and according to the first reference information, a global prompt message is generated; For each field in the work order that has not been filled in by the entered information, based on the field prompt word set and according to the first reference information, local prompt information is generated for each field; and Based on the association and / or the hierarchical relationship, the first prompt information is generated according to the global prompt information and the local prompt information for each of the fields.

19. The method according to any one of claims 1 to 18, further comprising, after determining the target flowchart matching the triggering information: Based on the second reference information corresponding to the work order to be filled out, and according to a preset set of prompt words, a second prompt message is obtained; and The second prompt message is used to invoke the large model, fill in the work order to be filled, and obtain the target work order. The second prompt information is used to guide the large model to fill in each field of the work order to be filled in, so that the resulting target work order meets the preset completeness condition.

20. The method according to any one of claims 1 to 19, further comprising, after receiving trigger information for the pending service: By using a third prompt message generated based on the trigger information, the large model is invoked to determine whether the user intends to generate a work order; and In response to the user's stated intent, the large model is invoked via the third prompt information to determine the work order to be filled out from the plurality of candidate work orders, wherein... The third prompt information is used to guide the large model to determine the work order to be filled that matches the trigger information among the multiple candidate work orders.

21. The method according to claim 1, wherein, The triggering information includes at least one of the following: user interaction with the interface, user voice commands, user dialogue context, and user eye movement information.

22. A business processing apparatus, comprising: A first processing module is configured to, in response to receiving trigger information for a pending service, process the pending work order using input information obtained via an information input page to obtain a target work order. The pending work order is obtained based on a target flowchart matching the trigger information. The target flowchart includes at least two nodes with a sequential relationship, and each node represents a processing step of the pending service. The second processing module is used to process the target work order based on the sequence relationship using the at least two nodes to obtain the business processing result for the business to be processed.

23. An electronic device, comprising: One or more processors; Memory, used to store one or more instructions. When the one or more instructions are executed by the one or more processors, the one or more processors cause the one or more processors to implement the method of any one of claims 1 to 21.

24. A computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the method of any one of claims 1 to 21.

25. A computer program product comprising computer-executable instructions, which, when executed, are used to implement the method of any one of claims 1 to 21.

Images