Order display method and device, computer equipment, storage medium and program product

Abstract

The invention relates to an order display method and device, computer equipment, a storage medium and a program product. The method comprises the steps of displaying order information in a target area of an order list page in response to received order information; and if target demand information is identified in the order information, displaying a target graphic identifier in a target area where the order information is located, determining a work order type and a work order execution requirement based on the target demand information, generating a target work order based on the work order type and the work order execution requirement, and sending the target work order to a corresponding work order terminal. The work order terminal is used for recording relevant information of executing a target work order by each corresponding processing node; and in response to a selection operation for the target graphic identifier, displaying execution information, sent by the work order terminal, for the target work order at each corresponding processing node. By adopting the method, the accuracy, automation and transparency of the order processing process can be realized.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to an order display method, apparatus, computer device, computer-readable storage medium, and computer program product. Background Technology

[0002] With the development of computer technology, electronic transaction platform technology has emerged, enabling the digital display of product information, the electronicization of transaction processes, and the networking of payment methods. To meet the growing personalized needs of consumers, personalized order requirements have gradually emerged.

[0003] In traditional methods, resource buyers typically enter order notes on the order page or contact customer service for relevant order notes. However, this approach suffers from scattered and inconsistent note information, and is prone to errors due to omissions or oversights by order preparation personnel (such as warehouse pickers and packers), ultimately leading to a poor user experience and increased after-sales costs. Summary of the Invention

[0004] Therefore, it is necessary to provide an order display method, apparatus, computer equipment, computer-readable storage medium, and computer program product that can achieve precision, automation, and transparency in the order processing process, in response to the aforementioned technical problems.

[0005] Firstly, this application provides an order display method, including:

[0006] Upon receiving order information, the order information is displayed in the target area of ​​the order list page;

[0007] If target demand information is identified in the order information, a target graphic identifier is displayed in the target area where the order information is located. Based on the target demand information, the work order type and work order execution requirements are determined. Based on the work order type and work order execution requirements, a target work order is generated and sent to the corresponding work order terminal. The work order terminal is used to record the relevant information of each processing node executing the target work order.

[0008] In response to the selection of the target graphic identifier, the execution information of the target work order at each corresponding processing node is displayed, sent by the work order terminal.

[0009] Secondly, this application also provides an order display device, comprising:

[0010] The first display module is used to display the order information in the target area of ​​the order list page in response to receiving the order information;

[0011] The work order generation module is used to identify target demand information in the order information, display the target graphic icon in the target area of ​​the order information, determine the work order type and work order execution requirements based on the target demand information, generate the target work order based on the work order type and work order execution requirements, and send the target work order to the corresponding work order terminal. The work order terminal is used to record the relevant information of each processing node executing the target work order.

[0012] The second display module is used to respond to the selection operation of the target graphic identifier and display the execution information of the target work order at each corresponding processing node sent by the work order terminal.

[0013] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps described in the above methods.

[0014] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps described in the methods.

[0015] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps described in the methods.

[0016] The aforementioned order display method, apparatus, computer equipment, computer-readable storage medium, and computer program product, in response to receiving order information, display the order information in a target area of ​​the order list page. If target demand information is identified in the order information, the work order type and execution requirements are determined based on this target demand information, and a target work order is generated based on the work order type and execution requirements. This automatically transforms users' vague and diverse personalized needs into standardized and clear job execution, thereby ensuring the accuracy and standardization of demand information. Furthermore, the target work order is sent to the corresponding work order terminal, enabling automatic allocation of work order tasks without manual intervention, greatly reducing the complexity of information processing and the probability of human error, and improving operational efficiency. In addition, a target graphic identifier is displayed in the target area where the order information is located, and in response to the selection of the target graphic identifier, the execution information of the target work order at each corresponding processing node sent by the work order terminal is displayed. This provides managers or customer service personnel with an intuitive and eye-catching visual marker, enabling them to quickly identify orders with special needs, and achieving transparent management and traceability of the entire work order process. Attached Figure Description

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

[0018] Figure 1 This is an application environment diagram of the order display method in one embodiment;

[0019] Figure 2 This is a flowchart illustrating an order display method in one embodiment;

[0020] Figure 3 This is a schematic diagram of an order list page in one embodiment;

[0021] Figure 4 This is a schematic diagram of an order details page in one embodiment;

[0022] Figure 5 This is a schematic diagram of a work order details page in one embodiment;

[0023] Figure 6 This is a structural block diagram of an order display device in one embodiment;

