-
Type:
Bug
-
Resolution: Fixed
-
Priority:
High
-
Component/s: Virtual Agent - Channels
-
7
-
Severity 3 - Minor
-
6
Issue Summary
When using the Virtual Agent Intent step, 'Change request type and fields' the Additional fields will not be set even if the JSON is correct if the field is added after the Virtual Agent Intent is created.
Steps to Reproduce
- Create a Virtual Agent Intent with the step Change Request Type and Fields and set the status to live.
- Create a new custom field and associate it with the request type.
- In the Additional Fields section, input the JSON of the field you wish to have changed when the ticket is escalated.
- Navigate through the intent flow and escalate the ticket.
- The Additional Field information will not be populated.
Expected Results
The field specified in the JSON will be set when the ticket is created.
Actual Results
The fields will not be set when the ticket is created.
Workaround
Removing and re-adding the request type will allow the fields to be set correctly.
- Navigate to Project Settings -> Chat.
- Click on the Request Type tab.
- Disconnect the Request type that is created in your virtual agent intent by selecting the disconnect button in the upper right.
- Click Add Request type and re-add the request type that is created in your virtual agent.
- is duplicated by
-
JSDCLOUD-15977 Updating fields via "Change request Type and Fields" on intents not working
-
- Closed
-
- mentioned in
-
Page Loading...