You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info
On Monday, February 27th, 2017, we began releasing a new version of Apigee Edge for Public Cloud.
New features and updatesThe following lists the new features and updates.
Deleting monetization data for an organization
You may wish to delete monetization data for your organization in the following scenarios:
- Delete your organization. In this case, you must delete the monetization data before you can delete the organization.
- Clear monetization data from a test organization that you would like to reuse. In this case, you must synchronize the Apigee Edge data after you delete the monetization data.
For more information, see Delete monetization data from your organization. (DEVRT-2481)
The following bugs are fixed in this release. This list is primarily for users checking to see if their support tickets have been fixed. It's not designed to provide detailed information for all users.
|Add notification templates for company-developer notifications
Default notification templates have been added for company-developer notifications, including
DEVELOPER_INVITES_COMPANY. For more information, see Set up notifications using
|Rate plan not renewed on renewal date
An issue has been fixed that was preventing rate plans from being renewed on the configured renewal date.
|Rate plans not generating usage notifications
An issue has been fixed that was preventing rate plan usage notifications from being sent.
|API calls are not blocked after rate plan expires
An issue has been fixed that was enabling API calls to go through after the rate plan expiration date.
|Deleting an API package with draft or expired plans returns a 500 HTTP
When deleting an API package that had draft or expired rate plans, the delete operation would fail with a 500 HTTP error. A more descriptive error is now returned indicating that the user must delete the expired or draft rate plans before they can delete the API package.
|Future rate plan not applied to developer accepting parent rate plan after
future rate plan is published
If one or more developers accepted a parent rate plan after a future rate plan had been published, the future rate plan was not honored and they were suspended when the parent rate plan expired. This issue has been fixed.
|Duplicate notifications sent for some events
Duplicate notifications are no longer sent for the same event.