You're viewing **Apigee Edge** documentation.  
[Go to the
**Apigee X** documentation](http://cloud.google.com/apigee/docs). info

On Monday, February 27th, 2017, we began releasing a new version of Apigee Edge for Public
Cloud.

> [!NOTE]
> **Note:** **Private Cloud customers** : Is this cloud release included in your Private Cloud version? See your version's release notes to see which cloud releases it contains. Also, see [About release
> numbering](https://docs.apigee.com/release/apigee-edge-release-process) to understand how you can figure it out by comparing release numbers.
>
> **Questions or issues?** Contact [Apigee Edge Support](https://docs.apigee.com/api-platform/troubleshoot/support)
>
> **Release notifications** : See [Get Apigee Edge release notifications](https://docs.apigee.com/release/get-release-notifications).
>
> [Release notes home page](https://docs.apigee.com/release/notes/apigee-release-notes)

## New features and updates

The 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](https://docs.apigee.com/api-platform/monetization/delete-monetization-data-organization). (DEVRT-2481)

## Bugs fixed

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.

| Issue ID | Description |
|---|---|
| DEVRT-3385 | **Add notification templates for company-developer notifications** Default notification templates have been added for company-developer notifications, including `COMPANY_INVITES_DEVELOPER` and `DEVELOPER_INVITES_COMPANY`. For more information, see [Set up notifications using notification templates](https://docs.apigee.com/api-platform/monetization/set-up-notification-templates). |
| DEVRT-3364 | **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. |
| DEVRT-3325 | **Rate plans not generating usage notifications** An issue has been fixed that was preventing rate plan usage notifications from being sent. |
| DEVRT-3297 | **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. |
| DEVRT-3296 | **Deleting an API package with draft or expired plans returns a 500 HTTP error** 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. |
| DEVRT-3178 | **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. |
| DEVRT-3113 | **Duplicate notifications sent for some events** Duplicate notifications are no longer sent for the same event. |