A general data flow approval system, method, device and medium

Abstract

The application relates to a universal data flow approval system, method, device and medium, wherein a client and a public processor and an operation processor in a public approval service are arranged, the client sends an approval request, the public processor pre-registers a callback interface, the callback interface is defined in the operation processor, and the approval system is called to receive a message of the approval request and create an approval sheet in response to the approval request; when execution is successful, a task ID of the approval system is returned, a callback task request is sent, the operation processor receives the callback task request by using the callback interface, corresponding task records are obtained from a storage database according to the task ID of the approval system, and an approval state and a task execution state are updated to complete a final process of an approval chain. Through multi-terminal interaction, the public approval service provides conditions for efficient access of multiple parties to the approval system, thereby simplifying an access process and improving approval processing efficiency.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, and in particular to a universal data flow approval system, method, device and medium. BACKGROUND

[0002] With the rapid development and wide application of information technology, the business approval, report approval and document approval system has been basically realized in various industries such as finance, education and manufacturing, so as to replace the traditional approval mode of paper delivery, greatly improve the business approval efficiency, ensure the transparency of the approval process, increase the accuracy of business approval, and provide real-time approval node for checking at any time, and intuitively grasp the progress of the approval process.

[0003] The existing relatively perfect approval system, such as the Ping An EOA file approval system, can formulate flexible serial, parallel, collaborative and superior-subordinate approval, and can provide multiple flow states. The only disadvantage is that the access is complicated, the learning cost is high, and if in a complex scenario, all systems need to go through a complex process to access, which undoubtedly increases the time and energy of the access party, resulting in low approval processing efficiency, and it is not convenient to manage uniformly, and the user experience is not good. Therefore, how to simplify the access process and improve the approval processing efficiency has become a technical problem to be solved by the technical personnel in the field. SUMMARY

[0004] Therefore, it is necessary to provide a universal data flow approval system, method, device and medium to solve the problem that the existing technology cannot solve the complicated access process of the existing approval system and the low approval processing efficiency.

[0005] The first aspect of the embodiment of the present application provides a universal data flow approval system, which comprises at least one client and a public approval service; the public approval service comprises a public processor and an operation processor, and the at least one client, the public processor and the operation processor are wirelessly connected;

[0006] The public processor pre-registers a callback interface to the approval system, and defines the callback interface in the operation processor;

[0007] The client sends an approval request to the public processor;

[0008] The public processor responds to the approval request, calls the approval system to receive a message of the approval request, and the approval system creates an approval sheet according to the message. When the creation of the approval sheet is successfully executed, the task ID of the approval system is returned;

[0009] The approval system sends a callback task request, wherein the callback task request carries information about the callback interface of the callback task;

[0010] The operation processor receives the callback task request by using the callback interface, obtains a corresponding task record from a storage database according to the task ID of the approval system, updates an approval state and a task execution state, and completes a final process of an approval chain.

[0011] A second aspect of the embodiment of the application provides a general data flow approval method, and the general data flow approval method comprises the following steps:

[0012] The client sends an approval request to the common processor;

[0013] The common processor pre-registers a callback interface to the approval system, defines the callback interface in the operation processor, and in response to the approval request, calls the approval system to receive a message of the approval request, and the approval system creates an approval sheet according to the message, and returns a task ID of the approval system when the creation of the approval sheet is successful;

[0014] The approval system sends a callback task request, wherein the callback task request carries information about the callback interface of the callback task;

[0015] The operation processor receives the callback task request by using the callback interface, obtains a corresponding task record from a storage database according to the task ID of the approval system, updates an approval state and a task execution state, and completes a final process of an approval chain.

[0016] In a third aspect, the embodiment of the application provides a computer device, which comprises a processor, a memory, and a computer program stored in the memory and executable on the processor, and the processor implements the general data flow approval method when executing the computer program.

[0017] In a fourth aspect, the embodiment of the application provides a computer readable storage medium, which stores a computer program, and the computer program is executable on a processor to implement the general data flow approval method.

