The Production environment automatically replicates transactional data, such as approval processes, budgets, and contacts, into the Sandbox environment for testing and development purposes. Configuration and setup changes made in Sandbox must be manually published in the production environment by an admin or development resource to ensure the production environment is updated with the latest approved changes.
Certain data, such as user settings and roles, can be replicated bi-directionally between the Sandbox and Production environments, while other data, like photo albums and email history, are not replicated.
Production to Sandbox
Transactional data entered directly into the Production environment gets automatically replicated into the sandbox environment allowing Sandbox to have an up-to-date copy of the live production data for testing and development purposes. This data includes:
- Approval Process results (except dynamic steps)
- Budgets and Budget Security
- Employee Giving transactional data (gifts, hours, events, deductions, nominations, etc)
- Contact records and associations
- Custom Field data (not configuration)
- Discussions
- Friends and Family records
- Donor/Employee Profile updates
- Impact Reports
- Mailing Lists and associations
- Organizations
- Organization Status records
- Payees
- Payments
- Payment Type and related permissions
- Reports
- Watchlist Scanning settings
- Surveys
- Email/Letter Templates
- User Groups
Sandbox to Production
Configuration/setup changes to client accounts are all made in the Sandbox environment and must be published to the production environment either by an Admin user with the appropriate permissions, or an AC or Development resource.
Client Published Items:
- Custom Fields
- Approval Rules
- Website Styles
- Portal Layout – portlets, portal pages
- Request Mapping
- Employee Giving Programs – configuration, donor, and gift rules
- Eligibility Quizzes
- Conditional Field behavior
- Email Event and Reminder – proposal type language, behavior, and scheduling
- Grantmaker Primary Information
- Invitation Codes
- Impact Report – schedule and configuration
- Payment Preferences
- Proposal Types – sections, configurable text, geo and tax filters, active dates, etc.
- Support Area FAQs – Proposal Type configuration
Bonterra CSR Published Items:
- Client customizations – reports, feeds, and functionality
- Standard Data Resources – IRS/NCES/International lists, US Zip Code database
- Bridger Watchlists
- Standard System Functionality
Sandbox to Production and Production to Sandbox
The following items can be created/edited either in Production or Sandbox. They will be automatically created/updated in the corresponding environment:
- Donor/Employee Roles (Employee Giving Administration area)
- Editor Linking settings
- Employee Type (Employee Giving Administration area)
- Internal User - creation and configuration
- Internal User Roles
- Internal User Groups
No Replication
Certain items are not replicated between the Sandbox and Production environments. Those that may be of interest to clients are:
- Photo Album contents (Employee Giving)
- Email Event transmittal history
- File Uploads
- Eligibility Quiz responses
- Chart/Graph Portlet data
- Impersonation/Proxy data (Employee Giving)
- Password History
- Audit Trail data (Request, Organization, Payment, etc. logs)
Change Dependencies
Individual Publishing items can be published to production alone, without any downstream impacts on other areas of the system.
High-Level Publishing items have sub-components that must also be published in order to ensure that the High-Level Publishing item performs properly. High-Level Publishing only will publish the individual items that are directly included as part of the Proposal Type/Impact Report/Portal, etc.
What else do you need help with?
Not what you're looking for? Navigate to Understanding CyberGrants Sandbox and Production Environments
