Data processing system, method and device, electronic equipment and readable storage medium

Abstract

The embodiment of the invention discloses a data processing system, method and device, electronic equipment and a readable storage medium. The system is connected with and receives push data reported by corresponding approval systems through at least one interface module in a data access system; the background service system creates approval information corresponding to each approval system, and generates notification information according to the approval information and the push data; and the access system receives the access request of the user and displays the notification information corresponding to the access request, so that the overall working efficiency of the multiple approval systems can be improved while data integration among different approval systems is realized.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and more specifically to a data processing system, method, apparatus, electronic device, and readable storage medium. Background Technology

[0002] In modern enterprises, with the continuous expansion of business and the increasing level of informatization, numerous approval systems have emerged. These systems generally cover many aspects of approval, such as financial approval, personnel changes, project progress, purchase orders, and contract management.

[0003] Existing approval systems typically include distributed systems and unified approval platforms that integrate multiple approval functions. In distributed systems, each approval function relies on an independent subsystem, requiring users to spend a significant amount of time reviewing pending approvals in each system and processing them individually, resulting in low overall efficiency. In a unified approval platform, when a user accesses the platform, the platform sends data requests to each approval subsystem in real time to obtain the user's approval information and then integrates and displays the information to the user. However, because data acquisition uses real-time capture and the various approval systems are closely interconnected, there are high requirements for the response speed of each approval system, data security, and the network environment for data capture. If a problem occurs in any link, the overall approval efficiency will be affected, therefore, approval efficiency still needs to be improved. Summary of the Invention

[0004] In view of this, the purpose of this invention is to provide a data processing system, method, apparatus, electronic device, and readable storage medium to improve the overall working efficiency of multiple approval systems while realizing data integration between different approval systems.

[0005] In a first aspect, embodiments of the present invention aim to provide a data processing system, the system comprising:

[0006] The data access system includes at least one interface module, each of which is connected to a corresponding approval system. The interface module is configured to receive push data reported by the approval system.

[0007] The backend service system is configured to create approval information corresponding to each of the approval systems and generate notification information based on the approval information and the push data.

[0008] The access system is configured to receive user access requests and display notification information corresponding to the access requests.

[0009] Secondly, embodiments of the present invention aim to provide a data processing method, the method comprising:

[0010] Create approval information corresponding to at least one approval system, and each approval system has a corresponding interface module;

[0011] The interface module receives the corresponding push data reported by the approval system.

[0012] A notification message is generated based on the approval information and the push data;

[0013] In response to receiving a user's access request, display the notification information corresponding to the access request.

[0014] Thirdly, embodiments of the present invention aim to provide a data processing apparatus, the apparatus comprising:

[0015] A creation unit is used to create approval information corresponding to at least one approval system, and each approval system has a corresponding interface module.

[0016] The processing unit is configured to receive push data reported by the approval system through the interface module; and generate notification information based on the approval information and the push data.

[0017] The notification unit is used to display notification information corresponding to the access request in response to receiving a user's access request.

[0018] Fourthly, embodiments of the present invention aim to provide a computer program product, the computer program product including a computer program / instruction, which, when executed by a processor, implements the method described in any of the preceding claims.

[0019] Fifthly, embodiments of the present invention aim to provide an electronic device, including a memory and a processor, wherein the memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method described above.

[0020] Sixthly, embodiments of the present invention aim to provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the method steps described above.

[0021] The technical solution of this invention connects to and receives push data reported by the corresponding approval system through at least one interface module in the data access system; the background service system creates approval information corresponding to each approval system and generates notification information based on the approval information and push data; the access system receives user access requests and displays the notification information corresponding to the access requests, which can improve the overall work efficiency of multiple approval systems while realizing data integration between different approval systems. Attached Figure Description

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

[0023] Figure 1 This is a schematic diagram of the data processing system according to an embodiment of the present invention;

[0024] Figure 2 This is a schematic diagram of the data processing system according to an embodiment of the present invention;

[0025] Figure 3 This is a flowchart of the data processing method according to an embodiment of the present invention;

[0026] Figure 4 This is a flowchart illustrating the creation of approval information according to an embodiment of the present invention;

[0027] Figure 5 This is a schematic diagram of the interface module according to an embodiment of the present invention;

[0028] Figure 6 This is an interactive diagram showing notification information according to an embodiment of the present invention;

[0029] Figure 7 This is a schematic diagram of the access page according to an embodiment of the present invention;

[0030] Figure 8 This is a schematic diagram of the process details page according to an embodiment of the present invention;

[0031] Figure 9 This is a schematic diagram of a data processing device according to an embodiment of the present invention;

[0032] Figure 10 This is a schematic diagram of an electronic device according to an embodiment of the present invention. Detailed Implementation

