Migrate the client action from ITSM Agent Workspace to Service Operations Workspace for ITSM

Configure the client actions to migrate list actions from ITSM Agent Workspace to Service Operations Workspace for ITSM.

Before you begin

When performing the migration, you must have selected the List actions option for ITSM Agent Workspace features. For example, the List actions option for List. For information about the migration process, see Migrate from ITSM Agent Workspace to Service Operations Workspace for ITSM.

Role required: admin

About this task

At the end of the migration process, a confirmation message specifies if the migration is successful or not. You can review the migration information and perform the post-migration steps to confirm successful migration of your configuration or customization.

Procedure

1. Navigate to All > Now Experience Framework > Declarative Actions > List actions.
2. Filter the records based for Implemented As is set as Client action.
3. View the log in the failed record in the migration process and find the sys_Id of the record from the List Actions list.
4. Select the failed record with the corresponding sys_id.
5. Select and hold (or 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 UXF Client Action.
9. In the Action configuration related list, select Edit, and then select SOW Actions from the Collection list to the Action configurations list.
10. Save the Action configurations list by selecting Save.
11. Select Update.
12. If the client action key is ITEM_SELECTED or PREVIEW_RECORD, create a CREATE_NEW_RECORD key with the code block payload for the Action Payload Definition [sys_declarative_action_payload_definition] table.

    This step is performed only once.

    { 
                "route": "record", 
                "fields": { 
                    "table": "{{table}}", 
                    "sysId": "-1" 
                }, 
                "params": { 
                    "query": "{{query}}", 
                    "parentTable": "{{parentTable}}", 
                    "parentRecordSysId": "{{parentRecordSysId}}" 
                }, 
                "parent_table": "{{parentTable}}", 
                "additional_data": { 
                    "query": "{{query}}" 
                } 
            } 

13. Modify the client action created for ITEM_SELECTED and PREVIEW_RECORD list records.

    When you modify the client action, the payload map in action attributes should be transformed based on the payload.

    The following tables are used in the migration process:

    • M2m Action Assig Ux Action Config [sys_ux_m2m_action_assignment_action_config]
    • Action Payload Definition [sys_declarative_action_payload_definition]

    Note:

    The ITEM_SELECTED and PREVIEW_RECORD actions function in the ITSM Agent Workspace but not in SOW. Therefore, an action payload named CREATE_NEW_RECORD Is introduced in SOW. While there could be other action payloads that might not function properly, the base system client actions for the list continue to work effectively in SOW post-migration.