Cross-system approval task integration management system

Abstract

A cross-system approval task integration and management system is disclosed. The approval task management platform is connected to a first approval system, a second approval system, and an approval terminal device. The approval task filtering module is connected to an approval task information standardization module, a page generation module, an approval priority ranking module, a prediction and warning module, and an approval task discrimination module. The approval priority ranking module is connected to the page generation module. The approval task management platform integrates the pending approval task information from the first and second approval systems, so that all pending approval tasks can be presented with a unified data structure. Based on the approval identification information provided by the approval terminal device, the pending approval tasks related to the approver are dynamically filtered from the standardized data table to generate corresponding approval task management pages. This allows users to view all pending approval items across systems in a unified interface, thereby improving the efficiency of cross-system approval operations, reducing the risk of omissions, and enhancing the intelligence of the approval process.

Description

Cross-system approval task integration management system Technical Field

[0001] This invention relates to an information processing and management system, specifically a cross-system approval task integration management system that integrates the information of pending approval tasks from multiple approval systems for standardization, filtering, sorting, risk prediction, and page generation, enabling a single approval terminal device to quickly and uniformly process all pending approval tasks. Prior Technology

[0002] In existing technologies, enterprises or financial institutions typically build multiple independently operating approval systems to address different business processes. These include administrative approval systems, procurement review systems, financial transaction review systems, credit review systems, and information change or authorization application systems, etc. Because each system is built by different units, their internal data structures, field names, task formats, and presentation methods are inconsistent. As a result, each system can only present its own pending approval task information in its own independent interface, lacking cross-system integration capabilities.

[0003] In practice, approvers responsible for multiple types of review work often need to log into different approval systems to view pending tasks in each system. This not only creates an operational burden but also makes it easy to overlook some pending tasks due to frequent system switching or scattered information. In addition, because the task field formats of each system are inconsistent, such as the naming and format of task number, applicant information, approver information, or application time fields, the existing technology cannot directly compare or integrate data across systems.

[0004] Therefore, the goal of this work is to integrate the pending task information from different approval systems and provide standardized processing, sorting judgment and omission prediction capabilities to effectively improve the efficiency of the approval process and reduce the risk of omissions.

[0005] In summary, it is evident that previous technologies have long suffered from problems such as the inability to integrate cross-system data, the lack of a unified data format, the inability to perform cross-system sorting and risk assessment, and the lack of omission prediction and intelligent reminder functions. Therefore, it is necessary to propose improved technical means to solve this problem. Summary of the Invention

[0006] In view of the problems of previous technologies, such as the inability to integrate cross-system data, the lack of a unified data format, the inability to perform cross-system sorting and risk assessment, and the lack of omission prediction and intelligent reminder functions, this invention discloses a cross-system approval task integration and management system, wherein:

[0007] First, this invention discloses a cross-system approval task integration management system, which includes: a first approval system, a second approval system, an approval terminal device, and an approval task management platform. The approval task management platform further includes: an approval task information standardization module, an approval task filtering module, and a page generation module.

[0008] The first approval system provides the first approval system identification information and multiple first-pending approval task information to the approval task management platform; the second approval system provides the second approval system identification information and multiple second-pending approval task information to the approval task management platform.

[0009] The signing terminal device logs into the signing task management platform using the signing identification information. The signing task management page provided by the signing task management platform displays multiple first pending signing task information and / or second pending signing task information corresponding to the signing identification information. When one of the first pending signing task information or the second pending signing task information is selected, the signing task management platform guides the user to the corresponding first signing system or second signing system to perform the signing procedure.

[0010] The approval task management platform is connected to the first approval system, the second approval system, and the approval terminal device. The approval task management platform operates through an application programming interface (API). The API obtains the identification information of the first approval system and multiple first pending approval task information and the identification information of the second approval system and multiple second pending approval task information from the first approval system and the second approval system, respectively. The approval task information standardization module of the approval task management platform performs standardization processing based on a standardized data table with multiple standardized fields, filling the approval task items in the first and second pending approval task information into the corresponding standardized fields of the standardized data table. The approval task filtering module of the approval task management platform is connected to the approval task information standardization module, and filters out the first pending approval task information and / or the second pending approval task information corresponding to the approval identification information from the standardized data table. The page generation module of the approval task management platform is connected to the approval task filtering module, and generates an approval task management page based on the filtered first and / or second pending approval task information and provides it to the approval terminal device.

