Business handling method, device, electronic device and storage medium

Abstract

The embodiment of the present invention provides a method, device, electronic device and storage medium for handling business, the method comprising: pre-collecting multiple interactive actions for completing different sub-processes in a business, and converting the multiple interactive actions into corresponding multiple action chain sub-scripts; then splicing the multiple action chain sub-scripts into an action chain script for different businesses; when a request for a target business is received, the corresponding target action chain script can be determined in response to the request, and the target action chain script can be executed; then, based on the executed target action chain script, a business acceptance report corresponding to the target business is output. Through the embodiment of the present invention, a low-cost automated business handling function is realized; compared with secondary development of a dedicated batch acceptance program directly based on the core software code, the embodiment of the present invention can reduce costs by generating action chain scripts for different businesses.

Description

Technical Field

[0001] The present invention relates to the technical field of data processing, and in particular to a business handling method, device, electronic device and storage medium. Background Art

[0002] A CRM (Customer Relationship Management) system refers to a business software system that uses computers to automatically analyze sales, marketing, customer service, and support the above business processes.

[0003] Currently, telecom operators' CRM systems have automated acceptance capabilities for certain services. This is achieved by developing a dedicated batch acceptance program based on the core CRM system software code. The backend completes a series of pre-configured batch process actions, including generating batch orders, sending network element instructions, and updating databases with archive data. This solution, which relies on secondary iteration of the core system's underlying code to implement batch services, has the following drawbacks:

[0004] 1. The program development cycle is long and the cost is high;

[0005] 2. Each telecommunications service acceptance process is different and the code cannot be reused;

[0006] 3. During the program operation, the number of orders is high in a short period of time, which puts pressure on downstream systems such as the system database, service activation system, network element equipment and business platform, easily causing a backlog of work orders and affecting the normal business operations of the business hall. Summary of the Invention

[0007] In view of the above problems, a method, device, electronic device and storage medium for handling a business are proposed to overcome the above problems or at least partially solve the above problems, including:

[0008] A business handling method, characterized in that the method includes:

[0009] Collect multiple interactive actions for completing different sub-processes in the business, and convert the multiple interactive actions into corresponding multiple action chain sub-scripts;

[0010] Splicing the multiple action chain sub-scripts into action chain scripts for different businesses;

[0011] In response to a request from a target service, determining a corresponding target action chain script and executing the target action chain script;

[0012] Based on the executed target action chain script, a business acceptance report corresponding to the target business is output.

[0013] Optionally, the target action chain script includes at least one target action chain sub-script, and executing the target action chain script includes:

[0014] According to the correspondence between the preset action chain scripts and the rules, determine the target rules corresponding to each target action chain script;

[0015] During the execution of a target action chain script, detect whether the corresponding target rule is triggered;

[0016] If the corresponding target rule is triggered, the corresponding rule verification result is stored as a tracking log, and the next target action chain script is executed;

[0017] If the corresponding target rule is not triggered, the next target action chain script is executed.

[0018] Optionally, before outputting the service acceptance report corresponding to the target service, the method further includes:

[0019] The tracking log is written into the business acceptance report.

[0020] Optionally, the method further comprises the step of establishing the corresponding relationship:

[0021] For an action chain script, set a corresponding rule strategy;

[0022] For the rule strategy, set one or more corresponding rules;

[0023] A correspondence between the action chain script, the rule policy, and the corresponding one or more rules is established.

[0024] Optionally, the collection is used to complete multiple interactive actions of different sub-processes in the business, including:

[0025] Record the acceptance segments of the sub-processes for manually accepting each business;

[0026] According to the acceptance fragments, interactive actions for completing different sub-processes in each business are determined.

[0027] Optionally, converting the plurality of interactive actions into corresponding plurality of action chain sub-scripts includes:

[0028] Encapsulating the multiple interactive actions into corresponding instruction sets;

[0029] According to the instruction set, a plurality of action chain sub-scripts corresponding to the plurality of interactive actions are generated.

[0030] An embodiment of the present invention further provides a service processing device, the device comprising:

[0031] A collection module, configured to collect multiple interactive actions for completing different sub-processes in a business, and convert the multiple interactive actions into corresponding multiple action chain sub-scripts;

[0032] A splicing module, used to splice the multiple action chain sub-scripts into action chain scripts for different services;

[0033] An execution module, configured to determine a corresponding target action chain script in response to a request of a target business, and execute the target action chain script;

[0034] The output module is used to output a business acceptance report corresponding to the target business based on the executed target action chain script.

[0035] Optionally, the target action chain script includes at least one target action chain sub-script, and the execution module includes:

[0036] The rule determination submodule is used to determine the target rule corresponding to each target action chain subscript based on the correspondence between the preset action chain subscript and the rule;

[0037] The detection submodule is used to detect whether the corresponding target rule is triggered during the execution of a target action chain subscript;