[0024] Figure 7 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0025] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0026] The order display method provided in this application embodiment can be applied to, for example, Figure 1In the application environment shown, terminal 102 communicates with server 104 via a network. Server 104 communicates with at least one work order terminal 106 via a network. In some embodiments, terminal 102 may also communicate directly with at least one work order terminal 106 to send the generated target work order to the corresponding work order terminal. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated on server 104 or placed on the cloud or other network servers. For example, a third-party server (e.g., an order platform) sends order information to terminal 102. In response to receiving the order information, the order information is displayed in the target area of ​​the order list page of terminal 102. If target requirement information is identified in the order information, a target graphic identifier is displayed in the target area where the order information is located. The work order type and work order execution requirements are determined based on the target requirement information, and a target work order is generated based on the work order type and work order execution requirements. Then, terminal 102 sends the target work order to the corresponding work order terminal 106. Relevant personnel can operate the work order terminal 106 to obtain the relevant information of the target work order and start the processing flow according to the target work order. After processing, in response to relevant personnel operating the work order terminal 106, the relevant processing results are input into the work order terminal 106. The work order terminal 106 then sends the relevant processing results to terminal 102 or server 104. This allows terminal 102 to display the execution information for the target work order at each corresponding processing node, sent by work order terminal 106, in response to the selection operation of the target graphic identifier. Terminal 102 and work order terminal 106 can be, but are not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, and projection devices. Portable wearable devices can include smartwatches, smart bracelets, and head-mounted devices. Head-mounted devices can be virtual reality (VR) devices, augmented reality (AR) devices, and smart glasses. Server 104 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services.

[0027] In one exemplary embodiment, such as Figure 2 As shown, an order display method is provided, which is applied to... Figure 1 Taking terminal 102 as an example, the explanation includes the following steps 202 to 206. Wherein:

[0028] Step 202: In response to receiving the order information, display the order information in the target area of ​​the order list page.

[0029] In this context, order information refers to the complete set of digitized data contained in a transaction within a trading system. Order information includes not only basic information such as order number, product list, quantity, price, and shipping address, but also all raw inputs that users may generate during the order placement process, such as the free text content in the "order remarks".

[0030] The order list page refers to the graphical user interface (GUI) that users (usually merchants or platform administrators) see in the backend management system. It displays and manages multiple orders. This page presents key summary information about the orders in a list or card format. For details, please refer to [link / reference]. Figure 3 As shown.

[0031] The target area, in the order list page, refers to the specific display area occupied by a single order's information. For example, in list view, it could be an entire row containing all the information for that order; in card view, it could be a single card representing that order.

[0032] For example, a resource purchaser places an order in a third-party system (e.g., an order system). The third-party server corresponding to the third-party system generates the corresponding order information and sends it to the server. The server then sends the order information to the terminal. Upon receiving the order information, the terminal displays the order information in target area 302 of the order list page (see reference). Figure 3 In this way, resource operators (such as managers, customer service personnel, and after-sales personnel) can obtain order information through the terminal's output device.

[0033] Step 204: If target demand information is identified in the order information, display the target graphic identifier in the target area where the order information is located, determine the work order type and work order execution requirements based on the target demand information, generate the target work order based on the work order type and work order execution requirements, and send the target work order to the corresponding work order terminal. The work order terminal is used to record the relevant information of each processing node executing the target work order.

[0034] Among them, target demand information refers to key information fragments related to preset value-added services (such as engraving, gift packaging, etc.) identified from order information (including raw, unstructured information, such as user notes) through specific algorithms or rules.

[0035] The target graphic identifier refers to a visual UI element, such as an icon, badge, or color-coded label. It is displayed within the target area of ​​the order and serves as a quick and intuitive visual signal to the operator that the order includes value-added services requiring special handling. See details for further information. Figure 3 The target graphic identifier is shown in Figure 301.

[0036] The work order type is a structured data field that categorizes value-added services. It defines the major categories of tasks to be performed, such as "gift wrapping," "product engraving," and "scheduled delivery." The system uses work order types to distinguish different processing flows and responsible departments.

[0037] The work order execution requirements are specific and clear operational instructions corresponding to the work order type. For example, for the "gift wrapping" type, the execution requirements might be "use red wrapping paper and add ribbon".

[0038] The target work order is a structured data entity containing all necessary information, including the associated order ID, work order type, work order execution requirements, current status, and creation time. It serves as a digital task credential connecting order requirements with specific execution stages. (Reference) Figure 5 , Figure 5 This page displays the details of a specific work order. The node area 502, corresponding to the work order processing flow, displays the execution information of each processing node.

[0039] A work order terminal refers to a work endpoint that is physically or logically responsible for executing a specific work order. It can be a PDA held by a warehouse picker, a tablet computer at a packaging station, a dedicated software interface, or a control interface for automated equipment. Its core functions are receiving work orders and providing feedback on the execution status. One work order terminal can correspond to multiple processing nodes.

[0040] In this context, processing nodes refer to the key stages or steps a work order goes through from creation to completion. For example, the processing nodes of a "gift wrapping" work order may include: "Pending allocation", "Picking", "Packaging", "Completed", and "Outbound".

