Network instances

Customers are allotted four Sandbox instances and one Production instance with their Network license.

New Network instances

When new Sandbox or Production instances are created, the following configuration is applied:

• All existing Veeva OpenData fields are configured to be enabled
• Reference data configuration in the instance is identical to the configuration in all OpenData instances.
• A "System and Data Admin" user is created. This user type has access to all of the features in the Network UI.
• A data visibility profile for US data is created.
• All system-managed user groups are created.
• A default Notes Permission Set is created.
• The following inbox task groups are created: Data Stewards (US), Data Loading Jobs.
• Default Network hashtags are enabled.
• The following hierarchies are created to
• A Network Portal is created with a unique URL for the instance.

• All features are configured to be enabled.

  Note: There are a few features that must be enabled by Veeva Support. When a feature is not enabled by default, it is noted in the Network Help so you can request the feature by contacting Veeva Support.

Production instances

Production instances display a tag to help you quickly identify the environment you are using. These tags display for awareness, but also help prevent Admin and Data Manager users from accidentally changing data in the wrong environment, which can be time-consuming and costly to fix.

The Production tag is visible on all of the Admin areas in a Production instance. It does not display on the Network menu bar.

Sandbox instances

Sandbox environments are pre-production environments used for development and testing. Sandboxes do not have connections to Network Production instances.

By default, new customers receive one Production instance and one Sandbox instance.

Network releases

PODs that contain Sandbox instances are updated two weeks before Production PODs.

Use the Sandbox release to begin validation assessment and to try out new features and enhancements.

Veeva OpenData considerations

The first Sandbox instance that is provisioned for new customers is connected to a copy of Veeva OpenData; not the OpenData production instance. This Sandbox instance can receive updates from that master data using Veeva OpenData subscriptions.

Any subsequent Sandbox instances are not connected to Veeva OpenData by default; but you can request a connection.

Data change requests

Data change request (DCRs) processing depends on the Sandbox configuration:

• Sandbox is connected to an OpenData instance (your first Sandbox instance) - Data change requests on OpenData owned fields and records are auto-approved. They are not processed unless arrangements are made with OpenData.

  All other requests will be processed locally according to the workflow settings on the page.

• Sandbox is not connected to an OpenData instance (subsequent instances) - Data change requests on OpenData owned fields and records can be automatically approved in the following situations:

  • Workflow settings have auto-approve option enabled (Settings > Workflow Settings)
  • The DCR creator is a data steward or data manager user
  • The DCR is a change to Veeva OpenData record; for example, changing a value in a Veeva OpenData field. Adding a sub-object on a Veeva OpenData record will not be auto-approved.

  All other requests will be processed locally according to the workflow settings on the page. DCRs that are not auto-approved remain as Pending Review in your Sandbox environment.

The Workflow Settings page indicates how the Sandbox instance will process data change requests.

Example - Sandbox not connected to an OpenData instance

Requesting a Sandbox environment

Customers are allotted four Sandbox instances with their Network license. To request another of your allotted Sandbox instances, contact Veeva Support.

The following information is required in your Support request:

• Domain name of the new Sandbox environment; for example, customerdev2.veevanetwork.com.
• Name and email address of the person who will receive the welcome email.

• Requested configuration - do you want a blank Sandbox instance (default) or a clone of another environment (includes the data and configurations).

You can request to link the new Sandbox instance to Veeva OpenData; by default, it will not be connected.

Note: Additional Sandbox instances can be purchased. Contact your Veeva Account Executive.

Using cloned data in your Sandbox instance

Cloning an existing environment so your Sandbox contains data, configurations, and custom settings enables you to test configurations and new features outside of your Production environment. Also, it helps to keep your Network Sandbox and Veeva CRM or Vault CRM Sandbox integration aligned.

For more information about the CRM alignment, see the Synchronizing your CRM Sandbox section below.

Task considerations

When a Network instance (Sandbox or Production) is cloned, all tasks are included. This includes tasks in any state. Pending tasks should be closed before the source instance is cloned because cloned tasks cannot be processed in the target instance. If a pending task is cloned to a target instance, there is no indication on the task to identify if it came from cloning or it was newly created in the instance.

Refreshing a Sandbox environment

To request a new Sandbox or refresh an existing Sandbox using a clone of a Network Production instance, contact Veeva Support.

The following information is required in your request:

• Source environment - The instance that will be cloned. Provide the instance ID and instance name. This is typically a Network Production instance.
• Target environment - The instance that is receiving the clone. This might be the domain name of your new Sandbox instance.
• Date that the clone request should be started or completed.

Data that will be cloned

The following data is included in a standard clone request:

• All data from the source instance (objects, sub-objects, relationship objects)

