1. Managing applications in the environment

1. Edit: Allows editing and making changes to the application. This option is only available for the development environment, as the application can only be modified in that environment.
   
2. Access: Access the application in the preferred environment.
   
3. Settings: Configure features like demo users, notifications, variables, and schedules. In the production environment, only variables can be configured.
   
4. Logs: Tracks form actions, schedules, emails, and integrations with timestamps in the respective environment.
   

1.1. Edit

Note: This option is only available in the Development environment, as applications can only be modified within this environment.

1. Navigate to the Environments section, click the ellipsis icon near the preferred application, and select Edit.
   
2. You will be directed to the edit mode of the application. The required changes can be made to the application here.
   

Alternatively, you can edit the preferred application from the Solutions page by clicking the Environment dropdown on the application card and selecting Edit.

1.2. Access

1. Navigate to the Environments section, click the ellipsis icon near the preferred application, and select Access listed under the preferred environment.
   

1. From the Solutions section: Navigate to the Solutions page, click the Environment dropdown on the preferred application card, and select Access under the preferred environment to open the live mode of the chosen environment.
   
2. From the Edit mode of the application: While in Edit mode, click Access Development Live at the top-right corner to access the development environment. To access other environments, click the drop-down icon next to Access Development Live and select the preferred environment.
   

1.3. Settings

Alternatively, you can navigate to settings of the preferred application in the environments from the Solutions page by clicking the Environment dropdown on the application card and selecting Settings.

1. Demo Users
   
2. Notifications
   
3. Variables
   
4. Workflow Schedules
   

Note: In the production environment, the Settings option includes only Variables, as other sections are used solely for testing, which is conducted in the development and stage environments.

1.3.1. Demo Users

Note: The permissions assigned to demo users are the existing application permissions configured in Application Settings and are not separate permissions exclusive to testing.

1. Navigate to the Settings in the development or stage environment of the preferred application. A settings pane will open.
   
2. Click + Add Demo User under the Demo Users tab.
   
3. A pop-up will be shown. Select the demo user in the drop-down Name field. The demo users are predefined, and you can test up to five users.
   
4. Select the demo user type as User or Portal User based on your testing needs. Choose User if you want to assign roles and permissions within the application or Portal User to apply portal permissions defined in the application.
      
5. Select permissions and roles for the demo user from the drop-down, then click Add.
   
1. Only the permissions and roles added in the respective environment will be listed. The demo user will be able to perform actions in the app depending on the assigned permissions.
   
2. 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.
   

1.3.2. Notifications

1. Mail Notifications
   
2. SMS Notifications
   
3. Push Notifications
   

Note: Notifications here refer to notifications of the send mail task and SMS tasks in workflows and form submissions.

1. Disable Emails: Emails will not be sent to any user irrespective of the preconfigured recipient.
   
2. Login User: All emails will be sent only to the logged-in user who has triggered the notification, irrespective of the preconfigured recipient.
   
3. Selected User: Emails will be sent only to a selected developer or admin from the dropdown irrespective of the preconfigured recipient.
   
4. Application specific: Mail notifications will be sent to the recipients preconfigured in the send email action and send mail Deluge task within the workflows of the respective environment.
   

1. Disable: SMS notifications will not be sent to any user irrespective of the preconfigured recipient phone numbers in the workflows.
   
2. Application specific: SMS notifications will be sent to the recipient phone numbers preconfigured in the send SMS action and the Deluge SMS integrations in the workflows of the respective environment.
   

1. Disable Push Notifications: Push notifications will not be sent to any user, irrespective of the preconfigured recipient.
   
2. Login User: Push notifications will be sent only to the logged-in user who has triggered the notification, irrespective of the preconfigured recipient.
   
3. Selected User: Push notifications will be sent only to the selected developer or admin from the dropdown, irrespective of the preconfigured recipient.
   
4. 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.

Select the preferred option and click Done to apply.
  

3.3.3. Variables

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 that get updated in real-time based on script executions.
   

1.3.4. Workflow Schedules

1. Suspend All Schedules: All the schedule workflows configured for that application will be suspended in the respective development or stage environment. 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. Only schedules with an enabled status on the workflows will be executed. 
   

Notes:

1. The selected option will only apply to the specific environment of an application where it is configured.
   
2. The ability to suspend schedules specific to an environment is a valuable addition as it aids in efficiently managing schedule limits within that environment. For example, the development and stage environments share a combined limit of 20% of the total schedule limit based on your pricing plan. Instead of continuously triggering schedules, you can optimize this limit by suspending the schedules in the applications that are no longer needed in the environments.
   

1.4. Logs

1. Success logs display the success response, action details, the user who configured the action, the time of execution, and the type of action.
   
2. Failure logs will also display additional error details.
   

You can filter the logs based on Time/Period and Type. The Time/Period options are Last one Hour/Day/Week/Month.

2. View Version History

1. Navigate to Environments and click the Version History button.
   
   The Version History page containing the list of all versions will be displayed. It also provides you with the flexibility to filter versions either by the application name or version type.
   
2. Click on the preferred version to look at it in depth. You'll be shown the list of components present in the application.
   
3. Click on a component to get a comprehensive view of changes made.
   

3. Points to note

1. When the application is added to environments, the users with the Developer role will be removed from the application. They can be re-added for development and stage environments as needed. Learn more about adding a developer to the application.
   
2. The application can only be edited or modified in the development environment.
   
3. In the production environment, the Settings will only contain Variables, as other sections such as Demo Users, Notifications, and Workflow Schedules are used solely for testing, which is conducted in the development and stage environments.
   
4. The Demo Users in the environments are configured with the existing application permissions configured in Application Settings and are not separate permissions exclusive to testing.
   
5. Script executions are environment-specific, so the current values of the variables may differ across environments based on script executions in different environments. Learn more about variable publish flow.
   
6. You can only view the defined value and current value of variables specific to the environment in the Variables section of the environment Settings. To create or manage variables, you must access the application settings in the development environment.
   
7. Current values of variables will not be carried forward when publishing the application to the consecutive environment. Instead, the current values will be replaced with the published defined values.
   
8. Applications installed from the marketplace support environments except development, since they cannot be modified. You can install updates, test them in the stage environment, then publish them to the production application.
   
9. Variables cannot be viewed or managed for the applications installed from the marketplace.
   

4. Related topics

1. Understanding environments
   
2. Adding applications to environments
3. Remove applications from Environments