Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 10 Next »

Kbot is designed to leverage your Snow environment configuration. It is not aimed at duplicating information that is already defined in Snow. This page describes how you can get the best experience by configuring your environment.

This content is targeted to administrators who are familiar with the ServiceNow concepts. In particular, we will cover OAuth2 authentication, portal links, and sys_class_name.

Snow authentication

Configure the Snow OAuth2 authentication, so the users are authenticated by same principle as in the Snow platform. To make Kbot propose the Snow authentication to users, you must register it:

1. Log in to the admin view of the ServiceNow portal.

2. Navigate to the System Oauth section in the menu on the left side of the window (or use the search field) and click Application Registry to create a provider.

3. Configure the provider:

  • Add the URL of the bot as a callback, typically something like: https://yourcompany.konverso.ai

  • Collect the Client ID and Client secret.

Portal links

The bot must know which portal you are using to propose links to users. Retrieve sys_id of your portal from the Portal view, and set it in the following configuration: 

snow_portal_sys_id = f1226637dbed8b0014c99ee3db9619f1

Kbot uses the knowledge base configured in the portal by default, but you can force the chatbot to use a particular knowledge base. To do so, define the snow_kb_sys_id parameter:

snow_kb_sys_id = 15c9c81cdbe9cf00e386f3731d96195d

Page mapping class

The portal might define a special “page” for displaying particular types of ServiceNow objects. The mapping is defined in the configuration variable snow_sys_class_name_to_pagein the following format: 

snow_sys_class_name_to_page = <sys_class_name>:<page_name>[,<sys_class_name>:<page_name>]*

Use the wildcard * to define the fallback page.

See the sample of page mapping:

snow_sys_class_name_to_page = pc_hardware_cat_item:device, kb_knowledge:kb_article, sc_cat_item_guide:sc_cat_item_guide,
incident:incident, sc_req_item:request_item, change_request:change, dmn_demand:demand, *:sc_cat_item

Live chat

To enable the live chat, define the Queue you plan to use. This can be done with a setup of the following kind: 

snow_chat_queue = d34cc972db798bc014c99ee3db961980

Once it is done, you need to define a few triggers. The Konverso team will send you the code. Please send a request to contact@konverso.ai.

Portal widget

We recommend adding Kbot as a widget inside the Snow portal. To do so:

  1. Create an application inside Kbot for your new view. Call it ServiceNow (for example) and enable only Snow OAuth2 there.

  2. Create a widget inside Kbot and configure the display parameters to fit your needs.

  3. Copy the widget code inside the portal.

Users are prompted for the authentication once; then their authentication token is refreshed automatically.

Users will be prompted once for authentication, then their authentication token will automatically refresh.

  • No labels