[0033] The present application is described below based on embodiments, but it is not limited to these embodiments. In the detailed description of the present application below, certain specific details are described in detail. Those skilled in the art can fully understand the present application without these details. To avoid obscuring the substance of the present application, well-known methods, processes, flows, elements, and circuits are not described in detail.

[0034] Furthermore, those skilled in the art should understand that the accompanying drawings provided herein are for illustrative purposes only and are not necessarily drawn to scale.

[0035] Unless the context explicitly requires it, words such as "including" or "contains" throughout the application should be interpreted as including rather than exclusive or exhaustive; that is, meaning "including but not limited to".

[0036] In the description of this application, it should be understood that the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Furthermore, in the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0037] In accordance with the present invention and the embodiments, if information acquisition is involved, data will be collected in a legal and compliant manner to ensure the legality of the data source, and appropriate technical and management measures will be taken to ensure data security.

[0038] The solutions described in this specification and embodiments, if involving the processing of personal information, will be processed only under the premise of having a legal basis (such as obtaining the consent of the personal information subject, or being necessary for the performance of a contract), and will only be processed within the scope stipulated or agreed upon. A user's refusal to process personal information beyond what is necessary for basic functions will not affect the user's use of basic functions.

[0039] Existing approval systems include distributed systems and unified approval platforms that integrate multiple approval functions. However, in distributed systems, each approval function relies on an independent subsystem, and each subsystem has its own independent entry point and user interface. For users, especially those who frequently need to conduct cross-departmental approvals, a significant amount of time is usually spent switching between different systems, viewing pending approvals one by one, and then processing them one by one. This not only results in low approval efficiency and a high error rate, but also greatly affects user experience and satisfaction, which is detrimental to improving enterprise competitiveness.

[0040] Meanwhile, existing unified approval platforms can bring together the entry points of all types of approval subsystems through a single platform and display approval information to users through data integration, reducing the switching and repetitive operations between different approval subsystems and providing enterprises with the convenience of one-stop approval. However, a series of problems exist in practical applications. For example, since the data related to each subsystem in the approval platform is captured in real time when the user accesses it, a slow response or failure in a certain approval system will affect the performance of the entire platform and the user experience. Simultaneously, this unified approval method has high requirements for network stability; large network fluctuations or transmission limitations can lead to data capture failures or delays. Furthermore, because real-time data capture requires frequent access to various systems, excessive capture frequency or large data volumes can put pressure on the overall system, causing slow response or crashes, thus affecting normal user operation or imposing additional maintenance costs on enterprises. Moreover, the data capture process requires transmission and exchange between different systems, which increases the risk of data leakage and attacks, requiring enterprises to improve their security measures. Finally, due to differences in approval processes and data formats across different systems, even if data is integrated through real-time capture, inconsistencies and process mismatches may still exist. In other words, while existing unified approval platforms can achieve data integration between different approval systems to a certain extent, the data integration performance and overall approval efficiency still need improvement.

[0041] In view of this, the present invention aims to provide a data processing system that can improve the overall work efficiency of multiple approval systems while realizing data integration between different approval systems.

[0042] Figure 1 This is a schematic diagram of the data processing system according to an embodiment of the present invention. Figure 1As shown, the data processing system 100 in this embodiment is a unified approval platform, including a data access system 1, a backend service system 2, and an access system 3. The data access system 1 serves as a bridge connecting the unified approval platform with different approval systems, providing a series of data interface services. It is configured to connect with each approval system and receive push data reported by each approval system, enabling each approval system to successfully push data to the unified approval platform. The backend service system 2 manages and configures various parameters and templates related to data integration. It is configured to create approval information corresponding to each approval system and generate notification information based on the approval information and the push data reported by the corresponding approval system. The access system 3 is an interactive system for users to access the unified approval platform. Users establish a communication connection with the unified approval platform 100 through user terminal 200 and send access requests. The access system 3 is configured to receive user access requests and display the corresponding notification information, allowing users to clearly view relevant approval processes, task lists, and processing progress information.

[0043] Furthermore, Figure 2 A schematic diagram of the data processing system of this embodiment is shown, such as... Figure 2 As shown, the data access system 1 in the data processing system 100 (i.e., the unified approval platform) of this embodiment includes at least one interface module 11. Each interface module 11 is connected to a corresponding approval system, and each interface module 11 is configured to receive push data reported by the corresponding approval system. Optionally, the interface module can adopt an API interface. Thus, by providing interface modules corresponding to each approval system, this embodiment makes the design of each interface module more flexible and universal, thereby adapting to the data structure and business logic of different approval systems. For each independent approval system, including existing old systems and newly launched advanced systems, this embodiment can push the push data inside the approval system to the unified approval platform in real time by calling the interface module. Furthermore, since the data push process is transparent to the approval system, the approval system does not need to do any additional adaptation work when reporting push data, which can greatly reduce the complexity and cost of subsequent data integration, thereby improving the overall efficiency of multiple approval systems.

