Information deregistration method, device and equipment based on RPA robot, and storage medium

Abstract

The present disclosure provides an information deregistration method and device based on an RPA robot, an equipment and a storage medium, which can be applied to the field of computer technology or the field of financial technology. The method comprises: in response to an information deregistration request, creating a virtual account of a management personnel, wherein the information deregistration request is generated based on personnel change of a managed object; logging into a personnel information management platform according to the virtual account to obtain a first check source file, wherein the first check source file at least includes identification information of the managed object; logging into a personnel authority management system according to the virtual account to obtain a second check source file; comparing the second check source file with the first check source file according to the identification information of the managed object to obtain an account to be deregistered in the second check source file; and showing the management personnel with deregistration information associated with the account to be deregistered, so that the management personnel deregisters the information to be deregistered.

Description

Technical Field

[0001] This disclosure relates to the fields of computer technology or financial technology, and in particular to an information cancellation method, apparatus, device, medium and program product based on RPA robot. Background Technology

[0002] Effective human resource management has become a key element in enhancing the competitiveness of enterprises undergoing digital transformation. Human resource management can involve tasks such as account cancellation and permission revocation. Robotic Process Automation (RPA) robots can simulate human repetitive operations, automatically executing process tasks according to rules, thus improving business workflows. In realizing the concept of this invention, the inventors discovered the following problems in related technologies: An administrator's account can generally only log in once at a time, but when an RPA robot handles business, it uses the administrator's account and permissions. This results in the RPA robot and the administrator competing for account space, reducing the efficiency of business processing. Summary of the Invention

[0003] In view of the above problems, this disclosure provides information deregistration methods, apparatus, devices, media and program products based on RPA robots.

[0004] One aspect of this disclosure provides an information cancellation method based on an RPA robot, comprising: responding to an information cancellation request, creating a virtual account for an administrator, wherein the information cancellation request is generated based on personnel changes of the managed object; logging into a personnel information management platform using the virtual account to obtain a first verification source file, wherein the first verification source file includes at least the identification information of the managed object; logging into a personnel access control system using the virtual account to obtain a second verification source file; comparing the second verification source file with the first verification source file based on the identification information of the managed object to obtain an account to be cancelled in the second verification source file; and displaying the cancellation information associated with the account to be cancelled to the administrator, so that the administrator can cancel the cancellation information.

[0005] According to embodiments of this disclosure, the virtual account includes a first virtual account and a second virtual account, wherein the first virtual account has the same permissions as the second virtual account; logging into the personnel information management platform using the virtual account includes: using the RPA robot to log into the personnel information management platform based on the first virtual account; logging into the personnel access control system using the virtual account includes: using the RPA robot to log into the personnel access control system based on the second virtual account.

[0006] According to an embodiment of this disclosure, obtaining the first verification source file includes: after logging into the personnel information management platform using the RPA robot based on the first virtual account, querying the basic information of personnel marked as normal or deregistered in the personnel information management platform; and generating the first verification source file based on the basic information of the personnel.

[0007] According to an embodiment of this disclosure, obtaining the second verification source file includes: after logging into the personnel access management system using the RPA robot based on the second virtual account, querying the personnel operation permission information marked as normal in the personnel access management system; and generating the second verification source file based on the personnel operation permission information.

[0008] According to embodiments of this disclosure, the process of comparing the second verification source file with the first verification source file based on the identification information of the managed object to obtain the accounts to be cancelled in the second verification source file includes: preprocessing the first verification source file using the RPA robot to obtain basic information of personnel marked as cancelled in the first verification source file; determining the identification information of the managed object based on the basic information of the personnel in the cancelled state; and searching for accounts associated with the identification information of the managed object in the second verification source file to obtain the accounts to be cancelled in the second verification source file.

[0009] According to embodiments of this disclosure, the method further includes: after the administrator cancels the information to be canceled, the RPA robot is used to automatically cancel the first virtual account and the second virtual account.

[0010] According to embodiments of this disclosure, the information to be deregistered includes at least one of the following: the personnel number to be deregistered, the personnel role information to be deregistered, and the personnel operation permissions to be deregistered.

[0011] Another aspect of this disclosure provides an information cancellation device based on an RPA robot, comprising: a creation module for creating a virtual account for an administrator in response to an information cancellation request, wherein the information cancellation request is generated based on personnel changes of the managed object; a first login module for logging into a personnel information management platform using the virtual account and obtaining a first verification source file, wherein the first verification source file includes at least the identification information of the managed object; a second login module for logging into a personnel access control system using the virtual account and obtaining a second verification source file; a comparison module for comparing the second verification source file with the first verification source file based on the identification information of the managed object to obtain the account to be cancelled in the second verification source file; and a display module for displaying the cancellation information associated with the account to be cancelled to the administrator, so that the administrator can cancel the cancellation information.

[0012] Another aspect of this disclosure provides an electronic device, including: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to execute the information deregistration method based on the RPA robot.

[0013] This disclosure also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the aforementioned information deregistration method based on an RPA robot.

