Skip to main content
hamburger menu Created with Sketch.
Updates were made to the Support and Services ticketing processes. Click the link below the search bar for more information.

Search the Knowledge Base

Engage Connect FAQ: Testing in the Engage Sandbox Environment

  • Updated

For ease of reading, we have broken out the Engage Connect FAQs into sub-articles.

This article covers: 

For other topics in the Engage Connect FAQ, please see the sub-articles list on the top level article
FAQs: Engage Connect Functionality and Best Practices in Veeva CRM. 

When testing Engage Connect in the Engage Sandbox environment, CRM Users and Test HCPs should be sure to log in to the Sandbox environment, not Production Engage Connect. Please see our documentation on Testing Veeva Engage in Sandboxes, and remember the points explained below.

 

How do Test HCPs log in to the Sandbox Environment of Engage Connect? 

Test HCPs should either log in to the Sandbox Engage Web Client at https://sandbox.veevaengage.com or log in to the Veeva Engage app with the method detailed in Testing Veeva Engage in Sandboxes - Signing up and Signing in on the Mobile App. 

With this method, Test HCPs append .app-sbx to the end of their email address when signing up or signing in, to access the Sandbox environment.

Note: Test HCPs do not need to be set up in the Company Configuration File with .app-sbx appended on their email address. This suffix must just be typed after the HCP's email address when logging in to the mobile app, to direct the app to connect to the Sandbox environment.

 

How do CRM Users (Reps) log in to the Sandbox Environment of Engage Connect? 

CRM Users accessing Engage Connect and wanting to connect to the Sandbox environment must select the Gear icon on the login screen.

mceclip2.png

Next, the user must select the Sandbox option:

mceclip3.png

Then, the user can log in with their CRM Sandbox Org credentials.

mceclip4.png

Note: Unlike Test HCPs logging into the mobile app, CRM Users do not need to add .app-sbx to the end of their email address to log into the Engage Sandbox environment. The app is directed to log into Sandbox by the steps listed above. 

 

How can Test HCPs or CRM Users verify they are logged into Sandbox Engage Connect? 

Test HCPs and CRM Users both can verify they are logged in to the Sandbox Engage Connect environment by looking for sandbox.veevaengage.com displayed at the bottom of the Me Tab, under the Sign Out option, as shown here:

mceclip1.png

 

Can New Functionality in Engage Sandbox be tested in the Mobile Apps before it is added to Production? 

New Engage Connect functionality is put into the Sandbox environment of Engage before it becomes available in the Production Environment of Engage.

When new functionality is added to the Sandbox environment of Engage Connect, it is available only on the Sandbox Engage Web Client website (https://sandbox.veevaengage.com) used by HCPs, until the functionality is added to Production Engage. This is because there are not separate Sandbox versions of the HCP and CRM User Engage Connect Apps.

Functionality that is still only in the Sandbox environment of Engage is therefore not available for the Android and iOS apps, and not available for CRM Users to test. But if it is HCP-facing functionality, it can be seen in the Sandbox Engage Web Client.

Once the functionality is released to Production it is then made available on all platforms, both the HCP website and the HCP and CRM User mobile apps.

 

Sandbox User Email Addresses and Engage Connect Groups 

In a Sandbox org, user email addresses are automatically appended with .invalid at the time of org refresh. 

As noted in our Online Help, users cannot be added to Engage Connect groups if their email address ends in .invalid. Please correct Sandbox user email addresses after Org refresh before adding them to Engage Connect Groups. 

Related Documentation:

CRM Help Documentation: 

 

Powered by Zendesk