Work order system post-processing method, device, equipment and medium
By using the ticket context constructor and asynchronous storage post-plug-ins in the ticket system, the ticket system handles link verbose and data coverage problems are solved, and more efficient database access and data storage are achieved, ensuring data reliability and consistency.
Patent Information
- Application Number
- CN202510076212.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-01-17
- Publication Date
- 2025-05-23
AI Technical Summary
The existing work ticket system has long processing links, which leads to excessive frequent read and write operations and takes a long time, which increases database burden, and may lead to data overwrite in high concurrency situations.
Reduce database access times through a work ticket context constructor, and encapsulate it into independent modules using preloading, synchronous execution, asynchronous processing and database operations, simplifying business logic and improving code reuse rate. After the work ticket data is successfully saved, the asynchronous storage post-plug-in is used for post-asynchronous storage to optimize resource utilization and ensure data reliability and consistency.
It effectively reduces the number of database accesses, reduces the burden on the server, solves the data coverage problem caused by concurrency, simplifies business logic, improves code reuse, and optimizes resource utilization to ensure data reliability and consistency.
Smart Images

Figure CN120029540A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer technology, and in particular to a work order system post-processing method, device, equipment and medium. Background Art
[0002] The work order system is an important tool for enterprises to manage data and track user service requests. It can integrate multiple channels and seamlessly connect with other company systems, allowing enterprises to handle user issues more efficiently. By optimizing the post-processing process, the efficiency of work order processing and the work experience of customer service personnel can be significantly improved, while reducing resource consumption and data concurrency issues, thereby comprehensively improving the service quality and operational efficiency of the enterprise.
[0003] In existing technologies, there are often multiple links in the process from work order creation to final resolution, and since each work order information update requires recording or modifying the data in the database, the read and write operations are too frequent, the entire process takes a long time, and the database burden increases. Summary of the invention
[0004] In view of this, the present invention provides a work order system post-processing method, device, equipment and medium to solve the problem of too frequent read and write operations caused by lengthy processing links in the prior art.
[0005] In a first aspect, the present invention provides a post-processing method for a work order system, the method comprising:
[0006] Load the work order information from the database and use the work order context builder to generate the work order context required for the current operation;
[0007] Run the preloading plug-in to preload basic information, configuration items, and public resources into the context;
[0008] Execute synchronous plug-ins and asynchronous plug-ins, save the data that needs to be updated to the database, and reset the fields to be stored in the work order context;
[0009] After the work order data is saved successfully, use the asynchronous storage post-plugin for post-asynchronous storage.
[0010] The present invention reduces the number of database accesses and server burden by utilizing a work order context constructor and a workflow model based on the work order context, solves the problem of data overwriting caused by concurrency, and encapsulates preloading, synchronous execution, asynchronous processing, and database operations into independent modules to simplify the business logic implementation process and improve the code reuse rate. After the work order data is successfully saved, an asynchronous storage post-plug-in is used to perform post-asynchronous storage to optimize resource utilization and ensure data reliability and consistency.
[0011] In an optional implementation, after loading the work order information from the database, the method further includes:
[0012] The factory design pattern is used to create a work order context constructor, which is used to generate a work order context object.
[0013] The present invention adds a new work order context type without modifying the existing code through the factory design pattern, so as to improve the flexibility and scalability of the code, simplify the client code, clarify the responsibility, and improve the maintainability of the system.
[0014] In an optional implementation, after using the work order context builder to generate the work order context object required for the current operation, the method further includes:
[0015] Determine whether the work order plug-in matches;
[0016] If the ticket plugin matches, execute the steps to run the preloaded plugin;
[0017] If the work order plug-in does not match, the database is updated and the step of performing post-asynchronous storage using the asynchronous post-storage plug-in is executed.
[0018] The present invention determines the matching result of the work order plug-in and dynamically selects the most suitable processing method to flexibly adapt to different business needs and scenario changes, thereby improving flexibility and adaptability.
[0019] In an optional implementation, executing the synchronous plug-in and the asynchronous plug-in to save the data to be updated to the database includes:
[0020] Execute the synchronous sequential plug-in, execute the synchronous concurrent plug-in, and write to the database;
[0021] Execute asynchronous sequential plug-in, execute asynchronous concurrent plug-in, and write to the database.
[0022] The present invention ensures the real-time and consistency of data by combining the synchronous plug-in and the asynchronous plug-in, and processes multiple tasks in parallel by the synchronous concurrent plug-in and the asynchronous concurrent plug-in, so as to make full use of resources and improve the response speed.
[0023] In an optional implementation, after executing the asynchronous sequential plug-in, executing the asynchronous concurrent plug-in, and writing to the database, the method further includes:
[0024] Update field information in the database, including overdue reminders and user notifications.
[0025] The present invention quickly responds to user requests by updating field information in a database and feeds back results to the user, thereby improving response speed, avoiding blocking of the main process, and optimizing performance.
[0026] In an optional embodiment, the method further includes:
[0027] When data that needs to be saved again is detected, the steps of saving the data that needs to be updated to the database and resetting the fields to be stored in the ticket context are repeated.
[0028] The present invention repeatedly updates data to a database to ensure data consistency and integrity, reset fields to be stored, avoid unnecessary repeated writing operations, reduce load, and improve performance.
[0029] In a second aspect, the present invention provides a post-processing device for a work order system, the device comprising:
[0030] The generation module is used to load the work order information from the database and use the work order context builder to generate the work order context required for the current operation;
[0031] The preloading module is used to run the preloading plug-in to preload basic information, configuration items, and public resources into the context;
[0032] The execution module is used to execute synchronous plug-ins and asynchronous plug-ins, save the data to be updated to the database, and reset the fields to be stored in the work order context;
[0033] The storage module is used to perform post-asynchronous storage using the asynchronous storage post-plug-in after the work order data is successfully saved.
[0034] In a third aspect, the present invention provides a computer device, comprising: a memory and a processor, the memory and the processor are communicatively connected to each other, computer instructions are stored in the memory, and the processor executes the work order system post-processing method of the first aspect or any corresponding embodiment thereof by executing the computer instructions.
[0035] In a fourth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the work order system post-processing method of the first aspect or any corresponding embodiment thereof.
[0036] In a fifth aspect, the present invention provides a computer program product, comprising computer instructions for causing a computer to execute the work order system post-processing method of the first aspect or any corresponding embodiment thereof. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0038] Figure 1 is a flowchart of a post-processing method of a work order system according to an embodiment of the present invention;
[0039] Figure 2 is a schematic diagram of a post-processing flow of a work order system according to an embodiment of the present invention;
[0040] Figure 3 is a structural block diagram of a post-processing device of a work order system according to an embodiment of the present invention;
[0041] Figure 4 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION
[0042] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.
[0043] In the current work order processing process, there are mainly the following problems:
[0044] 1. Lengthy processing links: From work order creation to final resolution, it usually involves multiple levels of approval. The entire process takes a long time, resulting in a poor user experience and reduced overall work efficiency.
[0045] 2. Frequent database access: Since each work order information update requires recording or modifying the data in the database, the read and write operations are too frequent and time-consuming, and the database pressure is doubled, including but not limited to increased processor load, increased memory consumption, and a surge in the number of connections;
[0046] 3. Data coverage under high concurrency: Due to the use of a partial asynchronous processing mechanism, multiple updates occurring simultaneously under high concurrency may cause data to be incorrectly overwritten;
[0047] 4. Unclear responsibilities: The unclear allocation of responsibilities for each link in the entire processing chain increases the difficulty of maintenance and limits the maintainability and flexibility of the system.
[0048] According to an embodiment of the present invention, an embodiment of a post-processing method of a work order system is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.
[0049] In this embodiment, a work order system post-processing method is provided, which can be used in a mobile terminal. Figure 1 is a flowchart of a post-processing method of a work order system according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps:
[0050] Step S101, loading work order information from a database, and using a work order context constructor to generate a work order context required for the current operation.
[0051] In an embodiment of the present invention, all write operations on work orders are centrally managed to ensure data consistency and integrity, load the latest work order details from the database in real time, ensure that the data used in the processing process is the most accurate information, and use the work order context constructor to generate the work order context object required for the current operation.
[0052] Step S102: Run the preload plug-in to preload basic information, configuration items and public resources into the context.
[0053] In an embodiment of the present invention, a preloading plug-in is run to preload some commonly used basic information, configuration items, and public resources into the context to reduce repeated queries in subsequent operation steps, such as work order configuration, operator information, etc., thereby improving user experience.
[0054] Step S103, execute the synchronous plug-in and the asynchronous plug-in, save the data to be updated to the database, and reset the fields to be stored in the work order context.
[0055] In an embodiment of the present invention, a synchronous plug-in is executed in a sequential or parallel manner, and after processing, the data is saved to the database, and the fields to be stored in the work order context are reset. An asynchronous plug-in is also executed in a sequential or parallel manner, and after processing, the data is saved to the database, and the fields to be stored in the work order context are reset.
[0056] Step S104, after the work order data is successfully saved, post-asynchronous storage is performed using an asynchronous storage post-plug-in.
[0057] In the embodiment of the present invention, after confirming that the work order data is successfully saved, the asynchronous storage post-plug-in is used to implement operations that can only be performed after the work order data is successfully saved, such as point data collection. By clarifying the functional scope of various events and the relationship between them, duplication of work or unclear responsibilities can be avoided, and scalability and stability can be increased.
[0058] The post-processing method of the work order system provided in this embodiment reduces the number of database accesses and the server burden by utilizing the work order context constructor and the workflow mode based on the work order context, solves the problem of data overwriting caused by concurrency, and encapsulates preloading, synchronous execution, asynchronous processing, and database operations into independent modules to simplify the business logic implementation process and improve the code reuse rate. After the work order data is successfully saved, the asynchronous storage post-plug-in is used to perform post-asynchronous storage to optimize resource utilization and ensure data reliability and consistency.
[0059] In this embodiment, a post-processing method of a work order system is provided, and the process includes the following steps:
[0060] Step S201, loading work order information from a database, and using a work order context constructor to generate a work order context required for the current operation.
[0061] For details, please see Figure 1 Step S101 of the illustrated embodiment will not be described in detail here.
[0062] Step S202: Create a work order context constructor using the factory design pattern. The work order context constructor is used to generate a work order context object.
[0063] In an embodiment of the present invention, a factory design pattern is used to construct a work order context constructor, and a workflow pattern based on context transfer is adopted to reduce the number of unnecessary database accesses, thereby alleviating the burden on the server and solving the problem of data coverage caused by concurrency.
[0064] Commonly used data is cached in the work order context and updated only when the data changes. First, the work order context interface is defined, and specific context implementation classes are created for each different type of work order. The factory interface is defined, and multiple specific factory classes are implemented according to actual needs. Each factory class creates a work order context object of a certain category. The client calls the factory, passes in the necessary parameters through the factory interface, and obtains the work order context object.
[0065] The factory design pattern allows new work order context types to be added without modifying existing code, thereby improving code flexibility and scalability, simplifying client code, clarifying responsibilities, and improving system maintainability.
[0066] Step S203, determine whether the work order plug-in matches.
[0067] Step S204: If the work order plug-in matches, the step of running the preloaded plug-in is executed.
[0068] Step S205: If the work order plug-in does not match, the database is updated, and the step of performing post-asynchronous storage using the asynchronous post-storage plug-in is executed.
[0069] In the embodiment of the present invention, a plug-in matching mechanism is used to determine whether the work order plug-in matches. Specifically, the work order plug-in matches according to the work order type, business rules or other conditions. For matching plug-ins, step S206 is executed to run the preloaded plug-in to ensure consistency in subsequent processing. For unmatched plug-ins, the database (Database, DB) is updated, and step S209 is executed to trigger the post-asynchronous storage to process tasks that do not require immediate feedback.
[0070] By judging the matching results of the work order plug-in, the most suitable processing method is dynamically selected to flexibly adapt to different business needs and scenario changes, thereby improving flexibility and adaptability.
[0071] Step S206: Run the preload plug-in to preload basic information, configuration items and public resources into the context.
[0072] For details, please see Figure 1 Step S102 of the illustrated embodiment will not be described in detail here.
[0073] Step S207, execute the synchronous plug-in and the asynchronous plug-in, save the data to be updated to the database, and reset the fields to be stored in the work order context.
[0074] Specifically, the above step S207 includes:
[0075] Step S2071, execute the synchronous sequential plug-in, execute the synchronous concurrent plug-in, and write to the database.
[0076] Step S2072, execute the asynchronous sequential plug-in, execute the asynchronous concurrent plug-in, and write to the database.
[0077] In the embodiment of the present invention, the synchronous sequential plug-in and the synchronous concurrent plug-in are executed, and the specific fields (such as operation time, operation log, etc.) that need to be saved or updated to the database are set according to the context tool. After the processing is completed, the necessary data is written to the database, saved to the database, and the fields to be updated are reset. Similarly, the asynchronous sequential plug-in and the asynchronous concurrent plug-in are executed, and the processing results are also saved to the database, and the fields to be updated are reset.
[0078] By combining synchronous plug-ins with asynchronous plug-ins, the real-time and consistency of data can be ensured. By processing multiple tasks in parallel with synchronous concurrent plug-ins and asynchronous concurrent plug-ins, resources can be fully utilized and response speed can be improved.
[0079] Step S208, updating the field information in the database.
[0080] In an embodiment of the present invention, after executing the asynchronous sequential plug-in and the asynchronous concurrent plug-in, the field information in the database is updated, such as overdue reminders, user notifications, etc., to ensure that these operations do not block the main process.
[0081] By updating the field information in the database, we can quickly respond to user requests and feed back the results to users, thereby improving response speed, avoiding blocking the main process, and optimizing performance.
[0082] Step S209: After the work order data is successfully saved, the asynchronous storage post-placement plug-in is used for post-asynchronous storage.
[0083] For details, please see Figure 1 Step S103 of the illustrated embodiment will not be described in detail here.
[0084] In some optional embodiments, the method further comprises:
[0085] Step S210, when data that needs to be saved again is detected, the steps of saving the data that needs to be updated to the database and resetting the fields to be stored in the work order context are repeated.
[0086] In the embodiment of the present invention, for the data that needs to be saved again, the step of saving the data that needs to be updated to the database and resetting the fields to be stored in the work order context in step S207 is repeated.
[0087] The post-processing method of the work order system provided in this embodiment ensures the consistency and integrity of the data by repeatedly updating the data to the database, resets the fields to be stored, avoids unnecessary repeated writing operations, reduces the load, and improves performance.
[0088] like Figure 2 As shown, Figure 2 This is the post-processing flow chart of the work order system. First, the work order is written, the work order information is loaded, the work order context information is constructed, and the work order plug-in is matched. If the work order plug-in does not match, the database is directly updated and the post-storage plug-in is executed. If the work order plug-in matches, the pre-load plug-in is executed. Then the synchronous sequential plug-in is executed, the synchronous concurrent plug-in is executed, the database is written, the operation field is reset, and then the asynchronous sequential plug-in is executed, the asynchronous parallel plug-in is executed, the database is written, and the operation field is reset. Finally, the post-storage plug-in is executed and the process ends.
[0089] The post-processing method of the work order system provided by the embodiment of the present invention has the following advantages:
[0090] (1) Unified management of plug-in development and write operations: Develop corresponding synchronous and asynchronous plug-ins according to system business requirements, and uniformly manage and control the write operations of all work orders;
[0091] (2) System deployment and configuration: After completing the unified management of plug-in development and write operations, redeploy the work order system and optimize the preload-related configuration settings;
[0092] (3) Work order operations: Users can perform various work order related operations in the background of the work order system or on the passenger side, such as submitting new work orders, updating existing work order information, etc.
[0093] In this embodiment, a post-processing device for a work order system is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and will not be repeated hereafter. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.
[0094] This embodiment provides a post-processing device for a work order system, such as Figure 3 As shown, including:
[0095] The generation module 301 is used to load the work order information from the database and generate the work order context required for the current operation using the work order context constructor.
[0096] The preloading module 302 is used to run the preloading plug-in to preload basic information, configuration items and public resources into the context.
[0097] The execution module 303 is used to execute the synchronous plug-in and the asynchronous plug-in, save the data to be updated to the database, and reset the fields to be stored in the work order context.
[0098] The storage module 304 is used to perform post-asynchronous storage using an asynchronous storage post-plug-in after the work order data is successfully saved.
[0099] In some optional embodiments, the device further comprises:
[0100] A creation module is used to create a work order context constructor using the factory design pattern. The work order context constructor is used to generate a work order context object.
[0101] In some optional embodiments, the device further comprises:
[0102] The judgment module is used to determine whether the work order plug-in matches.
[0103] The first execution module is used to execute the step of running the preloaded plug-in if the work order plug-in matches.
[0104] The second execution module is used to update the database and execute the step of performing post-asynchronous storage using the asynchronous post-storage plug-in if the work order plug-in does not match.
[0105] In some optional implementations, the execution module 303 includes:
[0106] The first execution unit is used to execute the synchronous sequential plug-in, execute the synchronous concurrent plug-in, and write into the database.
[0107] The second execution unit is used to execute the asynchronous sequential plug-in, execute the asynchronous concurrent plug-in, and write to the database.
[0108] In some optional embodiments, the device further comprises:
[0109] The update module is used to update the field information in the database, including overdue reminders and user notifications.
[0110] In some optional embodiments, the device further comprises:
[0111] The re-execution module is used to repeatedly save the data that needs to be updated to the database and reset the fields to be stored in the work order context when detecting data that needs to be saved again.
[0112] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.
[0113] The post-processing device of the work order system in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.
[0114] The embodiment of the present invention also provides a computer device having the above Figure 3 The post-processing device of the work order system is shown.
[0115] See also Figure 4 , Figure 4 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 4As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting the components, including a high-speed interface and a low-speed interface. Each component communicates with each other using different buses and can be installed on a common motherboard or in other ways as needed. The processor can process instructions executed within the computer device, including instructions stored in the memory or on the memory to display graphical information of the GUI on an external input / output device (such as a display device coupled to the interface). In some alternative embodiments, if needed, multiple processors and / or multiple buses can be used together with multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (such as an array of servers, a set of blade servers, or a multi-processor system). Figure 4 In the figure, one processor 10 is taken as an example.
[0116] The processor 10 can be a central processing unit, a network processor, or a combination thereof. Among them, the processor 10 can further include a hardware chip. The above hardware chip can be an application-specific integrated circuit, a programmable logic device, or a combination thereof. The above programmable logic device can be a complex programmable logic device, a field-programmable gate array, a generic array logic, or any combination thereof.
[0117] Among them, the memory 20 stores instructions executable by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiments.
[0118] The memory 20 can include a program storage area and a data storage area. Among them, the program storage area can store an operating system and application programs required for at least one function; the data storage area can store data created according to the use of the computer device, etc. In addition, the memory 20 can include a high-speed random access memory and can also include a non-transitory memory, such as at least one disk storage device, a flash memory device, or other non-transitory solid-state storage devices. In some alternative embodiments, the memory 20 can optionally include a memory remotely set relative to the processor 10, and these remote memories can be connected to the computer device through a network. Examples of the above network include but are not limited to the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.
[0119] The memory 20 can include a volatile memory, such as a random access memory; the memory can also include a non-volatile memory, such as a flash memory, a hard disk, or a solid-state drive; the memory 20 can also include a combination of the above types of memories.
[0120] The computer device further includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30, and the output device 40 can be connected through a bus or other means. Figure 4 The example of connecting through bus is taken in the following.
[0121] The input device 30 can receive input digital or character information and generate key signal input related to user settings and function control of the computer device, such as a touch screen, etc. The output device 40 can include a display device, etc.
[0122] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.
[0123] A part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the existence of the computer program instruction in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc., and accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium accessible to the computer.
[0124] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations all fall within the scope of the present application.
Claims
1. A post-processing method for a work order system, characterized in that: The method comprises: Load the work order information from the database and use the work order context builder to generate the work order context required for the current operation; Run the preloading plug-in to preload basic information, configuration items, and public resources into the context; Execute synchronous plug-ins and asynchronous plug-ins, save the data that needs to be updated to the database, and reset the fields to be stored in the work order context; After the work order data is saved successfully, use the asynchronous storage post-plugin for post-asynchronous storage.
2. The method according to claim 1, characterized in that: After loading the work order information from the database, the method further includes: A work order context constructor is created using a factory design pattern, and the work order context constructor is used to generate a work order context object.
3. The method according to claim 1, characterized in that After using the work order context builder to generate the work order context object required for the current operation, the method further includes: Determine whether the work order plug-in matches; If the work order plug-in matches, execute the step of running the preloaded plug-in; If the work order plug-in does not match, the database is updated and the step of performing post-asynchronous storage using the asynchronous post-storage plug-in is executed.
4. The method according to claim 1, characterized in that The execution of the synchronous plug-in and the asynchronous plug-in to save the data to be updated to the database includes: Execute the synchronous sequential plug-in, execute the synchronous concurrent plug-in, and write to the database; Execute asynchronous sequential plug-in, execute asynchronous concurrent plug-in, and write to the database.
5. The method according to claim 4, characterized in that After executing the asynchronous sequential plug-in, executing the asynchronous concurrent plug-in, and writing to the database, the method further includes: Update the field information in the database, including overdue reminders and user notifications.
6. The method according to claim 1, characterized in that The method further comprises: When data that needs to be saved again is detected, the steps of saving the data that needs to be updated to the database and resetting the fields to be stored in the work order context are repeated.
7. A post-processing device for a work order system, characterized in that: The device comprises: The generation module is used to load the work order information from the database and use the work order context builder to generate the work order context required for the current operation; The preloading module is used to run the preloading plug-in to preload basic information, configuration items, and public resources into the context; The execution module is used to execute synchronous plug-ins and asynchronous plug-ins, save the data to be updated to the database, and reset the fields to be stored in the work order context; The storage module is used to perform post-asynchronous storage using the asynchronous storage post-plug-in after the work order data is successfully saved.
8. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the work order system post-processing method according to any one of claims 1 to 6 by executing the computer instructions.
9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the work order system post-processing method according to any one of claims 1 to 6.
10. A computer program product, characterized in that It comprises computer instructions, and the computer instructions are used to enable a computer to execute the work order system post-processing method according to any one of claims 1 to 6.