June 2015 Release Notes

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

June 2015 Release Notes

Welcome to the Zuora June 2015 Release, R189, 189.1, 189.2. This release includes new Zuora features, enhancements, resolved issues, and improvements to the Knowledge Center.

Highlights by Zuora Keys

Summary of generally available features and enhancements by Zuora Keys:

  • PRICE: Previewing Charge-level metrics available through SOAP and REST APIs | Subscription Rate Plans and Rate Plan Charges Now Support Custom Fields 
  • BILL: New Barcode capability for Custom Invoices
  • COLLECT: Access Token for Authorizing Transactions | Mandate Confirmation Page for SEPA Direct Debit
  • ACCOUNT: AR Aging and Revenue Detail Reports Include Segment Data | More Control Defining Discount Segments | New Accounting Close Options on Unprocessed Events | Transaction Type of Journal Entry Items Supported on Data Source
  • NURTURE: GA Support for Salesforce Connected App

Released Versions

Environment Current Product Version Release Date Current WSDL
Production R189.1 June 24, 2015 68.0
API Sandbox R189.2 July 1, 2015 68.0

See Version Information for more version information.

GA Highlights by Zuora Keys

Zuora for Salesforce Release (Q1 2015)

Zuora for Salesforce Quotes Q1 2015 Release Notes and Zuora 360 Q4 2014 Release Notes (note that Zuora 360 release remains Q4 2014)

Z-Suite Integrations Release

Z-Suite Integrations Release Notes
Release May 27, 2015, v329

Features and Enhancements


Barcodes Available on Invoices

Zuora has added the ability to include up to five barcodes on your invoices when you use Code 128 merge fields on your invoice templates. This feature is available only on the new invoice file generation service.

See Using Barcodes on Invoice Templates for more information.

New Invoice File Generation Service Zuora will stop supporting the old file generation service as of the September, 2015 Release R192. If you have not already done so, you will need to update your invoice templates before that time.

Support for Preview of Charge Level Metrics

In previous Zuora releases, you could only get subscription level metrics. Now you can get charge level metrics through REST and SOAP API preview calls. Charge level metrics previews let you show charge details to your customers before they make a purchase by including the following information:

  • Charge level Monthly Recurring Revenue
  • Charge level change in Monthly Recurring Revenue
  • Charge level Total Contract Value
  • Charge level change in Total Contract Value

For more information about using charge level metrics previews with SOAP, see the following:

For more information about using charge level metrics previews with REST, see the following:

Support for Custom Fields in Subscription Rate Plans

Zuora now supports custom fields for subscription rate plans and for subscription rate plan charges. You add and store more information in your subscription rate plans. You can find support for subscription rate plan custom fields in the Zuora application, SOAP API calls, and REST API resources.

See Manage Custom Fields for more information about subscription rate plan custom fields in the Zuora application.

See RatePlan for more information about SOAP API calls.

For more information about subscription rate plan custom fields in REST, see the following:

Support for Custom Fields in Subscription Rate Plan Charges

Subscription rate plan charge custom fields are available on Zuora REST API resources. You can use these custom fields to add and store additional information about your rate plan charges.

See the following for more information:


Salesforce Connected App Generally Available with Zuora 360

Now Zuora offers the option to use OAuth to authenticate to Salesforce through a Connected App. Previously, you could only authenticate into Salesforce with Salesforce login credentials and a security token. 

The OAuth option gives you a more secure method for connecting to Salesforce:

  • Tokens only are used instead of a Salesforce login and password that are stored in Zuora
  • Salesforce integration can be controlled centrally from Salesforce, instead of from Zuora, the sending application

Salesforce Connected App is deployed with Zuora 360 and requires the installed Zuora 360 Package, version 2.110 or higher.

Salesforce Connected App is not deployed with Zuora Quotes. If you want to use the OAuth authentication in Zuora Quotes, the Zuora 360 Package, version 2.110 and higher, must be installed in the same Salesforce org as Zuora Quotes.

See Set up Credentials to Connect to Salesforce about using the Connected App to connect to Salesforce.