[0044] The backend service system 2 includes a business management module 21, a process management module 22, and a notification management module 23. The business management module 21 is configured to create the corresponding business entity for the approval system based on the business entity information. The process management module 22 is configured to create the corresponding approval process based on the process information corresponding to the business entity. The notification management module 23 is configured to create the corresponding notification mechanism based on the mechanism information corresponding to the approval process. Furthermore, after creating the business entity, approval process, and notification mechanism for the approval system, the backend service system 2 will also integrate the data based on the push data reported by the approval system and the approval information composed of the business entity, approval process, and notification mechanism. This will determine the notification information corresponding to the approval-related data generated by the user in the approval system. While achieving data integration, this allows users to view the integrated approval-related data based on the notification information, thereby improving the overall work efficiency of different approval systems and enhancing the user experience.

[0045] The access system 3 includes a process library 31, an initiated module 32, a pending module 33, and a completed module 34. The process library 31 serves as a unified entry point for users to initiate processes, specifically configured to display all initiable processes and show the user the initiation page for the corresponding process based on user actions. The initiated module 32 is configured to display initiated processes and show the user the process details page for the corresponding initiated process based on user actions. The pending module 33 is configured to display processes awaiting processing (i.e., approval processes awaiting approval) and show the user the process details page for the corresponding pending process based on user actions. The completed module 34 is configured to display processed processes (i.e., approved approval processes) and show the user the process details page for the corresponding processed process based on user actions. Thus, users can view their initiable processes, task lists, and processing progress through these modules in the system, achieving a convenient and efficient approval experience.

[0046] Therefore, the data processing system in this embodiment enables each approval system to smoothly push data to the unified approval platform through the interface services provided by at least one interface module in the data access system. The backend service system pre-creates approval information corresponding to each approval system, establishing corresponding approval templates for the approval functions of each system. After the unified approval platform receives the push data sent by each approval system through its corresponding interface module, the backend service system integrates the approval information and push data to generate corresponding notification information. This achieves the integration of relevant data between different approval systems, improving the overall approval efficiency of multiple approval systems. Furthermore, by displaying the corresponding notification information to the user when accessing the system, the system not only achieves data integration between different approval systems but also allows users to easily understand all relevant approval content, further improving overall work efficiency and achieving a convenient and efficient approval experience.

[0047] Meanwhile, in order to enable different approval systems to access the unified approval platform simultaneously and improve the approval efficiency of different approval systems, this embodiment will explain the data processing methods in the data processing system (i.e., the unified approval platform).

[0048] Figure 3 This is a flowchart of a data processing method according to an embodiment of the present invention. Figure 3 As shown, the data processing method in this embodiment specifically includes the following steps.

[0049] In step S310, approval information corresponding to at least one approval system is created, and each approval system has a corresponding interface module.

[0050] In this embodiment, after determining which approval systems need to be connected to the unified approval platform, the background service system will create approval information corresponding to each approval system on the unified approval platform to complete the basic data configuration of each approval system on the unified approval platform through the approval information.

[0051] Optionally, the approval information in this embodiment includes the business entity, approval process, and notification mechanism. The business entity corresponds to the approval system and is used to distinguish different approval systems within the unified approval platform. The approval process characterizes the approval handling flow of the corresponding approval system. The notification mechanism provides a method for notifying users of the notification information corresponding to the approval process.

[0052] Figure 4 This is a flowchart illustrating the creation of approval information according to an embodiment of the present invention. Figure 4 As shown, in this embodiment, the approval information for each approval system is created through the following steps.

[0053] In step S410, a business entity corresponding to the approval system is created based on the business entity information.

[0054] In this embodiment, the business management module in the backend service system creates a corresponding business entity for the approval system based on the business entity information. This business entity information includes the business entity name, the approval system name, the system identifier (such as the system logo), and the business entity administrator information. Therefore, this embodiment manages the approval systems to be connected to the unified approval platform through the business management module and creates a corresponding business entity for each connected approval system, ensuring accurate correspondence and isolation of data between the unified approval platform and the approval systems.

[0055] In step S420, a corresponding approval process is created based on the process information of the business party.

[0056] In this embodiment, the process management module in the backend service system creates corresponding approval processes based on the process information of the business party. The process information includes the business party name, approval process name, approval process model identifier, approval process administrator information, process access scope settings (e.g., all employees, designated personnel, designated parts), and process initiation address information (e.g., initiation URL). Therefore, this embodiment, by creating and managing approval processes in various approval systems to be integrated into the unified approval platform through the process management module, provides users with a unified and streamlined approval experience.

[0057] In step S430, a corresponding notification mechanism is created based on the mechanism information corresponding to the approval process.

[0058] In this embodiment, the notification management module in the backend service system creates a corresponding notification mechanism based on the mechanism information corresponding to the approval process. The mechanism information includes the notification channel and the notification template. The notification channel can be a channel for sending information, such as email or instant messaging software. The notification template can be a default template pre-generated by the platform, or a custom template generated by the user based on provided options and their own input.