[0014] This disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the aforementioned information deregistration method based on an RPA robot.

[0015] According to the information cancellation method, apparatus, device, medium, and program product based on RPA robot provided in this disclosure, in response to an information cancellation request, a virtual account for the administrator is created. The administrator logs into the personnel information management platform and personnel access control system using the virtual account, obtains a first verification source file and a second verification source file, and compares the first and second verification source files to obtain the account to be cancelled in the second verification source file and cancels it. Since the RPA robot creates a virtual account for the administrator, this virtual account can have the same permissions as the administrator. The RPA robot can use this virtual account to handle account cancellation, permission cancellation, and other matters. Therefore, it at least partially solves the problem of RPA robots and administrators competing for accounts in related technologies, thereby achieving the technical effect of improving the efficiency of administrators in handling business and reducing time costs. Attached Figure Description

[0016] The foregoing contents, as well as other objects, features, and advantages of this disclosure, will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0017] Figure 1 This schematically illustrates a system architecture diagram of an RPA-based robot-based information deregistration method and apparatus according to embodiments of the present disclosure;

[0018] Figure 2 A flowchart illustrating an information deregistration method based on an RPA robot according to an embodiment of the present disclosure is shown schematically.

[0019] Figure 3 A flowchart illustrating an information deregistration method for an RPA-based robot according to another embodiment of the present disclosure is shown schematically.

[0020] Figure 4 A schematic diagram illustrating the structure of an RPA-based robot-based information deregistration device according to an embodiment of the present disclosure is shown; and

[0021] Figure 5 A block diagram schematically illustrates an electronic device suitable for implementing an information deregistration method based on an RPA robot according to an embodiment of the present disclosure. Detailed Implementation

[0022] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0023] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0024] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0025] When using expressions such as "at least one of A, B, and C," the expression should generally be interpreted in accordance with the meaning commonly understood by a person skilled in the art (e.g., "a system having at least one of A, B, and C" should include, but is not limited to, systems having A alone, having B alone, having C alone, having A and B, having A and C, having B and C, and / or having A, B, and C, etc.). Similarly, when using expressions such as "at least one of A, B, or C," the expression should generally be interpreted in accordance with the meaning commonly understood by a person skilled in the art (e.g., "a system having at least one of A, B, or C" should include, but is not limited to, systems having A alone, having B alone, having C alone, having A and B, having A and C, having B and C, and / or having A, B, and C, etc.).

[0026] When handling business processes triggered by personnel changes, managers typically use an employee information management platform based on a client-server (CS) architecture and an employee access control system based on a browser-server (BS) architecture. The CS-based management platform also manages basic operational permissions for employees, which may differ from those managed in the BS-based system. When canceling accounts or permissions, managers can log in to the client to perform business operations and processes. This process utilizes multiple components, each corresponding to a functional module within a different business domain. After processing by the CS-based management platform, the business flows to the BS-based management system, where managers can directly handle subsequent processes by logging into a browser. During business processing, the inventors discovered that the BS-based management system also internally manages its own user access control system. Therefore, user permissions in management platforms based on client-server (CS) architecture and management systems based on browser-server (BS) architecture cannot be uniformly controlled. When a user's account and permissions are revoked and become invalid in a management platform based on CS architecture, the same user's account and permissions can still be used normally in a management system based on BS architecture. This leads to data auditing risks and security vulnerabilities.

[0027] Because data silos exist between client-server (CS) based management platforms and browser-server (BS) based management systems, and because BS-based management systems themselves involve massive amounts of data and numerous upstream and downstream stakeholders, they are often indispensable. The common approach to interfacing between CS-based and BS-based management platforms is through upstream systems providing interfaces to downstream systems, or upstream systems pushing data files to a file service daily, with downstream systems then accessing the file service to retrieve, process, and store the data. This requires collaborative modifications to both upstream and downstream systems, resulting in significant challenges such as high modification difficulty, long cycles, and high development costs. Furthermore, after years of IT infrastructure development, banks now have numerous internal systems, complex back-office processes, and substantial cross-system data transfers. Processes characterized by high workload, repetitive nature, high modification difficulty, and potential compliance risks are the key focus and challenge of current digital transformation in banks.

[0028] Currently, the problem of information silos is usually solved by unifying the data interfaces between the two parties for synchronization or by manually maintaining data across systems and applications. However, the high investment, difficulty in coordination, and long cycle of data interfaces deter many enterprises; and manually processing large amounts of data is not the best option from the perspectives of security, efficiency, and accuracy.

[0029] In view of this, embodiments of this disclosure provide an information cancellation method based on an RPA robot. The RPA robot exists as an "add-on" outside the bank application, allowing for deployment and automation without altering or affecting the existing computer system. This eliminates the risks associated with system modification and has a shorter implementation cycle. By replacing manual processing with RPA robots, the error rate of management personnel is reduced, and the overall processing efficiency of management personnel is improved.

