Connect Support Chat creating records on new_call table does display the record after saving or submitting. The chat conversation is not recorded within the record to the activity formatter either when navigating to new_call_list.do and finding the record.
The browser console shows the error: "Failed to load resource: the server responded with a status of 500 (Internal Server Error)".
Steps to Reproduce
Ensure that the following plugins are enabled:
- Connect Support
- Service Desk Call
Navigate to Collaborate > Administration > Actions.
Select the Connect Action available, for example, /connect_action.do?sys_id=ad602553d70102002ae9602b6e6103a7.
Modify the script to choose the new_call table instead and rename the title to "Create New Call".
Impersonate a Chat Support agent, for example, David Loo.
On another browser impersonate an end user, for example, Aileen Mottern.
As Aileen Mottern navigate to /$chat_support.do?queueID=c54f0abf0a0a0b452db84664f409c79c.
Open a new chat session.
As David Loo accept the Service Desk Chat.
Click the context menu icon and choose Create New Call.
Fill in mandatory fields and then save the record.
Note that the record is saved but the page returned is blank. Also, the conversation is not stored within the record.
A browser console error states the following: "Failed to load resource: the server responded with a status of 500 (Internal Server Error)".
Contact ServiceNow Customer Support to add the necessary journal and work notes fields. This workaround must be performed by ServiceNow Customer Support because user-created fields have a "u" prefix added.
The new_call table needs comments and work notes journal fields added to the table definition (the same as the ones from the task table), which will fix both the lack of a message in the conversation and the conversation reflection piece, which copies comments and work notes to the new record, but which needs those fields to exist to populate.
Related Problem: PRB714486