An examination method and system suitable for a multi-examination platform and an electronic device

Abstract

The application discloses a kind of suitable for multi-approval platform's approval method, system and electronic equipment, in the method, according to the approval initiation request obtained, determine the approval platform of processing approval initiation request;Through uniform approval flow interface, the adapter of approval platform is called to create the approval instance of approval initiation request;According to the approval template corresponding to approval initiation request, generate notification content for approval instance;Notification content is sent to approval business associated person, and the approval result of approval business associated person is returned.The invention adopts uniform approval flow interface and adapter, can quickly connect different approval platforms, reduce the cost of repeated development, can reduce the work burden of developer, and through the notification content generated for approval instance by approval template, can reduce the complexity of data exchange and synchronization, to improve approval accuracy and efficiency.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, and in particular to an approval method and system suitable for multiple approval platforms and electronic equipment. BACKGROUND

[0002] Under the background of enterprise informatization and digital transformation, enterprises are facing increasingly complex business processes and approval requirements. This complexity not only comes from the diversity of business itself, but also from the coordination and integration between different departments and systems within the enterprise. In this case, the importance of the approval process system is increasingly highlighted. These systems can significantly improve the efficiency, transparency and traceability of business processes.

[0003] However, as the enterprise scale expands and business processes increase, a single approval system often cannot meet the needs of the enterprise. Therefore, enterprises often need to introduce multiple third-party approval systems to cover different business scenarios, but the coexistence of multiple systems has the following problems:

[0004] First, different third-party approval systems, such as DingTalk, WeChat for Enterprise, SAP, Oracle, etc., usually have their own interface specifications and calling protocols. Developers need to be familiar with and adapt to the interface of each system when integrating the system, which not only takes time and is prone to errors, but also increases the workload of developers. Second, data exchange and synchronization between different approval systems becomes very complex, which can lead to problems affecting data consistency and thus the accuracy of enterprise decision-making. It can be seen that the current approval system has the problems of low approval accuracy and low efficiency. SUMMARY

[0005] The embodiments of the present application provide an approval method and system suitable for multiple approval platforms and electronic equipment to solve the problems of low approval accuracy and low efficiency caused by multiple existing approval platforms.

[0006] In a first aspect, the embodiments of the present application provide an approval method suitable for multiple approval platforms, which comprises:

[0007] According to the obtained approval initiation request, determine the approval platform for processing the approval initiation request;

[0008] Create an approval instance of the approval initiation request by calling the adapter of the approval platform through a unified approval flow interface;

[0009] Generate notification content for the approval instance according to the approval template corresponding to the approval initiation request;

[0010] Send the notification content to the approval business associate and return the approval result of the approval business associate.

[0011] Further, the creating, by the adapter of the approval platform, of the approval instance of the approval initiation request through the unified approval flow interface comprises:

[0012] The approval initiation request is routed to the adapter of the approval platform according to the approval type and / or configuration identifier carried by the approval initiation request through the unified approval flow interface.

[0013] The adapter of the approval platform converts the approval initiation request in the unified format into the interface call and data format corresponding to the approval platform, to obtain the approval instance of the approval initiation request.

[0014] Further, if the approval platform is a system built-in approval system, the adapter of the approval platform comprises a process orchestration engine.

[0015] The creating, by the adapter of the approval platform, of the approval instance of the approval initiation request through the unified approval flow interface comprises:

[0016] The approval initiation request is routed to the process orchestration engine of the system built-in approval system according to the approval type and / or configuration identifier carried by the approval initiation request through the unified approval flow interface.

[0017] Further, the generating, by the approval template corresponding to the approval initiation request, of the notification content for the approval instance comprises:

[0018] The approval information in the approval instance is mapped and replaced with the placeholder in the approval template corresponding to the approval initiation request, to generate the notification content.

[0019] Further, the returning of the approval result of the approval business associated person comprises:

[0020] When it is identified that the approval flow of the approval initiation request enters an end state, a approval result callback mechanism is triggered to asynchronously push the approval result of the approval business associated person to the callback interface of the approval initiation request.

[0021] The approval result is authenticated using a pre-saved identity authentication token.

[0022] If the authentication is passed, the approval result is returned through the callback interface.

[0023] Further, before determining the approval platform for processing the approval initiation request according to the obtained approval initiation request, the method further comprises:

[0024] The parameters in the obtained approval initiation request are assembled into a preCommit object.

[0025] Pre-verification is performed on the preCommit object by calling a pre-verification interface and using a predefined business rule service.

[0026] If the pre-verification is passed, an approval process is created for the approval initiation request.

[0027] Further, the notification content is sent to an approval business associate, and an approval result of the approval business associate is returned.

[0028] The notification content is sent to an approval business associate by using a message queue, and an approval result of the approval business associate is returned.

[0029] Further, the method is applied to an approval system, and the approval system is deployed in a single form or a cluster form.

[0030] In a second aspect, an embodiment of the present application provides an approval system suitable for a multi-approval platform, and the system comprises:

[0031] A determination module is configured to determine an approval platform for processing an approval initiation request according to the obtained approval initiation request.

[0032] A processing module is configured to create an approval instance of the approval initiation request by calling an adapter of the approval platform through a unified approval flow interface, and generate notification content for the approval instance according to an approval template corresponding to the approval initiation request.

[0033] A notification module is configured to send the notification content to an approval business associate, and return an approval result of the approval business associate.

[0034] Further, the processing module is specifically configured to route the approval initiation request to the adapter of the approval platform according to an approval type and / or a configuration identifier carried by the approval initiation request through the unified approval flow interface, and convert the approval initiation request in a unified format into an interface call and a data format corresponding to the approval platform by using the adapter of the approval platform, to obtain an approval instance of the approval initiation request.

[0035] Further, if the approval platform is a system built-in approval system, the adapter of the approval platform comprises a flow arrangement engine.

[0036] The processing module is specifically configured to route the approval initiation request to the flow arrangement engine of the system built-in approval system according to the approval type and / or the configuration identifier carried by the approval initiation request through the unified approval flow interface.

[0037] Further, the processing module is specifically configured to map and replace the approval information in the approval instance with the placeholder in the approval template corresponding to the approval initiation request, to generate notification content.

[0038] Further, the notification module is specifically configured to trigger an approval result callback mechanism when identifying that the approval process of the approval initiation request enters an end state, to push the approval result of the approval business associated person to a callback interface of the approval initiation request asynchronously, to authenticate the approval result using a pre-saved identity authentication token, and to return the approval result through the callback interface if the authentication is passed.

[0039] Further, the pre-verification module is further configured to assemble the parameters in the obtained approval initiation request into a preCommit object, to perform pre-verification on the preCommit object using a pre-defined business rule service by calling a pre-verification interface, and to create an approval process for the approval initiation request if the pre-verification is passed.

[0040] Further, the notification module is specifically configured to send the notification content to the approval business associated person using a message queue, and to return the approval result of the approval business associated person.

[0041] Further, the approval system is deployed in a single form or in a cluster form.

[0042] In a third aspect, an electronic device is provided, which includes a processor and a memory, the memory is configured to store a program instruction, and the processor is configured to implement the steps of the above-mentioned approval method suitable for a multi-approval platform when executing the computer program stored in the memory.

[0043] In a fourth aspect, a computer readable storage medium is provided, which stores a computer program, and the computer program is executed by a processor to implement the steps of the above-mentioned approval method suitable for a multi-approval platform.

[0044] In the embodiment of the present application, the approval platform for processing the approval initiation request is determined according to the obtained approval initiation request, the adapter of the approval platform is called through the unified approval flow interface to create the approval instance of the approval initiation request, the notification content is generated for the approval instance according to the approval template corresponding to the approval initiation request, the notification content is sent to the approval business associated person, and the approval result of the approval business associated person is returned. In the present application, the unified approval flow interface and the adapter are used to quickly connect different approval platforms, reduce the repeated development cost, reduce the work burden of the developers, and generate the notification content for the approval instance through the approval template, which can reduce the complexity of data exchange and synchronization, and improve the approval accuracy and efficiency. BRIEF DESCRIPTION OF DRAWINGS

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

[0046] Figure 1 A process schematic diagram of an approval method suitable for a multi-approval platform provided by an embodiment of the present application;

[0047] Figure 2 A structure schematic diagram of an approval system suitable for a multi-approval platform provided by an embodiment of the present application;

[0048] Figure 3 A structure schematic diagram of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0049] In order to make the objects, technical solutions and advantages of the present application more clear, the present application will be further described in detail below with reference to the drawings. Obviously, the described embodiments are only some embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without any creative effort are within the scope of protection of the present application.

