Managing development environment
The following development environment actions are available to users:
The above options will be displayed when you click on the ellipsis for the required app listed in the Environments page.
Edit
The Edit option will open the edit mode of the application. The required changes to the app can be implemented here.
1. In the Environments page, click on the ellipsis for the required app. In the dropdown choose Edit option.
2. The edit mode of the application will be displayed. Here, the required changes can be made to the application.
Access
This option will open the app live mode in the Development environment, and is used to test how the app functions when someone accesses it. The Development label is displayed on the top bar for users to identify the environment. Demo users can be selected from the drop-down in the top bar to check how each demo user will see or can interact with the app. Data added here is kept isolated from other environments.
1. In the Environments page, click on the ellipsis for the required app. Choose the Access option from the dropdown.
2. The live application will be displayed. The Development label will be displayed in the top-left corner.
3. Under the View As field in the top bar, choose the demo user.
Settings
This section is to add demo users with various permissions to test the app, and to configure notifications.
Demo Users
You can add demo users with various permissions and roles to test the app. Demo users are pre-defined, which means you have to select from the list of provided options. You can assign different permissions and roles to check how each demo user will see or can interact with the app in the current environment.
Note: Permissions here refer to existing app permissions, and not separate permissions exclusive to testing. App permissions will reflect in Stage environment only after the app is published to Stage environment.To add demo users:
1. Click Settings in the drop down of the required application in the environments.
2. In the Setting pane, click Add User under Demo Users tab.
3. In Add Demo User pop-up, select the demo user in Name drop-down. The demo users are pre-defined, and a maximum of 5 are provided. Also select the demo user Type as User or Portal User depending on how you want to test your application.
Note: If the Type is selected as User, we can assign the permissions and roles configured in the app. If the Type is selected as Portal Users, we can assign the portal permissions configured in the app.
- Only the permissions and roles added in the current app will be listed. The demo user will be able to perform actions in the app depending on the assigned permissions. Click Add.
- Once the demo user has been added, you can access the application and select the added demo user from the dropdown to test the application according to the assigned permissions and roles.
Notifications
Because the Development environment is used for testing purposes, we usually don't need notifications to be triggered when the app is being tested. This section lets you decide if the notifications are to be disabled or to route them to any particular address.
Note: Notifications here refer to notifications of send mail task and SMS tasks in workflows and form submissions.
The following options are available for email notifications:
- Disable Emails - No emails will be sent
- Login User - All emails will be sent to logged-in user
- Selected User - Emails will be sent to a selected user from the list of developers and admins of the app in Development environment.
- Application specific - Email notifications will be sent to the specified email address in the workflow.
The following options are available for SMS notifications:
- Disable - No SMS notifications will be sent
- Application specific - SMS notifications will be sent to the specified phone number in the workflow.
The following options are available for push notifications:
The following options are available for sending push notifications in the development environment, regardless of the recipients preconfigured in the Send notification action and the Push notifications Deluge task:
- Disable Push Notifications - Push notifications will not be sent to any user irrespective of the preconfigured recipient.
- Login User - Push notifications will only be sent to the logged-in user who has triggered the notification, irrespective of the preconfigured recipient.
- Selected User - Push notifications will only be sent to the selected developer or admin from the dropdown irrespective of the preconfigured recipient.
- Application Specific - Push notifications will be sent to the recipients preconfigured in the Send notification action and the Push notifications Deluge task
Note: By default, the notification settings for this environment will be set to Application Specific which can be changed according to your requirement.
Variables
View variables along with their respective values for the selected environment. This tab contains the following information:
- Variable - The name of the variable.
- Defined value - The value that is assigned to variables.
- Current value - The current values of variables which get updated in real-time based on script executions.
Note:
- Script executions are environment-specific, so the current values may differ across environments based on script executions in different environments. Learn more about variable publish flow.
- You can only view the defined value and current value of variables specific to the selected environment. To create or manage variables, you must access the application settings in the development environment.
- Current values of variables will not be carried forward when publishing the application to the stage environment. Instead, they will be replaced with the published defined values.
Workflow Schedules
Whenever an application is edited, it is, by default, done in the Development environment for preliminary testing purposes.In the development environment, you might have configured schedule workflows in your application to be tested before publishing it to the stage environment. When you've completed validating the configured workflows, you may no longer need the schedule workflows to execute continuously. You can suspe nd the execution of all such configured schedules in the development environment by choosing one of the two below options. This allows you to suspend the execution of schedules whenever required without disturbing the schedule configuration defined in the development environment.
Note:
- This is an application-specific environment setting i.e., choosing one of the below options will affect only the configured schedules for the development environment in that application.
- The ability to suspend schedules specific to an environment is a valuable addition as it aids in efficiently managing schedule limits within that environment.
- Suspend All Schedules - All the schedule workflows configured for that application will be suspended in the development environment i.e., enabling this option will suspend the execution of all schedule workflows irrespective of their individual status (enabled/disabled) in that application.
- Application-Specific - Enabling this option will allow the schedule workflows to be executed as per their defined status in that application i.e., only those schedules that have an enabled status on the workflows will be executed.
Note: You can switch between the above mentioned options as required.
To manage the execution of schedule workflows in your development environment settings,
1. Select Workflow Schedules tab in the Environment Settings pane that appears.
2. Choose the required option -Suspend All Schedules or Application Specific and click Done.
Note: The selected option will be effective only in the Development environment.Logs
Logs are automatically-produced, time-stamped documentation of the history of actions related to Form Actions, Schedules, Integration, Pages, and Payments executed in an application in the Development environment. They are recorded for statistical, security, and debugging purposes. Admins and users having at least one environment permission can refer to logs to check an application's performance, and keep track of actions executed in an application or in the event of action failure.
- Success logs display the message, action details, user who configured the action; the time of execution; and the type of action.
- Failure logs will also display additional error details.
You can filter the logs based on Time/Period and Type. Time/Period options are Last one Hour/Day/Week/Month.
Related topics
Access your files securely from anywhere
Zoho CRM Training Programs
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
Zoho DataPrep Personalized Demo
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.
- Zoho Workerly Home
- Forums
- Connect With Us:
- Zoho Recruit Home
- Forums
- Connect With Us:
New to Zoho Writer?
Create. Review. Publish.
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho Marketing Plus?
Everything you need to run your marketing
New to Zoho Marketing Plus?
Everything you need to run your marketing
You are currently viewing the help pages of Qntrl’s earlier version. Click here to view our latest version—Qntrl 3.0's help articles.
New to Zoho Survey?
Zoho Sheet Resources
Zoho Forms Resources
New to Zoho Sign?
Zoho Sign Resources
Sign, Paperless!
New to Zoho TeamInbox?
Zoho TeamInbox Resources
New to Zoho ZeptoMail?
Design. Discuss. Deliver.
New to Zoho Workerly?
New to Zoho Recruit?
New to Zoho CRM?
New to Zoho Projects?
New to Zoho Sprints?
New to Zoho Assist?
New to Bigin?
Related Articles
Managing stage environment
The following stage environment actions are available to users: Access Settings Logs The above options will be displayed when you click on the ellipsis for the required app listed in the Environments page. Access Opens the app live mode in Stage ...Test application changes using a test environment
Requirement Workflows in an app have to be tested to ensure it is working as expected, before releasing the updates to users. Use Case An order management app contains two forms, one to store products details, and the other to store order details. A ...Managing environments
1. What does this page cover? This page provides a comprehensive guide on managing your application across Development and Stage environments using the environments dashboard. You'll learn how to navigate the environments dashboard, manage your ...Managing connections
1. What does this page cover? Learn about managing the created connections and the types supported in Developer Console for connecting your application with other services. 2. Availability Connections can be created and managed only by the super ...Publishing to the Stage environment
This help page is for users in Developer Console version 6. If you are in the older version (Developer Console 5), click here. Know your Developer Console version. 1. What does this page cover? Learn about publishing your applications from the ...
New to Zoho LandingPage?
Zoho LandingPage Resources