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

On Wednesday, January 18, 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

Following are the new features and updates in this release.

### Shared flows and flow hooks
features are GA

The shared flows and flow hooks features introduced in cloud release [16.09.21](https://docs.apigee.com/release/notes/160921-apigee-edge-public-cloud-release-notes)
have moved to [general availability](https://docs.apigee.com/release/release-stages) and
appear by default in the Edge management UI. These features let you perform consistent
operational behavior across multiple proxies. With shared flows, you group reusable policies and
resources, then execute them at specific points (flow hooks) before or after the main flows in an
API proxy. For example, a shared flow might verify the API key, protect against spike arrests,
and log data before the main proxy request flows execute (at the "Pre-proxy Flow Hook").

For more information, see:

- [Reusable shared flows](https://docs.apigee.com/api-platform/fundamentals/shared-flows)
- [Attaching a shared flow using a flow
  hook](https://docs.apigee.com/api-platform/fundamentals/flow-hooks)
- [Flow Callout
  policy](https://docs.apigee.com/api-platform/reference/policies/flow-callout-policy)
- [Shared
  flow bundle configuration reference](https://docs.apigee.com/api-platform/reference/shared-flow-bundle-configuration-reference)

(EDGEUI-839)

## 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 |
|---|---|
| EDGEUI-898 | **Errors importing or saving large bundles (\>10MB)** This issue was addressed in a hotfix released on February 6, 2017. (REL-3948) |
| EDGEUI-860 | **Users are not receiving an email when added to an org in the UI** This issue was addressed in a hotfix released on January 23, 2017. |
| EDGEUI-847 | **NodeJS option should be removed from Service Callout policy option** |
| EDGEUI-827 | **Custom roles can allow additional permissions unexpectedly** |