New Topic "Dynamic Translation Support Topic" visible under Virtual Agent list of topics

[sreeshsurendran]

Hi all,

There's a new topic "Dynamic Translation Support Topic" being visible under the list of topics in VA. Is there any way we can deactivate this. Also, found that in sys_cs_topic, this is an OOTB topic and can't deactivated. Need your help on this please.

Thanks,

Sreesh Surendran

[Satishkumar B]

@sreeshsurendran Please refer below document to disable/enable:

https://docs.servicenow.com/bundle/vancouver-servicenow-platform/page/administer/virtual-agent/task/...

please mark my response as helpful 👍and accept the solution ✅if it helped you

[Rajesh Chopade1]

Hi @sreeshsurendran 

You can hide or Deactivate the OOTB Topic using following ways:

1) Modify the availability conditions

You can set conditions that are never met for this topic to make it effectively inactive.

// Go to sys_cs_topic table and locate the 'Dynamic Translation Support Topic'
var gr = new GlideRecord('sys_cs_topic');
if (gr.get('<sys_id_of_the_topic>')) {
    gr.availability = 'never'; // This is a pseudo-code, adjust based on the actual conditions
    gr.update();
}

2) Update the Active Field via Script:

While the UI might not allow you to deactivate it, you can use a script to set the active field to false.

var gr = new GlideRecord('sys_cs_topic');
if (gr.get('<sys_id_of_the_topic>')) {
    gr.active = false; // This assumes there's an active field
    gr.update();
}

3) Utilize a Business Rule to Prevent Execution:

Create a business rule that prevents this topic from being shown or executed

(function executeRule(current, previous /*null when async*/) {
    if (current.name == 'Dynamic Translation Support Topic') {
        current.setAbortAction(true);
    }
})(current, previous);

I hope my answer helps you to resolve your issue, if yes mark my answer correct and helpful.

THANK YOU

rajesh chopade

[David Bembridge]

They are good suggestions but wont work as the topic has read protection on it, so I assume can only be updated by ServiceNow with maint role.  We had this same issue following upgrade to washington, I raised a case to support and they arranged a change to disable it for now.

[sreeshsurendran]

Thanks for this @David Bembridge . Let me raise a case with Support right away 🙂

Regards,

Sreesh Surendran