Skip to navigation

Deploy Revenue configuration for a Revenue-only customer

View as Markdown

Learn how to deploy Zuora Revenue configurations for a Revenue-only customers. The source tenant is a Revenue tenant, and the source-tenant connection uses OneID-based OAuth credentials.

  • Create a source tenant by using OneID-based OAuth credentials. Authentication for adding a source tenant from the Revenue UI always uses OneID-based OAuth client credentials. For more information about the source-tenant workflow, see Create a source tenant for deployment​.
  • Configure the Revenue role privileges required to open Deployment Manager and use the Revenue components.​
  • Ensure that the Revenue-enabled permission is assigned when Revenue components are not displayed in the Select screen.​
  • Select the correct OneID environment when creating the source tenant. The supported environment values are represented in the source-tenant flow as Stage, Pre-production, Sandbox, and Production.​
  • Confirm that the source and target tenants use compatible environment and authentication configurations.​
  • ​Confirm that Labels and other parent dependencies are available before deploying dependent components.
  • Add a Revenue source tenant by using the OneID client ID and secret for the intended environment.
1

​​Sign in to the Zuora Revenue tenant.​

2

From the Revenue interface, navigate to Data Interface Menu > Deployment Manager.

3

Click + New.

4

Provide a Deployment Name and an optional Description.

5

Select a Source Tenant and click Next.

6

Select the environment that matches the OneID endpoint for the source tenant. Do not use a production OneID endpoint when creating a sandbox source tenant.​

7

Select the Revenue components to compare and deploy.​

8

Compare the source and target tenants. Resolve missing or incompatible dependencies before deployment.

9

Verify and Deploy the selected Revenue configurations.​

10

Click Confirm, and confirm the Email notification.

11

Click Start Deployment.

Review View Logs and the History page after deployment.​