[0030] In the process of using RPA robots to handle employee account cancellation and permission cancellation, the inventors also discovered that the RPA robot requires the administrator's account to process the transaction. However, an administrator's account can only be logged in once at a time. If the RPA robot uses the administrator's account to handle account cancellation and permission cancellation, the administrator cannot log in to handle other matters and can only wait for the RPA robot to complete the process. This leads to the problem of the RPA robot and the administrator competing for the account, which still cannot improve the administrator's business processing efficiency.

[0031] In view of this, this disclosure provides an information cancellation method based on RPA robots to improve the business processing efficiency of managers and reduce time costs. Specifically, the method includes: in response to an information cancellation request, creating a virtual account for the manager, wherein the information cancellation request is generated based on personnel changes of the managed object; logging into the personnel information management platform using the virtual account to obtain a first verification source file, wherein the first verification source file includes at least the identification information of the managed object; logging into the personnel access control system using the virtual account to obtain a second verification source file; comparing the second verification source file with the first verification source file based on the identification information of the managed object to obtain the account to be cancelled in the second verification source file; and displaying the cancellation information associated with the account to be cancelled to the manager so that the manager can cancel the cancellation information.

[0032] It should be noted that the information cancellation method and apparatus based on RPA robots as determined in the embodiments of this disclosure can be used in the fields of computer technology or fintech. The information cancellation method and apparatus based on RPA robots as determined in the embodiments of this disclosure can also be used in any field other than computer technology and fintech. This disclosure does not limit the application field of the determined information cancellation method and apparatus based on RPA robots.

[0033] In the technical solution disclosed herein, the collection, storage, use, processing, transmission, provision, disclosure, and application of user personal information all comply with relevant laws and regulations, necessary confidentiality measures have been taken, and they do not violate public order and good morals. In the technical solution disclosed herein, user authorization or consent has been obtained before acquiring or collecting user personal information.

[0034] In the technical solutions disclosed herein, the acquisition, collection, storage, use, processing, transmission, provision, disclosure, and application of data all comply with relevant laws and regulations, necessary confidentiality measures have been taken, and they do not violate public order and good morals. In the technical solutions disclosed herein, authorization or consent has been obtained before acquiring or collecting data.

[0035] Figure 1 The diagram illustrates the system architecture of an information deregistration method and apparatus based on an RPA robot according to an embodiment of the present disclosure.

[0036] like Figure 1 As shown, the application scenario 100 according to this embodiment may include terminal devices 101, 102, 103, network 104, server 105, management platform based on CS architecture 106, and management system based on BS architecture 107.

[0037] Terminal devices 101, 102, and 103 can be various electronic devices in public or independent environments, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0038] Various communication client applications can be installed on terminal devices 101, 102, and 103, such as employee information management applications, financial applications, shopping applications, web browser applications, search applications, instant messaging tools, email clients, and / or social platform software (for example only).

[0039] Users can perform operations in the client applications of terminal devices 101, 102, and 103, such as filling in personnel change information of the managed objects, to execute business functions and send information cancellation requests to server 105.

[0040] Network 104 is a medium used to provide a communication link between terminal devices 101, 102, 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0041] The client-server architecture-based management platform 106 can be a personnel information management platform that stores employee information and basic permissions for all employees. All employees can include those marked as normal or not yet logged out, as well as those marked as logged out.

[0042] The B / S architecture-based management system 107 can be a personnel access control system that stores employee information and operational permissions for all employees. Employee operational permissions here can be determined based on employee role attributes and are not possessed by every employee, differing from basic employee permissions. All employees in the B / S architecture-based management system 107 can be employees whose status is not yet defined, or all employees marked as being in normal use. Server 105 needs to identify and delete accounts to be deactivated in the B / S architecture-based management system 107 based on information obtained from the C / S architecture-based management platform 106.

[0043] Server 105 can be a server providing various services or an RPA robot. Server 105 can be equipped with RPA input and output interfaces for the RPA robot to receive and send relevant information, respectively. Server 105 can process the received data and feed the processing results back to terminal devices 101, 102, and 103. For example, server 105 can respond to a cancellation request sent by terminal devices 101, 102, and 103 by creating a virtual account for the administrator. The cancellation request is generated based on personnel changes within the managed object. Server 105 logs into the client-server architecture-based management platform 106 using the virtual account and obtains a first verification source file, which includes at least the identification information of the managed object. Server 105 then logs into the browser-server architecture-based management system 107 using the virtual account and obtains a second verification source file. Based on the identification information of the managed object, server 105 compares the second verification source file with the first verification source file to obtain the account to be cancelled in the second verification source file. Finally, server 105 displays the cancellation information associated with the account to be cancelled to the administrator through terminal devices 101, 102, and 103, allowing the administrator to cancel the cancellation information.

[0044] It should be noted that the information deregistration method based on RPA robots provided in this disclosure can generally be executed by server 105. Correspondingly, the information deregistration device based on RPA robots provided in this disclosure can generally be located in server 105. The business processing method provided in this disclosure can also be executed by a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103, the CS-based management platform 106, the BS-based management system 107, and / or server 105. Correspondingly, the business processing device provided in this disclosure can also be located in a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103, the CS-based management platform 106, the BS-based management system 107, and / or server 105.

