Combined Robotic Process Automation (RPA) Hub release notes for upgrades from Washington DC to Xanadu

  • Release version: Xanadu
  • Updated June 16, 2026
  • 13 minutes to read

    • Consolidated page of all release notes for Robotic Process Automation (RPA) Hub from Washington DC to Xanadu.

    How to use this page

    To help you prepare for your upgrade, we have combined the cross-family Robotic Process Automation (RPA) Hub release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Washington DC to Xanadu.

    Tip:
    If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release."

    Important information for upgrading Robotic Process Automation (RPA) Hub to Xanadu

    Before you upgrade to Xanadu, review these pre- and post-upgrade tasks and complete the tasks as needed.

    Release Release notes

    Washington DC
    Ensure that you upgrade any of the following currently installed Microsoft Software Installers (MSIs) by downloading the RPA applications:
    • RPA Desktop Design Studio
    • Attended Robot
    • Unattended Robot
    • Unattended Robot Login Agent
    For more information, see Download the RPA applications from RPA Hub.

    The following upgrade steps are applicable only when you’re upgrading from San Diego or Tokyo to Washington DC.

    Based on the number of records in the application file table, you could experience a potential delay while upgrading the RPA Hub applications from Tokyo or before to Washington DC.

    Before upgrading RPA Hub to Washington DC, you must set the value of the glide.rollback.blacklist.TableParentChange.change system property to false. If this property doesn't exist in the System Property [sys_properties] table, add the property and set its value to false. For more information on how to add a property, see Add a system property.

    After you upgrade to the Washington DC, the bot process definitions change to the new structure, which is the bot process configuration.

    Although the bot process configuration doesn't replace the bot process completely, most fields are moved from bot process to bot process configuration. If you upgrade to the Utah version without updating the system property value, the tables don’t extend the Application File table. To update the table changes manually, see the Restructuring RPA Hub tables to sys_metadata in Utah article in the Now Support Knowledge Base.

    Xanadu

    		 No updates for this release.

    New features

    Between your current release family and Xanadu, new features were introduced for Robotic Process Automation (RPA) Hub.

    Release Release notes

    Washington DC
    Embedded Task Automation in RPA Hub

    Trigger attended bot processes, also known as attended automations, from the ServiceNow forms, playbooks, workspaces, and so on.

    To trigger this bot process from the ServiceNow form, select the Enable Embedded Task Automation check box in the Attended Bot Process form. After enabling this check box, two additional tabs, Process Field Parameters and Attended Configuration, are available on the Bot Process form. For more information about the Bot Process form, see Bot Process form.

    On the Process Field Parameters tab, create dynamic parameters that are used in the bot process. Process field parameters are used for setting a value or getting the value of a field on a particular form. For more information about creating process field parameters, see Create a process field parameter in RPA Hub. You can also create a parameter from the Field Parameter Mappings tab by selecting the Create parameter button from the Attended Configurations menu. For more information, see Map a table field to a bot process field parameter in RPA Hub.

    In the RPA Hub workspace, create an attended configuration record. For more information about creating an attended configuration record, see Create an attended configuration record in RPA Hub.

    On the Field Parameter Mappings tab, map the form fields to the process field parameters that are used in the automations. This process enables an easy data flow during the execution of a bot process. For more information about mapping field parameters, see Map a table field to a bot process field parameter in RPA Hub.

    Activate the attended configuration record to trigger the attended bot process. For more information, see Activate an attended configuration record in RPA Hub.

    New components for Embedded Task Automation
    The following four new components are added to the new Forms section in RPA Desktop Design Studio. These components are available under the new ServiceNow category in the Toolbox pane.
    • AttendedConfigurations component: Segregate the execution of the automations in a single automation project and call the respective logic according to the action invoked. For more information, see Use the AttendedConfigurations component.
    • GetProcessFieldParameters component: Fetch the values of the ServiceNow form fields associated in the Field Parameter Mapping of the corresponding attended configuration record in RPA Hub. For more information, see Use the GetProcessFieldParameters component.
    • GetRecordContextID component: Fetch the current record sys_id of the ServiceNow form, from where the automation is triggered. For more information, see Use the GetRecordContextID component.
    • SetProcessFieldParameters component: Update the values of the ServiceNow form fields associated in the Field Parameter Mapping of the corresponding attended configuration record in RPA Hub. For more information, see Use the SetProcessFieldParameters component.
    External credential vault in RPA Hub
    In RPA Hub, you can retrieve robot credentials, application credentials, or Time-based One-time Password (TOTP) seeds from the external credential vault.

    Create an external credential vault record in RPA Hub to register your external credential vault for further usage by the robot. For more information, see Create an external credential vault record in RPA Hub.

    A new External Credential check box is available in the credential set form, an application credential form, and a TOTP authenticator form. If this check box is selected, the credentials or TOTP seed is fetched from a configured external credential vault. If the check box is selected in the TOTP authenticator form, the seed is fetched from a configured external credential vault. For more information about these forms, see Create a credential set within a bot process, Create an application credential set in RPA Hub, and Create a TOTP authenticator in RPA Hub.

    If the application credential record has the External Credential check box enabled, then the SetApplicationCredential component in RPA Desktop Design Studio doesn’t set the credentials and displays an error. For more information about the SetApplicationCredential component, see Use the SetApplicationCredential component.

    Use the steps listed in the Steps to configure an external credential vault in RPA Hub topic to guide you through all the tasks of configuring an external credential vault in RPA Hub.

    Storage of process execution data in flat files

    In RPA Hub, you can configure the output type as flat files for the execution logs that are generated on the robot machine.

    On the Bot Process form, select an output type of the execution log file from the Output Type field from the Log Settings section. This field appears when the Track Execution Logs option is selected and when the Robot Machine is selected from the Storage field.

    The location of the flat files is Users\<Userprofile>\ServiceNow RPA Logs\.executionlogs\{InstanceName}\.archive\{ProcessJob number} in the machine on which you have installed the attended or unattended robot.

    If the size of the flat file exceeds 10 MB, it splits into multiple flat files with the log sequence appended to the file names until it executes the automation. A flat file doesn't log the data of input or output ports in a component or method that you have selected as Mark Data as Sensitive in the RPA Desktop Design Studio.

    New Workflow Studio Actions and Subflow
    Invoke the following new actions and subflow in Workflow Studio:
    • Change Life Cycle Stage Status of a Bot Process Action to modify the life cycle stage status of a bot process that is not retired.
    • Stop Process Action and Stop Process subflow to stop a bot process. If the robot pool option is enabled for the bot process, it stops all the robots assigned to the pool. If Graceful Stop is enabled, it provides a capability for robots to exit the automation smoothly. Graceful Stop is not applicable for bot processes with the robot pool option enabled.
    Wait for any screen method at the Universal App Connector level

    In RPA Desktop Design Studio, the WaitForAnyScreen method appears in the Object Explorer pane when you double-click the Universal App connector object under the Global Objects pane.

    The WaitForAnyScreen method finds an application screen within a specified duration, and then you can enable it to pass the control to another method. You can set up multiple application screens that appear in an order on the method, and the WaitForAnyScreen method tries to find a screen starting from the first application screen by matching the screen match rules. If the method doesn't find a screen, it tries to find the next screen in the order. However, if the method finds a screen, it completes execution and doesn't proceed to the screens next in the order. If the method doesn't find any screen within the specified duration, you may optionally enable it to pass the control to another component through the ELSE port.

    SetPassword Method
    In RPA Desktop Design Studio, the SetPassword method automates securely entering a password in the password field of a web-based, Java, or Windows application. It accepts the password as a SECURE STRING type and then enters it in the password field.
    SimulateMouseEvent Method
    In the RPA Desktop Design Studio, the SimulateMouseEvent method automates simulating a mouse event on an element on a web-based application. For example, automate the right-click mouse event on a button to open a context menu. The screen element on which the mouse event occurs must priorly have the mouse event defined in the HTML. The method supports a list of mouse events and mouse button types.
    IEnumerable data type port in connectors
    The IEnumerable input data type enables methods to accept arrays, array lists, and lists. This input data type port is available in multiple connectors.
    Universal App connector supports Shadow DOM elements
    The XPath and the CssSelector locators in the Universal App connector shows the full XPath and CSS path with the Shadow DOM elements, if a web application uses Shadow DOM.

    Xanadu

    		 No updates for this release.

    Changes

    Between your current release family and Xanadu, some changes were made to existing Robotic Process Automation (RPA) Hub features.

    Release Release notes

    Washington DC
    Manage plugins from a single location
    In the RPA Desktop Design Studio, install, view, update, or remove plugins from the Plugin Manager window or the Plugins node in the Project Explorer pane.
    New location for the Attachments and Workflow Studio components in the Toolbox pane
    In RPA Desktop Design Studio, the Attachments and Workflow Studio components are available under the new ServiceNow category in the Toolbox pane.

    Xanadu

    		 No updates for this release.

    Removed

    Between your current release family and Xanadu, some Robotic Process Automation (RPA) Hub features or functionality were removed.

    Release Release notes

    Washington DC

    		 No updates for this release.

    Xanadu

    		 No updates for this release.

    Deprecations

    Between your current release family and Xanadu, some Robotic Process Automation (RPA) Hub features or functionality were deprecated.

    Release Release notes

    Washington DC

    		 No updates for this release.

    Xanadu

    		 No updates for this release.

    Activation information

    Review information on how to activate Robotic Process Automation (RPA) Hub.

    Release Release notes

    Washington DC

    Install RPA Hub by requesting it from the ServiceNow Store.

    For cumulative release notes information on RPA Hub, see RPA Hub release notes.

    For cumulative release notes information on RPA Desktop Design Studio, see RPA Plugin Bundle release notes.

    For cumulative release notes information on RPA sample templates, see RPA sample template release notes.

    If you have previously downloaded the application from the ServiceNow Store and a new version is available, you can update it in your ServiceNow AI Platform instance at All > System Applications > All Available Applications.

    Xanadu

    		 No updates for this release.

    Additional requirements

    If any additional requirements were introduced or changed for Robotic Process Automation (RPA) Hub we have noted them here.

    Release Release notes

    Washington DC
    To use the Unattended Robot application, the minimum requirements are as follows:
    • Intel Processor (1vCPU).
    • 4-GB RAM.
    • Minimum 20-GB free disk space after installing the OS, patches, and base software.
    • Microsoft Windows 10 or Windows Server 2016 or Windows Server 2019.
    • .NET Framework 4.7.1 or later.
    • DPI scaling setting must be deactivated.
    To use the Unattended Robot application, the recommended requirements are:
    • Intel Processor (4vCPU).
    • 8-GB RAM.
    • Minimum 50-GB free disk space after installing the OS, patches, and base software.
    • Microsoft Windows 10 or Windows Server 2016 or Windows Server 2019.
    • .NET Framework 4.7.1 or later.
    • DPI scaling setting must be deactivated.

    An unattended robot is mapped to only one machine.

    Virtual Machines (VMs) that are used for the Unattended Robot application must be persistent and constantly on.

    To use the Attended Robot application, the minimum requirements are as follows:
    • Intel Processor (1vCPU).
    • 4-GB RAM.
    • Minimum 20-GB free disk space after installing OS, patches, and base software.
    • Microsoft Windows 10 or Windows Server 2016 or Windows Server 2019.
    • .NET Framework 4.7.1 or later.
    • DPI scaling setting must be deactivated.
    To use the Attended Robot application, the recommended requirements are as follows:
    • Intel Processor (4vCPU).
    • 8-GB RAM.
    • Minimum 50-GB free disk space after installing the OS, patches, and base software.
    • Microsoft Windows 10 or Windows Server 2016 or Windows Server 2019.
    • .NET Framework 4.7.1 or later.
    • DPI scaling setting must be deactivated.

    An attended robot is mapped to only one user.

    To use the RPA Desktop Design Studio application, the minimum requirements are as follows:
    • Intel Processor (Core i5 or later)
    • 4-GB RAM.
    • 20-GB free disk space.
    • Microsoft Windows 10 or Windows Server 2016 or Windows Server 2019.
    • .NET Framework 4.7.1 or later.
    • Monitor with 1920x1080p resolution.
    • DPI scaling setting must be deactivated.
    To use the RPA Desktop Design Studio application, the recommended requirements are as follows:
    • Intel Processor (Core i7).
    • 8-GB RAM.
    • 50-GB free disk space.
    • Microsoft Windows 10 or Windows Server 2016 or Windows Server 2019.
    • .NET Framework 4.7.1 or later.
    • Monitor with 1920x1080p resolution.
    • DPI scaling setting must be deactivated.

    Xanadu

    		 No updates for this release.

    Browser requirements

    If any specific browser requirements were introduced or changed for Robotic Process Automation (RPA) Hub we have noted them here.

    Release Release notes

    Washington DC

    ServiceNow workspaces don’t support mobile devices. For more information about the list of supported browsers, see Browser support.

    Xanadu

    		 No updates for this release.

    Accessibility information

    Review details on accessibility information for Robotic Process Automation (RPA) Hub, such as specific requirements or compliance levels.

    Release Release notes

    Washington DC

    		 No updates for this release.

    Xanadu

    		 No updates for this release.

    Localization information

    If there are specific localization considerations for Robotic Process Automation (RPA) Hub we have noted them here.

    Release Release notes

    Washington DC

    RPA Hub supports international languages. For more information, see Internationalization support for RPA Hub.

    Xanadu

    		 No updates for this release.

    Highlight information

    If there are specific highlight considerations for Robotic Process Automation (RPA) Hub we have noted them here.

    Release Release notes

    Washington DC
    • Use the Embedded Task Automation feature to trigger attended bot processes, also known as attended automations, from ServiceNow forms, playbooks, workspaces, and so on.
    • Retrieve sensitive information, such as usernames and passwords, securely from various external vaults by enabling the external credential vault feature in RPA Hub.
    • Store the logs of a process execution in a readable format through flat files.
    • New actions and subflow such as Change Life Cycle Stage Status of a Bot Process Action, Stop Process Action, and Stop Process Subflow are available in the Workflow Studio that further refine RPA integration via flows, subflows, and APIs.
    • Enhanced Universal App Connector.

    See Robotic Process Automation (RPA) Hub for more information.

    Xanadu

    		 No updates for this release.