User Help > Managing Your Personal Workspace in a Sandbox > Configuring a Sandbox
Configuring a Sandbox
 
si configuresandbox
If you want to change the configuration of a Sandbox, open the Sandbox Information view for a top-level Sandbox created by you (Sandbox > Views > View Information), and check the appropriate options on the General panel:
• Sparse if you do not want the Sandbox to retain working files when a member is checked in. A Sandbox is sparse if it has no working files. A sparse Sandbox does not retain working files when a member is checked in, and continues to function this way throughout its use; however, once created, Sandbox directories and sub Sandboxes remain in the Sandbox.
• Scope displays the current Sandbox scope definition (if specified) and allows you to change the scope. Sandbox scope defines what subprojects and/or members are included in the Sandbox. A Sandbox scope transfers specific subprojects and/or members from the PTC RV&S server to the Sandbox directory when the Sandbox is created, and controls what subprojects and/or members display in the Sandbox view.
To change the Sandbox scope definition, ensure that you are viewing the Sandbox information for the top-level Sandbox and click Change Scope.
Changes to the scope definition are automatically reflected in the Sandbox view. Out of scope subprojects are automatically hidden from the view unless the corresponding folders exist on disk. Members with working files in the Sandbox that no longer match the scope definition display deltas, but remain in the Sandbox. Selecting one of the members indicates that a working file exists and the member does not match the Sandbox scope. Perform a Resynchronize operation to remove out of scope members and subprojects from the Sandbox. For more information, see “Specifying the Sandbox Scope”.
* 
Using the si createsandbox and si configuresandbox commands, you can create and edit more complex Sandbox member scope definitions using a combination of logical AND or OR operators; however, these definitions may not always be editable from the GUI. If you attempt to edit a complex member scope definition from the GUI, PTC RV&S truncates the definition to what the GUI is capable of displaying. If you attempt to edit a complex member scope definition using the si configuresandbox -g/gui command, PTC RV&S displays a warning message that choosing to edit the scope definition removes the options the GUI is not capable of displaying.
• Use Checksums to Calculate Member Deltas identifies changes to the working files in the current sandbox by calculating the checksum of revisions. A full resync with --overwriteUnchanged option is also required for this option to take effect.
• Automatically Resolve Potentially Modified Working Files identifies working files that have identical checksum despite of having a modified timestamp. When selected, the system uses the differencing operation to confirm modifications in working files. Depending on the output of the differencing operation, the status of the working files is updated. This option works only when the Use Checksums to Calculate Member Deltas option is selected.
◦ For New Sandboxes: By default, the option is not selected. However, if your administrator has enabled it for the Create Sandboxes command in the PTC RV&S Administration Client, then by default, this option is selected for new sandboxes.
◦ For Existing Sandboxes: The selection of Automatically Resolve Potentially Modified Working Files option depends on the existing preferences. If no existing preferences are set for the sandbox, then it is not selected by default.
◦ For Imported Sandboxes:
▪ For sandboxes imported from versions older than PTC RV&S 13.3.0.0, the Automatically Resolve Potentially Modified Working Files option is not selected by default.
▪ For sandboxes imported from PTC RV&S 13.3.0.0 and later versions, the existing settings on the sandboxes are carried over.
* 
• In a sandbox, if the number of potentially modified files is large, selecting this option may have an adverse impact on the overall performance of the PTC RV&S Client, Server, or the FSA server.
• When the option is selected, the potentially modified working files are resolved in batches. If you clear the selection for this option when the resolution is in progress, the changed preference takes effect only after the differencing operation for the current batch is completed.
Was this helpful?