This article describes how to upgrade to Zuora 360 (Q4 2013 Titanium release), version 2.70 version.
The time required to upgrade Zuora 360 will depend on your upgrade path.
For example, between versions 2.1 and 2.4 we added fields to the Customer Account, Subscription, and Subscription Charge objects. In the first sync after upgrading, the sync session will migrate the data of all existing records in the Salesforce.com org to populate the new fields. Although this is an incremental sync, the amount of information to be processed will require a longer than normal sync time.
As a ballpark estimate, to go from 2.1 to 2.4 and migrate 75,000 billing accounts, 75,000 subscriptions, 150,000 subscription charges, and 75,000 invoices, the upgrade sync process would take approximately 100 minutes to complete. This is for a default installation of Zuora 360, version 2.4, without custom configurations.
The following types of Salesforce.com configurations can affect upgrade performance:
If you or one of your users has the Payment Sync permission and you have upgraded to the Zuora 360 package to version 2.4, the first regular sync will start a full sync of payments after the sync of billing accounts, subscriptions, subscription product charges, and invoices. Zuora recommends that you schedule the first full sync of payments to a time that will not affect your business processes.
To upgrade Zuora 360, determine the version of Zuora 360 that you have installed, then perform the upgrade process (if necessary).
The current version is 2.70. If you have an older version and wish to upgrade, contact Zuora Global Support to request an installation link, then follow the instructions below.
To upgrade Zuora 360, perform the following steps:
The following sections describe these steps in detail.
Note: The name of the menu item will be either Z-Billing or Zuora 360, depending on the version of Zuora 360 that you are upgrading from.
You must assign object permissions for the Payment and Invoice Payment objects to user profiles that you will use for the Z-Force sync.
Deletepermissions to the Refund and Refund Invoice Payment objects.
Select only the
Read permission for users who should only be able to view the objects synced from Zuora.
In Zuora 360 version 2.4, we added the following fields to Subscription object:
To use these fields in your sync processes:
Subscription Product & Chargeand
Related Listlayouts for Billing Account.
Next, you must assign object permissions for the for Payment and Invoice Payment objects to the Salesforce.com user used for the sync process. You can also assign read-only object permissions to the user profiles that need to view the objects that are synced from Zuora.
This is a controlled release feature. Contact Zuora Global Support to learn more about enabling this feature.
To assign object permissions:
Deletepermissions to the Payment and Invoice Payment objects.
Readpermission to the Payment and Invoice Payment objects.
Note that when you upgrade to Zuora 360 version 2.4 and assign the Payment Sync permission to a user, the first regular sync will start a full sync of payments after syncing the billing accounts, subscriptions, subscription product charges, and invoices. Because this process can take a significant amount of time, Zuora recommends that you schedule the first full sync of payments to a time that will not affect your business processes. See Time required for the Zuora 360 upgrade, above, for more information.
In Zuora 360 release 2.4, we added multiple new page layouts. If you are upgrading from version 2.4 or higher, you can skip this step. Otherwise, to use these layouts you must configure and assign them to user profiles.
The new page layouts are used by the payment and invoice payment sync process. This sync process is a controlled release feature. Contact Zuora Global Support to learn more about enabling this feature.
In the Q4 '13 release, we rebranded the product as Zuora 360.
To update the application labels:
Zuora Order Builder added these new classes in Zuora 360 version 2.4.
To use the new global Apex APIs in existing classes, you must change the version number of Zuora 360 to 2.4 or higher for this Apex class. This requirement is part of a feature of Salesforce.com that ensures backward compatibility of package releases. See the Salesforce.com documentation Managing Version Settings for Apex if you would like more information on this.
To change the package version number: