Section 2: Deployment Tenants Flashcards
What is a ‘tenant’ in the Workday system?
A unique instance of the Workday system where data is securely segregated through password-controlled access.
Name the three types of production tenants.
Production, Sandbox, and Sandbox Preview.
What is the purpose of a ‘Production’ tenant?
The environment where a customer’s live, active data is managed and stored.
What is the purpose of a ‘Sandbox’ tenant?
To develop and test new features, customizations, and configurations before deploying to the Production tenant.
What is the purpose of a ‘Sandbox Preview’ tenant?
To preview upcoming Workday releases and understand additional functionality that will be available in the future.
What is the ‘GMS’ tenant?
Global Modern Services tenant; a demonstration tenant with sample, pre-populated data for a fictitious customer.
What is the ‘agpbaseload’ tenant?
Also known as the Implementation tenant; where you load customer’s data (also referred to as the empty or foundation tenant).
What is the ‘Customer Central’ tenant?
An auto-provisioned tenant that contains access to deployment tools. It sits over all nonproduction tenants to make deployment more efficient.
WDSetup
Source of factory default data for foundation recipes and configuration catalog.
Foundation Recipes
Organize the content in WDSetup into configuration packages. We
consolidate these packages into recipes based on product SKU and
countries.
During the Foundation tenant build, implementers can select
factory default data to load based on customer scope of
Advanced Load
Export, manipulate, and load data using XLSX, CSV, CSV ZIP, and
XML files.
Configuration Catalog
Migrate specific data sets of factory default data from WDSetup into
customer non-Production tenants. This includes certain reports and
other sets of configuration.
Customer Central
An Implementation tenant that serves as a central hub to secure access
to data migration tools. Use it in deployments and ongoing Workday
configuration management.
Workday Deployment Stages
Plan
Architect/Config
Test
Deploy
Foundation recipe
A fixed scope of setup and configuration tasks used to build the foundation tenant. The foundation recipe consists of configuration packages that contain the tasks needed to build the initial tenant.
Foundation Tenant Build Task
Uses foundation recipes to orchestrate the build process. One recipe at a time.
Foundation Tenant Build Order
Country
Industry
Fins
HCM
Collective Agreements
Foundation Tenant Activities for the DC Consultant
Seed the tenant with starting defaults from WDSetup
Load customer data
Validation steps to make sure tenant is actionable
Process for seeding tenant with factory default data
- Identify scope of work
- Foundation Tenant Build
- Verify Target Tenant
- Resolve Errors
Two types of Foundry tenants
- Medium enterprise
- WDSetup for everything else
Implementation types detail
Report to identify if the tooling supports the implementation component, either Advanced Load or iLoad
Data Sources for an EIB
Amazon Simple Storage
FTP/SSL
sFTP
Google Drive
Deployment tools for implementers only
Advanced Load
Change Tracker
Foundation Recipes
iLoad
Implementation Suites Summary
Migration Recipes
Tenant Compare
PACMAN for Phase X
Deployment Tools for Customers and Implementors
EIB
Config Catalog
Customer Central
OX 2.0
WDSetup