[0045] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0046] The following will be based on Figure 1 The described scene, through Figures 2-3 The information deregistration method based on RPA robot of the disclosed embodiments is described in detail.

[0047] Figure 2 A flowchart illustrating an information deregistration method based on an RPA robot according to an embodiment of the present disclosure is shown schematically.

[0048] like Figure 2 As shown, the information cancellation method based on RPA robot in this embodiment includes operations S201 to S205.

[0049] In operation S201, in response to the information cancellation request, a virtual account for the administrator is created, wherein the information cancellation request is generated based on personnel changes of the managed object.

[0050] In operation S202, the first verification source file is obtained by logging into the personnel information management platform based on the virtual account. The first verification source file includes at least the identification information of the managed object.

[0051] In operation S203, the second verification source file is obtained by logging into the personnel access management system based on the virtual account.

[0052] In operation S204, based on the identification information of the managed object, the second verification source file is compared with the first verification source file to obtain the account to be cancelled in the second verification source file.

[0053] In operation S205, the administrator is shown the cancellation information associated with the account to be cancelled so that the administrator can cancel the cancellation information.

[0054] According to embodiments of this disclosure, RPA can be understood as a simulated operation method including keyboard and mouse, capable of acquiring and locating screen information, enabling tasks to be processed according to a prescribed flow, and automating the dispatching, control, and management of tasks. In the business processing of embodiments of this disclosure, RPA robots can be used to replace manual operation steps, achieving an automated process of deregistering information and returning processing results. The automated processing of RPA robots can be achieved by building automated scripts.

[0055] According to embodiments of this disclosure, personnel changes can be retirement or onboarding. The managed entity can be a retired employee or an employee in the process of retirement. The information cancellation request can include a process triggered in the event of the managed entity's retirement regarding account cancellation and permission cancellation. In one embodiment, the managed entity can also be an employee who has been hired or is in the process of being hired, and these employees need to complete a process to activate permissions.

[0056] According to embodiments of this disclosure, the cancellation request may also be generated based on the needs of the managed object, such as the managed object applying to cancel an account or permission that is no longer in use.

[0057] According to embodiments of this disclosure, administrators may be personnel responsible for handling personnel changes, such as those involved in processes like account cancellation, permission cancellation, and job information cancellation resulting from personnel changes. Each administrator may have a work account, which may have permissions such as logging into the system, retrieving files, and logging out.

[0058] According to embodiments of this disclosure, a virtual account can be an account created solely for the purpose of handling a specific transaction, such as account cancellation or permission revocation, and will be automatically deleted after the transaction is completed. A virtual account is understood to have the same organizational structure, role, and operational permissions as the administrator's work account.

[0059] According to embodiments of this disclosure, the personnel information management platform can be a client-server (CS) architecture-based platform. The platform stores personnel IDs, employee job information, and basic permissions for all managed objects within the enterprise. The enterprise can also be subdivided into multiple departments, and the platform can include the department ID of the department where the employee resides. The first verification source file can be the personnel IDs, department IDs, job information, and basic permissions of all managed objects within a specific department, where a specific department can be the department where the managed object resides. The employees in the first verification source file can be employees whose status has been differentiated between normal (not yet deregistered) and deregistered. The identification information of the managed object can be the personnel ID corresponding to the employee marked as deregistered.

[0060] According to embodiments of this disclosure, the personnel access control system can be a B / S architecture-based system that stores personnel IDs, organization IDs, and employee operation permissions for all managed objects within the enterprise. The employee operation permissions in this system differ from the basic permissions commonly used by employees. Specifically, the employee operation permissions in this system can be customized based on the various role attributes of the managed objects. Each managed object may have different permissions; some managed objects may have approval or modification permissions, while others may only have view permissions.

[0061] According to embodiments of this disclosure, the employees in the second verification source file can be the personnel numbers, organization numbers, job information, and employee operation permissions of all managed objects within an organization. The organization can be the organization where the managed object resides. The employees in the second verification source file can be those whose status is neither clearly defined as active nor deactivated; they are all in normal use and require processing by an RPA robot. The RPA robot compares these employees with the first verification source file to identify those that need to be marked as deactivated. The accounts to be deactivated can be the accounts corresponding to the employees whose status needs to be marked as deactivated in the second verification source file.

[0062] According to embodiments of this disclosure, the information to be deregistered may include at least one of the following: the personnel number to be deregistered, the personnel role information to be deregistered, and the personnel operation permissions to be deregistered. The personnel role information to be deregistered can be understood as the role information, job information, and hierarchical relationships of the managed object. The information to be deregistered can also be adaptively adjusted according to actual needs.

