Use NLU on VA input setting

Lynda1
Kilo Sage

I noticed this awhile back but kind of need to figure out where this went. There used to be a toggle on the input components to use the NLU. This was helpful for the Choice and Boolean components.

I would share what it looked like but since it is not there anymore, I cannot.

I do not see this any longer, where did it go?

If it is this, then it seriously fails or does not work on Setup Topics?

Lynda1_0-1743779182579.png

 

3 REPLIES 3

Shivalika
Mega Sage

Hello @Lynda1 

 

On which patch or version you are ? Did you compare with any other instance if this is happening ? If any update set or changes have been made - try reverting that. You can also try including this - 

""vaSystem.switchTopic()"' in your topic. 

 

Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket. 

 

Regards,

 

Shivalika 

 

My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194

 

My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY

We are on Washington DC, I think Patch 10. Working on updating to the latest version.

There used to be a setting that said (Use NLU) so that users were not restricted to the choice values or the Boolean. That went away a few versions ago, I used the Switch Topics toggle and that used the NLU if a user entered a phrase instead of selecting a value.  That apparently stopped working in this manner.

 

Using Switch topic approach is not a viable solution since I do not know what the user will enter as a phrase, hence wanting to use the NLU like it did before.

 

The question is around how to get the NLU searched again when a user enters a phrase instead of selecting an available choice. Since we are on an older version, I might have to wait to see if this was corrected in Yokohama.

Hello @Lynda1 

 

Yes, and it occurred probably because servicenow made updates but in the upgrade it was skipped while reviewing. So maybe in next upgrade accept that setting. 

 

Or open a servicenow case and ask them if you can somehow bring it back or its deprecated altogether. 

 

Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket. 

 

Regards,

 

Shivalika 

 

My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194

 

My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY