Multi-system approval flow processing method and system, electronic equipment and storage medium

Abstract

The invention discloses a multi-system examination and approval flow processing method and system, electronic equipment and a storage medium, the system is a unified office platform system, the method comprises the following steps: when any target subsystem triggers an examination and approval task, obtaining examination and approval flow data of the currently triggered examination and approval task from the target subsystem; converting the approval flow data flow of the approval task into a preset unified data format and uploading; performing management operation on the approval flow data flow of the approval task according to a preset rule; wherein the management operation at least comprises distribution operation of approvers; based on the approval flow data of the approval task, providing the approval task to an approver of the approval task for approval; and synchronizing a task result of the approval task by an approver of the approval task to the target subsystem.

Description

Technical Field

[0001] The present application relates to the technical field of multi-system data processing, and in particular to a multi-system approval flow processing method and system, electronic equipment, and storage medium. Background Art

[0002] Currently, many enterprises, especially large-scale enterprises, usually need to deploy to multiple business systems so that they can complete corresponding businesses through various business systems, such as ERP systems and CRM systems.

[0003] At present, when working with various business systems, we often encounter scenarios where the corresponding personnel need to approve the corresponding business matters. Therefore, in order to facilitate the approval of the corresponding business matters, the current business systems all support the approval function to realize the online approval of the corresponding business matters. Specific staff log in to the corresponding business system as needed, and then initiate the approval task on the business system according to the corresponding logic. Then, when the approver logs in to the business system, he will receive the corresponding notification and approve the approval task.

[0004] However, since there are relatively many business systems, the reviewers need to review more business systems for review, which is very inconvenient and easy to forget. In addition, different business systems have different logics and data formats, so the approval operations required will be different, so errors may occur due to confusion of the operations of each business system. Summary of the invention

[0005] Based on the above-mentioned deficiencies of the prior art, the present application provides a multi-system approval flow processing method and system, electronic device, and storage medium to solve the problem that the prior art is not convenient enough and is prone to errors.

[0006] In order to achieve the above objectives, this application provides the following technical solutions:

[0007] The first aspect of the present application provides a multi-system approval flow processing method, which is applied to a unified office platform system, including:

[0008] When any target subsystem triggers an approval task, the approval flow data of the currently triggered approval task is obtained from the target subsystem;

[0009] Convert the approval flow data flow of the approval task into a preset unified data format and upload it;

[0010] Performing management operations on the approval flow data flow of the approval task according to preset rules; wherein the management operations at least include the allocation operations of the approval personnel;

[0011] Based on the approval flow data of the approval task, providing the approval task to the approver of the approval task for approval;

[0012] The task result of the approval task by the approval personnel of the approval task is synchronized to the target subsystem.

[0013] Optionally, in the above-mentioned multi-system approval flow processing method, the step of acquiring the approval flow data of the currently triggered approval task from the target subsystem includes:

[0014] If the target subsystem belongs to the first type, querying the approval flow data of the currently triggered approval task from the corresponding database table of the target subsystem through the service interface of the target subsystem;

[0015] If the target subsystem belongs to the second type, data mining technology is used to analyze the business process log file of the target subsystem to extract the approval flow data of the currently triggered approval task.

[0016] Optionally, in the above-mentioned multi-system approval flow processing method, converting the approval flow data flow of the approval task into a preset unified data format and uploading it includes:

[0017] Identifying the data format of the target subsystem through an interface module connected to the target subsystem in the unified office platform system;

[0018] According to the mapping relationship between the data format of the target subsystem and the preset unified data format, the approval flow data flow of the approval task is converted into the preset unified data format;

[0019] Encrypting the approval flow data of the approval task after format conversion using an encryption algorithm;

[0020] The encrypted approval flow data of the approval task is uploaded to the approval process management module in the unified office platform system.

[0021] Optionally, in the above-mentioned multi-system approval flow processing method, the management operation on the approval flow data flow of the approval task according to the preset rules includes:

[0022] Determining key information of the approval task from the approval flow data flow of the approval task; wherein the key information of the approval task includes at least the task type and the approval amount;