[0011] The system disclosed in this work, as described above, integrates pending approval task information from the first and second approval systems through an approval task management platform. It uses a standardized data table with multiple standardized fields as its core to parse and match approval task items from different sources and in different formats, so that all pending approval tasks can be presented in a unified data structure. Based on the approval identification information provided by the approval terminal device, it dynamically filters the pending approval tasks related to the approver from the standardized data table to generate a corresponding approval task management page, so that users can view all pending approval items across systems in a single interface.

[0012] Through the aforementioned technical means, this invention can achieve the technical effects of improving the efficiency of cross-system approval processes, reducing the risk of omissions, and enhancing the intelligence of the approval process. Simple Explanation of the Diagram

[0013] Figure 1 shows a system block diagram of the cross-system approval task integration management system for this creation. Figure 2A illustrates the intended representation of standardized data for the integrated management of cross-system approval tasks in this project. Figure 2B illustrates the signature task management page for the cross-system signature task integration management of this creation. Figure 2C illustrates the reordering of pending approval tasks in the cross-system approval task integration management of this creation. Figure 3 illustrates the flowchart for the integrated management of cross-system approval tasks in this project. Figure 4 shows a schematic diagram of the components of the computing device proposed in this work. Implementation

[0014] The following will describe in detail the implementation of this invention with reference to the drawings and embodiments, so that you can fully understand how this invention uses technical means to solve technical problems and achieve technical effects and implement it accordingly.

[0015] The following section will first explain the cross-system approval task integration management system disclosed in this work, and please refer to "Figure 1", which is a block diagram of the cross-system approval task integration management system of this work.

[0016] First, this invention discloses a cross-system approval task integration management system, which includes: a first approval system 10, a second approval system 20, an approval terminal device 30, and an approval task management platform 40. The approval task management platform 40 further includes: an approval task information standardization module 41, an approval task filtering module 42, and a page generation module 43.

[0017] The first approval system 10 provides the first approval system identification information and multiple first pending approval task information to the approval task management platform 40. The second approval system 20 provides the second approval system identification information and multiple second pending approval task information to the approval task management platform 40. The first approval system identification information and the second approval system identification information are used to identify the first approval system 10 and the second approval system 20, respectively. The aforementioned first approval system 10 and second approval system 20 may be administrative operation approval systems, financial transaction approval systems, credit operation approval systems, information change or permission application systems, etc. The approval task items in the aforementioned first pending approval task information and second pending approval task information include, but are not limited to: applicant information, application time information, and approval personnel information. This is only an example and is not intended to limit the application scope of this invention.

[0018] The approval task management platform 40 obtains the first approval system identification information and multiple first approval task information and the second approval system identification information and multiple second approval task information from the first approval system 10 and the second approval system 20 through the application programming interface (API). The aforementioned APIs are, for example, RESTful, SOAP, etc., which are only examples here and are not intended to limit the application scope of this invention.

[0019] Next, the approval task information standardization module 41 of the approval task management platform 40 performs standardization processing based on the standardized data table with multiple standardized fields, filling the approval task items in the first and second approval task information into the corresponding standardized fields of the standardized data table.

[0020] Please refer to Figure 2A. Figure 2A illustrates the standardized data representation for the cross-system approval task integration and management of this invention. The aforementioned standardized data table 50 includes, but is not limited to, the standardized fields of approval system identification field 51, pending approval task identification field 52, applicant field 53, application time field 54, approver field 55, approval time field 56, and approval result field 57. This is only an example and is not intended to limit the application scope of this invention. The approval task information standardization module 41 parses the approval task items of the first pending approval task information and the second pending approval task information, and matches the approval task items with the standardized fields according to the definitions of each standardized field in the standardized data table. The approval task information standardization module 41 can then fill all the approval task items in the first pending approval task information and the second pending approval task information into the corresponding standardized fields in the standardized data table 50, forming standardized approval task data with a consistent structure.

