Welcome to the Zuora February 2016 Release, R197. This release includes new Zuora features, enhancements, and resolved issues.
|Environment||Current Product Version||Release Date||Current WSDL Version|
|Production||R197.2||March 10, 2016||75.0|
|API Sandbox||R197.2||March 8, 2016||75.0|
See Version Information for more version information.
Features and enhancements related to Relationship Business Management solutions.
This feature is in Limited Availability. If you wish to have access to the feature, submit a request at Zuora Global Support.
Previously, you could only configure a notification to be sent out on the date when the subscription ends. You could not configure a notification to be sent out when each charge ends on a different date than the subscription end date.
Now Zuora supports a key dates notification for the charge end date. For example, you can get a notification callout for deprovisioning access to your products based on the end date of certain charges. This feature is available for email and callout notifications. You can select the number of days before or after the charge end date to send out a notification.
See Key Date(s): Rate Plan Charge for more information.
You can now change the service activation date and customer acceptance date when creating the following amendments through the PUT Subscription method:
You can now specify a subscription number when creating a subscription through the following methods:
You can now retrieve information about subscription amendments through the Zuora REST API with the following two new methods:
The following subscription management issues were resolved in this release.
Querying the Category field from the Product object to get the product category, Zuora SOAP API returned DefaultCatalog regardless of the value of the Category field.
This issue is now resolved. You must download WSDL version 75.0+ for the query to return the actual value for the product category. To view product categories from data source, Zuora now supports the Category field in the Product data source.
When you preview a subscription through the POST subscription/preview method if you created a required account custom field in Z-Billing, an error message was displayed. This error occurred no matter whether you set a value for this custom field in the request.
This issue is now resolved. Zuora now supports custom fields for providing customer account information in the POST subscription/preview method.
You can now configure your invoice templates to display usage charges in nested tables. For example, display usage charges in your invoices that are grouped and subtotaled by a custom field, such as Billing Code, and sorted in ascending order by Charge Date.
Use the following new mergefields to configure nested tables:
You must have the Individual Usage feature enabled to display grouped subtotals.
NestedTable mergefields are currently available only on Usage tables. See Group and Subtotal Usage Data in Nested Tables for more information.
You can now set the tax exempt value using the REST API. The following tax exempt fields were added to the REST account methods.
See the following articles for more information:
We will soon be making the following changes to accounting codes in the Zuora April release, R199.
Please ensure that your Zuora integration complies with these changes.
You can now retrieve the GL Account Name and GL Account Number of accounting codes through the REST API. The glAccountName and glAccountNumber fields are now returned in the response of the following REST API calls:
When you download the latest Zuora WSDL, the WSDL now includes your tenant-specific custom fields for the accountingPeriod and accountingCode SOAP API objects. You no longer need to worry about re-adding your custom fields each time you download the latest WSDL.
During 360 sync or cleanup operations of Accounts and Related Objects, an error occurred: INVALID_TYPE of sObject. This expected and benign error was a result of Zuora 360 attempting to delete a record that did not exist.
Now Zuora 360 gracefully handles the non-critical or expected errors and prevents the errors unnecessarily returned to users during sync and cleanups.
Features, enhancements, and release announcements for Zuora admins, Zuora integrations, and general information about Zuora APIs.
Email and callouts now have access to most data source fields associated with the notification event – including custom fields.
Now you can send richer emails with more personalized and specific data. For example, you can send an email before an invoice is due and include the details of the payment method the customer has chosen to settle with.
Before, you only had access to a limited set of predefined fields.
See Create and Edit Notifications for more information.
You can now send email notifications to the invoice owner of a subscription. For example, send a notification to the invoice owner letting them know of an upcoming subscription renewal. Before, you could only send subscription-related notifications to subscription owners.
Support for Invoice Owners is available on following notification events:
Amendment: Amendment Processed
See Create and Edit Email Templates for more information.
Z-Suite Integrations Release Notes January 27, 2016, v528 – Production Release.
Zuora no longer supports the Developer Console to test the Zuora REST API. Please remove any bookmarks you may have to https://apigee.com/ZuoraAPI/embed/console/CRESTAPI.
Try using other third party REST Clients, such as Postman or Advanced REST Client to test the Zuora REST API. Sample code is available with Zuora REST API reference articles.
Current WSDL version: 75
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.
Request queries can now explicitly set ISO-8601 compliant UTC output for fields of type dateTime.
When using the AQuA API Post Query (with WSDL 69 or later), you can specify the dateTimeUtc request parameter to true to ensure that the data set returned will have all dateTime values returned in ISO-8601 compliant UTC format.
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.