[0041] For example, after receiving order information, the terminal analyzes the order information to determine whether target demand information exists in the order information. If the target demand information does not exist in the order information, subsequent steps are not executed. If the target demand information exists in the order information, a target work order needs to be generated based on the target demand information, so that relevant personnel or relevant equipment can execute the target work order. Furthermore, a target graphic identifier can be additionally displayed in the target area of ​​the order information displayed on the order list page, so that resource operators can intuitively identify orders with remarks information.

[0042] In some embodiments, the work order type and execution requirements corresponding to the target requirement information can be determined using keyword matching algorithms or regular expressions. Then, the corresponding work order terminal can be determined according to the work order type, and a target work order can be generated based on the work order execution requirements, and the target work order can be sent to the corresponding work order terminal.

[0043] In some embodiments, after generating a target work order based on the work order type and execution requirements, the target work order can be sent to the target workflow engine. The target workflow engine can determine the execution order of each target work order to be processed based on predefined business process information. The execution order can be, for example, parallel execution or serial execution. After determining the execution order of each target work order to be processed, the target workflow engine sends each target work order to the corresponding work order terminal according to the execution order. It also determines the timing of sending some target work orders by monitoring the execution information and execution order of the processing nodes of the work order terminal. For example, two target work orders a1 and b1 are generated based on order information A, and one target work order a2 is generated based on order information B. Work orders a1 and a2 belong to the same type of work order (type a) from different orders, and can be sent to the work order terminal matching type a in the order the order information arrives. According to the business process information type b, a work order can only be executed after a work order of type a is completed. Therefore, the target workflow engine can monitor the execution status of work orders of type a, and then send the work order of type b to the corresponding work order terminal after the work order of type a is completed. This allows the work order terminal to process the result of the completed work order of type a. This reduces the possibility of work order execution errors caused by sending the work order of type b to the corresponding work order terminal in advance, resulting in the terminal failing to correctly obtain the corresponding work order execution result. This implementation method can handle not only simple linear processes but also complex business logic, such as triggering "gift wrapping" only after "engraving" is completed.

[0044] Step 206: In response to the selection operation of the target graphic identifier, display the execution information of the target work order at each corresponding processing node sent by the work order terminal.

[0045] The execution information consists of data recorded and fed back by the work order terminal at each processing node, describing the current and historical status of the work order. Execution information includes, but is not limited to, node status, operator, operation time, remarks, and even on-site photos, forming a complete processing traceability chain for the work order.

[0046] For example, resource operators can click or hover over a target graphic icon in the target area of ​​the order list page on the terminal's output device. The terminal's output device will then display the execution information for the target work order sent by the work order terminal at each corresponding processing node. The execution information for each processing node can be found in [reference needed]. Figure 5 The node region 502 is shown in the figure.

[0047] Optionally, the execution information can be displayed directly on the order list page, or the user can click to jump to another page and display the execution information on that page.

[0048] In the above embodiments, by automatically converting vague user needs into structured work orders and supplementing them with visual status tracking, the problems of execution errors and management blind spots caused by unstructured information in traditional e-commerce processes are fundamentally solved. First, by identifying target demand information and generating target work orders, the accurate conversion from unstructured data to structured tasks is achieved, ensuring the accuracy and executability of information from the source. Second, by sending target work orders to the corresponding work order terminals, the task is accurately bound to the executing entity and pushed to the target, freeing operators from tedious information screening, significantly reducing the probability of errors and omissions due to human negligence, and improving the automation and execution efficiency of warehousing operations. Finally, by displaying target graphic icons and responding to selected operations to display execution information, a transparent monitoring system is built from the order list to the backend execution, enabling management or customer service personnel to intuitively and in real time grasp the processing progress of value-added services, achieve rapid problem location and traceability, and ultimately effectively reduce the company's after-sales communication costs and operational management costs while ensuring service quality and improving user experience.

[0049] In some embodiments, the order list page displays brief information about each order. By selecting a target area corresponding to an order on the order list page, the user is redirected to the order details page (see reference). Figure 4 This method displays detailed information about the order, including information about each target work order related to the order. This enables hierarchical management of order information. For example, the method further includes: in response to a selection operation on a target area, redirecting to an order details page, which includes brief information about each target work order corresponding to the order information; and in response to a selection operation on the order details page on a target work order, displaying detailed information about the target work order and its execution information at each corresponding processing node, including at least one of operator, operation time, and operation status information.

[0050] The selection of the target area refers to the interactive behavior of a user on the order list page, which involves using an input device (such as a mouse click or a finger touch) to select a specific display area (i.e., the target area) where a single order is located, with the intention of viewing more details of the order.

[0051] The order details page is a separate graphical user interface (GUI) used to centrally display all relevant information for a single order. It typically appears after a user clicks on an order in the order list and represents a deeper level of information than the order list itself.

[0052] The brief information for the target work order refers to the highly summarized information on the order details page, which outlines all value-added service work orders associated with the order. It typically includes only the most essential identifying information, such as the work order ID, work order type (e.g., "gift wrapping"), and current status (e.g., "processing"), with the aim of allowing users to quickly grasp the overall situation of all special tasks.

