1. Access
2. Settings
3. Logs
   

The above options will be displayed when you click on the ellipsis for the required app listed in the Environments page.

Access

Settings

This section is to add demo users with various permissions to test the app, and to configure notifications.

Note: Permissions here refer to existing app permissions, and not separate permissions exclusive to testing.

3. In Add Demo User pop-up, select the demo user in the Name drop-down. The demo users are pre-defined, and a maximum of 5 are provided. 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.

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

Notifications

Because the Stage environment is used for testing purposes, you 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 the send mail task and SMS tasks in workflows and form submissions.

1. Disable emails - No emails will be sent.
   
2. Login User - All emails will be sent to the logged-in user.
   
3. Selected User - Emails will be sent to a selected user from the list of developers and admins of the app in Stage environment.
   
4. Application specific - Email notifications will be sent to the specified email address in the workflow.
   

1. Disable - No SMS notifications will be sent
   
2. Application specific- SMS notifications will be sent to the specified phone number in the workflow.
   

The following options are available for sending push notifications in the stage environment, regardless of the recipients preconfigured in the Send notification action and the Push notifications Deluge task:

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

1. Variable - The name of the variable.
   
2. Defined value - The value that is assigned to the variable.
   
3. Current value - The current value of the variable, which gets 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.
   

Workflow Schedules

After publishing the configured schedule workflows (in development) to the stage environment, you might want to test those workflows before publishing them to the production environment. When you've completed validating those workflows, you may no longer need them to execute continuously. You can suspend the execution of all such configured schedules in the stage environment by choosing one of the below options. This allows you to suspend the execution of all or required schedules without disturbing the actual schedule configuration. 

Note:

1. This is an application-specific environment setting i.e., choosing one of the below options will affect only the configured schedules for the stage environment in that application. 
   
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.  
   

1. Suspend All Schedules - All the schedule workflows configured for that application will be suspended in the stage 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 stage environment settings,

1. SelectWorkflow 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 Stage environment.

Logs

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

Note: From the top bar, you can select the environment and the app for which you want to make the above changes.