On Tuesday, May 19, 2015, we released a new cloud version of Apigee Edge monetization.
If you have questions, go to Apigee Customer Support.
For a list of all Apigee Edge release notes, see Apigee Release Notes.
New features and enhancements
Following are the new features and enhancements in this release.
Rate plan email notifications
A new Rate Plan email notification type lets you notify developers when they reach a certain transaction or dollar limit in the volume-banded or bundle rate plans they've purchased. For details, see Set up notifications using notification templates.
Synchronization of Recurring Fee and Aggregation Basis periods
In a rate plan, there were potentially two different time periods in effect:
- Recurring Fee period, configured on the Fees tab of a rate plan, that determined when developers were charged a recurring fee.
- Aggregation Basis period, defined on the rate card for Volume Banded or Bundles plans, that determined when bundle use was reset for developers.
Those two periods are now synchronized. When both a non-zero recurring fee and a Volume Banded or Bundle rate card exist in a rate plan, the recurring fee period is used for both. For example, if a monthly recurring fee exists, then rate card bundles are also reset monthly (by default at the beginning of the month).
If no recurring fee exists, bundles are reset based on the Aggregation Basis defined on the rate card. For example, if a developer starts using a rate card on the 19th of the month, and the Aggregation Basis is every month, then the bundle use is reset a month after the 19th.
Aggregation Basis is being deprecated and will be removed from monetization in a future release. For more information, see Specify rate card plan details.
Custom Attributes in summary revenue reports
Transaction recording policies let you optionally capture custom attribute data from transactions, and you can now include those custom transaction attributes in summary revenue reports. By adding a MINT.SUMMARY_CUSTOM_ATTRIBUTES property to your organization, you can indicate which custom attributes are added to the database tables for use in reports.
Cloud customers must contact Apigee Support to enable the property. Apigee Edge for Private Cloud customers can set the flag with the following API call and System Administrator credentials.
curl -u email:password -X PUT -H "Content-type:application/xml" http://host:8080/v1/o/myorg -d \ "<Organization type="trial" name="MyOrganization"> <Properties> <Property name="features.isMonetizationEnabled">true</Property> <Property name="MINT.SUMMARY_CUSTOM_ATTRIBUTES">["my_attribute_1","my_attribute_2"]</Property> <Property name="features.topLevelDevelopersAreCompanies">false</Property> </Properties> </Organization>"
Note that the array of custom attributes in the API call is URL-encoded.
The following bugs are fixed in this release.
|DEVRT-1583||Monetization UI shows "Future" badge for a current rate plan|
|DEVRT-1546||Plan limits not working|
|DEVRT-1511||mint.resourceDoesNotExist error for an existing developer|