[0053] The detailed information for a target work order refers to the complete and comprehensive descriptive data displayed for a specific selected work order. This detailed information includes not only the content of the brief information but also all static and dynamic attributes related to the work order, such as its specific execution requirements (e.g., "use red wrapping paper"), creation time, and estimated completion time.

[0054] Here, "operator" refers to the person or automated system that actually executes the work order task at a specific processing node. "Operation time" refers to the timestamp when the corresponding operation of the work order is triggered or completed at a specific processing node. "Operation status information" refers to data describing the execution result of the work order at a specific processing node, such as "success," "failure," "in progress," or "skipped."

[0055] For example, when a user hovers their mouse over a target area on the order list page, the front-end can predictively initiate an API request to pre-fetch the order details and brief work order information. This way, when the user actually clicks and navigates to the page, the data may already be in the local cache, allowing the page to load instantly and improving the user experience. On the order details page, a component-based design can be used, with each work order brief information item being an independent component. This component internally manages its own "expand / collapse" state. When the user clicks on this component, it triggers an internal state change, which in turn initiates an API request to retrieve detailed information, rendering the retrieved data as the component's "expanded" view. This allows for a high degree of cohesion between the page's interaction logic and data retrieval logic, resulting in a clearer code structure and smoother interaction.

[0056] In this embodiment, a hierarchical information interaction path, from macro to micro and from overview to detail, is constructed to achieve efficient and accurate management of complex order statuses. First, by including brief information on each target work order on the order details page, this solution establishes an information-focused intermediate layer. This allows users to immediately gain a global and structured overview of all value-added service tasks involved in the order upon entering the order details page, avoiding information overload and achieving a clear transition from order to task set. Second, this solution adopts a progressive disclosure design principle, hiding the most detailed data after secondary interactions. This not only maintains the simplicity of the initial page but, more importantly, precisely guides query permissions and attention to the specific tasks that users care about. By displaying execution information including operator, operation time, and operation status, this solution constructs an immutable and clearly traceable digital footprint for each value-added service work order, enabling refined and transparent traceability of the execution process. Ultimately, this two-level interactive model transforms the originally fragmented and ambiguous order processing process into a well-structured, clearly defined, and fully controllable digital management system, greatly improving the efficiency of problem identification and the reliability of internal management.

[0057] In some embodiments, logistics information can also be displayed on the order details page, i.e., logistics information is generated based on the order information, so that the order information can be displayed in the first sub-area of ​​the target area and the logistics information can be displayed in the second sub-area of ​​the target area.

[0058] Logistics information refers to digital status data related to the physical transfer of ordered goods. Logistics information is typically generated by the logistics service provider's system and synchronized to the order system via an interface. Logistics information includes, but is not limited to, the name of the logistics company, the tracking number, the current logistics status of the package (e.g., "picked up," "in transit," "on delivery," "signed for"), the latest logistics node update time, and the estimated delivery time.

[0059] The first sub-area refers to a section within the target area that is visually or logically demarcated specifically for displaying the core information of the order. This information typically includes the order number, product thumbnail, buyer's nickname, and order amount, serving as the basic identifier of the order. The second sub-area refers to a section within the target area that is parallel to or adjacent to the first sub-area, specifically for displaying logistics information. Its function is to present the order's fulfillment status in an independent and prominent manner.

[0060] For example, after an order is shipped, the terminal can call the logistics service provider's API or receive push notifications from the logistics service provider to obtain logistics information. This information is then associated with the corresponding order ID and stored in the database. When a user requests the order list page, the server queries the order table and the logistics information table, aggregates the data from both, generates a composite data object containing both order and logistics information, and returns it to the terminal. After receiving the data, the terminal can use HTML and CSS technologies to create two side-by-side [images / objects] within the target area. The containers are designated as the first and second sub-regions, respectively. Then, the order information from the composite data object is rendered into the first sub-region, and the logistics information is rendered into the second sub-region, thus achieving partitioned display of information.

[0061] In this embodiment, by spatially integrating and logically separating basic order information and dynamic logistics information in the macro view of the order list, a significant improvement in information presentation density and efficiency can be achieved.

[0062] In some embodiments, the work order execution requirements include work order time requirements. After generating target work orders based on work order type and work order execution requirements, the process includes: determining the work order execution period for each target work order based on the work order time requirements; for each target work order, determining the node execution period for each corresponding processing node based on the work order execution period corresponding to the target work order; for each processing node, if the execution result information corresponding to the processing node is not received within the corresponding node execution period, generating exception information based on the information of the processing node.

[0063] Among them, the work order time requirement refers to the original constraint or expectation put forward by the user or business rules on the completion time of a certain value-added service. It can be a relative time (such as "completed before shipment" or "processed within 24 hours") or an absolute time (such as "must be delivered before 18:00 on December 24, 2023").

