vaSystem.getConversationId() in Script Include not working in scoped appication

[Yousuf Kamal]

I have cloned "FAQ Conversation Builder" OOB topic block on scoped application. It is calling a Script Include global.VAGlobalContextualSearchUtil which has the following line at 262 :

var conversationId = vaSystem.getConversationId();

When testing I found this line is giving error 

com.glide.script.RhinoEcmaError: "vaSystem" is not defined.

When trying to access in the VA designer itself it is giving value but Script include is unable to access this var.

This works fine in Global but not in scoped application. I have just cloned OOB topic block in a scoped app and it causing issue. Any way to resolve this?

[kheller]

Have the exact same issue after cloning the Search KB topic. Please post if you identify the problem 🙂

[Yousuf Kamal · Accepted solution]

As per KB1158000 in Hi Portal

Details

With San Diego, the custom contextual search topic blocks are not returning the desired result.

The end-user might end up getting the error message as:

"I'm having technical issues and won't be able to continue this conversation.
There are no agents available at the moment. Please try again later."

Additional Information

The issue is mainly due to the 'vaSystem' variable that is being used in the VAGlobalContextualSearchUtil.

After the upgrade to San Diego, it has been seen that the custom topic blocks that are using the VAGlobalContextualSearchUtil are in a scoped application, but it should be in the global scope as the variable vaSystem which is used in the can only be accessed in the 'global' scope.

Up until Rome, the custom contextual search in a scoped application would work fine, even if VAGlobalContextualSearchUtil is called in a scoped topic block.

As a result, after upgrade to SD, multiple customers might face this issue.

Resolution:
You need to create a clone of the custom contextual search topic block in the global application scope, and then use it in the global or scoped topics where the contextual search operation needs to be performed.

This change has been introduced with the San Diego release.

Looks like topic block needs to be created in Global scope and called in Scoped Application topic 😑