Changing the scope of a topic in Virtual Agent Designer

[Nasreen2]

Hi All,

There is a requirement to change the scope of already created topic/topic block from Global to new scope. Lets say that I need to change the scope of a topic 'Report an Issue' and if I do that by creating a duplicate topic in the new scope and then remove/rename the old one which is in Global scope. And all the other topics where this 'Report an Issue' is called are still in the Global scope.

Now, if I do this scope change, will it affect the functionality of Report an Issue topic or wherever it was called ?

[Dr Atul G- LNG]

Hi @Nasreen2 

I think no, it not impact.

[Mark Roethof]

Hi there,

It can indeed affect functionality, though can also go well. Without knowing your topic in depth, we can't tell.

For example it could already be an issue because by duplicating the topic, you actually created a new one. If anywhere in your instance that old topic is referenced, by sys_id or name, its an issue. Another issue which can occur, when you've used scripting in your topic. Scripting which is global for example and suddenly your topic in in a scope. Etcetera.

So hard to tell based on your input. It can affect functionality. Though can also be that it does not affect functionality.

[Nasreen2]

Hi Mark,

Thanks for your reply!!!

I have tried it in a lower instance and after duplicating the topic in new scope, I have renamed the topic name like the old name which was in Global scope and I have changed the old topic name to something else. And when I tested in VA chat it was not working fine and it affected functionality. So as far as I am aware in some other topics this Report an issue topic was referenced using its name by switchTopic() method. I am not sure if it is referenced using sys_id anywhere else.....

Also, could you let me know in terms of scripting which was used inside topics in Global scope, what could go wrong if it is moved to scoped application?

To give you an idea, in this report an issue topic most probably GlideRecords were used in script utility nodes and also some ML solutions(classification/similarity) were being called through Action utility component from 'Predictive Intelligence for Flow Designer' spoke as shown below.....

Thanks Again,

Nasreen