Knowledge Center

Knowledge Center > What's New > Previous Zuora Releases > 2015 New Features > February 2015 Release Notes

February 2015 Release Notes

Welcome to the Zuora February 2015 Release, R185, R185.1, R185.2, R185.3, R185.4. 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:

  • BILL: Update or Assign Billing Batch through REST API
  • COLLECT: SEPA payment method support for Hosted Pages | Two new source fields on Payment object indicates if payment was created through API or Zuora application
  • NURTURE: Set incremental start time through AQuA API job to get new or updated records | Usability improvement on CRM Account ID now has icon indicating if Billing Account exists in Salesforce

​Released Versions

Environment Current Product Version Release Date Current WSDL
Production R185.4 March 11, 2015 65
API Sandbox R185.4 March 10, 2015 65

See Version Information for more version information.

Z-Suite Integrations Release

Z-Suite Integrations Release Notes
Released March11, 2015, Z-Suite v328

Features and Enhancements

Commerce

Single Euro Payments Area (SEPA) Bank Transfer Payment Method Supported in Payment Pages 2.0

Starting with this release, Payment Pages 2.0 supports the SEPA Bank Transfer as a payment method. You can create a Payment Page to accept payments via SEPA Direct Debit. 

You need to enable the Bank Transfer tenant permission to be able to create a Payment Page for SEPA Bank Transfer.

See Configure Payment Pages 2.0 for creating a Payment Page for a payment method.

Enhanced CRM Account Id Field with a Link to Salesforce Account

In Zuora application, the CRM Account ID field on the Customer Account page specifies to which Salesforce Account the Customer Account belongs. When the the field contains a valid Salesforce Account ID, the corresponding Salesforce account name appears with a link to the Salesforce Account page. If the CRM Account ID is invalid or empty, a warning icon displays. The CRM Account ID field is an editable text field.

See Basic Information for Customer Account for information about the CRM Account ID field.

Payments

Two New Fields Under Payment Object

Two new fields have been added to the Payment object fields: Source and SourceName, which indicate how the payment was created, such as through API or manually.

See Payment  for more information.

Additional Configuration Parameters Added to Chase Paymentech (Orbital Gateway)

Two configuration parameters have been added to the Chase Paymentech (Orbital Gateway) that enables AVS and CVV filtering.

See Chase Paymentech (Orbital Gateway) for more information.

Zuora APIs

AQuA API

Ability to Override the Start Time for an AQuA Job to Retrieve Incremental Records

You can now override the time from which a Stateful AQuA job incrementally retrieves records that have been created or modified, using the incrementalTime parameter. For example, if you set incrementalTime = 2015-01-21 10:30:01, AQuA will retrieve records that have created or modified beginning at 10:30:02. If this parameter is not set, AQuA will continue to use the Start Time of the last AQuA session to retrieve records incrementally.

See Post Query with Retrieval Time for more information.

REST API

Update or Assign Billing Batch when Creating Accounts through REST API

In R184, Zuora introduced alias names for batches accessible via SOAP. In this release, we now support batch fields for the REST API. This enhancement allows for use of default batches (Batch1, Batch2...) as well as batch aliases.

You can access the batch field using the following REST API resources:

SOAP API

WSDL Version

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

Resolved Issues

The following issue was resolved in this release.

Billing & Subscription

GatewayResponse and GatewayResponseCode not found in Subscribe Result when expected

When a payment transaction failed on a subscribe call, the GatewayResponse and GatewayResponseCode fields were not included in the subscribe result as expected. The GatewayResponse and GatewayResponseCode are now included in the subscribe result in all cases.

Knowledge Center

Customer-requested Improvements to Articles

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

Maintenance Release 185.4

  • Production release, March 11, 2015
  • API Sandbox release, March 10, 2015

This maintenance release includes internal fixes

Maintenance Release 185.3

  • Production release, March 4, 2015
  • API Sandbox release, March 3, 2015

This maintenance release includes internal fixes

Maintenance Release 185.2

  • Production release, February 25, 2015
  • API Sandbox release, February 24, 2015

This maintenance release includes internal fixes

Maintenance Release 185.1

This maintenance release includes internal fixes.

Last modified
18:50, 18 Mar 2015

Tags

Classifications

(not set)