• Edit
• Access
• Settings
• Logs

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

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.

1. 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:
   
   • Click Settings in the drop down of the required application in the environments.
     

     

   • In the Setting pane, click Add User under Demo Users tab.
     

     

   • 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.
     
2. 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:
   

   

   • Disable Push Notifications - No push notifications will be sent
   • Login User - All push notifications will be sent to the logged-in user
   • Selected User - All push notifications will be sent to a selected user from the list of developers and admins of the app in Development environment.
   • Application Specific - Push notifications will be sent to the device defined in the workflow.
3. Variables : View variables along with their respective values for the selected environment. This tab contains the following information:
   
1. Variable - The name of the variable.
   
2. Defined value - The value that is assigned to variables.
   
3. Current value - The current values of variables which get updated in real-time based on script executions.
   

Note:

1. 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.
2. 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.
3. 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.

4. 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.

1. 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.
   
2. 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

Related Links

• Understand Environments