• 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

1. In the Environments page, click the ellipsis for the required app. In the dropdown, choose the Access option under the Stage section.

   

2. The live application will be displayed. The Stage label will be displayed in the top-left corner.

   

3. Under the View As field in the top bar, choose the demo user.

   

Settings

1. Demo Users - You can add demo users with various permissions and roles to test the app. Demo users are predefined, 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.
   To add demo users:
   • Click Settings in the drop-down of the required application in the environments.

     

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

     

   • 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 10 are provided. Select a user.
     

   • Select a permission and a role for the user. The 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 the assigned permissions. Click Add.
2. 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.
   The following options are available for email notifications:

   

   • Disable emails - No emails will be sent.
   • Login User - All emails will be sent to the logged-in user.
   • Selected User - Emails will be sent to a selected user from the list of developers and admins of the app in Stage 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 stage 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 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.

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

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

Related Links

• Understand Environments