Disclosure of Invention
In view of the above, there is a need to provide a method, an apparatus, a computer device and a storage medium for processing services based on page operations, which are capable of effectively compatible with multiple financial processing services.
A business processing method based on page operation is characterized in that the method comprises the following steps:
acquiring a target service currently waiting for processing, and determining at least one target service page needing to be operated in the processing process of the target service and a page operation sequence corresponding to the at least one target service page;
searching at least one target page packaging unit corresponding to each target service page from a page packaging unit pool; the page packaging unit pool comprises a plurality of page packaging units, and each page packaging unit correspondingly comprises a service page for performing service processing and a page processing instruction corresponding to the service page;
sequencing the at least one target page packaging unit according to the page operation sequence to obtain a processing unit sequence corresponding to the target service;
and reading the service page and page processing instruction in each target page packaging unit in the processing unit sequence, and processing the target service according to the service page and page processing instruction in each target page packaging unit in sequence based on the processing unit sequence.
In one embodiment, the page encapsulating unit includes a first service page encapsulating unit, and the method further includes:
acquiring general service actions corresponding to all service types;
acquiring a first service page corresponding to the general service action;
determining a first operation instruction and a first jump instruction corresponding to the first service page, and taking the first operation instruction and the first jump instruction as page processing instructions corresponding to the first service page; the first jump instruction is used for entering a next service page; the first operation instruction comprises first operation content, a first operation interface, an interface calling instruction and a first execution instruction; the interface calling instruction is used for acquiring interface parameters; the first execution instruction completes corresponding first operation content through the first operation interface based on the interface parameter;
and encapsulating the first service page and the page processing instruction corresponding to the first service page to obtain a first service page encapsulation unit.
In one embodiment, the page encapsulating unit further includes a second service page encapsulating unit, and the method further includes:
determining non-universal service actions corresponding to different service types respectively; the non-universal service action is a service action except the universal service action in all service actions;
acquiring second service pages corresponding to the non-universal service actions respectively;
determining a second operation instruction and a second jump instruction corresponding to each second service page, and taking the second operation instruction and the second jump instruction as page processing instructions corresponding to the second service pages; the second jump instruction is used for entering a next service page or entering an end page; the second operation instruction comprises second operation content, a second operation interface and a second execution instruction, and the second execution instruction completes the corresponding second operation content through the second operation interface;
and encapsulating the second service page and the page processing instruction corresponding to the second service page to obtain a second service page encapsulation unit.
In one embodiment, acquiring a target service currently waiting for processing, and determining at least one target service page that needs to be operated in a processing process of the target service and a page operation sequence corresponding to the at least one target service page, includes:
acquiring a target service from a service list waiting for processing;
judging the target service type of the target service, and determining the service action corresponding to the target service according to the target service type;
acquiring a target service page needing to be operated in the processing process of the target service based on the service action corresponding to the target service; the business page comprises at least one first business page;
and arranging the target service pages based on the service action corresponding to the target service to obtain a page operation sequence corresponding to the target service pages.
In one embodiment, the page encapsulating unit further includes a result encapsulating unit, where the result encapsulating unit includes the result page and result information, and the result information is used to indicate that the target service currently being processed is ended, and send a result message indicating whether the target service currently being processed is successfully processed.
In one embodiment, the target service is an electronic invoice processing service, and the bill processing service is any one of a value-added tax special invoice downloading service, a value-added tax general invoice downloading service and a value-added tax invoice deduction and checking service.
A service processing apparatus operating based on a page, the apparatus comprising:
the page acquisition module is used for acquiring a target service currently waiting for processing, and determining at least one target service page needing to be operated in the processing process of the target service and a page operation sequence corresponding to the at least one target service page;
the searching module is used for searching at least one target page packaging unit corresponding to each target service page from a page packaging unit pool; the page packaging unit pool comprises a plurality of page packaging units, and each page packaging unit correspondingly comprises a service page for performing service processing and a page processing instruction corresponding to the service page;
the sequencing module is used for sequencing the at least one target page packaging unit according to the page operation sequence to obtain a processing unit sequence corresponding to the target service;
and the processing module is used for reading the service pages and the page processing instructions in each target page packaging unit in the processing unit sequence, and processing the target service according to the service pages and the page processing instructions in each target page packaging unit in sequence based on the processing unit sequence.
In one embodiment, the page encapsulating unit includes a first service page encapsulating unit, and the apparatus further includes:
the encapsulation module is used for acquiring the general service actions corresponding to all service types; acquiring a first service page corresponding to the general service action; determining a first operation instruction and a first jump instruction corresponding to the first service page, and taking the first operation instruction and the first jump instruction as page processing instructions corresponding to the first service page; the first jump instruction is used for entering a next service page; the first operation instruction comprises first operation content, a first operation interface, an interface calling instruction and a first execution instruction; the interface calling instruction is used for acquiring interface parameters; the first execution instruction completes corresponding first operation content through the first operation interface based on the interface parameter; and encapsulating the first service page and the page processing instruction corresponding to the first service page to obtain a first service page encapsulation unit.
A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor when executing the computer program implements the steps of:
acquiring a target service currently waiting for processing, and determining at least one target service page needing to be operated in the processing process of the target service and a page operation sequence corresponding to the at least one target service page;
searching at least one target page packaging unit corresponding to each target service page from a page packaging unit pool; the page packaging unit pool comprises a plurality of page packaging units, and each page packaging unit correspondingly comprises a service page for performing service processing and a page processing instruction corresponding to the service page;
sequencing the at least one target page packaging unit according to the page operation sequence to obtain a processing unit sequence corresponding to the target service;
and reading the service page and page processing instruction in each target page packaging unit in the processing unit sequence, and processing the target service according to the service page and page processing instruction in each target page packaging unit in sequence based on the processing unit sequence.
A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of:
acquiring a target service currently waiting for processing, and determining at least one target service page needing to be operated in the processing process of the target service and a page operation sequence corresponding to the at least one target service page;
searching at least one target page packaging unit corresponding to each target service page from a page packaging unit pool; the page packaging unit pool comprises a plurality of page packaging units, and each page packaging unit correspondingly comprises a service page for performing service processing and a page processing instruction corresponding to the service page;
sequencing the at least one target page packaging unit according to the page operation sequence to obtain a processing unit sequence corresponding to the target service;
and reading the service page and page processing instruction in each target page packaging unit in the processing unit sequence, and processing the target service according to the service page and page processing instruction in each target page packaging unit in sequence based on the processing unit sequence.
According to the page operation-based service processing method, device, computer equipment and storage medium, since service pages possibly related to a target service are all packaged into page packaging units in advance, in a specific target service processing process, only the service pages needing to be operated in the processing process of each target service need to be obtained, the target page packaging units corresponding to the target service pages are searched from a page packaging unit pool, then the target page packaging units are sequenced according to a page operation sequence, a processing unit sequence corresponding to the target service is obtained, and the target service is processed based on the processing unit sequence. For a plurality of target services with certain similarity and different differences, the page packaging unit pool can be used for including service pages and corresponding operations which may be related to the plurality of target services, and for specific target services, the corresponding page packaging units can be taken out from the page packaging unit pool at any time to be freely combined for processing, and an operation process does not need to be designed for each target service, so that the convenience and compatibility of target service processing are greatly improved.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
According to the tax management system of 'controlling tax with ticket' and 'controlling account with ticket' in China, the invoice management is the central importance of financial work of enterprises. The term "controlling tax with invoice" refers to enhancing the concept of tax law and the awareness of tax payment to the utmost extent through strict invoice management, thereby maximizing the tax payment. At present, financial operations of enterprises relate to a large amount of repetitive work, such as logging in a value-added tax invoice service platform to download value-added tax special invoices and general invoices, executing deduction and check on incoming tax invoices and the like. Similar to these works, the existing processing method is usually solved by manual operation, value-added tax special tickets and general tickets are downloaded by logging in a website every day, deduction and check of incoming tax invoices are performed every month, and the like. In response to the urgent requirement of high-efficiency invoice management, the invoice needs to be managed in a standardized and flow manner, the automatic support is improved, the manual efficiency of tax management is improved, and meanwhile, the accuracy of invoice management is improved through automation.
The business processing method based on page operation provided by the application can be applied to the application environment shown in fig. 1. Wherein the service processing terminal 102 can communicate with the server 104 through a network. When a specific target service is processed, the service processing terminal 102 determines a service page to be operated according to the current specific processing target service, then finds a corresponding page encapsulation unit from the page encapsulation unit pool based on the specific service page to be operated by the current target service, sorts the page encapsulation unit to obtain a processing unit sequence for the current target service, and executes the processing unit sequence to realize automatic processing of the current target service. The pool of page wrapper units is located in the server 104. The service processing terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and mainly provides visualization of a current target service processing flow, or initiates a processing request, and the server 104 may be implemented by an independent server or a server cluster formed by a plurality of servers.
The present application is a scheme obtained by improving some problems existing in the above scenario. The network attack identification method provided by the embodiments of the present application may be executed by the service processing terminal 102 or the server 104 alone, or may be executed by cooperation of the service processing terminal 102 and the server 104. Before describing the business processing method based on page operation in the present application, the following explanations are first made for some terms involved in the embodiments of the present application:
target service: page operations with specific purposes, aimed at obtaining specific business results;
service page: a network page which needs to be operated and processed in the process of executing the target service;
a page processing instruction: the system is used for completing corresponding operation actions on a certain business page;
a page packaging unit: correspondingly, the system comprises a service page for performing service processing and a page processing instruction corresponding to the service page, and is used for completing a specific step in the process of executing the target service;
the processing unit sequence is as follows: and sequencing the page packaging units involved in the target service processing to obtain a page packaging unit sequence, wherein the page packaging unit sequence is used for processing the target service to obtain a corresponding service result.
In one embodiment, as shown in fig. 2, a method for automatically processing a service based on a page operation is provided, which is described by taking the method as an example of being applied to a computer device (such as the service processing terminal 102 or the server 104 in fig. 1), and the method for processing the service based on the page operation includes the following steps:
step S202, obtaining the target service waiting for processing currently, and determining at least one target service page needing to be operated in the processing process of the target service and the page operation sequence corresponding to the at least one target service page.
Specifically, when the service processing method is used to automatically process a target service, when the computer device is a server, it first needs to obtain a specific target service to be processed from a service processing terminal, and when the computer device is a service processing terminal, it obtains the specific target service to be processed locally. Then, the computer device identifies the target service, determines the service pages involved in the processing process of the target service, and correspondingly performs the operation steps required to be performed on each service page. For example, suppose that for a particular invoice download service, the service pages involved are: after the invoice downloading service is read, the computer equipment determines the login page and the download page which need to be processed, the login operation needed to be carried out on the login page, the download operation needed to be carried out on the download page and the like based on the invoice downloading service, and meanwhile, the login page and the download page have a clear sequence of operation.
Step S204, at least one target page packaging unit corresponding to each target service page is searched from the page packaging unit pool; the page packaging unit pool comprises a plurality of page packaging units, and each page packaging unit correspondingly comprises a service page for performing service processing and a page processing instruction corresponding to the service page.
Specifically, according to the service page corresponding to the specifically processed target service, the target page encapsulation unit corresponding to the service page can be taken out from the page encapsulation unit pool. The page packaging unit pool comprises a plurality of non-repetitive page packaging units, each page packaging unit is packaged with a service page and a page processing instruction corresponding to the service page, and for each page packaging unit, certain operation can be performed on the current service page based on the page processing instruction so as to complete a specific action in the target service processing process.
Further, the page packaging units in the page packaging unit pool are obtained based on a plurality of service classes. Although the specific service processing processes corresponding to a plurality of similar service classes have a certain difference, the pages involved in the processing processes have little difference, and by extracting the union of the service pages corresponding to the service classes, the service pages involved in the service classes and the corresponding page processing instructions can be correspondingly packaged to form a page packaging unit, so that a page packaging unit pool is formed. Based on the page packaging unit pool, the services in a plurality of similar service types can be processed without additionally setting a processing flow for each service type.
For example, for the target service a, the service pages involved include page 1, page 2, and page 3, and for the target service B, the service pages involved include page 1, page 3, and page 4. Therefore, for the target services a and B, the union of the service pages of the two services is page 1, page 2, page 3, and page 4, and as long as the page encapsulation unit pool includes the page encapsulation unit 1, the page encapsulation unit 2, the page encapsulation unit 3, and the page encapsulation unit 4 respectively corresponding to the page 1, the page 2, the page 3, and the page 4, the computer device can automatically process the target service a and the target service B without setting a processing flow for the target service a and the target service B respectively.
Step S206, at least one target page packaging unit is sequenced according to the page operation sequence, and a processing unit sequence corresponding to the target service is obtained.
Specifically, after obtaining each target page encapsulation unit corresponding to the target service, the computer device further needs to sort each target page encapsulation unit according to an operation sequence of the target service based on the service page, so as to obtain a specific processing unit sequence. Therefore, each service page in the processing unit sequence corresponds to each service page needing to be operated in the target service processing process.
For example, for a specific bill downloading process, the operation page includes a login page and a download page, the order of the login page and the download page is clear, and the target page encapsulation units are sorted according to the order in the acquisition processing unit sequence.
Step S208, reading the service page and page processing instruction in each target page packaging unit in the processing unit sequence, and processing the target service according to the service page and page processing instruction in each target page packaging unit in sequence based on the processing unit sequence.
Specifically, based on the processing unit sequence, the computer device may read each target page encapsulation unit in the processing unit sequence in sequence, and process the service page based on the page processing instruction in the target page encapsulation unit until all target page encapsulation units in the processing unit sequence are executed. For example, for the above bill downloading process, after acquiring the corresponding sequence of processing units, the corresponding processing process of the computer device is as follows: reading a first page packaging unit (corresponding to a login page) in a processing unit sequence, processing a service page in the unit based on a page processing instruction in the first page packaging unit, then reading a second page packaging unit (corresponding to a download page) in the processing unit sequence, processing the service page in the unit based on the page processing instruction in the second page packaging unit until all the page packaging units in the processing unit sequence are processed, and obtaining a bill downloading result.
Further, when the computer device is a service processing terminal, the processing result corresponding to the target service may be correspondingly displayed on the service processing terminal, and when the computer device is a server, the processing result corresponding to the target service may be transmitted to the service processing terminal via the server for corresponding display. According to the service processing method based on page operation, since service pages possibly related to target services are all packaged into page packaging units in advance, in the specific target service processing process, only the service pages needing to be operated in the processing process of each target service need to be obtained, the target page packaging units corresponding to the target service pages are searched from the page packaging unit pool, then the target page packaging units are sequenced according to the page operation sequence, the processing unit sequence corresponding to the target services is obtained, and the target services are processed based on the processing unit sequence. For a plurality of target services with certain similarity and different differences, the page packaging unit pool can be used for including service pages and corresponding operations which may be related to the plurality of target services, and for specific target services, the corresponding page packaging units can be taken out from the page packaging unit pool at any time to be freely combined for processing, and an operation process does not need to be designed for each target service, so that the convenience and compatibility of target service processing are greatly improved.
In one embodiment, the page encapsulation unit includes a first service page encapsulation unit, and the method further includes: acquiring general service actions corresponding to all service types; acquiring a first service page corresponding to the general service action; determining a first operation instruction and a first jump instruction corresponding to a first service page, and taking the first operation instruction and the first jump instruction as page processing instructions corresponding to the first service page; the first jump instruction is used for entering the next service page; the first operation instruction comprises first operation content, a first operation interface, an interface calling instruction and a first execution instruction; the interface calling instruction is used for acquiring interface parameters; the first execution instruction is based on the interface parameters, and corresponding first operation content is completed through a first operation interface; and encapsulating the first service page and the page processing instruction corresponding to the first service page to obtain a first service page encapsulation unit.
Specifically, for each service category in the embodiment, the same operation page may exist in the specific service action corresponding to each service category. For example, in a plurality of specific service processing procedures, the first page to be processed is a login page, and at this time, the login page is processed to belong to a common service action corresponding to all service classes. In this embodiment, for a general service action, a corresponding service page, for example, a login page, and a first operation instruction and a first jump instruction corresponding to the service page are determined. The first operation instruction is used for processing the login page and comprises first operation content, a first operation interface, a first interface calling instruction and a first execution instruction. Taking the login page as an example, the page encapsulation unit corresponding to the universal service action includes corresponding first page information (such as a page website of the login page or access information), and the first operation content is to acquire account password information logged in by the user for logging in; the first operation interface is an interface position for inputting account password information on a login page; the first interface calling instruction is used for acquiring corresponding account password information from the outside (such as other security platforms or identity authentication devices); the first execution instruction is to input parameters such as account number and password information acquired by calling the first interface calling instruction into the first operation interface, and then enter the next service page through the first jump instruction, for example, a specific bill downloading page.
In the embodiment, the first service page corresponding to the general service action is encapsulated once and put into the unit pool, and the specific services corresponding to all service classes can be processed by using the general first service page encapsulation unit, so that the compatibility of the service processing system is improved, and the complexity and the development cost of the service processing system are reduced.
In one embodiment, the page encapsulation unit further includes a second service page encapsulation unit, and the method further includes: determining non-universal service actions corresponding to different service types respectively; the non-universal service action is a service action except the universal service action in all the service actions; acquiring second service pages corresponding to the non-universal service actions respectively; determining a second operation instruction and a second jump instruction corresponding to each second service page, and taking the second operation instruction and the second jump instruction as page processing instructions corresponding to the second service pages; the second jump instruction is used for entering a next service page or entering an end page; the second operation instruction comprises second operation content, a second operation interface and a second execution instruction, and the second execution instruction completes the corresponding second operation content through the second operation interface; and encapsulating the second service page and the page processing instruction corresponding to the second service page to obtain a second service page encapsulation unit.
Specifically, the service categories in this embodiment are different, and specific service actions corresponding to the service categories have service pages that are not completely the same. For example, for the service class a, the service pages related in the processing process include P1, P2, P3, and P4, meanwhile, the service page corresponding to the service class B includes P1, P2, and P4, and the service page corresponding to the service class C includes P1, P3, and P5. Therefore, P1 is the first service page corresponding to the generic service action, P2, P3, and P4 are service pages shared by two service classes, and P5 is a service page unique to service class C. At this time, P2, P3, P4 and P5 are the second service pages corresponding to the non-generic service actions.
And for the page packaging unit corresponding to the second service page, the page packaging unit comprises the second service page, and a second operation instruction and a second jump instruction corresponding to the packaged second service page. The second operation instruction is used for completing corresponding page operation on a second service page, and the second jump instruction is used for indicating to enter a next service page or an end page. And for each second service page, second operation content needing to be executed is corresponding to the second service page, and the second operation content is completed by executing the second operation interface. For example, in an invoice deduction checking service, the operation content corresponding to one second service page is that the invoice file is uploaded through the second operation interface and checking is performed on the current page, and then the next step is performed. In the embodiment, the general service actions and the non-general service actions are distinguished, each page encapsulation unit in the page encapsulation unit pool can be effectively utilized, the number of required encapsulation units can be reduced, specific services of various service types are processed through the minimum page encapsulation units, the effectiveness and the maintainability of service processing are effectively improved, and the load of a system is reduced.
In one embodiment, acquiring a target service currently waiting for processing, and determining at least one target service page that needs to be operated in a processing process of the target service and a page operation sequence corresponding to the at least one target service page, includes: acquiring a target service from a service list waiting for processing; judging the target service type of the target service, and determining the service action corresponding to the target service according to the target service type; acquiring a target service page needing to be operated in the processing process of the target service based on the service action corresponding to the target service; the service page comprises at least one first service page; and arranging the target service pages based on the service actions corresponding to the target service to obtain a page operation sequence corresponding to the target service pages.
Specifically, because a plurality of page encapsulation units related to each service class already exist in the page encapsulation unit pool, for a specific target service to be processed, based on the service class of the target service, the service action required for processing the target service can be confirmed, and then each target service page to be operated is determined. The general service action is an operation that each target service needs to be performed in the processing process, so each target service page necessarily includes a first service page, and a second service page corresponding to the first service page and a page operation corresponding to the second service page can be further determined based on the service class to which the specific target service belongs. Based on the information, each target page packaging unit corresponding to the page packaging unit can be taken out from the page packaging unit pool, and each target page packaging unit is sequenced, so that a processing unit sequence capable of automatically processing specific target service can be obtained
In the embodiment, the target service page and the corresponding page operation sequence involved in the service processing process are easily determined based on the service category corresponding to the target service, so that the target service is conveniently and quickly processed without additionally configuring other processing programs.
In one embodiment, the page encapsulating unit further includes a result encapsulating unit, where the result encapsulating unit includes a result page and result information, and the result information is used to indicate that the target service currently being processed is ended, and send a result message indicating whether the target service currently being processed is successfully processed.
Specifically, for the target service, in the process of performing the specific processing, in order to determine the validity of the processing process, the embodiment further includes a result encapsulating unit, where the result encapsulating unit has a result page and result information, and it can be known whether the current target service is successfully processed through the result information in the result encapsulating unit.
In the embodiment, the result encapsulation unit is used for effectively judging the processing result of the target task, so that the effectiveness and the accuracy of the business processing process can be greatly improved.
In one embodiment, the target service is an electronic invoice processing service, and the bill processing service is any one of a value-added tax special invoice downloading service, a value-added tax general invoice downloading service and an invoice deduction checking service.
Specifically, in this embodiment, the service category is generally various services related to the financial system, which often require repeated labor, such as a value-added tax special invoice downloading service, a value-added tax general invoice downloading service, and an invoice deduction checking service.
In the embodiment, the service categories respectively have the same operation flow, the corresponding operation pages are financial operation pages, and the cost required for completing the specific services in the categories can be greatly reduced by packaging the service pages needing to be operated.
It should be understood that, although the steps in the flowchart of fig. 2 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a portion of the steps in fig. 2 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least a portion of the other steps or stages.
In one embodiment, a financial automation tool based on an RPA technology is provided, and a set of RPA financial automation processing system is constructed based on a selenium technology by referring to an automation testing thought. The system realizes the fixed-time and automatic completion of designated financial work by simulating the manual operations of downloading value-added tax special tickets, general tickets and the like on the browser page. Compared with the existing manual processing, the method has the advantages that manpower is liberated from a large amount of repetitive financial work, the processing efficiency is improved, and meanwhile risks of making mistakes, not performing in time and the like are avoided. Furthermore, a set of framework suitable for the tax automatic processing system is provided, which can be used for realizing the automation of value-added tax special bill downloading, common bill downloading and income tax invoice deduction and check-out, and ensures the feasibility of automation of more financial operation processes. The selenium technology is an open-source automation framework and supports all web-based management task automation; the method is widely used for automatic testing of Web application programs.
Specifically, the detailed technical solution corresponding to the financial processing system of the embodiment is described as follows: 1) the financial processing system of the embodiment allows different financial operation flows to be regarded as independent task cases to be packaged and called, so that an external system can carry out value-added tax special bill downloading, general bill downloading, income tax invoice deduction and checking and the like through a calling interface, and after the external system calls the interface to carry out corresponding operation, the financial processing system of the embodiment generates a task record in a 'to-be-processed' state in a database; 2) the financial processing system of the embodiment executes the task record of the 'to-be-processed' state every 5 minutes in an asynchronous single-thread polling manner, calls and records the corresponding operation class, executes an instruction based on a selenium technology to simulate an operation browser, and updates the state of the task record after the execution is finished; 3) the financial processing system of the embodiment opens a calling interface for task record inquiry to an external system, and the external system can inquire the task record state in real time.
As shown in fig. 3, is a specific deployment architecture diagram of the above-described embodiment. The method comprises the following steps that a calling system (such as a service system) calls an interface of a financial RPA system, a specific service type processing request is sent, and after the RPA system receives the request, a task record in a to-be-processed state is generated in a database; the asynchronous single-thread polling database of the financial RPA system records the task in the 'to-be-processed' state, accesses an external system (namely a bill service platform in figure 3, such as a value-added tax invoice service platform), and automatically executes corresponding service class tasks; further, if the financial RPA system and the website accessed by the browser can not directly carry out network interaction, the financial RPA system uses an agent to solve the problem; if the file interaction exists, sftp technology is adopted, such as invoice file interaction after downloading.
Fig. 4 is a system architecture diagram of a business automation processing method based on page operations in an embodiment. Specifically, the following are included: firstly, according to the Service action corresponding to each Service type, different financial operation flows are regarded as independent task cases (Service) to be packaged and called, when an external system calls an interface of a financial RPA system, a task record generated by a Controller contains the corresponding Service type, and accurate Service can be positioned according to a type field when the system polls the task record. For example, the special ticket downloading process is used as an independent Service to be packaged and called, and when the specific Service of the type is inquired, the Service corresponding to the special ticket downloading can be accurately positioned.
Secondly, according to a Page-Object design mode, subdividing the logic flow of each task case into Page dimensions (namely determining a business Page corresponding to each business type), for example, when manually downloading a special ticket from a browser, inputting user information on a login Page for login, jumping to a special ticket downloading Page from a homepage, and clicking a downloading button on a filling condition of the special ticket downloading Page. The logic of the special ticket downloading is divided into three Page types (namely Page packaging quality) for maintenance, so that the maintainability can be improved, and the operation of logging in the Page can be repeatedly used in other task cases.
And finally, encapsulating the RPA tool class according to the selenium technology, ensuring that each method of the tool class corresponds to one step of manual page operation, realizing abstract encapsulation of the same operation, and encapsulating and processing abnormal conditions.
The above-mentioned architecture diagram in this embodiment has borrowed the automation test thinking, and its specific thinking is as follows: (1) the method comprises the steps that different financial operation processes are regarded as independent task cases (services) to be packaged and called, when a system calls an interface of a financial RPA system, a task record generated by a Controller contains a corresponding Service type, and accurate services can be positioned according to type fields when the system polls the task record; (2) according to the Page-Object design mode, the logic flow of each task case is subdivided into Page dimensions, for example, when a user manually downloads a special ticket from a browser, the user needs to input user information on a login Page for login, jump to a special ticket downloading Page from a homepage, and click a downloading button on a filling condition of the special ticket downloading Page. The logic of downloading the special ticket is divided into three Page maintenance types, so that the maintainability can be improved, and the operation of logging in the Page can be repeatedly used in other task cases; (3) and (3) encapsulating the RPA tool class according to the selenium technology, ensuring that each method of the tool class corresponds to one step of manual page operation, realizing abstract encapsulation of the same operation, and encapsulating and processing abnormal conditions.
Fig. 5 is a flowchart of a system for downloading special tickets by using a business automation processing method based on page operation in an embodiment. Wherein, the flow of each task case is consistent, and the download of the special ticket is taken as an example: firstly, an external task calls a request interface for downloading a special ticket, and the financial RPA system generates a task record in a pending state and stores the task record in a database. Secondly, the financial RPA system asynchronously and single-threaded polls the task records to be processed every 5 minutes, locates the records to a special ticket download Service, calls a browser through the RPA tool class, executes corresponding instructions, and executes the state of finishing updating the task records. And finally, calling a query interface of the task record by the system at intervals, querying the state of the task record in real time, and downloading the invoice file from the SFTP if the record state is 'processing success'. The special invoice downloading process corresponding to fig. 5 may also be applicable to other types of financial service processing, such as general invoice downloading service or income tax invoice deduction and checking service, and the RPA processing procedures corresponding to different service categories are different, but the system response processes are consistent, which is not described in this embodiment.
As shown in fig. 6, the state diagram is a state diagram of task records of a service automation processing method based on page operations in an embodiment, and when a system calls an interface of a financial RPA system, the financial RPA system generates a task record in a "to-be-processed" state in a database; the asynchronous single thread polling of the financial RPA system is used for polling the task record to be processed, and the record state is synchronously updated to be processed during processing; the recording status is updated to "processing success" or "processing failure" according to the execution result. In this embodiment, the RPA system updates the state of the task record according to a specific processing flow, so as to implement real-time monitoring on the task record.
In one embodiment, as shown in fig. 7, there is provided a business automation processing device based on page operation, including: a page obtaining module 702, a searching module 704, a sorting module 706, and a processing module 708, wherein:
the page obtaining module 702 is configured to obtain a target service currently waiting for processing, and determine at least one target service page that needs to be operated in a processing process of the target service and a page operation step corresponding to the at least one target service page.
A searching module 704, configured to search at least one target page encapsulation unit corresponding to each target service page from the page encapsulation unit pool; the page packaging unit pool comprises a plurality of page packaging units, and each page packaging unit correspondingly comprises a service page for performing service processing and a page processing instruction corresponding to the service page.
The sorting module 706 is configured to sort the at least one target page encapsulation unit according to the page operation order, and obtain a processing unit sequence corresponding to the target service.
The processing module 708 is configured to read the service page and the page processing instruction in each target page encapsulation unit in the processing unit sequence, and sequentially process the target service according to the service page and the page processing instruction in each target page encapsulation unit based on the processing unit sequence.
According to the page operation-based service processing device, since service pages possibly related to the target service are all packaged into page packaging units in advance, in the specific target service processing process, only the service pages needing to be operated in the processing process of each target service need to be obtained, the target page packaging units corresponding to the target service pages are searched from the page packaging unit pool, then the target page packaging units are sequenced according to page operation steps, a processing unit sequence corresponding to the target service is obtained, and the target service is processed based on the processing unit sequence. For a plurality of target services with certain similarity and different differences, the page packaging unit pool can be used for including service pages and corresponding operations which may be related to the plurality of target services, and for specific target services, the corresponding page packaging units can be taken out from the page packaging unit pool at any time to be freely combined for processing, and an operation process does not need to be designed for each target service, so that the convenience and compatibility of target service processing are greatly improved.
In one embodiment, the page packaging unit comprises a first service page packaging unit, and the device further comprises a packaging module, wherein the packaging module is used for acquiring general service actions corresponding to all service types; acquiring a first service page corresponding to the general service action; determining a first operation instruction and a first jump instruction corresponding to a first service page, and taking the first operation instruction and the first jump instruction as page processing instructions corresponding to the first service page; the first jump instruction is used for entering the next service page; the first operation instruction comprises first operation content, a first operation interface, an interface calling instruction and a first execution instruction; the interface calling instruction is used for acquiring interface parameters; the first execution instruction is based on the interface parameters, and corresponding first operation content is completed through a first operation interface; and encapsulating the first service page and the page processing instruction corresponding to the first service page to obtain a first service page encapsulation unit.
In the embodiment, the first service page corresponding to the general service action is encapsulated once and put into the unit pool, and the specific services corresponding to all service classes can be processed by using the general first service page encapsulation unit, so that the compatibility of the service processing system is improved, and the complexity and the development cost of the service processing system are reduced.
In one embodiment, the encapsulation module is further configured to: determining non-universal service actions corresponding to different service types respectively; the non-universal service action is a service action except the universal service action in all the service actions; acquiring second service pages corresponding to the non-universal service actions respectively; determining a second operation instruction and a second jump instruction corresponding to each second service page, and taking the second operation instruction and the second jump instruction as page processing instructions corresponding to the second service pages; the second jump instruction is used for entering a next service page or entering an end page; the second operation instruction comprises second operation content, a second operation interface and a second execution instruction, and the second execution instruction completes the corresponding second operation content through the second operation interface; and encapsulating the second service page and the page processing instruction corresponding to the second service page to obtain a second service page encapsulation unit.
In the above embodiment, the generic service actions and the non-generic service actions are distinguished, each page encapsulation unit in the page encapsulation unit pool can be effectively utilized, the number of required encapsulation units can be reduced, and the specific services of each service category are processed through the fewest page encapsulation units, so that the effectiveness of service processing is effectively improved, and the load of the system is reduced.
In one embodiment, the page obtaining module is further configured to: acquiring a target service from a service list to be processed; judging the target service type of the target service, and determining the service action corresponding to the target service according to the target service type; acquiring a target service page needing to be operated in the processing process of the target service based on the service action corresponding to the target service; the service page comprises at least one first service page; and arranging the target service pages based on the service actions corresponding to the target service to obtain page operation steps corresponding to the target service pages.
In the embodiment, the target service page and the corresponding page operation steps involved in the service processing process are easily determined based on the service category corresponding to the target service, so that the target service is conveniently and quickly processed without additionally configuring other processing programs.
In one embodiment, the page encapsulating unit further includes a result encapsulating unit, where the result encapsulating unit includes a result page and result information, and the result information is used to indicate that the target service currently being processed is ended, and send a result message indicating whether the target service currently being processed is successfully processed.
In the embodiment, the result encapsulation unit is used for effectively judging the processing result of the target task, so that the effectiveness and the accuracy of the business processing process can be greatly improved.
In one embodiment, the target service is an electronic invoice processing service, and the bill processing service is any one of a value-added tax special invoice downloading service, a value-added tax general invoice downloading service and a value-added tax invoice deduction and checking service.
In the embodiment, the service categories respectively have the same operation flow, the corresponding operation pages are financial operation pages, and the cost required for completing the specific services in the categories can be greatly reduced by packaging the service pages needing to be operated.
For specific limitations of the service automation processing device based on page operations, reference may be made to the above limitations of the service automation processing method based on page operations, and details are not described here. The modules in the page-based operation business automation processing device can be wholly or partially realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 8. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing business processing data based on page operation. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a business processing method based on page operations.
Those skilled in the art will appreciate that the architecture shown in figure Y is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as a particular computing device may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is further provided, which includes a memory and a processor, the memory stores a computer program, and the processor implements the steps of the above method embodiments when executing the computer program.
In an embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.