[0023] Based on the key information of the approval task, the priority of the approval task is set according to preset rules, the approval personnel of the approval task are assigned, and the approval limit time of the approval task is set.

[0024] Optionally, in the above-mentioned multi-system approval flow processing method, providing the approval task to the approver of the approval task for approval based on the approval flow data of the approval task includes:

[0025] Within the approval limit time of the approval task, the approval flow data of the approval task is provided to the approver of the approval task for approval according to the priority of the approval task.

[0026] Optionally, in the above-mentioned multi-system approval flow processing method, it also includes:

[0027] According to the role of the user currently logging into the unified office platform system, permissions corresponding to the role are allocated to the user; wherein the permissions corresponding to the role at least include approval permissions and data query permissions.

[0028] Optionally, in the above-mentioned multi-system approval flow processing method, it also includes:

[0029] Storing the approval flow data of the approval task and the associated data generated by the approval task during the approval process;

[0030] When a user queries the data of the approval task, it is determined whether the user has the authority to query the data of the approval task according to the role of the user;

[0031] If the user has the authority to query the data of the approval task, the data of the approval task is queried and fed back to the user.

[0032] The second aspect of the present application provides a multi-system approval flow processing system, the multi-system approval flow processing system is a unified office platform system, and the multi-system approval flow processing system includes:

[0033] A data acquisition unit, used for acquiring the approval flow data of the currently triggered approval task from any target subsystem when the approval task is triggered by the target subsystem;

[0034] A preprocessing unit, used to convert the approval flow data flow of the approval task into a preset unified data format and upload it;

[0035] A management unit, used to manage the approval flow data flow of the approval task according to preset rules; wherein the management operation at least includes the allocation operation of the approval personnel;

[0036] An approval unit, configured to provide the approval task to an approver of the approval task for approval based on the approval flow data of the approval task;

[0037] The synchronization unit is used to synchronize the task result of the approval task by the approval personnel of the approval task to the target subsystem.

[0038] Optionally, in the above-mentioned multi-system approval flow processing system, the data acquisition unit includes:

[0039] A first data acquisition unit is used to query the approval flow data of the currently triggered approval task from the corresponding database table of the target subsystem through the service interface of the target subsystem when the target subsystem belongs to the first type;

[0040] The second data acquisition unit is used to analyze the business process log file of the target subsystem by using data mining technology when the target subsystem belongs to the second type, and extract the approval flow data of the currently triggered approval task.

[0041] Optionally, in the above-mentioned multi-system approval flow processing system, the pre-processing unit includes:

[0042] A format identification unit, used to identify the data format of the target subsystem through an interface module connected to the target subsystem in the unified office platform system;

[0043] A format conversion unit, configured to convert the approval flow data flow of the approval task into the preset unified data format according to the mapping relationship between the data format of the target subsystem and the preset unified data format;

[0044] An encryption unit, used for encrypting the approval flow data of the approval task after format conversion by using an encryption algorithm;

[0045] The transmission unit is used to upload the encrypted approval flow data of the approval task to the approval process management module in the unified office platform system.

[0046] Optionally, in the above-mentioned multi-system approval flow processing system, the management unit includes:

[0047] An information determination unit, used to determine key information of the approval task from the approval flow data flow of the approval task; wherein the key information of the approval task at least includes the task type and the approval amount;

[0048] The setting unit is used to set the priority of the approval task, assign the approval personnel of the approval task and set the approval limit time of the approval task according to preset rules based on the key information of the approval task.

[0049] Optionally, in the above-mentioned multi-system approval flow processing system, the approval unit includes:

[0050] The approval subunit is used to provide the approval flow data of the approval task to the approver of the approval task for approval within the approval limit time of the approval task and according to the priority of the approval task.

[0051] Optionally, in the above-mentioned multi-system approval flow processing system, it also includes:

[0052] The authority allocation unit is used to allocate the authority corresponding to the role of the user currently logging into the unified office platform system to the user according to the role of the user; wherein the authority corresponding to the role at least includes approval authority and data query authority.

