Widget installation

Widget code

On the web page where you want the chat to be displayed, add the following code before the closing tag </body> to enable the chat widget:

<!-- BEGIN CHAT {literal} -->
<script type="text/javascript">
  !function(e,a){"use strict";window.ThreadsWidget={},e=e||"/settings.json";function n(e,t){const n=setInterval(function(){ThreadsWidget&&!ThreadsWidget.isDummy&&(clearInterval(n),ThreadsWidget[e]&&ThreadsWidget[e].apply(void 0,t))},100)}ThreadsWidget.isDummy=!0,["hideInvite","version","commitHash","showChat","hideChat","onHideChat","onScenarios","onLoad","on","reInit","init","unInit"].forEach(t=>{ThreadsWidget[t]=(...e)=>{n(t,e)}});const t=function(){const i=new XMLHttpRequest;return function(e,t,n,a){i.onreadystatechange=function(){if(4===i.readyState)if(200===this.status)n(i.response);else{if("function"!=typeof a)throw new Error(i.response);a(i)}},i.open(e,t),i.send()}}();function i(t){t.webchat&&(t.webchat.filename=t.filename),a&&"string"==typeof a&&(t.webchat.currentLocale=a),a&&"object"==typeof a&&(a.locale&&"string"==typeof a.locale&&(t.webchat.currentLocale=a.locale),a.unavailable&&"boolean"==typeof a.unavailable&&(t.webchat.isUnavailableOnStart=a.unavailable));try{sessionStorage.setItem("__threadsWidget",JSON.stringify(t.webchat))}catch(e){window.__threadsWidget=JSON.stringify(t.webchat)}if(t.filename){const e=document.createElement("script"),n=(e.type="text/javascript",e.async=!0,e.src=t.filename,document.getElementsByTagName("script")[0]);n?n.parentNode.insertBefore(e,n):document.body.appendChild(e)}else console.error("Invalid bundle")}function o(){t("GET",e+"?rnd="+Math.random(),function(e){const t=JSON.parse(e);i(t)})}"complete"===document.readyState?o():window.addEventListener("DOMContentLoaded",o,!1)}("settings.json",{});
</script>
<!-- {/literal} END CHAT -->

Settings file

Place the settings.json file on your website so that this file is available on http(s)://your.site.ru/your/path/to/settings.json. We recommend that you place the file to the same directory where the **_.js chat files are located.

IMPORTANT! The path to the settings file settings.json is set at the end of the initialization script:

... ("settings.json")

As the value for this parameter, use the absolute path from the root of your website. Example:

('/your/path/to/settings.json');

If necessary, you can set additional parameters during the initial initialization.

'/your/path/to/settings.json',
  {
    locale: 'en',
    unavailable: true,
  };

where:

• locale - Locale language
• unavailable - Widget unavailability (true if unavailable). If unavailable is set to true, the chat will be hidden after the chat page loads, unless the client has an active thread.

Widget configuration

The chat settings are stored in the provided settings.json file. The file contains file storage connection data, appearance theme settings, connection settings, and API keys you need to use for edna API.

Connection to external edna API and datastore

The settings are unique for each new connection. In the examples of edna SDK they are set to "FIX_ME" and you must edit them before the launch. You must do it for the following parameters:

• webchat/package = <application_package>
• webchat/uid = <application_uid>
• webchat/websocket = <push server websocket URL>
• webchat/datastore = <datastore URL>
• webchat/backend/history = <datastore history URL>
• webchat/backend/rootUrl = <datastore API URL>

You will get the values of these parameters from the deployment manager.

Note: In case of on-premise deployment of edna Datastore, the parameters webchat/datastore, webchat/backend/history and webchat/backend/rootUrl depend on the address of the installed edna Datastore.

Authorized and unauthorized zones

The chat widget can be in one of the two modes:

1. Guest mode. The time of the user session existence are defined by the parameters in settings.json. webchat/backend/unauthorizedHistory. For example:

   {
     "cookie": {"Max-Age": 15552000}
   }

   where:

   • Max-Age - Time in second of history storing for the site users

   The session identifier is stored in cookie, the storing parameters are configured in the webchat/backend/unauthorizedHistory/cookie object, where the key corresponds to the specifications of the cookie directives.

2. Authorized mode. The mode can be activated for an authorized website user by passing the unique user identifier to the chat to create a link "edna client" - "website user". The session of such a user is not linked to the current browser tab, the user will see the chat history on any tab where the chat is open. Set the parameter clientId in the settings.json file in the global JavaScript object window to pass the unique identifier of the authorized user to the chat. Do this before the chat initialization. The string in the settings.json (in its simplest form) can look as follows:

   "clientId": "clientId",

   This way, if you decide to place the unique user identifier in the property of the window object, which you decide to name clientId (as in the example above), insert the following string before the initialization code:

   window.clientId = 'user identifier';

   You can pass additional client data the same way (in the JSON format). This client data will be displayed in the client information in the agent WP. To do this, in the clientData parameter of settings.json, set the name of the property, in which you will pass the client's details. Usually, the name is left the same - clientData - as in the example below:

   "clientData": "clientData",

   Then, in the global JavaScript object window, set the value of this property. To do this, insert the following string before the initialization code:

   window.clientData = `<client data>`;

   where <client data> is a JSON object converted into a string. As you see in the example, the data is passed in window.clientData, as clientData was set as the name of the property. Following is an example of passing the client details that consist of name, phone, email, personal_manager, and customField:

   window.clientData =
     '{"name":"Name Surname","phone":"+7-999-999-99-99","email":"e@mail.com","personal_manager":"login","customField":"customValue"}';

NOTE: The examples in the SDK contain all necessary settings.

Extended authorization (optional)

Optionally, you can pass additional parameters in requests to the server. For these settings, use the extendedAuth section of the parameters in settings.json.

The dataKey parameter is a string that contains the name of the property in the global JavaScript object window that stores the object with extended data for authorization. The parameter is optional, its default value is extendedAuth.

window.extendedAuth = <JSON data>;

For example:

{
  "custom-property": "value for custom header",
  "token": "some token value",
  "type": "token type"
}

The http.enabled parameter enables or disables the extended authorization mode for HTTP(S)-requests (boolean). The http.headersMap parameter is an object whose keys are the names of the headers passed in HTTP(S)-requests, and their values are the names of the properties from the extended data object. This way, you can configure any number of optional headers.

For example:

"extendedAuth": {
    "dataKey": "extendedAuth",
    "http": {
        "enabled": true,
        "headersMap": {
            "Header-Name": "custom-property",
            "X-Auth-Token": "token",
            "X-Token-Type": "type"
        }
    }
}

Example of a request with extended authorization headers:

GET /some/backend/url
Host: example.com
Content-Type: application/json
Header-Name: value for custom header
X-Auth-Token: some token value
X-Token-Type: token type
...

Chat launch

Once you save the settings, open the webpage with the tab with the chat in your browser. You will see the chat button in the right bottom corner. Once you click it, the start chat window opens (img. 1).

Img. 1. Start chat window