• Tasks in all states (pending review, accepted, rejected, and so on)

  Note: Cloned tasks cannot be processed in the cloned instance. Pending tasks should be closed in the source instance before the instance is cloned.

• Audit history
• Configuration (source subscriptions, target subscriptions, data maintenance jobs, and so on).

Data that will not be cloned

These configurations or data cannot be cloned and must be created in your new Sandbox environment:

• Revision History
• FTP folder contents
• Job events for jobs that ran in the source environment
• User accounts
• Data visibility profiles
• Field restrictions
• Profile Notes
• General settings - Some settings will not be included; for example, the Validation Rules settings are not included in the clone.

Cloning process

Typically, it takes 3-5 days to clone an environment. When the cloning process occurs, the target Sandbox is locked and users cannot log into the instance. Veeva Support will advise you when the clone is complete and the Sandbox can be used again.

If a new Sandbox instance is being created and is being updated with cloned data from another instance, you will receive the System and Data Admin welcome email with credentials, but you will be unable to log in; the instance will be locked until the clone is complete. Support will let you know when your new Sandbox environment is ready.

Sandbox URLs

Sandbox instances have their own URL. This is helpful for displaying the single sign-on button on your Sandbox instance's login page.

Note: If your Sandbox instance was created before 20R3, the URL was generic; for example, sandbox.veevanetwork.com. The generic URL is still valid.

Sandbox tags

A Sandbox tag displays throughout the Sandbox instance; on the Network menu bar and in the Admin console. It displays the instance name so you can identify the instance you are in if you have multiple instances.

Synchronizing your CRM Sandbox

It is important to keep your Veeva CRM Sandbox and Network Sandbox instances aligned so you can validate the integration.

Veeva IDs (VIDs) for Veeva managed records remain the same, but the VIDs for locally managed records change from environment to environment when records are created. The key to keeping the integration intact between Veeva CRM and Network is to ensure the VIDs align. The Production clone process ensures the VIDs from your Production instance and Sandbox instance are the same and integration between your CRM Sandbox and Network Sandbox is seamless.

To synchronize your Network and CRM Sandbox instances, complete the following tasks.

Refresh the Sandbox instances

1. Refresh your CRM Sandbox instance.

2. Contact Veeva Support to request a Network Sandbox refresh using a clone of your Production instance.

   The Network Sandbox refresh will take 3-5 business days. When the clone is complete, you will receive an email to reset your password.

Network Bridge configuration

Complete these steps:

1. Log into the Network Sandbox instance.
2. In the Admin console, click System Interfaces > Systems and note the system name for your Veeva CRM instance (for example, VCRM or the org ID, VCRM-00DA0000000xxxxxx)
3. Click Users and create an integration user for the Network Bridge. The format of the Username should be: <integration_username>@<Network Sandbox name>.veevanetwork.com.
4. In the Welcome email, reset the password for the Network Bridge user.

5. Click Settings > External Credentials and create a new Salesforce™ credential.

   

   1. Name - A meaningful name for the credential.
   2. Username and Password - The credentials for the Network Sandbox integration user.
   3. URL - Choose https://test.salesforce.com from the list.
   4. Click Test Connection to validate the credentials.
6. Click System Interfaces > Network Bridge.
7. Update the integration user and Salesforce credentials in the Network Bridge. Save your changes.

CRM Sandbox configuration

1. Log into the Veeva CRM Sandbox that is associated with this Network Sandbox. Use https://test.salesforce.com.
2. Click the Network Administration tab.

3. Edit the Network Credentials:

   1. Type the Network Sandbox URL. For example, https://sandbox.veevanetwork.com.
   2. Add the username and password for the integration user to access the Network Sandbox; for example, <integration_username>@<Network Sandbox name>.veevanetwork.com. For Network Bridge users, this is the Network Bridge username and password that you created in the Network Sandbox
   3. Click Submit and then Validate.

4. Edit the Salesforce Credentials:

   1. Add the Salesforce username and password; for example, <network.admin>@.verteo.com.sbx.
   2. Beside Sandbox? choose Yes.
   3. Click Submit and then Validate.

5. Edit the System Identification. Select the System Name for the CRM Production system that is used in Network; for example, VCRM.

   

6. Click Submit and then Validate.
7. Clear Veeva Cache.

Troubleshooting the synchronization

After you synchronize the refreshed Network and CRM Sandbox instance, errors might occur when you are testing the multichannel server.

Perform the following steps to resolve the errors:

1. In the Veeva CRM Sandbox, click Setup > App Setup > Develop > Custom Settings.
2. Next to MultiChannel Settings, click Manage.
3. Click Edit and then Save (without making any changes).
4. Return to the Custom Settings page. Beside Network Settings, click Manage.
5. Click Edit and then Save (without making any changes).
6. Clear Veeva Cache.

Test the connection using Network Account Search and by running the Network Bridge.