---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Migrate the UI component from ITSM Agent Workspace to Service Operations Workspace

# Migrate the UI component from ITSM Agent Workspace to Service Operations Workspace {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Configure the UI component to migrate related list declarative actions from ITSM Agent Workspace to Service Operations Workspace.

## Before you begin

Role required: admin

## Procedure

1. Navigate to AllNow Experience FrameworkDeclarative ActionsRelated List actions.
2. Filter the records based for Implemented As is set as UI component.
3. View the log in the failed record in the migration process and find the sys_Id of the record from the list of Related List Actions.
4. Select the failed record with the corresponding sys_id.
5. Right-click on the header, and select Insert and Stay.
6. Clear the Workspace and View fields.
7. Select the Experience Restricted check box.
8. Update the value in the Implemented as field as <kbd class="ph userinput">UXF Client Action</kbd>.
9. In the Action configuration related list, select Edit, and then select SOW Actions from Collection to Action configurations list.
10. Select Save to save the Action configurations related list.
11. Select Update.  
    The migration utility supports MRA and interceptor declarative actions of UI Component type only.
12. For MRA, create an action payload as specified below, update the values in action attributes with component attributes of ITSM Agent Workspace declarative action.  
    If no value is filled in the ITSM Agent Workspace declarative action record, then fill the value with {{ key }}. For example, if the component attributes table is empty then in the payload the value should {{table}}.  

        { 

        "label": "label", 

                        "extensionPoint": "extensionPoint", 

                        "userGivenTable": "userGivenTable", 

                        "hideSelectAll": "hideSelectAll", 

                        "parentRecordSysId": "parentRecordSysId", 

                        "table": "table", 

                        "referencedFieldName": "referencedFieldName", 

                        "type": "type", 

                        "parentFieldName": "parentFieldName", 

                        "columns": "columns", 

                        "view": "view", 

                        "relatedListName": "relatedListName" 

                } 

13. For Interceptor, create an action payload as specified below in the sys_declarative_action_payload_definition table.  

        { 

            "table": "target", 

                        "sysId": "-1", 

                        "parentTable": "{{parentTable}}", 

                        "parentSysId": "{{parentRecordSysId}}", 

                        "referencedFieldName": "", 

                        "pageTitle": "Create " + tableLabel, 

                        "pageSubTitle": "Choose one of the following " + tableLabel + " types", 

                        "useDomain": false 

        } 

14. Add an add-on event mapping to the migrated declarative action.  
    Find the matching declarative action in SOW and add all the add-on event mapping to the migrated declarative action. Use the following steps to find the equivalent declarative action in SOW.
    1. Navigate to Allsys_ux_addon_event_mapping.list
    2. Filter the table and using the migrated <kbd class="ph userinput">tablename</kbd> and Target Payload Mapping contains <kbd class="ph userinput">mra</kbd> or <kbd class="ph userinput">interceptor route</kbd>.
    3. If the record is found, return the declarative action sys_id.  
       Iterate through all add-on event mappings of the found DA and add them to the migrated DA.
    4. If the record isn't found with the table, remove the table filter and search for targetPayload contains route=mra or interceptor.  
       For List and Field decorator, you must add the MRA and interceptor add-on event mappings manually. For more information, see [Create a UX add-on event mapping](https://www.servicenow.com/docs/access?context=create-a-ux-add-on-event-mapping&version=australia&pubname=australia-platform-user-interface&ft:locale=en-US).

    {#migrate-related-list-ui-component-aw-sow__substeps_acn_znj_dcc}  
    Note:  
    The Change_request interceptor record in ITSM Agent Workspace exists in SOW.  
    Migrating workspace space record type selector for the interceptor type of declarative action are:
    * ITSM Agent Workspace table: aw_record_type_selector
    * SOW table: sn_sow_interceptor_record_type_selector
    {#migrate-related-list-ui-component-aw-sow__ul_eql_3pj_dcc}

    For a change_request table that has a value as standard, Active is set as False when migrating the records from ITSM Agent Workspace to SOW.

*[\>]: and then