We are pleased to provide you with a summary of our June, 2011 release.
This release includes the following new features and enhancements.
The following features have been added to Z-Billing.
Zuora is now able to track fixed amount discount balance for every recurring billing period. This allows you to take advantage of available discounts, even in past periods even when the billing operation has advanced to the current billing period.
Zuora no longer supports the update operation for discount charges. You cannot update a discount charge to change the value of a discount that you have already provided. Because your customers may have applied the discount to their subscriptions, you cannot change the terms of the discount.
Instead, you must remove the existing discount charge and add a new discount. First, create an amendment to remove the incorrect discount charge. Then create a second amendment to add the corrected discount charge. Your customers can then apply the new discount to new subscriptions.
See Discount Charge Models for more information.
Zuora has added a new Auto-set option to the account billing cycle date (BCD) that allows the account BCD to be set automatically to the same day as the billing date of the first recurring charge on the account. This allows the account BCD and the triggering dates of all charges in the subscriptions to easily align on the same day.
This option will set the BCD based on the first recurring charge, and not one-time or usage charges.
Previously, you were required to change the BCD manually to match the triggering date of the first recurring charge.
See Dates in Zuora for more information.
In this release, Zuora changed the tenant-level permission for the Invoice Subscription Separately (ISS) capability to make it available for all tenants. You can activate this feature by selecting Invoice the Subscription Separately in the Subscription detail page, or you can use the Z-Commerce API subscribe() call and Subscription update call.
In this release, Zuora added the ability to edit the definitions of custom fields of type Text or Picklist. You can edit existing values, add new values, and set a default value. This feature also applies to Z-Payments.
We continue to release more data sources that allow you to customize the fields you would like to extract. You can also use data sources to combine key objects into a single dataset that can be accessed via the Zuora interface or via APIs. To use the new data sources, navigate to Z-Billing > Reports, then select the Data Sources tab.
See Export ZOQL for more information about exporting data sources.
We have added the ProductRatePlanCharge data source this release. Every product can have one or more rate plans, and each rate plan can have one or more rate plan charges. The ProductRatePlanCharge data source includes the following objects:
The following features have been added to Z-Payments.
As part of our Payment Operations, Zuora supports the ability to accept overpayments (cash on account) using the Credit Balance functionality. We have enhanced our Accounting Code functionality to provide the ability to automatically associate different Accounting Codes to the Credit Balance Adjustment.
As of this release, you can define the accounting code to use to perform the following actions:
You can also select whether to use the Accounting Code from the Payment, from the Payment Method, or to define a separate accounting code for the following:
See Configure Accounting Codes for more information.
This release introduces the following changes to the subscribe() call:
In API version 30, the invoice ID and invoice number fields returned by a subscribe() call represent the ID and number of the subscription that is created by the subscribe() call.
You can now use the OR and NOT operators to create compound conditions when using the Export ZOQL. In addition, you can use parentheses to indicate the order of the condition.
See Export ZOQL for more information.
The Session Token is a string that we return during the login process of the API. The session token contains information that confirms that the user making an API request is authenticated. All non-login APIs must pass the session token (received during the login process) as part of the request header.
The session token length is variable. In this release, we have modified the token generation, which results in an increase of the token length. The session token can be up to 512 characters in length. If you want to store the session token on the client side, you must make sure that the storage can accommodate the string of up to 512 characters.
See LoginResult for additional information.
In this release, Zuora added the CommunicationProfile object. This object contains information about communication profile for an account. We have also added a CommunicationProfileId field to the Account object, which you can use to specify a communication profile from a subscribe call when creating a new subscription.
The following issues are resolved in this release.
The following Z-Billing issues are resolved in this release:
Previously, the Z-Commerce API did not support the use of the != operator to filter fields of type date.
In this release, you can now use the != operator successfully.