[0050] In order to solve the problems of low accuracy and low efficiency of the existing multiple approval platforms, an approval method, system and electronic device suitable for a multi-approval platform are provided by an embodiment of the present application.

[0051] Embodiment 1: Figure 1 A process schematic diagram of an approval method suitable for a multi-approval platform provided by an embodiment of the present application, the process includes the following steps:

[0052] S101: According to the obtained approval initiation request, determine the approval platform for processing the approval initiation request.

[0053] S102: Create an approval instance of the approval initiation request through a unified approval flow interface and call an adapter of the approval platform.

[0054] S103: Generate notification content for the approval instance according to the approval template corresponding to the approval initiation request.

[0055] S104: Send the notification content to the approval business associate and return the approval result of the approval business associate.

[0056] The application embodiment adopts the unified approval flow interface and adapter, can quickly connect different approval platforms, reduces the repeated development cost, can reduce the work burden of the developer, and can reduce the complexity of data exchange and synchronization through the approval template to generate the notification content for the approval instance, thereby improving the approval accuracy and efficiency.

[0057] The application embodiment provides the approval method suitable for multiple approval platforms, and is applied to an approval system.

[0058] The approval initiation request obtained in S101 can be an approval initiation request transmitted when a business system (for example, a CRM (Customer Relationship Management) system) or an external interface calls the approval service (that is, the approval system). The approval initiation request can include the following parameter information: an approval type, initiator information, business parameters, and callback configuration information (optional). The approval type can be, for example, performance information complaint, performance supplement complaint, and the like. The initiator information can include, for example, a user ID (IDentity), a department, and the like. The business parameters are used to describe the key fields required for the current approval, such as an amount, a quantity, a time, and the like. The callback configuration information can be used to identify security information, such as the target interface address and Token (identity verification token) to which the result needs to be returned after the current approval.

[0059] The approval service provides an approval flow adapter. (1) When performing adapter packaging, independent adapter classes can be written for different third-party approval platforms. Each adapter implements a set of uniformly defined methods to ensure consistent calling processes. The adapter can complete the adaptation and packaging of third-party API (Application Programming Interface, application programming interface) parameters, authentication methods, and message formats. (2) When performing dynamic loading and configuration of the adapter, the configuration center or the database can be used to record the approval types, business scenarios, calling methods, and the like corresponding to the adapter. When the system receives an approval request, the corresponding configuration is queried, and the request is automatically routed to the specified adapter without the need for hard coding at the code level. (3) In an example, if Dingding approval is used, the adapter needs to convert the unified request structure into the Dingding Request format, fill in the required fields of the Dingding API, and then call the interface for creating an approval form. When the approval status is updated, the adapter is also responsible for extracting the status code from the Dingding callback analysis and converting it into the unified approval status identifier of the system. In S101 in the example, the approval platform that processes the request can be determined according to the business type in the approval initiation request, and then routed to the corresponding adapter.

[0060] In a possible implementation manner, the adaptation to multiple approval platforms can be achieved by selecting and processing through the approval flow adapter. For example, in S102 described above, the approval initiation request can be routed to the adapter of the approval platform through the unified approval flow interface according to the approval type and / or configuration identifier carried by the approval initiation request. The adapter of the approval platform is used to convert the approval initiation request in the unified format into the interface call and data format corresponding to the approval platform, to obtain the approval instance of the approval initiation request.

[0061] In this implementation manner, through the unified approval flow interface, the system can route to the adapter of the corresponding third-party approval platform (such as Dingding, WeChat for Enterprise, SAP, etc.) or use the built-in approval engine of the system according to the approval type or configuration identifier. The adapter is responsible for converting the internal unified format of the approval request into the interface call and data format required by the third-party platform. If it is a self-developed approval module of the system, the local process orchestration engine is directly called. In an example, if the approval platform is a built-in approval system of the system, the adapter of the approval platform includes the process orchestration engine. When the approval initiation request is routed to the process orchestration engine of the built-in approval system of the system through the unified approval flow interface according to the approval type and / or configuration identifier carried by the approval initiation request, the approval initiation request can be routed to the process orchestration engine of the built-in approval system of the system through the unified approval flow interface according to the approval type and / or configuration identifier carried by the approval initiation request.

