Version switching method, device, terminal device and storage medium of RPA tool

Abstract

The present application is applicable to the field of RPA technology, and provides a version switching method, apparatus, terminal device and storage medium for an RPA tool. The above-mentioned version switching method of the RPA tool includes: obtaining a first configuration file of the current RPA tool; obtaining a second configuration file of the target RPA tool; determining the version difference between the current RPA tool and the target RPA tool according to the first configuration file and the second configuration file; generating a compatibility patch according to the version difference; performing version switching on the current RPA tool according to the compatibility patch to obtain the target RPA tool. The embodiment of the present application can automatically complete the version switching by determining the version difference between the current RPA tool and the target RPA tool, generating a compatibility patch according to the version difference, and then performing version switching through the compatibility patch, and solves the compatibility problems that may occur during version switching, thereby improving the user experience.

Description

Technical Field

[0001] The present application belongs to the field of RPA technology, and in particular, relates to a version switching method, apparatus, terminal device, and storage medium of an RPA tool. Background Art

[0002] With the rapid development of RPA (Robotic Process Automation) technology, more and more companies are beginning to use RPA tools to automatically execute business processes to improve work efficiency and save labor costs. With the continuous upgrading of RPA tools, different versions of RPA tools have emerged. Different versions of RPA tools may modify some functions or data formats of RPA tools, so compatibility issues are likely to occur when switching the version of RPA tools. In related technologies, when compatibility issues occur when switching the version of RPA tools, users need to solve them by themselves, which requires users to have certain RPA knowledge and takes a lot of time, greatly affecting the user experience. Summary of the invention

[0003] The embodiments of the present application provide a method, apparatus, terminal device, and storage medium for switching versions of an RPA tool, which can solve the problem in the related art that when compatibility issues arise when switching versions of RPA tools, users need to solve them by themselves, resulting in a poor user experience.

[0004] In a first aspect, an embodiment of the present application provides a version switching method of an RPA tool, including:

[0005] Get the first configuration file of the current RPA tool;

[0006] Obtaining a second configuration file of a target RPA tool, where the target RPA tool has a different version from the current RPA tool;

[0007] Determine, according to the first configuration file and the second configuration file, a version difference between the current RPA tool and the target RPA tool;

[0008] generating a compatibility patch according to the version differences;

[0009] The current RPA tool is switched to a new version according to the compatibility patch to obtain the target RPA tool.

[0010] In a second aspect, an embodiment of the present application provides a version switching device for an RPA tool, including:

[0011] A first acquisition module, used to acquire a first configuration file of the current RPA tool;

[0012] A second acquisition module is used to acquire a second configuration file of a target RPA tool, where the target RPA tool has a different version from the current RPA tool;

[0013] A determination module, configured to determine a version difference between the current RPA tool and the target RPA tool according to the first configuration file and the second configuration file;

[0014] A generation module, used for generating a compatibility patch according to the version difference;

[0015] A switching module is used to switch the version of the current RPA tool according to the compatibility patch to obtain the target RPA tool.

[0016] In a third aspect, an embodiment of the present application provides a terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the version switching method of the above-mentioned RPA tool when executing the computer program.

[0017] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the steps of the version switching method of the above-mentioned RPA tool.

[0018] In a fifth aspect, an embodiment of the present application provides a computer program product, which, when running on a terminal device, enables the terminal device to execute the version switching method of the above-mentioned RPA tool.

[0019] The beneficial effect of the embodiment of the present application compared with the prior art is: the embodiment of the present application obtains the first configuration file of the current RPA tool and obtains the second configuration file of the target RPA tool, and then determines the version difference between the current RPA tool and the target RPA tool according to the first configuration file and the second configuration file, and then generates a compatibility patch according to the version difference, and then switches the version of the current RPA tool according to the compatibility patch to obtain the target RPA tool. The embodiment of the present application determines the version difference between the current RPA tool and the target RPA tool, generates a compatibility patch according to the version difference, and then switches the version through the compatibility patch, which can automatically complete the version switching and solve the compatibility problems that may occur during the version switching, thereby improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0021] Figure 1 It is a schematic diagram of an implementation flow of a version switching method of an RPA tool provided in an embodiment of the present application;