[0063] According to the information cancellation method, apparatus, device, medium, and program product based on RPA robots provided in this disclosure, in response to an information cancellation request, a virtual account for the administrator is created. The administrator logs into the personnel information management platform and personnel access control system using the virtual account, obtains a first verification source file and a second verification source file, and compares the first and second verification source files to obtain the account to be cancelled in the second verification source file and cancels it. Since the RPA robot creates a virtual account for the administrator, this virtual account can have the same permissions as the administrator. The RPA robot can use this virtual account to handle matters such as account cancellation and permission cancellation. Therefore, it at least partially solves the problem of RPA robots and administrators competing for accounts in related technologies, thereby achieving the technical effect of improving the efficiency of administrators in handling business and reducing time costs.

[0064] According to embodiments of this disclosure, a virtual account may include a first virtual account and a second virtual account, wherein the first virtual account has the same permissions as the second virtual account; then operation S202 may further include the following operation: using an RPA robot to log in to the personnel information management platform based on the first virtual account; operation S203 may further include the following operation: using an RPA robot to log in to the personnel permission management system based on the second virtual account.

[0065] According to an embodiment of this disclosure, after logging into the personnel information management platform using an RPA robot based on a first virtual account, the basic information of personnel marked as normal or deregistered in the personnel information management platform is queried; and a first verification source file is generated based on the personnel basic information.

[0066] According to an embodiment of this disclosure, after logging into the personnel access management system using an RPA robot based on a second virtual account, the system queries the personnel operation permission information marked as normal in the personnel access management system; and generates a second verification source file based on the personnel operation permission information.

[0067] According to embodiments of this disclosure, an RPA robot can invoke the transaction process of a personnel information management platform component related to business processes. Based on the work account of the administrator logging into the organization where the managed object resides on the personnel information management platform, a first virtual account x11 and a corresponding first virtual password y11 are created. The RPA robot can use the first virtual account x11 and the first virtual password y11 to log into the personnel information management platform, query and download the basic information and job information of employees marked as normal or deregistered under the organization where the managed object resides, and generate detailed reports based on the employee basic information and job information to obtain a first verification source file.

[0068] According to embodiments of this disclosure, an RPA robot can invoke the transaction process of a personnel access control system component related to business processes. Based on the work account of the administrator logging into the organization where the managed object resides under the personnel access control system, a second virtual account x22 and a corresponding second virtual password y22 are created. The RPA robot can use the second virtual account x22 and the second virtual password y22 to log into the personnel access control system, query and download the employee operation permission table (or the employee operation permission table for all employees) marked as normal under the organization where the managed object resides, and obtain a second verification source file based on the employee operation permission table. In one embodiment, there can be multiple second verification source files. For example, the managed object can have multiple operation permissions. Multiple second verification source files can be obtained by acquiring permissions, and each second verification source file has the same operation permissions.

[0069] According to embodiments of this disclosure, by proposing the concept of "virtual employees," that is, before using RPA robots to process business, first virtual accounts and second virtual accounts of managers are created using RPA robots. Using virtual accounts to process daily business with fixed processes can solve the problem of RPA robots and managers competing for work accounts, and can also quickly improve the business processing efficiency of managers at a lower cost.

[0070] According to an embodiment of this disclosure, operation S204 may further include the following operations: preprocessing the first verification source file using an RPA robot to obtain basic information of personnel marked as deregistered in the first verification source file; determining the identification information of the managed object based on the basic information of the deregistered personnel; and searching for accounts associated with the identification information of the managed object in the second verification source file to obtain the accounts to be deregistered in the second verification source file.

[0071] According to embodiments of this disclosure, preprocessing may involve filtering the first verification source file to identify basic information of personnel marked as deregistered, including the personnel ID, position, and organization number. Specifically, the RPA robot can use the first verification source file as a benchmark, call Excel VBA functions to filter out data records with the user status column marked as deregistered, and then compare and match the personnel ID and organization number columns in the filtering results with multiple second verification source files to process and identify the accounts to be deregistered in multiple second verification source files under the personnel access control system.

[0072] According to embodiments of this disclosure, after an administrator cancels information to be canceled or finds an account to be canceled, an RPA robot can be used to automatically delete the initially created first virtual account, first virtual password, second virtual account, and second virtual password. The first virtual account, first virtual password, second virtual account, and second virtual password can be recreated when the next task is executed.

[0073] According to embodiments of this disclosure, operation S205 may further include the following: the RPA robot calls an email service to send the information to be deregistered to the administrator via email. The RPA robot may also call an NFT (Network File Transfer) service to push the information to be deregistered to a downstream platform or the platform that initiated the information deregistration request. Specifically, it may push the information to the target file address corresponding to the processing flow within the platform. At this time, the downstream platform will display the information to be deregistered and support administrators in viewing, downloading, and deregistering it online. In one embodiment, the RPA robot may also automatically deregister the information and display the deregistration result to the administrator.

[0074] According to embodiments of this disclosure, the RPA robot can also perform the above-described operations S201 to S205 periodically or at set intervals. When there are many people seeking services, it can be set to open services at set times every day; when there are few people seeking services, it can be set to open services only once every certain period of time. The periodic appointment settings can be adaptively adjusted according to actual needs.

