---
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


---

# Restructuring RPA Hub tables

# Restructuring RPA Hub tables {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Starting with the Utah release, the Robotic Process Automation (RPA) tables are restructured to an application file, so
that changes that you make to these tables are captured in the update sets and can be moved
seamlessly across environments. With this process, you don't have to re-create the data records
in the targeted environment.
The table architecture that supports the RPA Hub application has been
restructured to extend the Application file (sys_metadata). This action automatically
captures all the data into the update sets.

If you are upgrading from Tokyo or older to Brazil, the bot process definitions change to the new structure, that is the bot process configuration.  
The following diagram shows the tables of RPA Hub before restructuring.Figure 1. RPA Hub tables before restructuring  
The following diagram shows the tables of RPA Hub after restructuring.Figure 2. RPA Hub tables after restructuring

For detailed information about the script that restructures the tables during an upgrade, see the [Restructuring RPA Hub tables to sys_metadata in Utah](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1223629) article in the Now Support
Knowledge Base.