Service request processing method and device, equipment and medium

Abstract

The invention relates to the technical field of service processing, and discloses a service request processing method and device, equipment and a medium, which can analyze a service request sent by a user side to obtain a target service identifier and request data carried in the service request. If it is determined that the request data does not include the approver information, searching at least one piece of corresponding approver information in pre-defined approver configuration information according to the target service identifier, and returning the information to the user side, so that the user side: selecting target approver information from the at least one piece of approver information, and generating a new service request carrying the target service identifier and the new request data. And receiving a new service request sent by the user side, and forwarding the new service request to an approval side corresponding to the target approver information for processing. According to the invention, normal business processing can be effectively guaranteed, and business processing scenes are enriched.

Description

Technical Field

[0001] The present invention relates to the technical field of business processing, and particularly to a method, device, equipment and medium for processing business requests. Background Art

[0002] With the development of computer science and technology, business processing technology has been continuously improved.

[0003] Currently, most Internet enterprises are equipped with business processing systems that match their own businesses to process daily office business and core business related to the enterprises, ensuring the normal processing and processing efficiency of the business.

[0004] For some business requests, users need to specify an approver when initiating a business request. If the user does not specify an approver, the related technology cannot effectively implement the processing of the business request. Summary of the Invention

[0005] The present invention provides a method, device, equipment and medium for processing business requests to solve the defect that in the related technology, if the user does not specify an approver in the business request, the related technology cannot effectively implement the processing of the business request, effectively ensuring the normal processing of the business and enriching the business processing scenarios.

[0006] In a first aspect, the present invention provides a method for processing a business request, including: Analyze the business request sent by the user terminal to obtain the target business identifier and request data carried in the business request; Determine whether the request data includes approver information; If it is determined that the request data does not include approver information, search for at least one corresponding approver information in the pre-defined approver configuration information according to the target business identifier; wherein, the approver configuration information includes the corresponding relationship between multiple business identifiers and multiple approver information; Return the at least one found approver information to the user terminal so that the user terminal: select target approver information from the at least one approver information, generate a new business request carrying the target business identifier and new request data, and the new request data includes the request data and the target approver information; Receive the new business request sent by the user terminal and forward the new business request to the approval terminal corresponding to the target approver information for processing.

[0007] Optionally, the determining whether the request data includes approver information includes: Determine whether the request data includes an approver field and a corresponding valid field value; If it is determined that the request data includes an approver field and a corresponding valid field value, it is determined that the request data includes approver information; If it is determined that the request data does not include an approver field or a corresponding valid field value, it is determined that the request data does not include approver information.

[0008] Optionally, the forwarding of the new service request to the approval end corresponding to the target approver information for processing includes: Parsing the new service request to obtain new request data carried in the new service request; If it is determined that the new request data includes the target approver information, determine the approval end corresponding to the target approver information, and forward the new service request to the approval end corresponding to the target approver information for processing.

[0009] Optionally, after determining whether the request data includes approver information, the method further includes: If it is determined that the request data includes approver information, directly forward the service request to the approval end corresponding to the approver information in the request data for processing.

[0010] Optionally, after forwarding the new service request to the approval end corresponding to the target approver information for processing, the method further includes: Receiving the approval result returned by the approval end and returning it to the user end.

[0011] In a second aspect, the present invention provides a service request processing device, including: A parsing unit for parsing a service request sent by a user end to obtain a target service identifier and request data carried in the service request; A judgment unit for judging whether the request data includes approver information; A searching unit for, if it is determined that the request data does not include approver information, searching for at least one corresponding approver information in pre-defined approver configuration information according to the target service identifier; wherein, the approver configuration information includes the corresponding relationship between multiple service identifiers and multiple approver information; A returning unit for returning the at least one searched approver information to the user end, so that the user end: selects target approver information from the at least one approver information, generates a new service request carrying the target service identifier and new request data, and the new request data includes the request data and the target approver information; A receiving unit for receiving the new service request sent by the user end; A forwarding unit, configured to forward the new service request to an approval terminal corresponding to the target approver information for processing.

[0012] Optionally, the determination unit is further configured to: Determine whether the request data includes an approver field and a corresponding valid field value; If it is determined that the request data includes an approver field and a corresponding valid field value, it is determined that the request data includes approver information; If it is determined that the request data does not include an approver field or a corresponding valid field value, it is determined that the request data does not include approver information.

[0013] Optionally, the forwarding unit is further configured to: Parse the new service request to obtain new request data carried in the new service request; If it is determined that the new request data includes the target approver information, determine an approval terminal corresponding to the target approver information, and forward the new service request to the approval terminal corresponding to the target approver information for processing.

[0014] In a third aspect, the present invention provides a computer device, including: a memory and a processor, which are communicatively connected to each other. The memory stores computer instructions, and the processor executes the computer instructions to execute the service request processing method according to the first aspect or any corresponding embodiment thereof.

[0015] In a fourth aspect, the present invention provides a computer-readable storage medium, on which computer instructions are stored. The computer instructions are used to cause a computer to execute the service request processing method according to the first aspect or any corresponding embodiment thereof.

[0016] The service request processing method, device, equipment and medium provided by the present invention can parse the service request sent by the client to obtain the target service identifier and request data carried in the service request. Determine whether the request data includes approver information. If it is determined that the request data does not include approver information, at least one corresponding approver information is searched in the pre-defined approver configuration information according to the target service identifier; wherein, the approver configuration information includes the corresponding relationship between multiple service identifiers and multiple approver information. Return the at least one searched approver information to the client, so that the client: select the target approver information from the at least one approver information, generate a new service request carrying the target service identifier and new request data, and the new request data includes the request data and the target approver information. Receive the new service request sent by the client and forward the new service request to the approval end corresponding to the target approver information for processing. The present invention can find matching approver information for the client and return it to the client when the client does not specify an approver in the service request, so that the client can select the approver information and initiate a new service request according to the selected approver information, effectively ensuring the normal processing of the service and enriching the service processing scenario. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the present invention or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0018] Figure 1 It is a flowchart of a service request processing method provided by an embodiment of the present invention; Figure 2 It is a flowchart of another service request processing method provided by an embodiment of the present invention; Figure 3 It is a flowchart of still another service request processing method provided by an embodiment of the present invention; Figure 4 It is a schematic structural diagram of a service request processing device provided by an embodiment of the present invention; Figure 5 It is a schematic structural diagram of a computer device provided by an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0019] To make the objectives, technical solutions, and advantages of the present invention clearer, the following will clearly and completely describe the technical solutions in the present invention in conjunction with the accompanying drawings in the present invention. Obviously, the described embodiments are some, but not all, of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present invention without creative efforts shall fall within the protection scope of the present invention.

[0020] The following will describe Figures 1 - 3 the business request processing method of the present invention.

[0021] As Figure 1 shown, the first business request processing method is proposed in this embodiment, and the method may include the following steps: S101. Analyze the business request sent by the client to obtain the target business identifier and request data carried in the business request.

[0022] It should be noted that this embodiment can be applied to a process service system.

[0023] Specifically, this embodiment can receive the business request sent by the client, and then analyze the business request to obtain the target business identifier and request data carried in the business request.

[0024] Among them, the target business identifier can be used to identify the business type. The request data is the relevant data necessary for making a business request and performing business processing, and it may specifically include the user name, IP address, request timestamp, authentication information, etc.

[0025] S102. Determine whether the request data includes approver information.

[0026] Among them, the approver information can be identifiers such as the approver's name and job number.

[0027] Specifically, this embodiment can further analyze the request data to find out whether the request data includes approver information.

[0028] Optionally, in the second business request processing method proposed in this embodiment, step S102 may include steps S1021, S1022, and S1023. Among them: S1021. Determine whether the request data includes an approver field and the corresponding valid field value.

[0029] Among them, the valid field value is a non-empty value and is not a field value such as null, undefined, and empty string.

[0030] S1022. If it is determined that the request data includes an approver field and the corresponding valid field value, it is determined that the request data includes approver information.

[0031] Specifically, in this embodiment, when it is determined that the request data includes an approver field and corresponding valid field values, it can be determined that the request data includes approver information.

[0032] S1023. If it is determined that the request data does not include an approver field or the corresponding valid field value, it is determined that the request data does not include approver information.

[0033] Specifically, in this embodiment, when it is determined that the request data does not include an approver field and the corresponding valid field values, it can be determined that the request data does not include approver information.

[0034] S103. If it is determined that the request data does not include approver information, at least one corresponding approver information is found in the pre-defined approver configuration information according to the target service identifier; wherein, the approver configuration information includes the corresponding relationship between multiple service identifiers and multiple approver information.