[0059] Optionally, the notification channels and templates in this embodiment are determined based on the notification type of the approval process (including pending, transferred, termination notification initiator, termination notification approver, rejection to initiator, revocation, etc.). Therefore, this embodiment creates a notification mechanism through the notification management module to generate notification information based on this mechanism, enabling users to receive relevant notifications in a timely and accurate manner.

[0060] In step S320, the corresponding push data reported by the approval system is received through the interface module.

[0061] In this embodiment, after the backend service system creates the approval information corresponding to each approval system, the approval system can call the corresponding interface module to report and push data to the unified approval platform. Simultaneously, the unified approval platform receives the pushed data reported by the corresponding approval system through the interface module. Therefore, this embodiment can centralize data scattered across various approval systems onto a unified platform. By adapting the data structures and business logic of different approval systems through the interface module, data integration and sharing can be achieved without large-scale modifications or replacements of the approval systems, thereby improving the compatibility of the unified approval platform with different approval systems. Furthermore, through data aggregation and sharing, users can obtain the information they need more quickly, reducing the time spent switching and querying between multiple approval systems, lowering operational difficulty and learning costs, improving user operational efficiency, and enhancing the collaboration and coordination efficiency of approval processes across multiple approval systems, thereby improving the overall work efficiency of multi-approval tasks.

[0062] Since the approval process is typically initiated by the initiator and processed by approvers at different nodes according to a predetermined approval order, a closed-loop process is established whereby the processing result is returned to the initiator after all approvers have completed their processing. Furthermore, corresponding process data and approval data are generated at each processing node of the approval process. Therefore, in this embodiment, the data pushed to the unified approval platform by each approval system includes process data and approval data. However, it should be understood that the type of data pushed in this embodiment can be set according to the actual usage scenario, and may include other types of data in addition to the aforementioned process data and approval data.

[0063] Taking the push data, which includes process data and approval data, as an example, the process data in this embodiment is used to characterize the process structure and attribute information in the approval process corresponding to the approval system, including process definition, node settings, role allocation, approval conditions, notification rules, and other information. The process definition describes the basic information of the entire approval process, including the process name, process identifier, process description, or title. Nodes are set as the node information of each approval node in the process, including node name, node type (single or multiple nodes, approval order, etc., and each node corresponds to one or more approvers), etc. The node information of each approval node can also be represented by an approval process model, and different approval process models have corresponding approval process model identifiers. Role allocation refers to the responsibilities, permissions, and processing time (such as process initiation time, process viewing address, process end time, and viewing address) of each role in the approval process (e.g., initiator, approver, copy recipient, etc.). Approval conditions are the conditions that trigger the process or node transfer in the approval process, such as department attributes, reimbursement amount, etc. Notification rules are the notification mechanism during the approval process, such as the system automatically sending notifications to relevant personnel when approval is passed or rejected.

[0064] Approval data is used to characterize various data generated during the approval process related to specific approval tasks, including approval task information, initiator information, approver information, approval opinions, approval results, and attachment information. Specifically, approval task information includes a unique identifier for the approval task (such as the process identifier or task identifier (task ID)), task name, task status (such as pending approval, approved, rejected), creation time, the approval address corresponding to the creation time, processing time, and the processing address corresponding to the processing time. Initiator information records the basic information of the person initiating the approval task, such as name, department, and position. Approver information records the basic information of the personnel participating in the approval task, including the approver's name, department, and position. Approval opinions are the opinions or suggestions given by the approver during the approval process, which can be text, numbers, or other forms of input. Approval results represent the final outcome of the approval task, such as approved, rejected, or returned. Attachment information includes relevant documents or materials uploaded during the approval process, such as contracts and reports.

[0065] It should be noted that, in addition to the above examples, the process data and approval data in this embodiment can also use other types of data according to the actual use scenario, or a combination of some or all of the data in the above examples with other types of data.

[0066] Optionally, since different approval systems and different approval processes within the same approval system each have a unique identifier, to facilitate the differentiation of approval systems corresponding to different approval processes, the identifiers of approval processes under different approval systems in this embodiment can not only reflect the corresponding approval system but also the process number within that approval system. For example, the identifier for a certain approval process might be xitong1-001, where xitong1 represents that the approval system to which the approval process belongs is system A, and 001 represents the process number within approval system A.

[0067] It should be understood that the data encoding of various types of data in the process data and approval data in this embodiment can be implemented by selecting an appropriate data encoding method according to the actual use scenario, so as to meet the expression of process data and approval data in the corresponding scenario, facilitate the subsequent identification and use of process data and approval data of each approval process, and help to further improve the overall work efficiency.

[0068] Optionally, to facilitate the transmission of different types of data in the approval system, different interfaces are used for data transmission for different types of pushed data in this embodiment, so as to prevent mutual interference between different types of data generated in the approval system during transmission, which is conducive to improving data transmission efficiency and ensuring data transmission accuracy.

