A WebRPA operation and maintenance method and system

By encapsulating WebRPA into multiple components and recording logs in real time, the problem of low troubleshooting efficiency of traditional WebRPA is solved, in-depth analysis and rapid positioning of faults are achieved, and troubleshooting efficiency is significantly improved.

CN114726714BActive Publication Date: 2024-11-22ZHUHAI ZIXUN INFORMATION TECH CO LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN202210151001.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-02-18
Publication Date
2024-11-22
Estimated Expiration
2042-02-18

AI Technical Summary

Technical Problem

Traditional WebRPA lacks abnormal context and data related to data flow changes during operation, which makes it difficult to troubleshoot and consumes a lot of time and energy.

Method used

WebRPA is encapsulated into several components in sequence based on the operation logic, and records the pre-run status, operation results and post-run status logs of each component in real time, and reports it to the log server, combining the start operation log, component operation log and end operation log for operation and maintenance.

Benefits of technology

Through detailed logging and analysis, we can deeply analyze the root cause of the failure from the entire task process of WebRPA, greatly improving the efficiency of troubleshooting.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114726714B_ABST
    Figure CN114726714B_ABST
Patent Text Reader

Abstract

The present invention provides a WebRPA operation and maintenance method and system in the field of WebRPA operation and maintenance technology, the method comprising: step S10, encapsulating WebRPA into several components in sequence based on operation logic; step S20, running WebRPA and the first state data before running, generating a start operation log based on the first state data and reporting it to a log server; step S30, opening a Web page through WebRPA and running each component in sequence; step S40, recording the pre-operation state log, the operation result, and the post-operation state log of each component, generating a component operation log based on the pre- and post-operation state log of the component and reporting it to the log server; step S50, after the WebRPA runs, recording the second state data of WebRPA, generating an end operation log based on the second state data and reporting it to the log server; step S60, the log server performs operation and maintenance based on the start operation log, the component operation log, and the end operation log. The advantage of the present invention is that the efficiency of WebRPA troubleshooting is greatly improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of WebRPA operation and maintenance technology, and in particular to a WebRPA operation and maintenance method and system. Background Art

[0002] With the development of technology, WebRPA is no longer limited to local scheduling, but can also be used for cloud scheduling to help users run some repetitive tasks on a regular basis to achieve unattended operation. For example, in the cross-border e-commerce industry, many sellers have connected to WebRPA cloud scheduling to assist operations.

[0003] Due to the variability of web pages, it is impossible to perfectly adapt to all scenarios when choreographing WebRPA. It is inevitable that many WebRPA operations will fail, which brings great trouble to users. When WebRPA fails to run, it is necessary to conduct timely troubleshooting to locate the cause of the failure, thereby improving the success rate of WebRPA operation. However, when running, traditional WebRPA only records the relevant logs of task start, task end and operation exceptions. It lacks the context of the exception and the relevant data of data flow changes during the operation. As a result, when troubleshooting, the operation and maintenance personnel can only see the appearance of the operation failure, and cannot deeply analyze the root cause from the entire task process of WebRPA, resulting in troubleshooting and repairing. It takes a lot of time and energy.

[0004] Therefore, how to provide a WebRPA operation and maintenance method and system to improve the efficiency of WebRPA troubleshooting has become a technical problem that needs to be solved urgently. Summary of the invention

[0005] The technical problem to be solved by the present invention is to provide a WebRPA operation and maintenance method and system to improve the efficiency of WebRPA troubleshooting.

[0006] In a first aspect, the present invention provides a WebRPA operation and maintenance method, comprising the following steps:

[0007] Step S10: Encapsulate WebRPA into several components in sequence based on the operation logic;

[0008] Step S20: running the WebRPA, recording first state data before the WebRPA runs, and generating a start-of-running log based on the first state data and reporting it to a log server;

[0009] Step S30: Open a web page through the WebRPA, and run each component on the web page in sequence;