[0062] In this implementation, the approval service also provides a unified approval flow interface. (1) The unified approval flow interface can provide a unified HTTP (Hypertext Transfer Protocol) or RPC (Remote Procedure Call) entry when the API gateway is designed, support multiple request methods (GET, POST, PUT, DELETE) and data formats (JSON, XML, form-urlencoded, etc.), and distribute to specific adapters through fields in the request Header or query parameters. (2) When routing and authentication are performed, the unified approval flow interface can utilize the routing configuration of the gateway layer to help the system decouple from third-party platforms. If the system provides services to the outside, unified authentication and authorization need to be performed at the gateway layer to avoid directly exposing internal services.

[0063] After the approval instance is successfully created in 102, the system calls the notification and template management function to select a corresponding notification template according to the approval type and / or configuration information in the approval initiation request. In one implementation, in S103, the approval information in the approval instance can be mapped and replaced with placeholders in the approval template corresponding to the approval initiation request to generate notification content.

[0064] In this implementation, the approval service also provides a notification and template management function. (1) This function can implement template management and matching. For example, in a database or configuration center, corresponding notification templates, channels, and placeholder rules are configured for different approval types or subtypes. After receiving an approval process creation event, a suitable notification template is matched according to the approval type and business parameters (such as the amount size or department). (2) This function can implement dynamic data filling. Notification templates often contain placeholders. After obtaining the approval request data, the system calls a template engine for dynamic replacement. If it is connected to an enterprise internal data extraction service, it can declare in the configuration file where more fields need to be extracted, and then write the extraction results to the template to generate a complete notification message. (3) This function can implement multi-channel notification. The module can configure sending channels as needed, such as: 1. Enterprise WeChat / DingTalk internal IM (Instant Messaging) messages; 2. Email; 3. SMS; 4. Webhook or custom push; the system maintains independent sending submodules for each channel to ensure flexibility; if sending fails, logs are recorded and retries or degradation are performed according to the configuration. (4) This function can implement associated processes. The notification and approval process status are kept synchronized: remind the approver when creating, notify the applicant (i.e., the initiator) when rejecting, and notify the finance or downstream system when passing; each notification has a unique ID or log record for easy subsequent tracking and auditing.

[0065] The approval initiation request is mapped and replaced with the placeholders in the template, the notification content is generated, and is sent to the relevant approvers or followers through a specified channel (such as email, SMS, or IM). If a multi-channel parallel or failure retry strategy is configured, the notification operation is performed sequentially or in parallel. Optionally, in S103, if the required notification template is not hit or there is no suitable notification template, the system administrator and the corresponding business personnel are informed through the system notification, and the template is supplemented.

[0066] In S104, the notification content is sent to the approval business associated person (including the approver, and can also include the remaining associated persons such as the supervisor). The approver can pass, reject, or transfer the application based on the business rules in the third-party platform or the local approval engine. The approval operation of each node in the process is synchronized back to the system (or actively queried by the system at regular intervals), the process state is updated, and the operation log is written, so that the approval flow transfer and state maintenance can be realized.

[0067] In S104, the approval completion and result callback can also be realized. In the example, when the approval result of the approval business associated person is returned, the approval result callback mechanism is triggered when the approval process enters the end state, and the approval result of the approval business associated person is pushed to the callback interface of the approval initiation request asynchronously. The approval result is authenticated using a pre-saved identity authentication token. If the authentication is passed, the approval result is returned through the callback interface. In this example, when the approval process enters the end state (including pass, reject, and cancel), the system triggers the “approval result callback mechanism”. If the callback address is configured by the calling party or the business system when it is initiated, the system will push the approval result, approval time, approval single ID, and other key information to the corresponding interface asynchronously, and use the Token or security token pre-saved in the database for authentication. After the callback call is successful, the relevant response is recorded in the log. If it fails, it will continue to try according to the configured retry strategy, or finally record the failure state for subsequent troubleshooting.

