Welcome to the release notes for the Zuora June 2016 Release, R201. This release includes new Zuora features, enhancements, resolved issues, and improvements to the Knowledge Center.
The following table shows the product versions currently released on the Zuora Production and API Sandbox environments.
| Environment | Current Product Version | Release Date | Current WSDL Version |
|---|---|---|---|
| Production | R201.2 | June 30, 2016 | 77.0 |
| API Sandbox | R201.2 | June 30, 2016 | 77.0 |
See Product Versions and Release Dates for more information.
You can now define the following number formats by setting the default prefixes in Z-Billing settings:
For example, you can use the initials of the company name as the prefix. If you use ZUO as the default prefix for subscription numbers, when creating a subscription, the subscription number is named with the prefix ZUO, such as ZUO00000062.
The newly defined prefixes are used when creating a subscription or a subscription amendment. The existing subscription numbers, charge numbers, and amendment numbers will not be affected by your newly defined prefixes.
To define number formats, navigate to Settings > Z-Billing Settings > Define Numbering and SKU Formats.
See Define Numbering and SKU Formats for more information.
The Key Date(s) notification for Rate Plan Charge Start Date is in Limited Availability. If you already have Key Date(s) notification for Rate Plan Charge enabled, this notification is available automatically. Submit a request at Zuora Global Support only if you wish to have access to Rate Plan Charge Key Date(s) Notification.
Zuora now supports a key dates notification for the rate plan charge start date. You can configure an email or callout to send a notification on a charge effective date.
Navigate to Settings > Z-Billing Settings > Setup Profiles, Notifications and Email Templates to configure notifications.
See Key Date(s) | Rate Plan Charge Start Date for more information.
Previously, you could only nest tables for usage charges and you were not allowed to have more than one level of nesting. Now you can also group and subtotal invoice items in nested tables. Zuora supports multi-level nested tables within the invoice items or usage charges table. You can organize charges logically in order to display complex invoices more clearly to your customers.
See Grouping and Subtotal Functions in Nested Tables and Examples: Using Nested Tables in Invoices for more information.
The new InvoiceItem.IsNew merge field gives you more flexibility in displaying new invoice item charges. The merge field lets you display only charges that were not displayed in the most recently posted invoice. You can use this merge field to do the following:
Vision
NestedTable:GroupColumn merge field.TableSort merge field.See Merge Fields for Invoices for more information about the InvoiceItem.IsNew merge field.
You can include Mandate ID in invoices by adding the new Account.PaymentMethodMandateId merge field to your invoice template. A mandate is a signed authorization for UK and NL customers. This merge field is used only for the direct debit payment method.
See Merge Fields for Invoices for more information.
You now have access to a full set of REST API calls to manage accounting periods, further simplifying your general ledger integration with Zuora. The following calls are available:
Previously, if you configured a subscription owner to be different from the invoice owner, segment values for invoice transactions would come from the invoice owner, and segment values for revenue transactions would come from the subscription owner.
Now you can choose which owner the segment values come from by using the following two new settings:
The settings are located in Settings > Z-Finance Settings > Configure Segments.
See Segments for more information.
Current WSDL version: 77
See Zuora WSDL for information on how to check your version and download the latest version.
See Zuora SOAP API Version History for a summary of updates made to the SOAP API in recent Zuora releases.
Please read this important note before using WSDL version 69 or later.
In WSDL 68 and earlier, 56 Zuora SOAP API date fields are treated as dateTime fields. As of WSDL 69, Zuora will treat these fields as date only fields. These fields are no longer compatible with dateTime values. Date and dateTime values in WSDL 69 are now the same as date and dateTime values in the Zuora application.
Before downloading and using WSDL 69, check to see if your SOAP integration passes or receives dateTime values to or from any of these fields.
The AQuA API is also affected by these date field changes. If you use the AQuA API, you must review the date field changes and take the appropriate action.
See Date Field Changes in the WSDL for more information.
We have updated the following Knowledge Center articles based on your feedback:
The panHash token is required in the payment transactions. You must select the Verify new credit card checkbox in the configuration so that a panHash token is generated by NETS during the payment method verification.
The Shopper Reference token is required in the payment transactions. You must select the Verify new credit card checkbox in the configuration so that a Shopper Reference token is generated by Adyen during the payment method verification.