[0038] The first execution sub-step is used to store the corresponding rule verification result as a tracking log if the corresponding target rule is triggered, and execute the next target action chain script;

[0039] The second execution sub-step is used to execute the next target action chain sub-script if the corresponding target rule is not triggered.

[0040] Optionally, the device further comprises:

[0041] The log writing module is used to write the tracking point log into the business acceptance report before outputting the business acceptance report corresponding to the target business.

[0042] Optionally, the device further comprises:

[0043] The rule establishment module is used to set a corresponding rule strategy for an action chain script; set one or more corresponding rules for the rule strategy; and establish a correspondence between the action chain script, the rule strategy and the corresponding one or more rules.

[0044] Optionally, the collection module includes:

[0045] Recording submodule, users record the acceptance segments of the sub-processes of manually accepting various businesses;

[0046] The interaction action determination submodule is used to determine the interaction actions for completing different sub-processes in each business according to the acceptance fragment.

[0047] Optionally, the collection module includes:

[0048] An encapsulation submodule, configured to encapsulate the plurality of interactive actions into corresponding instruction sets;

[0049] The sub-script generation sub-module is used to generate a plurality of action chain sub-scripts corresponding to the plurality of interactive actions according to the instruction set.

[0050] An embodiment of the present invention further provides an electronic device, comprising a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program implements the above-mentioned business processing method when executed by the processor.

[0051] An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the method for handling the above business is implemented.

[0052] The embodiments of the present invention have the following advantages:

[0053] In an embodiment of the present invention, multiple interactive actions for completing different sub-processes in a business can be collected in advance, and the multiple interactive actions can be converted into corresponding multiple action chain sub-scripts; then the multiple action chain sub-scripts are spliced ​​into action chain scripts for different businesses; when a request for a target business is received, the corresponding target action chain script can be determined in response to the request, and the target action chain script can be executed; then, based on the executed target action chain script, a business acceptance report corresponding to the target business is output. Through the embodiment of the present invention, a low-cost business automation processing function is achieved; compared with directly developing a dedicated batch acceptance program based on the core software code, the embodiment of the present invention can reduce costs by generating action chain scripts for different businesses; and because the action chain sub-script is only for sub-processes, if different businesses have the same sub-processes, the corresponding action chain sub-scripts can also be used universally. In addition, by using additional scripts to handle business, it is possible to avoid a large pressure on the system when the number of businesses is high in a short period of time, thereby avoiding affecting the business processing of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] In order to more clearly illustrate the technical solution of the present invention, the following briefly introduces the drawings required for use in the description of the present invention. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0055] Figure 1 This is a flowchart of a method for handling a business according to an embodiment of the present invention;

[0056] Figure 2 is a flowchart of another method for predicting optical module performance according to an embodiment of the present invention;

[0057] Figure 3 This is a schematic diagram of a partially repackaged RPA robot instruction set according to an embodiment of the present invention;

[0058] Figure 4 is a schematic diagram of an example code according to an embodiment of the present invention;

[0059] Figure 5 This is a schematic diagram of a process for generating an action chain script according to an embodiment of the present invention;

[0060] Figure 6 This is an example diagram of multiple sub-processes of a business acceptance process, corresponding CRM pages, and corresponding action chains in an embodiment of the present invention;

[0061] Figure 7 This is a schematic diagram of the relationship between an action chain script, a rule strategy, and rules according to an embodiment of the present invention;

[0062] Figure 8 This is a schematic diagram of a detection rule process according to an embodiment of the present invention;

[0063] Figure 9 This is a schematic diagram of an RPA robot automated acceptance process according to an embodiment of the present invention;

[0064] Figure 10 This is a schematic diagram of an RPA robot task workflow according to an embodiment of the present invention;

[0065] Figure 11 This is a schematic diagram of a scenario of a method for handling a service according to an embodiment of the present invention;

[0066] Figure 12 This is a structural block diagram of a service processing device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0067] To make the above-mentioned objects, features, and advantages of the present invention more clearly understood, the present invention is further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the embodiments described are only a portion of the embodiments of the present invention, not all of them. All other embodiments derived by persons of ordinary skill in the art based on the embodiments of the present invention without inventive effort are also within the scope of protection of the present invention.

[0068] Reference Figure 1 , which shows a flowchart of a method for handling a business according to an embodiment of the present invention, which may include the following steps:

[0069] Step 101: Collect multiple interactive actions for completing different sub-processes in the business, and convert the multiple interactive actions into corresponding multiple action chain sub-scripts.

[0070] In actual applications, a business may consist of multiple different sub-processes; different businesses may have the same sub-processes, such as opening a browser, closing a window, maximizing a window, etc.

[0071] When a user needs to complete a business, they need to perform interactive actions on the terminal for different sub-processes. In this case, the user's interactive actions in different sub-processes during the business can be collected in advance, for example: the interactive action of clicking the right mouse button and the interactive action of double-clicking the left mouse button.

