Environment Custom Types

In the section Understanding Custom Types and Properties the basic concepts of managing custom types and properties are described. In this section we focus on how to apply those concepts in the context of environments.

Environments may be of different types, such as Test Environment, Production Environment, ... When a new environment is created, a new instance of a particular environment type (for example, Production Environment) is created as well.

Properties of Custom Component Types

When you create a new custom environment type version (using the create command), you can define the following properties:

• Name

  The name of the custom environment type.

  Example: Test, Preproduction, Production

• Properties

  The properties of the Environment.

• DynamicProperties

  The dynamic properties of the Environment.

See: Working with Custom Types

Behavior

• If you create a new component type version based on an existing type version, a clone of the old version is created. You can therefore change any properties without affecting the older version.
• When updating a component custom type, changes to properties (of the project type and milestones) immediately affect ALL current instances of that component type version. For example, if you delete a property, you will irreversible delete the data of all components (of that type version) which were entered for that property.
• You cannot delete component types which have instances