Concept: Strategic Sourcing Ad-Hoc Sandbox Refreshes
Overview
Ad-Hoc Sandbox Refresh enables joint Workday and Strategic Sourcing customers to refresh their Strategic Sourcing sandbox environment on demand alongside a Workday tenant refresh. The refresh operates on a fixed 1-to-1 relationship between a Workday tenant (Implementation or Sandbox Preview) and a Strategic Sourcing company.
Workday acts as the source of truth for integrations, including single sign-on (SSO), webhooks, user provisioning, and supplier master data. Raising a tenant refresh request on the Workday side automatically triggers a paired backup and restore operation that populates the mapped Strategic Sourcing sandbox with a copy of your Strategic Sourcing production tenant data.
Business Benefits
- Like-for-Like Testing: Matches configuration and data across non-production environments to test features, integrations, and configuration changes against production-matched data.
- Training and Demonstrations: Enables realistic demonstrations and training in an environment reflecting live configurations.
- Data and Integration Continuity: Eliminates Strategic Sourcing data loss and broken integration states (such as user provisioning and webhooks) caused by unsynchronized tenant refreshes.
- On-Demand Scheduling: Allows administrators to request refreshes as needed without manual environment realignment.
Architectural Scope and Limitations
- Paired Operation: The refresh is paired, not bi-directional. Configuration and data move strictly from your Strategic Sourcing production tenant into the sandbox.
- One-to-One Mapping: One Workday tenant maps to exactly one Strategic Sourcing company. An import always loads into an existing sandbox and cannot create a new sandbox or split mappings.
- Deferred Capabilities: This phase does not support Strategic Sourcing Preview or Implementation tenant types, Object Transport (OX) workflows, or automated weekly refreshes with exception handling.
Environment Availability During Refresh
During a refresh, environment access varies by stage:
Stage | Source Tenant | Destination Tenant |
|---|---|---|
Export and Backup | Fully available | Reachable, but should not be accessed |
Purge | Fully availableFully available | Unavailable |
Import | Fully available | Unavailable; Strategic Sourcing sandbox in maintenance mode |
Complete | Fully available | Available, reflecting imported data |
Data Behavior During Refresh
A refresh replaces specific production data, preserves environment-specific sandbox configurations, and clears temporary or environment-coupled records.
Copied from Production
The following production data overwrites existing sandbox data in these areas:
- Sourcing and Events: Sourcing events (RFPs), bids, bid responses, line items, price sheets, award scenarios, and analysis.
- Projects: Projects, project types, layouts, related links, tasks, and milestones.
- Contracts: Contracts, contract documents, revisions, clauses, clause templates, renewals, and auto-renewal cycles.
- Documents: Requested documents, response documents, questionnaires, responses, and evaluations.
- Suppliers:Supplier companies, contacts, classifications, categories, groups, onboarding forms, performance, and risk data.
- Attachments and Files: File attachments stored against copied records.
- Users: User accounts, buyer and supplier profiles, teams, departments, and access groups.
- Configuration Data: Custom fields, spend categories, approval flows, approval groups, automation rules, saved views, currencies, and payment terms.
- Collaboration: Comments, notifications, and activity history.
Preserved on Sandbox
To keep the sandbox reachable and distinct from production, these are preserved and not overwritten:
- Single Sign-On (SSO): SSO settings and tenant mapping.
- Web Addresses: Sandbox subdomains and public sourcing site URL.
- Company Identity: Sandbox company name, logo, and icon.
- E-Signature Connections: Account links for DocuSign and Adobe Sign.
- Integration Credentials: API keys, OAuth secrets, and external integration connections.
- Concierge Configuration: Business Purchase and Concierge configurations.
- Lookup & Reference Data: Lookup field sources, country/payment-method reference data, and sandbox feature enablement.
- Email Logs: Supplier email logs and suppressed-email lists.
Cleared or Regenerated
These are cleared during import and rebuilt or reconnected post-refresh:
- Third-Party Integration Documents: Evisort, Adobe Sign, and DocuSign agreement and document records.
- External Enrichment Results: Dun & Bradstreet, EcoVadis, OneTrust, and sanction-screening results.
- Workday CLM Data: Workday Contract Lifecycle Management records.
- Sessions and Tokens: Active sessions, SSO tokens, and personal API session tokens.
- Logs: Audit logs and authentication logs.
- Search Caches: Search indexes and caches (rebuilt post-import).
User and Supplier Access Post-Refresh
- Disabled Status: Users brought over from production for the first time arrive in a disabled state and must be manually enabled before signing in.
- Supplier Protection: Supplier access is disabled post-import, and no emails are sent during export or import. A sandbox refresh never contacts live suppliers.
- Email Addresses: User email addresses remain identical to production and are not masked or rewritten.