--- sourceDocument: Brazil IT Service Management sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil IT Service Management ft:clusterId : - itsm bundleId : - itsm workflow : - Technology --- # Migration of Agent assist from ITSM Agent Workspace to Service Operations Workspace for ITSM # Migration of Agent assist from ITSM Agent Workspace to Service Operations Workspace for ITSM {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Migration of Agent assist from ITSM Agent Workspace to Service Operations Workspace for ITSM This guide explains the migration process for Agent assist configurations from ITSM Agent Workspace to Service Operations Workspace (SOW) within ServiceNow's ITSM Brazil release. The migration focuses on transferring relevant configuration data, identifying eligible records, and addressing potential limitations. The goal is to ensure Agent assist functionality continues seamlessly in the new workspace environment. Show full answer Show less ## Key Features * **Tables Involved in Migration:** * **cxstableconfig:** Stores all Agent assist configurations for both ITSM Agent Workspace and SOW. * **declarativeactionassignment:** Contains references (sysid) to cxstableconfig records for ITSM Agent Workspace configurations. * **sysuxscreen:** Holds the Agent Assist SNC record in SOW, where the Macroponent Configuration field maps tables to their cxstableconfig sysid. * **Configuration Differences:** * In ITSM Agent Workspace, Agent assist configurations are tied to declarative actions using the UI component `now-agent-assist` and stored in `cxstableconfig`. * In SOW, configurations are stored within the Agent Assist SNC record in `sysuxscreen`, linking each table to its configuration. * **Migration Identification Criteria:** The migration utility selects Agent assist configurations for migration only if: * The Workspace field equals "Agent Workspace". * The UI component is `now-agent-assist`. * The Table field corresponds to a migratable table. * The configuration is active. * **Migration Process:** The utility searches the `sysdeclarativeactionassignment` table for the latest qualifying record per table and copies its `cxsTableConfig` value into the corresponding SOW Agent Assist SNC record. * **Handling Multiple Configurations:** If multiple configurations exist for the same table, only the most recently updated active configuration is migrated. ## Limitations * If multiple Agent assist configurations exist for the same table, only the latest updated configuration migrates. * Migration overwrites any pre-existing Agent assist configurations in SOW. ## Post-Migration Actions * Verify that migrated Agent assist configurations in SOW align with those from ITSM Agent Workspace. * Adjust the migrated configurations in SOW as needed to suit your operational requirements. Migration of the Agent assist from ITSM Agent Workspace to Service Operations Workspace (SOW) include identifying the required tables, eligible form header records for migrations and the migrations process. ## Tables used for migration {#agent-assist-migration-itsm-aw-sow__section_fkp_lfq_dcc} {#agent-assist-migration-itsm-aw-sow__table_vlt_nfq_dcc__entry__2} | Table name | Description | |-|-| | cxs_table_config | Table that contains all the Agent assist configurations in ITSM Agent Workspace and SOW. | | declarative_action_assignment | Table that contains the sys_id of the cxs_table_config record in the component attributes with the cxsTableConfig key name in ITSM Agent Workspace. | | sys_ux_screen | Tables that contains the sys_id of the cxs_table_config record in the Macroponent Configuration field of the Agent Assist SNC (468f70f443b47110cc25ff53e9b8f296) record. This record is available in the base system. | [ ] {#agent-assist-migration-itsm-aw-sow__table_vlt_nfq_dcc} ## Limitations {#agent-assist-migration-itsm-aw-sow__section_ln2_yvj_dcc} When migrating agent assist configurations from ITSM Agent Workspace to SOW, you may encounter any of the following issues: * If customer has configured more than one Agent assist configuration on the same table, the most recently updated configuration is migrated. * The Agent assist migration from ITSM Agent Workspace overrides any pre-existing changes in SOW. {#agent-assist-migration-itsm-aw-sow__ul_qsg_zvj_dcc} ## Configuring Agent assist in ITSM Agent Workspace and SOW {#agent-assist-migration-itsm-aw-sow__section_ggj_2tj_dcc} You can configure Agent assist in ITSM Agent Workspace and SOW using the following tables: * For ITSM Agent Workspace, Agent Assist configuration data exist in the following tables where the configuration data is stored: * Agent assist is configured on a particular table using a declarative action with the UI component now-agent-assist. * Configuration is stored in the cxs_table_config table. * Declarative action on the table stores the sys_id of the cxs_table_config record in the component attributes with the cxsTableConfig key name. {#agent-assist-migration-itsm-aw-sow__ul_qkl_d5j_dcc} * For SOW, Agent assist configuration data exist in the following tables: * The configuration record from cxs_table_config is stored in the Agent Assist SNC record from sys_ux_screen. * In SOW, a field named Macroponent Configuration contains the mapping of each individual table with its configured sys_id of cxs_table_config record. {#agent-assist-migration-itsm-aw-sow__ul_vwb_g5j_dcc} {#agent-assist-migration-itsm-aw-sow__ul_dfk_c5j_dcc} ## How the migration utility identifies Agent assist for migration {#agent-assist-migration-itsm-aw-sow__section_bcz_35j_dcc} The SOW migration utility identifies the eligible agent assist configuration records for migration from ITSM Agent Workspace to SOW only if the configuration records meet the following conditions: * The Workspace field is set to Agent Workspace. * The ui_component field has the value now-agent-assist. * The Table field is set to a value (table) for which migration must be done. * The Active check box is selected. {#agent-assist-migration-itsm-aw-sow__ul_unh_k5j_dcc} ## How the migration works {#agent-assist-migration-itsm-aw-sow__section_knd_y5j_dcc} The SOW migration utility uses the following sequence to migrate Agent assist from ITSM Agent Workspace to SOW: 1. Searches the sys_declarative_action_assignment table with the following conditions and only retrieves the record which is recently updated. * The Workspace field is set to Agent Workspace. * The ui_component field has the value now-agent-assist. * The Table field is set to a value (table) for which migration must be done. * The Active check box is selected. {#agent-assist-migration-itsm-aw-sow__ul_j4h_dvj_dcc} 2. If the sys_declarative_action_assignment record is found with the conditions, then the value in the cxsTableConfig is copied to the Agent assist SNC record from the sys_ux_screen against its corresponding table key. The following screenshot depicts sys_id's of all the record types in the Macroponent Configuration field of the Agent assist SNC record. The following screenshot depicts the Agent assist for incident sys_id record that contains the cxsTableConfig as the component attributes. 3. If multiple configurations exist for same table, the SOW migration utility migrates the one that was most recently updated. 4. If an active configuration is not found in the table then the sow configuration remains same and is not updated. {#agent-assist-migration-itsm-aw-sow__ol_gdw_z5j_dcc} * **[Perform post-migration tasks for Agent assist configuration](https://www.servicenow.com/docs/li3Ya7xeP8Fq9Dih0fa8Qw)** Verify that the Agent assist configurations in Service Operations Workspace (SOW) are consistent with the Agent assist configurations in ITSM Agent Workspace (ITSM AW) and are ready for use in SOW. You can update the migrated Agent assist configuration settings in SOW based on your requirements. **Related reference** * [Migration of UI actions and layouts from ITSM Agent Workspace to Service Operations Workspace for ITSM](https://www.servicenow.com/docs/ZPvRTrRamu4FlIJhRWLqEg "Migration from ITSM Agent Workspace to Service Operations Workspace for ITSM includes identifying the required tables, identifying the eligible UI actions and layout records for migrations, and the migration process.") * [Ribbons migration from ITSM Agent Workspace to Service Operations Workspace for ITSM](https://www.servicenow.com/docs/~VwSG9aNtiRfBmJGo_N_xA "Migration of the ribbons from ITSM Agent Workspace to Service Operations Workspace for ITSM includes identifying the required tables, identifying ribbons records for migration, and the migration process.") * [Migration of view rules from ITSM Agent Workspace to Service Operations Workspace for ITSM](https://www.servicenow.com/docs/aNHwtAKHKq5MTgj~wypoPg "Migration of view rules from ITSM Agent Workspace to Service Operations Workspace for ITSM includes identifying the required tables, identifying the view rules for migrations, and the migration process.") * [New record menu items migration from ITSM Agent Workspace to Service Operations Workspace for ITSM](https://www.servicenow.com/docs/j9qmU5myK5UdAiPOQ7X1VQ "Migration of the new record menu items from ITSM Agent Workspace to Service Operations Workspace for ITSM includes identifying the required tables, identifying new record menu items for migrations, and the migration process.") * [Migration of highlighted fields in lists and forms from ITSM Agent Workspace to Service Operations Workspace for ITSM](https://www.servicenow.com/docs/AjuYC05mLHx2q_upS1nivA "Migration of the highlighted fields in lists and forms from ITSM Agent Workspace to Service Operations Workspace for ITSM includes identifying the required tables, identifying eligible highlighted field records for migrations, and the migration process.") * [List actions migration from ITSM Agent Workspace to Service Operations Workspace for ITSM](https://www.servicenow.com/docs/1aEAZc2DE8rYlNiSjyFkJQ "Migration of the list actions from ITSM Agent Workspace to Service Operations Workspace for ITSM includes identifying the tables and the migration process.") * [List categories and modules migration from ITSM Agent Workspace to Service Operations Workspace for ITSM](https://www.servicenow.com/docs/SYta1nzl3JSZ9XUDipvjCw "Migration from ITSM Agent Workspace to Service Operations Workspace (SOW) for ITSM includes identifying the required tables, highlighted field records for migrations, and the migration process.") * [Migration of form headers from ITSM Agent Workspace to Service Operations Workspace for ITSM](https://www.servicenow.com/docs/TXX4UxfEFhHW~tk711h4YQ "Migration of the form headers from ITSM Agent Workspace to Service Operations Workspace (SOW) include identifying the required tables, eligible form header records for migrations and the migration process. Form headers provide an overview of the record.") * [Migration of search configurations from ITSM Agent Workspace to Service Operations Workspace for ITSM](https://www.servicenow.com/docs/WgEtlhVPa7rF3gStGSorNg "Migration of the search configuration from ITSM Agent Workspace to Service Operations Workspace (SOW) include identifying the eligible form header records and the migration process.") * [Migration of Related list declarative actions from ITSM Agent Workspace to Service Operations Workspace for ITSM](https://www.servicenow.com/docs/AcE16p9nkC8Quj0wnWrbVw "Migration of the related list declarative actions from ITSM Agent Workspace to Service Operations Workspace that includes identifying the tables and the migration process.") * [Migration of field decorators from ITSM Agent Workspace to Service Operations Workspace for ITSM](https://www.servicenow.com/docs/UV0PJfP~C5osMGTCL5uh0g "Migration of the field decorators actions from ITSM Agent Workspace to Service Operations Workspace that includes identifying the tables and the migration process.")