[0072] After collecting the interaction actions for different sub-processes, a corresponding relationship between the sub-processes and the interaction actions can be established.

[0073] Then, multiple interactive actions can be converted into one or more action chain sub-scripts that can be automatically executed; each action chain sub-script can correspond to a sub-process.

[0074] As an example, each action chain sub-script can be used to simulate the manual operation of the corresponding sub-process, such as clicking a mouse, clicking a key on a keyboard, etc., which is not limited in this embodiment of the present invention.

[0075] Step 102: Combine multiple action chain scripts into action chain scripts for different businesses.

[0076] After obtaining multiple action chain sub-scripts, you can splice the multiple action chain sub-scripts according to the order of the sub-processes in the business, so as to obtain action chain scripts for completing different businesses.

[0077] For example: the action chain sub-scripts include "a", "b", "c", "d", "e", "f", and "g", which correspond to sub-processes "A", "B", "C", "D", "E", "F", and "G" respectively; the sub-process sequence of business 1 is C→A→D→E→G, then the action chain script "c→a→d→e→g" can be generated for business 1.

[0078] As an example, after determining the action chain scripts for different services, a correspondence between the services and the action chain scripts may be established, so that the action chain script corresponding to the current service to be processed may be quickly determined based on the correspondence.

[0079] Generating action chain scripts for different businesses can significantly reduce costs compared to developing dedicated batch acceptance programs directly based on the core software code. Furthermore, since action chain scripts are specific to sub-processes, the corresponding action chain scripts can be used interchangeably across different businesses with the same sub-processes. Furthermore, using additional scripts to handle business operations can avoid significant system pressure when a high number of businesses are concurrently processing business transactions for a short period of time, thereby preventing the impact on the system's business processing.

[0080] Step 103: In response to the request of the target service, determine the corresponding target action chain script and execute the target action chain script.

[0081] When a user wants to handle a target service, he or she can first generate a request for the target service on the client side. The request may include the service the user wants to handle, the user's information, etc.

[0082] In response to the request of the target business, a corresponding target action chain script may be determined first, and then the target action chain script may be executed to simulate manual mouse and keyboard operations to complete one or more sub-processes corresponding to the target business.

[0083] Generating action chain scripts for different businesses can significantly reduce costs compared to developing dedicated batch acceptance programs directly based on the core software code. Furthermore, since action chain scripts are specific to sub-processes, the corresponding action chain scripts can be used interchangeably across different businesses with the same sub-processes. Furthermore, using additional scripts to handle business operations can avoid significant system pressure when a high number of businesses are concurrently processing business transactions for a short period of time, thereby preventing the impact on the system's business processing.

[0084] Step 104: Based on the executed target action chain script, a business acceptance report corresponding to the target business is output.

[0085] After the target action chain script is executed, the system may output a business acceptance report corresponding to the target business in response to the request of the target business and the operation executed by the target action chain script.

[0086] In an embodiment of the present invention, multiple interactive actions for completing different sub-processes in a business can be collected in advance, and the multiple interactive actions can be converted into corresponding multiple action chain sub-scripts; then the multiple action chain sub-scripts are spliced ​​into action chain scripts for different businesses; when a request for a target business is received, the corresponding target action chain script can be determined in response to the request, and the target action chain script can be executed; then, based on the executed target action chain script, a business acceptance report corresponding to the target business is output. Through the embodiment of the present invention, a low-cost business automation processing function is achieved; compared with directly developing a dedicated batch acceptance program based on the core software code, the embodiment of the present invention can reduce costs by generating action chain scripts for different businesses; and because the action chain sub-script is only for sub-processes, if different businesses have the same sub-processes, the corresponding action chain sub-scripts can also be used universally. In addition, by using additional scripts to handle business, it is possible to avoid a large pressure on the system when the number of businesses is high in a short period of time, thereby avoiding affecting the business processing of the system.

[0087] Reference Figure 2 , which shows a flowchart of a method for handling a business according to an embodiment of the present invention, which may include the following steps:

[0088] Step 201: Record the acceptance segments of the sub-processes for manually accepting each business.

[0089] In actual applications, the handling process of different businesses can be recorded to obtain acceptance fragments for the sub-processes of each business; the acceptance fragments can be in the form of video, image, or text, which is not limited in the embodiment of the present invention.

[0090] As an example, the business may be a business handled in a CRM system; the acceptance segment may be recorded with the help of a Selenium IDE component.

[0091] Step 202: Determine the interactive actions for completing different sub-processes in each business based on the acceptance fragment.

[0092] For each acceptance fragment, the interaction action corresponding to the sub-process in the completed business can be obtained; for example: each acceptance fragment can be identified to determine the corresponding sub-process and the corresponding interaction action; the interaction action can refer to the operation performed by the user when completing the sub-process.

