An Environment is a logical name given to a group of servers, applications, and technologies which work together to provide a software solution for the purpose of development, testing, or a production implementation. Typical Environments include, but are not limited to, Development (DEV), System Integration Testing (SIT), User Acceptance Testing (UAT), and Production (PROD).
...
By default, all active Environments are displayed in the search results. To refine the search results, type all or part of the Environment name into the Search box, and the list will automatically filter. Select the Active checkbox to show the inactive environments as well.
Creating/Editing an Environment
...
Field Name | Required | Description |
|---|---|---|
Environment Id | N/A | System generated identifier (read-only). |
Environment Code | Yes | Short name for the Environment. |
Environment Name | Yes | Long display name for the Environment. |
Description | No | A description of the Environment. |
Active | Yes | Whether or not the Environment is active in the system. Defaults to "Yes". |
Build Environment | Yes | Identifies whether the Environment is used for builds. Defaults to "No". |
Sort Order | Yes | A sort index to control the order in which the Environment is displayed within lists. |
Click the next tab is to optionally associate Instances to this Environment. Note that this is an optional step since there may not be any Instances created yet. In this case, simply save the Environment and perform the association when creating the Instance. Read about Creating Instances.
...
To inactivate an Environment at any time, click the Active link on the desired Environment, and it will toggle to Inactive. This will hide that Environment after leaving the screen, until the Active checkbox is unchecked. To reactivate an Environment, click the Inactive link and it will toggle back to Active. This Environment is now active in the system again and ready for use.