Sandbox Deployment

the altrata salesforce app can be deployed to a salesforce sandbox so teams can test and validate the integration before going live in production 🟢 recommended test in a sandbox first if you're migrating from a foundation app (boardex, relsci, wealth x), running a complex field mapping configuration or rolling out to a large user base sandbox testing lets you validate matching behavior without touching production data or user permissions what you can test in a sandbox a sandbox deployment supports the same core functionality as a production deployment you can install the managed package in a sandbox salesforce org authenticate using a sandbox specific service account (see below) validate matching behavior (bulk and manual) validate altrata data enrichment on records run advanced search and review results test page layout components and end user workflows this makes sandbox a good place to confirm your configuration works end to end before promoting it to production without affecting production metadata, users or downstream automations how sandbox authentication works sandbox authentication uses a separate service account from production the setup is identical to production authentication (username + password + api key on the altrata authentication tab see installation & configuration https //app archbee com/docs/gihmquksunpyi tpbn 89/ktmmtvduqyzkwelakvtru ) with two key differences the sandbox uses a dedicated service account distinct from production a username prefix convention identifies the account as a sandbox account everything else i e api key handling, account level configuration, permissions, entitlements matches production from the integration's perspective, your sandbox behaves like a separate instance of the salesforce app rather than a fully isolated tenant you'll receive sandbox credentials from altrata as a separate set from your production credentials if you don't have sandbox credentials and need them, contact your technical support representative do not share credentials between sandbox and production using the same credentials over more than one altrata salesforce app will result in failures important limitation shared data across environments ⚠️ sandbox is not a fully isolated tenant some data is shared between your sandbox and your production environment plan your testing accordingly specifically, the following are shared between sandbox and production relationships connections you add, edit, or modify in sandbox can appear in production lists lists created or modified during sandbox testing are visible in production user linked artifacts objects tied to salesforce users (e g , user specific saved searches) are not isolated use sandbox for functional and integration testing — installation, configuration, matching, data enrichment, page layouts, user workflows don't use sandbox to validate environment specific relationship or list data because those changes propagate when to use sandbox vs production goal use sandbox? validate installation and configuration steps ✅ yes test field mapping and match settings before bulk match ✅ yes confirm page layout components render correctly ✅ yes train admins on the integration ✅ yes test connections / relationships workflows ⚠️ with caution changes appear in production validate isolated list management scenarios ❌ no lists are shared with production user acceptance testing involving real user data ⚠️ with caution user linked artifacts are shared