Managing Dialogs¶
Your bot can have many dialog tasks with related components. You can use the Dialog Editor to create, review, and edit a single dialog task for a bot. However, to better visualize and understand relationships and settings for all dialog tasks in a bot, you must use the Manage Components feature.
Manage Task Components¶
To manage your dialog tasks, follow the below steps:
- Open the bot for which you want to manage the dialog task components.
- Select the Automation from the left menu
- On the Automation menu, click USE CASES > Dialogs.
-
Click Manage Components on the top-right.
Dialog Components¶
The Dialog Components window shows all the components used in any dialog task of the bot. To view or modify the settings of a component, click its name. The Properties panel of the node opens.
The following table lists the details included in the window for each component type
COMPONENT TYPE | DETAILS |
User Intent |
|
Entity |
|
Service |
|
Script |
|
Message |
|
Confirmation |
|
GenAI Node |
|
GenAI Prompt |
|
Webhook |
|
Agent Transfer |
|
Form |
|
Logic |
|
Bot Action |
|
Process |
|
Upgrade Tasks¶
After you publish a task, the Bots Admin approves and deploys the task to make changes in the published bot. You must upgrade the bot; then publish the upgrade for Bots Admin approval and deploy it to users.
Upgrade Tasks¶
If you need changes to the published task, you must upgrade the task to a new version.
Upgrade Types¶
There are two types of upgrades for a task:
- Mandatory – A mandatory upgrade generally does not require end-user action, and users are only informed that the task was upgraded with an auto-upgrade. If a mandatory upgrade does require end-user action, for example, new authentication requirements, the end-user is notified to take the action for a manual upgrade, sent reminder notifications, and finally, expiration of the original task after 15 days.
- Optional – An optional upgrade is not required and is not auto-upgraded for users. End-user action is required to complete the manual upgrade and the user can choose whether or not to upgrade.
Task Upgrade Definitions¶
A Version Type is either a major or minor update. Depending on the changes of the bot task, you can specify the version type as a minor or major update for the revision number. All published tasks begin with the Version set to 1.0. A major update is set with the Version to 2.0, while a minor update is set with the Version to 1.1.
As part of the end-user upgrade experience, you must define the messages shown to the user to describe the upgrade and other messages that describe what the upgrade will change.
Verify Flows¶
If the upgraded task is mapped in a flow, you must review, update, and confirm existing mapping values defined in the flow. If the flows are not verified, mapped action tasks will not be displayed in the upgraded task for the end-user.
Note
You cannot publish another upgrade to a mandatory published task that requires manual end-user input during the initial 15-day deployment.
Upgrade a Task¶
Using the Upgrade command, a duplicate of the original task is created where you can make your modifications without affecting the published version. Then, when ready to deploy, you can decide if the upgraded task is mandatory or optional for users that are already using the originally published task.
To upgrade a task, follow the below steps:
- Open the app to edit the task
- Select the Automation from the left menu
- On the Automation menu, click USE CASES > Dialogs..
- Click the More icon of the published task you want to upgrade, and then click Upgrade.
- A duplicate of the published task is created with the Status set to Upgrade In Progress and the General tab is displayed.
- Modify the task and click Finish Setup.
After the modifications to the upgraded task, the task status is set to Configured and the version is set to Draft.
Next Steps
You might want to look into how to work with the Prompt Editor, refer here for more.