[0068] The approval service also provides an approval result callback mechanism. (1) Callback information registration can be achieved. When the approval is initiated, if the callback address (callbackUrl) and security token (token, etc.) are passed by the calling party, the system will save them together with the approval sheet ID in the database. If the callback interface is uniformly specified in the configuration center for the approval type, registration can also be automatically completed. (2) Asynchronous calling process can be achieved. When the approval ends in the third-party system or local engine, the system will trigger an end event. The callback mechanism module listens to the event, reads the previously recorded callback information in the database, assembles the callback parameters, including: approval result (pass, reject, revoke, etc.), approval sheet ID, approver list, approval time, etc., custom fields (if the template or rules require), uses Token and other security information to send a callback request to the target interface through HTTPS or signature method. (3) Security and retry can be achieved. Callback can use signature mechanism or Token verification to avoid being forged or intercepted. If the callback fails (network failure, timeout, abnormality of the other party), the system will try multiple times according to the configured retry strategy (retry interval, maximum number of times, etc.). If the retry still fails, it will be recorded in the callback failure table for subsequent manual or automatic compensation.

[0069] In a possible implementation manner, before S101, pre-verification can also be performed. For example, the parameters in the obtained approval initiation request can be assembled into a preCommit object. A pre-defined business rule service is called to perform pre-verification on the preCommit object. If the pre-verification passes, an approval process is created for the approval initiation request. In this implementation manner, if the system configuration has enabled the "pre-verification function" and the corresponding approval type needs to be pre-verified, the pre-verification interface will be called before the approval process is formally created. The system assembles the necessary parameters in the current approval request into a preCommit object. The preCommit object is sent to the pre-defined business rule service by calling the "verification interface" recorded in the configuration center or the database. If the verification fails, the system immediately returns an error message and interrupts the process. If the verification passes, the subsequent operation is continued.

[0070] In this implementation, the present approval service also provides a pre-verification function, (1) can realize triggering and interface calling, when the system checks that the approval type needs pre-verification, or the calling party explicitly declares "enable pre-verification" when initiating the request, the system will first assemble the preCommit object; call the configured "verification interface" URL (Uniform Resource Locator, Uniform Resource Locator), and send the core business parameters together to perform verification. (2) The processing of the verification result can be realized. If the verification returns "not passed", the system will terminate the process creation and return the corresponding error code and error information to the calling party; if the verification "passes", the normal approval process is created and the subsequent operations such as notification, callback, etc. are triggered. (3) It can prevent process waste and context consistency. Through pre-verification, it can prevent the situation of being rejected after entering the approval due to unsatisfied business logic, and improve the system efficiency; the system will completely retain all operation logs and process context records, ensuring that the introduction of the pre-verification function does not affect the accuracy and consistency of the existing operation history.

[0071] In addition, the present approval service can provide subsequent operations and high-availability support. If the approval passes and subsequent business operations need to be triggered (such as automatically generating a complaint form, updating the CRM approval form status, etc.), it can be done in the notification or callback stage.

[0072] In high-availability design, the entire system can be deployed in a single form or support clustering and load balancing to ensure stable operation in high-concurrency and high-availability scenarios, and to improve system fault tolerance through distributed caching, message queues, etc. (1) Implement single and cluster support. The approval system using this method is deployed in a single form or in a cluster form. The system can be deployed as a single application in small and medium-sized scenarios, and can distribute requests to multiple nodes through load balancing when the business volume is high. The same database or distributed cache is shared between nodes to ensure consistency of process status and callback information. (2) Implement message queue and asynchronous processing. For notification sending and callback processing, which are prone to blocking, message queues can be used to achieve asynchronous processing and improve system throughput. If node failure causes notification tasks to be incomplete, message retry or consumer switching mechanisms can be used to transfer remaining tasks to healthy nodes. For example, in S104 above, a message queue can be used to send notification content to the approval business associate and return the approval result of the approval business associate. (3) Implement configuration center and rule engine. Key information such as notification templates, callback addresses, and pre-verification interfaces can be placed in a distributed configuration center and updated dynamically through a listening mechanism. For complex business rules, script engines or rule engines can be used to achieve dynamic adjustment without frequent system code modifications.