[0021] Specifically, assuming the first approval system identification information is "A01", and the first pending approval task information includes approval task number "Mission_A02", applicant information "Applicant A", application time information "2025 / 11 / 01", and approval personnel information "Review Supervisor A", the approval task information standardization module 41 can write the first approval system identification information "A01" into the approval system identification field 51 of the standardized data table 50, and the approval task information standardization module 41 can write the approval task number "Mission_A02" in the first pending approval task into the pending approval field of the standardized data table 50. The core task identification field 52 and the standardized module 41 for signing task information can write the applicant information "Applicant A" from the first pending signing task information into the applicant field 53 of the standardized data table 50. The standardized module 41 for signing task information can write the application time information "2025 / 11 / 01" from the first pending signing task information into the application time field 54 of the standardized data table 50. The standardized module 41 for signing task information can write the signatory information "Review Supervisor A" from the first pending signing task information into the signatory field 55 of the standardized data table 50. This is only an example and is not intended to limit the application scope of this invention.

[0022] Similarly, assuming the first approval system identification information is "A01", and the first pending approval task information includes approval task number "Mission_A05", applicant information "Applicant A", application time information "2025 / 11 / 10", and approval personnel information "Review Supervisor B", the approval task information standardization module 41 can write the first approval system identification information "A01" into the approval system identification field 51 of the standardized data table 50, and the approval task information standardization module 41 can write the approval task number "Mission_A05" in the first pending approval task into the pending approval field of the standardized data table 50. The task identification field 52 and the standardized module 41 for signing task information can write the applicant information "Applicant A" from the first pending task information into the applicant field 53 of the standardized data table 50. The standardized module 41 for signing task information can write the application time information "2025 / 11 / 10" from the first pending task information into the application time field 54 of the standardized data table 50. The standardized module 41 for signing task information can write the signatory information "Review Supervisor B" from the first pending task information into the signatory field 55 of the standardized data table 50. This is only an example and is not intended to limit the application scope of this invention.

[0023] Similarly, assuming the second approval system identification information is "B02", and the second pending approval task information includes approval task number "Mission_B01", applicant information "Applicant B", application time information "2025 / 11 / 01", and approval personnel information "Review Supervisor B", the approval task information standardization module 41 can write the second approval system identification information "B02" into the approval system identification field 51 of the standardized data table 50, and the approval task information standardization module 41 can write the approval task number "Mission_B01" in the second pending approval task into the pending approval field of the standardized data table 50. The task identification field 52 and the standardized module 41 for signing task information can write the applicant information "Applicant B" from the second pending task information into the applicant field 53 of the standardized data table 50. The standardized module 41 for signing task information can also write the application time information "2025 / 11 / 01" from the second pending task information into the application time field 54 of the standardized data table 50. The standardized module 41 for signing task information can also write the signatory information "Review Supervisor B" from the second pending task information into the signatory field 55 of the standardized data table 50. This is only an example and is not intended to limit the application scope of this invention.

[0024] Similarly, assuming the second approval system identification information is "B02", and the second pending approval task information includes approval task number "Mission_B04", applicant information "Applicant A", application time information "2025 / 11 / 10", and approval personnel information "Review Supervisor B", the approval task information standardization module 41 can write the second approval system identification information "B02" into the approval system identification field 51 of the standardized data table 50, and the approval task information standardization module 41 can write the approval task number "Mission_B04" in the second pending approval task into the pending approval field of the standardized data table 50. The task identification field 52 and the standardized module 41 for signing task information can write the applicant information "Applicant A" from the second pending task information into the applicant field 53 of the standardized data table 50. The standardized module 41 for signing task information can also write the application time information "2025 / 11 / 10" from the second pending task information into the application time field 54 of the standardized data table 50. The standardized module 41 for signing task information can also write the signatory information "Review Supervisor B" from the second pending task information into the signatory field 55 of the standardized data table 50. This is only an example and is not intended to limit the application scope of this invention.

