Name | Enter a name for the development. |
Revision | Enter the initial revision value for the development. |
Description | Provide a description of the purpose for this development. |
Copy Development | Click to search for and select the development whose development settings you want to use as the basis for the new development. For more information about copying developments, see About Copying or Revising Developments. |
Model Version Connection | The current model version name and revision, which will be associated with the new development. |
Development Path | Path to the development's storage directory accessible by the server to store ancillary development data, including a copy of the development setting used to control the development. This development path contains the location where all the design data is fetched and managed locally into the development’s data replication root. All development areas defined by users are placed into this development path as well. |
Development Area Root | Defines the relative path to the directory that will hold all the users’ development areas created for this development. If you do not define a value, the app creates the user-specific development area in this subdirectory: DevelopmentAreas/<userName>/<developmentAreaName> You can define a relative path to the directory that will hold all the users’ development areas. You can include environment variables to build the path name. This path is relative to the development path (defined above). |
UNIX Group | The UNIX group that provides group ownership for the development file hierarchy on the server. |
Allow Area Path Override | Select 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 | Select 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 Develoment Path | Enter 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 | Enter 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. |