Production v. Pre-Production Environments
This article outlines the distinctions between Fullcast's production and preproduction environments. Preproduction environments are staging areas where Fullcast can be deployed and tested before being released to your production environment. These environments are ideal for testing scenarios such as exporting jobs to verify their configuration or testing motion policies to ensure their proper functionality.
Production environments are where Fullcast is used in real-world conditions. Effective planning for your production environment should be closely aligned with testing in the preproduction environment to ensure functionality.
Note: Planning should start in production from the beginning while you work on testing in the preproduction environment.
This article outlines the key differences and limitations of these environments.
Feature | Preproduction | Production |
Purpose | Used for testing | Serves as the live environment |
Records | A maximum of 100,000 records per entity. | No max |
Active Users | A maximum of 5 active users. | No max |
SSO Support | No SSO support. | SSO supported |
Schedule Jobs | Run scheduled jobs at least once a week. | Schedule jobs supported |
Cost | Cost associated | Cost associated |
Connection | Connection only to a customer’s Sandbox Salesforce environment. | Connection to a customer's Prod SF Env. |
Backup and Restore | No backup or restore capabilities | Backup and restore capabilities |
SLA Policy Availability | No SLA or ticket responses. | SLA Ticketing Process available. |
Performance Testing | No Performance Testing | |
Migration | No Migration | |
Export Jobs | Can test export jobs to ensure they function correctly. | Export jobs available. |
Testing Policies | Able to test all policies. | All Policies are available. |
Number of Plans | Currently, No Plan Limit |
Note: Fullcast cannot commit to SLAs regarding pre-production issues.