August 2015 Release Notes

Knowledge Center > ZZ ARCHIVE > ARCHIVED Zuora Billing Release Notes > 2015 New Features > August 2015 Release Notes

August 2015 Release Notes

Welcome to the Zuora August 2015 Release, R191. This release includes new Zuora features, enhancements, resolved issues, and improvements to the Knowledge Center.

Released Versions

Environment Current Product Version Release Date Current WSDL
Production R191.5 September 14, 2015 69.0
API Sandbox R191.4 September 8, 2015 69.0

See Version Information for more information.

GA Highlights by Zuora Keys

  • PRICE: Regenerate PDF Invoices from the Zuora Application
  • COLLECT: Payment Pages 2.0 is Now GA | Updated Payment Pages 2.0 JavaScript Library | New Payment Pages 2.0 Input Fields
  • ACCOUNT: REST API Now Supports Monthly Revenue Recognition | New Revenue Data Sources Available
  • NURTURE: HTML Email Notifications Now Available

Z-Suite Integrations Release

Z-Suite Integrations Release Notes v467, Sandbox Release August 19, 2015

Features and Enhancements

Billing and Subscription​

Regenerate Invoice PDFs from the Zuora Application

You can now regenerate an invoice PDF by clicking Regenerate Invoice PDF on the Invoice Details page in the Zuora application. Draft invoices and posted invoices can be regenerated in this way.

See Invoice Introduction for more information.

Multiple Origin Addresses in Avalara

Zuora now supports multiple origin address and company codes for tenants with Avalara enabled. Taxes can be calculated based on origin and sold-to addresses in Avalara. With multiple origin addresses and company codes, you can establish relationships between origin and sold-to addresses for your tax calculations.

This feature is in Limited Availability. If you want to have access to the feature, submit a request at Zuora Global Support

See Configure Your Tenant Profile and Permissions for more information.


Payment Pages 2.0 Now Generally Available

A new and improved version of hosted payment method pages, Payment Pages 2.0, is now generally available. While retaining the benefits of the existing Hosted Payment Method Pages, Payment Pages 2.0 are more flexible to configure, easier to localize and customize on the fly, and faster to implement.

Payment Pages 2.0 provides the following enhancements:

  • Styling Flexibility
  • Easier to style HTML: Payment Pages 2.0 uses clean, modern HTML, making it easier for you to add your own CSS to match the look and feel of your website. 
  • New overlay styling option: You have more flexibility in your checkout flow with an option to display the form as an embedded form or an overlay form. 
  • Dynamic Configuration and Localization
  • Multiple translations: For each payment page, you can upload alternate translations for the labels, error messages, and texts on the form. You assign each of the uploaded translations to a locale.
  • Dynamic configuration: Use the JavaScript parameters to dynamically display your Payment Pages based on users' locale and other criteria. For example, once you have added your translations, you can use the parameters to specify which label translations should be used and which gateway should be used to display and process the Payment Pages.
  • Enhanced security
  • Improved encryption: Using public-private key cryptography, Payment Pages 2.0 provides an additional layer of encryption for payment information submitted through the payment pages. You have control over your security keys, and you can regenerate them at will from the Zuora application.
  • Faster and Easier Implementation
  • Simplified front-end code: We provide you with a JavaScript library for implementing your payment page. Now you can load the payment form in only a few lines of HTML and JavaScript using the library.

    Any future enhancements to the JavaScript library will be backward compatible.

  • In-form submit button: With the new option to put the submit button in the payment form, you no longer need to implement a separate callback page. You can control the response to success or failure by customizing a simple JavaScript function.
  • Digital signature generation: To ensure security, requests to load your payment page must be digitally signed. However, you are no longer required to implement the code to create a digital signature yourself. Instead, use the new API call to generate the signature for your payment page.

See Payment Pages 2.0 for implementing payment pages.

Payment Pages 2.0 JavaScript Library Version Update

The two earliest versions, 1.0.0 and 1.1.0, of the Payment Pages 2.0 JavaScript library were deprecated in this release. If you are using one of those versions of the zuora.js library, you should upgrade the JavaScript library to the latest version, 1.3.0.

Version 1.2.0 and the new version released in the 191 release, 1.3.0, are supported in Payment Pages 2.0.

Additional Input Fields Added to Payment Pages 2.0

The following input fields were added to the UK Direct Debit Type Payment Pages:

  • Agreement Checkbox

For the implementations with an inside Submit button, the Submit button is not enabled on Payment Pages until the user selects this checkbox.

For the implementations with an external Submit button, an event handler is available for your app to listen and trigger an appropriate action. See Event Handler for UK Direct Debit Payment Method for sample code that uses the event handler. This event handler is only supported in the 1.3.0 version of zuora.js.

  • E-mail

​Now you can collect the email address of your customer on a Payment Page and forward it to the payment gateways, such as GoCardless. The payment gateways use the email address to send a notification to the customer on your behalf.

​See Configure UK Direct Debit Type Payment Pages 2.0 for configuring a Payment Page to accept the UK Direct Debit type payments.

To use the new input fields described in this section in Payment Pages, you need to use the version 1.3.0 of the Payment Pages 2.0 JavaScript library, zuora.js, in your integration.


REST API Now Supports Monthly Revenue Recognition

Previously you could only perform monthly revenue recognition through the Zuora application. Now you can also perform monthly revenue recognition through the REST API. To do so, specify a Monthly Distribution value in the distributionType field when you distribute revenue by recognition start and end dates.

This feature is available to all Z-Finance users.

New Revenue Data Sources Available

The following data sources are now available:

The new data sources allow you to export a list of Revenue Event Items with their associated Invoice Items or Invoice Item Adjustments.

These new data sources are available to all Z-Finance users.


HTML Format Now Supported for Email Templates

You can now choose between plain text and HTML formatting for email templates. The addition of HTML formatting lets you:

  • Use a variety of fonts, point sizes, and other formatting options such as bold, italics, text colors, and bulleted lists
  • Include images—for example, your company logo
  • Include hyperlinks to text and images
  • Edit the HTML source directly 

See Create and Edit Email Templates for more information.

Zuora APIs​


For Release 191, the WSDL version is 69.0. See Zuora WSDL for information about downloading the current version.​

Date Field Changes for WSDL Versions 69 and Later

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, eview the date field changes and take the appropriate action.

See Date Field Changes in the WSDL for more information.

Resolved Issues

The following issues were resolved in this release.


Payment Pages 2.0 Only Executed the First Callback Function

The Zuora JavaScript function, Z.render, loads Payment Pages. If you invoked Z.render multiple times with different callback functions, only the first callback function was executed.

This fix to execute multiple callback functions requires you upgrade zuora.js to the 1.3.0 version.

Knowledge Center

Customer-requested Improvements to Articles

We have updated the following Knowledge Center articles based on customer-reported feedback:

Maintenance Release 191.5

This release includes an internal fix.

  • Production release, September 14, 2015

Maintenance Release 191.4

This release includes internal fixes.

  • API Sandbox release, September 8, 2015
  • Production release, September 11, 2015

Maintenance Release 191.3

This release includes internal fixes.

  • API Sandbox release, August 31, 2015
  • Production release, September 1, 2015

Maintenance Release 191.2

This release includes internal fixes.

  • API Sandbox release, August 25, 2015
  • Production release, August 27, 2015

Maintenance Release 191.1

This release includes internal fixes.

  • API Sandbox release, August 18, 2015
  • Production release, August 19, 2015
Last modified


This page has no custom tags.


(not set)