[0075] According to embodiments of this disclosure, the use of RPA robots to automatically connect data between a client-server (CS) architecture-based management platform and a browser-server (BS) architecture-based management system can not only help enterprises complete digital transformation, but also break down information silos and connect information gaps within the enterprise.

[0076] According to embodiments of this disclosure, RPA robots can be centrally deployed on devices in a data center. Compared to deploying RPA robots directly on devices used by individual users in their daily office work, centralized deployment allows users to initiate tasks on a fixed range of devices when executing business processes, facilitating maintenance and unified software installation. When additional RPA applications are subsequently added to integrate with the personnel information management platform and personnel information management system, they can be directly deployed on the currently defined range of devices. Therefore, centrally deploying RPA applications on servers that meet the requirements facilitates installation and maintenance while reusing device capabilities to save equipment resources.

[0077] Figure 3 A flowchart illustrating an information deregistration method for an RPA-based robot according to another embodiment of this disclosure is shown.

[0078] like Figure 3 As shown, the information cancellation method based on RPA robot in this embodiment includes operations S301 to S311.

[0079] When operating S301, if there is a change in personnel among the managed objects, an account cancellation process is initiated on the relevant process components in the personnel information management platform.

[0080] According to embodiments of this disclosure, the relevant process components can uniformly manage multiple user permissions of the managed object.

[0081] In operation S302, start the RPA robot.

[0082] According to embodiments of this disclosure, the RPA robot can also be set up on a docking platform. This platform can display the application details of the RPA robot and can also periodically schedule, suspend, and terminate the RPA robot. Periodic scheduling refers to allowing users to pre-set the time for starting the RPA robot application within a future period. The docking platform can also display information awaiting deregistration. The platform can provide functions such as querying the execution details of the RPA robot and downloading information awaiting deregistration.

[0083] In operation S303, the RPA robot creates the first virtual employee account x11.

[0084] When operating S304, the RPA robot logs into the personnel information management platform and processes and obtains the first verification source file.

[0085] When operating S305, the RPA robot creates a second virtual employee account x22.

[0086] When operating S306, the RPA robot logs into the personnel access control system and processes and obtains multiple second verification source files.

[0087] According to the embodiments of this disclosure, operations S303 to S304 can refer to operations S201 to S203, and will not be described again here.

[0088] When operating S307, report processing is performed using Excel VBA functions.

[0089] According to the embodiments of this disclosure, operation S307 can be referred to operation S204, and will not be described again here.

[0090] During operation S308, the RPA robot cancels the first virtual employee account x11 and the second virtual employee account x22.

[0091] In operation S309, the email service is invoked to send the result file.

[0092] When operating the S310, the NFT file service is invoked to push the resulting file to the interface platform.

[0093] According to the embodiments of this disclosure, the result file may be information to be cancelled, and operations S309 to S310 can refer to operation S205, which will not be described again here.

[0094] When operating S311, query the execution details on the interface platform, and view or download the result file online.

[0095] According to embodiments of this disclosure, the RPA robot simulates human activities using technologies such as UIAutomation and MASS. First, it logs into the personnel information management platform to query and obtain detailed reports on employee basic information and job information. Then, it logs into the personnel access control system to query and obtain reports such as the platform operator information table and the centralized point operator user auxiliary table. Next, it uses Excel VBA functions to process these reports to obtain result files. Finally, it calls the email service to send the result reports to target users such as parameter administrators via email, and simultaneously calls the file service to push the result files to the target file address of the interface platform so that the interface platform can display the information to be deregistered.

[0096] According to the information cancellation method based on RPA robots provided in this disclosure, using RPA robots to execute business processes is an easy-to-implement process automation solution. RPA robots can be developed through low-code visualization, and deployment is quick, simple, and fast, requiring no backend modifications, and is secure and reliable. By introducing RPA to handle related business, when the personnel information management platform completes account cancellation, the RPA robot can connect the data breakpoints between the personnel information management platform and the personnel access control system to eliminate data silos. RPA robots are compatible with cross-system and cross-language applications. During data collection and processing, they can solve the problem of cross-system data collection and, while eliminating operational breakpoints, also avoid data silos, allowing more dimensions of data to be used for business purposes.

[0097] According to the information deregistration method based on RPA robots provided in this disclosure, the RPA robot can exist outside the application as an "add-on". It can be deployed and automated without changing or affecting the original computer system, eliminating the risks that may occur during system modification and with a shorter implementation cycle.

[0098] The information cancellation method based on RPA robots provided in this disclosure can ensure the normal execution of applications based on rules, while having the characteristic of traceable records, which is conducive to enhancing the compliance of operation and management and improving risk prevention and control capabilities such as auditing.

[0099] According to the information cancellation method based on RPA robot provided in the embodiments of this disclosure, the entire process can be connected to applications with different architectures for data collection, processing and transmission, and with minor modifications, it can be easily applied to other scenarios, thus having universality.

[0100] The information cancellation method based on RPA robots provided in this disclosure is fast, efficient, and cost-effective. It not only avoids human risks but also provides 24 / 7 service, quickly responds to users, fully leverages the productivity of "digital employees," empowers and reduces the burden on managers, and allows them to focus on more creative and comprehensive decision-making tasks.