[0018] In summary, the application provides a general data flow approval system, method, device and storage medium, at least one setting client and a public processor and operation processor in the public approval service are set and wirelessly connected, the client sends an approval request to the public processor, the public processor registers a callback interface to the approval system in advance, defines the callback interface in the operation processor, and in response to the approval request, calls the approval system to receive a message of the approval request, creates an approval sheet according to the message, returns a task ID of the approval system when the creation of the approval sheet is successfully executed, and sends a callback task request, wherein the callback task request carries information related to the callback interface of the callback task, the operation processor receives the callback task request by using the callback interface, obtains the corresponding task record from the storage database according to the task ID of the approval system, and then updates the approval state and the task execution state to complete the final process of the approval chain. The application provides conditions for efficient access of the multi-party to the approval system EOA by using the callback interface for multi-end interaction, thereby simplifying the access process and improving the approval processing efficiency. BRIEF DESCRIPTION OF DRAWINGS

[0019] In order to more clearly illustrate the technical solutions of the embodiments of the application, the following will briefly introduce the drawings needed to be used in the description of the embodiments of the application. Obviously, the drawings in the following description are only some embodiments of the application, and other drawings can be obtained by those skilled in the art without creative labor.

[0020] Figure 1 is a structural schematic diagram of a general data flow approval system provided by an embodiment of the application;

[0021] Figure 2 is an entity information diagram in a general data flow approval system provided by an embodiment of the application;

[0022] Figure 3 is a flow schematic diagram of a general data flow approval method provided by an embodiment of the application;

[0023] Figure 4 is a structural schematic diagram of a computer device provided by an embodiment of the application. DETAILED DESCRIPTION

[0024] The technical solutions in the embodiments of the application will be described clearly and completely below with reference to the drawings in the embodiments of the application. Obviously, the described embodiments are only some embodiments of the application, not all the embodiments. Based on the embodiments in the application, all other embodiments obtained by those skilled in the art without creative labor are within the protection scope of the application.

[0025] It should be understood that the word "comprising" when used in the specification and claims of this application indicates the existence of the stated features, integers, steps, or elements but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, or groups thereof.

[0026] It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items, and that the term "at least one of' denotes one, or a plurality of, or any combination of the listed items.

[0027] As used in the description of the application and the appended claims, the term "if' can be interpreted to mean "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrase "if it is determined" or "if [a described condition or event] is detected" can be interpreted to mean "upon determining" or "in response to determining" or "upon detecting [the described condition or event]" or "in response to detecting [the described condition or event]," depending on the context.

[0028] In addition, the terms "first", "second", "third", etc. as used in the description of the application and the appended claims are merely used for distinguishing between similar elements and do not necessarily have an ordinal or chronological significance.

[0029] Reference herein to "one embodiment" or "some embodiments" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the application. The appearances of the phrases "in one embodiment", "in some embodiments", "in other embodiments", "in additional embodiments", and so on, in various places in the specification are not necessarily all referring to the same embodiment, nor are they necessarily referring to one or more particular embodiments, unless otherwise indicated by the context. The terms "including", "comprising", "having" and variations thereof herein are meant to be broad and encompass the terms "consisting of" and "consisting essentially of", unless otherwise indicated.

[0030] It should be understood that the sequence of steps in the following embodiments does not mean the order of execution, and the execution order of each process should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the application.

[0031] Embodiment one

[0032] Please refer to Figure 1 , Figure 1 The structure schematic diagram of a general data flow approval system in the embodiment of the application is shown. As shown in Figure 1As shown, the general data flow approval system is interacted with at least one client through the public processor and the operation processor, ensures the real-time of the approval process, and improves the approval processing efficiency. It should be noted that the public processor and the operation processor in the general data flow approval system in the embodiment are two different processors, which can be independent processors, or a processor cluster composed of several processors, or a cloud computing processor, etc., which is not limited here; the client includes but is not limited to various personal computers, notebook computers, smart phones, tablet computers, and the client is multiple.

