180731 - Apigee Edge for Public Cloud release notes

On Monday, August 20, 2018, we began releasing a new version of Apigee Edge for Public Cloud.

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 to understand how you can figure it out by comparing release numbers.

Questions or issues? Get help here.

Release notifications: Go to http://status.apigee.com and click Subscribe to Updates.

Release notes home page

New Features and Updates

Following are the new features and updates in this release.

Issue ID Component Name Description
110996654 Management Server

Add API to GET and SYNC distributed flow hook deployment status

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 Component Name Description
113904969 Management Server

Issue with deletion of API proxies in demo orgs

Fixed September 10, 2018.

112192639 Management Server

Management server tries to deploy to router even if deployment to message processor failed

112133192 Connectors

Extensions: JSON validation on <Input> element is too strict to inject flow variables

In an ExtensionCallout policy, if the <Input> element contains a JSON payload, you can include Edge message flow variables using the standard curly braces syntax (for example, {client.ip}) without getting an invalid JSON error.

111503565 Management Server

"mdc" property returned on get environment management API calls

110719914 Management Server

Create Sense built-in roles for existing and new orgs

78105568 Management Server

Shared flow deployments do not show up in /org/{org}/sharedflows/{sharedflow}/deployments management API calls after updating a deployed shared flow