Configuring Agent Assist visible on interaction record >> gives error "Invalid configuration"

Stefan K_
Tera Expert

Use case: I want to activate Agent Assist in Agent Workspace to be visible on interaction record to be able to do knowledge search from interaction directly. Using knowledge from interaction is needed for agent to check if the interaction should be escalated to incident/request or perhaps it can be dealt directly.

What has been configured:
1. Declarative Action Assignment [sys_declarative_action_assignment]
Created a similar record that already existed for incident:

 

2. Table configuration [cxs_table_config]
Created a similar record that already existed for incident:

 

And the table configuration is active:

Problem:
Agent Assist is visible, but gives error "Invalid configuration, table configuration is inactive". 

Why?

 

 

ANSWER:

Okay figured it out, on the "Declarative Action Assignment" there are attributes (below screenshot from OOB record pointing to incident). There is some client script logic how this gets set and it didn't get set when creating new record. 

I copied these values manually to my new record and now Agent Assist works from interaction.

Sadly this is not well documented by ServiceNow. 

 

11 REPLIES 11

John Green2
Tera Expert

Really appreciate your sharing this Stefan - it has saved hours of work. Thanks! 

KB15
Giga Guru

FYI, the sys_id that the Action Attributes points to is the Table Configuration you want this to apply to. Not sure why this isn't a related table field to make thins easier.

Using this specific sys_id points to the default table configuration. If you're not sure why your changes are not appearing (Like the "Results header text"), point it to your custom Table Configuration.

I also want to add that I've seen an error with new instances (at least with my personal one) where the Action Attributes shows the incorrect name as "cxstableconfig"

It should not be in lowercase. It should read as "cxsTableConfig" as below. I was running around to see why I was still getting the error until I manually corrected this read only field value. I've already created a case to make sure this isn't a systemic bug.

find_real_file.png

Community Alums
Not applicable

After hours jumping between multiple docs for contextual search / workspace / agent assist in multiple releases to review my configuration and hoping to get an answer on why Agent Assist wasn't working, I finally started spreading out the search and got my life saved by this. Thanks KB, I would hit that Helpful button 10 times if I could!

Any updates on the case you logged by any chance?