[0022] Figure 2 It is a structural diagram of a version switching device of an RPA tool provided in an embodiment of the present application;

[0023] Figure 3 It is a schematic diagram of the structure of the terminal device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0024] In order to make the purpose, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work are protected by the present application.

[0025] It should be noted that the terms "include", "comprises" and "have" and any variations thereof in the specification and claims of the present application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, terminal, product or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units that are inherent to these processes, methods, products or devices. In the claims, specification and drawings of the present application, relational terms such as "first" and "second" are merely used to distinguish one entity / operation / object from another entity / operation / object, and do not necessarily require or imply any such real-time relationship or order between these entities / operations / objects.

[0026] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0027] With the rapid development of RPA (Robotic Process Automation) technology, more and more companies are beginning to use RPA tools to automatically execute business processes to improve work efficiency and save labor costs. With the continuous upgrading of RPA tools, different versions of RPA tools have emerged. Different versions of RPA tools may modify some functions or data formats of RPA tools, so compatibility issues are likely to occur when switching the version of RPA tools. In related technologies, when compatibility issues occur when switching the version of RPA tools, users need to solve them by themselves, which requires users to have certain RPA knowledge and takes a lot of time, greatly affecting the user experience.

[0028] In view of this, the embodiment of the present application determines the version difference between the current RPA tool and the target RPA tool, generates a compatibility patch based on the version difference, and then performs version switching through the compatibility patch. This can automatically complete the version switching and solve the compatibility issues that may arise during version switching, thereby improving the user experience.

[0029] In order to illustrate the technical solution of the present application, a specific embodiment is provided below for illustration.

[0030] Figure 1 The present invention provides a schematic diagram of the implementation process of a method for switching versions of an RPA tool, which can be applied to a terminal device. The terminal device can be a mobile phone, a tablet computer, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, etc.

[0031] The terminal device can receive a version switching instruction issued by a user on the current RPA tool. The terminal device can receive the version switching instruction and execute the version switching method of the above RPA tool.

[0032] Specifically, the version switching method of the above RPA tool may include the following steps S101 to S105.

[0033] Step S101, obtaining a first configuration file of the current RPA tool.

[0034] The current RPA tool is the RPA tool that the user is currently using.

[0035] In an implementation manner of the present application, the terminal device may query a configuration file, that is, a first configuration file, from a file directory of the current RPA tool.

[0036] Step S102: Obtain a second configuration file of the target RPA tool.

[0037] The target RPA tool is a different version from the current RPA tool. The target RPA tool is the version of the RPA tool that the user wants to switch to. It is understandable that the version of the target RPA tool may be higher or lower than the version of the current RPA tool, and the implementation method of the present application does not limit this.

[0038] In an embodiment of the present application, the terminal device can query the configuration file of the target RPA tool, that is, the second configuration file, from the installation package corresponding to the target RPA tool. It is understandable that to switch the current RPA tool to the target RPA tool, the installation package of the target RPA tool is first obtained, and the installation package can include the configuration file of the target RPA tool.

[0039] Step S103: determining the version difference between the current RPA tool and the target RPA tool according to the first configuration file and the second configuration file.

[0040] The version difference can be used to characterize the difference between the current RPA tool and the target RPA tool, such as the difference between data formats, the difference between functions, etc. It should be understood that the reason why there is a compatibility problem when switching the current RPA tool to the target RPA tool is the version difference between the current RPA tool and the target RPA tool.

[0041] In an implementation manner of the present application, after obtaining the first configuration file and the second configuration file, the terminal device can compare the first configuration file with the second configuration file, for example, compare the differences between the functions of the two versions, thereby determining the version difference between the current RPA tool and the target RPA tool.

[0042] Step S104: Generate a compatibility patch according to the version difference.

[0043] Among them, the compatibility patch can be used to solve the compatibility issues between the current RPA tool and the target RPA tool. It can be a script, a set of codes, or a set of configuration change suggestions.

[0044] In an implementation manner of the present application, after the version difference is determined, the terminal device may generate a compatibility patch according to the version difference.