[0064] The work order execution deadline refers to the latest time that a work order must be completed, calculated based on its time requirements. The work order execution deadline is a specific, system-identifiable absolute timestamp (such as a specific date and time), and represents the final deadline for the entire work order lifecycle.

[0065] The node execution deadline refers to the latest completion time allocated to each specific processing node within the total execution period of the work order to ensure timely completion of the entire process. The node execution deadline is a sub-deadline for a single processing node obtained by decomposing the corresponding work order execution period, used for fine-grained control of the time consumed in each step.

[0066] Among them, the execution result information refers to the status data that the work order terminal returns to the system after completing the task of a certain processing node, indicating that the task of that node has been completed.

[0067] Anomaly information refers to an alarm message automatically generated when the system (including systems for terminals, servers, and work order terminals) detects that the actual completion time of a processing node exceeds the corresponding preset node execution deadline (or the terminal has not received the execution result information by the deadline). This anomaly information may include key elements such as the anomaly type, the associated work order ID, the timed-out processing node, the expected completion time, and the actual completion time, and is used to trigger subsequent intervention processes (such as notifying the supervisor, creating a high-priority task, etc.).

[0068] For example, after generating the target work order, the server calculates the work order execution deadline and the execution deadline of each node based on the work order time requirements and the preset standard time consumption for each node, and stores these timestamps as fields in the work order table and work order node table of the database. Simultaneously, the server can deploy a scheduled task that runs at fixed intervals (e.g., every minute). During runtime, this scheduled task queries the database, filtering out all processing nodes whose "status is incomplete" and whose "current time is greater than the node execution deadline". For each timed-out node, the system generates an exception record based on its information and inserts it into the exception information table, potentially triggering an email or SMS notification.

[0069] Optionally, after a work order is created and the execution deadlines for each node are calculated, the server or terminal can calculate the delay time corresponding to each processing node based on the node's execution deadline and the current time. Subsequently, the server or terminal can send a message containing the work order ID and node ID to a delay queue. If the processing node completes normally within the deadline, the work order terminal will send a "completion event." Upon receiving this event, the server or terminal can find and delete the corresponding pending message from the delay queue based on the work order ID and node ID. If the node times out and fails to complete, the pending message will arrive in the queue after a preset delay time and be consumed by a consumer (an exception handling service). Upon receiving the message, the service confirms that a timeout has occurred and then generates the corresponding exception information.

[0070] In this embodiment, by introducing the time dimension, a closed-loop management system can be constructed, from macro-level target decomposition to micro-level node monitoring and then to automatic anomaly triggering, thereby achieving proactive and predictive control over the work order processing process.

[0071] In some embodiments, after generating exception information based on the information of the processing node, the following steps may be performed: displaying an exception graphic identifier in the target area of ​​the order list page; and in response to a selection operation on the exception graphic identifier, displaying the exception work order and exception processing node information corresponding to the exception information.

[0072] Anomaly graphic markers are special visual elements used in user interfaces (UIs) to indicate that an order or work order has an abnormal status. These markers typically use striking colors (such as red or orange) and warning icons (such as exclamation marks or warning triangles) to clearly distinguish them from the target graphic markers. Their core function is to quickly attract the user's attention.

[0073] Among them, the exception handling node refers to the specific step in the work order execution process where a timeout or failure to complete as expected actually occurs.

[0074] For example, refer to Figure 3 In response to the selection of the abnormal graphic identifier 303, the abnormal work order and its handling node information corresponding to the abnormal information can be displayed directly on the order list page. Alternatively, in response to the selection of the abnormal graphic identifier 303, the user can be redirected to the order details page, where the abnormal graphic identifier is displayed in the work order area corresponding to the abnormal information.

[0075] Specifically, when the server generates exception information, it updates the order or work order record associated with the exception in the database, adds a status flag field, and stores the exception information's ID. When a user requests the order list page, the server can return this status flag along with the order information to the terminal. The terminal checks this status flag when rendering the target area for each order. If the flag is true, it renders the "exception graphic identifier"; otherwise, it either doesn't render or renders a normal identifier. When the user clicks on the exception identifier, the terminal sends an API request to the server to retrieve exception details, carrying the stored exception ID. The backend queries the database based on the exception ID, returning complete exception information, associated work order details, and specific information about the timeout processing node, which the terminal then displays accordingly.

[0076] In this embodiment, by automatically monitoring abnormal information from the server and transforming it into visual warning indicators and interactive details on the terminal, the information can be proactively pushed to the operator's field of vision in an intuitive and eye-catching manner, achieving real-time visual alerts for anomalies and greatly shortening the time it takes to discover problems. Furthermore, it transforms anomaly handling from a passive and vague investigation process into a proactive and precise localization process, thereby significantly improving the efficiency and accuracy of anomaly handling, effectively preventing small problems from escalating into major losses, and ensuring the stability and reliability of the order fulfillment process.