[0069] Furthermore, such as Figure 5 As shown in the diagram, taking an interface module corresponding to an approval system as an example, the interface module 11 in this embodiment includes a process interface 111 and an approval interface 112. The process interface 111 is configured to receive process data reported by the approval system, and the approval interface 112 is configured to receive approval data reported by the approval system. Therefore, each approval system can push its own process data and task data to the unified approval platform in real time through the process interface and approval interface in the corresponding interface module. This enables the unified approval platform to integrate data pushed from different approval systems while reducing the mutual influence between process data and task data, ensuring the accuracy of data transmission.

[0070] Optionally, to facilitate subsequent data processing, the interface module in this embodiment, after receiving the push data (including process data and approval data) reported by the approval system, will also store the push data in a local database to achieve data backup and ensure data reliability and stability. Therefore, when a user needs to access the unified approval platform, this embodiment can view the integrated approval data and process data from the local database. Furthermore, by combining an efficient data retrieval and display mechanism, this embodiment allows users to obtain the required data in a short time, which is beneficial to further improving the overall approval efficiency and user experience.

[0071] Furthermore, in this embodiment, the process data and approval data can be stored separately in a database. Specifically, after receiving the process data reported by the approval system, the process interface in this embodiment stores the process data in a local process information table. Simultaneously, after receiving the approval data reported by the approval system, the approval interface in this embodiment stores the approval data in a local task information table. Therefore, by storing the process data and approval data reported by the approval system in the local process information table and local task information table respectively, the data storage classification becomes clearer, facilitating subsequent querying and use.

[0072] Optionally, when the approval system reports process data and approval data, in one optional implementation, the approval system in this embodiment can periodically report and push data to the unified approval platform after the approval process is initiated, until the approval process ends. In another optional implementation, the timing of the approval system reporting and pushing data in this embodiment can be determined based on changes in the processing nodes of the approval process or the task processing stage.

[0073] Furthermore, when determining the reporting timing based on changes in the processing nodes of the approval process, this embodiment can report push data once each time the approval process reaches a new node. When determining the reporting timing based on the task processing stage of the approval process, this embodiment will report the corresponding push data when the approval process begins (i.e., the initiator initiates a new approval process), when the approval task begins processing (i.e., the first approver begins to approve the approval process), when the approval task processing ends (i.e., the last approver completes the approval process), and when the approval process ends (the initiator receives the approval process receipt).

[0074] Specifically, in this embodiment, the timing of data reporting is determined based on the processing progress of the approval process. This ensures the timeliness of data reporting while reducing the number of data reports and saving system computing resources.

[0075] Furthermore, in this embodiment, upon receiving an approval process creation request from the initiator, the process interface is configured to respond to the received approval process creation request by receiving the process data reported by the approval system and storing the process data in a local process information table. The process data at this time corresponds to the process creation request and includes a process identifier, process title, approval process model identifier, process initiator, process initiation time, and process viewing address.

[0076] Upon receiving an approval task creation request, the approval interface is configured to respond to the completion of the approval process by receiving the process data reported by the approval system and storing the approval data in a local task information table. This approval data includes the process identifier, task identifier, task name, task handler (i.e., approver), task creation time, and approval address.

[0077] After the approval task is completed, the approval interface is also configured to receive the approval data reported by the approval system in response to the completion of the approval task, and update the corresponding approval task in the local task information table. The approval data at this time includes the task identifier, the task handler, the task processing time, and the approval address. Therefore, by updating the approval data of the approval task in the local task information table when the approval task is completed, the local process information table can store complete task data for the approval process.

[0078] After the approval process is completed, the process interface is also configured to respond to the end of the approval process by receiving the process data reported by the approval system and updating the corresponding approval process in the local process information table. This process data includes the process identifier, process end time, and viewing address. Therefore, by updating the approval process data in the local process information table at the end of the process, the local process information table can store complete approval process data.

[0079] Optionally, after receiving the push data, the unified approval platform in this embodiment processes the received push data based on data encryption and access control mechanisms to ensure data security during transmission and storage. By saving the push data to local process information tables and local task information tables, and subsequently using the data in these tables, the reliability and stability of the data can be guaranteed based on data backup and recovery mechanisms.

[0080] In step S330, a notification message is generated based on the approval information and the push data.

[0081] In this embodiment, after receiving all process data and all approval data corresponding to the approval process in the approval system, the unified approval platform integrates the data based on the approval information, the process data, and the approval data, and generates notification information corresponding to the approval process. This allows users to view the integrated approval data and process data of the corresponding approval process when they need to access the unified approval platform.

[0082] Furthermore, when the unified approval platform generates notification information based on the approval information corresponding to the approval system and the push data reported by the interface module, since the approval information provides the process framework and notification framework of the approval process, by integrating the push data with the approval information, the push data is filled into the corresponding framework position, and the notification information corresponding to the approval process can be generated.

