Genesys Cloud - Main

 View Only

Sign Up

  Thread closed by the administrator, not accepting new replies.

  • 1.  Web chat deployment vs legacy

    Posted 07-18-2018 21:03
    No replies, thread closed.
    Hey Everyone, 

    I was looking to get some clarification or help with a question. As per the release notes, web chat has a more modern look that we can activate. This is something I have been wanting for a while now and great to see. 

    Firstly, do we have any examples of how the new one looks?

    Secondly, and most importantly, out current chat deployment is done with the PureCloud JavaScript API and the chat configuration container added. Within the container, this has all of our <g class="gr_ gr_503 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar multiReplace" id="503" data-gr-id="503">config</g>, including skills, queue routing etc. 

    As I would like to take advantage of the new more modern look, we need to do this through a web chat deployment in PureCloud. How do we keep all the configuration when moving to this new deployment method as the only thing it appears for me to add is;

    <script
    id="purecloud-webchat-js"
    type="text/javascript"
    src="https://apps.mypurecloud.com.au/webchat/jsapi-v1.js"
    region="ap-southeast-2"
    org-guid="xxxxxxxxxxxxxx"
    deployment-key="xxxxxxxxxxxxx"
    ></script>

    Hoping someone can help me with this before I request the change in my <g class="gr_ gr_883 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" id="883" data-gr-id="883">org</g> 

    Thanks, 



    ------------------------------
    Lawrence Drayton • Head of Fan Success
    OVO | Prepaid Mobile | #ForTheFans


    ------------------------------


  • 2.  RE: Web chat deployment vs legacy

    Posted 07-19-2018 03:43
    No replies, thread closed.
    You would use the web chat deployments configuration alongside the existing configuration on your website. In other words, you wouldn't remove anything you have, you would only add the new web chat configuration.

    Here is a screenshot of before and after for the updated look and feel. There are a few minor details that are different in the production version over the screenshot. We are adding more details to the resource center to show the new look.



    ------------------------------
    Lucie DeCristofaro
    Genesys - Employees
    ------------------------------

    Original Message


  • 3.  RE: Web chat deployment vs legacy

    Posted 07-19-2018 17:56
    Edited by Mark Francis 07-19-2018 17:56
    No replies, thread closed.
    Spent all morning trying to get this going.

    Scenario 1: 
    - Have 'webchat deployment' activated in org 
    - Have created webchat deployment in org (name "Test CSS Webchat") - with NO authorization required 
    - Generate test webchat via developer tool: https://developer.mypurecloud.com.au/developer-tools/#/webchat 
    - Receive error 'Chat is unavilable due to an authorization error"

    Scenario 2 
    - Have 'webchat deployment' activated in org 
    - Have created webchat deployment in org (name "Test CSS Webchat") - with NO authorization required 
    - Implement test webchat script with code as per this site: https://developer.mypurecloud.com.au/api/webchat/ (including the webchat deployment code generated by PureCloud)
    - Receive error: "blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource." 

    Support now saying this feature is only available to authenticated chat users, in spite of there being a toggle for either option in the UI, and no mention of this in the documentation (that we have found yet).

    Hope this helps someone else before the doc is updated!

    ------------------------------
    Mark
    ------------------------------

    Original Message


  • 4.  RE: Web chat deployment vs legacy

    Posted 07-31-2018 08:19
    No replies, thread closed.
    Mark and I ended up solving this offline (via Johnathan) but to update this post - web chat deployments are available with or without authentication. Authentication is simply an option for a web chat deployment.

    The first issue is caused by not being able to provide web chat deployment ID via the dev center when testing web chat. We need to update that. Once you turn on the toggle in your org that web chat is only available when you use web chat deployments, the dev center test will no longer work.

    The second issue was caused by not using https and instead using http.

    ------------------------------
    Lucie DeCristofaro
    Genesys - Employees
    ------------------------------

    Original Message


Related Content