[0077] In some embodiments, after generating exception information based on the information of the processing nodes, the following steps may be performed: in response to a selection operation on the target area, jump to the order details page, and display an exception graphic identifier in the work order area corresponding to the exception work order corresponding to the exception information in the order details page; in response to a selection operation on the order details page for the exception work order, display the execution information of the exception work order at each corresponding processing node, and display an exception graphic identifier in the node area corresponding to the exception processing node corresponding to the exception information.

[0078] For example, after generating the exception information, the terminal displays an exception graphic icon in the target area where the corresponding order information is located. Clicking the exception graphic icon redirects the terminal's output device (e.g., a display screen) to the order details page. Since the order details page displays brief information about each work order, the exception graphic icon can be displayed in the work order area corresponding to the exception work order with the exception information on the order details page. In other words, the work order that has experienced an exception can be directly marked on the order details page using the exception graphic icon. Furthermore, clicking the work order area corresponding to the exception work order on the order details page or clicking the exception graphic icon displays the execution information of the exception work order at each corresponding processing node, and displays the exception graphic icon in the exception area corresponding to the exception processing node with the exception information.

[0079] In this embodiment, by constructing a multi-layered, progressive anomaly visualization navigation path from order to work order and then to processing node, it is possible to accurately locate and quickly diagnose complex business anomalies. Furthermore, through this progressively focusing visual guidance mechanism, abstract anomaly information is transformed into a clear and actionable "diagnostic funnel." This allows operators to follow a standardized path of "discovering problematic orders -> locating abnormal work orders -> locking down failure nodes," quickly tracing the root cause from the symptoms, thereby significantly shortening fault response and resolution time and improving the robustness and maintainability of the entire business process.

[0080] In some embodiments, determining the work order type and work order execution requirements based on target requirement information includes: extracting keywords from the target requirement information to obtain target keywords corresponding to the target requirement information; and / or matching the target keywords in the target requirement information based on target regular expressions; selecting work order types that match the target keywords from the target work order information database, as well as work order requirement information corresponding to the work order types; and extracting work order execution requirements that match the work order requirement information from the target requirement information.

[0081] Keyword extraction is a Natural Language Processing (NLP) technique that aims to automatically identify and extract words or phrases that best represent the core theme or intent of a text. Target keywords are key words with clear business meaning obtained from target information through keyword extraction or regular expression matching. For example, extracting "engraving" and "happy birthday" from "Please engrave a message for me, the content is 'Happy Birthday'". Target regular expressions are predefined, specific string templates used for pattern matching in text. Target regular expressions are a rule-based, precise matching technique suitable for extracting information with relatively fixed formats, such as matching the format "engraving content: [any character]".

[0082] The target work order information database is a structured data storage system (such as a database table, configuration file, or knowledge graph). The target work order information is used to store the mapping relationship between target keywords and work order types, as well as the standard parameter fields required for each work order type (i.e., work order requirement information).

[0083] The work order execution requirements refer to the specific values ​​extracted from the user's "target requirement information" and used to populate the "work order requirement information" template. For example, {"engraving content": "Happy Birthday", "font": "KaiTi", "position": "bottom right corner"}. It is a clear instruction on "how to do it specifically".

[0084] For example, the terminal can build a rule base containing a large number of "target regular expressions," each corresponding to a service mode (such as extracting engraving content). Upon receiving target requirement information, the system uses these regular expressions one by one for matching. If a match is successful, the matched keyword (such as "engraving") is taken as the "target keyword." Then, the terminal queries the target work order information database (e.g., a simple mapping table, such as a JSON file), and retrieves the corresponding work order type (such as "engraving") and work order requirement information (such as a template containing a "engraving content" field) based on the target keyword. Finally, the terminal uses the capture groups of the regular expression (i.e., the part within parentheses) to directly extract the specific values ​​and populate the template as the work order execution requirements. This requirement extraction process is simple, logically clear, and highly efficient.

[0085] In some embodiments, deep semantic analysis of the target requirement information can be performed based on NLP models, such as TF-IDF (Term Frequency-Inverse Document Frequency), TextRank algorithm, or a named entity recognition model based on BERT (Bidirectional Encoder Representations from Transformers), to automatically extract target keywords, rather than relying solely on fixed text patterns. For example, an NLP model can understand the similarity in intent between "carve a flower" and "engrave a character." The terminal can then input one or more extracted keywords into a target work order information database (which could be a more complex vector database or knowledge graph). Through semantic similarity calculation or exact matching, the most relevant work order type and its requirements are determined. Finally, the terminal can again utilize information extraction or relation extraction models from NLP technology to locate and extract the corresponding work order execution requirements (such as the specific value "Happy Birthday") from the original text based on known work order requirements (such as the field "engraving content"). This approach better handles the diverse and colloquial nature of user expressions, resulting in higher recognition accuracy.

[0086] In this embodiment, a multi-layered parsing process, from fuzzy to precise, automatically and accurately transforms users' unstructured natural language requirements into structured work order instructions that can be understood and executed by computers. This transforms a process that originally required manual interpretation and was prone to errors into a highly efficient, accurate, and scalable automated workflow, fundamentally solving a series of subsequent execution errors caused by misunderstandings of information.

