Vision
Deployment Manager Known Facts and Limitations
Known facts
The Deployment Manager has the following behaviors by design concerning Workflow, Custom Objects, Notifications, and General facts:
Always deploy Custom Fields prior to deploying Chart of Accounts and Invoice Templates.
It is recommended that Notifications and Workflow be deployed as separate components without any other deployment components for best results.
Workflow
- When the source tenant and the target tenant have workflows with the same name but different versions, the result of deployment is an incremental active version of the same workflow in the target tenant. Version increment is based on the last version present in the target. For example, if a workflow is present in both the source and the target, the source has versions 0.0.3, 0.0.2, and 0.0.1, while the target has versions 0.0.2 and 0.0.1. Following deployment, an incremental version of 0.0.3 will be created regardless of whether the user selected only 0.0.2 or 0.0.1.
- When a workflow is configured in the source tenant but missing in the target tenant, the result of deployment is a new workflow created in the target tenant with the same version as present in the source tenant.
Custom Objects
- If a custom object is present in both source and target tenants, and the migration flag (
enableRecordMigrationfield) is enabled in the source but not in the target, the flag will be enabled in the target but the records will not be migrated by the deployment. - The provisioning for Custom Objects limit in the tenant is 10. The deployment will not succeed when this limit is reached in the target tenant, the deployment will not succeed.
Notifications
- If there are notifications with the same name, the system will only deploy the Notification that is read first in the backend, other Notifications with the same name will not be deployed.
General
- The Deployment Manager does not delete the function for objects configured in the target tenant.
Limitations
The Deployment Manager currently has the following limitations:
- Indexed custom fields cannot be updated to non-indexed; non-indexed custom fields cannot be updated to indexed.
- Accounting periods are not supported.
- Revenue platform is not supported.
- NoAE Notifications are not supported.
- Comparing the content of billing document templates is not supported.
- Custom fields associated with Accounting Codes cannot be deployed in the target.
- The following settings are not supported:
| Section | Settings |
|---|---|
| Administration | Security Policies |
| Manage User Roles | |
| Manage Users | |
| External SMTP | |
| AQuA Stateful Time Offset | |
| Billing | Download the Zuora WSDL |
| Callout Options | |
| Payments | Payment Method |
| Setup Payment Gateway | |
| Setup Payment Method Updater | |
| Setup Hosted Pages | |
| CIT/MIT Configuration | |
| Commerce | Synchronize Salesforce.com Data |
| Configure Salesforce.com Quote Templates | |
| Manage Checkout Pages | |
| Finance | Configure Accounting Codes |
| Manage Currency Conversion | |
| Reporting | Manage Datasources |
| AQuA job finder | |
| Connect | Lockby Ruby |
| Disputes | |
| Collection Window | |
| Advance Payment Retry/Configurable Payment Retry | |
| Notes | |
| Statement Generator | |
| Advance Payment Manager |
- Zuora settings APIs in Billing are not supported with the public APIs for the following Parameters:
| Parameter | Fields |
|---|---|
| Charge Types / Models | High Water Mark Tiered Pricing |
| High Water Mark Volume Pricing | |
| Multi-Attribute Pricing | |
| Pre-Rated Per Unit Pricing | |
| Pre-Rated Pricing | |
| One-Time and Recurring | |
| Subscription Order Settings | Invoice Past End of Term |
| Contract Renewal | |
| Implementation Period | |
| Increase Price Renew Subscription | |
| Price Increase Percentage |