[0025] By standardizing the information on the first and second pending approval tasks as described above, approval task information from different approval systems can be presented in a unified field format, which facilitates the subsequent workflow dispatch, sorting, reminders, status monitoring, and task statistical analysis of all approval tasks by the approval task management platform 40.

[0026] The signing terminal device 30 uses the signing identification information to log in to the signing task management platform 40. The signing identification information may be, for example, a combination of account and password, digital certificate, etc. The signing terminal device 30 may be, for example, a general computer, a laptop computer, a tablet computer, a smart device, etc. This is only an example and is not intended to limit the application scope of this invention.

[0027] After the signing terminal device 30 logs into the signing task management platform 40 using the signing identification information, the signing task filtering module 42 of the signing task management platform 40 filters out the first pending signing task information and / or the second pending signing task information corresponding to the signing identification information from the standardized data table 50.

[0028] Specifically, the approval terminal device 30 logs into the approval task management platform 40 using the approval identification information "Audit Supervisor B". The approval task filtering module 42 filters out one first pending approval task and two second pending approval tasks corresponding to the approval identification information "Audit Supervisor B" from the approval personnel field 55 in the standardized data table 50. The first pending approval task includes an approval task number of "Mission_A05", applicant information of "Applicant A", and application time information of "2025 / 11 / 10". The information for the first pending approval task is "Review Supervisor B". The information for the second pending approval task includes the approval task number "Mission_B01", the applicant information is "Applicant B", the application time information is "2025 / 11 / 01", and the approval personnel information is "Review Supervisor B". The information for the second pending approval task includes the approval task number "Mission_B04", the applicant information is "Applicant A", the application time information is "2025 / 11 / 10", and the approval personnel information is "Review Supervisor B".

[0029] The page generation module 43 of the approval task management platform 40 then generates an approval task management page 60 based on the filtered first and / or second approval task information and provides it to the approval terminal device 30. Following the example above, please refer to Figure 2B for a schematic diagram of the approval task management page 60. Figure 2B illustrates the approval task management page for cross-system approval task integration management in this invention. The approval task management page 60 can present the approval task information in a table format, including the approval task number "Mission". The following are examples of applications with the following information: _A05, applicant information "Applicant A", application date "2025 / 11 / 10", and approver information "Review Supervisor B"; the following are examples of applications with the following information: _A05, applicant information "Applicant A", application date "2025 / 11 / 01", and approver information "Review Supervisor B"; and the following are examples of applications with the following information: _A05, applicant information "Applicant B", application date "2025 / 11 / 10", and approver information "Review Supervisor B".

[0030] The approval task management platform 40 further includes an approval priority ranking module 44. The approval priority ranking module 44 uses an approval priority model to analyze the first and / or second approval task information that has been selected, so as to give priority indicators to the first and / or second approval task information respectively, and then sorts the first and / or second approval task information according to the priority indicators. The page generation module 43 generates an approval task management page based on the sorted first and / or second approval task information.

[0031] The aforementioned approval priority model is based on the historical approval behaviors provided by the first approval system 10 and the second approval system 20 as training data. Historical approval behaviors include, for example: average processing time of past approvals, correlation between task type and urgency, success rate and rejection rate of tasks frequently handled by the approver, characteristics of task amount or risk level, time distribution of different types of tasks being accelerated or delayed, etc. These are only examples and are not intended to limit the application scope of this work.

[0032] The approval priority sorting module 44 then converts the selected first and / or second pending approval task information into feature vectors readable by the approval priority model, so as to give priority indicators to the selected first and / or second pending approval task information respectively. Then, the first and / or second pending approval task information are sorted according to the priority indicators. The page generation module 43 generates an approval task management page based on the sorted first and / or second pending approval task information.

