Editing Development Properties

You can edit the values of properties for a development.

See Also
Development Properties
  1. Open the required development. See Opening a Development.
  2. Click Edit .
  3. Edit these details:

    Note: When you are editing a development that has no development instances or has all of its development instances in the Created state, you can change the DesignSync module or the model version associated with the development.
    Field NameDescription
    DescriptionEnter a description of the purpose for this development.
    Path

    Only shows if no development instances have been created for this development.

    Click to search for and select the path to a DesignSync module or module version.

    Development Area RootEnter 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 GroupEnter the UNIX group that provides group ownership for the development file hierarchy on the server.
    Allow Area Path OverrideSelect whether users can specify their own path name for their development area:

    OptionDescription
    YesUsers can specify their own path name for their development area.
    NoUsers must use the development area root path.
    DefaultUse the value for the DesignSync server associated with this development.

    Allow External AreasSelect whether users can create development areas on clients that do not have direct access to the main project path:

    OptionDescription
    YesUsers 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.

    NoUsers cannot create development areas on clients that do not have direct access to the main project path.
    DefaultUse the value for the DesignSync server associated with this development.

    External Develoment PathEnter 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 PeriodEnter 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.
    Note: Any changes you make do not affect any existing development instances in any state other than Created. Your changes will be used for new development instances and those in the Created state after you click Done.

  4. Click Done.