- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Use case:
It is understood that both the portal and the bot are closely integrated within ServiceNow. The 'conversation interface' serves as the intermediary layer to facilitate these configurations. Which URL should be utilized to invoke the BOT for your specific business needs?
Solution:
You can invoke the virtual agent pop-up through any UI click event, such as a form link or button. To enable this feature, you need to modify the '$sn-va-web-client-app' condition in your URL. Please refer to the link below for further understanding.
https://xxxx.service-now.com/$sn-va-web-client-app.do
This URL facilitates the opening of the native bot within your script.
I recognize that there is a need to access the custom bots created within the landscape. How can you trigger the custom bot during your UI click event? ServiceNow provides a straightforward approach by adding a parameter to your URL. Please refer to the link below for additional information.
In this case, the sysparm_branding_key is used to call the custom bot in your script. You must identify the brand key from the 'Conversational Interface' settings.
How to identify the 'brand_key':
Conversational Interface > Home > Settings > General > Branding > Locate the brand_key associated with your bot.
How to invoke the default topic in the Bot:
The parameter 'sysparm_default_topic' is utilized to call the topic that should appear by default when triggered by click events. You need to provide the sys_id of the topic, which will be recognized in the 'sys_cs_topic' table. Please refer to the link below for further clarification.
https://xxxx.service-now.com/$sn-va-web-client-app.do?sysparm_branding_key=coral_light&sysparm_defau...3aac3b4c93113e90e3c87d532bba10a5&sysparm_skip_load_history=true
Regards,
Suresh.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