Support Single Subscription in Zuora CPQ

When you create an amendment and sync it to Salesforce, the original version of the subscription was deleted, and a new subscription with a new Salesforce ID was created in Salesforce. In some customer applications, this behavior could break lookup references to the original subscription.

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

To enable and use this feature, you need to perform the required steps in the order given below:

  1. Stop existing sync operations.
  2. Upgrade your Zuora 360 package to the 2.104 or later release.
  3. Ensure that the user who performs 360 syncs has the correct security access to the new fields listed below.

  4. Contact Zuora Support to enable the tenant permission In your Zuora Sandbox. Test 360 Sync thoroughly in the API Sandbox.
  5. If all testing is successful in the API Sandbox, repeat the steps #1 to #4 to enable your tenant permission in your Production environment.

We implemented a new feature to support the single subscription for amendments. The following two new fields were added to Zuora 360:

  • The Subscription Number field (Zuora__SubscriptionNumber__c) was added to the Subscription object as an External ID. If this feature is enabled in your tenant, 360 Sync will upsert a Subscription using the Subscription Number. Since Subscription Number does not change across Subscription versions, Subscription records in Salesforce will have the same Salesforce Record ID across multiple Subscription versions.
  • The Charge Number field (Zuora__SubscriptionChargeNumber__c) was added to the Subscription Product Charge object as an External ID. If this feature is enabled in your tenant, 360 Sync will upsert a Subscription Product Charge using the Charge Number. Since Charge Number does not change across Subscription Product Charge versions, the Subscription Product Charge records in Salesforce will have the same Salesforce Record ID across multiple Subscription Product Charge versions.

The user who performs 360 Sync must have the field-level Visible access to the above two fields in Salesforce. See Setting Field-Level Security in Salesforce for checking and setting the field-level access for profiles.

New Confirmation Dialog Option for Payment Pages 2.0 for the SEPA Payment Pages

We've added a Confirmation Dialog option to the Commerce Payment Pages 2.0 workflow. This option is turned on by default for the SEPA Bank Transfer payment method. When your customers select to pay with SEPA Direct Debit as a payment type, they must confirm the mandate information on this Confirmation Dialog page before payments can be processed.

Key features include:

  • All you need to capture SEPA information in a compliant manner. The required display information includes Creditor Identifier and the customer's IBAN.
  • Look and feel is customizable. You control the styling and placement of content within the dialog.
  • Content can be localized into any language, include legal terms, labels, and dates.

As always, Payment Pages 2.0 is available in Salesforce through Zuora for Salesforce and is mobile-compatible.

See Configure SEPA Type Payment Pages 2.0 for configuring your SEPA Payment Page with the Confirmation Dialog.

New Advanced Digital Signature for Payment Pages 2.0

If your business requires additional security to protect sensitive information, now you have the option to use the advanced digital signature in the callback response for Payment Pages 2.0. The advanced signature provides the following functionality in addition to what the basic signature offers:

  • Encrypts the payment method ID returned from Zuora.
  • Allows you to validate additional information in the signature.

See Validate the Digital Signature for Payment Pages 2.0 for information about the digital signatures in Payment Pages 2.0.


Finance Reports Now Include Segment Data

The AR Aging and Revenue Detail reports now automatically include data from segments that you have configured for summary journal entries.

See Accounts Receivable Aging and Revenue Detail Exported Data Descriptions for more information.

More Control Over Discount Segmentation

We have introduced the Discount segment value setting to give you greater control over how discounts are segmented. The new setting lets you choose whether discount charges:

  • Always use the segment values from the Discount objects
  • Always use the segment values from the objects that are discounted against
  • Determine the segment values based on the discount flag in the Product Catalog

The setting is located in Settings > Z-Finance Settings > Configure Segments under Additional Configurations.

See Segments and GL Segmentation Rule for more information.

Confirmation Dialog Provides Accounting Close Options for Unprocessed Events

Previously when closing an accounting period, you might not know whether all events that impact revenue for that period, such as revenue distribution, had finished processing.

