02.05.2013 Views

User Guide - Mks.com

User Guide - Mks.com

User Guide - Mks.com

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 5: Project and Sandbox Operations<br />

140<br />

2 <strong>User</strong>s share the sandbox by importing it through the network or<br />

mapped drive. The imported sandbox is by reference, so no working<br />

files are stored on the users’ machines.<br />

3 <strong>User</strong>s who imported the shared sandbox now have access to the<br />

working files in the shared sandbox, and use those files to create test<br />

builds on their machines without requiring those files to be stored<br />

locally.<br />

NOTE<br />

To share sandboxes, all clients connecting to the shared sandbox must be<br />

Source Integrity 8.6 or later.<br />

Imported<br />

Sandbox 1<br />

References<br />

Working Files<br />

Shared Sandbox<br />

Common<br />

Location With<br />

Working Files<br />

Imported<br />

Sandbox 2<br />

References<br />

Working Files<br />

Sandbox Shared With Multiple <strong>User</strong>s<br />

<strong>User</strong>s sharing sandboxes:<br />

must select View > Scan for Changes for the project to update their<br />

Sandbox view to see the true state of the sandbox (top level project<br />

updates recursively)<br />

should all be in same time zone<br />

can see deferred operations in their sandbox views that were created<br />

by other users, but those operations do not appear as entries in their<br />

individual Change Package views for the change packages<br />

corresponding to the deferred operations<br />

u s e r g u i d e<br />

Imported<br />

Sandbox 3<br />

References<br />

Working Files

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!