Migrate the client action from ITSM Agent Workspace to Service Operations Workspace for field decorators actions
Configure the client actions to migrate field decorators actions from ITSM Agent Workspace to Service Operations Workspace.
Before you begin
Role required: admin
Procedure
- Navigate to All > Now Experience Framework > Declarative Actions > Field Decorators.
- Filter the records based for Implemented As is set as Client action.
- 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.
- Select the failed record with the corresponding sys_id.
- Right-click on the header, and select Insert and Stay.
- Clear the Workspace and View fields.
- Select the Experience Restricted check box.
- Update the value in the Implemented as field as UXF Client Action.
- In the Action configuration related list, select Edit, and then select SOW Actions from Collection to Action configurations list.
- Select Save to save the Action configurations related list.
- Select Update.
-
If specify client action key is ITEM_SELECTED or PREVIEW_RECORD, create CREATE_NEW_RECORD key with the payload mentioned below in the code block in the
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}}" } } -
Modify the client action created for ITEM_SELECTED and PREVIEW_RECORD declarative actions records.
When you modify the client action, then the payload Map in action Attributes should be transformed based on the payload.
The following tables are used in the migration process:- sys_ux_m2m_action_assignment_action_config
- sys_declarative_action_payload_definition
Note:The ITEM_SELECTED and PREVIEW_RECORD actions function in the ITSM Agent Workspace but not in SOW. Therefore, a new 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 List continue to work effectively in SOW post-migration.