[0053] Optionally, in the above-mentioned multi-system approval flow processing system, it also includes:

[0054] A storage unit, used to store the approval flow data of the approval task and the associated data generated by the approval task during the approval process;

[0055] An authority judgment unit, used for judging whether the user has the authority to query the data of the approval task according to the role of the user when the user queries the data of the approval task;

[0056] The query unit is used to query the data of the approval task and feed back the data to the user when the user has the authority to query the data of the approval task.

[0057] A third aspect of the present application provides an electronic device, including:

[0058] Memory and processor;

[0059] Wherein, the memory is used to store programs;

[0060] The processor is used to execute the program, and when the program is executed, it is specifically used to implement the multi-system approval flow processing method as described in any one of the above.

[0061] A fourth aspect of the present application provides a computer storage medium for storing a computer program, which, when executed by a processor, is used to implement a multi-system approval flow processing method as described in any one of the above.

[0062] The present application provides a multi-system approval flow processing method, which is applied to a unified office platform system. Specifically, when any target subsystem triggers an approval task, the approval flow data of the currently triggered approval task is obtained from the target subsystem, so that when the approval task is triggered on each target subsystem, the approval flow data of its approval task will be obtained. Then the approval flow data flow of the approval task is converted into a preset unified data format and uploaded, so that the approval flow data of the approval task triggered by the target subsystem is formatted in a unified manner so that it can be uploaded to the unified office platform for unified processing. Then, the approval flow data flow of the approval task is managed according to the preset rules. Among them, the management operation at least includes the allocation operation of the approval personnel. Then, based on the approval flow data of the approval task, the approval task is provided to the approval personnel of the approval task for approval, so that the approval task of the target subsystem can be approved on the unified office platform without logging into the target subsystem. Finally, the task results of the approval task of the approval personnel of the approval task are synchronized to the target subsystem, so that the target subsystem can also complete the approval task on it synchronously, which is convenient for subsequent business processing. This ensures that the approval tasks of each target subsystem can be processed directly through the unified office platform system, so there is no need to log in to each target subsystem separately, and one approval operation can be used for approval, making approval more convenient and less prone to operational errors. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0064] Figure 1 A flowchart of a multi-system approval flow processing method provided in an embodiment of the present application;

[0065] Figure 2 A flowchart of a method for format conversion and uploading of an approval flow data stream provided in an embodiment of the present application;

[0066] Figure 3 A flowchart of a method for managing an approval flow data flow provided in an embodiment of the present application;

[0067] Figure 4 A flowchart of a method for querying approval data provided in an embodiment of the present application;

[0068] Figure 5 A schematic diagram of the architecture of a multi-system approval flow processing system provided in an embodiment of the present application;

[0069] Figure 6 A schematic diagram of the architecture of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0070] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0071] In this application, relational terms such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element.

[0072] The present application embodiment provides a multi-system approval flow processing method, which is applied to a unified office platform system. Figure 1 As shown, a multi-system approval flow processing method provided in an embodiment of the present application includes:

[0073] S101. When any target subsystem triggers an approval task, the approval flow data of the currently triggered approval task is obtained from the target subsystem.

[0074] The target subsystem is a system connected to the unified office platform system and managed uniformly through the unified office platform system, such as ERP system, CRM system, financial system, personnel system, etc. Specifically, an interface module can be established and connected with each target subsystem through the interface module.

[0075] Specifically, when a user needs to initiate an approval task, he can use the approval initiation function of the corresponding target subsystem to create and initiate the approval task according to the needs. At this time, the target subsystem will trigger the approval task. In order to be able to approve the approval task through the unified office platform system, the approval flow data of the currently triggered approval task in the target subsystem is obtained through the interface model.

[0076] Optionally, in another embodiment of the present application, a specific implementation of step S101 includes:

[0077] If the target subsystem belongs to the first type, the approval flow data of the currently triggered approval task is queried from the corresponding database table of the target subsystem through the service interface of the target subsystem.

