We are pleased to provide you with a summary of our May, 2011 release.
This release includes the following new features and enhancements.
The following features have been added to Z-Billing.
Zuora now verifies that Subscription names are unique across all customer accounts.
Zuora provides a default template for every customer notification. These templates include default values for the FROM address, REPLY_TO address, subject, and email body. However, the default values might not be appropriate for your organization.
Zuora now requires that you edit the email template before activating the notification, to be sure that you are using the correct information.
Zuora now uses the HTTP Secure (https) protocol for callout notifications. When creating callouts, you must now specify an https address for the Base URL.
See Configuring Callout Notifications for more information about callout notifications.
Support for Additional Custom Fields
The Zuora applications now allow you to create up to 50 custom fields for each field type.
Order Builder allows you to create highly-complex and customized Ordering flows from within a Salesforce.com org. Order Builder provides programmatic access to Zuora’s APIs in the Force.com environment, and is delivered as part of the Z-Force 360 managed package. With Order Builder, a Force.com developer can import the WSDL from their Zuora tenant into Salesforce and then call Zuora’s APIs using Apex (the Force.com programming language.)
See the Z-Force Order Builder documentation for more information.
You now have the option of creating Evergreen quotes. If you select the Evergreen option, the Initial Term and Renewal Term should be 0, and this is enforced through a validation rule.
In this release, the Evergreen option is not available for Amendments.
You can now specify the Service Activation Date and/or Customer Acceptance Date when creating or editing new quotes. The Customer Acceptance Date must always be on or after the Service Activation Date, and the Service Activation Date must always be on or after the Contract Effective Date/Start Date. This is enforced through a validation rule when the quote is saved.
Currently, Z-Force Amendments do not allow changing dates/terms. Because of this, the ability to specify Service Activation Date and Customer Acceptance Date is not available in Amendments in this release.
A new configuration option allows you to generate the Quote PDF and save it as an attachment on the Opportunity with a single click. If this option is selected, the PDF will not be displayed after it is generated.
If you select Specific Months Billing Period in Z-Billing for any charge, the number of months is synced to Z-Quotes and is displayed to the user when they add new products. The number of months can also be displayed in the Quote PDF.
The updated Product Selector page has an improved interface and styling that is more consistent with the native Salesforce look-and-feel. The new page loads faster and imposes no limitations on the size of the Product Catalog.
The Default Payment Method selected in a Zuora Account is now synced to Z-Force and is displayed in the Billing Account in
Quote Templates now support Product Rate Plan Name. Users now have the ability to add Product Rate Plan Name to their Quote Templates.
A County field has been added to the Contact standard object in Salesforce. The Country field is used to capture County information and then send that information to Z-Billing when a user clicks Send to Z-Billing for any Quote. This has been added for Taxation purposes.
This feature provides support for setting the Opportunity Amount to the Quote TCV amount whenever a quote is created or updated. This feature can be turned on through the Z-Force configuration setting Update Opportunity Amount with Quote TCV, located in the Z-Force Config tab in Salesforce.
The following features have been added to Z-Payments.
Zuora now supports transacting reference transactions using PayPal's PPREF. (Zuora has always been able to transact using PNREF transactions.) This allows you to store customer-created credit card and reference it using PNREF or PPREF.
Zuora supports the following PayPal products:
This feature is useful if you have customers in Zuora, you are are transacting against them using PayPal, and you want to add Zuora functionality, but do not want customers to have to re-enter their credit card numbers. You can instead pass the PPREF or PNREF values, and Zuora will use them to create payment methods with a reference transaction. Zuora will then use those values to transact against PayPal and make payments accordingly.
Zuora supports only reference number refreshes with the PNREF transactions.
You can now create, edit, and view custom fields for Credit Balance Adjustments. You can use this new feature with the user interface and the API.
You can create custom fields, then assign a value to the custom field when creating a Credit Balance Adjustment. You can then edit the custom field value when you view the Credit Balance Adjustment.
To create custom fields for Credit Balance Adjustments, navigate to Settings > Manage Custom Fields and select Credit Balance Adjustment Fields.
We allow you to pass in any value for payments for Verifi and CyberSource.
Note: The Verifi gateway is in controlled release. If you would like to use this gateway, please contact Zuora Global Support.
This feature allows you to specify one or more gateway options. For each gateway option, you pass a name and a value. Zuora takes the name and value passes it to the gateway. This allows you to add functionality that supported by a specific gateway but currently not supported by Zuora. See Customizable Gateway Option Example for more information.
Zuora now supports advanced API fields for passing custom data to Verifi. You can pass any field to the gateway, including merchant-defined fields. This allows you to leverage advanced gateway features associated to these merchant defined fields or overwrite Zuora standard fields.
Note: The Verifi gateway is in controlled release. If you would like to use this gateway, please contact Zuora Customer Care.
The following fields are passed automatically to Verifi:
|This Zuora field...||...is mapped to this MDF field:|
|Number of Process Payments for that Payment Method||MDF2|
|Text field on Z Gateway for Verifi||MDF3|
|Payment Method number of consecutive failed payments||MDF9|
The following issues were resolved in this release.
Previously, data source filters did not allow empty strings (" ") as a comparison condition for data types.
In this release, if the data type of the filter is the text format Zuora allows an empty string input as the comparison condition for the filter. You can use this to find or exclude records with empty string field (for example, an empty comment or empty email contact). If a data type of the filter is not text, Zuora will continue to generate an error message for an empty string input.
Previously, it was difficult to select a product or rate plan when updating or removing a product in an amendment if multiple products or rate plans have the same name.
In this release, the Effective Start Date has been appended to the rate plan names to help you determine which rate plan to select.
Users are now prevented from updating the account numbers of accounts in the following cases:
Previously, Zuora would not allow you to delete export records for data sources from the user interface.
In this release, you can now delete export records.
Previously, the ZOQL did not check for some cases of faulty syntax. In this release, the ZOQL will not accept queries that use the following syntax:
select *.* from item;
The *.* syntax is no longer allowed.
select Name Account;
ZOQL requires the from keyword. For example:
select Name from Account;