A development can use any number of development settings. Also, more than one development can use a specific development setting. For example, you could define one development setting to support a locking model for hardware designers where data cannot be merged and a merge model development setting for software developers.
A development setting can be in any of these states:
Table 1. Lifecycle States for Development Settings| State | Description |
|---|
| Reference | Developments directly use this development setting. |
| Make Copy | For the first development instance of the related development, Enterprise DesignSync Administration creates a new branch (a full copy) of the design setting module, then the development instance connects to the branched development setting. The original development setting remains in the Make Copy state. The branched development setting, in use by the development instance, is changed to the Reference state. A development setting in the Make Copy state can only be connected to a single development. The copied development setting, which is in the Reference state, can be connected to additional developments. |
| Make Branch | For the first development instance of the related development, Enterprise DesignSync Administration creates a new branch (a full copy) of the design setting module, then the development instance connects to the branched development setting module. The original development setting remains in the Make Branch state. The branched development setting, in use by the development instance, is changed to the Reference state. A development setting in the Make Branch state can only be connected to a single development. The copied development setting, which is in the Reference state, can be connected to additional developments. |
When using the Make Copy or Make Branch state, Enterprise DesignSync Administration creates the branched module under the sync:///Modules/SYNC/DevelopmentSettings/ path on the same server that hosts the developments.
If the store defined for the development uses a different path, that store cannot be used to specify the connection for the branched module. If the app cannot find a store that can be used to access the new development setting module, it creates one. The new store is defined using this path: /Modules/SYNC/DevelopmentSettings. The app uses this format to name the store:
<Development Data Store Name>_settings<n>
where the <Development Data Store Name> is the name of the store used by the development data, and <n> is the next available integer. The app uses the username and password of the development data store for the new store.