3. Environments dashboard

The environments dashboard is a centralized space where you can manage your applications across the Development and Stage environments. The dashboard groups the applications according to the environments they're present in, and also includes additional information about any changes available for publishing to the Stage environment. Various environment-specific actions can be performed, like editing or accessing the app, configuring settings, and viewing logs. It also lists the version history of apps and allows users to publish apps to the Stage environment.

• Edit 
  
• Access
• Settings
• Logs

3.1 Editing an application

3.2 Accessing an application

In the live mode of the environment, a label is displayed on the top bar for users to identify the environment, for example, as Development or Stage. 

Note: Data added in one environment is kept isolated from the other environment.

Under the View as field in the top bar, you have the option to test the application as a demo user. You can learn about demo users in the upcoming section.

3.3 Settings

Note: All settings options will only be applied to the selected environment. For example, if you click Settings under Development, all configurations will only be applied to the Development environment, and vice-versa for the Stage environment.

This section allows you to configure:

• Demo users - Select predefined test users and assign them with various permissions and roles for testing the app. This refers to mock user profiles, and not actual users.
• Notifications - Disable or route notifications, since testing the app may not require notifications to be sent to actual users or other developers of the application.
• Workflow schedules - Disable any schedules that don't need to be executed during the testing phase. By default, the application's schedule settings are considered.
  
  

Note: Permissions here refer to existing app permissions and not separate permissions exclusive to testing. Only the roles and permissions already added to the current app will be listed.

 To add demo users:

1. Click Settings for the required application and environment.
   
2. On the next page, click Add Demo User under the Demo Users tab.
   
3. In the Add Demo User pop-up, select the demo user in the Name dropdown. 
   
   
   
   
   
   Note: Demo users are predefined mock users, and a maximum of five are provided.
   
   
4. 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. 
5. Select a Permission and a Role for the user.
   
   
   

Note: Permissions and roles are app specific. This means 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 these assigned permissions.
6. Click Add.
   
   

Note: Notifications here refer to notifications sent using the send mail task and push notification action.

The following options are available for email notifications:

• Disable emails - Emails will not be triggered.
• Login User - All emails will be sent to the current logged-in user.
• Selected User - Emails will be sent to a selected user from the list of developers and super admins.
• Application Specific - Email notifications will be sent according to the configured workflow. This option is selected by default.
  
  

The following options are available for push notifications:

1. Disable Push Notifications - Push notifications will not be triggered.
   
2. Login User - All push notifications will be sent to the current logged-in user.
   
3. Selected User - Push notifications will be sent to a selected user (super admin or developer) from the list of developers and super admins.
   
4. Application Specific - Push notifications will be sent according to the configured workflow. This option is selected by default.
   

Note: The ability to suspend schedules specific to an environment is a valuable addition, as it aids in efficiently managing schedule limits within that environment.

3.4 Logs

Note: All the logs displayed will be specific to the selected environment. For example, if you click Logs under Development, all logs specific to the Development environment will be visible, and vice-versa for the Stage environment.

Logs are automatically generated and time-stamped records of actions related to forms, schedules, email data, pages, payments, and batch workflows in an application within the respective environment. These logs are crucial for tracking application performance, debugging, and ensuring security.

3.5 Version history

The version history lists all the published versions and app changes in each of those versions. This serves as a reference to view all past versions and their changes.

Click on the required version to get an in-depth look—you'll then be shown the list of components present in the application.

The below screenshot gives you an illustration of a component with an Added marker:

3.6 Publish to Stage

Once you've created an application or made changes to it, you can publish it to the Stage environment to perform thorough testing.

4. Related topics

• Understand Developer Console
• Understand Environments
  
• Understand Marketplace