Copying or Revising a Development

You can copy or revise an existing development.

See About Copying or Revising Developments for information about the difference between copying and revising a development.

  1. To copy or revise a development:

    1. View the list of Developments. See Developments Page.
    2. Open the required development. See Opening a Development.
    3. To copy a development, select Copy Development .

      or

      To revise a development, select Revise Development .

      This action is only available if the development was created from a DesignSync store.

      Note: You can also revise a development from the Developments page. See Developments Page.

  2. Enter or update these details:

    Field NameDescription
    Name

    Only editable when you are copying a development.

    		Enter a name for the development.
    RevisionEnter the initial revision value for the development.
    DescriptionProvide a description of the purpose for this development.
    Store

    Only editable when you are copying a development.

    		Click to search for and select the DesignSync store.
    Path

    Only editable when you are copying a development.

    		Click to search for and select the path to a DesignSync module or module version. You can also type the path in the text box. If you type a path to a module that does not exist, the DesignSync server creates the path.

    If you manually enter the path, it cannot contain any of these special characters: @,*?[]#${}"<>|: ' ~%^&()`= The path name should resolve to a module or module version on the DesignSync server. If the path needs to create a module, the new module cannot be created under another module.

    Folder/Module

    Only editable when you are copying a development.

    		Indicate whether the path is for a folder or a module.
    SelectorEnter the name of the branch.

    • If the branch does not exist, it will not be created.
    • If you enter Trunk, the systems appends :Latest to the branch; the selector would be Trunk:Latest.
    • If you enter a text string with a colon, the system appends Latest to the branch. For example, if you enterGold:, the selector would be Gold:Latest.
    • If you enter a text string other than Trunk without a colon, the system does not append anything to the branch. For example, if you enter Gold, the selector would be Gold.

    Development PathSpecify the path to the development's storage directory accessible by the development 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 RootSpecify a 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.

    UNIX GroupSpecify the UNIX group that provides group ownership for the development file hierarchy on the file 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.

  3. Click Done.