| Name | The name of the development. |
| Revision | The revision level of the development. |
| Description | A description of the development. |
| Validated for Use | As icon indicating if the development is available for users to create development areas.| Icon | Description |
|---|
 | At least one development setting needs to be defined for the development. |
| Users can create development areas. |
|
| Model Version Connection | Model Version | The name and revision level of the model version associated with the development. This value is blank if the development was created using the Create Development from Store action. |
| Selector Only appears if the development was created using the Create Development from Model Version action. | The name of the branch where development data is stored. |
| DesignSync Connection Only appears if the development was created using the Create Development from Store action. | Store | The name of the store. |
| Path | The path to the development data on the above store. |
| Folder/Module | Specifies whether the path is for a folder or a module. |
| Selector | The name of the branch where development data is stored. |
| Other Development Information | Development Path | The path to the directory that will hold all the data associated with the development on the file server. |
| Development Area Root | The relative path to the directory that will hold all the development areas that users create for this development. |
| UNIX Group | The UNIX group that provides group ownership for the development file hierarchy on the file server. |
| Allow Area Path Override | Specifies whether users can specify their own path name for their development area:| Option | Description |
|---|
| Yes | Users can specify their own path name for their development area. | | No | Users must use the development area root path. | | Default | Use the value for the DesignSync server associated with this development. |
|
| Allow External Areas | Specifies whether users can create development areas on clients that do not have direct access to the main project path:| Option | Description |
|---|
| Yes | Users can create development areas on clients that do not have direct access to the main project path. Select this option for Windows users, or users on a different network that can access the development server but not the physical project path. | | No | Users cannot create development areas on clients that do not have direct access to the main project path. | | Default | Use the value for the DesignSync server associated with this development. |
|
| External Development Path | The path to the directory that will hold external development areas. The app manages the external development instance in this directory. You can use environment variables to build the path name. |
| Area Scrub Period | The period in days for clearing of unused data in the file and module caches maintained by the data replication system for the development. For information on data replication cache scrubbing, see the ENOVIA Synchronicity DesignSync Administrator's Guide. |
