Migration of Agent assist from ITSM Agent Workspace to Service Operations Workspace for ITSM

  • Release version: Zurich
  • Updated July 31, 2025
  • 2 minutes to read
    • Summarize
    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 process enables ServiceNow customers to migrate Agent Assist configurations from the ITSM Agent Workspace to the Service Operations Workspace (SOW) as part of the Zurich release. The migration involves identifying and transferring relevant configuration records across specific tables to ensure continuity and functionality of Agent Assist in the new workspace environment.

    Show full answer Show less

    Key Features

    • Tables Involved: Migration uses the cxstableconfig table (holds Agent Assist configurations), declarativeactionassignment table (links configurations via sysid), and sysuxscreen table (stores configuration mappings in SOW).
    • Configuration Identification: The migration utility selects eligible Agent Assist configurations based on these conditions:
      • Workspace field set to "Agent Workspace".
      • uicomponent field equals "now-agent-assist".
      • Active configurations on tables targeted for migration.
    • Migration Logic: The utility searches for the most recently updated active declarative action assignment records and transfers their cxsTableConfig sysid values to the corresponding SOW Agent Assist SNC record in the sysuxscreen table.
    • Configuration Management: In ITSM Agent Workspace, Agent Assist is configured via declarative actions linked to specific tables. In SOW, these configurations are represented within the Macroponent Configuration field mapped to the respective tables.

    Limitations

    • If multiple Agent Assist configurations exist for the same table, only the most recently updated configuration is migrated.
    • Migrating will overwrite any pre-existing Agent Assist configurations in the Service Operations Workspace.

    Post-Migration Guidance

    After migration, verify that Agent Assist configurations in the Service Operations Workspace align with those from the ITSM Agent Workspace. Adjust migrated configurations in SOW as necessary to meet operational needs.

    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

    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.

    Limitations

    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.

    Configuring Agent assist in ITSM Agent Workspace and SOW

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

    How the migration utility identifies Agent assist for migration

    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.

    How the migration works

    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.
    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. Agent assist SNC record

      The following screenshot depicts the Agent assist for incident sys_id record that contains the cxsTableConfig as the component attributes. Agent assist incident

    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.