Understanding the virtual environments overview page

Introduction

Virtual environments can be viewed, created, and managed from the overview page:

Here you'll find all existing virtual environments, with related information and options.

Available information & options

#	Summary
1	Shows the number of deployed virtual environments from your total allowance. A virtual environment is considered to be deployed when it includes at least one process flow deployment, irrespective of whether that deployment is enabled or disabled. If you have a virtual environment that's no longer used, you should remove any associated flow deployments to ensure that it's no longer considered as 'deployed' for your allowance count. Your allowance is determined by your Core subscription tier and associated bolt-ons.
2	Existing virtual environments are shown as tiles in the main display area. Each tile includes summary information, so you can see the current status and related details.
3	If you have lots of virtual environments, it can be useful to filter those displayed by type and/or status, or to search for virtual environments by name.

Virtual environment tile summaries

Each tile displays summary details for the virtual environment:

Available information is summarised below:

#	Summary
1	The virtual environment name, as a hyperlink. Click the name to access the configuration for this virtual environment.
2	Access options to delete or duplicate the virtual environment.
3	Lists all process flows currently deployed in the virtual environment.
4	When creating a virtual environment, you select a type of either test or live. Your selection here has no functional impact; however, you can filter environments based on this value.
5	The number of versions (of any status) associated with this virtual environment. A virtual environment is only 'active' (i.e. available for flow version deployments) when a deployed version is present.
6	A virtual environment is marked as deployed when it (a) includes a deployed virtual environment version AND (b) includes at least one deployed flow version. For more information, please see Understanding virtual environment versions.