[0083] Optionally, to ensure data consistency between the unified approval platform and the approval system, such as Figure 5 As shown, the interface module in this embodiment also includes a verification module 113 to verify data consistency. Specifically, the verification module 113 in this embodiment is configured to compare the process data reported by the approval system with the local process information table to verify the consistency of the process data; and to compare the approval data reported by the approval system with the local task information table to verify the consistency of the approval data.

[0084] Furthermore, in this embodiment, when the data comparison is consistent—that is, when the process data reported by the approval system matches the process data in the local process information table, and the approval data reported by the approval system matches the approval data in the local task information table—the data comparison ends, and a notification message is generated based on the process data in the local process information table, the approval data in the local task information table, and the aforementioned approval information. However, when the data comparison is inconsistent—that is, when the process data reported by the approval system is inconsistent with the process data in the local process information table, and / or the approval data reported by the approval system matches the approval data in the local task information table—it is necessary to continue calling the process interface and / or the approval interface to perform data compensation, supplementing the data in the local process information table and / or the local task information table until the data comparison is consistent.

[0085] It should be understood that in this embodiment, when setting the verification module in the above manner, the unified approval platform includes multiple verification modules. There is a corresponding relationship between the verification modules and the approval systems, and the push data uploaded by each approval system is verified through the corresponding verification module. In another optional implementation, since the push data uploaded by each approval system has a corresponding process identifier, the number of verification modules in the unified approval platform in this embodiment can also be set to one. When using a single verification module, the push data uploaded by different approval systems is verified through this verification module.

[0086] In step S340, in response to receiving a user's access request, notification information corresponding to the access request is displayed.

[0087] In this embodiment, after generating the notification information corresponding to the approval process, the system receives the user's access request and queries the local database for the notification information of the approval process corresponding to the access request based on the access request. Then, the system displays the corresponding notification information to the user so that the user can clearly view the approval process, task list, and processing progress information related to them.

[0088] Figure 6 This is an interactive diagram displaying notification information according to an embodiment of the present invention. For example... Figure 6 As shown, the notification information is displayed through the following steps in this embodiment.

[0089] In step S610, an access request is sent to the user.

[0090] In this embodiment, the user terminal 200 sends an access request to the access system 3 in the unified approval platform based on the user's operations on the access page. The access request includes processing requests related to the approval process, such as process creation requests and task creation requests. Furthermore, the access request carries key characters related to the approval process, such as the process identifier, creation time, and creation address, to quickly determine the corresponding approval process based on the access request.

[0091] In step S620, obtain the notification information corresponding to the access request.

[0092] In this embodiment, after receiving an access request from a user terminal, the access system 3 retrieves the corresponding notification information from the local database of the unified approval platform. Optionally, this embodiment can employ high-performance data processing and querying technologies to retrieve the corresponding notification information from the local database of the unified approval platform, thereby improving the efficiency of determining approval process notification information and enhancing user experience and satisfaction.

[0093] In step S630, a notification message is sent.

[0094] In this embodiment, after the access system 3 obtains the notification information corresponding to the access request, it sends the notification information to the user terminal 200.

[0095] In step S640, a notification message is displayed.

[0096] In this embodiment, the user terminal 200 receives notification information sent by the access system 3 and displays the corresponding notification information based on a preset display method.

[0097] Furthermore, the access system in this embodiment provides access functions including access to processes that can be initiated, processes that have already been initiated, processes that are pending approval, and processes that have already been approved. Correspondingly, users can access processes through methods such as... Figure 7 The access page shows the function options to view the corresponding approval process. Specifically, as shown... Figure 7 As shown, the access page P offers access options for "Process Library P1," "Initiated P2," "Pending Approval P3," and "Approved P4." Each option can be selected and trigger a corresponding access request by the user's clicks, swipes, or other actions. Specifically, "Process Library P1" displays the approval processes corresponding to different approval systems that can be initiated after the user selects the option. "Initiated P2" displays initiated approval processes after the user selects the option. "Pending Approval P3" displays pending approval processes after the user selects the option. "Approved P4" displays processed approval processes after the user selects the option.

[0098] Meanwhile, when displaying different types of approval processes, the logic for displaying processes that can be initiated can be based on the approval processes configured in the process management module, such as those with an open scope of all employees, those with specified personnel including the current user, or those with specified departments including the current user's department. The logic for displaying initiated processes is the approval process retrieved from the unified approval platform's local process information table, where the process initiator is the current user. The logic for displaying pending processes is the task retrieved from the unified approval platform's local task information table, where the task handler is the current user and the task processing time is empty (i.e., no task processing time exists). The logic for displaying processed processes is the task retrieved from the unified approval platform's local task information table, where the task handler is the current user and the task processing time is not empty.

