These are instructions sent from ServiceNow that resolved our issues:
Root cause:
1. The "Agent Assist Global Mobility" variant created by the customer was never shown.
2. This is because the UX Screen Condition to showAgentAssist always returns true for the default variant (Agent Assist default).
- Reason: sn_hr_core_case_global_mobility is the child table of sn_hr_core_case and agent assist is shown for all the child tables of sn_hr_core_case.
But since the customer has enabled the sn_hr_core_case_global_mobility COE, the cxs_table_config record for the COE has to be added (which the customer did) and map the record in the Table config property of the Agent Assist component.
Navigate to: UI Builder -- HR Agent Workspace -- "Record" page -- "Case" variant -- Contextual sidebar -- Agent Assist default:
1. Added the config map to the table "sn_hr_core_case_global_mobility" in the scripted property "Table config" of the Agent Assist default variant.
Added "sn_hr_core_case_global_mobility": "53f1d72097b691505721769e2153afb3" to the "tableNameSysIdMap" const variable.
Notes on the customer implementation:
1. The config properties isNewRecord, fields, sysId, and table are missing bindings in the body of the "Agent Assist Global Mobility" variant.
2. The screen condition used for the "Agent Assist Global Mobility" is expected to show the variant for the "sn_hr_core_case_global_mobility" case record.
The screen condition added to the "Agent Assist Global Mobility" variant is "table=sn_hr_core_case_global_mobility". Only the required parameters to the page can be used in screen condition and the "table" is not a required parameter of the "Agent Assist page".
