...

Update procedure

...

...

...

...

...

• Foreground: this report runs quickly in the foreground. It fails with a timeout if the processing takes more than 5 minutes.

• Background: this report runs slower in a separate process task. It is appropriate if the foreground report fails due to a timeout. In general we recommend to use this report only when you work on large classifiers and dataset files, which can cause the report to run over 5 minutesclassifiers were changed greatly or a lot of articles were added. So if you have huge changes, pick a background report.

Review the changes carefully and click the Approve and save button if you want to keep the changes.

...

• Retrieve the changes made in production. While it is not usual to have configuration changes done directly in production, this might occur for simple things like messages, or corrective actions that are done directly inside the production environmentProduction host might have some changes that appeared during the day-to-day bot usage, such as FAQ articles or AI patterns, created by a knowledge manager while they were busy with conversation training. You might want to get these changes, since FAQ articles can help you test the search performance, for example.

• Retrieve the changes made in a development environment. This is the expected path. Developers work on dev and commit/push their changes after they are done. You could merge the changes to your pre-production environment to validate them before implementing them in production.

• Sometimes it can be useful to transfer a data base (a conversation history, for example) from prod to preprod in order to carry out some improvements. Real customer data can help to test various tools and check real-life results.

Apply

In this tool you can:

...