[0033] The general data flow approval system can include: at least one client, a public processor, an operation processor (such as CPU, etc.), a storage database DB, an approval system, a communication bus 1002, a callback interface, a client interface. Among them, the communication bus is used to realize the connection communication between these components. The client interface can include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional client interface can also include a standard wired interface, a wireless interface. The callback interface can assign the reference of the object created by a class using a certain interface to the interface variable declared by the interface, so that the interface variable can call the method of the interface implemented by the class. In fact, when the interface variable calls the method in the interface implemented by the class, it is to inform the corresponding object to call the method of the interface, and this process is called interface callback of object function. The storage database can be a high-speed RAM memory, or a stable memory (non-volatile memory) such as a disk memory, which can store abstract entity information.

[0034] Those skilled in the art can understand that Figure 1 The hardware structure of the general data flow approval system shown in the embodiment does not constitute a limitation on the approval system, and can include more or fewer components than shown, or combine certain components, or different component arrangements.

[0035] In Figure 1 In the embodiment, the approval system includes at least one client and a public approval service; the public approval service includes a public processor and an operation processor, and the at least one client, the public processor and the operation processor are wirelessly connected, and specifically:

[0036] The public processor pre-registers a callback interface to the approval system, and defines the callback interface in the operation processor;

[0037] The client sends an approval request to the public processor;

[0038] The common processor invokes the approval system to receive a message of the approval request in response to the approval request, the approval system creates an approval sheet according to the message, and returns a task ID of the approval system when the creation of the approval sheet is successfully executed;

[0039] The approval system sends a callback task request, wherein the callback task request carries information related to a callback interface of a callback task;

[0040] The operation processor receives the callback task request by using the callback interface, obtains a corresponding task record from a storage database according to the task ID of the approval system, and updates an approval state and a task execution state to complete a final process of the approval chain.

[0041] In the embodiment, the approval system, at least one client, the common processor, and the operation processor are communicatively connected, the client can include a plurality of clients, the approval system is configured to receive an approval request sent by each client, and the approval system is further configured to, when receiving an approval completion instruction returned by the approval end, update an approval state and a task execution state to complete a final process of the approval chain. In addition, the approval user can log in to the approval system through an approval terminal (such as a smart phone, a PC, or the like) to view a to-be-approved sheet and an already-approved sheet under an approval account of the approval user, and can view other related information of the to-be-approved sheet and the already-approved sheet, such as detail information (including information of a department of an applicant, an application time, an application demand, or the like), attachment information (such as a leave case), historical approval information (including an approval time, an approval opinion, an approval type, and a lag time of all already-approved users), approval chain information (including all approval chain information of a current approval sheet), or the like, and can perform approval processing on the to-be-approved sheet through an approval control (including but not limited to read, agree, disagree, return for modification, return to a previous level, task transfer, and assistance approval). It can be understood that the approval user can also be an applicant, and therefore the approval user can also view an already-submitted application sheet of the approval user.

[0042] The public processor in the public approval service is configured to receive an approval request triggered by an application user of a client based on an application terminal (such as a smart phone, a PC or the like), and to generate a corresponding to-be-approved form according to approval information (including application user information, a business system name, an approval event, an approval user and the like) in the approval request, and then to send the to-be-approved form to an approval system. The operation processor in the public approval service is configured to receive an approval result returned by the approval system, and to execute a corresponding operation according to the approval result, to update an approval state and a task execution state, so as to complete a final process of an approval chain. The approval result includes an approval type and approval opinion information. The approval type includes, but is not limited to, read, agree, disagree, return for modification, return to a previous level, task transfer and assisted approval. The approval opinion information is related approval opinion input by an approval user during approval processing. The approval state is approval success or approval success. The task execution state is that the approval of the node has been executed or the approval of the node has not been executed.

