RPA release managers or RPA admins select code quality check rules from a pre-defined set in the RPA Hub instance. Then, the RPA Desktop Design Studio performs an in-built code quality check before publishing a package.

RPA developers can also perform a pro-active code quality check on a package in the RPA Desktop Design Studio, by inspecting an activity or a complete automation project for any issues by using the Code Quality Check feature.

The issues and their details are displayed in the Code Quality Check Results window. Troubleshoot the issues before you publish the automation project to RPA Hub. For more information on how to perform the code quality check in RPA Desktop Design Studio, see Code quality check in RPA Desktop Design Studio.

If an error or a warning occurs in the automation, a decision is derived if the package can be published successfully or not, based on the system property configuration (error, warning, or no restrictions).

To view a list of the pre-defined code quality rules in the RPA Hub instance, see Code quality rules list.

View a code quality rule form along with the type and description. For more information, see Code quality rule form.

In the code quality rule form, RPA release managers and admins can edit the Severity, Regular Expression, Active, and Value fields.

To enable the code quality check at the instance level, ensure that you mark the new system property sn_rpa_fdn.enable_code_quality_check as true.

Track scheduled maintenance (SM) days on the robot calendar for an optimum functioning of the bot processes and to take preventive measures.

After a change request is created, it reflects as a scheduled maintenance day on the robot calendar, only when the change request is either in Scheduled, Implement, or Review states. An associated scheduled maintenance event card appears on the robot calendar to track the scheduled maintenance day.

RPA release managers and RPA admins have visibility to the potential impacts on the current or future automation executions. They can take an appropriate call to action. Such as, either to accept or reject an associated scheduled maintenance event card of the configuration item (associated robot or a bot process) on the robot calendar. As a result of this action, a maintenance request is created for tracking purposes. For more information, see Manage scheduled maintenance days in RPA Hub and View maintenance requests in RPA Hub.

Create a robot pool record in RPA Hub from the Robot Pool menu for an optimum utilization of robots to execute the bot processes.

Enable the robot pool option for a bot process on the Bot Process form to allocate robots dynamically, for the bot process execution. For more information, see Enable robot pool for a bot process in RPA Hub.

Associate a queue with a bot process before you enable the robot pool option. For more information, see Associate a queue to the bot process from the related list.

Select and configure the robot pool fields on the Bot Process form to define the allocation type. For more information, see Bot Process form.

Configure the robot pool related fields for Average Handling Time (AHT) calculation on the Queue form. For more information, see Queue form.

Calculate the number of robots required with a new UI button Calculate. Based on allocation type, Service Level Agreement (SLA) or percentage reduction, the robots are allocated from the selected robot pool to execute the bot process. For more information, see Calculate the number of robots in RPA Hub.

Access the robot calendar for the robots assigned to a robot pool. On the ribbon of the robot calendar, you can see the associated robot pool name along with robot type, robot state, and so on.

Right-click or double-click an empty slot of the robot calendar to create a schedule. These options are available along with the New Schedule button on the robot calendar.

However, the RPA support user or developer must be a part of the Managed By Group list to access this functionality.

• Select the view bot process details icon () to get the bot process details in a new tab.
• Select the view event details icon () to view more details about the schedule in the contextual side panel.
• Select the edit schedule icon () to edit an existing schedule.
• Select the delete schedule icon () to delete a schedule that you no longer need.

Access the RPA Hub Workspace from the Workspaces tab of an instance.

Another way to access the RPA Hub is by navigating to All > Robotic Process Automation > RPA Hub Workspace. For more information, see RPA Hub Workspace.

In the navigation menu, the RPA Hub Workspace label is changed from RPA Hub.

Configure the new robot pool related fields for Average Handling Time (AHT) calculation on the Queue form. The new fields are Include All Work Items and Work Item Count.

For more information, see Queue form.

Associate a queue to a bot process from the Queues tab. It’s available on the related list of the bot process.

For more information, see Associate a queue to the bot process from the related list.

RPA developers, support users, and business users can view the list of queues.

They have access only those queues and work items that are associated to a bot process, assigned to them. However, they must be a part of the Managed By Group list to access this functionality.

Previously for unattended automations, the process job record for a bot process was created only when the unattended robot logs in to the robot machine successfully or unsuccessfully.

Now, a process job record gets created as soon as the unattended robot starts initiating the bot process in the robot machine. The Message field is updated during the different stages of the process that provides insight and visibility regarding the status of your bot process. For more information on how to run an automation by using Unattended Robot, see Using Unattended Robot.

For more information on how to use Flow Designer components in RPA Desktop Design Studio, see Flow Designer components