Revenue configurations with Deployment Manager
Use Deployment Manager to pre-validate, compare, validate, and deploy Zuora Revenue configuration between source and target tenants, ensuring consistent setup across non-production and production environments.
Revenue configuration deployment enables you to pre-validate, compare, validate, and deploy Zuora Revenue configuration from a source tenant to a target tenant using Deployment Manager. It is intended to help IT administrators, global services consultants, and implementation partners baseline environments and promote Revenue configuration consistently across development, sandbox, user acceptance testing, pre-production, and production environments.
- The access path and authentication method depend on the customer configuration. Order to Revenue (OTR) customers access Deployment Manager from Zuora Billing, while Revenue-only customers access it from the Zuora Revenue interface and use OneID-based authentication for Revenue source tenants.
- Revenue components have application-specific dependencies. Labels are a parent dependency for many Revenue components and should be deployed before dependent components.
- Deployment Manager pre-validates supported Revenue configurations on the Select screen. Pre-validation helps identify configuration issues early so you can resolve them before deploying the configuration.
Supported Revenue objects
Deployment Manager displays the following revenue objects on the Select screen:
- Accounting Setup
- Application
- File Upload
- Policies
- Policies - Cost
- Policies-Variable-Consideration
- Revenue Layout
- Revenue Report
- Setup
- SSP
Supported Revenue configurations
On the Compare screen, you can compare and validate a granular selection of configurations for each object.