APEX Project Eye 26.1 delivers a major upgrade to Page Links, expanding support for newer APEX components and adding dedicated reports to help you understand how users move through your applications. These improvements make it easier to spot unreachable pages, dead ends, and navigation hubs so you can refine your application flows with confidence.

Page Links in APE Page Dashboard

From the Application Dashboard, open the Page Dashboard to review inbound and outbound links for a specific page. The Page Links region now includes links coming from newer APEX components such as Navigation Menu and Navigation Bar entries, Map Layers, Card Actions, Template Component Actions, Chart Series, Calendar Links, Search Configuration Links, and Dynamic Lists links.

If you need to go beyond the list view, you can jump straight into Page Link Explorer for an application-wide view of how pages connect.

Page Flow with navigation links

The Page Flow tab now includes links from navigation menus and tabs directly in the visual page flow diagram. Use filters to focus on specific applications, page ranges, or link types and quickly see how users can move through your app from entry points to end pages.

New Page Links Reports utility

APE 26.1 introduces a dedicated Page Links Reports utility under Utilities → Page Link Reports.

This utility groups several reports—Page Link Analysis, Page Link Explorer, Orphans Overview, Orphan Pages, and Orphan Chains—so you have a single place to analyse navigation patterns and unreachable pages.

Page Link Analysis and Page Link Explorer

Page Link Analysis shows each page with its number of inbound and outbound links and classifies it as an orphan, dead end, hub, or sink. Hubs and sinks are calculated relative to the application average, and you can optionally include activity data to see how heavily each page is used in practice.

Page Link Explorer lets you analyze links at both application and page level, combining link structure with activity data. You can see where users come from, where they go next, and how selected pages fit into the navigation flow, including any differences in authorization schemes along the path.

Orphan Pages and Chains

From the Page Links Reports utility, APE offers three focused reports: Orphans Overview, Orphan Pages, and Orphan Chains. If you maintain business-critical APEX applications, these reports give you a clear picture of which pages are still in use, and which have become disconnected over time.

In this context, orphan pages are pages that are no longer reachable from your application’s navigation and have no inbound connections or links; users will never see them in normal usage. Orphan chains are groups of connected pages that are isolated from the main application flow, again with no inbound links from the rest of the app. APE helps you find these pages and chains so you can decide whether to remove them to simplify maintenance or reconnect them if they are still valuable.

Keep in mind that Page Links Reports do not capture links generated dynamically in database packages, included only in emails, or assembled at runtime in JavaScript code, so these should still be considered during reviews.

Orphans Overview

The Orphans Overview report shows you, per application, how many orphan pages and orphan chains exist.

You can filter by workspace to focus on a specific environment or group of applications, and ideally both counts should be 0 for a clean, well-structured app.

From this overview, you can drill down directly into the Orphan Pages and Orphan Chains reports by clicking the respective links in each row.

Orphan Pages

The Orphan Pages report lists all orphaned pages within a selected application.

For each page, you can see details such as page type, page group, authorization scheme, access status, staleness, and when it was last updated.

You can choose whether to include APE activity data, which helps you understand if a page is not only structurally orphaned but also never or rarely accessed.

Orphan Chains

The Orphan Chains report focuses on chains of connected pages that are isolated from your main application flow.

It shows the root page, full chain, chain length, access status, staleness, and who last updated the chain, making it easier to review entire flows at once.

With this information, you can quickly identify obsolete flows to remove or important flows that should be linked back into the application’s navigation.