[0078] If the target subsystem belongs to the second type, data mining technology is used to analyze the business process log file of the target subsystem to extract the approval flow data of the currently triggered approval task.

[0079] It should be noted that, since the storage locations of approval flow data are different for different target subsystems, but can be generally divided into storage in the database and storage in the log, in the embodiment of the present application, each target subsystem is divided into the first type or the second type in advance according to the storage location of the approval flow data.

[0080] For the target subsystem belonging to the first type, the approval flow data of the currently triggered approval task can be queried from the corresponding database table of the target subsystem through the service interface of the target subsystem. For example, for the ERP system, the Web service interface provided by it uses the SOAP protocol for communication and queries a specific database table to obtain the approval flow metadata, such as the purchase order amount and the number of days due for payment.

[0081] For the second type of target subsystem, data mining technology is used to analyze the business process log file of the target subsystem to extract the approval flow data of the currently triggered approval task. For example, for the CRM system, data mining technology is used to analyze its business process log file to extract metadata related to customer order approval, such as customer credit rating, order amount, responsible sales representative, etc.

[0082] S102: Convert the approval flow data flow of the approval task into a preset unified data format and upload it.

[0083] Since the formats of approval flow data of different target subsystems are different, in order to adapt to the unified office platform system and to enable unified processing so that the same operations can be used for approval and management, it is necessary to convert the approval flow data flow of the approval task into a preset unified data format and then upload it from the interface module to the unified office platform system for processing.

[0084] Optionally, in another embodiment of the present application, a specific implementation of step S102 is as follows: Figure 2 As shown, the following steps are included:

[0085] S201. Identify the data format of the target subsystem through an interface module connected to the target subsystem in a unified office platform system.

[0086] S202: According to the mapping relationship between the data format of the target subsystem and the preset unified data format, the approval flow data flow of the approval task is converted into the preset unified data format.

[0087] Specifically, in an embodiment of the present application, the mapping relationship between the data format of each target subsystem and the preset unified data format, that is, the mapping relationship between each data, is pre-stored, so the approval flow data flow of the approval task can be converted into the preset unified data format according to the mapping relationship between the data format of the target subsystem and the preset unified data format.

[0088] S203: Encrypt the approval flow data of the approval task after format conversion by using an encryption algorithm.

[0089] In order to ensure the security of data transmission, the approval flow data of the approval task after format conversion needs to be encrypted.

[0090] S204: Upload the encrypted approval flow data of the approval task to the approval process management module in the unified office platform system.

[0091] It should be noted that an approval process management module is set up in the unified office platform system to perform unified management operations on the approval flow data uploaded to the unified office platform system.

[0092] S103: manage the approval flow data flow of the approval task according to preset rules.

[0093] Among them, the management operation at least includes the allocation operation of the approval personnel, so that the approval flow data flow of the approval task can be pushed to the assigned approval personnel for approval. Optionally, the allocation operation of the approval personnel is determined and processed from the approval flow data flow of the approval task, that is, the approval personnel have been specified in the approval flow data flow of the approval task. Therefore, it is only necessary to allocate the approval flow data flow of the approval task to the designated user. It can also be determined in response to the user's operation on the same office platform system, or one of the approval personnel can be selected from multiple already set personnel according to the corresponding rules. Or other methods are adopted. Of course, in addition to the approval personnel operation, other operations can be performed on the approval flow data flow of the approval task according to management needs, such as priority setting.

[0094] Optionally, in another embodiment of the present application, a specific implementation of step S103 is as follows: Figure 3 As shown, including:

[0095] S301. Determine key information of the approval task from the approval flow data flow of the approval task.

[0096] Among them, the key information of the approval task includes at least the task type and the approval amount. Of course, other information can also be set according to needs to facilitate subsequent management operations based on these key information.

[0097] S302: Based on the key information of the approval task, set the priority of the approval task, assign the approval personnel of the approval task, and set the approval limit time of the approval task according to the preset rules.