[0099] Optionally, this embodiment can provide users with access to all access functions in the system, including a process library, initiated modules, pending modules, and completed modules. Specifically, access modules corresponding to approval processes handled by the user will display the corresponding process content. Access modules not involved in the user's processing, including those where the user has processing authority but the approved processes are empty (e.g., the user can approve but there are no pending or approved approval processes) and those where the user does not have processing authority (i.e., the user does not need to approve), will display empty content. Therefore, this embodiment, through the above-described display settings of access modules, allows users to easily view all approval processes of all processing types related to themselves.

[0100] Furthermore, for different types of access modules that do not involve user processing, this embodiment can use the same or different display methods. For example, for access modules where the user has processing permissions but the approval process content is empty, and for access modules where the user does not have processing permissions, both can display a message like "No content available" to indicate to the user that there is no approval process under the corresponding access module. Alternatively, for access modules where the user has processing permissions but the approval process content is empty, displaying "No content available" will remind the user that there is no approval process under the corresponding access module; while for access modules where the user does not have processing permissions, displaying "No processing permission available" will remind the user that they do not have the processing permission for the corresponding access module.

[0101] Alternatively, considering that different users may have different processing permissions for approval processes—for example, some users can only initiate processes without approval, while others can both—this embodiment can also determine corresponding access permissions based on the user's processing permissions, thereby providing the user with corresponding access functions and reducing the display of access modules without data content. For example, for users who do not have approval permissions but can only initiate processes, only the process library and initiated modules can be displayed, while the empty pending and completed modules are not displayed. For users who only need to approve processes, only the pending and completed modules can be displayed. For users who are involved in both process initiation and approval operations, the process library, initiated modules, pending modules, and completed modules are displayed simultaneously.

[0102] Furthermore, when a user needs to view specific options within the approval process, the access page will display the corresponding approval process processing details based on the user's actions. For example, when a user needs to view the process details of process A1 in an initiated process, the user can click the selection control corresponding to process A1 to jump to the relevant page. Figure 8 The process details page shown is shown below. Users can view the process details page P' to understand the approval details and records of process A1, and thus understand the entire processing procedure of this approval process, which can improve the user experience.

[0103] The technical solution of this embodiment, through the cooperation of the data access system, backend service system, and access system in the unified approval platform, enables each approval system to report the push data of its respective approval process to the unified approval platform. This eliminates data silos between different approval systems, allowing diverse approval data to be processed and displayed on a unified platform, thus improving the overall work efficiency of multiple approval systems. Simultaneously, the backend service management system integrates the approval information and push data of each approval process in each approval system, ensuring smooth cross-system approval processes and avoiding data confusion or loss due to process differences. Furthermore, by saving push data to a local database in real time and updating local data, the system ensures data timeliness based on a real-time data synchronization and update mechanism, thereby ensuring that users can obtain the latest and most accurate approval information. Finally, the access system obtains the notification information corresponding to the user's access request and displays the notification information to the user. Combined with high-performance data processing and query technology, this provides users with a user-friendly interface and operating experience, thereby improving the user's approval experience and satisfaction.

[0104] Figure 9 This is a schematic diagram of a data processing apparatus according to an embodiment of the present invention. Figure 9 As shown, the data processing device in this embodiment includes a creation unit 91, a processing unit 92, and a notification unit 93. The creation unit 91 is used to create approval information corresponding to at least one approval system, each approval system having a corresponding interface module. The processing unit 92 is used to receive push data reported by the corresponding approval system through the interface module; and generate notification information based on the approval information and the push data. The notification unit 93 is used to respond to a user's access request by displaying the notification information corresponding to the access request. Therefore, this embodiment can improve overall work efficiency while achieving data integration between different approval systems.

[0105] Figure 10 This is a schematic diagram of an electronic device according to an embodiment of the present invention. (For example...) Figure 10 As shown, Figure 10The illustrated electronic device is a general address lookup device, comprising a general computer hardware architecture, including at least a processor 101 and a memory 102. The processor 101 and memory 102 are connected via a bus 103. The memory 102 is adapted to store instructions or programs executable by the processor 101. The processor 101 can be a standalone microprocessor or a collection of one or more microprocessors. Thus, the processor 101 executes the instructions stored in the memory 102, thereby performing the method flow of the embodiments of the present invention as described above to process data and control other devices. The bus 103 connects the aforementioned components together, and also connects these components to a display controller 104, a display device, and an input / output (I / O) device 105. The input / output (I / O) device 105 can be a mouse, keyboard, modem, network interface, touch input device, motion-sensing input device, printer, and other devices known in the art. Typically, the input / output device 105 is connected to the system via an input / output (I / O) controller 106.

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

[0107] This application is described with reference to flowchart illustrations of methods, apparatus (devices), and computer program products according to embodiments of this application. It should be understood that each step in the flowchart can be implemented by computer program instructions.