[0093] Step 203: Encapsulate multiple interactive actions into corresponding instruction sets.

[0094] After obtaining the interaction actions corresponding to different sub-processes, the interaction actions can be encapsulated into corresponding instruction sets.

[0095] For example, the automation methods in the open-source Web automation component Selenium can be repackaged to quickly obtain the RPA (Robotic Process Automation) robot instruction set. The Selenium open-source component provides developers with an open WebDriver driver interface for current mainstream browsers, which provides a foundation for the rapid development and implementation of Web-based automation RPA software robots.

[0096] like Figure 3 , shows part of the RPA robot instruction set after secondary packaging in an embodiment of the present invention; some sample codes can be as follows Figure 4 As shown (implemented in Python); multiple action chain scripts can form an RPA robot.

[0097] Table 1 shows the classification of some instruction sets according to the embodiment of the present invention, and the corresponding instruction functions of the secondary encapsulation Selenium method.

[0098] Table 1:

[0099]

[0100] As an example, the instruction set may be encapsulated into a tool interface for Web automation operations.

[0101] Step 204: Generate multiple action chain sub-scripts corresponding to the multiple interactive actions according to the instruction set.

[0102] After obtaining the instruction set corresponding to each interactive action, the action chain script corresponding to each interactive action can be generated according to the instruction set. After obtaining the action chain script, the ID of each action chain script can be marked.

[0103] like Figure 5 , you can first record each acceptance segment and get the corresponding action chain script.

[0104] After generating an action chain script, you can train it. For example, you can simulate real-world acceptances in a CRM system test environment. Through repeated testing of both normal and abnormal cases, you can verify the stability and accuracy of the action chain script's automated acceptance, thereby improving the accuracy and success rate of automated acceptance by RPA robots.

[0105] After the training of multiple dimensional indicators such as success rate, average processing time for a single business, and maximum concurrent number meets the standards, the process training can be ended and the version can be solidified and stored in the database.

[0106] As an example, you can use Python to write the code of an executable action chain script. In one example, the example of the "locate customer" action chain script can be as follows:

[0107] wait=WebDriverWait(RPA_Driver.driver,30,0.5)

[0108] wait.until(EC.element_to_be_clickable((By.XPATH,' / html / body / div[1] / div[4] / div[1] / ul / li / a / i')))

[0109] RPA_Driver.locator('xpath',' / html / body / div[1] / div[4] / div[1] / ul / li / a / i').click()

[0110] wait.until(EC.element_to_be_clickable((By.XPATH,' / / *[@id="main1"]')))

[0111] RPA_Driver.locator('xpath',' / / *[@id="main1"]').click()

[0112] wait.until(EC.element_to_be_clickable((By.XPATH,' / html / body / div[1] / div[1] / div / div / div / div[2] / div[1] / a[1]')))

[0113] RPA_Driver.locator('xpath',' / html / body / div[1] / div[1] / div / div / div / div[2] / div[1] / a[1]').click()

[0114] time.sleep(2)

[0115] RPA_Driver.switch_to_frame('ifrPage100002')

[0116] wait.until(EC.element_to_be_clickable((By.XPATH,' / html / body / div[3] / div[2] / div / div[2] / div / div / div[3] / div / div / a[1]')))

[0117] RPA_Driver.locator('xpath',' / html / body / div[3] / div[2] / div / div[2] / div / div / div[3] / div / div / a[1]').click()

[0118] Step 205: Combine multiple action chain scripts into action chain scripts for different businesses.

[0119] After obtaining multiple action chain sub-scripts, you can splice the multiple action chain sub-scripts according to the order of the sub-processes in the business, so as to obtain action chain scripts for completing different businesses.

[0120] like Figure 6 , showing multiple sub-processes of a business acceptance process according to an embodiment of the present invention, as well as corresponding CRM pages and an example diagram of a corresponding action chain.

[0121] Step 206: In response to the request of the target service, determine the corresponding target action chain script.

[0122] When a user wants to handle a target service, he or she can first generate a request for the target service on the client side. The request may include the service the user wants to handle, the user's information, etc.

[0123] In response to the request of the target business, a corresponding target action chain script may be determined first, and then the target action chain script may be executed to simulate manual mouse and keyboard operations to complete one or more sub-processes corresponding to the target business.

[0124] Step 207: The target action chain script includes at least one target action chain sub-script. According to the preset correspondence between the action chain sub-scripts and the rules, the target rule corresponding to each target action chain sub-script is determined.

[0125] During the business processing process, there may be many scenarios where acceptance fails. When an acceptance failure occurs, the target action chain script may be forced to exit, resulting in the interruption of the RPA automation task.

[0126] To avoid this, embodiments of the present invention can pre-determine the possible acceptance failure scenarios that may occur during the execution of the target action chain script and then set corresponding rules for different acceptance failure scenarios. By using rule verification, interception is set for abnormal situations to prevent interruption of RPA automation tasks.

