Skip to main content

Sandbox environments

Depending on the specifics of your license agreement with Salesforce, your organization should have access to Sandbox environments that can be leveraged to facilitate ongoing development and quality assurance activities as new changes are introduced and promoted through your Salesforce environments. Each time a new change is to be made that will be promoted to the Production Salesforce environment it is recommended that a new Sandbox environment be created to ensure all work is being performed within an environment that matches what is available within Production. You may also opt to refresh an already existing Sandbox rather than creating a new environment to be used.

Determination whether a sandbox should be created or refreshed is outside the scope of this page and varies across customers. You are encouraged to reference the Salesforce product documentation for additional information and consideration when leveraging Sandboxes.

Regardless of approach (refresh or create new), the critical point is to ensure work begins in an environment that is representative of the latest and greatest configuration within your production environment. Once a fresh Sandbox is available, a series of steps must be performed to ensure Komodo Publications Planning functions correctly and does not interfere with any production environments. The sections below detail the changes recommended for native Komodo Publications Planning product capabilities; it does not cover any customizations or additional integrations leveraged in conjunction with Komodo Publications Planning.

Sandbox types

Generally there are 3 types of sandboxes that are of concern when selecting a type for new Sandboxes:

  • Full Sandboxes contain full copies of your production data and metadata. These instances require the least amount of consideration when attempting to re-establish Komodo Publications Planning functionality. However, there are typically less of these environments available when compared to the other types.

  • Partial Copy Sandboxes generally contain your production metadata but only a portion of the available data. In these cases, it is highly recommended to copy all Custom Settings (if available) and these custom objects:

    • Region (mvn__Region__c)

    • Product (mvn__CM_Product__c)

    • Congress (mvn__Congress__c)

    • Congress Location (mvn__PP_Congress_Location__c)

    • Journal (mvn__PP_Journal__c)

  • Developer Sandboxes generally contain your production metadata and no data. As a result, special steps need to be taken depending on the nature of the change you are attempting to make to restore Komodo Publications Planning functionality.

Application configuration

Email deliverability

A new Sandbox always has the ability to send emails turned off. To turn this capability back on:

  1. Navigate to Setup > Administer > Email Administrations > Deliverability

  2. Change Access Level to All Mail.

  3. Click Save.

Product and Region catalogs

A Full Sandbox refresh retains all data (i.e. Documents, Targets, Contacts, Plans, Product, etc.) from Production. Partial Sandbox refreshes and Developer Sandbox refreshes do NOT. If this is the case, you need to export the Product (CM_Product__c) and Region (mvn__Region__c) records and re-import them in your new Sandbox using a Salesforce data tool, such as Data Loader or Salesforce Workbench. Depending on the number of products and regions in your Production environment, you can manually re-create the records in your Sandbox environment rather than importing them.

Microsoft 365 integration

Komodo Health maintains two Microsoft 365 instances: Microsoft 365 production and Microsoft 365 test. Connect and use the Microsoft 365 production instance in a Komodo Publications Planning production environment and the Microsoft 365 test instance in a Komodo Publications Planning sandbox environment.

To configure Microsoft 365 in your sandbox environment, visit Microsoft 365.