Difference between revisions of "Sandboxes"
imported>Aeric (Created page with "Sandboxes provide safe environments for development and testing that are separated from the production environment. They allow object definitions and platform elements to migrate…") |
imported>Aeric |
||
| Line 3: | Line 3: | ||
==About Sandboxes== | ==About Sandboxes== | ||
A tenancy. | When you log in to the platform, you log into your organization's [[tenancy]]. (Basically, your organization is a "tenant" in the platform.) When you set up a ''sandbox'', you create a "sub tenant" that can interact with the main tenancy, and with other sub tenants. | ||
In a sandbox, you can modify and test an application without changing the production version. When the application is ready, it can be migrated to a Q/A sandbox to further assure quality, before finally migrating to the main tenancy--the "production" system that everyone in your organization is using on a day-to-day basis. | |||
:;Considerations: | :;Considerations: | ||
::* Data does not migrate. To copy data between sandboxes, use the [[Export]] and [[Import]] mechanisms. | ::* Data does not migrate. To copy data between sandboxes, use the [[Export]] and [[Import]] mechanisms. | ||
::* Sandboxes can only created when logged into the main tenancy. They cannot be created from a sandbox. | |||
::* All capabilities that are enabled in the main tenancy are enabled in the sandbox, when the sandbox is created. (After creation, changes made to either one do not affect the other.) | |||
==Working with Sandboxes== | ==Working with Sandboxes== | ||
{{Capability| feature | Sandboxes}} | {{Capability| feature | Sandboxes}} | ||
{{Permissions|Manage Sandboxes| create and delete sandboxes}} | {{Permissions|Manage Sandboxes| create and delete sandboxes}} | ||
Revision as of 23:45, 25 October 2011
Sandboxes provide safe environments for development and testing that are separated from the production environment. They allow object definitions and platform elements to migrate to and from the production environment, and between sandboxes.
About Sandboxes
When you log in to the platform, you log into your organization's tenancy. (Basically, your organization is a "tenant" in the platform.) When you set up a sandbox, you create a "sub tenant" that can interact with the main tenancy, and with other sub tenants.
In a sandbox, you can modify and test an application without changing the production version. When the application is ready, it can be migrated to a Q/A sandbox to further assure quality, before finally migrating to the main tenancy--the "production" system that everyone in your organization is using on a day-to-day basis.
- Considerations
-
- Data does not migrate. To copy data between sandboxes, use the Export and Import mechanisms.
- Sandboxes can only created when logged into the main tenancy. They cannot be created from a sandbox.
- All capabilities that are enabled in the main tenancy are enabled in the sandbox, when the sandbox is created. (After creation, changes made to either one do not affect the other.)
Working with Sandboxes
Users that have the Manage Sandboxes permission can create and delete sandboxes