[0045] Step S105: switch the version of the current RPA tool according to the compatibility patch to obtain the target RPA tool.

[0046] In an implementation manner of the present application, after obtaining the compatibility patch, the terminal device can switch the version of the current RPA tool based on the target RPA tool installation package in combination with the compatibility patch, thereby obtaining the target RPA tool.

[0047] The beneficial effect of the embodiment of the present application compared with the prior art is: the embodiment of the present application obtains the first configuration file of the current RPA tool and obtains the second configuration file of the target RPA tool, and then determines the version difference between the current RPA tool and the target RPA tool according to the first configuration file and the second configuration file, and then generates a compatibility patch according to the version difference, and then switches the version of the current RPA tool according to the compatibility patch to obtain the target RPA tool. The embodiment of the present application determines the version difference between the current RPA tool and the target RPA tool, generates a compatibility patch according to the version difference, and then switches the version through the compatibility patch, which can automatically complete the version switching and solve the compatibility problems that may occur during the version switching, thereby improving the user experience.

[0048] In some specific embodiments of the present application, the above-mentioned version differences may include functional differences, format differences and language differences. The above-mentioned determination of the version differences between the current RPA tool and the target RPA tool based on the first configuration file and the second configuration file may specifically include steps S401 to S405.

[0049] Step S401: query the first function code, the first data format, and the first language of the current RPA tool according to the first configuration file.

[0050] The first function code can be used to implement the function corresponding to the current RPA tool. The first data format is the format of the data in the current RPA tool, such as XML, JSON, etc. The first language is the programming language used by the current RPA tool code, such as Python, Java, etc.

[0051] In an embodiment of the present application, the terminal device can query the code segment corresponding to each function of the current RPA tool from the first configuration file to obtain the first function code. Similarly, the terminal device can also query the first data format and the first programming language used by the current RPA tool from the first configuration file.

[0052] Step S402: query the second function code, the second data format, and the second language of the target RPA tool according to the second configuration file.

[0053] The second function code can be used to implement the function corresponding to the target RPA tool. The second data format is the format of the data in the target RPA tool, such as XML, JSON, etc. The second language is the programming language used by the target RPA tool code, such as Python, Java, etc.

[0054] In an implementation manner of the present application, the terminal device can query the second function code of the target RPA tool and the second data format and the second programming language used from the second configuration file.

[0055] Step S403: determining a function difference according to the first function code and the second function code.

[0056] Among them, the functional difference can be used to characterize the functional difference between the current RPA tool and the target RPA tool, which is specifically reflected in the difference in code.

[0057] In an implementation manner of the present application, after obtaining the first function code and the second function code, the terminal device can compare the first function code with the second function code one by one to determine the code added, deleted, or modified by the target RPA tool compared to the current RPA tool, thereby determining the functional differences.

[0058] Step S404: determining a format difference according to the first data format and the second data format.

[0059] The format difference can be used to characterize the difference in data format between the current RPA tool and the target RPA tool.

[0060] In an implementation manner of the present application, after obtaining the first data format and the second data format, the terminal device can compare the first data format with the corresponding second data format to determine the difference between the two in data output or input format, that is, the format difference. For example, different versions may use different file formats, data structures or encoding methods.

[0061] Step S405: determining a language difference according to the first language and the second language.

[0062] Among them, language differences can be used to characterize the differences in programming languages ​​between the current RPA tool and the target RPA tool.

[0063] In an implementation manner of the present application, after obtaining the first language and the second language, the terminal device can compare the first language with the corresponding second language to determine the differences in syntax, functions or commands between the two, that is, language differences, which may lead to incompatibility of scripts or codes.

[0064] The implementation mode of the present application uses the configuration files of the current RPA tool and the target RPA tool to comprehensively compare the current RPA tool and the target RPA tool in terms of function, format and language, so as to accurately identify the version differences between the two, which helps to generate more accurate compatibility patches and improve the efficiency and success rate of version switching.

[0065] In some specific implementations of the present application, the above-mentioned generation of a compatibility patch according to version differences may specifically include step S501 and step S502.

[0066] Step S501: formulate a compatibility strategy according to version differences.