[0098] It should be noted that in the embodiment of the present application, in addition to assigning the approval personnel of the approval task, the basic management operation also sets the priority of the approval task, so that more important approval tasks can be pushed to the approval personnel first, so that more important approval tasks can be processed first. In order to enable the approval personnel to approve in time within the time limit, the approval limit time of the approval task is also set accordingly.

[0099] Optionally, the personnel who can handle the approval task can be determined based on the task type and the approval amount, and the approval personnel can be selected from them. The priority and approval limit time of the approval task can be determined based on the importance coefficient of the task type and the coefficient corresponding to the range of the approval amount.

[0100] S104. Based on the approval flow data of the approval task, the approval task is provided to the approval personnel of the approval task for approval.

[0101] Specifically, the approval flow data of the approval task is pushed to the account of the approver of the approval task. The approver of the approval task can see the pushed approval flow data of the approval task on the unified office platform system and perform approval operations on the unified office platform system.

[0102] Optionally, in step S103, Figure 3 When the method shown is implemented, accordingly, in the embodiment of the present application, a specific method of step S104 includes:

[0103] Within the approval limit time of the approval task, the approval flow data of the approval task is provided to the approver of the approval task for approval according to the priority of the approval task.

[0104] S105: Synchronize the task results of the approval task by the approval personnel of the approval task to the target subsystem.

[0105] Specifically, after the approver approves the approver, in order to allow the approver on the target subsystem to also have the corresponding approval result, so that the initiator of the approver can promptly learn about the approval status through the target subsystem, so as to facilitate the subsequent business operations in a timely manner, the unified office platform system will synchronize the task result to the target subsystem. After receiving the task result, the target subsystem will set the task result as the approval result of the approval task on it.

[0106] Optionally, in another embodiment of the present application, in order to ensure data security, the following may be further included:

[0107] According to the role of the user currently logging into the unified office platform system, the user is assigned permissions corresponding to the role.

[0108] The permissions corresponding to the role at least include approval permissions and data query permissions. Approval permissions limit the types of tasks that users can approve, while data query permissions limit the data that users can query.

[0109] Correspondingly, in another embodiment of the present application, data query may be further included. Figure 4 As shown, a method for querying approval data provided by an embodiment of the present application includes the following steps:

[0110] S401: Store the approval flow data of the approval task and the associated data generated during the approval process of the approval task.

[0111] S402: When a user queries the data of an approval task, it is determined whether the user has the authority to query the data of the approval task according to the user's role.

[0112] Specifically, no matter the user queries the approval flow data or the associated data of the approval task, it will be determined based on the user's role whether the user has the authority to query the data of the approval task.

[0113] If the user has the authority to query the data of the approval task, step S403 is executed. If the user does not have the authority to query the data of the approval task, the user may be prompted that he does not have the query authority.

[0114] S403: Query the data of the approval task and feed back to the user.

[0115] The embodiment of the present application provides a multi-system approval flow processing method, which is applied to a unified office platform system. Specifically, when any target subsystem triggers an approval task, the approval flow data of the currently triggered approval task is obtained from the target subsystem, so that when the approval task is triggered on each target subsystem, the approval flow data of its approval task will be obtained. Then the approval flow data flow of the approval task is converted into a preset unified data format and uploaded, so that the approval flow data of the approval task triggered by the target subsystem is formatted in a unified manner so that it can be uploaded to the unified office platform for unified processing. Then, the approval flow data flow of the approval task is managed according to the preset rules. Among them, the management operation at least includes the allocation operation of the approval personnel. Then, based on the approval flow data of the approval task, the approval task is provided to the approval personnel of the approval task for approval, so that the approval operation of the target subsystem can be performed on the unified office platform without logging into the target subsystem. Finally, the task results of the approval task by the approval personnel of the approval task are synchronized to the target subsystem, so that the target subsystem can also synchronously complete the approval task on it, which is convenient for subsequent business processing. This ensures that the approval tasks of each target subsystem can be processed directly through the unified office platform system, so there is no need to log in to each target subsystem separately, and one approval operation can be used for approval, making approval more convenient and less prone to operational errors.