[0073] Currently, in the environment of multiple systems coexisting, there are the following technical problems: 1. Interface diversity: Different third-party approval systems (such as Dingding, WeChat for Enterprise, SAP, Oracle, etc.) usually have their own interface specifications and calling protocols. When developing system integration, developers need to be familiar with and adapt to the interface of each system, which not only consumes time and is prone to errors, but also increases the workload of developers. 2. Data exchange complexity: Data exchange and synchronization between approval systems becomes very complex. The lack of effective standards and tools can lead to data consistency problems, affecting the accuracy of enterprise decision-making. 3. Cross-system process integration: In the case of multiple systems coexisting, it is a big problem to realize the automation and integration of end-to-end business processes. The approval status and results between different systems need to be coordinated, which is usually achieved through manual intervention or complex code in the prior art, increasing the difficulty of maintenance. 4. Maintenance and upgrade difficulties: As the business of the enterprise changes and the third-party system updates, developers need to frequently adjust and upgrade the system. This constantly changing environment increases the complexity of system operation and maintenance. 5. Lack of standardization: Due to the lack of unified approval interface standards, the interoperability between systems is poor. This limits the flexibility of enterprises in choosing and replacing systems, further increasing the cost of enterprise digital transformation. Against the above background, the market urgently needs a solution that can provide a unified approval interface standard, realize high integration and flexible configuration between different systems, and thus reduce development and maintenance costs, improve enterprise operation efficiency and response capability.

[0074] Based on this, the embodiment of the present application provides an approval method and system suitable for multiple approval platforms, and proposes the following processing methods: 1. Approval flow adapter: Provide corresponding adapters for different third-party approval platforms (such as Dingding approval, WeChat Enterprise approval, etc.), and encapsulate the interfaces of different platforms into a unified interface specification. 2. Unified approval flow interface: Provide a unified API interface for CRM system to call, simplify the integration and development of the approval process. The interface supports multiple HTTP request methods (GET, POST, PUT, DELETE) and data formats (JSON, XML, POST, form-urlencoded), which is convenient for developers to call flexibly. 3. Notification and template management: Support configuring different approval flows and message notification templates. Through the abstract template engine, the notification content can be dynamically generated according to different approval types and data. If there is an existing data extraction service, it can be directly configured for reuse without additional development. 4. Approval result callback mechanism: Support asynchronous callback mechanism, and push the approval result to the specified callback interface. In order to realize cross-system callback, the system saves the callback interface address and the Token information required for calling, uses the Token associated with the creator for callback, and avoids damaging the interface logic of the original system. 5. Pre-verification function: Support pre-verification function before approval. When pre-verification is enabled, the system will call the pre-defined verification interface before submitting the approval, and pass the pre-verification parameters (preCommit) to the interface. The verification interface can judge whether to allow submitting the approval according to the business logic, and return the verification result. If the verification fails, the subsequent approval process is interrupted. The callback interface needs to be modified accordingly to receive the pre-verification parameters. 6. Context integrity: The operation log after the approval is executed is consistent with the operation log before joining the approval, and the operation record and other records will not be recorded incorrectly due to joining the approval.

[0075] Through the above embodiments, the present scheme can realize the following effects in an enterprise environment where multiple platforms and multiple systems coexist: unified interface and adapter: quickly connect to Dingding, WeChat Enterprise, SAP, Oracle and other approval platforms, and can add or delete adapters as needed, reducing the cost of repeated development. Notification and template management: flexibly configure message content and multi-channel push strategy, significantly improving the notification efficiency of the approval node. Approval result callback: through asynchronous callback and retry mechanism, ensure that the approval information can be obtained by external business systems in time. Pre-verification function: effectively reduces the creation of invalid approval processes, improves the approval success rate and maintains context consistency. High availability and scalability: Use cluster deployment, message queue and distributed configuration and other technical means to cope with high concurrency and high reliability requirements, and ensure the stable operation of enterprise-level systems.

[0076] Embodiment 2: based on the above embodiments, Figure 2 The structure diagram of the approval system suitable for multiple approval platforms provided by the embodiment of the present application comprises:

[0077] determining module 201 is configured to determine, according to the obtained approval initiation request, an approval platform for processing the approval initiation request;

[0078] The processing module 202 is configured to create an approval instance of the approval initiation request by calling an adapter of the approval platform through a unified approval flow interface; and generate notification content for the approval instance according to an approval template corresponding to the approval initiation request.

[0079] The notification module 203 is configured to send the notification content to an approval business associate and return an approval result of the approval business associate.

[0080] Further, the processing module 202 is specifically configured to route the approval initiation request to an adapter of the approval platform according to an approval type and / or a configuration identifier carried by the approval initiation request through a unified approval flow interface; and convert the approval initiation request in a unified format into an interface call and a data format corresponding to the approval platform by using the adapter of the approval platform, to obtain an approval instance of the approval initiation request.

