Using a personal workspace and named sandboxes
Using a personal workspace typically offers a performance improvement over Direct Writeback because users can evaluate their data changes before they commit them, so there is usually less server processing. When Job Queuing is turned on, your personal workspace is subject to processing in the queue before committed changes are merged with the base.
In personal workspace, you begin with the base data. When you make data entry changes, the content that changes, including dependent cells such as consolidations or rule-generated values, change color to blue to remind you that these changes have not yet been merged with the base model. When you commit the personal workspace and processing is complete, the color changes back to black and you are working on the Base again. See Understanding cell coloring for changed data values.
When you have personal workspace granted and the ability to name sandboxes also granted, the starting point for sandbox data is identified in the toolbar as [Default].
You have access to the Commit and Reset Data buttons when you work in personal workspace.
| You want to | Personal workspace mode | Sandbox |
|---|---|---|
| Always work in a private area and decide when to commit your changes to the server manually. Occasionally, you want to save a set of changes and name them something such as "Best Case" before you commit them to the server. | On | On |
When you have personal workspace and named sandboxes, the toolbar includes Commit, Reset Data, Sandbox buttons and the sandbox starting point is called [Default]:
You have the Commit and Reset Data buttons because you are working in a personal workspace. The [Default] sandbox is the way to identify the starting sandbox until you name a sandbox.