Welcome to the Zuora October 2015 Release, R193. This release includes new Zuora features, enhancements, resolved issues, and improvements to the Knowledge Center.
|Environment||Current Product Version||Release Date||Current WSDL|
|Production||R193.2||November 9, 2015||71.0|
|API Sandbox||R193.1||November 2, 2015||71.0|
See Version Information for more version information.
Z-Suite Integrations Release Notes v482, Release September 24, 2015
You can now create an Update Product amendment even if there is already a future-dated Update Product amendment on the subscription. You no longer need to revert the future-dated amendment before creating your new amendment.
Currently this enhancement is only supported through the Zuora APIs. For SOAP API, you can use the new SpecificUpdateDate field on the Amendment object. For REST API, you can use the new specificUpdateDate field in the Update Subscription method.
Previously taxes could only be calculated based on the sold-to contact of the subscription owner. Now taxes can also be calculated based on the sold-to contact of the invoice owner. All the account information of the specified contact, including tax exemption, value-added tax (VAT), any applicable company codes, and other tax information is included in the tax calculation.
You might choose to calculate taxes based on the account information of the invoice owner if the invoice owner is the reseller and the subscription owner is the end user.
You can define this tax calculation rule using the Calculate taxes using information from Customer Account of: setting from Settings > Z-Billing Settings > Billing Rules. By default, the subscription owner is used to calculate taxes.
See Define Billing Rules for more information.
Previously notifications for key dates (introduced in September, 2015) were available only for subscriptions with the following statuses: pending activation, pending acceptance, or active. This release adds key dates notifications for subscriptions with a canceled status.
See the September 2015 Release Notes for more information about key dates notifications.
You can now update custom fields on expired subscriptions from the Zuora UI and from the SOAP API.
The following objects allow updates on custom fields when a subscription has a status of expired:
A subscription becomes expired when creating an amendment and the originating subscription is versioned. To edit a custom field on an expired subscription, navigate to the expired subscription. From the Basic Information and the Product & Charges section, click Edit Custom Fields that follows the list of custom fields.
The List Price Base on a Product Rate Plan Charge allows you to specify the term a recurring charge is based on. The List Price Base field was added to the Product Rate Plan Charge in the May 2015 release, R188. Starting in this October 2015 release, R193, the List Price Base values in Zuora are synced to Zuora 360 when you perform Product Catalog Syncs.
The Mass Updater is now generally available to all Z-Finance users. The Mass Updater is a tool that allows you to easily perform mass actions in Zuora. Instead of performing the same action over and over again, you simply put all the data in a single
.csv file and upload that file to the Mass Updater. The Mass Updater then processes the actions asynchronously and returns a response file containing information about the outcome of each action. You can perform mass actions through the Zuora UI or REST API.
We currently support the following mass actions:
See Mass Updater for more information.
Please read this important note before using WSDL version 69 or later. The current WSDL version is 71.
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.
The following issue was resolved in this release.
Customers were sometimes incorrectly invoiced past the end of their subscription term even when the Invoice Past End-of-Term when Auto-Renew is OFF? setting was set to No. This issue occurred when a segmented charge ended before the subscription term end date, the billing period ended after the term end date, and the invoice target date was set earlier than the segmented charge end date.
This issue is now resolved. Subscriptions are no longer invoiced past the end of their term when the Invoice Past End-of-Term when Auto-Renew is OFF? setting is set to No.
See Define Default Subscription Settings for more information on this setting.
We have updated the following Knowledge Center articles based on customer feedback:
The Refund create() call will return Success in the response along with the Refund ID regardless of the gateway response. When processing a refund the create() call refers to the successful creation of the Refund object. It is not an indicator that the payment gateway processed the refund successfully.