[0127] Specifically, during the execution of the target action chain script, the correspondence between the preset action chain sub-scripts and the rules can be traversed, and the target rule corresponding to each target action chain sub-script can be determined.

[0128] Then, the condition information required by each target rule (eg, elements, attribute values ​​of elements) is actively cached.

[0129] In one embodiment of the present invention, the following steps may be included to establish a corresponding relationship between the action chain script and the rule:

[0130] For an action chain script, a corresponding rule strategy is set; for a rule strategy, one or more corresponding rules are set; and a correspondence between an action chain script, a rule strategy and one or more corresponding rules is established.

[0131] For each action chain script, a rule strategy with a unique correspondence can be set. One or more rules can be deployed in the rule strategy. The rules can be used to verify the operation of the action chain script. Figure 7 , showing the relationship between action chain scripts, rule policies and rules.

[0132] After setting the rule strategy and the rules in the rule strategy, a corresponding relationship between an action chain script, a rule strategy and one or more corresponding rules can be established.

[0133] As an example, during the execution of the target action chain script, it may be interrupted due to system reasons or user reasons; therefore, the embodiment of the present invention can pre-set system-level rules for the system and business-level rules for the user.

[0134] System-level rules refer to exceptions caused by problems in the CRM system operation or by the RPA robot automation program itself during execution;

[0135] As an example, three system-level rules can be set: RPA robot action chain script loading failure, element positioning failure, and network connection timeout.

[0136] Among them, the rule network connection timeout will inevitably lead to the failure to locate the element. According to the atomic characteristics of the rule, the network connection timeout rule should be eliminated, and only the system-level rules of RPA robot action chain script loading failure and element positioning failure should be retained.

[0137] Business-level rules are unrelated to the RPA robot automation program itself. They refer to acceptance failures caused by the business verification of the acceptance object itself not meeting business requirements, or preset rules set manually to capture process data for automated acceptance.

[0138] As an example, six business-level rules can be set: the application cannot be processed if the user number information does not exist, the application cannot be processed without real-name authentication, no business can be processed in the downtime state, the application cannot be processed if there is no optional relationship between the package and the traffic package, the location of the accepted mobile phone number is output after the customer is successfully located, and the order serial number is output after successful acceptance.

[0139] Table 2 shows the correspondence between some action chain scripts and rules in an embodiment of the present invention.

[0140] Table 2:

[0141] Action chain script ID Action chain name Rule policy ID Rule ID 001 Open your browser 001 1001 002 Log in to the CRM system 002 1001，1002 003 Targeting customers 003 1001，1002，1003，1004，1005，1007 004 Order Attachment 004 1001，1002，1006 005 Submit Order 005 1001，1002，1008 006 Charge invoice 006 1001，1002 007 Print receipt 007 1001，1002

[0142] Table 3 shows some rules and corresponding triggering actions according to an embodiment of the present invention.

[0143] Table 3:

[0144] Rule ID Rule Type rule The action is triggered when the rule verification succeeds 1001 System level Action chain script loading failed RPA task ends, log cache 1002 System level Element positioning failed RPA jumps out of the loop, counter +1, cache log 1003 Business level User number information does not exist RPA jumps out of the loop, counter +1, cache log 1004 Business level No real-name authentication RPA jumps out of the loop, counter +1, cache log 1005 Business level Number suspension status RPA exits the loop, counter +1, and caches the log 1006 Business level There is no optional relationship between package and traffic package RPA jumps out of the loop, counter +1, cache log 1007 Business level Positioning Customer Success Locate the element "number location" and cache logs 1008 Business level Successfully accepted Locate the element "Order Serial Number" and cache the log

[0145] like Figure 8 , rules can include system-level rules and business-level rules; when the system-level rule verification is successful, the exception log can be cached and the RPA task can continue.

[0146] Business-level logs can include general business rules and user-defined business rules. When general business rules are successfully verified, exception logs can be cached and the RPA task can continue. When users automatically verify successfully with business rules, embedded data can be captured and logs can be cached.

[0147] Afterwards, the above logs can be written into the acceptance report; the RPA robot can output the acceptance report after the task is completed.

[0148] Step 208: During the execution of a target action chain script, detect whether the corresponding target rule is triggered.

[0149] Since the rule strategy and the action chain sub-script are bound one-to-one, and the rule strategy and the rules are one-to-many, the RPA robot will traverse and collect the target rules associated with the currently executed target action sub-chain script during operation, actively cache the condition information required for the target rule (usually elements and their attribute values), and determine whether to trigger the corresponding target rule based on the required condition information.

[0150] Step 209: If the corresponding target rule is triggered, the corresponding rule verification result is stored as a tracking log, and the next target action chain script is executed.

[0151] If the corresponding target rule is triggered, the RPA robot will collect relevant information and obtain the corresponding rule verification results; then, the rule verification results can be stored as tracking logs.