[0010] Step S40, recording in real time the component pre-operation state log, the component operation result and the component post-operation state log of each component operation, generating a component operation log based on the component pre-operation state log and the component post-operation state log and reporting it to a log server;

[0011] Step S50: After the WebRPA is completed, the second state data of the WebRPA is recorded, and a running end log is generated based on the second state data and reported to a log server;

[0012] Step S60: The log server operates and maintains WebRPA based on the start operation log, the component operation log, and the end operation log.

[0013] Furthermore, in step S10, the component at least carries a component ID, a component name, an operation sequence, component parameters and component variables.

[0014] Furthermore, the step S20 is specifically as follows:

[0015] Manually run the WebRPA, or regularly run the WebRPA through a cloud scheduling service, and record first state data before the WebRPA runs, and generate a start-running log based on the first state data and report it to a log server in real time;

[0016] The first status data at least includes an operation ID, a start time of operation, operation parameters, operation variables, an operation environment and an operation source.

[0017] Furthermore, the step S40 specifically includes:

[0018] Step S41, WebRPA records in real time the pre-operation status log of each component before the operation;

[0019] The component pre-operation status log includes at least the component ID, component name, start time, pre-operation component parameters and pre-operation component variables;

[0020] Step S42, WebRPA obtains in real time the component operation results fed back during the operation of each of the components;

[0021] The component operation result at least includes a state mark and feedback data; the state mark indicates operation success or operation failure; when the state mark indicates operation success, the feedback data is operation data; when the state mark indicates operation failure, the feedback data at least includes a fault code, a fault cause and fault detailed information;

[0022] Step S43: WebRPA generates a post-operation status log of the component after the component is operated based on the component operation result;

[0023] The component post-operation status log includes at least the component ID, component name, end-of-operation time, post-operation component parameters, post-operation component variables, status identification, and feedback data;

[0024] Step S44: WebRPA generates a component operation log based on the component pre-operation status log and the component post-operation status log, and reports the component operation log to a log server in real time.

[0025] Furthermore, in the step S50, the second status data at least includes an operation ID, an end time of operation, operation parameters, operation variables, an operation environment and an operation source.

[0026] In a second aspect, the present invention provides a WebRPA operation and maintenance system, including the following modules:

[0027] The component encapsulation module is used to encapsulate WebRPA into several components based on the operation logic;

[0028] A start-up log reporting module, used for running the WebRPA, recording first state data before the WebRPA runs, and generating a start-up log report to a log server based on the first state data;

[0029] A component running module, used to open a web page through the WebRPA and run each component on the web page in sequence;

[0030] The component operation log reporting module is used to record the component pre-operation state log, component operation result and component post-operation state log of each component operation in real time, generate the component operation log based on the component pre-operation state log and the component post-operation state log and report it to the log server;

[0031] An end-of-run log reporting module, configured to record the second state data of the WebRPA after the WebRPA is run, and generate an end-of-run log based on the second state data and report it to a log server;

[0032] The WebRPA operation and maintenance module is used for the log server to operate and maintain WebRPA based on the start operation log, component operation log and end operation log.

[0033] Furthermore, in the component packaging module, the component carries at least a component ID, a component name, an operation sequence, component parameters and component variables.

[0034] Furthermore, the start-up log reporting module is specifically:

[0035] Manually run the WebRPA, or regularly run the WebRPA through a cloud scheduling service, and record first state data before the WebRPA runs, and generate a start-running log based on the first state data and report it to a log server in real time;

[0036] The first status data at least includes an operation ID, a start time of operation, operation parameters, operation variables, an operation environment and an operation source.

[0037] Furthermore, the component operation log reporting module specifically includes:

[0038] A component pre-operation state log recording unit, used for WebRPA to record the component pre-operation state log before each component is operated in real time;

[0039] The component pre-operation status log includes at least the component ID, component name, start time, pre-operation component parameters and pre-operation component variables;

