Name | Enter a name for the instance, or select the AutoName check box to have the system generate a name. |
DesignSync Server | Click to select the server where this instance will be created. |
State | Enter the state in which this instance will be created:State Name | Description |
---|
Enabled | Immediately created on the server and then promoted to the Enabled state. If you choose this state, these conditions must exist:- The development path and development area path must be entered in this dialog box, or for the parent development or DesignSync server.
- The parent development must have at least one design tool suite for the DesignSync type defined.
- The parent development must have at least one development setting defined.
- If you select Yes for Allow External Development Areas, or you select Default and the Default is Yes, the external path must be defined in this dialog box or for the parent development.
If the instance cannot be promoted to the Enabled state, it is still remains in the Created state. | Created | The instance will exist, but cannot be used until additional configuration (listed in for the Enabled state) is completed. |
|
Description | Enter a description of the purpose of this instance. |
Development Path | Enter the directory path to the development. If you to not enter a value, the path defined for the development is used. If the development does not have a path defined, the path defined for the DesignSync server is used. If the server does not have a path defined, you can create the instance but you cannot enable it. |
Development Area Root | Enter the path to the development area. If you to not enter a value, the path defined for the development is used. If the development does not have a path defined, the path defined for the DesignSync server is used. If the server does not have a path defined, you can create the instance but you cannot enable it. |
UNIX Group | Enter the UNIX group that provides group ownership for the development file hierarchy on the server. |
Allow Area Path Override | Select whether to allow the user to override the development area path:Option | Description |
---|
Yes | Users can specify their own path name for their development area. | No | Users must use the development area root path. | Default | The value for the development associated with this instance is used. |
|
Allow External Areas | Select whether to allow the user to use a development area path 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. | No | Users cannot create development areas on clients that do not have direct access to the main project path. | Default | The value for the development associated with this instance is used. |
|
External Development Path | Enter the path to the directory for external development areas. If you to not enter a value, the path defined for the development is used. If the development does not have a path defined, the path defined for the DesignSync server is used. If the server does not have a path defined, you can create the instance but you cannot enable it. |
Area Scrub Period | Enter the period in days for cleaning the unused data in the file and module caches maintained by the data replication system for the development. |
Data Replication Root Path | Enter the path to the data replication root that holds the automatically-populated design data for the development. |