[0043] In the embodiment, the client is multiple, such as clientA, clientB, client and the like in the Figure 1 The public processor and the operation processor constitute a public approval service, and the public approval service is a general data flow component. The public processor can receive and process an approval process initiated by a client service, and uniformly interacts with an approval system EOA, and can register a callback interface and query a to-be-approved form state. When the public processor uniformly interacts with the approval system EOA, the approval system EOA can be called across a subsidiary company by a group internal subsystem, and there is a unified ESG platform (an interface management + authentication platform). The ESG platform can be understood as an API centralized management platform. By using a resource group permission of the approval system EOA in the application Ping'an platform, a link can be connected to call the approval system EOA interface, to perform logical operations such as initiating approval, canceling approval and activating approval. The callback interface is registered by using the ESG platform. The public processor applies a new resource group A on the ESG platform, and registers a callback interface parameter and an access address in the resource group A. These registration actions can be directly configured by using a visual interface. The approval system EOA calls the permission of the resource group on the ESG platform, and then realizes the callback. The operation processor mainly receives a callback request of the approval system EOA, and acquires information in a storage database DB to execute actual logic. The public approval service provides conditions for efficient access of multiple parties to the approval system EOA. A developer does not need to spend a large amount of cost to learn the access of the complete approval system EOA, and the development efficiency is improved. The DB storage database entity has more expansion, can record approval description, an initiator, an approver and other notes, and provides conditions for a custom approval chain.

[0044] In the embodiments of the present disclosure, the review process includes at least one level of review, and each level of review includes at least one parallel review node. Parallel means cooperation, which means that the parallel review nodes can make comments and review the data at the same time without affecting each other. Moreover, the review process can be a fixed review process set in advance, or a corresponding review process dynamically set according to actual review data and review conditions. Of course, the review process can also be adjusted during the review process.

[0045] For example, if an audit process includes three audit stages of preliminary review, review, and final review, the preliminary review includes parallel audit nodes of administrative review, market review, procurement review, etc., the review includes financial review, expert review, etc., and the final review includes board member review, etc.

[0046] In the embodiments, in the process of using the general data flow review system to undertake the process review work of insurance companies, medical companies, etc., multi-end interaction is performed by using the callback interface, and the public review service is used to provide conditions for efficient access of multiple parties to the review system EOA, so as to simplify the access process and improve the review processing efficiency.

[0047] As an implementation manner, the information related to the callback interface includes at least one of an address of the callback interface, a request mode of the callback interface, and a callback request parameter of the callback interface.

[0048] For example, taking the callback interface as the target interface for review mentioned in the foregoing as an example, the request mode of the callback interface can include a GET request mode or a POST request mode. Correspondingly, the callback request parameter of the callback interface can be a parameter in the form of a URL (Uniform Resource Locator, uniform resource locator) corresponding to the GET request mode, that is, the transmission parameter is included in the URL; or a parameter in the form of a BODY (package body) corresponding to the POST request mode, that is, the transmission parameter is included in the BODY. It can be understood that the above description of the request mode supported by the callback interface and / or the data format of the callback request parameter is only an example, and according to actual scene requirements and / or according to different functions or types of the callback interface, the request mode supported by the callback interface and / or the data format of the callback request parameter can also include various other different modes and / or formats.

[0049] As an implementation manner, the public processor stores the task ID and the input parameter abstraction information of the review system in a storage database to obtain abstract entity information, and when the review result is passed or not passed, the operation processor interface registered in the public processor is called back.

[0050] In the embodiments, the public processor stores the task ID and the input parameter abstraction information of the review system in a storage database DB to obtain abstract entity information, such asFigure 2 As shown, the task ID of the approval system, the approval chain creator (some identification information such as appld), the service name, the service url, the interface call data packet, the task execution state, etc. are included. When the approval result is passed or not passed, the operation processor interface registered in the public processor is further called back.

[0051] As an implementation, the final process of the approval chain is specifically configured to determine whether the approval state and the task execution state meet the preset condition; if the approval state and the task execution state meet the preset condition, the approval process logic is executed according to the service name, the service url and the request parameter of the entity information in the storage database.

[0052] In this embodiment, the operation processor receives the callback request initiated by the approval system EOA. First, the task ID of the approval system is obtained from the storage database to obtain the corresponding task record, and the approval state and the task execution state are updated. The preset condition is that the approval state and the task execution state are all completed, and if only one side is not completed, it is not allowed. For example, it is necessary to determine whether the approval state is successful and whether the task execution state is executed. If the approval state is successful and the task execution state is executed, it is determined as a success signal, and then according to the service name service_name, the service url, the request parameter data, the specific logic is executed, and the final process of the approval chain is completed. If the approval state is not successful and the task execution state is not executed, it is determined as a success signal, and the final process of the approval chain cannot be completed.

