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

Pre-Chat answers do not display for the first Chat request

SA-77680

Summary



On adding Pre-Chat answers to the Chat header in the Interaction portal in the Employee Information section, the answers do not display for the first Chat request after logging into the application. However, the answers display correctly in the subsequent Chat requests.


Error Messages



Not Applicable


Steps to Reproduce

  1. Launch the Interaction Portal.
  2. Connect to the Chat queue.
  3. Initiate a Chat request by passing the Pre-chat answers in preChatAnswers field.
  4. Accept the incoming Chat request. Verify the Employee Information in the chat header.


Root Cause



This behavior is as per Pega product design.
The ChatInitiatorDetails page is created and loaded in the GetChatInitiationDetails activity which executes on the PS1_TABTHREAD1 thread. However, the CSInteractionHeaderCustomerSummary section is loaded on OpenPortal thread. The Named pages are thread level pages and cannot be used when thread is switched.


Resolution



Perform either of the following local-changes:
  1. Create a Requestor level data page with Interaction ID as a parameter.
  2. Populate data in the data page.
  3. Refer the data page in the section to display Employee Information.
OR
  1. Save the Pre-Chat answers related properties to the D_Interaction data page.
  2. Use the data page to display the Employee Information.

Published August 19, 2019 - 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