[0067] Among them, the compatibility policy can be used to indicate how to repair, adjust or convert version differences to ensure a smooth transition between two versions.

[0068] In an implementation manner of the present application, the terminal device may formulate a detailed strategy to handle version differences based on determined version differences (eg, functional differences, format differences, and language differences).

[0069] Specifically, in some specific implementations of the present application, the above-mentioned version differences may include functional differences, format differences and language differences, and the above-mentioned compatibility strategy formulated according to the version differences may specifically include steps S601 to S604.

[0070] Step S601, formulating a code conversion strategy according to functional differences.

[0071] In an embodiment of the present application, the terminal device can formulate a code conversion strategy based on the functional differences between the two versions to ensure that the functions of the two versions can operate normally. The code conversion strategy can be used to indicate how to modify the function code of the current RPA tool so that the function code of the current RPA tool is consistent with the function code of the target RPA tool. Exemplarily, assuming that the target RPA tool has added a certain function, the terminal device can obtain the code corresponding to the function in the target RPA tool and generate a code conversion strategy that adds the code of the function to the function code of the current RPA tool.

[0072] Step S602: formulating a data format mapping strategy according to the format differences.

[0073] In an embodiment of the present application, the terminal device can formulate a data format mapping strategy based on the format differences between the two versions to ensure the integrity and consistency of the data. The data format mapping strategy can be used to indicate how to convert the data format of the current RPA tool so that the data format of the current RPA tool is consistent with the data format of the target RPA tool. Exemplarily, assuming that the data format of the target RPA tool is XML and the data format of the current RPA tool is JSON, the terminal device can generate a data format mapping strategy that converts the data format of the current RPA tool from JSON to XML based on the format differences.

[0074] Step S603: formulating a language adjustment strategy according to language differences.

[0075] In an embodiment of the present application, the terminal device can formulate a language adjustment strategy based on the language differences between the two versions to ensure that the script can run normally in the new version. The language adjustment strategy can be used to indicate how to convert the language of the current RPA tool so that the language of the current RPA tool is consistent with the language of the target RPA tool. Exemplarily, assuming that the data format of the target RPA tool is Python and the data format of the current RPA tool is Java, the terminal device can generate a language adjustment strategy that converts the language of the current RPA tool from Java to Python based on the language differences.

[0076] Step S604: synthesize a compatibility strategy according to the code conversion strategy, the data format mapping strategy, and the language adjustment strategy.

[0077] In the implementation manner of the present application, after obtaining the code conversion strategy, data format mapping strategy and language adjustment strategy, the terminal device can combine the above code conversion strategy, data format mapping strategy and language adjustment strategy to form an overall compatibility strategy. The strategy can be used to guide how to handle and solve all identified incompatible issues, thereby ensuring smooth version switching.

[0078] Step S502: developing a compatibility patch according to the compatibility strategy.

[0079] In the implementation of the present application, after obtaining the compatibility policy, the terminal device can further develop an actual compatibility patch according to the compatibility policy. The patch can be a code library, script or specific tool used to solve the actual incompatibility problem. For example, if the new version introduces new functions or modifies old functions, the patch can contain additional code or logic to implement these changes.

[0080] In some embodiments of the present application, after generating a compatibility patch based on version differences, and before performing version switching on the current RPA tool based on the compatibility patch to obtain the target RPA tool, the method may further include steps S701 and S702.

[0081] Step S701: query the second data format in the second configuration file.

[0082] Step S702: convert the data format of the compatibility patch into a second data format to obtain a converted compatibility patch.

[0083] It is understandable that the data format of the compatibility patch is not necessarily consistent with the data format of the target RPA tool. When the data format of the compatibility patch is inconsistent with the data format of the target RPA tool, the target RPA tool cannot use the compatibility patch.

[0084] In an embodiment of the present application, the terminal device can query the second data format of the target RPA tool in the second configuration file, and then convert the data format of the compatibility patch into the second data format, so that the data format of the converted compatibility patch is consistent with the data format of the target RPA tool, ensuring that the data format of the compatibility patch matches the data format of the target RPA tool, so that the version switch can be carried out smoothly.

