Migration of search configurations from ITSM Agent Workspace to Service Operations Workspace for ITSM

  • Release version: Australia
  • Updated March 12, 2026
  • 3 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 Search Configurations from ITSM Agent Workspace to Service Operations Workspace for ITSM

    The migration of search configurations from ITSM Agent Workspace to Service Operations Workspace (SOW) involves identifying eligible records and executing a systematic migration process. The goal is to ensure that search functionalities are seamlessly transitioned to the SOW environment, enhancing operational efficiency.

    Show full answer Show less

    Key Features

    • Identification of Search Configurations: The migration utility filters application search source records linked to ITSM Agent Workspace and identifies those not mapped to SOW, ensuring unique configurations are addressed.
    • Order Management: The utility updates the order of search mappings in SOW to match those in ITSM Agent Workspace when discrepancies are found.
    • Search Configuration Migration: It facilitates the transfer of search view configurations and updates relevant SOW page properties to reflect the new mappings.
    • Post-Migration Verification: Users can verify that all migrated search configurations in SOW are consistent and ready for operational use.

    Key Outcomes

    Upon successful migration, customers can expect:

    • Enhanced search capabilities within SOW, reflecting the configurations from ITSM Agent Workspace.
    • The ability to modify migrated search settings post-migration to suit specific operational needs.
    • A streamlined process for managing search configurations, ensuring that necessary search functionalities are accessible in SOW.

    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.

    How the migration utility identifies search configuration for migration

    The migration utility in SOW identifies the eligible set of search configuration records to be migrated based on the following sequence:
    1. Filters the application search sources records (sys_search_source) that are mapped to ITSM Agent Workspace master config record using the m2m_search_context_config_search_source table.
    2. Checks the application search sources that are mapped to SOW context config record.
    3. Searches each filtered record that are mapped to ITSM Agent Workspace master config record and checks if that record is not mapped to SOW context config record to identify the search sources which are unique to ITSM Agent Workspace only and not mapped to SOW context config record.
    4. For all those unique search records that are mapped to ITSM Agent Workspace, the SOW migration utility creates similar mapping to SOW context config record at m2m_search_context_config_search_source table.
    5. If common search sources mapped between ITSM Agent Workspace and SOW are found and the order of the mapping is differed in SOW from ITSM Agent Workspace, the SOW migration utility updates the order from ITSM Agent Workspace mapping to SOW mapping.
    6. Migrates the values of ITSM Agent Workspace search view config record to SOW search view config record.
    7. When both the search view config and the search sources are mapped to SOW from ITSM Agent Workspace, the SOW migration utility updates the globalSearchDataConfigIdSOW page property to reflect SOW context config record available in the base system.

    How the migration works

    The SOW migration utility uses the following sequence to migrate the search configuration records from ITSM Agent Workspace to SOW:
    1. Searches the reference record for Global Search Data Config and Global Search View Config using the sys_aw_master_config table in ITSM Agent Workspace.
    2. Determines the Search engine type in the Global Search Data Config record. If the search engine is zing then migration proceeds. Else, the migration process stops.
    3. Using the Global Search Data Config record, a query is run on the Application Search Sources (m2m_search_context_config_search_source) table to retrieve all the search sources.
    4. Using the SOW search context config available in the base system, a query is executed on the Application Search Sources (m2m_search_context_config_search_source) table to retrieve all the search sources.

      The SOW search context config exists as a record in the sys_search_context_config table and sys_id can be found at SOW page property called globalSearchDataConfigId.

    5. Compares between the search sources by executing a query on the Application Search Sources (m2m_search_context_config_search_source) table using Global Search Data Config record (ITSM Agent Workspace search sources) and SOW search context config record (SOW search sources), to find unique search sources mapped to ITSM Agent Workspace but not SOW.
    6. If the order value of a SOW search source is different than the order value of the ITSM Agent Workspace search source at the Application Search Sources table, the SOW migration utility updates the SOW search source with the same order value as in mapped in ITSM Agent Workspace.
    7. Creates record in the Application Search Sources (m2m_search_context_config_search_source) table with SOW context config record that is available in the base system and searches the unique sources that are found by comparing the ITSM Agent Workspace search sources and SOW search sources.
    8. Opens the Global Search View Config reference record that is retrieved using the sys_aw_master_config table in ITSM Agent Workspace and copy all the values to SOW view config record (SOW page property with name global_search_configurations). The SOW view config record is available in the base system.
    9. Updates the SOW page property globalSearchDataConfigId to have OOB SOW context config record.