Now when you try to close an accounting period while events that impact revenue for that period are still being processed, a confirmation dialog is displayed. The dialog shows the number of unprocessed events and gives you the option of waiting until the events are complete or closing the accounting period anyway.

This enhancement applies only when closing an accounting period through the Zuora user interface.

Transaction Type of Journal Entry Items Available Through Data Source

You can now get the Transaction Type of individual Journal Entry Items through the related Journal Entry object. When you perform a data export on the Journal Entry Item data source, include Journal Entry > Transaction Type in the export.

See Journal Entry Item Data Source for more information.


New Access Token Field for Authorizing Transactions on GoCardless Payment Gateway 

GoCardless is upgrading their API. They will no longer accept the username and password for logging into their service. Going forward, only an Access Token will be required. This change becomes effective on July 1, 2015. 

We've updated the GoCardless payment gateway UI with the new required Access Token field. This new field replaces the Username and Password fields that were previously used for authorizing all transactions.

Required Action: Zuora recommends that you set your Access Token prior to the GoCardless API upgrade deadline of July 1. This action will enable Zuora to continue processing your transactions without interruption. See Update Gateway Settings to Support the New GoCardless API Version.

Have questions or concerns regarding this upgrade? Please contact GoCardless for more information about their API upgrade or Zuora Support for more information about the Access Token.

Zuora APIs


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

Resolved Issues

The following issue was resolved in this release.

Export ZOQL Duplicate Column Aliases

Prior to R189, you could make duplicate column aliases in Export ZOQL. Now duplicate column aliases are not allowed in Export ZOQL. You will get an error message if you try to use duplicate column aliases.

See Export ZOQL Select Statements for more information.

Knowledge Center

Customer-requested Improvements to Articles

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

  • CreditBalanceAdjustment object: Updated this reference with the following changes
    • Introduction. Clarified how a credit balance is applied.
    • Supported Calls. Added the supported but missing update() call.
    • AccountingCode and Type fields. Removed Delete as an allowed operation.
    • Updated Required to Create column to N/A for all fields with Query and Filter as allowed operations.
    • SourceTransactionId field: Added Create as an allowed operation. This field is not required on create.
    • SourceTransactionType field. Removed Create as an allowed operation.
    • CancelledOn field: Added a missing field definition.
  • PaymentMethod object: Updated this reference with the following changes:
    • Added the missing Bank Transfer as a supported payment method. Moved SEPA as a support type under Bank Transfer. Added missing types: Direct Debit (NZ), Direct Debit (UK), Direct Debit (AU), and Lastschrift (CH)
    • Updated the Type field to include BankTransfer as a value.
  • Vantiv Payment Gateway: Removed a duplicate phrase in the Support Recurring section: "Zuora will mark such payments as recurring when submitting the sale payment transactions to" 
  • Upgrade Zuora Quotes to Q1 2015:  Added a new section: Update Zuora Connection Settings with the Zuora recommendation to upgrade your Zuora connection to the latest WSDL version to avoid server exception errors.
  • Payment Method Updater: Removed a duplicate phrase in the Why Zuora's Payment Method Updater section: "Vantiv, CyberSource, and WorldPay will provide you with the account updater service and the required"
  • Get Invoices REST API: Updated the sentence on how invoices are returned in reverse chronological order by Update Date. Previously we indicated Invoice Date.

Maintenance Release 189.2

  • Production release, July 2, 2015
  • API Sandbox release, July 1, 2015

This maintenance release includes internal fixes and the following resolved issue:

Multiple Card Authorizations Occurring with Payment Pages 2.0

When your customer clicked the "submit" button on a Payment Page, the button turned gray, but remained clickable. If the "submit" button was clicked more than once, multiple authorizations were sent to the payment gateway, causing multiple charges to the credit card. 

Maintenance Release 189.1

  • Production release, June 24, 2015
  • API Sandbox release, June 23, 2015

This maintenance release includes internal fixes.

Last modified


This page has no custom tags.


(not set)