--- sourceDocument: Brazil Workflow Data Fabric sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Workflow Data Fabric ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # RPA Hub features # RPA Hub features {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Learn about the various RPA Hub features and capabilities. ## Bot process {#rpa-hub-features__section_dgr_znc_f3c} Bot process : A bot process is a predefined sequence of actions that a robot follows to accomplish a specific task or achieve a particular goal. Bot process configuration : A bot process configuration is a record that contains the bot process settings. The bot process configuration record is mapped to a bot process record. It is a one to one mapping. For more information, see [Bot process](https://www.servicenow.com/docs/Fh5n_jyVL~kis5vxVwxTSQ "In RPA Hub, you can create a bot process configuration record and assign assets to associate it with a bot process. Or you can just save the bot process configuration record, however it won't be associated to a bot process. It remains orphaned."). ## Robots {#rpa-hub-features__section_zvb_znc_f3c} A robot runs a bot process (automation). Robots are designed to interact with software applications, data sources, and user interfaces like a human operator would, but in a more efficient, accurate, and consistent manner. There are two types of robots: * Unattended robots: robots that run unattended automations that don't require any human intervention. * Attended robots: robots that run attended automations that require human intervention. {#rpa-hub-features__ul_r5j_bq3_f3c}For more information, see [Robots](https://www.servicenow.com/docs/WG0Q1sFiRdq9T_6YKYaExw "Mimic human actions to perform repetitive, rule-based tasks using robots in RPA Hub. These robots interact with user interfaces and automate tasks."). ## Package and package version {#rpa-hub-features__section_l22_c4c_f3c} A package is a container that groups together one or more automation logic and their related files, configurations, and dependencies. A package version is a specific release of a package. After a package is created, the RPA developer publishes an automation from RPA Desktop Design Studio. This process results in a new package version. For more information, see [Package and package version](https://www.servicenow.com/docs/hBkzpkkse9Eu2hOGQV3vRA "A package is a container that groups together one or more automation logic and their related files, configurations, and dependencies. A package version is a specific release of a package."). ## Credential management {#rpa-hub-features__section_o31_d4c_f3c} Streamline the credentials that robots use to perform the automation that you define in the bot process. Instead of creating the same set of credentials for each bot process, you can create a credential group that includes a robot credential, application credentials, and external credentials. You can then associate the credential group to multiple bot processes. For more information, see [Credential management](https://www.servicenow.com/docs/3uJ63lPKT75HPcoR1IMcSQ "Streamline the credentials that robots use to perform the automation that you defined in the bot process. Instead of creating the same set of credentials for each bot process, you can create a credential group that includes a robot credential, application credentials, and external credentials. You can then associate the credential group to multiple bot processes."). ## Smart card {#rpa-hub-features__section_v4c_x4c_f3c} Smart card login for a Windows machine is a secure method of logging into the system using a physical smart card instead of a username and password. It's commonly used in organizations to enhance security, particularly in environments with high security requirements. For more information, see [Smart card](https://www.servicenow.com/docs/x4QdHPuaR7cO_tZnvmxoZQ "Smart card login for a Windows machine is a secure method of logging into the system using a physical smart card instead of a username and password. It’s commonly used in organizations to enhance security, particularly in environments with high security requirements."). ## Embedded Task Automation (ETA) {#rpa-hub-features__section_ssh_t4c_f3c} With the embedded task automation feature, trigger attended bot processes (attended automations) from the ServiceNow forms, apart from initiating them from the Attended Robot application. For more information, see [Embedded Task Automation](https://www.servicenow.com/docs/I0zUXsz4veyo~U40rWPMkA "With the embedded task automation feature, trigger attended bot processes (attended automations) from the ServiceNow forms, apart from initiating them from the Attended Robot application."). ## Robot pool {#rpa-hub-features__section_mp1_x4c_f3c} Create a robot pool in RPA Hub to distribute and manage the workload among multiple unattended robots for unattended bot processes. For more information, see [Robot pool](https://www.servicenow.com/docs/9HFTScMf6pPb6kCE6wD4Cg "Create a robot pool in RPA Hub to distribute and manage the workload among multiple unattended robots for unattended bot processes."). ## Robot calendar {#rpa-hub-features__section_lzh_54c_f3c} You can use the robot calendar in RPA Hub to view and create the schedule for the unattended robots. It's a simple, efficient, and interactive way to work with robots and schedules. By using the calendar, you can manage and plan a robot's schedule in a single view. For more information, see [Robot calendar](https://www.servicenow.com/docs/IUoD95ZqxdH0VIBXSW9NqA "You can use the robot calendar in RPA Hub to view and create the schedule for the unattended robots. It’s a simple, efficient, and interactive way to work with robots and schedules. By using the calendar, you can manage and plan a robot's schedule in a single view."). ## Scheduled maintenance days {#rpa-hub-features__section_xx1_x4c_f3c} Track the scheduled maintenance (SM) days on the robot calendar so that the bot processes can function optimally. If an issue occurs, you can take preventive measures. For example, you can know in advance about the days when the robot or the bot process is unavailable so that you can avoid the number of skipped process jobs. For more information, see [Scheduled maintenance days](https://www.servicenow.com/docs/4fCAtEaTD8LwrNhZtbEqcw "Track the scheduled maintenance (SM) days on the robot calendar so that the bot processes can function optimally. If an issue occurs, you can take preventive measures. For example, you can know in advance about the days when the robot or the bot process is unavailable so that you can avoid the number of skipped process jobs."). ## Graceful stop {#rpa-hub-features__section_kfb_x4c_f3c} Graceful Stop functionality provides a capability for robots to exit the automation smoothly. You can define a secure termination point within an automation process. It also enables you to perform clean-up tasks such as closing in-use applications. It is applicable for assigned robots as well as robots in a robot pool. For more information, see [Graceful stop functionality](https://www.servicenow.com/docs/qO7buUTEf8w9CUEoDLp3lQ "Graceful Stop functionality provides a capability for robots to exit the automation smoothly. You can define a secure termination point within an automation process. It also enables you to perform clean-up tasks such as closing in-use applications. It is applicable for assigned robots as well as robots in a robot pool."). ## Queues {#rpa-hub-features__section_dmb_x4c_f3c} The queues are implemented to distribute the workload among various robots. Work Items (WI) within a queue are processed simultaneously by two or more robots. A queue is a repository that can hold a number of work items. Work items can store multiple types of data, such as transaction information, customer details, or information from a document. For more information, see [Queues implementation](https://www.servicenow.com/docs/fjiZ3FHBXryc5vYJk_F9SQ "In RPA Hub, the queues are implemented to distribute the workload among various robots. Work Items (WI) within a queue are processed simultaneously by two or more robots."). ## Work items {#rpa-hub-features__section_hcg_cpc_f3c} A work item is a record in a work queue that stores the data a robot needs to perform a specific task. Each item in the queue is processed separately, allowing robots to handle large workloads in smaller, manageable parts. For more information, see [Work items](https://www.servicenow.com/docs/daHbAA_Nxe43QssMecSjCw "A work item is a record in a work queue that stores the data a robot needs to perform a specific task."). ## Shared parameters {#rpa-hub-features__section_ltb_x4c_f3c} Shared parameters enable you to store the global variables or configurable items in one place. These variables are used across bot processes. For more information, see [Shared parameters](https://www.servicenow.com/docs/MyAa1U04nBsoPpPmij1uzQ "Shared parameters enable you to store the global variables or configurable items in one place. These variables are used across bot processes."). ## Process parameters {#rpa-hub-features__section_l1c_x4c_f3c} Process parameters store the variables that are used within a bot process. The process parameter can only be used by the bot process they are created in. For more information, see [Process parameters within a bot process](https://www.servicenow.com/docs/LKuLJA3HHgiYm3DgJU3jxA#create-process-parameter-botprocess "Create a process parameter to store the variables that are used within a bot process. The process parameter that you just created can only be used by this bot process."). ## Code quality checks {#rpa-hub-features__section_ohc_x4c_f3c} A code quality check refers to the process of evaluating the automation file or script to assess its adherence to coding standards, best practices, maintainability, and overall quality. Code quality checks are essential in RPA development life cycle, to ensure that the automation file is robust, efficient, and free from common issues that could lead to errors or difficulties in the future. For more information, see [Code quality checks](https://www.servicenow.com/docs/AymWcHiZsCvZBXI73dhFhg "A code quality check refers to the process of evaluating the automation file or script to assess its adherence to coding standards, best practices, maintainability, and overall quality."). ## Alert rule and variable {#rpa-hub-features__section_mjg_cpc_f3c} Alert rules are configurations that define conditions in which an alert or a notification must be triggered. These rules help in managing and responding to issues identified in automations. Alert variable refers to a variable or parameter associated with alerts in RPA Hub. For more information, see [Alert rule and variable](https://www.servicenow.com/docs/7dGXb1ZSJVg1mZDm9UDFNw "A rule that defines when and how the system should notify users about issues in automation execution."). ## Process jobs {#rpa-hub-features__section_ptf_cpc_f3c} A process job represents the execution of a bot process on a robot. For more information, see [View process jobs](https://www.servicenow.com/docs/SaRp85ikw2bxyvp6_j~Ysg#view-process-jobs-botprocess "View a list of execution logs of a bot process in RPA Hub."). ## Automation logs {#rpa-hub-features__section_umy_s1j_f3c} Automation logs are series of succession stages or a series of checkpoints that occur during the execution of a bot process. It enables monitoring and auditing the automation process. These logs are generated from the robot for unattended and attended bot processes. For more information, see [View automation logs](https://www.servicenow.com/docs/kt6L0efc60~IJsnE3O5DCw#view-automation-logs-rpa "Automation logs are series of succession stages or a series of checkpoints that occur during the execution of a bot process. It enables monitoring and auditing the automation process. These logs are generated from the robot for unattended and attended bot processes.").