[0101] It should be noted that, unless it is explicitly stated that there is a sequential order of execution between different operations, or that there is a sequential order of execution between different operations in terms of technical implementation, the execution order between multiple operations may not be significant, and multiple operations may be executed simultaneously.

[0102] Based on the above-described information deregistration method using an RPA robot, this disclosure also provides an information deregistration device based on an RPA robot. The following will be combined with... Figure 4 The device is described in detail.

[0103] Figure 4 A schematic block diagram of an information deregistration device based on an RPA robot according to an embodiment of the present disclosure is shown.

[0104] like Figure 4 As shown, the information deregistration device 400 based on RPA robot in this embodiment includes a creation module 410, a first login module 420, a second login module 430, a comparison module 440, and a display module 450.

[0105] Module 410 is created to create a virtual account for administrators in response to an information cancellation request, wherein the information cancellation request is generated based on personnel changes of the managed object.

[0106] The first login module 420 is used to log in to the personnel information management platform based on the virtual account and obtain the first verification source file, wherein the first verification source file includes at least the identification information of the managed object.

[0107] The second login module 430 is used to obtain the second verification source file by logging into the user permission management system based on the virtual account.

[0108] The comparison module 440 is used to compare the second verification source file with the first verification source file based on the identification information of the managed object, and obtain the account to be cancelled in the second verification source file.

[0109] The display module 450 is used to display the cancellation information associated with the account to be cancelled to the administrator, so that the administrator can cancel the cancellation information.

[0110] According to the information cancellation method, apparatus, device, medium, and program product based on RPA robots provided in this disclosure, in response to an information cancellation request, a virtual account for the administrator is created. The administrator logs into the personnel information management platform and personnel access control system using the virtual account, obtains a first verification source file and a second verification source file, and compares the first and second verification source files to obtain the account to be cancelled in the second verification source file and cancels it. Since the RPA robot creates a virtual account for the administrator, this virtual account can have the same permissions as the administrator. The RPA robot can use this virtual account to handle matters such as account cancellation and permission cancellation. Therefore, it at least partially solves the problem of RPA robots and administrators competing for accounts in related technologies, thereby achieving the technical effect of improving the efficiency of administrators in handling business and reducing time costs.

[0111] According to embodiments of this disclosure, the first login module may further include a first login unit, and the second login module may further include a second login unit.

[0112] The first login unit is used to log in to the personnel information management platform using an RPA robot based on a first virtual account.

[0113] The first login unit is used to log in to the personnel access control system using an RPA robot based on a second virtual account.

[0114] According to embodiments of this disclosure, the first login module may further include a first query unit and a first generation unit.

[0115] The query unit is used to query the basic information of personnel marked as normal or deactivated in the personnel information management platform after logging into the platform using an RPA robot based on a first virtual account.

[0116] The generation unit is used to generate the first verification source file based on the basic information of the personnel.

[0117] According to embodiments of this disclosure, the second login module may further include a second query unit and a second generation unit.

[0118] The second query unit is used to query the operation permission information of personnel marked as normal in the personnel permission management system after logging into the personnel permission management system using the second virtual account via the RPA robot.

[0119] The second generation unit is used to generate a second verification source file based on the personnel operation permission information.

[0120] According to embodiments of this disclosure, the comparison module may further include a preprocessing unit, a determination unit, and a search unit.

[0121] The preprocessing unit is used to preprocess the first verification source file using an RPA robot to obtain the basic information of personnel marked as deregistered in the first verification source file.

[0122] The identification unit is used to determine the identification information of the managed object based on the basic information of the personnel whose status has been cancelled.

[0123] The lookup unit is used to search for accounts associated with the identification information of the managed object in the second verification source file, and obtain the accounts to be cancelled in the second verification source file.

[0124] According to embodiments of this disclosure, the information deregistration device based on RPA robots further includes a deregistration module.

[0125] The deletion module is used to automatically delete the first and second virtual accounts using an RPA robot after the administrator deletes the information to be deleted.

[0126] According to embodiments of this disclosure, any plurality of modules among the creation module 410, the first login module 420, the second login module 430, the comparison module 440, and the display module 450 may be combined into one module, or any one of these modules may be split into multiple modules. Alternatively, at least a portion of the functionality of one or more of these modules may be combined with at least a portion of the functionality of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the creation module 410, the first login module 420, the second login module 430, the comparison module 440, and the display module 450 may be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or any other reasonable means of integrating or packaging circuitry, or implemented in software, hardware, or firmware, or in any suitable combination of any of these three implementation methods. Alternatively, at least one of the creation module 410, the first login module 420, the second login module 430, the comparison module 440, and the display module 450 may be implemented at least partially as a computer program module, which can perform corresponding functions when the computer program module is run.

[0127] It should be noted that the information cancellation device part based on RPA robot in the embodiments of this disclosure corresponds to the information cancellation method part based on RPA robot in the embodiments of this disclosure. For a detailed description of the information cancellation device part based on RPA robot, please refer to the information cancellation method part based on RPA robot, which will not be repeated here.