[0033] Following the example above, assuming that the approval priority sorting module 44 assigns a priority index of "0.75" to the first pending approval task information, "0.5" to the first second pending approval task information, and "0.85" to the second second pending approval task information, the approval priority sorting module 44 can sort the first pending approval task information, the first second pending approval task information, and the second second pending approval task information according to the priority index into the second second pending approval task information, the first pending approval task information, and the first second pending approval task information. For a schematic diagram of the sorted pending approval task information and the approval task management page 60, please refer to "Figure 2C". "Figure 2C" is a schematic diagram of the reordering of pending approval tasks in the cross-system approval task integration management of this creation. The pending approval task information is presented in a table format on the approval task management page 60.

[0034] The approval task management platform 40 further includes a prediction and warning module 45. The prediction and warning module 45 predicts omissions in the first approval system 10 and the second approval system 20 based on the approval history records and the correlation of the tasks to be approved. It then sends a reminder to the approval terminal device 30 about the predicted first and / or second tasks to be approved.

[0035] The prediction and warning module 45 can use machine learning classification models (e.g., Logistic Regression, Random Forest, XGBoost, or deep learning models, etc.) to build an omission prediction model. The training data for the omission prediction model includes, for example, task type (procurement, credit granting, authorization, human resources, information maintenance, etc.), task urgency and remaining SLA time, approval load indicators, omission rate of similar tasks, approval history (task types that are often delayed / ignored), whether the task requires cross-unit or multi-stage approval, whether it has dependencies on other tasks, etc., to provide omission risk indicators for the first and / or second tasks to be approved.

[0036] When the prediction and warning module 45 determines that the omission risk index of the first task information to be signed and / or the second task information to be signed is greater than or equal to the indicator threshold, the prediction and warning module 45 can send a reminder to the signing terminal device 30 about the predicted first task information to be signed and / or the second task information to be signed.

[0037] The approval task management platform 40 further includes an approval task discrimination module 46. The approval task discrimination module 46 judges the risk level of the selected first and / or second approval task information. When either the first or second approval task information with a high risk level is selected by the approval terminal device 30, the approval task management platform 40 guides the user to the corresponding first approval system 10 or second approval system 20 for approval procedures. Conversely, when either the first or second approval task information with a low risk level is selected by the approval terminal device 30, the approval task management platform 40 provides direct approval procedures for either the first or second approval task information.

[0038] Next, the operation process of this creation will be explained below. Please also refer to "Figure 3", which shows the flowchart of the cross-system approval task integration and management of this creation.

[0039] First, the first approval system provides its identification information and multiple first pending approval task information to the approval task management platform (step 701); then, the second approval system provides its identification information and multiple second pending approval task information to the approval task management platform (step 702); next, the approval task management platform obtains the first approval system identification information and multiple first pending approval task information, and the second approval system identification information and multiple second pending approval task information from the first and second approval systems respectively through an application interface (step 703); finally, the approval task management platform uses standardized data with multiple standardized fields... The data table is standardized by filling the first and second pending approval task information into the corresponding standardized fields in the standardized data table (step 704); then, the approval terminal device logs into the approval task management platform using the approval identification information (step 705); then, the approval task management platform filters out the first pending approval task information and / or the second pending approval task information corresponding to the approval identification information from the standardized data table (step 706); and the approval task management platform generates an approval task management page based on the filtered first and / or second pending approval task information (step 707).

[0040] The first approval system 10, the second approval system 20, the approval terminal device 30, and the approval task management platform 40 are all different forms of computing devices. Please refer to Figure 4, which shows a schematic diagram of the components of the computing device mentioned in this work.

[0041] The computing device described in this invention includes, but is not limited to, one or more processors 801, one or more memory modules 802, and bus 803, wherein the bus 803 can connect to different hardware components. Through the included multiple hardware components, the computing device can load and execute an operating system, allowing the operating system to run on the computing device, and can also execute software or programs. The computing device also includes a housing 809, within which the aforementioned hardware components are disposed.

[0042] The bus 803 of the computing device mentioned in this invention may include one or more types, such as data bus, address bus, control bus, expansion bus, and / or local bus. The bus of the computing device includes, but is not limited to, parallel Industry Standard Architecture (ISA) buses, Peripheral Component Interconnect (PCI) buses, Video Electronics Standards Association (VESA) local buses, and serial Universal Serial Bus (USB) and High Speed ​​Peripheral Component Interconnect (PCI-E) buses.