[0085] In some implementations of the present application, after the current RPA tool is switched in version according to the compatibility patch to obtain the target RPA tool, the method may further include steps S801 to S803.

[0086] Step S801: Use the target RPA tool to execute all functions in the preset task process.

[0087] Step S802: When the target RPA tool fails to execute any function, the corresponding failed function is marked.

[0088] Step S803: Generate a test result according to the failed function.

[0089] The preset task process includes all functions that have functional differences between the current RPA tool and the target RPA tool.

[0090] In the implementation mode of the present application, after the current RPA tool switches to the target RPA tool, the terminal device can use the target RPA tool to execute all functions in the preset task flow. When the target RPA tool executes a function in the order of the preset task flow, and the target RPA tool fails to execute the function, it can be considered that the target RPA tool still has compatibility issues with this function. At this time, this function can be marked as a failed function, and the name of the failed function and the corresponding code segment can be obtained to generate test results, providing a reference for subsequent troubleshooting and repair.

[0091] In some implementations of the present application, the above method may further include steps S901 to S904.

[0092] Step S901, periodically obtain a first configuration file of the current RPA tool and a third configuration file of the latest RPA tool.

[0093] Among them, the latest RPA tool is the latest version of the RPA tool.

[0094] In an implementation of the present application, the terminal device can periodically obtain the first configuration file of the current RPA tool and the third configuration file of the latest RPA tool. Specifically, the terminal device can periodically log in to the official website of the RPA tool used to obtain the configuration file of the latest RPA tool.

[0095] Step S902: Determine the latest version difference between the current RPA tool and the latest RPA tool according to the first configuration file and the third configuration file.

[0096] In the implementation manner of the present application, the detailed process of determining the latest version difference can refer to the above step S103 and the corresponding specific implementation steps, which will not be repeated here.

[0097] Step S903, generating the latest compatibility patch according to the latest version difference.

[0098] In the implementation manner of the present application, the detailed process of generating the latest compatibility patch can refer to the above-mentioned step S104 and the corresponding specific implementation steps, which will not be repeated here.

[0099] Step S904: store the latest compatibility patch in the first configuration file of the current RPA tool.

[0100] In the implementation manner of the present application, after obtaining the latest compatibility patch, the terminal device can store the latest compatibility patch in the first configuration file of the current RPA tool, so that when the current RPA tool is subsequently upgraded to the latest RPA tool, the latest compatibility patch can be directly obtained from the first configuration file without regenerating the latest compatibility patch. Therefore, it can save the user time to upgrade the current RPA tool to the latest RPA tool, thereby improving the user experience.

[0101] Figure 2 A schematic diagram of the structure of a version switching device of an RPA tool provided in an embodiment of the present application is shown. The version switching device 2 of the RPA tool can be configured on a terminal device. Specifically, the version switching device 2 of the RPA tool can include:

[0102] A first acquisition module 201 is used to acquire a first configuration file of the current RPA tool;

[0103] A second acquisition module 202 is used to acquire a second configuration file of a target RPA tool, where the target RPA tool has a different version from the current RPA tool;

[0104] A determination module 203, configured to determine a version difference between the current RPA tool and the target RPA tool according to the first configuration file and the second configuration file;

[0105] A generating module 204, configured to generate a compatibility patch according to the version difference;

[0106] The switching module 205 is used to switch the version of the current RPA tool according to the compatibility patch to obtain the target RPA tool.

[0107] The beneficial effect of the embodiment of the present application compared with the prior art is: the embodiment of the present application obtains the first configuration file of the current RPA tool and obtains the second configuration file of the target RPA tool, and then determines the version difference between the current RPA tool and the target RPA tool according to the first configuration file and the second configuration file, and then generates a compatibility patch according to the version difference, and then switches the version of the current RPA tool according to the compatibility patch to obtain the target RPA tool. The embodiment of the present application determines the version difference between the current RPA tool and the target RPA tool, generates a compatibility patch according to the version difference, and then switches the version through the compatibility patch, which can automatically complete the version switching and solve the compatibility problems that may occur during the version switching, thereby improving the user experience.

