Skip to main content

An Introduction to Applications

Markus Taylor avatar
Written by Markus Taylor
Updated this week

Who This Is For

This article is for Navgar users who operate, monitor, or manage business processes that have been published as Applications. It is also useful for flow creators who want to understand how their Flow Templates translate into Applications for end users.

Real-World Scenarios

Applications are commonly used when organizations want to provide operators with a clean, simplified interface for running standardized processes, such as:

  • HR onboarding workflows

  • Missing luggage reports

  • IT hardware requests

  • Safety incident reports

  • Compliance verification steps

In all these situations, operators should only see what is necessary to run the process—not the underlying subflows, routing logic, email templates, or builder-level components. Applications solve this by offering a streamlined, operator-friendly view.


What Are Applications?

Navgar Applications are published versions of Flow Templates designed for operational use. When enabled, an Application appears in the Applications module as a card inside its assigned group, making it easier for operators to locate and launch processes without navigating the complexities of Flow Templates.

Applications inherit the same organizational structure and permissions as Flow Templates, but they hide all builder-only components such as:

  • Subflows

  • Email templates

  • Script steps

  • System logic

Only flows explicitly toggled as Applications are shown.


How to Enable an Application (Flow Creator Action)

Flow creators can turn any Flow Template into an Application using a simple toggle.

Steps:

  1. Open the Flow Template.

  2. Navigate to its Settings panel.

  3. Enable the “Application” toggle.

  4. Assign it to the appropriate Application Group.

  5. Save and publish your changes.

Once enabled, the flow becomes visible in the Applications module for permitted users.


Navigating the Applications Module

Application Cards

Each Application appears as a card displaying key operational information.

You will see:

  • Application Name

  • Information (i) — reveals its underlying description

  • Running Instances — count of active flows

  • My Tasks — tasks currently assigned to you

  • Unread Chats — conversations requiring attention

  • Statistics Button — available when metrics exist

  • Launch Button — to start a new instance


Launching an Application

Click Launch to begin a new instance of the process.
Users of the application will be guided/assigned through the steps defined by the flow creator.


Viewing and Managing Instances

Selecting an Application takes you to a table of all its instances.

Standard Columns (available for every Application)

  • Progress

  • Status (On track, Completed, Cancelled, etc.)

  • Chat (instance-level conversation icon)

  • Flow Instance Name

  • Launched At

  • Concluded At

  • Current Owners (who currently holds open tasks)

  • Task Completion Ratio (e.g., 0/6, 6/6)

  • Alerts (such as overdue, or cancellation option for active flows)


Custom Fields

Following the standard columns, Applications typically include custom fields defined by the Flow Template creator. These fields differ based on the process’s operational needs.

For example, in a Missing Luggage Application, you might see:

  • Agent

  • Passenger First Name

  • Passenger Last Name

  • Bag Serial ID

  • Brand

  • Description

  • Flight ID

These fields are unique to each Application and help operators track all data collected during the process.


Filtering, View Options, and Exports

Column Visibility

Use the Columns button to show or hide any column in your table.

Filters

You can filter on any column—for example:

  • show only “On track” items

  • filter by specific Agent

  • filter by bag brand or ID

  • date filtering on Launch or Concluded times

Density Control

Switch between:

  • Compact

  • Standard

  • Comfortable

This adjusts spacing for better readability.

Export

Export the table at any time for reporting or auditing purposes.

Expand Tasks

Toggle Expand Tasks to display all tasks associated with open instances, allowing you to see where each active flow currently sits.


FAQ

Do Applications replace Flow Templates?

No. Flow Templates are for creators; Applications are for operators. They work together.

Can any flow become an Application?

Yes—if the creator enables the Application toggle.

Do Applications show subflows and email templates?

No. These are intentionally hidden to reduce clutter.

Will different Applications have different custom fields?

Yes. Custom fields depend entirely on the needs of the underlying process.

Did this answer your question?