[0035] Specifically, in this embodiment, when it is determined that the request data does not include approver information, the pre-defined approver configuration information can be retrieved first. The approver configuration information includes the corresponding relationship between multiple service identifiers and multiple approver information. It should be noted that the corresponding relationship between the service identifier and the approver information can be a one-to-many relationship, that is, one service identifier can correspond to multiple approver information.

[0036] Specifically, in this embodiment, one or more matching approver information can be found in the approver configuration information according to the target service identifier.

[0037] S104. Return the at least one approver information found to the client, so that the client: selects the target approver information from the at least one approver information, generates a new service request carrying the target service identifier and the new request data, and the new request data includes the request data and the target approver information.

[0038] Specifically, in this embodiment, all the approver information found according to the target service identifier can be returned to the client. At this time, the client can select the target approver information suitable for processing the current service request from all the received approver information. Then, the client can generate new request data according to the target approver information, and generate a new service request according to the new request data and the target service identifier.

[0039] S105. Receive the new service request sent by the client.

[0040] Specifically, in this embodiment, after the client generates a new service request, the new service request sent by the client can be received.

[0041] S106. Forward the new service request to the approval terminal corresponding to the target approver information for processing.

[0042] Specifically, after receiving the new service request sent by the user terminal in this embodiment, the new service request can be forwarded to the approval terminal corresponding to the target approver information for processing.

[0043] Optionally, as Figure 2 shown, in the third service request processing method proposed in this embodiment, step S106 may include steps S201, S202, and S203. Among them: S201. Analyze the new service request to obtain the new request data carried in the new service request; S202. If it is determined that the new request data includes the target approver information, determine the approval terminal corresponding to the target approver information.

[0044] S203. Forward the new service request to the approval terminal corresponding to the target approver information for processing.

[0045] It can be understood that after receiving the new service request in this embodiment, the new service request can also be analyzed to obtain the target service identifier and new request data carried in the new service request, and it is judged whether the new request data includes the approver information. When it is determined that the new request data includes the target approver information, the approval terminal corresponding to the target approver information can be found, and the new service request can be forwarded to the approval terminal corresponding to the target approver information.

[0046] Optionally, in other service request processing methods proposed in this embodiment, after step S106, it may further include: Receiving the approval result returned by the approval terminal and returning it to the user terminal.

[0047] Specifically, after receiving the new service request, the approval terminal can perform corresponding processing based on the new service request to obtain the approval result, and the approval result can be returned to the user terminal through the process service system.

[0048] The service request processing method proposed in this embodiment can parse the service request sent by the client to obtain the target service identifier and request data carried in the service request. Determine whether the request data includes approver information. If it is determined that the request data does not include approver information, at least one approver information corresponding thereto is found in the pre-defined approver configuration information according to the target service identifier; wherein, the approver configuration information includes the corresponding relationship between multiple service identifiers and multiple approver information. Return the at least one approver information found to the client so that the client can: select target approver information from the at least one approver information, generate a new service request carrying the target service identifier and new request data, and the new request data includes the request data and the target approver information. Receive the new service request sent by the client and forward the new service request to the approval end corresponding to the target approver information for processing. This embodiment can find matching approver information for the client and return it to the client when the client does not specify an approver in the service request, so that the client can select approver information and initiate a new service request according to the selected approver information, effectively ensuring the normal processing of the service and enriching the service processing scenario.

[0049] Based on Figure 1 , this embodiment proposes a fourth service request processing method, which may further include, after the above step S102: If it is determined that the request data includes approver information, directly forward the service request to the approval end corresponding to the approver information in the request data for processing.

[0050] Specifically, in this embodiment, when it is determined that the request data of the service request sent by the client includes approver information, the approval end corresponding to the approver information can be found, and the service request can be directly sent to the approval end for processing.

[0051] The service request processing method proposed in this embodiment can directly process the service request when the service request sent by the client includes approver information, ensuring the normal processing of the service request.

[0052] The implementation method of the process service approver configuration in the related art generally includes the following content. Set the process definition according to the Business Process Modeling Notation (BPMN), set the roles used in the process and bind relevant personnel to the roles, and bind the process nodes in the process definition to the roles used in the process. This method has a simple structure and is easy to maintain. However, it cannot meet the scenario where the user selects one from multiple approvers according to business needs. Moreover, there are often differences in different process service implementation methods, and when the process system is switched, this processing often needs to be redefined and implemented.

[0053] To solve the above problems, in this embodiment, the process node for finding approvers in the process service system can be encapsulated into a Java JAR package component. The process node is bound to the process role and related approvers for processing, encapsulated into an independent function, and provided for different process service systems to use. This makes the function reusable and improves development efficiency.

[0054] This embodiment can establish a process handler search service and an integration component (JAR package) for process system integration. The process handler search service is used to provide a service for finding process handlers according to process information. The integration component facilitates the process system to quickly integrate and use the process search service, and contains the processing logic for obtaining handler information. Among them, the process handler search service mainly provides the following functions: process information configuration - process definition and node configuration table, role and personnel configuration - process role and personnel configuration table, and binding configuration of process information and role and personnel.

[0055] This embodiment can also set up a process system integration component (JAR package), which mainly includes a predefined web filter to determine whether the request is a process-related request such as process submission and review. When the process system submits a request, it is necessary to pass in process definition information, next node information, handler information, etc.

[0056] Check whether there is handler information in the web filter. If there is handler information, skip the filter and enter the process processing of the process system. If there is no handler information, call the process approver search service according to the submitted request information to query the handler information. After querying the handler information, return the handler information to the process system.

[0057] Based on Figure 1 , this embodiment proposes a fifth method for processing business requests, which may include the following steps: Build a process handler search service to provide functions such as process information configuration, role and personnel configuration, binding configuration of process information and role and personnel, and a process handler search interface service.

[0058] The integration component (JAR package) mainly includes a predefined web filter to determine whether the request is a process-related request such as process submission and review.

[0059] When the process system submits a request, it is necessary to pass in process definition information, next node information, handler information, etc. Check whether there is approver information in the web filter.

[0060] If there is approver information, skip the filter and enter the process processing of the process system.

[0061] If there is no approver information, based on the submitted request information, call the process approver search service to query the approver information. After querying the approver information, return the approver information to the process service system.

[0062] Deploy the business Java-based Web process system, install the integration components (jar packages), configure the web filter and enable the filter, and introduce the dependencies required in the jar.

[0063] Deploy the business process in the Web process system, and perform process-related configurations in the process handler search service, including information configuration, role personnel configuration, and process information and role personnel binding configuration.

[0064] The Java Web process system processes the user request through the Web filter, calls the process handler search service, and returns the approver information.

[0065] The Java Web process system reforms the submission process service processing process, receives the returned approver information from the web filter, and returns it to the client for selection and processing. After the client selects and processes it, the selected approver information is obtained. Then submit the processing again.

[0066] The integration component (Jar package) determines whether the user has set the approver, and passes the request to the Web process system for processing.

[0067] As Figure 3 shown, in the sixth business request processing method proposed in this embodiment, the following steps may be included: Integrate the process handler search service with the integration component (jar) to form a process handler search component (jar package). It mainly includes process information configuration, role personnel configuration, process information and role personnel binding configuration functions, and a process handler search interface service.

[0068] Pre-define a web filter to determine whether the request is a process-related request such as process submission or review. When the process system submits a request, it is necessary to pass in process definition information, next node information, approver information, etc. Check whether there is approver information in the web filter.

[0069] If there is approver information, skip the filter and enter the process system process processing. If there is no approver information, based on the submitted request information, call the process approver search interface to query the approver information. After querying the approver information, return the approver information to the process service system.

[0070] Deploy the business Java-based Web process system, install the process handler search component (jar package) in it, configure the web filter and enable the filter, and introduce the dependencies required in the jar.

[0071] The Web process system in Java, according to the user request, after being processed by the Web filter, calls the process handler lookup interface and returns the process handler information.

[0072] The Web process system in Java transforms the submission process service handling process, receives the returned handler information from the web filter, and returns it for the user to select for processing. After the user selects the processing, the selected person's information is submitted again for processing.

[0073] The integration component (Jar package) determines whether the user has set the handler and passes the request to the Web process system for processing. For the business request processing method proposed in this embodiment, the process service can call the process handler lookup service through the integration component (Jar package) to obtain the handler information, and this handler information can be returned to the user in the form of a list for the user to select according to the situation. This embodiment can adopt the method of process components, improving the reuse of functions. When multiple different process systems are called, this part of the content does not need to be re-developed and defined.

