October 2014 - New Features

Knowledge Center > ZZ ARCHIVE > ARCHIVED Zuora Billing Release Notes > 2014 New Features > October 2014 - New Features

October 2014 - New Features


Welcome to the Zuora October 2014 Release (R181, R181.2, 181.3). This release includes new features, enhancements, resolved issues, and improvements to the Knowledge Center.

Released Versions

Environment Current Product Version Release Date Current WSDL
Production R181.4 November 3, 2014 61.0
API Sandbox R181.4 November 3, 2014 61.0

See Version Information for more version information.

Highlights by Zuora Keys

  • ACQUIRE: Payment Pages fast, easy implementation ​| Change History displays users who updated the subscription  | Improved performance on Mass Order Entry
  • BILL: Customization supported on Subscription Product Feature in subscriptions and amendments
  • COLLECT: Moneris payment gateway supports the Discover Card
  • ACCOUNT: Accounting Codes must be active to process them in Zuora APIs
  • SCALE: Downloading Zuora WSDL supports custom fields ​| Export tenant-specific user data to a CSV file

Zuora for Salesforce Release (Q3 2014)

Some of the highlights in the Q3 2104 release of Zuora CPQ are:

  • Guided Selling:  The Guided Selling features enable you to implement customized product recommendation rules and provide easy and effective quoting experience with advanced navigation and filtering of your product catalog.
  • Entitlements: A new entity, feature, was added to Zuora Product Catalog. You can define features, add features to products, and add products and additional features to Quotes.

See Zuora for Salesforce Quotes Q3 2014 Release Notes and Zuora 360 Q3 2014 Release Notes for details.

Z-Suite Integrations Release

See  Z-Suite Integrations Release Notes for details.

New Zuora Features and Enhancements

Billing & Subscription

Feature Description and Custom Fields Editable on New Subscriptions and Amendments

Now you can customize the Features in a Subscription or Amendment by editing the Description and Custom Fields of the Subscription Product Features.

This feature is supported for New Subscriptions and Add/Update Products Amendments.

See Manage Subscription Product Features for more information.

Change History Accurately Displays Users Who Updated the Subscription

The Subscription Change History in the Zuora Application now displays the individual users who made updates to the subscription. This enhancements applies only to subscriptions created as of this release.

Change History:  09/18/2014 17:11:47 gene@GreensMarket.com new creation, status: Draft, date:09/18/2014
                 09/18/2014 17:12:05 gene@GreensMarket.com Contract effective date:09/19/2014
                 09/19/2014 09:40:54 sarah@GreensMarket.com Service activation date:09/20/2014
                 09/19/2014 09:46:04 sarah@GreensMarket.com Customer acceptance date:09/20/2014

Previously, Change History displayed only the user who initially created the subscription regardless of who made the change.

See Viewing a Subscription for more information about change history.

Mass Order Entry Performance Enhancement

We've improved the performance when importing records during a mass order entry process. Zuora recommends a maximum of 400 records per file. 

See Using Mass Order Entry to Create Subscriptions or Create Amendments through Mass Order Entry for more information.


The Second Generation of Zuora Payment Pages, Payment Pages 2.0

Since their launch, Zuora’s Payment Pages have allowed subscribers to send payment details directly to Zuora in a secure, PCI-compliant manner. Payment Pages have enabled you to create Payment Pages matched to the look and feel of your checkout flow.

A new and improved version of payment pages, Payment Pages 2.0, is available in a controlled release. While retaining the benefits of the existing Payment Pages 1.0, 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 a) an embedded form or b) 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 user's locale and other criteria. For example, once you have added your translations, you can use the parameters to specify what 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 UI.
  • 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.

Getting started with Payment Pages 2.0

  • How do I get access to Payment Pages 2.0?

This feature is in Controlled ReleaseSubmit a request at Zuora Global Support to get this feature enabled for your tenant.

  • Do I need to change my implementation if I am already using the first version of Payment Pages?

Yes, you will have to update your implementation to take advantage of the new features.

  • What does this mean for any Payment Method 1.0 pages I've created? 

Your Payment Method 1.0 pages will continue to be available and will function. Once Zuora Support enables Payment Pages 2.0, you will be able to create and manage Payment Pages 1.0 or 2.0 pages.

At some point, once you have fully migrated to Payment Pages 2.0, you can ask support to turn off access to your ​Payment Method 1.0 pages so that they no longer appear in the UI.


Moneris Payment Gateway Supports Discover Card

We support Discover Card with Moneris.

See Supported Payment Methods for more information.

Credit Balance Adjustment API and Data Source Supports CBAAmount Field 

The CBAAmount field has been added to the Invoice object in the Data Source and API.

Revenue & Finance

Accounting Codes Must be Active Before You Can Include Them in API Calls

Zuora now requires that accounting codes be active in your Zuora Chart of Accounts before you can include them in SOAP or REST API calls.

In previous releases, Zuora allowed you to include inactive accounting codes in API calls. Now, if you try to include an inactive accounting code in an API call, Zuora returns the following error message:

The specified accounting code {name} is inactive.

For Z-Finance users, see Set Up Chart of Accounts for information about how to activate accounting codes in Zuora. For all other users, see Set Up Chart of Accounts.

Note that this enhancement was first announced in the September 2014 R180.2 maintenance release.

Platform & Cloud

New Ability to Export Tenant-specific User Data to CSV File 

Export your tenant user data and their associated roles from the Exports page or from the Administrator Settings, Manage Users page. The CSV file includes the following exported user data:

  • User ID
  • User Name
  • First and Last Name
  • Status
  • Email
  • Created On
  • Zuora Roles: Billing Role, Payments Role, Commerce Role, Platform, Finance Role
  • Last Login

See Managing Users or Export Report for more information.

Zuora APIs


WSDL Version

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

Downloading Latest  Zuora WSDL Includes Custom Fields

Downloading the latest Zuora WSDL now includes your tenant-specific custom fields. Get the latest Zuora WSDL version without worrying about re-adding your custom fields.

See Zuora WSDL and Custom Field in SOAP Objects for more information.

Resolved Issues

The following issues were resolved for this release.


Multiple AQuA Sessions Running in Parallel

AQuA sessions with the same Tenant ID, Partner ID, and Project ID cannot run in parallel. When this occurs, they are executed sequentially, in the order in which they are received. 


Clean Up Order ID for Moneris

We fixed the Order ID for future transactions and restored the Order ID for legacy transactions.


Reporting Permission to Access Z-Reporting 

Only users with the Complete Data Access Control permission can access Z-Reporting.

Knowledge Center

Customer-requested Improvements to Articles

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

Maintenance Release 181.2

  • Production release, October 29, 2014
  • API Sandbox release, October 29, 2014

These maintenance releases include internal fixes.

Maintenance Release 181.3

  • Production release, October 31, 2014
  • API Sandbox release, October 31, 2014

These maintenance releases include internal fixes.

Maintenance Release 181.4

  • Production release, November 3, 2014
  • API Sandbox release, November 3, 2014

These maintenance releases include internal fixes.

Last modified


This page has no custom tags.


(not set)