[0152] To avoid interruption of the RPA automation task, you can continue to execute the next target action chain script.

[0153] Step 210: If the corresponding target rule is not triggered, execute the next target action chain script.

[0154] If the corresponding target rule isn't triggered, it indicates that the target action chain script hasn't experienced an exception. At this point, the next target action chain subscript can be executed to complete all target action chain subscripts of the target action chain script. By implementing action chain subscript association rule strategies, RPA robots can think like humans and make decisions during the acceptance process, improving acceptance accuracy, stability, and intelligence.

[0155] Step 211: Write the tracking log into the business acceptance report.

[0156] If the target action chain script stores tracking logs during execution, you can write the information from the tracking logs into the business acceptance report before outputting the business acceptance report for the target business. Compared to existing technologies that only output acceptance results of failure or success, this allows users to know what kind of exception occurred.

[0157] Step 212: Based on the executed target action chain script, a business acceptance report corresponding to the target business is output.

[0158] After the target action chain script is executed, the system may output a business acceptance report corresponding to the target business in response to the request of the target business and the operation executed by the target action chain script.

[0159] like Figure 9 , shows a business acceptance report output after an RPA robot automatically accepts a business.

[0160] like Figure 10 , which shows a schematic diagram of an RPA robot task workflow according to an embodiment of the present invention:

[0161] 1. Build an RPA robot instruction set based on CRM page automation: Exhaust all human-computer interaction actions in the CRM system and encapsulate all actions into a tool interface for web automation operations.

[0162] 2. Split a CRM business acceptance process into multiple independent sub-process fragments.

[0163] 3. Convert the sub-process fragments into reusable, automated action chain scripts. Specific steps:

[0164] (1) Recording an action chain script. Record the acceptance fragment of the manual acceptance sub-process, generate a script case, convert the script case into an action chain script that can be automatically executed by the RPA robot, and mark the unique action chain script ID.

[0165] (2) Training the action chain script. Before the action chain script is put into production, it must be simulated in the CRM system test environment to simulate real acceptance. Through repeated testing of normal and abnormal cases, the stability and accuracy of the action chain script's automatic acceptance are verified, thereby maximizing the accuracy and success rate of the RPA robot's automated acceptance.

[0166] (3) The action chain script is stored in the database. After the training of multiple dimensional indicators such as success rate, average processing time of a single business, and maximum number of concurrent users reaches the standard, the process training is completed and the version is solidified and stored in the database.

[0167] 4. By splitting multiple business acceptance processes, repeating steps 2 and 3, an action chain script library can be established.

[0168] 5. Define the associated rule strategy for each action chain script, and define the associated rules for the rule strategy. Rules are the core AI engine that implements the RPA robot's automated fault tolerance mechanism. Specific steps:

[0169] (1) Based on the different acceptance tasks and operation steps completed by each action chain script, the acceptance failure scenarios that may occur during the execution of the action chain script are predicted and different rules are defined. Through rule verification, interception can be set for abnormal situations to prevent the interruption of RPA automation tasks.

[0170] (2) From the user's perspective, rules can be designed manually and the rule verification results can be used as log points to capture the process data of automated acceptance.

[0171] (3) The rule strategy should meet the following characteristics:

[0172] ① Relationship constraints between rule strategies (fine-grained, unique) and action chain scripts (one-to-one);

[0173] ② Relationship constraints (one-to-many) between rule strategies and rules (large ones; for example, whether something appears or not is a rule);

[0174] ③ The rules are unique, deterministic, and atomic;

[0175] ④ Rules are divided into two categories: system-level rules and business-level rules. System-level rules refer to exceptions caused by problems with the CRM system or during the execution of the RPA automation program itself. Business-level rules are unrelated to the RPA automation program itself and refer to acceptance failures caused by the business verification of the acceptance object not meeting business requirements, or the aforementioned rules set manually to capture process data for automated acceptance.

[0176] ⑤ Rule verification. Because rule policies and action chain scripts are bound one-to-one, and rule policies and rules are bound one-to-many, the RPA robot traverses and collects all rules associated with the currently executing action chain script during operation. It proactively caches the conditional information required by the rule (usually elements and their attribute values). Once the condition is met, the rule verification is immediately triggered. The rule verification result only represents the state of the RPA robot at the time of the triggering verification.

[0177] 6. Splice, combine, and logically arrange multiple action chain scripts to assemble and adapt RPA robots with different tasks to realize the automated acceptance of any business.

[0178] 7. During the execution of tasks, the RPA robot triggers rule verification, and the tracking log is output to the automated acceptance report.

[0179] like Figure 11 , which shows a scenario diagram of a method for handling a business according to an embodiment of the present invention:

[0180] When the RPA robot receives a task and the task starts, it can first load user details, such as user accounts, etc.; then determine the corresponding action chain script; the action chain script can be determined from the action chain script library based on the task.