[0074] As Figure 4 shown, this embodiment proposes a business request processing device, which may include: A parsing unit 401, configured to parse the business request sent by the user terminal to obtain the target business identifier and request data carried in the business request; A determination unit 402, configured to determine whether the request data includes approver information; A lookup unit 403, configured to, if it is determined that the request data does not include approver information, look up at least one corresponding approver information in the pre-defined approver configuration information according to the target business identifier; wherein, the approver configuration information includes the corresponding relationship between multiple business identifiers and multiple approver information; A return unit 404, configured to return the at least one approver information found to the user terminal, so that the user terminal: selects the target approver information from the at least one approver information, generates a new business request carrying the target business identifier and new request data, and the new request data includes the request data and the target approver information; A receiving unit 405, configured to receive the new business request sent by the user terminal; A forwarding unit 406, configured to forward the new business request to the approval terminal corresponding to the target approver information for processing.

[0075] It should be noted that the processing processes and the beneficial effects brought by the parsing unit 401, the determination unit 402, the lookup unit 403, the return unit 404, the receiving unit 405, and the forwarding unit 406 can be respectively referred to Figure 1Steps S101 to S106 therein will not be elaborated further.

[0076] Optionally, the determination unit 402 is further configured to: Determine whether the request data includes an approver field and a corresponding valid field value; If it is determined that the request data includes an approver field and a corresponding valid field value, it is determined that the request data includes approver information; If it is determined that the request data does not include an approver field or a corresponding valid field value, it is determined that the request data does not include approver information.

[0077] Optionally, the forwarding unit 406 is further configured to: Parse the new service request to obtain the new request data carried in the new service request; If it is determined that the new request data includes target approver information, determine the approval end corresponding to the target approver information, and forward the new service request to the approval end corresponding to the target approver information for processing.

[0078] Optionally, the above device further includes: A first processing unit, configured to directly forward the service request to the approval end corresponding to the approver information in the request data for processing after determining whether the request data includes approver information.

[0079] Optionally, the above device further includes: A second processing unit, configured to receive the approval result returned by the approval end after forwarding the new service request to the approval end corresponding to the target approver information for processing, and return it to the user end.

[0080] The service request processing device proposed in this embodiment can parse the service request sent by the client to obtain the target service identifier and request data carried in the service request. It determines whether the request data includes approver information. If it is determined that the request data does not include approver information, at least one corresponding approver information is found in the pre-defined approver configuration information according to the target service identifier; wherein, the approver configuration information includes the corresponding relationship between multiple service identifiers and multiple approver information. The at least one found approver information is returned to the client so that the client can: select the target approver information from the at least one approver information, generate a new service request carrying the target service identifier and new request data, and the new request data includes the request data and the target approver information. The new service request sent by the client is received and forwarded to the approval end corresponding to the target approver information for processing. This embodiment can find matching approver information for the client and return it to the client when the client does not specify an approver in the service request, so that the client can select the approver information and initiate a new service request according to the selected approver information, effectively ensuring the normal processing of the service and enriching the service processing scenario.

[0081] The service request processing device in this embodiment is presented in the form of functional units. Here, the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and a memory that execute one or more software or fixed programs, and / or other devices that can provide the above functions.

[0082] An embodiment of the present invention also provides a computer device having the above Figure 4 shown service request processing device.

[0083] Please refer to Figure 5 , a schematic structural diagram of a computer device provided by an alternative embodiment of the present invention. The computer device includes: one or more processors 10, a memory 20, and an interface for connecting each component, including a high-speed interface and a low-speed interface. Each component communicates with each other using different buses and can be installed on a common motherboard or installed in other ways as needed. The processor can process instructions executed within the computer device, including instructions stored in the memory or on the memory to display graphical information of the GUI on an external input / output device (such as a display device coupled to the interface).

[0084] In some alternative embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a set of blade servers, or a multi-processor system).Figure 5 Take a processor 10 as an example.

[0085] The processor 10 can be a central processing unit, a network processor, or a combination thereof. Among them, the processor 10 can further include a hardware chip. The above-mentioned hardware chip can be an application-specific integrated circuit, a programmable logic device, or a combination thereof. The above-mentioned programmable logic device can be a complex programmable logic device, a field-programmable gate array, a generic array logic, or any combination thereof.

[0086] Among them, the memory 20 stores instructions that can be executed by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiments.

[0087] The memory 20 can include a program storage area and a data storage area. Among them, the program storage area can store an operating system and application programs required for at least one function. The data storage area can store data created according to the use of the computer device, etc.

[0088] In addition, the memory 20 can include a high-speed random access memory, and can also include a non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state storage devices. In some alternative embodiments, the memory 20 can optionally include a memory remotely set relative to the processor 10, and these remote memories can be connected to the computer device through a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.

