Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Chatbot script cannot initiate chat request to agent

SA-97942

Summary



On integrating the Pega Chatbot and Mashup script to the same website, the Chatbot script cannot initiate the chat request to  the agent. However, the Mashup code loads correctly.


Error Messages



Not Applicable


Steps to Reproduce

  1. Include Create New Work Mashup code in to the webpage.
  2. Download the web Chatbot files from the Self Service portal and include in the same webpage.
  3. Load the webpage.
  4. Complete the Create New Work functionality.
  5. Initiate a chat request.


Root Cause



This behavior is as per Pega product design.
The Mashup code and the Chatbot script cannot be integrated in to the same webpage.


Resolution



Here’s the explanation for the reported behavior:

The limitation with Pega or Mashup until Platform Pega 8.2 is that only one session is established 'per domain'. .

Perform the following local-change (outside of the Pega application):

At the Infra level, use a different virtual domain with a 'Reverse proxy' server which points to the same Pega application. The Create New Work Mashup and Chatbot Mashup must point to different domains which internally direct the request to the same Pega application.


However, from Pega Platform 8.3, with the new URL Semantics support which the engine provides, multiple Mashups can run on the same domain with different Operator contexts.

Published July 15, 2020 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us