Refresh a sandbox site

If you are making any major changes to your site, we recommend that you initially make the changes in a full sandbox organization. However, when your full sandbox organization is refreshed, there are some steps you need to take in the full sandbox organization to make the site work properly:

• Enable OrchestraCMS licenses for the new organization ID
• Edit domain and URL settings to use sandbox properties

Refreshing a sandbox and SandboxCleaner class

A Full Sandbox should be refreshed from the Production org as close to the intended upgrade date as possible. This ensures that the upgrade process is an almost exact representation of the experience that will be seen for the eventual Production upgrade.

In a full sandbox refresh, content, pages and media will be transferred from the production org. In a non-full sandbox refresh, content, pages and media will not be transferred.

If you are using a partial copy sandbox, we do not recommend including any OrchestraCMS-related records and may be unable to provide support to a sandbox in this state.

The "SandboxCleaner" class should not be used when refreshing a full sandbox. When refreshing a sandbox, one can specify an apex class to run after the refresh. Using SandboxCleaner will automatically clear settings carried over in the refresh that prevent OrchestraCMS from running as expected.

Because we cannot automatically remove OrchestraCMS Permission Sets that have been assigned to communities, when you are using the SandboxCleaner class, please check the Apex Job records after the sandbox refresh has completed.

If there are no errors, as it will be like a brand-new installation of OrchestraCMS.

If there is an error that says "First error: Delete failed. First exception on row 5 with id 0PS000000000000000; first error: DEPENDENCY_EXISTS, you can't delete this permission set because it is used in a community", you will need to remove the users from the OrchestraCMS permission sets manually before deleting them.

All Permission Sets related to OrchestraCMS sites will be named in the format of "ocms OrchestraCMS [PROFILE NAME] [SITE NAME]" and also the ocms_SiteViewer permission set.

Customers can contact the Stantive Customer Support team to assist in restoring the application to a state with a blank site without having to uninstall and reinstall OrchestraCMS. (Login access will need to be provided to the Stantive Customer Support team for this.). This should only be required if you have not used the SandboxCleaner class.

The Scheduler

The OrchestraCMS Scheduler is used for caching, and it should be started by a user with a Salesforce System Administrator profile to prevent any permission errors if it is not running.

The upgrade should be performed by a user with a Salesforce System Administrator profile who has access to all sites — such as an OrchestraCMS System or Site Administrator.

Enable OrchestraCMS licenses for the new organization ID

Your OrchestraCMS licenses are associated with your Salesforce organization IDs. Each time a sandbox is refreshed, a new organization ID is created. To have your OrchestraCMS licenses applied to the refreshed sandbox, contact customer support to add the new organization ID to your account at customer-support@stantive.com.

Edit domain and URL settings to use sandbox properties

The domain and URLs for Force.com sites include the Salesforce instance of the organization. These properties must be updated in OrchestraCMS Setup to reflect the sandbox organization.

To edit domain and URL site settings

1. In OrchestraCMS Setup, under Site, click Details.
2. On the Site Details page, click Edit.
3. Edit the following fields as applicable:
   • Site Domain
   • Site Secure Domain
   • Site URL
   • Site Secure URL
4. Click Save.