Welcome to the Zuora May 2014 Release (R176, R176.1, R176.2). This release includes new features, enhancements, resolved issues, and improvements to the Knowledge Center.
|Environment||Current Product Version||Release Date||Current WSDL|
|Production||R176.2||May 29, 2014||56.0|
|API Sandbox||R176.2||May 28, 2014||56.0|
See Version Information for more version information.
Zuora is now integrated with the third party tax engine, Avalara, which allows you to easily calculate and report tax rates for multiple tax jurisdictions using up-to-the-minute tax rate data. Avalara is especially useful if you have nexus in multiple tax locations, as it helps you to avoid updating thousands of tax rates every month.
By connecting your Zuora tenant to Avalara you can:
To find out more, see our new Avalara Integration guide.
This feature is in Controlled Release. Submit a request at Zuora Global Support to get this feature enabled for your tenant.
A new permission for subscription and amendments is now available:
Users with this permission can do the following:
|New permissions are selected by default. Your tenant administrator must explicitly remove new permissions from users. |
Users without this permission can only view and download. An error message is returned if Zuora platform users and Zuora API users try to perform actions for which they do not have permission.
See Z-Billing Roles for more information.
We have enhanced the user interface text for the usage import notification. The message has been changed from:
For usage import results, please setup the appropriate notification or use the appropriate API call.
For usage import results, please setup the appropriate Import Notification or use the appropriate API call.
A new role category for Z-Commerce was added in Manage User Roles under the Administration Settings. On the Manage Roles page, you can select a new drop-down option, Z-Commerce, to manage permissions for the Z-Commerce users.
Under the Z-Commerce category, there are two new roles:
Users in the Z-Commerce Admin User role can:
Users in the Z-Commerce Standard User role can:
When this is rolled out as part of R176, all users will receive the Administrator Role, by default, to preserve previous behavior.
See Z-Commerce Roles for more information.
A new permission, Manage 360 Sync, was added to allow a user role to modify Salesforce credentials, sync, or cancel syncs between Zuora and Salesforce.
See Z-Commerce Roles for more information.
A new permission, Allow Clean Up, was added to allow a user role to run sync cleanups of the Accounts and Product Catalog between Zuora and Salesforce.
Starting in this release, the users with the "Allow Clean Up" permission can run Product Catalog Clean Up. You no longer need to contact Zuora Support to enable the Product Catalog Sync operation.
See Z-Commerce Roles for more information.
On-demand usage rating was enhanced. The UsageRecordRatingOption field available on the RatePlanCharge object is now also available on the ProductRatePlanCharge object.
This new field is available in WSDL version 56.0.
See ProductRatePlanCharge for more information about the newly added field.
When the event processing latency of Real-time Sync event is too high, Real-time sync is automatically switched to Turbo Sync. For example, when a bulk operation, such as Bill or Payment Run is performed, Real-time Sync will automatically switch to Turbo Sync and save your tenant's API limits. When a switch from Real-time Sync to Turbo Sync happens, you get a message in UI and a log entry in Sync History.
See Real-Time Sync for detail information about this enhancement.
We have upgraded to CyberSource Simple Order API version 1.97. This contains many enhancements, including support for ACH payments through Telecheck.
See CyberSource Payment Gateway for more information.
We have added a recurring flag to CyberSource for the Atos processor. Select this option only when the Commerce Indicator is set to Recurring.
We now support non-reference refunds for the CreditCardReferenceTransaction payment method. The CyberSource Token Gateway must be enabled the Zuora tenant administrator.
We have added a recurring flag to Global Collect. When recurring is enabled, the recurring flag is sent to Global Collect.
The new Gateway field was added to the Payment SOAP API object. This field returns the name of the gateway instance for the payment.
See Payment for more information on the newly added field.
A new field for the payment gateway name is now available in the Payment Export Data Source. This new field, called "gateway", specifies the name of the gateway instance used for each payment transaction.
A number of usability improvements were made in the Payments Operations areas:
The following Zuora UI pages were enhanced with sections and fields added and re-organized:
Litle & Co. has split the certification/testing environment into separate environments, Pre-Live and and Post-Live, and optimized each environment for different uses. Starting from the 176 Release, Zuora supports the Pre-Live environment as well as the Post-Live and the Production environments. You can create new Litle & Co. gateway instances or modify existing ones with their Pre-Live credentials.
Your Litle test and production instances created before this change will still work with the same environment setting. The test instances will point to the Post-Live environment with their existing Merchant Id.
Litle & Co. Updater is not affected by this change.
See Litle Payment Gateway for information about accessing the testing environments of Litle & Co. Payment Gateway.
When submitting a payment to Chase Paymentech Orbital Gateway, we now submit the whole payment number, including the "P-" prefix.
This enhancement should improve your ability to reconcile payments between Zuora and Chase Paymentech without the need for any data manipulation.
We've enhanced log in security with Two-factor Authentication (2FA). 2FA is a system which uses two different forms of user authentication, providing a higher level of authentication consisting of the following:
Zuora tenant administrators can enable Two-factor Authentication for tenants through Administration Settings > Security Policies. Once Two-factor authentication has been enabled for your tenant, all users within the tenant will be forced to enter an authentication code after logging into Zuora with their Zuora username and password.
See Two-Factor Authentication for more information.
For Release 176, the WSDL version is 56.0. See The Zuora WSDL for information about downloading the current version.
The following issues were resolved for this release.
For recurring charges with tier or volume pricing model, if quantity of charge was 0, the total amount charge and the CMRR of that subscription did not reflect the correct value. This issue has been resolved and now reflects the correct value.
The Edit price in multi-currency feature did not allow you to save changes. The issue has been resolved. You can save after you edit the price in multi-currency.
The Trial Balance Summary no longer includes deleted taxes on Invoice Items. Run the Trial Balance again to generate a correct summary without deleted tax information.
Incorrect credit card expiration date showed in payment decline notifications when the day portion of the payment decline date
did not exist in the credit card expiration month. For example, if a payment was declined on May 31, and the credit card expiration date was "April 2015," the decline notification would have "May 2015" as the credit card expiration date.
The issue has been resolved. The correct credit card expiration date appears in the payment decline notification email.
We made a few user experience enhancements to the Knowledge Center:
We are moving content around a bit to reduce the browsing levels in the left navigation panel. These changes will reduce the number of clicks - giving you more direct access to content. Be sure to update your browser bookmarks.
We've refreshed our visual cues on notations.
|Used to indicate helpful information, such nice-to-know or usage tips.|
|Used to highlight important information, such as release information.|
|Used when we make a recommendation for improved usage or to suggest a best practice.|
|Used to indicate the user role or permission required to perform an action.|
We updated the following Knowledge Center articles based on customer-reported feedback:
This maintenance release includes the following resolved issue and internal fixes.
The following error occurred when making a SOAP API call to update the draft payment's Status to 'Processed' and TransferredToAccounting to 'Yes':
The Payment has been transferred to accounting and cannot be changed.
This error prevented syncing payments from Netsuite to Zuora.
This maintenance release includes internal fixes.