[0040] A component operation result acquisition unit, used for WebRPA to obtain in real time the component operation results fed back during the operation of each component;

[0041] The component operation result at least includes a state mark and feedback data; the state mark indicates operation success or operation failure; when the state mark indicates operation success, the feedback data is operation data; when the state mark indicates operation failure, the feedback data at least includes a fault code, a fault cause and fault detailed information;

[0042] A component post-operation status log generating unit, used for WebRPA to generate a component post-operation status log after the component is operated based on the component operation result;

[0043] The component post-operation status log includes at least the component ID, component name, end-of-operation time, post-operation component parameters, post-operation component variables, status identification, and feedback data;

[0044] The component operation log generating unit is used for WebRPA to generate a component operation log based on the component pre-operation status log and the component post-operation status log, and report the component operation log to the log server in real time.

[0045] Furthermore, in the end-of-run log reporting module, the second status data at least includes an operation ID, an end-of-run time, an operation parameter, an operation variable, an operation environment, and an operation source.

[0046] The advantages of the present invention are:

[0047] By recording the start and end logs before and after the WebRPA runs and reporting them to the log server, WebRPA is encapsulated into several components based on the running logic, and the pre-running status log of each component is recorded before the running of each component, the running result of each component is obtained during the running of each component, and the post-running status log of each component is generated based on the running result of the component after the running of each component, and then the component running log is generated based on the pre-running status log and the post-running status log and reported to the log server, so that the log server not only stores the start and end logs of WebRPA, but also stores the component running logs of each component. By combining the start log, the component running log and the end log, the root cause of the fault can be deeply analyzed from the entire task process of WebRPA, overcoming the traditional defects of lacking abnormal context and relevant data of data flow changes during the running process, and ultimately greatly improving the efficiency of WebRPA troubleshooting. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] The present invention will be further described below in conjunction with embodiments with reference to the accompanying drawings.

[0049] Figure 1 It is a flow chart of a WebRPA operation and maintenance method of the present invention.

[0050] Figure 2 It is a structural schematic diagram of a WebRPA operation and maintenance system of the present invention.

[0051] Figure 3 It is a schematic diagram of the process of the present invention. DETAILED DESCRIPTION

[0052] The technical solution in the embodiments of the present application has the following overall idea: WebRPA is encapsulated into several components in sequence based on the operation logic, the component operation log of each component is recorded and reported to the log server, the start operation log and the end operation log are recorded before and after the WebRPA operation and reported to the log server, and the start operation log, component operation log and end operation log stored in the log server are combined to deeply analyze the root cause of the fault from the entire task process of WebRPA to improve the efficiency of WebRPA troubleshooting.

[0053] Please refer to Figures 1 to 3 As shown, a preferred embodiment of a WebRPA operation and maintenance method of the present invention includes the following steps:

[0054] Step S10: Encapsulate WebRPA into several components based on the operation logic, that is, abstract WebRPA into components with single responsibilities based on the operation logic. One WebRPA is composed of several components. Running WebRPA means running each component in sequence according to certain conditions until all components are completed.

[0055] Step S20: running (triggering) the WebRPA, recording first state data before the WebRPA runs, and generating a start-running log based on the first state data and reporting it to a log server;

[0056] Step S30: Open a web page through the WebRPA, and run each component on the web page in sequence;

[0057] Step S40, recording the pre-operation status log, the component operation result and the post-operation status log of each component operation in real time, generating a component operation log based on the pre-operation status log and the post-operation status log and reporting it to a log server; through the component operation log, the context of the fault and the change of the data flow can be quickly understood, so as to quickly find the root cause of the fault and reduce the difficulty of troubleshooting;

[0058] Step S50: After the WebRPA is completed, the second state data of the WebRPA is recorded, and a running end log is generated based on the second state data and reported to a log server;