[0089] The memory 20 can include a volatile memory, such as a random access memory. The memory can also include a non-volatile memory, such as a flash memory, a hard disk, or a solid-state drive. The memory 20 can also include a combination of the above-mentioned types of memories.

[0090] The computer device further includes a communication interface 30 for the computer device to communicate with other devices or communication networks.

[0091] The embodiments of the present invention also provide a computer-readable storage medium. The method according to the embodiments of the present invention can be implemented in hardware, firmware, or be implemented as computer code that can be recorded on a storage medium, or be implemented by downloading through a network and originally stored in a remote storage medium or a non-transitory machine-readable storage medium and will be stored in a local storage medium, so that the method described herein can be stored on such a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware for software processing. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only memory, a random access memory, a flash memory, a hard disk, or a solid-state drive, etc.; further, the storage medium can also include a combination of the above-mentioned types of memories.

[0092] It can be understood that a computer, a processor, a microprocessor controller or programmable hardware includes a storage component that can store or receive software or computer code, and when the software or computer code is accessed and executed by the computer, the processor or the hardware, the methods shown in the above embodiments are implemented.

[0093] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for processing a business request, characterized in that: include: Parsing the service request sent by the user end to obtain the target service identifier and request data carried in the service request; Determining whether the request data includes approver information; If it is determined that the request data does not include the approver information, then searching for at least one corresponding approver information in the predefined approver configuration information according to the target business identifier; wherein the approver configuration information includes the correspondence between multiple business identifiers and multiple approver information; The at least one approver information found is returned to the user end, so that the user end: selects target approver information from the at least one approver information, generates a new service request carrying the target service identifier and new request data, wherein the new request data includes the request data and the target approver information; The new service request sent by the user end is received, and the new service request is forwarded to the approval end corresponding to the target approver information for processing.

2. The method according to claim 1, characterized in that The determining whether the request data includes approver information includes: Determine whether the request data includes an approver field and a corresponding valid field value; If it is determined that the request data includes an approver field and a corresponding valid field value, then it is determined that the request data includes approver information; If it is determined that the request data does not include the approver field or the corresponding valid field value, it is determined that the request data does not include the approver information.

3. The method according to claim 1, characterized in that The forwarding of the new business request to the approval end corresponding to the target approver information for processing includes: Parsing the new service request to obtain new request data carried in the new service request; If it is determined that the new request data includes the target approver information, the approval end corresponding to the target approver information is determined, and the new business request is forwarded to the approval end corresponding to the target approver information for processing.

4. The method according to claim 1, characterized in that: After determining whether the request data includes approver information, the method further includes: If it is determined that the request data includes the approver information, the business request is directly forwarded to the approval end corresponding to the approver information in the request data for processing.

5. The method according to claim 1, characterized in that After forwarding the new business request to the approval end corresponding to the target approver information for processing, the method further includes: The approval result returned by the approval end is received and returned to the user end.

6. A service request processing device, characterized in that: include: A parsing unit, used for parsing the service request sent by the user end to obtain the target service identifier and request data carried in the service request; A judging unit, used to judge whether the request data includes the approver information; A search unit, configured to search for at least one corresponding approver information in predefined approver configuration information according to the target business identifier if it is determined that the request data does not include approver information; wherein the approver configuration information includes a correspondence between multiple business identifiers and multiple approver information; A returning unit, used for returning the at least one approver information found to the user end, so that the user end: selects target approver information from the at least one approver information, generates a new service request carrying the target service identifier and new request data, wherein the new request data includes the request data and the target approver information; A receiving unit, configured to receive the new service request sent by the user terminal; The forwarding unit is used to forward the new business request to the approval end corresponding to the target approver information for processing.

7. The device according to claim 6, characterized in that The judgment unit is also used for: Determine whether the request data includes an approver field and a corresponding valid field value; If it is determined that the request data includes an approver field and a corresponding valid field value, then it is determined that the request data includes approver information; If it is determined that the request data does not include the approver field or the corresponding valid field value, it is determined that the request data does not include the approver information.

8. The device according to claim 6, characterized in that The forwarding unit is also used to: Parsing the new service request to obtain new request data carried in the new service request; If it is determined that the new request data includes the target approver information, the approval end corresponding to the target approver information is determined, and the new business request is forwarded to the approval end corresponding to the target approver information for processing.

9. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the service request processing method according to any one of claims 1 to 5 by executing the computer instructions.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the service request processing method according to any one of claims 1 to 5.

Images