You're viewing **Apigee Edge** documentation.  
[Go to the
**Apigee X** documentation](http://cloud.google.com/apigee/docs). info

On Monday, April 15, we began releasing a new version of Apigee Edge integrated portal.

> [!NOTE]
> **Resources** :
>
> - **Questions or issues?** Contact [Apigee Edge Support](https://docs.apigee.com/api-platform/troubleshoot/support)
> - Subscribe to release notifications: See [Get Apigee Edge release notifications](https://docs.apigee.com/release/get-release-notifications).

## Bugs fixed

The following bug is 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 | Component Name | Description |
|---|---|---|
| 129866439 | Developer Portal | **Change live portal route from `/my-apps/<app-name>` to `/myapps/<app-id>`** URLs in the live portal for a specific app are changing from `/my-apps/<app-name>` to `/my-apps/<app-id>`. |
| 126604886 | Developer Portal | **Request payload required fields are not rendering as required for array objects** Fixed issue where required array objects were not marked as required in SmartDocs. |
| 123644708 | Developer Portal | **Gracefully handle missing host field in spec** Fixed issue where SmartDocs would fail to render spec if host value was not specified. |
| 119200785 | Developer Portal | **Support absolute URLs in menu items** Fixed issue where external links or file references could not be configured in menu items. |

## Known issues

The following are known issues in this release; they will be fixed in a future release.

| Area | Known Issue |
|---|---|
| Portal | - Apps with multiple credentials are not supported by the portal at this time. - Simultaneous portal updates (such as page, theme, CSS, or script edits) by multiple users is not supported at this time. |
| Specifications | - Apigee recommends that you provide unique names (titles) for the specifications within your organization. - The behavior of remote references in specifications is not guaranteed at this time. - Versioning of specifications will be supported in a future release. - Sharing of specifications with teams will be supported in a future release. |
| API proxy management | - For best results, Apigee recommends that you maintain a one-to-one relationship between an OpenAPI Specification, an API proxy, and an API product. This limitation will be relaxed in a future release of the product. |
| App registration | APIs that are not published are not displayed to app developers when registering an app. In a future release, this issue will be fixed to display all APIs (both published and unpublished) to app developers. |
| API documentation | - If you delete an API reference page, there is no way to recreate it; you'll need to delete and re-add the API product. - The API reference documentation does not handle form parameters properly at this time. - When using Try It, the `Accept` header is set to `application/json` regardless of the value set for `consumes` in the OpenAPI Specification. |
| Email Notifications | - If a user clicks a time-sensitive link in a notification after the 10-minute expiration, an error is thrown. - If a user clicks the reset password link twice in an email notification, an error is thrown. |