Storacle in a Sandbox

A sandbox brings the package across without the records an install creates. Three free steps put them back.

Why a sandbox needs steps at all

A sandbox refresh is a copy, not an install. Storacle creates its reference data and starts its trial when it is installed, and a copy never runs that install, so none of it is there.

Storacle supports sandboxes so you can check that the package behaves in your org before you rely on it. It is not built to run the product there. For the org your team will rely on, follow the Setup Guide.

What a sandbox has, whatever production holds

These hold for every sandbox type, including Full and Partial Copy sandboxes.

It runs on the free tier

Whether you install Storacle into a sandbox or it arrives in a copy of an org that has it, the sandbox gets the free tier.

Seats stay with the org that bought them

A seat belongs to one org. Seats held in production do not follow the copy, so a sandbox of a paid org is still a free-tier org.

There is no trial

A trial starts once, when Storacle is installed, in the org that installed it. A sandbox never starts one.

The user list starts empty

No Storacle user records come across in the copy, so nobody is on the user list until someone is added. That is the second step below.

There is no history yet

Storacle has no measurements in the sandbox, so there are no snapshots and no forecast until the engine has run there long enough to build some.

The three steps

All three are free, and none of them needs a seat. Restore the configuration first: the engine needs it to take snapshots.

1

Restore the configuration

Storacle Home shows a banner saying Storacle is missing configuration it creates when it is installed. Its Restore Configuration button opens Storacle Configuration, where the same button puts back the shipped reference data: the tracked-object exclusions, the storage-factor exceptions, the snapshot definitions, and the alert definitions.

Without that reference data, snapshots, forecasting, and alerting do not run. Restoring writes nothing the org already holds, so it is safe to press more than once.
2

Add yourself to the Storacle user list

If you hold the Manage Storacle Users custom permission, which the Storacle Administrator permission set carries, add yourself from the users section of Storacle Configuration. If an administrator has given you the Storacle permission set instead, Storacle Home offers Add me to Storacle.

Either way you join the list as a free user. Neither path needs a seat.
3

Schedule the engine

Open the Setup section of Storacle Configuration and press Schedule the Engine. It schedules the nightly run under you, replacing any job someone else holds. Scheduling needs the Run Storacle Engine custom permission.

The first measurement comes with tonight's run. Press Run Engine Now on Storacle Home if you would rather have one immediately.

If a step does not work

Troubleshooting covers a banner that will not clear and an engine that will not run. If that does not settle it, contact support.

← Back to Documentation