[0108] In some embodiments of the present application, the version differences include functional differences, format differences and language differences. The above-mentioned determination module 203 can also be used to: query the first function code, the first data format, and the first language of the current RPA tool according to the first configuration file; query the second function code, the second data format, and the second language of the target RPA tool according to the second configuration file; determine the functional difference according to the first function code and the second function code; determine the format difference according to the first data format and the second data format; determine the language difference according to the first language and the second language.

[0109] In some implementations of the present application, the generation module 204 may also be used to: formulate a compatibility strategy according to the version difference; and develop the compatibility patch according to the compatibility strategy.

[0110] In some embodiments of the present application, the above-mentioned generation module 204 can also be used to: formulate a code conversion strategy based on the functional differences; formulate a data format mapping strategy based on the format differences; formulate a language adjustment strategy based on the language differences; and synthesize the compatibility strategy based on the code conversion strategy, the data format mapping strategy and the language adjustment strategy.

[0111] In some embodiments of the present application, the version switching device 2 of the above-mentioned RPA tool may also include a conversion module, which is used to: query the second data format in the second configuration file; convert the data format of the compatibility patch into the second data format to obtain the converted compatibility patch.

[0112] In some embodiments of the present application, the version switching device 2 of the above-mentioned RPA tool may also include a testing module, which is used to: use the target RPA tool to execute all functions in a preset task process; when the target RPA tool fails to execute any function, mark the corresponding failed function; and generate test results based on the failed function.

[0113] In some embodiments of the present application, the version switching device 2 of the above-mentioned RPA tool may also include a second generation module, which is used to: regularly obtain a first configuration file of the current RPA tool and a third configuration file of the latest RPA tool; determine the latest version difference between the current RPA tool and the latest RPA tool based on the first configuration file and the third configuration file; generate the latest compatibility patch based on the latest version difference; and store the latest compatibility patch in the first configuration file of the current RPA tool.

[0114] like Figure 3 As shown, it is a schematic diagram of a terminal device provided in an embodiment of the present application. The terminal device 3 may include: a processor 301, a memory 302, and a computer program 303 stored in the memory 302 and executable on the processor 301, such as a version switching program of an RPA tool. When the processor 301 executes the computer program 303, the steps in the above-mentioned RPA tool version switching method embodiments are implemented, such as Figure 1 Alternatively, when the processor 301 executes the computer program 303, the functions of each module / unit in the above-mentioned device embodiments are realized, for example Figure 2 The first acquisition module 201, the second acquisition module 202, the determination module 203, the generation module 204, and the switching module 205 are shown.

[0115] The computer program may be divided into one or more modules / units, which are stored in the memory 302 and executed by the processor 301 to complete the present application. The one or more modules / units may be a series of computer program instruction segments capable of completing specific functions, which are used to describe the execution process of the computer program in the terminal device.

[0116] The terminal device may include, but is not limited to, a processor 301 and a memory 302. Those skilled in the art will appreciate that Figure 3 It is only an example of a terminal device and does not constitute a limitation of the terminal device. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the terminal device may also include input and output devices, network access equipment, buses, etc.

[0117] The processor 301 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0118] The memory 302 may be an internal storage unit of the terminal device, such as a hard disk or memory of the terminal device. The memory 302 may also be an external storage device of the terminal device, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the terminal device. Further, the memory 302 may also include both an internal storage unit of the terminal device and an external storage device. The memory 302 is used to store the computer program and other programs and data required by the terminal device. The memory 302 may also be used to temporarily store data that has been output or is to be output.

[0119] It should be noted that, for the convenience and brevity of description, the structure of the above-mentioned terminal device can also refer to the specific description of the structure in the method embodiment, which will not be repeated here.

[0120] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0121] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps in the version switching method of the above-mentioned RPA tool can be implemented.

[0122] An embodiment of the present application provides a computer program product. When the computer program product runs on a mobile terminal, the steps in the version switching method of the above-mentioned RPA tool can be implemented when the mobile terminal executes the computer program product.

