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.
Summary of generally available features and enhancements by Zuora Keys:
|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.
Z-Suite Integrations Release Notes
Release May 27, 2015, v329
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.
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:
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:
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:
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:
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:
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.
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 wish 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:
Ensure that the user who performs 360 syncs has the correct security access to the new fields listed below.
We implemented a new feature to support the single subscription for amendments. The following two new fields were added to Zuora 360:
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.
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:
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.
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:
See Validate the Digital Signature for Payment Pages 2.0 for information about the digital signatures in Payment Pages 2.0.
The AR Aging and Revenue Detail reports now automatically include data from segments that you have configured for summary journal entries.
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:
The setting is located in Settings > Z-Finance Settings > Configure Segments under Additional Configurations.
See Segments and GL Segmentation Rule for more information.
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.
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.
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.
For Release 189, the WSDL version is 68.0. See Zuora WSDL for information about downloading the current version.
The following issue was resolved in this release.
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.
We have updated the following Knowledge Center articles based on customer-reported feedback:
BankTransferas a value.
This maintenance release includes internal fixes and the following resolved issue:
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.
This maintenance release includes internal fixes.