Xoxoday preserves client-specific customizations across every software release through version-controlled configuration layers and a mandatory customization impact assessment before each deployment cycle.
How Xoxoday Manages Customizations Through Releases
All client-specific configurations are documented, version-controlled, and stored in modular or configurable layers of the Xoxoday platform. This architecture separates core product code from organisation-level settings, which means product updates do not overwrite or reset the configurations your organisation has put in place. Before every release cycle, Xoxoday runs a customization impact assessment. This assessment identifies any configurations that might be affected by upcoming changes and flags them for review by the Product and Customer Success teams before the release goes live.What Happens When a Release Affects Your Configuration
In cases where an upcoming change does interact with an existing customization, Xoxoday takes a proactive approach. Your organisation receives advance notice, detailed release notes, and direct support through User Acceptance Testing (UAT) if needed. The team works with your organisation to propose backward-compatible alternatives, implement non-breaking configuration flags where possible, or provide dedicated support to restore functionality post-upgrade. For example, if your organisation uses a custom integration between Xoxoday and Darwinbox to trigger rewards based on HR milestones, and a platform update touches that integration layer, Xoxoday coordinates directly to ensure continuity before the release reaches production. Where feasible, customizations are built using APIs or feature flags rather than hard-coded overrides. This approach significantly reduces the risk of disruption and makes future upgrades smoother for organisations operating at scale.Governance and Continuity
These practices are governed by Xoxoday’s internal change control procedure and jointly overseen by the Product and Customer Success teams to ensure every release maintains operational continuity. The process is designed to catch conflicts early — not resolve them after the fact. This is especially relevant for organisations running Xoxoday alongside enterprise systems such as SAP SuccessFactors, Microsoft Teams, or Workday, where even minor platform changes can have downstream effects on connected workflows. Xoxoday’s release process is designed to absorb those risks before they reach your organisation.Learn more: Xoxoday Help Centre — Support
How Xoxoday handles platform integrations
Learn how Xoxoday connects with tools like Workday, SAP SuccessFactors, Darwinbox, Slack, and Microsoft Teams to keep reward workflows running across systems.
What is Xoxoday's change management process?
Understand how Xoxoday manages software updates, release cycles, and client communication throughout every deployment.