[0053] As an implementation, the approval process logic is configured to call back to the operation processor in the public approval service when the approval is completed, and the operation processor extracts the service url from the storage database and initiates a call request to the client to make the client execute the approval process logic.

[0054] In this embodiment, the service name service_name, the service url and the request parameter data represent the logic that should be executed after the approval is passed. The combination of the three can initiate an http request. That is, http: / / service_name / url (the service name and the service url are client services). The role of this record is to call back the approval system for this approval link, that is, EOA->operation processor->client. When the approval is completed, the operation processor in the public approval service is called back. The operation processor extracts the service url from the storage database DB and initiates a call request to the client to make the client execute the process logic after the approval is successful / failed.

[0055] As an implementation, the public approval service includes two automatic execution callback modes.

[0056] The public approval service is pre-configured with a service name that is an automatic execution client, which automatically executes callback mode logic according to a service url and request parameters input by a user;

[0057] When the approval ends, the public approval service wraps the approval result into a parameter according to a specified format, calls a client service url, and the client automatically executes callback mode logic after receiving the call.

[0058] In this embodiment, the approval public service supports two callback modes. First, configure the automatic execution after approval success. In the approval public service, the service name service_Name is an automatic execution client, which automatically executes an operation action according to a service url and request parameters data input by a user. For example, when a client wants to modify data, the client initiates a report signing by updating the update interface service url and modifying data parameters. The approval public service saves these information in a storage database DB. After the approval is completed, the service url and request parameters data are taken out to initiate a call to help directly modify the data, achieving the effect of interrupting the process and resuming it. Alternatively, the approval public service wraps the parameters to notify the client of a specified service url approval result. That is, the client initiates the approval by carrying the service url. After the approval ends, the approval public service wraps the approval result into a parameter according to a specified format (currently defined as a client producerId, an approval status result approveStatus, and an approval single eoaId), calls the service url of the client, and the client handles the success / failure logic after receiving the call.

[0059] As an implementation, the callback interface is one. Since the approval system EOA and the public approval service only have one callback interaction, only this one callback interface needs to be registered.

[0060] In this embodiment, the public approval service provides conditions for efficient access of multiple parties to the approval system EOA, and the efficient access is reflected in the convenience of other subsystems accessing the approval system EOA. The system newly accessing the approval system EOA needs to go through many link approvals (including alignment of four attachments, two email confirmations, one test acceptance, and approval copy services, managers, and leaders), demand alignment, and the like. In addition, mutual registration, application between interfaces, additional opening of storage space, authorization, and the like are needed in the aspect of attachments. The encapsulation here omits all the complex processes, such as the access of the WeChat Enterprise client operation assistant, and all the above steps can be completely ignored. Directly out of the box, the public approval service can be called, the repeated development and some invalid behaviors are saved, and the development efficiency is improved. Moreover, the DB storage database entity information has more extensions. When the B field needs to be extended, the B field can be directly added to the request parameter data field. The request parameter data field is a JSON structure string. When the client initiates, the service url can be specified according to the business needs, and is not limited to a certain service url. The parameters can be defined by the client, and the request parameter data is arbitrarily spelled as {“A”: xxxx, “B”: xx, “C”: XXX}. Further, the approval description, initiator, approver and other notes can be recorded, and conditions for customizing the approval chain are provided.

[0061] In summary, the application provides a universal data flow approval system, method, device and storage medium. At least one setting client, public processor and operation processor in the public approval service are set and wirelessly connected. The client sends an approval request to the public processor. The public processor pre-registers a callback interface to the approval system. The callback interface is defined in the operation processor. In response to the approval request, the approval system is called to receive a message of the approval request. An approval sheet is created according to the message. When the creation of the approval sheet is successfully executed, a task ID of the approval system is returned. A callback task request is sent, wherein the callback task request carries information related to the callback interface of the callback task. The operation processor receives the callback task request by using the callback interface. The corresponding task record is obtained from the storage database according to the task ID of the approval system. The approval state and the task execution state are updated to complete the final process of the approval chain. The application uses the callback interface for multi-end interaction. The public approval service provides conditions for efficient access of multiple parties to the approval system EOA. The access process is simplified, and the approval processing efficiency is improved.