[0181] During the execution of the action chain script, the rule engine can obtain the corresponding rules from the rule policy library and generate a log cache based on the rule detection process.

[0182] Based on the log cache, an acceptance report can be output; at this point, the task is completed.

[0183] In an embodiment of the present invention, the acceptance fragments of the sub-processes for manually accepting each business can be pre-recorded; based on the acceptance fragments, the interactive actions for completing different sub-processes in each business are determined; multiple interactive actions are encapsulated into corresponding instruction sets; based on the instruction sets, multiple action chain sub-scripts corresponding to the multiple interactive actions are generated; multiple action chain sub-scripts are spliced ​​into action chain scripts for different businesses; in response to the request of the target business, the corresponding target action chain script is determined; the target action chain script includes at least one target action chain sub-script, and the target rule corresponding to each target action chain sub-script is determined according to the correspondence between the preset action chain sub-script and the rule; in the process of executing a target action chain sub-script, it is detected whether the corresponding target rule is triggered; if the corresponding target rule is triggered, the corresponding rule verification result is stored as a burial point log, and the next target action chain sub-script is executed; if the corresponding target rule is not triggered, the next target action chain sub-script is executed; the burial point log is written into the business acceptance report; based on the executed target action chain script, the business acceptance report corresponding to the target business is output. Through the embodiment of the present invention, a low-cost automated business processing function is achieved; compared to directly developing a dedicated batch acceptance program based on the core software code, the embodiment of the present invention can reduce costs by generating action chain scripts for different businesses; and because the action chain sub-scripts are only for sub-processes, if different businesses have the same sub-processes, the corresponding action chain sub-scripts can also be used universally. In addition, by using additional scripts to handle business, it is possible to avoid a large pressure on the system when the number of businesses is high and concurrent for a short period of time, thereby avoiding affecting the business processing of the system.

[0184] And in the process of executing the action chain script, it detects whether the preset rules are triggered, and sets interceptions for abnormal situations through rule verification, which can effectively prevent the interruption of automated tasks.

[0185] It should be noted that for the sake of simplicity, the method embodiments are described as a series of actions. However, those skilled in the art should be aware that the embodiments of the present invention are not limited by the order of the actions described, because according to the embodiments of the present invention, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present invention.

[0186] Reference Figure 12 , which shows a schematic diagram of the structure of a service processing device according to an embodiment of the present invention, and may include the following modules:

[0187] The collection module 1201 is used to collect multiple interactive actions for completing different sub-processes in the business and convert the multiple interactive actions into corresponding multiple action chain sub-scripts;

[0188] The splicing module 1202 is used to splice multiple action chain sub-scripts into action chain scripts for different services;

[0189] The execution module 1203 is used to determine the corresponding target action chain script in response to the request of the target business, and execute the target action chain script;

[0190] The output module 1204 is configured to output a business acceptance report corresponding to the target business based on the executed target action chain script.

[0191] In an optional embodiment of the present invention, the target action chain script includes at least one target action chain sub-script, and the execution module 1203 includes:

[0192] The rule determination submodule is used to determine the target rule corresponding to each target action chain subscript based on the correspondence between the preset action chain subscript and the rule;

[0193] The detection submodule is used to detect whether the corresponding target rule is triggered during the execution of a target action chain subscript;

[0194] The first execution sub-step is used to store the corresponding rule verification result as a tracking log if the corresponding target rule is triggered, and execute the next target action chain script;

[0195] The second execution sub-step is used to execute the next target action chain sub-script if the corresponding target rule is not triggered.

[0196] In an optional embodiment of the present invention, the device further comprises:

[0197] The log writing module is used to write the tracking point log into the business acceptance report before outputting the business acceptance report corresponding to the target business.

[0198] In an optional embodiment of the present invention, the device further comprises:

[0199] The rule establishment module is used to set a corresponding rule strategy for an action chain script; set one or more corresponding rules for a rule strategy; and establish a corresponding relationship between an action chain script, a rule strategy and one or more corresponding rules.

[0200] In an optional embodiment of the present invention, the collection module 1201 includes:

[0201] Recording submodule, users record the acceptance segments of the sub-processes of manually accepting various businesses;

[0202] The interaction action determination submodule is used to determine the interaction actions for completing different sub-processes in each business based on the acceptance fragment.

[0203] In an optional embodiment of the present invention, the collection module 1201 includes:

[0204] The encapsulation submodule is used to encapsulate multiple interactive actions into corresponding instruction sets;

[0205] The sub-script generation sub-module is used to generate multiple action chain sub-scripts corresponding to multiple interactive actions according to the instruction set.

