Knowledge Center

Knowledge Center > What's New > Previous Zuora Releases > 2016 New Features > May 2016 Release Notes

May 2016 Release Notes

Welcome to the release notes for the Zuora May 2016 Release, R200. This release includes new Zuora features, enhancements, resolved issues, and improvements to the Knowledge Center.

Current Product Version

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 R200.2 June 2, 2016 76.0
API Sandbox R200.2 June 1, 2016 76.0

See Product Versions and Release Dates for more information.

Billing and Payments

Display Tax Code on Invoices

You can now display tax code on invoices by adding the new InvoiceItem.TaxCode merge field to your invoice template. This enhancement gives you more flexibility in summarizing tax information on invoices.

See Merge Fields for Invoices for more information.

Finance

Manage Your Chart of Accounts Using the REST API

You now have access to a full set of REST API calls to manage your chart of accounts. The following calls are available:

Platform

Attachments on Subscriptions, Accounts, and Invoices

Now you can attach documents to accounts, subscriptions, and invoices to capture additional information. Example attachments could be a purchase order, a tax exemption document, or an ownership transfer form.

Attachments are files of various formats. They are uploaded and associated with a specific account, a subscription, or an invoice in the Zuora UI or through the Zuora REST API.

APIs

SOAP API

Current WSDL version: 76

See Zuora WSDL for information on how to check your version and download the latest version.

SOAP API Change History

See Zuora SOAP API Version History for a summary of updates made to the SOAP API in recent Zuora releases.

Date Field Changes as of WSDL 69

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.

Knowledge Center

We have updated the following Knowledge Center articles based on your feedback:

  • Invoice Subscriptions to Different Accounts: Added a "Limitations" section to explain that even after transferring the ownership of a subscription or its invoices, any associated revenue will continue to use the customer account of the original owner.
  • BillingPreviewRun SOAP object: Added a "Field Descriptions of the CSV Output File" section to describe the object output.
  • Invoice Adjustment: Added the following note to invoice adjustment related articles in the Knowledge Center:

    Invoice Adjustment is deprecated on Production. Zuora recommends that you use Invoice Item Adjustment instead.

  • Calculating Total Amount with Partial Period Proration: Provided formulas and examples about how to calculate charge amount and prorated amount for recurring charges.

  • HMAC Signatures REST API: Clarified the <field_n> field description and provided all the REST API methods that need to include the <field_n> field in the request body of POST HMAC Signatures method. 

  • Zuora CORS REST: Added the missing but supported CORS-enabled REST API method, RSA Signatures.

  • amend() SOAP call: Added a note in the GenerateInvoice and ProcessPayments fields of the AmendOptions object:

    Even if you do not include this field in the amend() call, Zuora still parses this field with the default value, true, when processing the amend() call. If you do not want to generate the invoice or collect payments after creating the New Product or Term And Condition amendment, set the value of this field to false in the request.

  • Update Basic Information of a Summary Journal Entry: Corrected the formatting of the example JSON request.

Last modified
21:39, 8 Aug 2016

Tags

Classifications

(not set)