15.07.08 - Apigee Edge cloud release notes

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

On Thursday, July 9, 2015, we released a new cloud version of Apigee Edge.

New features and enhancements

Following are the new features and enhancements in this release.

JavaScript access to policy properties

When using JavaScript in API proxy flows, you can access properties defined in the JavaScript policy. This is particularly useful if you want to use well-known variables in your JavaScript code. For example, say your JavaScript policy contained the following property definition:

    <Property name='source'>response.content</Property>

In your JavaScript, you could access the message response with a reference to the 'source' property, like this:
var source = properties.get('source'); // returns: response.content
var source = properties.source
var source = properties['source']

For more information, see JavaScript policy. (APIRT-1460)

Organization-level audits

Organization Administrators can audit the history of actions taken at the organization level. In the management UI, select Admin > Organization History. For more information, see Audits: API, Product, and organization history. (MGMT-2232)

Organization administrator self-removal from role

Organization administrators can remove themselves from the Organization Administrator role in the management UI by going to Admin > Organization Users and clicking Remove next to their name. (MGMT-934)

API proxy bundle import progress indicator

When uploading a large API proxy bundle in the management UI, a "working" animation is displayed to indicate the import is still occurring, which keeps you from interacting with the management UI until the import is complete. (MGMT-1285)

Bugs fixed

The following bugs are fixed in this release.

Issue ID Description
MGMT-2381 Unable to deploy proxies using the new proxy editor
MGMT-2374 Space in BasePath element should be trimmed before saving the ProxyEndpoint
MGMT-2355 UI does not correctly calculate permissions for multiple roles if one role is orgadmin
MGMT-2324 Importing a Swagger model produces incorrect SmartDocs nodes
MGMT-1518 UI shows proxy as deployed even though deployment failed on MPs
MGMT-1489 API Product not generating correct resources
DOC-1246 Contradicting statement in the docs about access tokens

The following monetization bugs were fixed in a monetization-only release on Thursday, July 16, 2015.

Issue ID Description

NextRecurringFeeDate is empty when developer accept feature rate plan
If a developer accepted a monthly flat, volume banded, or bundle rate plan that starts at a future date, made a couple of API calls on the rate plan before the start date, and was then blocked from making calls (expected behavior), the developer was not automatically unblocked when the rate plan went into effect. This issue has been fixed.