Pesquisar

It is possible to deploy the WCFS widget on your Oracle B2C Service site without using Engagement Engine by integrating it directly through the WCFS SDK. 

This article provides step-by-step instructions for implementing WCFS using the SDK, along with sample files to support the integration.

Step 1. Set the OIT_CORS_ALLOWLIST configuration setting properly to ensure your chosen chat UI is approved to interact with your site. For testing purposes, you can set a value of .* to allow all sites to interact with the chat UI.

Step 2. Create a JavaScript file containing the WCFS configuration settings and upload it to your site.

For general information, see the WCFS Readme documentation: https://ee.channels.ocs.oraclecloud.com/wcfs/docs/index.html. 

Attached is a sample settings.js file that includes the most commonly used WCFS features, along with embedded explanations derived from the full WCFS Readme documentation. Please note that you must update the URI on line 36 to point to your own Oracle B2C Service site using interface.widget.custhelp.com

Step 3. Update your .php template to include script tags referencing both the WCFS SDK location and the settings.js file created in Step 2, where all WCFS attributes are configured. 

We recommend using the wcfs-sdk.js file hosted on Oracle’s Akamai CDN, as it includes all required resources, such as translations for 35 languages and additional assets (for example, the audio file used by the enableAudioAlerts feature). See WCFS Usage.

You can find attached a sample of the out-of-the-box standard.php template file, modified for this implementation at lines 95-97.

Please note that you may also need to update your Content Security Policy (CSP) to allow resources from the Oracle CDN.