[0206] In an embodiment of the present invention, multiple interactive actions for completing different sub-processes in a business can be collected in advance, and the multiple interactive actions can be converted into corresponding multiple action chain sub-scripts; then the multiple action chain sub-scripts are spliced ​​into action chain scripts for different businesses; when a request for a target business is received, the corresponding target action chain script can be determined in response to the request, and the target action chain script can be executed; then, based on the executed target action chain script, a business acceptance report corresponding to the target business is output. Through the embodiment of the present invention, a low-cost business automation processing function is achieved; compared with directly developing a dedicated batch acceptance program based on the core software code, the embodiment of the present invention can reduce costs by generating action chain scripts for different businesses; and because the action chain sub-script is only for sub-processes, if different businesses have the same sub-processes, the corresponding action chain sub-scripts can also be used universally. In addition, by using additional scripts to handle business, it is possible to avoid a large pressure on the system when the number of businesses is high in a short period of time, thereby avoiding affecting the business processing of the system.

[0207] An embodiment of the present invention further provides an electronic device, comprising a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program implements the above-mentioned business processing method when executed by the processor.

[0208] An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the method for handling the above-mentioned business is implemented.

[0209] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0210] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0211] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, apparatus, or computer program products. Thus, embodiments of the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, embodiments of the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0212] The embodiments of the present invention are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, 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 terminal device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the process in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0213] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0214] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable terminal device to implement the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0215] Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they become aware of the basic creative concepts. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present invention.

[0216] Finally, it should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or terminal device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or terminal device that includes the element.

[0217] The above is a detailed introduction to the service processing method, device, electronic device and storage medium provided. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for general technical personnel in this field, based on the ideas of the present invention, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as limiting the present invention.

Claims

1. A business handling method, characterized in that: The method comprises: Collect multiple interactive actions for completing different sub-processes in the business, and convert the multiple interactive actions into corresponding multiple action chain sub-scripts; According to the order of the sub-processes in the business, the multiple action chain sub-scripts are spliced ​​into action chain scripts for different businesses. The action chain sub-scripts corresponding to the same sub-processes in different businesses are universal; In response to a request from a target service, determining a corresponding target action chain script and executing the target action chain script; Outputting a business acceptance report corresponding to the target business based on the executed target action chain script; The target action chain script includes at least one target action chain sub-script, and executing the target action chain script includes: According to the correspondence between the preset action chain scripts and the rules, determine the target rules corresponding to each target action chain script; During the execution of a target action chain script, detect whether the corresponding target rule is triggered; If the corresponding target rule is triggered, the corresponding rule verification result is stored as a tracking log, and the next target action chain script is executed; If the corresponding target rule is not triggered, the next target action chain script is executed.

2. The method according to claim 1, characterized in that Before outputting the business acceptance report corresponding to the target business, the method further includes: The tracking log is written into the business acceptance report.

3. The method according to claim 1, characterized in that The method further comprises the step of establishing the corresponding relationship: For an action chain script, set a corresponding rule strategy; For the rule strategy, set one or more corresponding rules; A correspondence between the action chain script, the rule policy, and the corresponding one or more rules is established.

4. The method according to any one of claims 1 to 3, characterized in that The collection is used to complete multiple interactive actions of different sub-processes in the business, including: Record the acceptance segments of the sub-processes for manually accepting each business; According to the acceptance fragments, interactive actions for completing different sub-processes in each business are determined.

5. The method according to any one of claims 1 to 3, characterized in that The converting the plurality of interactive actions into corresponding plurality of action chain sub-scripts includes: Encapsulating the multiple interactive actions into corresponding instruction sets; According to the instruction set, a plurality of action chain sub-scripts corresponding to the plurality of interactive actions are generated.

6. A business handling device, characterized in that: The device comprises: A collection module, configured to collect multiple interactive actions for completing different sub-processes in a business, and convert the multiple interactive actions into corresponding multiple action chain sub-scripts; A splicing module is used to splice the multiple action chain sub-scripts into action chain scripts for different businesses according to the order of the sub-processes in the business. The action chain sub-scripts corresponding to the same sub-processes in different businesses are universal; An execution module, configured to determine a corresponding target action chain script in response to a request of a target business, and execute the target action chain script; An output module, configured to output a business acceptance report corresponding to the target business based on the executed target action chain script; The target action chain script includes at least one target action chain sub-script, and the execution module includes: The rule determination submodule is used to determine the target rule corresponding to each target action chain subscript based on the correspondence between the preset action chain subscript and the rule; The detection submodule is used to detect whether the corresponding target rule is triggered during the execution of a target action chain subscript; The first execution sub-step is used to store the corresponding rule verification result as a tracking log if the corresponding target rule is triggered, and execute the next target action chain script; The second execution sub-step is used to execute the next target action chain sub-script if the corresponding target rule is not triggered.

7. An electronic device, characterized in that: The method comprises a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein when the computer program is executed by the processor, the method for handling the business as claimed in any one of claims 1 to 5 is implemented.

8. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method for handling the business according to any one of claims 1 to 5 is implemented.

Images