[0081] Further, if the approval platform is a system built-in approval system, the adapter of the approval platform includes a flow arrangement engine.

[0082] The processing module 202 is specifically configured to route the approval initiation request to a flow arrangement engine of the system built-in approval system according to an approval type and / or a configuration identifier carried by the approval initiation request through a unified approval flow interface.

[0083] Further, the processing module 202 is specifically configured to map and replace approval information in the approval instance with a placeholder in an approval template corresponding to the approval initiation request, to generate notification content.

[0084] Further, the notification module 203 is specifically configured to trigger an approval result callback mechanism when identifying that an approval flow of the approval initiation request enters an end state, to asynchronously push an approval result of the approval business associate to a callback interface of the approval initiation request; use a pre-stored identity authentication token to authenticate the approval result; if the authentication is passed, return the approval result through the callback interface.

[0085] Further, the pre-verification module is configured to assemble parameters in the obtained approval initiation request into a preCommit object; call a pre-verification interface to pre-verify the preCommit object by using a pre-defined business rule service; and if the pre-verification is passed, create an approval flow for the approval initiation request.

[0086] Further, the notification module 203 is specifically configured to send the notification content to the approval business associate in a message queue, and return the approval result of the approval business associate.

[0087] Further, the approval system is deployed in a single form or in a cluster form.

[0088] Embodiment 3 Figure 3 A structural schematic diagram of an electronic device is provided in the embodiment of the application, and on the basis of the above embodiments, the electronic device in the embodiment of the application further comprises a processor 301, a communication interface 302, a memory 303 and a communication bus 304, wherein the processor 301, the communication interface 302 and the memory 303 complete mutual communication through the communication bus 304.

[0089] The memory 303 stores a computer program, and when the program is executed by the processor 301, the processor 301 executes the steps of the approval method suitable for the multi-approval platform in the above embodiments.

[0090] For the specific implementation process, refer to the above embodiments, and similar parts will not be described.

[0091] The communication bus mentioned in the above electronic device can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For the convenience of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or only one type of bus.

[0092] The communication interface 302 is used for communication between the above electronic device and other devices.

[0093] The memory can include a random access memory (RAM) and can also include a non-volatile memory (NVM), for example, at least one disk memory. Optionally, the memory can also be at least one storage device located away from the aforementioned processor.

[0094] The processor can be a general processor, including a central processing unit, a network processor (NP), etc.; can also be a digital signal processor (DSP), an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, etc.

[0095] In the embodiments, the processor can be a general processor, including a central processing unit, a network processor (NP), etc.; can also be a digital signal processor (DSP), an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, etc.

[0096] For specific implementation process, refer to the above embodiments, and similar parts are not described in detail.

[0097] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROMs, optical storage devices, etc.) containing computer-usable program code.

[0098] The present application is described with reference to flowcharts and / or block diagrams of the method, device (system), and computer program product according to the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing apparatus to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing apparatus produce a device implemented in the flowcharts and / or block diagrams. Figure 1 one or more flows and / or blocks Figure 1 an apparatus that performs the functions specified in the flow(s) or block(s).

[0099] These computer program instructions can also be stored in a computer-readable memory that can direct the computer or other programmable data processing apparatus to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including instruction apparatus, which implements the flowcharts and / or block diagrams. Figure 1 one or more flows and / or blocks Figure 1 an apparatus that performs the functions specified in the flow(s) or block(s).

[0100] These computer program instructions can also be loaded into a computer or other programmable data processing devices, so that a series of operational steps are performed on the computer or other programmable data processing devices to generate computer-implemented processes, thus the instructions executed on the computer or other programmable data processing devices provide processes for implementing the functions specified in the flowchart Figure 1 one or more flows and / or blocks Figure 1 one or more blocks or steps of the functions specified in the flowchart

[0101] Obviously, those skilled in the art can make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application belong to the scope of the claims of the present application and their equivalent technologies, the present application also intends to include these modifications and variations.

Claims

