...
| Info |
|---|
A sandbox is a test environment that allows you to experiment with Projector. There are three main benefits to having a test environment.
Sandboxes are strongly recommended for:
Projector provides two types of sandboxes. Production and Implementation. Please see this page to learn about how these options differ. There is typically a cost associated with a sandbox. For more information about how to obtain a sandbox and the associated cost, please contact your sales representative or contact support. |
Production Sandboxes
Production Sandboxes are copies of your production account. Projector can make/refresh your sandbox on demand with one business day notice. We may require it to be done over a weekend if you have a large amount of data. The sandboxes are based on backups made each weekend. When you create a sandbox you can choose either the previous weekend or the coming weekend as the data basis.
...
Please note that your choice of options may affect the cost of your sandbox.
| Sandbox Options | Description |
|---|---|
| Structural | Contains clients, users, resources, projects, and detailed task management |
Full | Same as structural +
|
Implementation Sandboxes
Implementation sandboxes are available to new customers who have agreed to implementation consulting. During an implementation it is common for Projector consultants to create and destroy sandboxes for testing, training, and data loading. When you are ready to "go live" (or nearly so), we create your production environment from the sandbox. You can then start using Projector to help run your business. Once you are live, your implementation sandbox can be deleted or converted into a Production sandbox. These sandboxes are offered for a maximum of 90 days in order to correspond to the normal implementation period plus about one month.
Show if
| special | @authenticated |
|---|
We only give users the most basic of choices, structural and full, as too many choices can lead to confusion. We do have the option of more granular sandbox details though. See . Click 'Here'.
In general, support isn't even involved in this anymore. Rather, it is a sales/billing team issue. So if possible, ask that division of Projector to handle these requests.
Source
We can create sandboxes based on either staging or production data. By default we use staging as you can end up with corrupt sandboxes if something changes in production mid-copy. There are also performance reasons to leave production alone. Staging gets backed up each Saturday night. And so, we typically tell clients that we can make their sandbox early next week based on this weekend's data. If they need it right away, we can use last weekend's data, but keep in mind that if it is Thursday or Friday, we may not have time to do it before the next sandbox refresh takes place.
Ask them if they want to terminate their old sandbox.
E-Mail Hack
In order to prevent users for being prompted to enter an account code, we can append .sandbox to their email addresses. Tell clients we do this by default and explain why. If they prefer, the hack does not need to be used.
Options
Offer them a Structural or a Full sandbox. There are many different ways to configure a sandbox, but don't bog them down with options unless they specifically request something.
Structural -> Clients, Users, Resources, Projects, and Project Management Data (DTM plans)
Full -> Everything in Structural plus Scheduling Data and Project Accounting Data
This simple list tries to break down what each level includes.
- Structure -> Clients, Users, Resources, and Projects
- Project Management Data -> Task Plans
- Scheduling Data -> Request and Booked hours
- Project Accounting Data -> Time cards, Cost cards, Invoices
The following are off by default, but can be turned on if needed. There may be additional charges for things like Salesforce.
- Salesforce
- SSO
- DA
- Scheduled Reports
- e3 Program
- Documents - by default no documents are included