[0062] Embodiment two

[0063] Please refer to Figure 3 , Figure 3 is a flowchart of the universal data flow approval method provided by the embodiment of the application. The steps of the universal data flow approval method in this embodiment are used to execute Figure 2Corresponding to the hardware in the embodiment. Please refer to Figure 1 And Figure 1 The relevant description in the corresponding embodiment. For ease of illustration, only the part related to the present embodiment is shown. Please refer to Figure 3 The general data flow approval method comprises:

[0064] S301: the client sends an approval request to the public processor;

[0065] S302: the public processor pre-registers a callback interface to the approval system, defines the callback interface in the operation processor, and in response to the approval request, calls the approval system to receive the message of the approval request, and the approval system creates an approval sheet according to the message, and returns the task ID of the approval system when the creation of the approval sheet is successfully executed;

[0066] S303: the approval system sends a callback task request, wherein the callback task request carries information related to the callback interface of the callback task;

[0067] S304: the operation processor receives the callback task request by using the callback interface, obtains the corresponding task record from the storage database according to the task ID of the approval system, updates the approval state and the task execution state, and completes the final process of the approval chain.

[0068] Embodiment three

[0069] Figure 4 is a structural schematic diagram of a computer device provided by the embodiment of the present application. As Figure 4 shown, the computer device of the embodiment comprises a processor, a memory, a network interface and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control ability. The memory of the computer device comprises a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with the external terminal through the network connection. The computer program realizes the steps in any one of the general data flow approval method embodiments described above when the computer program is executed by the processor.

[0070] The computer device can include, but is not limited to, a processor and a memory. Those skilled in the art can understand, Figure 4The computer device is only an example and does not limit the computer device. The computer device can include more or less components than shown, or combine some components, or have different components, such as a network interface, a display screen, and an input device, etc. In one embodiment, a computer device is provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements each step of any embodiment of the general data flow approval method when executing the computer program.

[0071] Embodiment Four

[0072] In one embodiment, a computer readable storage medium is provided, which, when instructions in the computer readable storage medium are executed by a processor in a computer device, enables the computer device to perform each step of any embodiment of the general data flow approval method disclosed in the present application, which is not repeated here. The computer readable storage medium can be non-volatile or volatile.

[0073] The processor can be a CPU, and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic components, discrete hardware components, etc. The general-purpose processor can be a microprocessor or can also be any conventional processor.

[0074] The memory includes a readable storage medium, an internal memory, etc., wherein the internal memory can be the memory of the computer device, and the internal memory provides an environment for the operation system and the computer readable instructions in the readable storage medium. The readable storage medium can be the hard disk of the computer device, and in other embodiments, can also be the external storage device of the computer device, such as the plug-in hard disk, the smart media card (SMC), the secure digital (SD) card, the flash card, etc. Further, the memory can include both the internal storage unit of the computer device and the external storage device. The memory is used to store the operation system, the application program, the boot loader, the data, and other programs, such as the program code of the computer program, etc. The memory can also be used to temporarily store the data that has been output or will be output.

[0075] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer readable storage medium, and when the computer program is executed, the processes of the above-mentioned embodiments of the methods can be included. Any reference to memory, storage, database or other medium used in the embodiments provided in the present application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration but not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0076] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above-mentioned functional units and modules is exemplified, and in actual application, the above-mentioned functions can be completed by different functional units and modules according to needs, that is, the internal structure of the device is divided into different functional units or modules to complete all or part of the functions described above. Each functional unit and module in the embodiment can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or software. In addition, the specific name of each functional unit and module is only for easy distinction, and does not limit the protection scope of the present application. The specific working process of the unit and module in the above-mentioned device can refer to the corresponding process in the above-mentioned method embodiment, which will not be repeated here. If the integrated unit is realized in the form of software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.

