Sandbox Deployment

12 min

overview the altrata salesforce sandbox environment allows you to test and validate your salesforce integration before deploying to production a sandbox environment provides a dedicated non production environment that is separate from your production altrata account this allows your team to validate authentication, configuration, matching behaviour and user workflows without impacting your production implementation a sandbox environment includes \ component \ \ purpose \ sandbox account dedicated altrata testing environment service user used by the salesforce app for authentication api key used for api connectivity web user allows users to access and test altrata functionality directly when should i use a sandbox? we recommend using a sandbox if you are migrating from a foundation app (wealth x, boardex or relsci) implementing complex field mapping rules testing custom automations or workflows rolling out to a large number of users performing user acceptance testing before go live using a sandbox allows you to validate your configuration and deployment process before introducing changes into production how the sandbox environment works the altrata sandbox environment is a separate environment from production when a sandbox account is provisioned, it is created as a dedicated sandbox account with its own service user (used by the salesforce app for authentication) web user (used to test user facing functionality) api key authentication credentials sandbox credentials are different from production credentials and must be configured separately within the altrata salesforce app production and sandbox environments can be used at the same time what can i test in a sandbox? a sandbox supports the same core integration workflows as production you can ✅ install the altrata salesforce app ✅ configure authentication ✅ test api connectivity ✅ configure and test field mapping ✅ run bulk matching ✅ run manual matching ✅ validate enrichment behavior ✅ test lightning page layouts ✅ validate automation processes ✅ test user workflows ✅ test user contributed content ✅ validate reports and dashboards that depend on altrata data ✅ perform migration and deployment testing this makes the sandbox environment suitable for validating your end to end deployment before go live what data is available in the sandbox? sandbox environments use the same underlying altrata profile data available through your production subscription this means users can test against real altrata profile data and subscription entitlements synthetic or sample profile data is not currently available is sandbox content isolated from production? yes sandbox environments are designed to be isolated from production environments the sandbox account uses separate users and separate contributed content from production relationships and other user created content remain within the sandbox environment and do not share with the production account authentication sandbox authentication works in the same way as production the salesforce app is configured using username password api key the only difference is that sandbox environments use sandbox specific credentials which are provided separately from production credentials 🛑 do not use production credentials in a sandbox environment \ environment \ \ user type \ \ example username \ production service user svc abc crm sandbox service user svc abc crm sandbox production web user alex\@abc com sandbox web user alex\@abc com sandbox this allows the same individual to access both production and sandbox environments using separate accounts your sandbox credentials will be provided when your sandbox environment is provisioned current capabilities the sandbox environment currently supports ✅ dedicated sandbox account ✅ dedicated sandbox credentials ✅ dedicated sandbox api key ✅ salesforce integration testing ✅ api testing ✅ subscription replication ✅ product configuration replication ✅ isolated user contributed content ✅ mfa authentication ✅ parallel production and sandbox operation current limitations \ limitation \ \ details \ single sign on (sso) sandbox environments currently support password and mfa authentication only sso is not available sandbox reset there is currently no one click reset mechanism copying production content content cannot be copied from production into sandbox sample data synthetic or demo profile data is not available user synchronization changes to production users are not automatically mirrored to sandbox users sandbox capacity sandbox environments are provisioned with 1 service user and 1 web user and are intended for testing purposes only frequently asked questions can i use production and sandbox at the same time? yes production and sandbox environments operate independently and can be used simultaneously can i use sso in a sandbox? no sandbox environments currently support password and mfa authentication only can i generate synthetic or demo data? no sandbox environments use the same altrata profile data available through your subscription synthetic data is not currently supported can production content be copied into a sandbox? no this option is not available can multiple users test in a sandbox? sandbox environments are initially provisioned with one service user and one web user testing that requires user contributed content should be performed using the sandbox web user if your testing requirements extend beyond the standard allocation, contact your altrata representative to discuss your requirements