Zuora 360 Version 5 Release Notes
These release notes provide a summary of new features, enhancements, and resolved issues in the Zuora 360 Version 5 releases. Version 5.0 is the major release, after which all the 5.X maintenance releases are based. Version 5.0 was released in Q3, 2018. To see previous release notes, go to Previous Zuora CPQ Releases.
Starting from January 2021, a dedicated release notes for Zuora 360+ is available. If you have enabled Zuora 360+, see Zuora 360+ Release Notes for the features, enhancements, and resolved issues of Zuora 360+.
Maintenance Release 5.9 (Release Date: 2021-2-3)
The 5.9 release includes the following resolved issue.
Resolved issue: DefaultPaymentMethodUpdaterTrigger class triggered on PaymentMethod creation
Previously, if you took the following steps:
- In your Salesforce account, navigate to a billing account that does not have a default payment method.
- Create a new payment method on this billing account.
You might find that the Default Payment Method checkbox of the new payment method was automatically selected. It was because that the Zuora.DefaultPaymentMethodUpdaterTrigger
class was triggered on the creation of the PaymentMethod object. This issue has been resolved now.
Maintenance Release 5.8 (Release Date: 2021-1-19)
The 5.8 release includes the following enhancement.
New text field added to SubscriptionProductChargeHistory object
The Product Rate Plan Charge Id (Zuora__ProductRatePlanChargeId__c
) text field has been added to the Subscription Product & Charge History (Zuora__SubscriptionProductChargeHistory__c
) object.
See New object types supported only when Zuora 360+ enabled for more information.
Maintenance Release 5.7 (Release Date: 2020-10-20)
The 5.7 release includes the following enhancement.
Support for OAuth in Zuora Central Sandbox
Zuora 360 now supports OAuth in both the US and EU Zuora Central Sandbox environments.
The URLs used to access the Zuora Central Sandbox are:
Maintenance Release 5.5 (Release Date: 2020-5-5)
The 5.5 release includes the following enhancements and resolved issues.
Resolved issue: Associated Accounts missing in synced Invoices/Payments/Refunds
Previously, when Invoices, Payments, or Refunds were synced through 360+ Sync to Salesforce, the associated Accounts might be missing due to the Billing Accounts' CRM ids being added later or being changed in Zuora. This issue has been resolved.
Maintenance Release 5.4 (Release Date: 2020-3-9)
The 5.4 release includes the following enhancements and resolved issues.
Support for the sync of the Default Payment Method flag in Payment Method
Zuora 360+ Sync now supports the sync of the Default Payment Method flag in the Payment Method object.
Resolved issue: Date/Time field values within a daylight saving time period shifted one hour backward
Previously, when you run ZOQL with ZApi, the Date/Time field values within a daylight saving time period shifted one hour backward in the returned records. This issue has been resolved.
Maintenance Release 5.3 (Release Date: 2019-9-4)
The 5.3 release includes the following enhancements and resolved issues.
Support for Tax Company Code and VAT Id fields of Billing Account
The Tax Company Code and VAT Id fields have been added to Billing Account. Zuora 360+ Sync will support the sync of these fields soon.
Support for new fields of Product
The following fields have been newly added to Product:
-
Category (
Category__c
) -
Zuora Created Date (
CreateDate__c
) -
Effective Start Date (
Effective_Start_Date__c
) -
Zuora Updated Date (
Updated_Date__c
)
Zuora 360+ Sync will support the sync of these fields soon.
Support for ZContact object
The ZContact object has been added to Zuora for Salesforce 360 package. Zuora 360+ Sync will support the sync of ZContact objects in the future.
Support for full-length BankTransferAccountName in PaymentMethod
Zuora 360+ Sync now supports the full length of BankTransferAccountName in PaymentMethod as on Zuora side.
Length of Country field in PaymentMethod increased to 255
The length of Country(Zuora__Country__c
) field in PaymentMethod has been increased from 2 to 255.
Resolved issue: inconsistent number of decimal places for Price and Overage Price fields between Zuora and Salesforce
Previously, the number of decimal places for Price and Overage Price fields in Subscription and Product Charge objects is 2 on Salesforce side and 4 on Zuora side. To be consistent with Zuora side, Zuora 360+ Sync has now supported 4 decimal places for Price and Overage Price fields also on Salesforce side.
Maintenance Release 5.2 (Release Date: 2018-11-21)
The 5.2 release includes the following enhancements.
Support Object Types for Subscription History
360+ Sync is an add-on to Zuora 360. If you want to have access to the feature, submit a request at Zuora Global Support.
Zuora 360+ Sync now supports the following object types for Subscription History:
- Subscriptions History
- Subscription Rate Plans History
- Subscription Product & Charges History
- Subscription Charge Tier History
See Data Connect Object and Field Mapping for more information.
Limitations are applicable to these object types. See Limitations in Data Connect for more information.
New Global Class GlobalRestHelper in Order Builder
A new global class GlobalRestHelper
is released in Zuora 360 5.2. This class provides methods to facilitate making REST calls to Zuora using the configuration in 360. You can use the getServerUrl()
method to retrieve the endpoint URL configured in 360. The mockRestHelper()
method allows the exposed REST methods to be mocked out for testing purposes. See GlobalRestHelper Class for more information.
Major Release 5.0 (Release Date: 2018-9-12)
The 5.0 release includes the following enhancement.
Support Object Types for Invoice Settlement
360+ Sync is an add-on to Zuora 360. If you want to have access to the feature, submit a request at Zuora Global Support.
Zuora 360+ now supports the following object types for Invoice Settlement:
- Credit Memo
- Credit Memo Item
- Credit Memo Part
- Debit Memo
- Debit Memo Item
- Payment Part
- Refund Part
See Data Connect Object and Field Mapping for more information.
Limitations are applicable to these object types. See Limitations in Data Connect for more information.