15.06.24 - Apigee Edge cloud release notes

You're viewing Apigee Edge documentation.
Go to the Apigee X documentation.

On Tuesday, June 23, 2015, we released a new cloud version of Apigee Edge.

New features and enhancements

Following are the new features and enhancements in this release.

New Proxy Editor as default

The new API proxy editor is enabled by default in the management UI. The new editor includes many usability improvements, including more comprehensive views of conditional flows and endpoints on the Overview page, all configuration on the Develop page, more intuitive adding of conditional flows, endpoints, and policies, more complete XML views rather than small snippets, search that crawls filenames and text, and more. (MGMT-2279)

New Delete OAuth v2.0 Info policy

A new "Delete OAuth v2.0 Info" policy lets you delete OAuth v2 access tokens and authorization codes. The policy replaces the functionality previously provided by the management API. For more information, see Delete OAuthV2 Info policy. (MGMT-2257)

New Delete OAuth v1.0 Info policy

A new "Delete OAuth v1.0 Info" policy lets you delete OAuth v1.0 request tokens, access tokens, and verifier codes. The policy replaces the functionality previously provided by the management API. For more information, see Delete OAuth V1 Info policy. (APIRT-1351)

Updated schemas for endpoints, proxies, and other entities

Reference schemas have been updated for non-policy entities such as TargetEndpoint, ProxyEndpoint, APIProxy, and many others. See https://github.com/apigee/api-platform-samples/tree/master/schemas. (APIRT-1249)

Error Messages in the management UI

Following are error message enhancements in the management UI:

  • The management UI used to group and display all error messages on the UI for the entire login session unless you dismissed them. With this update, the error messages are cleared automatically when you navigate away from the page on which they occurred. (MGMT-2254)
  • The management UI no longer suppresses duplicate error messages. (MGMT-2242)

Role hyperlinks on Organization Users page in the management UI

On the Organization Users page in the management UI (Admin > Organization Users), role names are now hyperlinked, letting you quickly navigate to role pages. (MGMT-1055)

Statistics Collector policy: automatic conversion of statistics name to lowercase

When creating a custom analytics collection in the API proxy editor (Develop page > Tools > Custom Analytics Collection), the collector variable (statistic) "Name" must be lowercase. If you enter the name with uppercase letters, the tool automatically converts the Statistic name to lowercase in the Statistics Collector policy. (MGMT-740)

Bugs fixed

The following bugs are fixed in this release.

Issue ID Description
MGMT-2235 For expiring SSL certificates, Expiry relative time can be confusingly rounded
For expiring SSL certificates, the relative time of the expiry date is always shown in days instead of being rounded up to months, when the certificate expires in 90 days or less.
MGMT-2173 Trace UI doesn't allow legal URLs
The Trace UI now lets you send requests with query parameter values that contain nested query parameters.
MGMT-2067 Trace: If API proxy revision deployed in 2 environments, selecting revision and environment does not work correctly

Problem attaching API proxy to existing API product
Fixed attaching an API proxy to an API product in the Management UI when the API proxy had a resource for the "/" path.

MGMT-1563 Send button on Trace remains disabled if it encounters an error
MGMT-787 UI alert usability issue
In the management UI, when you click + API Proxy and the New API Proxy dialog appears, you can press Esc to dismiss the dialog.
AXAPP-1708 Analytics API appears to produce different numbers for the same statistic depending on how I ask
APIRT-1425 continueOnError attribute when set to "true" has no effect in JavaCallout policy
APIRT-1206 target_ip is not recorded in the fact table for 503s and most of the 504s
APIRT-67 OAuth GenerateAccessToken policy doesn't set the oauthV2.failed variable correctly