[0116] Another embodiment of the present application provides a multi-system approval flow processing system, which is a unified office platform system. Figure 5 As shown, the multi-system approval flow processing system provided in the embodiment of the present application includes:

[0117] The data acquisition unit 501 is used to acquire the approval flow data of the currently triggered approval task from the target subsystem when any target subsystem triggers the approval task.

[0118] The pre-processing unit 502 is used to convert the approval flow data flow of the approval task into a preset unified data format and upload it.

[0119] The management unit 503 is used to manage the approval flow data flow of the approval task according to preset rules, wherein the management operation at least includes the allocation operation of the approval personnel.

[0120] The approval unit 504 is used to provide the approval task to the approval personnel of the approval task for approval based on the approval flow data of the approval task.

[0121] The synchronization unit 505 is used to synchronize the task result of the approval task by the approval personnel of the approval task to the target subsystem.

[0122] Optionally, in a multi-system approval flow processing system provided in another embodiment of the present application, the data acquisition unit includes:

[0123] The first data acquisition unit is used to query the approval flow data of the currently triggered approval task from the corresponding database table of the target subsystem through the service interface of the target subsystem when the target subsystem belongs to the first type.

[0124] The second data acquisition unit is used to analyze the business process log file of the target subsystem by using data mining technology when the target subsystem belongs to the second type, and extract the approval flow data of the currently triggered approval task.

[0125] Optionally, in a multi-system approval flow processing system provided in another embodiment of the present application, the preprocessing unit includes:

[0126] The format recognition unit is used to recognize the data format of the target subsystem through the interface module connected to the target subsystem in the unified office platform system.

[0127] The format conversion unit is used to convert the approval flow data flow of the approval task into a preset unified data format according to the mapping relationship between the data format of the target subsystem and the preset unified data format.

[0128] The encryption unit is used to encrypt the approval flow data of the approval task after format conversion by using an encryption algorithm.

[0129] The transmission unit is used to upload the encrypted approval flow data of the approval task to the approval process management module in the unified office platform system.

[0130] Optionally, in a multi-system approval flow processing system provided in another embodiment of the present application, the management unit includes:

[0131] The information determination unit is used to determine the key information of the approval task from the approval flow data flow of the approval task. The key information of the approval task at least includes the task type and the approval amount.

[0132] The setting unit is used to set the priority of the approval task, assign the approvers of the approval task and set the approval limit time of the approval task according to the preset rules based on the key information of the approval task.

[0133] Optionally, in a multi-system approval flow processing system provided in another embodiment of the present application, the approval unit includes:

[0134] The approval subunit is used to provide the approval flow data of the approval task to the approver of the approval task for approval within the approval limit time of the approval task and according to the priority of the approval task.

[0135] Optionally, in another embodiment of the present application, the multi-system approval flow processing system further includes:

[0136] The authority allocation unit is used to allocate the authority corresponding to the role of the user currently logging into the unified office platform system to the user, wherein the authority corresponding to the role at least includes approval authority and data query authority.

[0137] Optionally, in another embodiment of the present application, the multi-system approval flow processing system further includes:

[0138] The storage unit is used to store the approval flow data of the approval task and the associated data generated by the approval task during the approval process.

[0139] The authority judgment unit is used to judge whether the user has the authority to query the data of the approval task according to the user's role when the user queries the data of the approval task.

[0140] The query unit is used to query the data of the approval task and feed back the data to the user when the user has the authority to query the data of the approval task.

[0141] It should be noted that the specific working process of each unit provided in the above embodiments of the present application can refer to the implementation process of the corresponding steps in the above method embodiments, and will not be repeated here.

[0142] Another embodiment of the present application provides an electronic device, such as Figure 6 As shown, including:

[0143] Memory 601 and processor 602 .

[0144] The memory 601 is used to store programs.

[0145] The processor 602 is used to execute the program stored in the memory 601. When the program is executed, it is specifically used to implement the multi-system approval flow processing method provided by any one of the above embodiments.

