Workflow for Using an External Job Site

If you or a colleague have already created an external job site using SCS Data Manager or some other means, you can import and edit that site's data within your project without affecting the data in the data synchronization area (assuming that you do not disable file overwrite protections; for more information, see Prevent Overwriting Job Site Data).

The chart below outlines the status of file overwrite protection and conflict resolutions for various paths through adding an external job site and external job site data:


Job Site	Job Site Designs
1a. Create a job site > File protection is off by default You can resolve site conflicts via the data sync area by: - writing project's site files to controllers - reading in* controller site files and then writing project's site files back out to all controllers	2a. Create a design > File protection is not available by default You can resolve design conflicts via the data sync area by: - writing project's design files to controllers - reading in controller's design files and then writing project's design files back out to all controllers	3. Add an external design (only if you delete a design previously created for the site in this project) File protection is off by default You can resolve design conflicts via the data sync area by: - reading in controller's design files and then writing project's design files back out to all controllers using stored file timestamps
1b. Add an external job site** > File protection is on by default You can resolve site conflicts via the data sync area by: - reading in controller's site files and then writing project's design files back out to all controllers using stored file timestamps	2b. Create a design** File protection is not available by default You can resolve design conflicts via the data sync area by: - writing project's design files to controllers - reading in controller's design files and then writing project's design files back out to all controllers
	2c. Add an external design** File protection is on by default You can import data from design files if there are no design conflicts between controllers
* "Reading in" means importing the data without creating an imported file node in the Project Explorer or adding the files to the Imported Files folder for the project. The only way to 'undo' data from ‘reading in’' is to resolve conflicts.
** If you save, close and reopen a project at stages 1b, 2b, or 2c, file protection settings are inherited from those stages, respectively.