[0128] Figure 5 A block diagram schematically illustrates an electronic device suitable for implementing an information deregistration method based on an RPA robot according to an embodiment of the present disclosure.

[0129] like Figure 5 As shown, an electronic device 500 according to an embodiment of the present disclosure includes a processor 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage portion 508 into a random access memory (RAM) 503. The processor 501 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 501 may also include onboard memory for caching purposes. The processor 501 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0130] RAM 503 stores various programs and data required for the operation of electronic device 500. Processor 501, ROM 502, and RAM 503 are interconnected via bus 504. Processor 501 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 502 and / or RAM 503. It should be noted that the programs may also be stored in one or more memories other than ROM 502 and RAM 503. Processor 501 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.

[0131] According to embodiments of this disclosure, the electronic device 500 may further include an input / output (I / O) interface 505, which is also connected to a bus 504. The electronic device 500 may also include one or more of the following components connected to the I / O interface 505: an input section 506 including a keyboard, mouse, etc.; an output section 507 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 508 including a hard disk, etc.; and a communication section 509 including a network interface card such as a LAN card, modem, etc. The communication section 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to the I / O interface 505 as needed. A removable medium 511, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 510 as needed so that computer programs read from it can be installed into the storage section 508 as needed.

[0132] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0133] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as including, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 502 and / or RAM 503 and / or one or more memories other than ROM 502 and RAM 503 described above.

[0134] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to enable the computer system to implement the RPA-based robot-based information deregistration method provided in the embodiments of this disclosure.

[0135] When the computer program is executed by the processor 501, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0136] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and may be downloaded and installed via the communication section 509, and / or installed from a removable medium 511. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0137] In such an embodiment, the computer program can be downloaded and installed from a network via communication section 509, and / or installed from removable medium 511. When the computer program is executed by processor 501, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0138] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0139] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0140] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0141] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A method for deregistering information based on an RPA robot, comprising: In response to an information cancellation request, a virtual account for the administrator is created, wherein the information cancellation request is generated based on personnel changes of the managed object, and the virtual account includes a first virtual account and a second virtual account with the same permissions; Using an RPA robot to log in to the personnel information management platform based on the first virtual account, query the basic information of personnel marked as normal or deregistered in the personnel information management platform, and generate a first verification source file based on the basic information of personnel. The first verification source file includes at least the identification information of the managed object, and the identification information includes the personnel number corresponding to the personnel marked as deregistered. The RPA robot logs into the personnel access control system based on the second virtual account, queries the personnel access control system for personnel whose status is marked as normal, and generates a second verification source file based on the personnel access control information. Based on the identification information of the managed object, the second verification source file is compared with the first verification source file to obtain the account to be cancelled in the second verification source file; The administrator is shown the cancellation information associated with the account to be cancelled, so that the administrator can cancel the cancellation information.

2. The method according to claim 1, wherein, The step of comparing the second verification source file with the first verification source file based on the identification information of the managed object to obtain the account to be cancelled in the second verification source file includes: The RPA robot is used to preprocess the first verification source file to obtain the basic information of the personnel marked as logged out in the first verification source file; Based on the basic information of the personnel whose status has been cancelled, determine the identification information of the managed object; The account associated with the identification information of the managed object is searched in the second verification source file to obtain the account to be cancelled in the second verification source file.

3. The method according to claim 1, further comprising: After the administrator cancels the information to be canceled, the RPA robot automatically cancels the first virtual account and the second virtual account.

4. The method according to claim 1, wherein, The information to be cancelled includes at least one of the following: The personnel ID to be cancelled, the role information of the personnel to be cancelled, and the operation permissions of the personnel to be cancelled.

5. An information cancellation device based on RPA robots, comprising: A creation module is used to create virtual accounts for administrators in response to information cancellation requests. The information cancellation request is generated based on personnel changes of the managed object, and the virtual accounts include a first virtual account and a second virtual account with the same permissions. The first login module is used to log in to the personnel information management platform using an RPA robot based on the first virtual account, query the basic information of personnel marked as normal status and deregistration status in the personnel information management platform, and generate a first verification source file based on the basic information of personnel. The first verification source file includes at least the identification information of the managed object, and the identification information includes the personnel number corresponding to the personnel marked as deregistered. The second login module is used to log in to the personnel access control system using the RPA robot based on the second virtual account, query the personnel access control system for personnel whose operation permissions are marked as normal, and generate a second verification source file based on the personnel operation permission information. The comparison module is used to compare the second verification source file with the first verification source file based on the identification information of the managed object, and obtain the account to be cancelled in the second verification source file; The display module is used to display the cancellation information associated with the account to be cancelled to the administrator, so that the administrator can cancel the cancellation information.

6. An electronic device, comprising: One or more processors; Storage device for storing one or more programs. Wherein, when the one or more programs are executed by the one or more processors, the one or more processors perform the method according to any one of claims 1 to 4.

7. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 4.

8. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1 to 4.

Images