Navigation Model

This page explains the structure of FT Configs UI. It also shows how to move between pages safely.

When to use it

Use this page if you are new to the UI or if you feel lost in a module.

Header

The header is always visible. It contains:

  • the product name and logo,

  • breadcrumbs with your current location,

  • the language switcher,

  • the user menu with Settings, About, and Log out.

Use the breadcrumbs to return to a higher level.

Page structure

Most pages have the same structure:

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

  • a toolbar with actions and filters,

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

  • optional side panels or dialogs for details and editing.

The same structure helps you move between modules.

Home page

The Home page is the entry point after you sign in. It has five application areas:

  • ACS: Auto Configuration Server settings. This is the only available area now.

  • Angular Console: 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 and export and section edits. Planned for future versions.

The Home page shows the four planned areas and marks them as unavailable.

Work in a module

Most modules use the same steps:

  1. Select the required context. Some modules need a client type or a similar context before they show data.

  2. Narrow the data. Use search fields, filters, or tabs to find the entries you need.

  3. View the details. Click a row or card to open the details.

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

  5. Apply changes, if your role allows it. You can create, edit, or delete entries. You can also use an import with a required dry-run.

If your role does not allow editing or importing, the UI can hide or disable the action buttons.

Guards and empty states

If a required context is missing, the module can show one of these:

  • an empty state with a text about the missing context,

  • a guard screen and no further actions.

The required context is, for example, the client type. Follow the instructions on the screen.

Navigation tips

  • Check the breadcrumbs before you apply changes.

  • Check the selected client type and module.

  • Click Export before you change data.

  • If you feel lost, return to Home and open the module again.

Related pages