[0059] Step S60, the log server operates and maintains WebRPA based on the start operation log, the component operation log, and the end operation log; in specific implementation, the operation status of each component can be counted based on the component operation log, and the components with a higher operation failure rate can be optimized in a targeted manner.

[0060] In step S10, the component carries at least a component ID, a component name, an operation sequence, component parameters and component variables; the component ID is the component number, and the operation sequence is the order in which the components are executed.

[0061] The step S20 is specifically as follows:

[0062] Manually run the WebRPA, or regularly run the WebRPA through a cloud scheduling service, and record first state data before the WebRPA runs, and generate a start-running log based on the first state data and report it to a log server in real time;

[0063] The first status data includes at least an operation ID, a start time, operation parameters, operation variables, an operation environment, and an operation source; the operation ID is an identifier of the number of times WebRPA has been run, the operation environment is the running browser version and the operating system installed by the browser, and the operation source is the installation path of WebRPA.

[0064] The step S40 specifically includes:

[0065] Step S41, WebRPA records in real time the pre-operation status log of each component before the operation;

[0066] The component pre-operation status log includes at least the component ID, component name, start time, pre-operation component parameters and pre-operation component variables;

[0067] Step S42, WebRPA obtains in real time the component operation results fed back during the operation of each of the components;

[0068] The component operation result at least includes a state mark and feedback data; the state mark indicates operation success or operation failure; when the state mark indicates operation success, the feedback data is operation data; when the state mark indicates operation failure, the feedback data at least includes a fault code, a fault cause and fault detailed information;

[0069] Step S43: WebRPA generates a post-operation status log of the component after the component is operated based on the component operation result;

[0070] The component post-operation status log includes at least the component ID, component name, end-of-operation time, post-operation component parameters, post-operation component variables, status identification, and feedback data;

[0071] Step S44, WebRPA generates a component operation log based on the component pre-operation status log and the component post-operation status log, and reports the component operation log to the log server in real time. By reporting the component operation log of each component to the log server in real time, rather than reporting all the components uniformly after they have completed operation, the timeliness of troubleshooting and locating is effectively improved.

[0072] In the step S50, the second status data at least includes an operation ID, an end time of operation, operation parameters, operation variables, an operation environment, and an operation source.

[0073] A preferred embodiment of a WebRPA operation and maintenance system of the present invention includes the following modules:

[0074] The component encapsulation module is used to encapsulate WebRPA into several components based on the operation logic. That is, WebRPA is abstracted into components with a single responsibility based on the operation logic. A WebRPA consists of several components. Running WebRPA means running each component in sequence according to certain conditions until all components are completed.

[0075] A start-up log reporting module, used for running (triggering) the WebRPA, recording first state data before the WebRPA runs, and generating a start-up log report to a log server based on the first state data;

[0076] A component running module, used to open a web page through the WebRPA and run each component on the web page in sequence;

[0077] The component operation log reporting module is used to record the pre-operation status log, component operation result and post-operation status log of each component operation in real time, generate the component operation log based on the pre-operation status log and post-operation status log and report it to the log server; through the component operation log, the context of the fault and the change of the data flow can be quickly understood, so as to quickly find the root cause of the fault and reduce the difficulty of troubleshooting;

[0078] An end-of-run log reporting module, configured to record the second state data of the WebRPA after the WebRPA is run, and generate an end-of-run log based on the second state data and report it to a log server;

[0079] The WebRPA operation and maintenance module is used for the log server to operate and maintain WebRPA based on the start operation log, component operation log and end operation log; in specific implementation, the operation status of each component can be counted based on the component operation log, and targeted optimization can be performed on the components with a higher operation failure rate.

[0080] In the component packaging module, the component carries at least a component ID, a component name, an operation sequence, component parameters and component variables; the component ID is the number of the component, and the operation sequence is the order in which the components are executed.

[0081] The starting operation log reporting module is specifically:

