Navigation Model

This page explains how FT Configs UI is structured and how to move through the application efficiently and safely.

Global layout

FT Configs UI uses a consistent layout across all areas.

Header

The sticky header is always visible and contains:

  • product name and logo,

  • breadcrumbs showing your current location,

  • language switcher,

  • user menu (profile and sign out).

Breadcrumbs help you understand where you are and let you quickly return to higher levels.

Page structure

Most pages follow the same structure:

  • a top section (hero) with the page title and context information,

  • a toolbar with actions and filters,

  • a main content area with tables, lists, or cards,

  • optional side panels or dialogs for details and editing.

This consistency makes it easier to move between modules without relearning the UI.

Home page

The Home page is the main entry point after sign in.

From here, you can navigate to five application areas:

  • ACS — Auto Configuration Server settings (currently the only available module).

  • Angular Console — Configuration dashboards and modules for structured configuration data. (Planned for future versions.)

  • Northbound Config — Northbound configuration editor with import and export workflows. (Planned for future versions.)

  • Service API — Service API configuration management. (Planned for future versions.)

  • Provision Portal — Provisioning configuration editor with XML import/export and section-based edits. (Planned for future versions.)

Currently, only the ACS area is available. The other four areas are displayed on the Home page but are marked as unavailable.

Module navigation pattern

Most modules follow the same interaction flow.

Typical steps inside a module:

  1. Select required prerequisites Some modules require a Client Type or similar context before data is shown.

  2. Narrow the data set Use search fields, filters, or tabs to find relevant entries.

  3. View details Click a row or card to open detailed information.

  4. Export data Use Export to download a snapshot of the current state.

  5. Apply changes (if permitted) Depending on your role, you may:

    • create, edit, or delete entries, or

    • use import flows with mandatory dry-run.

If your role does not allow editing or importing, action buttons may be hidden or disabled.

Guards and empty states

If a required prerequisite is missing (for example, Client Type), the module may display:

  • an empty state explaining what is required, or

  • a guard screen preventing further actions.

Follow the on-screen instructions to continue.

Navigation tips

  • Always check breadcrumbs before applying changes.

  • Verify the selected client type and module context.

  • Use Export before making changes.

  • If you feel lost, return to Home and re-enter the module.