{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":20980,"path":"integrate-applications/installed-with-rpa-hub.md","title":"Components installed with RPA Hub","bundle":null,"doc_type":null,"release":"australia","body":"\n# Components installed with RPA Hub\n\nSeveral types of components are installed with the activation of the RPA Hub plugin, including tables, user roles, and scheduled jobs.\n\n**Note:** The Application Files table lists the components that are installed with this application. For instructions on how to access this table, see [Find components installed with an application](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/find-components.md).\n\nDemo data is available for this plugin.\n\n## Roles installed\n\n**Note:** RPA role requires access to the cmdb\\_rel\\_ci table. If there are any customizations to the cmdb\\_rel\\_ci ACLs, provide the relevant read access role to the following RPA roles.\n\n\n
\n\nRole title \\[name\\]\n\n\n\nDescription\n\n\n\nContains roles\n\n
\n\nRPA admin\\[sn\\_rpa\\_fdn.rpa\\_admin\\]\n\n\n\nSets up RPA Hub application configurations and manages RPA Hub system property settings in various environments.\n\n\n\n- fd\\_read\n- itil\n- sn\\_rpa\\_fdn.rpa\\_user\n- cmdb\\_read\n\n
\n\nRPA assisted user\\[sn\\_rpa\\_fdn.rpa\\_assisted\\_user\\]\n\n **Note:**\n\nAssisted user is attended user.\n\n\n\nExecutes attended automations.\n\n\n\nNone\n\n
\n\nRPA business user\\[sn\\_rpa\\_fdn.rpa\\_business\\_user\\]\n\n\n\nManages data like work items, credentials, and so on. Extracts reports.\n\n\n\n- sn\\_rpa\\_fdn.rpa\\_user\n- cmdb\\_read\n\n
\n\nRPA developer\\[sn\\_rpa\\_fdn.rpa\\_developer\\]\n\n\n\nBuilds automation packages, tests the automation projects, and handles exceptions in the RPA Desktop Design Studio.Publishes packages to RPA Hub.\n\n Creates and deploys automations in a low-code environment.\n\n\n\n- fd\\_read\n- sn\\_rpa\\_fdn.rpa\\_user\n- cmdb\\_read\n\n
\n\nRPA elevated privileges \\[sn\\_rpa\\_fdn.rpa\\_elevated\\_privileges\\]\n\n\n\nUsers with this role and along with other roles \\(RPA developer, RPA support user, or RPA admin\\) can access sensitive logs that are captured in Process Execution Log table.\n\n\n\nNone\n\n
\n\nRPA release manager\\[sn\\_rpa\\_fdn.rpa\\_release\\_manager\\]\n\n\n\nManages data, schedules, and other configuration parameters.\n\n\n\n- itil\n- sn\\_rpa\\_fdn.rpa\\_user\n- cmdb\\_read\n\n
\n\nRPA robot\\[sn\\_rpa\\_fdn.rpa\\_robot\\]\n\n\n\nRole that is assigned to a service account for the unattended robot to successfully execute automations.\n\n\n\ncmdb\\_read\n\n
\n\nRPA support user\\[sn\\_rpa\\_fdn.rpa\\_support\\_user\\]\n\n\n\nIdentifies, diagnoses, and resolves the issues that are related to bot processes.Performs first-level troubleshooting.\n\n\n\n- sn\\_rpa\\_fdn.rpa\\_user\n- cmdb\\_read\n\n
\n\nRPA user\\[sn\\_rpa\\_fdn.rpa\\_user\\]\n\n\n\nQualifier role that is required for users to access to RPA Hub.\n\n\n\n- canvas\\_user\n- sn\\_change\\_read\n- fd\\_read\n- uxframework\\_user\n\n
## Scheduled jobs installed\n\n\n
\n\nScheduled job\n\n\n\nDescription\n\n
\n\nMachine Lookup value change\n\n\n\nValidates the values in the **Machine Name Lookup** field and **Machine Name** field. If the value is different, the schedule job updates the **Machine Name** \\(String field\\) with the value of the **Machine Name Lookup** field.\n\n Schedule runs every 3 hours and runs only when the **sn\\_rpa\\_fdn.enable\\_unattended\\_robot\\_machine\\_name\\_lookup** system property is set to **Yes**.\n\n When the schedule job updates the **Machine Name** field, the life cycle stage status of the robot is moved to **In Maintenance**.\n\n
\n\nRPA: Purge Process Jobs\n\n\n\nSchedule runs every day to purge process jobs and associated execution logs that are based on the information from a job's purging days and created date.\n\n
\n\nRPA: Purge Work Items\n\n\n\nSchedule runs every day to purge queue items that are based on a queue's purge after days and the purge status.Purge after days is the number of days after which the work items get purged based on the created date.\n\n
\n\nRPA: Purge Alert Rule Triggers\n\n\n\nSchedule runs every day to purge alert rule trigger records.\n\n
\n\nRPA: Purge Alerts\n\n\n\nSchedule runs every day to purge alerts.\n\n
\n\nRe-evaluate License Distribution\n\n\n\nSchedule runs on demand to validate the distribution of license records.For more information, see [Re-evaluate license distribution by executing RPA scripts](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/execute-rpa-script.md).\n\n
## Tables installed\n\n\n
\n\nTable\n\n\n\nDescription\n\n\n\nExtends\n\n
\n\nAlerts\\[sn\\_rpa\\_fdn\\_alert\\]\n\n\n\nContains the alerts that are generated from the alert rules and the information about the alert message, the associated alert rule name, and the trigger type.\n\n\n\n \n\n
\n\nAlert Rule\\[sn\\_rpa\\_fdn\\_alert\\_rule\\]\n\n\n\nContains the rules that are defined for the alerts to be generated and the information about the type and priority of the alert rule, the alert trigger, and the alert message.\n\n\n\nApplication file\n\n
\n\nApplication Credentials\\[sn\\_rpa\\_fdn\\_application\\_credentials\\]\n\n\n\nContains the user name and password of business application used by the bot process at the time of execution on a robot.\n\n\n\nCredentials\n\n
\n\nAttended Configuration\\[sn\\_rpa\\_fdn\\_attended\\_configuration\\]\n\n\n\nContains the details like the associated bot process name, table, action label, and conditions to trigger the attended bot process \\(automation\\) from the corresponding ServiceNow form.\n\n\n\nApplication file\n\n
\n\nAttended User Group\\[sn\\_rpa\\_fdn\\_rda\\_user\\_group\\]\n\n\n\nContains the details like the associated bot process name, the assigned user for the attended bot process, and the assigned group for the selected assigned user.\n\n\n\n \n\n
\n\nAuthorized User\\[sn\\_rpa\\_fdn\\_authorized\\_user\\]\n\n\n\nContains details of mapping between process credential mapping and an authorized user who can access the associated credential group.\n\n\n\n \n\n
\n\nAutomation Logsn\\_rpa\\_fdn\\_automation\\_log\n\n\n\nContains the live log and give real-time visibility of the status of the running process jobs.\n\n\n\n \n\n
\n\nAssigned Studio Usersn\\_rpa\\_fdn\\_assigned\\_studio\\_user\n\n\n\nDefines if a robot is available for impersonation in RPA Desktop Design Studio for an assigned user.RPA release manager and RPA admin can create this record and add assigned user.\n\n\n\n \n\n
\n\nBot Process Configuration\\[sn\\_rpa\\_fdn\\_bot\\_process\\_config\\]\n\n\n\nContains the bot process settings.\n\n\n\nApplication file\n\n
\n\nBot Process\\[cmdb\\_ci\\_rpa\\_process\\]\n\n\n\nContains the configuration details of a process that runs on a robot. Details include the package, package version, assigned robots, process credential mappings, process robot credential sets, assigned business applications, process parameters, and attended users or groups.\n\n\n\nBase Bot Process\n\n
\n\nCredential Group\\[sn\\_rpa\\_fdn\\_credential\\_group\\]\n\n\n\nContains details like the credential group name and the associated robot credentials.\n\n\n\n \n\n
\n\nCredential Group Application Credential\\[sn\\_rpa\\_fdn\\_m2m\\_credential\\_group\\_application\\]\n\n\n\nContains details like the credential group and the associated application credentials.\n\n\n\n \n\n
\n\nCode Quality Rule\\[sn\\_rpa\\_fdn\\_code\\_quality\\_rule\\]\n\n\n\nContains the details of compliance rules for code quality check feature.\n\n\n\n \n\n
\n\nExternal Credential Vault\\[sn\\_rpa\\_fdn\\_external\\_credential\\_vault\\]\n\n\n\nContains the details that enable you to register your external credential vault for further usage by the unattended robot.\n\n\n\n \n\n
\n\nField Parameter Mapping\\[sn\\_rpa\\_fdn\\_field\\_parameter\\_mapping\\]\n\n\n\nContains the details that enable you to map ServiceNow form fields of the associated attended configuration table to the process field parameters used in the attended automations.\n\n\n\nApplication file\n\n
\n\nInstalled RPA Plugin\\[sn\\_rpa\\_fdn\\_rpa\\_plugin\\]\n\n\n\nContains the details of the plugins that are available on the instance which can be used with RPA Desktop Design Studio, Attended Robot, and Unattended Robot.\n\n\n\n \n\n
\n\nInstalled RPA Plugin Version\\[sn\\_rpa\\_fdn\\_rpa\\_plugin\\_version\\]\n\n\n\nContains the details of the different versions that are available for the installed RPA plugins.\n\n\n\n \n\n
\n\nMaintenance Request\\[sn\\_rpa\\_fdn\\_maintenance\\_request\\]\n\n\n\nContains the details that tracks the status of the scheduled maintenance days on the robot calendar.\n\n\n\n \n\n
\n\nMFA Authenticator\\[sn\\_rpa\\_fdn\\_mfa\\_authenticator\\]\n\n\n\nContains the details of the authenticator and token length that acts as an enabler for the Time-based One-time Password \\(TOTP\\) authentication.\n\n\n\n \n\n
\n\nPackage\\[sn\\_rpa\\_fdn\\_package\\]\n\n\n\nContains a set of resource files that include the robot files required for an automation execution.\n\n\n\nApplication file\n\n
\n\nPackage Version\\[sn\\_rpa\\_fdn\\_package\\_version\\]\n\n\n\nContains the version details of a package.\n\n\n\nApplication file\n\n
\n\nProcess Credential Mapping\\[sn\\_rpa\\_fdn\\_process\\_credential\\_mapping\\]\n\n\n\nContains details of a credential group and associated bot process.\n\n\n\n \n\n
\n\nProcess Execution Log\\[sn\\_rpa\\_fdn\\_execution\\_log\\]\n\n\n\nContains the execution type and associated process job details.\n\n\n\n \n\n
\n\nProcess Job\\[sn\\_rpa\\_fdn\\_process\\_job\\]\n\n\n\nContains the details of the execution of a process on a robot. Details include the process job name, the state of the process job, the associated bot process name, the assigned robot of the bot process, the execution log status, the start and end time, and the date of the process job.\n\n\n\n \n\n
\n\nProcess Field Parameter\\[sn\\_rpa\\_fdn\\_process\\_field\\_parameter\\]\n\n\n\nContains the details that enable you to create dynamic parameters that are required in the attended automations.\n\n\n\nApplication file\n\n
\n\nProcess Parameter\\[sn\\_rpa\\_fdn\\_process\\_parameter\\]\n\n\n\nContains the details of the variables that are used within a bot process and across bot processes.\n\n\n\nApplication file\n\n
\n\nProcess Robot Credential\\[sn\\_rpa\\_fdn\\_process\\_robot\\_cred\\]\n\n\n\nContains the details of a credential group that a robot uses to perform the automation for the given bot process.\n\n\n\n \n\n
\n\nProcess Schedule\\[sn\\_rpa\\_fdn\\_schedule\\]\n\n\n\nContains the details that enable users to execute jobs in a planned manner at regular intervals. Details include the name and interval type of the schedule and the start and end date of the schedule.\n\n\n\nApplication file\n\n
\n\nProcess Skill Mapping\\[sn\\_rpa\\_fdn\\_m2m\\_process\\_skill\\_mapping\\]\n\n\n\nContains details about mapped package version and overridden version of the skill package for a bot process configuration.\n\n\n\n \n\n
\n\nRobot\\[cmdb\\_ci\\_rpa\\_robot\\]\n\n\n\nContains the details of a software agent that runs a bot process that is built in the RPA Desktop Design Studio. Details include the name, type, and department of the robot, the machine name that is used to install the Unattended Robot, and the attended user.\n\n\n\nBase Robot\n\n
\n\nRobot Credentials\\[sn\\_rpa\\_fdn\\_credentials\\_set\\]\n\n\n\nContains the login credentials that the robot uses to log in to a Windows machine and perform the automation.\n\n\n\nCredentials\n\n
\n\nRobots License Distribution\\[sn\\_rpa\\_fdn\\_license\\_distribution\\]\n\n\n\nContains the details of consumption and distribution of licenses in your organization.\n\n\n\n \n\n
\n\nRobots Pool\\[sn\\_rpa\\_fdn\\_robot\\_pool\\]\n\n\n\nContains the details of the number of robots selected for robot pool option.\n\n\n\n \n\n
\n\nSkill Mapping\\[sn\\_rpa\\_fdn\\_m2m\\_package\\_version\\_skill\\_mapping\\]\n\n\n\nContains attended and unattended package version and associated skill package version details.\n\n\n\n \n\n
\n\nTOTP Authenticator\\[sn\\_rpa\\_fdn\\_totp\\_authenticator\\]\n\n\n\nContains the details of MFA authenticator and seed which is the secret key of the authenticator that is used to generate the TOTP.\n\n\n\n \n\n
\n\nWork Queue\\[sn\\_rpa\\_fdn\\_work\\_queue\\]\n\n\n\nContains the details of a repository that can hold a number of work items. Details include the name, department, and description of the work queue, and purge-work item details.\n\n\n\nApplication file\n\n
\n\nWork Item\\[sn\\_rpa\\_fdn\\_work\\_queue\\_item\\]\n\n\n\nContains the details about the multiple types of data that are stored, such as the transaction information, the customer details, or the information from a document. Details include the name, status, and priority of the work item, and associated work queue name.\n\n\n\n \n\n
**Parent Topic:**[RPA Hub reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/rpa-hub-reference.md)\n\n"}}