[0082] Manually run the WebRPA, or regularly run the WebRPA through a cloud scheduling service, and record first state data before the WebRPA runs, and generate a start-running log based on the first state data and report it to a log server in real time;

[0083] The first status data includes at least an operation ID, a start time, operation parameters, operation variables, an operation environment, and an operation source; the operation ID is an identifier of the number of times WebRPA has been run, the operation environment is the running browser version and the operating system installed by the browser, and the operation source is the installation path of WebRPA.

[0084] The component operation log reporting module specifically includes:

[0085] A component pre-operation state log recording unit, used for WebRPA to record the component pre-operation state log before each component is operated in real time;

[0086] The component pre-operation status log includes at least the component ID, component name, start time, pre-operation component parameters and pre-operation component variables;

[0087] A component operation result acquisition unit, used for WebRPA to obtain in real time the component operation results fed back during the operation of each component;

[0088] The component operation result at least includes a state mark and feedback data; the state mark indicates operation success or operation failure; when the state mark indicates operation success, the feedback data is operation data; when the state mark indicates operation failure, the feedback data at least includes a fault code, a fault cause and fault detailed information;

[0089] A component post-operation status log generating unit, used for WebRPA to generate a component post-operation status log after the component is operated based on the component operation result;

[0090] The component post-operation status log includes at least the component ID, component name, end-of-operation time, post-operation component parameters, post-operation component variables, status identification, and feedback data;

[0091] The component operation log generation unit is used for WebRPA to generate a component operation log based on the component pre-operation status log and the component post-operation status log, and report the component operation log to the log server in real time. By reporting the component operation log of each component to the log server in real time, rather than reporting all the components uniformly after the operation is completed, the timeliness of fault troubleshooting and locating is effectively improved.

[0092] In the end-of-run log reporting module, the second status data at least includes an operation ID, an end-of-run time, an operation parameter, an operation variable, an operation environment, and an operation source.

[0093] In summary, the advantages of the present invention are:

[0094] By recording the start and end logs before and after the WebRPA runs and reporting them to the log server, WebRPA is encapsulated into several components based on the running logic, and the pre-running status log of each component is recorded before the running of each component, the running result of each component is obtained during the running of each component, and the post-running status log of each component is generated based on the running result of the component after the running of each component, and then the component running log is generated based on the pre-running status log and the post-running status log and reported to the log server, so that the log server not only stores the start and end logs of WebRPA, but also stores the component running logs of each component. By combining the start log, the component running log and the end log, the root cause of the fault can be deeply analyzed from the entire task process of WebRPA, overcoming the traditional defects of lacking abnormal context and relevant data of data flow changes during the running process, and ultimately greatly improving the efficiency of WebRPA troubleshooting.

[0095] Although the specific implementation modes of the present invention are described above, those skilled in the art should understand that the specific implementation modes described are only illustrative and are not intended to limit the scope of the present invention. Equivalent modifications and changes made by those skilled in the art in accordance with the spirit of the present invention should be included in the scope of protection of the claims of the present invention.

Claims