[0077] Those skilled in the art can understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized in electronic hardware or a combination of computer software and electronic hardware. Whether the functions are realized in hardware or software manner depends on the specific application and design constraints of the technical solution. The skilled person can use different methods to realize the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0078] The above embodiments are only used to illustrate the technical solutions of the present application, but not limit the present application; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that the technical solutions recorded in the foregoing embodiments can be modified, or some technical features can be replaced by equivalent replacements; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present application.

Claims

1. A universal data flow approval system, comprising at least one client and a common approval service; the common approval service comprises a common processor and an operation processor, and the at least one client, the common processor and the operation processor are wirelessly connected; the common processor pre-registers a callback interface to the approval system and defines the callback interface in the operation processor; the client sends an approval request to the common processor; the common processor responds to the approval request, calls the approval system to receive a message of the approval request, and the approval system creates an approval form according to the message, returns a task ID of the approval system when the creation of the approval form is successfully executed; the approval system sends a callback task request, wherein the callback task request carries information related to a callback interface of a callback task; the operation processor receives the callback task request by using the callback interface, acquires a corresponding task record from a storage database according to the task ID of the approval system, updates an approval state and a task execution state, and completes a final process of an approval chain; wherein the common processor stores the task ID of the approval system and input parameter abstract information in the storage database to acquire abstract entity information, and calls the operation processor interface registered in the common processor when the approval result is passed or not passed; the final process of the approval chain is specifically configured to judge whether the approval state and the task execution state meet preset conditions; if the approval state and the task execution state meet the preset conditions, the approval process logic is executed according to a service name, a service url and request parameters of the entity information in the storage database; the approval process logic is configured to call the operation processor in the common approval service by using the callback interface when the approval process logic is completed, the operation processor extracts the service url from the storage database and initiates a calling request to the client to make the client execute the approval process logic. The information related to the callback interface of the callback task comprises at least one of an address of the callback interface, a request mode of the callback interface and callback request parameters of the callback interface. The common approval service comprises two automatic execution callback modes; The common approval service pre-configures a service name as an automatic execution client, and automatically executes a callback mode logic according to a user-input service url and request parameters; When the approval is completed, the common approval service packs an approval result into input parameters according to a specified format, calls a client service url, and the client automatically executes the callback mode logic after receiving the approval result. The callback interface is one. The universal data flow approval method comprises: a client sends an approval request to a common processor; the common processor pre-registers a callback interface to the approval system, defines the callback interface in an operation processor, and responds to the approval request, calls the approval system to receive a message of the approval request, and the approval system creates an approval form according to the message, returns a task ID of the approval system when the creation of the approval form is successfully executed; ​ ​ 2. The universal data flow approval system of claim 1, wherein, ​ 3. The universal data flow approval system of claim 1, wherein, ​ ​ ​ 4. The universal data flow approval system of any one of claims 1-3, wherein, ​ 5. A general data flow approval method, characterized by, ​ ​ ​ The approval system sends a callback task request, wherein the callback task request carries information related to a callback interface of the callback task; The operation processor receives the callback task request by using the callback interface, acquires a corresponding task record from a storage database according to a task ID of the approval system, updates an approval state and a task execution state, and completes a final process of the approval chain; The public processor stores the task ID of the approval system and the input parameter abstract information in the storage database to obtain abstract entity information, and calls the operation processor interface registered in the public processor when the approval result is passed or not passed; The final process of the approval chain is specifically configured to judge whether the approval state and the task execution state satisfy a preset condition; if the approval state and the task execution state satisfy the preset condition, a service name, a service url and a request parameter of the entity information in the storage database are used to execute an approval process logic; The approval process logic is configured to call the operation processor in the public approval service by using the callback interface when the approval is completed, the operation processor extracts the service url for splicing from the storage database, initiates a calling request to a client, and enables the client to execute the approval process logic.

6. A computer device, comprising: The computer device includes a processor, a memory, and a computer program stored in the memory and executable on the processor, and the processor implements the general data flow approval method of claim 5 when executing the computer program.

7. A computer readable storage medium storing a computer program A sequence, characterized in that, The computer program is executed by the processor to implement the general data flow approval method of claim 5.

Images