1. An approval method suitable for a multi-approval platform, characterized in that, The method comprises: According to the obtained approval initiation request, determine the approval platform for processing the approval initiation request; Through a unified approval flow interface, call the adapter of the approval platform to create an approval instance of the approval initiation request; According to the approval template corresponding to the approval initiation request, generate notification content for the approval instance; Send the notification content to the approval business associated person, and return the approval result of the approval business associated person; The method comprises: Through a unified approval flow interface, according to the approval type and / or configuration identifier carried by the approval initiation request, route the approval initiation request to the adapter of the approval platform, wherein the adapter of the approval platform comprises a third-party approval platform adapter or a flow arrangement engine of a built-in approval system of the system; Use the adapter of the approval platform to convert the approval initiation request in a unified format into interface calling and data format corresponding to the approval platform, and obtain the approval instance of the approval initiation request; Wherein, when encapsulating, independent adapter classes are written for different third-party approval platforms, each adapter implements a set of uniformly defined methods to ensure consistent calling process; the adapter is responsible for converting the internal unified format approval request into interface calling and data format required by the third-party platform; The method comprises: If the approval platform is a built-in approval system of the system, the adapter of the approval platform comprises a flow arrangement engine; through a unified approval flow interface, according to the approval type and / or configuration identifier carried by the approval initiation request, route the approval initiation request to the flow arrangement engine of the built-in approval system of the system; Or, through a unified approval flow interface, according to the approval type and / or configuration identifier carried by the approval initiation request, route the approval initiation request to the corresponding third-party approval platform adapter.

2. The method of claim 1, wherein, The method comprises: Map and replace the approval information in the approval instance with the placeholders in the approval template corresponding to the approval initiation request to generate notification content.

3. The method of claim 1, wherein, The method comprises: When identifying that the approval process of the approval initiation request enters an end state, trigger an approval result callback mechanism to asynchronously push the approval result of the approval business associated person to the callback interface of the approval initiation request; Use the pre-saved identity authentication token to authenticate the approval result; If the authentication is passed, return the approval result through the callback interface.

4. The method of claim 1, wherein, Before the method comprises: Assemble the parameters in the obtained approval initiation request into a preCommit object; The preCommit object is pre-verified by calling a pre-verification interface and using a predefined business rule service; If the pre-verification is passed, an approval process is created for the approval initiation request.

5. The method of claim 1, wherein, The method comprises the following steps: The method comprises the following steps:

6. The method according to any one of claims 1 to 5, wherein, The method is applied to an approval system, which is deployed in a single form or a cluster form.

7. An approval system suitable for a multi-approval platform, characterized in that, The system comprises: A determination module is configured to determine an approval platform for processing the approval initiation request according to the obtained approval initiation request; A processing module is configured to create an approval instance of the approval initiation request by calling an adapter of the approval platform through a unified approval flow interface, and generate notification content for the approval instance according to an approval template corresponding to the approval initiation request; A notification module is configured to send the notification content to an approval business associate and return an approval result of the approval business associate; The processing module is specifically configured to route the approval initiation request to an adapter of the approval platform according to an approval type and / or a configuration identifier carried by the approval initiation request through the unified approval flow interface, the adapter of the approval platform comprising a third-party approval platform adapter or a flow arrangement engine of a built-in approval system of the system; and convert the approval initiation request in a unified format into an interface call and a data format corresponding to the approval platform by using the adapter of the approval platform, to obtain an approval instance of the approval initiation request. The adapter is configured to write independent adapter classes for different third-party approval platforms when encapsulating, each adapter implements a set of uniformly defined methods to ensure consistent calling processes; and the adapter is responsible for converting an internal unified format approval request into an interface call and a data format required by a third-party platform. If the approval platform is a built-in approval system of the system, the adapter of the approval platform comprises a flow arrangement engine. The processing module is specifically configured to: If the approval platform is a built-in approval system of the system, the adapter of the approval platform comprises a flow arrangement engine; and the approval initiation request is routed to the flow arrangement engine of the built-in approval system of the system according to an approval type and / or a configuration identifier carried by the approval initiation request through the unified approval flow interface. Alternatively, the approval initiation request is routed to a corresponding third-party approval platform adapter according to an approval type and / or a configuration identifier carried by the approval initiation request through the unified approval flow interface.

8. An electronic device, comprising: The electronic device comprises a processor and a memory, the memory is used to store program instructions, and the processor is used to execute the computer program stored in the memory to implement the steps of the approval method applicable to multiple approval platforms according to any one of claims 1-6.

Images