Early Access Environment(EAE)
Updated
Introduction
Sprinklr’s Early Access Environment (EAE) is a dedicated, pre-production environment hosted in a separate infrastructure (AWS Germany) that mirrors your production setup - excluding customer data. It enables early validation of upcoming quarterly platform releases, allowing you to test new features and updates in advance. This proactive validation helps enable a smooth transition to production by identifying potential issues early, without impacting your live operations.
Why EAE Matters
Operational Assurance: For organisations relying on Sprinklr for critical operations like customer service, EAE provides a safety net to validate changes before they go live.
Tailored Testing: EAE allows you to test new releases against your specific configurations and integrations, ensuring compatibility and minimising surprises.
Confidence in Releases: By validating updates in advance, you gain trust in the stability and reliability of upcoming changes.
Key Benefits
Risk Mitigation: Detect and resolve issues before they affect production.
Release Stability: Facilitate smoother rollouts with minimal disruption.
Environment-Specific Validation: Test updates in a replica of your production setup.
Operational Efficiency: Avoid productivity losses due to unforeseen issues.
Increased Confidence: Validate features in advance, reducing uncertainty.
EAE and the Sprinklr Release Cycle
EAE is aligned with quarterly releases only, which include major updates and new features.
Release Type | Description | EAE Availability |
Quarterly Releases | Major updates with new features and fixes | Available 2 weeks before production release .
|
Note: Monthly and ad-hoc patches are not included in EAE. | ||
Setting Up EAE
Initial Setup (One-Time Effort)
Sprinklr will provision the EAE instance and assist in migrating your production configurations. Key setup steps include:
Connected Environments: Link production and EAE for configuration migration.
Manual Configurations (approx. 10%):
SSO Setup: Configure Single Sign-On manually.
Account Mapping: Use separate test social media accounts (to be provided by customer).
API Setup: Update endpoints or credentials if needed.
Voice Configuration: Set up test voice accounts and IVR numbers.
Custom Integrations: Coordinate with Sprinklr for integrations like Calabrio.
Ongoing Testing (Per Release)
Release Schedule: Follow the quarterly release calendar.
UAT Sanity Checklist: Collaborate with Sprinklr Services (MS/IC/Partners) to validate critical workflows using a predefined checklist.
Note: While all users are encouraged to test, a minimum “Sev0” checklist should be validated in EAE.
Frequently Asked Questions (FAQs)
Who uses EAE?
EAE is initially available to selected alpha customers, typically platform administrators, QA teams, and implementation consultants.
When is EAE used?
EAE is used two weeks prior to quarterly releases for early validation.
Does EAE replace internal testing?
No. EAE complements internal testing by providing an additional layer of validation.
How is EAE different from Sandbox/Staging?
EAE is for validating unreleased code. Sandbox/Staging is used for ongoing testing and training.
How long is EAE active?
EAE is continuously available but is most relevant during the two-week window before quarterly releases.
What is the scope of testing in EAE?
Focus is on validating critical workflows and configurations.
How are issues handled?
Issues reported during EAE are prioritized and resolved before the production release.
What support is available?
Dedicated support is provided for EAE participants during the testing window.
Can EAE configurations be pushed to production?
No. EAE is a one-way mirror of production and does not support reverse migration.
Will EAE be available in my hosting location?
Regardless of the location of a customer’s production partner, EAE will be hosted exclusively in AWS Germany.
What kind of data can I process in EAE?
Since EAE is intended solely for testing purposes, customers are advised to use dummy or non-sensitive data for all testing activities, as well as test integrations and accounts. No actual, production data should be loaded to the EAE.
Disclaimer:
Environment Location
Regardless of the location of the client's production partner, the staging/preproduction partner will be hosted exclusively in AWS Germany. This setup is fixed and non-negotiable to ensure standardised operations and compliance.
Data Usage Policy
Clients are strictly prohibited from using real or sensitive data in the staging/preproduction partner. This environment is intended solely for testing purposes, and the use of real data may compromise the integrity and security of the system. Clients are advised to use dummy or non-sensitive data for all testing activities.
Important Notes :
The staging/preproduction environment is designed to replicate production functionality for testing purposes only. It is not a substitute for the production environment.
Any issues arising from the use of real data in this environment will not be the responsibility of the service provider.
Clients must adhere to this policy to maintain compliance and ensure a secure and reliable testing process.