[0123] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0124] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0125] In the embodiments provided in the present application, it should be understood that the disclosed devices / terminal equipment and methods can be implemented in other ways. For example, the device / terminal equipment embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0126] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0127] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0128] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0129] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A method for switching versions of an RPA tool, characterized in that: include: Get the first configuration file of the current RPA tool; Obtaining a second configuration file of a target RPA tool, where the target RPA tool has a different version from the current RPA tool; Determine, according to the first configuration file and the second configuration file, a version difference between the current RPA tool and the target RPA tool; generating a compatibility patch according to the version differences; Switching the version of the current RPA tool according to the compatibility patch to obtain the target RPA tool; The version difference includes a function difference, a format difference, and a language difference, and determining the version difference between the current RPA tool and the target RPA tool according to the first configuration file and the second configuration file includes: querying a first function code, a first data format, and a first language of the current RPA tool according to the first configuration file; querying a second function code, a second data format, and a second language of the target RPA tool according to the second configuration file; determining the functional difference according to the first functional code and the second functional code; Determining the format difference according to the first data format and the second data format; determining the language difference based on the first language and the second language; The step of generating a compatibility patch according to the version difference includes: Formulate a compatibility strategy based on the version differences; Developing the compatibility patch according to the compatibility strategy; The version differences include functional differences, format differences, and language differences, and formulating a compatibility strategy based on the version differences includes: Develop a code conversion strategy based on the functional differences described; Formulate a data format mapping strategy based on the format differences; Develop language adaptation strategies based on the described language differences; The compatibility policy is synthesized according to the code conversion policy, the data format mapping policy and the language adjustment policy.

2. The version switching method of the RPA tool according to claim 1, characterized in that: After generating a compatibility patch according to the version difference and before performing version switching on the current RPA tool according to the compatibility patch to obtain the target RPA tool, the method further includes: Query the second data format in the second configuration file; The data format of the compatibility patch is converted into the second data format to obtain a converted compatibility patch.

3. The version switching method of the RPA tool according to claim 1, characterized in that: After switching the version of the current RPA tool according to the compatibility patch to obtain the target RPA tool, the method further includes: Utilize the target RPA tool to execute all functions in the preset task process; When the target RPA tool fails to execute any function, mark the corresponding failed function; A test result is generated based on the failed function.

4. The version switching method of the RPA tool according to claim 1, characterized in that: The method further comprises: Regularly obtain the first configuration file of the current RPA tool and the third configuration file of the latest RPA tool; Determine, according to the first configuration file and the third configuration file, a latest version difference between the current RPA tool and the latest RPA tool; Generate the latest compatibility patch according to the latest version difference; The latest compatibility patch is stored in the first configuration file of the current RPA tool.

5. A version switching device for an RPA tool, characterized in that: include: A first acquisition module, used to acquire a first configuration file of the current RPA tool; A second acquisition module is used to acquire a second configuration file of a target RPA tool, where the target RPA tool has a different version from the current RPA tool; A determination module, configured to determine a version difference between the current RPA tool and the target RPA tool according to the first configuration file and the second configuration file; A generation module, used for generating a compatibility patch according to the version difference; A switching module, configured to switch the version of the current RPA tool according to the compatibility patch to obtain the target RPA tool; The version differences include functional differences, format differences and language differences, and the determination module is further used for: querying a first function code, a first data format, and a first language of the current RPA tool according to the first configuration file; querying a second function code, a second data format, and a second language of the target RPA tool according to the second configuration file; determining the functional difference according to the first functional code and the second functional code; Determining the format difference according to the first data format and the second data format; determining the language difference based on the first language and the second language; Wherein, the generating module is also used for: Formulate a compatibility strategy based on the version differences; Developing the compatibility patch according to the compatibility strategy; The version differences include functional differences, format differences and language differences, and the generation module is further used for: Develop a code conversion strategy based on the functional differences described; Formulate a data format mapping strategy based on the format differences; Develop language adaptation strategies based on the described language differences; The compatibility policy is synthesized according to the code conversion policy, the data format mapping policy and the language adjustment policy.

6. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the steps of the version switching method of the RPA tool as claimed in any one of claims 1 to 4 are implemented.

7. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the version switching method of the RPA tool as claimed in any one of claims 1 to 4 are implemented.

Images