Welcome to the Zuora February 2014 Release (R173, R173.1). This release includes new features, enhancements, resolved issues, and improvements to the Knowledge Center.
|Environment||Current product version||Release date||Current WSDL|
|Production||R173.1||February 28, 2014||53.0|
|API Sandbox||R173.1||February 25, 2014||53.0|
See Version Information for more version information.
We are now calculating the Total Contract Value (TCV) metric using full Monthly Recurring Revenue (MRR) values, no matter what day of the month a subscriptions ends on. We've changed this logic to better handle subscriptions that start on the last day of a month and end on the last day of a month with fewer days. For example, a subscription starting on March 31st and ending on June 30th.
Previously, for these rare cases, Zuora treated the final month as slightly less than a full month, and prorated the MRR for that month down. This was resulting in slightly lower than expected TCV values.
Existing TCV values will not change automatically, but from this release all calculations of TCV for new subscriptions and amendments will use the enhanced logic. If your business logic relies on the TCV metric, you may notice a small difference in these values.
See the Total Contract Value page for more information.
Zuora 360 Real-time Sync is available to Zuora tenants in Limited Availability. Contact Zuora Support to request Real-time Sync to be enabled on your ApiSandbox or Production tenant.
Real-time Sync monitors record changes in Zuora and automatically synchronizes the changed records to Salesforce once the number of record change events reaches the configured threshold.
Currently, Real-time Sync is available only to customers who have Zuora Enterprise Edition and Salesforce Professional Edition with API Access (or higher).
See Real-time Sync for detail information about Real-time Sync.
For Recurring Syncs, including Schedule Sync and Real-time Sync, you can specify which types of sync events trigger an email notification.
The configuration options for email notifications are:
For other types of syncs, such as On-demand Syncs, email notifications are sent after all sync operations.
See Synchronize Data from Z-Billing for information on how to configure email notification for Recurring Syncs.
When you create or edit a Hosted Payment Method page or a Hosted Checkout page, you can specify the display order of the input fields on the hosted page.
We’ve enhanced the default display on the Accounting Period List page to show the current Accounting Periods on top, without any scrolling needed. In the user interface, there is a new default view called Current and Past Periods, which allows you to filter out all future accounting periods and focus on the current accounting period, followed by the previous accounting periods.
See Set Up Accounting Periods for more information on this new default view.
We have created a new data source for Chart of Accounts called Accounting Code.
We also extended the Invoice Item, Invoice Item Adjustment, Product Rate Plan Charge, and Rate Plan Charge data sources to reflect the new accounting code objects:
See Accounting Code Data Source for more information.
We now support custom fields for Accounting Codes. You can create up to 50 custom fields, as well as edit, remove, and view them through Z-Finance > Manage Custom Fields > Accounting Code Fields. You can also view the custom fields through the data sources.
See Manage Custom Fields in Z-Finance Accounting Codes for more information.
We have created a new setting called Do not allow blank Accounting Code, under Z-Finance Settings > Manage Accounting Codes that does not allow blank accounting codes when configuring accounting codes on credit balance, payment method, tax code, and product rate plan charge.
Transactions, such invoices and payments can still be created with a blank accounting code if it is in your existing configurations. To avoid this, go through all the configurations to make sure you have configured the accounting code correctly.
See Assign Accounting Codes for more information.
You can now restrict access to the Zuora Platform user interface and API by specifying the allowable IP address ranges on custom Zuora Platform User roles. This extra level of security prevents users who are outside the allowable range from accessing Zuora.
Previously, allowable IP address ranges could only be specified on the Zuora Platform Standard User role.
As of this release, we are enforcing the UI Access and API Write Access permissions that exist on Allowable IP address ranges for standard Platform user roles as well. Zuora recommends that you check each IP address range that you have defined and if necessary, update the restriction to apply to the Zuora UI, API, or both. For example, if you have defined IP address ranges for the Zuora user interface, verify that your restrictions apply only to UI Access and not to API Write Access.
This option adds a powerful security layer to Zuora user access. If access is required for certain users from all areas, consider all possible locations from which these users would log into Zuora, for example, office, home, and other areas. Work with your IT security officer to determine the setup that is appropriate for your tenant.
See Zuora Platform Roles for more information.
For Release 173, the WSDL version is 53.0. See The Zuora WSDL for information about downloading the current version.
Zuora CORS REST is now generally available.
Calls to selected CORS-enabled REST APIs can be made directly to Zuora via AJAX calls, using the Cross-Origin Resource Sharing (CORS) mechanism. This enables your customers to submit their credit card information directly to Zuora without it passing through your web servers.
See Zuora CORS REST for more information.
Terms and Conditions amendments created to change a subscription's TermType from Evergreen to Termed could not be activated due to an error:
"Missing required value:Initial Term"
This occurred in both the Zuora application and in SOAP API calls.
The issue was resolved in this release.
When a bill run was interrupted during processing, an incorrect "Total Customers Processed" value was displayed in the Zuora user interface and in the data export.
The issue was resolved in this release.
We made following changes to the structure of the Knowledge Center:
Please update your bookmarks as needed.
This maintenance release includes internal fixes.