Possible integrations

Various possible integrations

Wordpress

Dydu offers a Wordpress plugin: dyduPress. This plugin allows the integration and thus the provision of its chatbot dydu on its wordpress site.

Download the plugin files in the /wp-content/plugins/dydupress directory, or install the plugin directly via the WordPress plugins screen.

Once the plugin is installed, enter the URL of your chatbox in the plugin settings and save your changes.

Your chatbox is ready to be used in your WordPress.

ServiceNow

It is possible to integrate your dydu chatbot into your Service Now instance. This integration is done through the creation and use of a Service Now widget. You can follow the video tutorial below to integrate your chatbot on ServiceNow

Sharepoint Online

It is possible to integrate your dydu chatbot on Sharepoint thanks to an extension provided by dydu.

Content Security Policy (CSP) Integration

When integrating the chatbox onto a page that defines a Content Security Policy (CSP), the following modifications are necessary to ensure the solution functions as expected:

Script Integration with a nonce Attribute

The chatbox loading script must be integrated by defining a nonce attribute. This nonce (number used once) can be static or dynamic; the crucial requirement is that the defined value must be strictly identical to the value subsequently reported in the CSP header.

Example of script integration:

<script nonce="dydu" src="[url_cdn]"></script>

Adaptation of CSP Directives

The Content Security Policy (CSP) must be adapted by adding the nonce and the required Dydu (or equivalent) URLs, categorized by directive.

Key elements to integrate:

• script-src: Adding 'strict-dynamic' is mandatory. It authorizes script execution via the nonce attribute and allows the authorized scripts to load their dependencies.

• style-src: Requires 'unsafe-inline' for the chatbox to apply its styles.

• connect-src, img-src, font-src: Must be configured to authorize communication with the solution's server URL (https://[url_server]) as well as the CDN URL (https://cdn.doyoudreamup.com).

Complete CSP Meta Tag Example (to be adapted):

<meta http-equiv="Content-Security-Policy"
      content="default-src 'self';
               script-src 'nonce-dydu' 'strict-dynamic';
               style-src 'unsafe-inline';
               connect-src https://[url_server]/servlet/api https://cdn.doyoudreamup.com;
               img-src data: https://[url_server] https://cdn.doyoudreamup.com;
               font-src https://[url_server] https://cdn.doyoudreamup.com;
               "
/>

The URL https://[url_server] in the example must be replaced by your specific server URL (e.g., https://app1.earth.doyoudreamup.com). The link https://cdn.doyoudreamup.com is common to all integrations and must not be modified.

Accessibility of the chatbox

The dydu chatboxes also respect the RGAA accessibility standards in terms of:

• Content

• navigation within the chatbox.

The RGAA standards have been integrated so that the design of the chatbox is compliant. However, the responsibility for compliance with these standards is ultimately the client's, as this same design can be customised through the dyduBox.

The default chatbox (without customisation) is designed to comply with these standards. In addition, dydu provides its customers with dedicated documentation to assist them in making the design compliant. There are two types of elements in the chatbox:

• elements already present in the HTML code of the chatbox (supported by dydu),

• elements that will be added when customising the chatbot (at the client's expense)

Chatbox & responsive design

The chatbox is responsive: it adapts to the size of the screen used, whether the end user is on a website or an application. The display can be customised according to the user's device (mobile, tablet, desktop) and operating system (iOS, Android).