[0087] In one exemplary embodiment, order push notifications from the e-commerce platform are monitored in real time via API or message queue, i.e., order information is received. In response to receiving order information, the order information is displayed in a target area of ​​the order list page. This order information is then processed to extract the corresponding key order fields. These key order fields may include, for example, product information and remarks related to the order.

[0088] If the order information contains remarks (i.e., the target requirement information mentioned above), then keywords are extracted from these remarks to obtain the target keywords corresponding to them. Alternatively, target keywords in the remarks are matched using a target regular expression. To determine the work order type corresponding to the remarks, work order types matching the target keywords, along with the corresponding work order requirements, are selected from the target work order information database. For example, if the remarks contain keywords such as "engraving," a "custom engraving work order" (one type of work order) is generated. If the remarks contain keywords such as "gift wrap," a "gift wrapping work order" (another type of work order) is generated.

[0089] For order information with remarks, such as Figure 3 As shown, the corresponding target graphic identifier 301 is displayed in the target area of ​​the order display. By clicking or hovering over the target graphic identifier 301, you can jump to a page displaying the detailed information of the work order (see reference). Figure 5 Alternatively, the corresponding work order information can be displayed directly on the order list page.

[0090] In addition, in this system, reference Figure 5 As shown, the system will also display detailed information about the target work order and its execution information at each corresponding processing node. This execution information includes at least one of the following: operator, operation time, and operation status. For example, the operator might be "Specialist A" or "Automation Equipment A," the operation time might be "2023-09-01 8:31:20," and the operation status might be "Operating." It can be understood that if the status information for a processing node is "Completed," a view control will be displayed in the node area corresponding to that processing node. In response to the selection of this view control, the execution completion result for that processing node will be displayed (e.g., an image taken of a packaged product).

[0091] In this embodiment, through the above steps, a business work order with clear user requirements can be generated immediately upon confirmation based on whether it is a special instruction order (e.g., a remark order), thus rigidly binding the subsequent processes for special requirements. Furthermore, when the work order circulates internally, the user requirements on the system can serve as the execution basis that each node must follow, ensuring that each position completes the service according to the instructions rather than other general operations. Additionally, "order information" and "work order identifier" are simultaneously displayed on the original order page of the e-commerce platform, forming a unified view and avoiding the need to switch between multiple systems such as customer service, warehousing, and logistics for searching. Moreover, clicking on the order item or work order identifier can expand the processing information of the work order at each flow node, enabling traceability and auditability of the special instruction execution process.

[0092] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0093] Based on the same inventive concept, this application also provides an order display device for implementing the order display method described above. The solution provided by this device is similar to the implementation described in the above method; therefore, the specific limitations in one or more order display device embodiments provided below can be found in the limitations of the order display method described above, and will not be repeated here.

[0094] In one exemplary embodiment, such as Figure 6 As shown, an order display device 600 is provided, including: a first display module 601, a work order generation module 602, and a second display module 603, wherein:

[0095] The first display module 601 is used to display the order information in the target area of ​​the order list page in response to receiving the order information.

[0096] The work order generation module 602 is used to identify target demand information in the order information, display a target graphic identifier in the target area where the order information is located, determine the work order type and work order execution requirements based on the target demand information, generate a target work order based on the work order type and work order execution requirements, and send the target work order to the corresponding work order terminal. The work order terminal is used to record the relevant information of each processing node executing the target work order.

[0097] The second display module 603 is used to display the execution information of the target work order at each corresponding processing node sent by the work order terminal in response to the selection operation of the target graphic identifier.

[0098] In some embodiments, the order display device 600 is further configured to: in response to a selection operation on a target area, jump to an order details page, the order details page including brief information of each target work order corresponding to the order information; in response to a selection operation on a target work order on the order details page, display detailed information of the target work order and execution information of the target work order at each corresponding processing node, the execution information including at least one of operator, operation time, and operation status information.

[0099] In some embodiments, after receiving the order information, the order display device 600 is further configured to: generate logistics information based on the order information; and display the order information in a target area of ​​the order list page, including: displaying the order information in a first sub-area of ​​the target area and displaying the logistics information in a second sub-area of ​​the target area.

[0100] In some embodiments, the work order execution requirements include work order time requirements. After generating target work orders based on work order type and work order execution requirements, the work order generation module 602 is further configured to: determine the work order execution period for each target work order based on the work order time requirements; for each target work order, determine the node execution period for each corresponding processing node based on the work order execution period corresponding to the target work order; for each processing node, if the execution result information corresponding to the processing node is not received within the corresponding node execution period, generate exception information based on the information of the processing node.

[0101] In some embodiments, after generating abnormal information based on the information of the processing node, the order display device 600 is further configured to: display an abnormal graphic identifier in a target area of ​​the order list page; and, in response to a selection operation on the abnormal graphic identifier, display the abnormal work order corresponding to the abnormal information and the information of the abnormal processing node.

[0102] In some embodiments, after generating exception information based on the information of the processing nodes, the order display device 600 is further configured to: in response to a selection operation on a target area, jump to the order details page and display an exception graphic identifier in the work order area corresponding to the exception work order corresponding to the exception information in the order details page; in response to a selection operation on the order details page for the exception work order, display the execution information of the exception work order at each corresponding processing node and display an exception graphic identifier in the node area corresponding to the exception processing node corresponding to the exception information.

[0103] In some embodiments, in determining the work order type and work order execution requirements based on target requirement information, the work order generation module 602 is specifically used to: extract keywords from the target requirement information to obtain target keywords corresponding to the target requirement information; and / or match the target keywords in the target requirement information based on target regular expressions; select the work order type that matches the target keywords from the target work order information database, as well as the work order requirement information corresponding to the work order type; and extract the work order execution requirements that match the work order requirement information from the target requirement information.

[0104] Each module in the aforementioned order display device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0105] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 7 As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements an order display method. The display unit of the computer device forms a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0106] Those skilled in the art will understand that Figure 7 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0107] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method embodiments.

[0108] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps in the above method embodiments.

[0109] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0110] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0111] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0112] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0113] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. An order display method, characterized in that, The method includes: Upon receiving order information, the order information is displayed in the target area of ​​the order list page; If target demand information is identified in the order information, a target graphic identifier is displayed in the target area where the order information is located. The work order type and work order execution requirements are determined based on the target demand information. A target work order is generated based on the work order type and the work order execution requirements. The target work order is sent to the corresponding work order terminal. The work order terminal is used to record relevant information of each corresponding processing node executing the target work order. In response to the selection operation of the target graphic identifier, the execution information of the target work order at each of the corresponding processing nodes sent by the work order terminal is displayed.

2. The method according to claim 1, characterized in that, After displaying the order information in the target area of ​​the order list page, the method further includes: In response to a selection operation on the target area, the user is redirected to the order details page, which includes brief information about each target work order corresponding to the order information. In response to the selection of a target work order on the order details page, the detailed information of the target work order and the execution information of the target work order at each of the corresponding processing nodes are displayed. The execution information includes at least one of the following: operator, operation time, and operation status information.

3. The method according to claim 1, characterized in that, After receiving the order information, the method further includes: Generate logistics information based on the order information; Displaying the order information in the target area of ​​the order list page includes: The order information is displayed in the first sub-region of the target area, and the logistics information is displayed in the second sub-region of the target area.

4. The method according to claim 1, characterized in that, The work order execution requirements include work order time requirements. After generating the target work order based on the work order type and the work order execution requirements, the process includes: The execution period for each target work order is determined based on the aforementioned work order time requirements; For each target work order, the execution period of each corresponding processing node is determined based on the execution period of the work order corresponding to the target work order; For each of the processing nodes, if the execution result information corresponding to the processing node is not received within the corresponding execution period of the processing node, an exception information is generated based on the information of the processing node.

5. The method according to claim 4, characterized in that, After generating the abnormal information based on the information from the processing node, the process includes: Display an abnormal graphic identifier in the target area of ​​the order list page; In response to the selection operation of the abnormal graphic identifier, the abnormal work order and abnormal processing node information corresponding to the abnormal information are displayed.

6. The method according to claim 4, characterized in that, After generating the abnormal information based on the information from the processing node, the process includes: In response to the selection operation of the target area, the user is redirected to the order details page, where an abnormal graphic identifier is displayed in the work order area corresponding to the abnormal work order corresponding to the abnormal information on the order details page; In response to the selection operation of the abnormal work order on the order details page, the execution information of the abnormal work order in each of the corresponding processing nodes is displayed, and the abnormal graphic identifier is displayed in the node area corresponding to the abnormal processing node corresponding to the abnormal information.

7. The method according to claim 1, characterized in that, The process of determining the work order type and work order execution requirements based on the target demand information includes: Extract keywords from the target demand information to obtain target keywords corresponding to the target demand information; and / or match the target keywords in the target demand information based on target regular expressions. Select the work order type that matches the target keyword from the target work order information database, and the work order requirement information corresponding to the work order type; Extract the work order execution requirements that match the work order requirement information from the target requirement information.

8. An order display device, characterized in that, The device includes: The first display module is used to display the order information in a target area of ​​the order list page in response to receiving the order information; The work order generation module is used to, if target demand information is identified in the order information, display a target graphic identifier in the target area where the order information is located, determine the work order type and work order execution requirements based on the target demand information, generate a target work order based on the work order type and the work order execution requirements, and send the target work order to the corresponding work order terminal. The work order terminal is used to record relevant information of each corresponding processing node executing the target work order. The second display module is used to display the execution information of the target work order at each of the corresponding processing nodes, sent by the work order terminal, in response to the selection operation of the target graphic identifier.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images