14.01.04.00 - Apigee Edge on-premises release notes
On Friday, February 28, 2014, we released a new patch for the on-premises 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.
|Trace stops working after applying the patch||
After applying OPDK patch R14.01.04, trace might stop working. To avoid this situation, after you apply the patch, update two config files:
Note: If you want the new trace functionality to be enabled by default in your OPDK, then in the apigee.conf file, set:
apigee.feature.traceVersionDefault2014 = true
|Importing a WSDL||
Importing a WSDL containing wrapped arrays now works as expected.
Importing a WSDL no longer hangs without completion.
Importing a WSDL no longer generates the error:
Error: No namespace declared for 'xsns:nameSpace'
|Role based access control||You can now limit users to only seeing API products created by users in a particular custom role.|
You can now specify the JMS headers
|API Analytics||The analytics for the top performing API's now appears when examining the API in the Edge management UI.|
|Edge management UI||
An app that is in a company is now selectable in the Publish > Developer Apps page of the Edge management UI.
The Edge management UI now displays items correctly when a user is assigned to a custom role.
Organization roles can no longer be accessed in an organization if Organization roles are disabled for that organization.
|API proxies||API proxies that have a role associated with them can now be traced.|
|Analytics install||You can now install Analytics as a non-root user.|
|Security||Fixed a security vulnerability in the Edge management UI.|
Help or comments?
- If something's not working: Ask the Apigee Community or see Apigee Support.
- If something's wrong with the docs: Send Docs Feedback
(Incorrect? Unclear? Broken link? Typo?)