You're viewing Apigee Edge documentation.
Go to the
Apigee X documentation. info
On Wednesday, April 5, 2017, we began releasing a new version of Apigee Edge for Public Cloud.
New features and updates
Following are the new features and updates in this release.
Stricter input validation for entities
Stricter input validation has been enforced across all entities of Apigee Edge organization. The allowed characters are usually alphabets (all cases), numbers, underscore. (MGMT-3840)
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 |
|---|---|
| MGMT-3843 | "org.antlr.v4.runtime.Vocabulary" error on rendering model as HTML |
| MGMT-3829 | Attempt to deploy an API proxy with shared flow deployment API endpoint appears
to succeed This bug fix adds validation in Sharedflow deployment API to return 400 Bad Request "NoSharedFlowsToDeploy" on deploying an apiproxy revision. |
| MGMT-3667 | GET /v1/o/{org}/developers returns inaccurate count of developers |
| MGMT-3575 | expressions.parser.InvalidPattern exception during deployment |
| MGMT-3511 | Proxy deployment returns 400 response code even though deployment
succeeds This bug fix takes care of ignoring the un-deployment status of an apiproxy revision triggered via another un-deployment api call during the override deployment of a new revision. |