15.04.29 - Apigee Edge cloud release notes

On Tuesday, April 28, 2015, we released a new cloud version of Apigee Edge.

If you have questions, go to Apigee Customer Support.

For a list of all Apigee Edge release notes, see Apigee Release Notes.

Analytics update

When generating analytics reports with the management UI or API, data older than six months from the current date is not accessible by default. If you want to access data older than six months, contact Apigee Support.

Bugs fixed

The following bugs are fixed in this release.

Issue ID Description
MGMT-2041 Remove FaultRules element from default attachment template
The FaultRules element, which is not used in policies or API proxy steps, is no longer automatically added when you create API proxies or add policies.
MGMT-2034 Fetch WSDL returns failure: "Fetch WSDL Error: Error processing WSDL."
MGMT-1986 UI error while adding developer
MGMT-1983 Get an OAuth 2.0 authorization code API returns wrong status
MGMT-1947 Unintuitive roles in management UI
If a user does not have permission to create or edit a Transaction Recording Policy, the UI buttons to create and edit a Transaction Recording Policy are now disabled.
MGMT-1824 Fetch WSDL error while importing WSDL file with .xml extension
MGMT-1777 Cannot add user with email address which has a TLD of .acn
MGMT-1061 SmartDocs: Description of body type parameter in Swagger definition not shown in doc UI
CORERT-613 SSL handshake failures due to "unrecognized_name"
AXAPP-1493 Cache performance statistics incorrect

Known issues

This release has the following known issues.

Issue ID Description
DEVRT-1574 Inconsistent balance and usage for developers with multiple active rate plans
In monetization, if a developer is active on more than one rate plan that has per-API call charges, then monetary balance usage may sometimes be inconsistent.