In Kata Platform 3.0, channel can be added under Environment menu which placed in Deploy. Each Environment featured various channel integration that customisable. Every environment has different channel list, it useful to ease Environment Management for clean and neat appearance.
Yes, the implementation is similar with previous version. You may define them in kataML
You can invite anyone to access your CMS Client under User menu on CMS Studio. Bear in mind for now, you can only invite user that is already registered on Kata Platform. This will change soon, stay tune for update.
Yup, on Version Page, you can Rollback to previous Versions. Please note this action will create a new Version, using old Version setup. For example, you’re on Version 1.0.1 now, and would like to Rollback to Version 1.0.0. When you hit that Rollback button, it will create a new Version, 1.0.2 with same setup as Version 1.0.0.
We have migrated all of your Bots and NLs to different projects. For example, if you have 5 Bots and 3 NLs, now you should have 8 different projects
It still goes by the name of Versions. But the new Versions may require you to specify Bot, NL and CMS Revisions
For those of you who have created *a lot of deployments and channels, *we will migrate this to Environments. So you should have multiple Environments, based on your Deployments. For example, previously you had 2 Deployments, on the new version you should have 5 Environments which consist of: the old 2 and the new 3 default Environments (Development, Staging, and Production)
Yes, you still can use this as usual
Yes, you should be able to build your own NL and CMS under a migrated Project. Should something goes wrong, feel free to reach out to us at firstname.lastname@example.org
Please contact us at email@example.com