1. A WebRPA operation and maintenance method, characterized in that: The steps include: Step S10: Encapsulate WebRPA into several components in sequence based on the operation logic; the components carry at least component ID, component name, operation order, component parameters and component variables; Step S20: manually run the WebRPA, or run the WebRPA regularly through a cloud scheduling service, and record first status data before the WebRPA runs, and generate a start-running log based on the first status data and report it to a log server in real time; The first status data at least includes an operation ID, a start time of operation, operation parameters, operation variables, an operation environment, and an operation source; Step S30: Open a web page through the WebRPA, and run each component on the web page in sequence; Step S40, recording in real time the component pre-operation state log, the component operation result and the component post-operation state log of each component operation, generating a component operation log based on the component pre-operation state log and the component post-operation state log and reporting it to a log server; Step S50: After the WebRPA is completed, the second state data of the WebRPA is recorded, and a log of the end of the operation is generated based on the second state data and reported to the log server; the second state data at least includes the operation ID, the end time of the operation, the operation parameters, the operation variables, the operation environment and the operation source; Step S60: The log server operates and maintains the WebRPA based on the start operation log, the component operation log, and the end operation log; The step S40 specifically includes: Step S41, WebRPA records in real time the pre-operation status log of each component before the operation; The component pre-operation status log includes at least the component ID, component name, start time, pre-operation component parameters and pre-operation component variables; Step S42, WebRPA obtains in real time the component operation results fed back during the operation of each of the components; The component operation result at least includes a state mark and feedback data; the state mark indicates operation success or operation failure; when the state mark indicates operation success, the feedback data is operation data; when the state mark indicates operation failure, the feedback data at least includes a fault code, a fault cause and fault detailed information; Step S43: WebRPA generates a post-operation status log of the component after the component is operated based on the component operation result; The component post-operation status log includes at least the component ID, component name, end-of-operation time, post-operation component parameters, post-operation component variables, status identification, and feedback data; Step S44: WebRPA generates a component operation log based on the component pre-operation status log and the component post-operation status log, and reports the component operation log to a log server in real time.

2. A WebRPA operation and maintenance system, characterized by: Includes the following modules: A component encapsulation module is used to encapsulate WebRPA into several components in sequence based on the operation logic; the components carry at least component ID, component name, operation order, component parameters and component variables; A start-up log reporting module, used to manually run the WebRPA, or to run the WebRPA regularly through a cloud scheduling service, and to record first state data before the WebRPA runs, and to generate a start-up log based on the first state data and report it to a log server in real time; The first status data at least includes an operation ID, a start time of operation, operation parameters, operation variables, an operation environment, and an operation source; A component running module, used to open a web page through the WebRPA and run each component on the web page in sequence; The component operation log reporting module is used to record the component pre-operation state log, component operation result and component post-operation state log of each component operation in real time, generate the component operation log based on the component pre-operation state log and the component post-operation state log and report it to the log server; An end-of-run log reporting module is used for recording the second state data of the WebRPA after the WebRPA runs, and generating an end-of-run log based on the second state data and reporting it to a log server; the second state data at least includes an operation ID, an end-of-run time, an operation parameter, an operation variable, an operation environment, and an operation source; A WebRPA operation and maintenance module, used for the log server to operate and maintain WebRPA based on the start operation log, the component operation log, and the end operation log; The component operation log reporting module specifically includes: A component pre-operation state log recording unit, used for WebRPA to record the component pre-operation state log before each component is operated in real time; The component pre-operation status log includes at least the component ID, component name, start time, pre-operation component parameters and pre-operation component variables; A component operation result acquisition unit, used for WebRPA to obtain in real time the component operation results fed back during the operation of each component; The component operation result at least includes a state mark and feedback data; the state mark indicates operation success or operation failure; when the state mark indicates operation success, the feedback data is operation data; when the state mark indicates operation failure, the feedback data at least includes a fault code, a fault cause and fault detailed information; A component post-operation status log generating unit, used for WebRPA to generate a component post-operation status log after the component is operated based on the component operation result; The component post-operation status log includes at least the component ID, component name, end-of-operation time, post-operation component parameters, post-operation component variables, status identification, and feedback data; The component operation log generating unit is used for WebRPA to generate a component operation log based on the component pre-operation status log and the component post-operation status log, and report the component operation log to the log server in real time.

Citation Information

Patent Citations

  • Fault positioning platform and fault positioning method and device

    CN106254144A

  • Fault locating method, fault locating device and fault locating system

    CN108768752A

  • Resource processing flow log collection system based on event mechanism

    CN112214459A

  • Analysis link calling method and system based on directed acyclic graph structure

    CN112527619A

  • System and method to diagnose applications by accessing log files associated with different subsystems of a data center via a common interface

    US10372595B1