[0043] The processor 801 of the computing device described in this invention is coupled to a bus 803. The processor 801 includes a register set or register space, which may be entirely located on the processing chip, or wholly or partially located off-chip and coupled to the processor via dedicated electrical connections and / or via a bus. The processor 801 may be a processing unit, a microprocessor, or any suitable processing element. If the computing device is a multiprocessor device, that is, the computing device contains multiple processors, then the processors contained in the computing device are identical or similar and are coupled and communicate via a bus. The processor 801 can interpret a series of instructions to perform specific operations or calculations, such as mathematical operations, logical operations, data comparison, copying / moving data, etc., to run an operating system or execute various programs, modules, and / or components.

[0044] The processor 801 of the computing device can be coupled to the chipset or electrically connected to the chipset via bus 803. The chipset consists of one or more integrated circuits (ICs), including a memory controller and a peripheral input / output (I / O) controller. That is, the memory controller and the I / O controller can be contained within a single IC or implemented using two or more ICs. The chipset typically provides I / O and memory management functions, as well as multiple general-purpose and / or dedicated registers, timers, etc., which can be accessed or used by one or more processors coupled or electrically connected to the chipset.

[0045] The processor 801 of the computing device can also access data in the memory module 802 and mass storage area installed on the computing device through the memory controller. The memory module 802 includes any type of volatile memory and / or non-volatile memory (NVRAM), such as static random access memory (SRAM), dynamic random access memory (DRAM), flash memory, read-only memory (ROM), etc. The mass storage area can contain any type of storage device or storage medium, such as a hard drive, optical disc, flash drive (flash memory), memory card, solid-state drive (SSD), or any other storage device. In other words, the memory controller can access data in static random access memory, dynamic random access memory, flash memory, hard drive, and solid-state drive.

[0046] The processor 801 of the computing device can also connect and communicate with peripheral devices or interfaces such as peripheral output devices, peripheral input devices, communication interfaces, and GPS receivers via a peripheral input / output controller and bus 803. Peripheral input devices can be any type of input device, such as a keyboard, mouse, trackball, touchpad, or joystick. Peripheral output devices can be any type of output device, such as a monitor or printer. Peripheral input devices and peripheral output devices can also be the same device, such as a touchscreen. Communication interfaces can include wireless communication interfaces and / or wired communication interfaces. Wireless communication interfaces can include interfaces supporting Wi-Fi, Zigbee, Bluetooth, infrared, Near Field Communication (NFC), 3G / 4G / 5G, or other wireless data transmission protocols. Wired communication interfaces can be Ethernet devices, Asynchronous Transfer Mode (ATM) devices, DSL modems, or cable modems. The processor 801 can periodically poll various peripheral devices and interfaces, enabling the computing device to input and output data through various peripheral devices and interfaces, and also to communicate with another computing device having the elements described above.

[0047] The modules mentioned in the first approval system 10, the second approval system 20, the approval terminal device 30, and the approval task management platform 40 are usually generated after the processor 801 in their respective computing devices executes a specific program loaded into the memory module 802, or are contained in the processor 801.

[0048] In summary, the approval task management platform integrates pending approval task information from the first and second approval systems. Using a standardized data table with multiple standardized fields as its core, it parses and maps approval task items from different sources and formats to their corresponding fields. This allows all pending approval tasks to be presented with a unified data structure. Based on the approval identification information provided by the approval terminal device, it dynamically filters pending approval tasks related to the approver from the standardized data table, generating a corresponding approval task management page. This provides users with a single interface to uniformly view all pending approval items across systems.

[0049] This technology can solve the problems of previous technologies, such as the inability to integrate cross-system data, lack of unified data format, inability to sort and assess risks across systems, and lack of omission prediction and intelligent reminder functions. In this way, it can improve the efficiency of cross-system approval operations, reduce the risk of omissions, and enhance the intelligence of the approval process.

