Let's say you have an application with multiple forms and reports and you want to add a new module containing a few additional forms and reports. Additionally, you want to add a new workflow to send email notifications to users on form submission. To prevent users from accessing the new module until all the changes have been implemented, you can first make the changes in the development environment and publish them to the Stage environment. Here, the new changes can be tested to see if they're working, and if the notifications are being triggered as expected. Once verified, the changes can be published to the production environment at once for your users.
Zoho Creator offers three environments:
Whenever an application is edited, it is, by default, done in the Development environment. However, the application can be accessed (live mode) in all three environments—development, stage, and production. To put it simply, there is one edit mode (development) and three live modes (development, stage, and production). Live mode also means that data can be added to the application. Data in each of those three live modes are stored separately.
Out of the three live modes, production is where the end users or consumers access the app. This means testing needs to happen in the development and staging environments, before the changes are published to production. Changes are first published to the stage environment, where the testing happens, and then to the production environment.
So, applications are created in the development environment, tested in the stage environment, and made accessible to end users in production mode.
The flow:
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
Write to us: support@zohoforms.com