[0146] Another embodiment of the present application provides a computer storage medium for storing a computer program. When the computer program is executed by a processor, it is used to implement the multi-system approval flow processing method provided in any of the above embodiments.

[0147] The computer storage media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0148] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0149] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A multi-system approval flow processing method, characterized in that: Applied to the unified office platform system, including: When any target subsystem triggers an approval task, the approval flow data of the currently triggered approval task is obtained from the target subsystem; Convert the approval flow data flow of the approval task into a preset unified data format and upload it; Performing management operations on the approval flow data flow of the approval task according to preset rules; wherein the management operations at least include the allocation operations of the approval personnel; Based on the approval flow data of the approval task, providing the approval task to the approver of the approval task for approval; The task result of the approval task by the approval personnel of the approval task is synchronized to the target subsystem.

2. The method according to claim 1, characterized in that The acquiring the approval flow data of the currently triggered approval task from the target subsystem includes: If the target subsystem belongs to the first type, querying the approval flow data of the currently triggered approval task from the corresponding database table of the target subsystem through the service interface of the target subsystem; If the target subsystem belongs to the second type, data mining technology is used to analyze the business process log file of the target subsystem to extract the approval flow data of the currently triggered approval task.

3. The method according to claim 1, characterized in that: The step of converting the approval flow data flow of the approval task into a preset unified data format and uploading the data format includes: Identifying the data format of the target subsystem through an interface module connected to the target subsystem in the unified office platform system; According to the mapping relationship between the data format of the target subsystem and the preset unified data format, the approval flow data flow of the approval task is converted into the preset unified data format; Encrypting the approval flow data of the approval task after format conversion using an encryption algorithm; The encrypted approval flow data of the approval task is uploaded to the approval process management module in the unified office platform system.

4. The method according to claim 1, characterized in that The managing operation on the approval flow data flow of the approval task according to the preset rules includes: Determining key information of the approval task from the approval flow data flow of the approval task; wherein the key information of the approval task includes at least the task type and the approval amount; Based on the key information of the approval task, the priority of the approval task is set according to preset rules, the approval personnel of the approval task are assigned, and the approval limit time of the approval task is set.

5. The method according to claim 4, characterized in that The step of providing the approval task to an approver of the approval task for approval based on the approval flow data of the approval task includes: Within the approval limit time of the approval task, the approval flow data of the approval task is provided to the approver of the approval task for approval according to the priority of the approval task.

6. The method according to claim 1, characterized in that Also includes: According to the role of the user currently logging into the unified office platform system, permissions corresponding to the role are allocated to the user; wherein the permissions corresponding to the role at least include approval permissions and data query permissions.

7. The method according to claim 6, characterized in that Also includes: Storing the approval flow data of the approval task and the associated data generated by the approval task during the approval process; When a user queries the data of the approval task, it is determined whether the user has the authority to query the data of the approval task according to the role of the user; If the user has the authority to query the data of the approval task, the data of the approval task is queried and fed back to the user.

8. A multi-system approval flow processing system, characterized in that: The multi-system approval flow processing system is a unified office platform system, and the multi-system approval flow processing system includes: A data acquisition unit, used for acquiring the approval flow data of the currently triggered approval task from any target subsystem when the approval task is triggered by the target subsystem; A preprocessing unit, used to convert the approval flow data flow of the approval task into a preset unified data format and upload it; A management unit, used to manage the approval flow data flow of the approval task according to preset rules; wherein the management operation at least includes the allocation operation of the approval personnel; An approval unit, configured to provide the approval task to an approver of the approval task for approval based on the approval flow data of the approval task; The synchronization unit is used to synchronize the task result of the approval task by the approval personnel of the approval task to the target subsystem.

9. An electronic device, characterized in that: include: Memory and processor; Wherein, the memory is used to store programs; The processor is used to execute the program, and when the program is executed, it is specifically used to implement the multi-system approval flow processing method as described in any one of claims 1 to 7.

10. A computer storage medium, characterized in that: Used to store a computer program, which, when executed by a processor, is used to implement the multi-system approval flow processing method as described in any one of claims 1 to 7.

Images