[0108] These computer program instructions may be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including an instruction means, the implementation process of which is described in the instruction means. Figure 1 The function specified in one or more processes.

[0109] These computer program instructions may also be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing device, produce instructions for implementing processes. Figure 1 A device for a function specified in one or more processes.

[0110] Another embodiment of the present invention relates to a non-volatile storage medium for storing a computer-readable program for use by a computer to execute some or all of the above-described method embodiments.

[0111] That is, those skilled in the art will understand that all or part of the steps in the methods of the above embodiments can be implemented by a program specifying the relevant hardware. This program is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0112] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A data processing system, characterized by The system comprises: a data access system comprising at least one interface module, each of the interface modules being connected with a corresponding approval system, the interface module being configured to receive push data reported by the approval system; a background service system configured to create approval information corresponding to each of the approval systems, and to generate notification information according to the approval information and the push data; an access system configured to receive an access request of a user, and to display notification information corresponding to the access request.

2. The system of claim 1, wherein, The approval information comprises a business party, an approval process, and a notification mechanism, and the background service system comprises: a business management module configured to create a business party corresponding to the approval system according to business party information; a process management module configured to create a corresponding approval process according to process information corresponding to the business party; a notification management module configured to create a corresponding notification mechanism according to mechanism information corresponding to the approval process.

3. The system of claim 2, wherein, The business party information comprises a business party name, a system name of the approval system, a system identifier, and business party administrator information.

4. The system of claim 2, wherein, The process information comprises a business party name, an approval process name, an approval process model identifier, approval process administrator information, setting information of a process opening range, and process initiation address information.

5. The system of claim 2, wherein, The mechanism information comprises a notification channel and a notification template, and the notification channel and the notification template are determined according to a notification type of the approval process.

6. The system of claim 1, wherein, The push data comprises process data and approval data, and the interface module comprises: a process interface configured to receive process data reported by the approval system, and to store the process data in a local process information table; an approval interface configured to receive approval data reported by the approval system, and to store the approval data in a local task information table.

7. The system of claim 6, wherein, The process interface is specifically configured to, in response to receiving an approval process creation request, receive process data reported by the approval system, and to store the process data in a local process information table; wherein the process data corresponds to the process creation request, and the process data comprises a process identifier, a process title, an approval process model identifier, a process initiator, a process initiation time, and a process viewing address.

8. The system of claim 6, wherein, The process interface is specifically configured to, in response to an end of approval process processing, receive process data reported by the approval system, and to update a corresponding approval process in the local process information table; wherein the process data comprises a process identifier, a process end time, and a viewing address.

9. The system of claim 6, wherein, The approval interface is specifically configured to, in response to receiving an approval task creation request, receive approval data reported by the approval system, and to store the approval data in a local task information table; wherein the approval data comprises a process identifier corresponding to an approval task, a task identifier, a task name, a task handler, a task creation time, and an approval address.

10. The system of claim 6, wherein, The approval interface is specifically configured to, in response to an end of approval task processing, receive approval data reported by the approval system, and to update a corresponding approval task in the local task information table; wherein the approval data comprises a task identifier, a task handler, a task handling time, and an approval address.

11. The system of claim 6, wherein, The interface module further comprises: a verification module configured to compare the process data reported by the approval system with the local process information table to verify the consistency of the process data, and compare the approval data reported by the approval system with the local task information table to verify the consistency of the approval data.

12. The system of claim 1, wherein, The access system comprises: a process library configured to show the user the launchable processes, and display the launch page of the corresponding launchable process to the user based on the user operation; an initiated module configured to show the user the initiated processes, and show the process detail page of the corresponding initiated process to the user based on the user operation.

13. The system of claim 12, wherein, The access system further comprises: a to-be-handled module configured to show the user the to-be-handled processes, and show the process detail page of the corresponding to-be-handled process to the user based on the user operation; a handled module configured to show the user the handled processes, and show the process detail page of the corresponding handled process to the user based on the user operation.

14. A data processing method, characterized by, The method comprises: creating approval information corresponding to at least one approval system, each of the approval systems having a corresponding interface module; receiving push data reported by the corresponding approval system through the interface module; generating notification information according to the approval information and the push data; in response to receiving an access request of a user, showing the notification information corresponding to the access request.

15. A data processing apparatus, characterized by The device comprises: a creating unit configured to create approval information corresponding to at least one approval system, each of the approval systems having a corresponding interface module; a processing unit configured to receive push data reported by the corresponding approval system through the interface module, and generate notification information according to the approval information and the push data; a notification unit configured to, in response to receiving an access request of a user, show the notification information corresponding to the access request.

16. A computer program product, characterised in that, The computer program product comprises computer programs / instructions, which are executed by a processor to implement the method in claim 14.

17. An electronic device comprising a memory and a processor, characterized in that The memory is configured to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method in claim 14.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which is executed by a processor to implement the method in claim 14.

Images