[0050] While the embodiments disclosed in this invention are as described above, the content is not intended to directly limit the scope of patent protection for this invention. Anyone skilled in the art to which this invention pertains may make minor modifications in form and detail without departing from the spirit and scope disclosed herein. The scope of patent protection for this invention shall still be determined by the appended claims.

[0051] 10: First Approval System 20: Second Sign-off System 30: Approval terminal device 40: Sign-off Task Management Platform 41: Standardized Module for Sign-off Task Information 42: Sign-off Task Screening Module 43: Page Generation Module 44: Approval Priority Module 45: Prediction and Warning Module 46: Sign-off Task Judgment Module 50: Standardized Data Sheet 51: Sign-off system identification field 52: Task Identification Field (Pending Approval) 53: Applicant Field 54: Application Time Field 55: Signatory Field 56: Approval Time Field 57: Approval Result Field 60: Sign-off Task Management Page 701-707: Steps 801: Processor 802: Memory Module 803: Busbar 809: Outer shell

Claims

1. A cross-system approval task integration management system, comprising: a first approval system providing a first approval system identification information and multiple first pending approval task information to an approval task management platform; a second approval system providing a second approval system identification information and multiple second pending approval task information to the approval task management platform; an approval terminal device logging into the approval task management platform using approval identification information, and displaying multiple first pending approval task information and / or second pending approval task information corresponding to the approval identification information on an approval task management page provided by the approval task management platform; and the approval task management platform being connected to the first approval system, the second approval system, and the approval terminal device, wherein the approval task management platform obtains the first approval system identification information and multiple first pending approval task information and the second approval system identification information and multiple second pending approval task information from the first approval system and the second approval system, respectively, through an application programming interface (API), and the approval task management platform further comprising: A standardized module for approval task information, based on a standardized data table with multiple standardized fields, performs standardized processing to fill the approval task items from the first and second approval task information into the corresponding standardized fields of the standardized data table; a standardized task filtering module, connected to the standardized module for approval task information, filters out the first and / or second approval task information corresponding to the approval identification information from the standardized data table; and a page generation module, connected to the standardized module for approval task information, generates the approval task management page based on the filtered first and / or second approval task information and provides it to the approval terminal device.

2. The cross-system approval task integration management system as described in claim 1, wherein the approval task management platform further includes an approval priority ranking module, the approval priority ranking module being connected to the approval task filtering module and the page generation module respectively, using an approval priority model to analyze the filtered first approval task information and / or second approval task information, to assign a priority index to the filtered first approval task information and / or second approval task information respectively, and then ranking the first approval task information and / or second approval task information according to the priority index, the page generation module generating the approval task management page based on the ranked first approval task information and / or second approval task information.

3. The cross-system approval task integration management system as described in claim 2, wherein the approval task management platform further includes a prediction and warning module, the approval priority ranking module is connected to the approval task filtering module, and based on the approval history records of the first approval system and the second approval system and the correlation of the tasks to be approved, it makes a prediction of omissions in the filtered first and / or second tasks to be approved information, and sends a reminder to the approval terminal device of the predicted first and / or second tasks to be approved information.

4. The cross-system approval task integration management system as described in claim 1, wherein the approval task management platform further includes an approval task discrimination module, the approval task discrimination module is connected to the approval task screening module, the approval task discrimination module judges the risk level of the first approval task information and / or the second approval task information selected by the screening, and when one of the first approval task information or the second approval task information with a high risk level is selected by the approval terminal device, the approval task management platform guides the corresponding first approval system or the second approval system to perform the approval procedure.

5. The cross-system approval task integration management system as described in claim 1, wherein the approval task management platform further includes an approval task discrimination module, the approval task discrimination module is connected to the approval task screening module, the approval task discrimination module judges the risk level of the first approval task information and / or the second approval task information selected by the screening, and when one of the first approval task information or the second approval task information with a low risk level is selected by the approval terminal device, the approval task management platform provides a direct approval procedure for the first approval task information or the second approval task information.

Images