Welcome to the Zuora December 2015 Release, R195. This release includes new Zuora features, enhancements, and improvements to the Knowledge Center.
| Environment | Current Product Version | Release Date | Current WSDL |
|---|---|---|---|
| Production | R195.3 | December 28, 2015 | 73.0 |
| API Sandbox | R195.3 | December 28, 2015 | 73.0 |
See Version Information for more version information.
Zuora for Salesforce Quotes Q4 2015 Release Notes and Zuora 360 Q2 2015 Release Notes
Z-Suite Integrations Release Notes December 16, 2015, v517 – Production Release
Previously you could only define the subscription initial terms and renewal terms in months, or update the current terms in months. Now you have more options for the period types of the subscription terms:
You can also view the current term and current term period type on the subscriptions.
In the SOAP API, the InitialTerm field on the Amendment object is deprecated in this release. Use the CurrentTerm field to update the current subscription term instead. See Deprecated SOAP API items for more information.
The following table shows the new fields for REST API methods, SOAP API objects, and data sources.
| New Field | REST API Method | SOAP API Object | Data Source Object |
|---|---|---|---|
| InitialTermPeriodType | Get subscriptions by account Get subscription by key Create subscription Preview subscription | Subscription | Subscription |
| RenewalTermPeriodType | Get subscriptions by account Get subscription by key Create subscription Update subscription | Subscription Amendment | Subscription Subscription Version Amendment |
| CurrentTerm | Get subscriptions by account Get subscription by key | Subscription Amendment | Subscription Subscription Version Amendment |
| CurrentTermPeriodType | Get subscriptions by account Get subscription by key Update subscription | Subscription Amendment | Subscription Subscription Version Amendment |
| renewalSetting | Get subscriptions by account Get subscription by key Update subscription | ||
| termStartDate | Update subscription |
In the Zuora November 2015 Release, R194, we added the ability to define when charges end by using the Zuora UI and SOAP API. Now you can define and preview the charge end dates when creating subscriptions using the REST API.
The following fields are supported in POST subscription and POST subscription/preview methods:
See Create subscription or Preview subscription for more information.
In the Zuora November 2015 Release, R194 and the Zuora October 2015 Release, R193, we added the ability to create Update Product amendments through the Zuora APIs even if a future-dated Remove Product or Update Product amendment already exists on the subscription. Now you can also create Update Product amendments from the Zuora UI with a future-dated Remove Product or Update Product amendment on the subscription.
See Update a Product on Subscription with Future-dated Updates and Update a Product on Subscription with a Future-dated Remove for more information.
You can now retrieve detailed information about expired subscriptions using the REST GET subscription by key method. This GET subscription method is now more consistent with the SOAP query call on the Subscription object.
See Get subscription by key for more information.
Zuora now supports the ability to distribute revenue on a specific recognition date. You can distribute revenue using:
The following options are available for distributing revenue on a specified recognition date:
| REST API Distribute Revenue on Specific Date | Mass Updater Update Revenue Schedules | Zuora UI Distribute Revenue on Specific Date |
|---|---|---|
| specific date (delta fixed amount) | Specific Date: delta amount | Fixed amount |
| specific date (delta percent total) | Specific Date: delta percent total | Percentage of total revenue |
| specific date (delta percent undistributed) | Specific Date: delta percent undistributed | Percentage of total undistributed revenue |
You can create milestone-based rules from either Billing-based or Custom Revenue Rule Models.
This feature is available with the Nine Edition and with the Revenue Recognition Add-on for other Zuora Editions.
Authorize.net is implementing a change to use Akamai network technology. Because Akamai uses an extensive network of servers and IP addresses, traffic is routed faster and more efficiently. All connections to Authorize.net will go through Akamai first.
Zuora is supporting this effort for its Authorize.net customers. The change has the following effect:
To learn more about Akamai, see Akamai FAQs on the Authorize.net website.
For more information about accessing the Authorize.net test and production environments from Zuora, see Authorize.net Gateway.
Your tenant ID is now displayed as read-only text on the Edit User Profile page for information purposes. In some situations, when you contact Zuora Support with an issue, the person helping you may ask you to provide the tenant ID.
To see the new read-only Tenant ID field, navigate to Settings > Personal Settings and select Manage Your Profile.
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. The current WSDL version is 73.
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 customer-reported feedback:
This release includes internal fixes.
This release includes internal fixes.
