Contents

Routes

Use any application immediately. Without training, without questions. With routes! Imagine that is sitting in front of an application for the first time - or the application has changed significantly. How can you operate it effectively and efficiently without training or asking colleagues or the help desk? The answer: by means of routes. Routes guide you step-by-step through the application and provide you with exactly the information you need to perform each step. AppNavi guides you through apps as safely as a navigation system guides you through the city.

Typical use cases for "Routes" Routes typically support in the following scenarios:

  • Onboarding: Introduction of new employees
  • SW rollout: Provision of new software / major release
  • Infrequent UseCases: support for infrequently performed operations.
  • Automation: acceleration in the execution of tasks (RPA)

Creating a Route

  1. Open AppNavi widget (Avatar) First, open the application for which you want to create a route. Please note that this application has also been added to the customer portal, and the AppNavi widget appears on the application, widget position can be changed. Now click on the AppNavi widget to open the AppNavi menu.

  2. Log in to the widget

    • Click on the Guide logo in the opened AppNavi menu.
    • To login, click click setting Icon.
    • Now click on the "Login" button.
    • Enter your login "Email address" and "Password'' in the login screen.
    • Confirm with "Login".
  3. Start the route creation

    • After you are logged in, click on the route icon in the AppNavi menu bar. • Now click on the "..." and "+" icons to initiate the route planner.

  1. Fill basic details
  • Language: User can select preferred language from language section, so the route will appear in that language (languages are added and selected from portal side according to the requirement of user)
  • Icon: Choose a speaking icon for the route.
  • Title: Give the route a very short, meaningful title. This title will appear on the front of the route tile.
  • Start Mode: User can select mode to play route, by default it will be in learning mode. Learning mode means that user will play route manually and Automation mode means route will be played automatically once done automation setting on each step.
  • Publication Status: Routes have two status type i.e. Publish and unpublish, it will be displayed here.

Now give the route a meaningful description. This description appears as soon as a user moves over the route tile (back side of the tile).

  1. Initiate the step recorder

    If you want to add steps to your route, you can choose between two step types:

    • Capture step:
      • click on + icon
      • click capture steps
      • A step recorder dialog will open
  2. Select the appropriate type in the step recorder

    User can drag-and-drop the step recorder to any place in your application so that it does not interfere with the recording of your route. Select any action type from the menu by clicking on the appropriate step type icon.

  • Show:
    This highlights an element on the screen to explain it. No direct interaction is made with the application. Via "Next" in the tooltip, the user gets to the next step.
  • Left Click:
    With the "Left Click" option, the user is prompted to perform a left click on the selected element directly within the application in order to proceed to the next step. There is no "Next" option in this case.
  • Right Click:
    Analogous to the "Left Click" option, the "Right Click" option prompts the user to perform a right click on the selected element directly in the application in order to proceed to the next step. There is no "Next" option in this case.
  • Edit:
    The "Edit" option prompts the user to enter an input or make a selection from a list or table.
  • Press Enter:
    The "Enter" option prompts the user to press the "ENTER" key. This may be necessary, for example, after entering a search term in a search field.
  • Hover:
    With the "Hover" option, it is sufficient for a user to hover over an element to get to the next step.
  1. Capture steps

Capture a step means AppNavi records exactly which element a step refers to. Its smart algorithm ensures the element can still be found even if it moves or changes, reducing maintenance to a minimum.

You can capture elements in two ways:

  • CTRL key (default): Quickly captures the step without extra adjustments.
  • SHIFT key: It fine-tune the step by choosing from a detailed path.

Capture with CTRL:
Select the step type in the step recorder.
Move your mouse over the application to the element you want to record.
As soon as the colored frame appears around the desired element, capture the element by pressing the CTRL key.
The recorded element now appears directly on the step recorder. Assign a meaningful title to this element directly to simplify editing in the planner.

Capture with SHIFT:
Select the step type in the step recorder.
Move your mouse over the application to the element you want to record.
As soon as the colored frame appears around the desired element, capture the element by pressing the SHIFT key.
A dialog appears with the different elements of the selected area: Select any element that you want to capture.

  • click on the img tag to capture an img element only, or
  • click on the div tag to capture a specific division of that element, or
  • click body to select the whole page, or
  • click html to select the whole html of that specific page.
  • The recorded element now appears directly in the step recorder. Assign a meaningful title to this element directly to simplify editing in the planner.
  1. Cancel, Save, or Discard Steps

While creating or modifying a route, you can manage steps at any time:

Cancel Step Capturing:

  • Start the step recorder and select a step type.
  • Move your mouse to the element you want to capture. A colored border appears.
  • To cancel the capture, press ESC. AppNavi will return to the step recorder without saving the element.

Save or Discard Captured Steps:

  • After capturing a step, it appears in the step recorder.
  • Click Apply to save the steps and add them to the route planner.
  • Click Cancel to discard the captured steps without saving.
  1. Adding and Editing Steps

    You can add, edit, delete or reorder steps using the step recorder or route planner.

    To Add a Step in the Route Planner:

    • Hover over the line between two steps until the “+” appears.
    • Click the “+” and choose:
      • Capture Step: Opens the step recorder to capture more steps
      • Inform Step: Adds a step with an empty tooltip in the Details section.
  2. Step options

  • Live Edit:
    It will display the step in the play mode, so the user may edit it similarly to how it's done in the route planner.
  • Copy step:
    It will copy each detail of that step, including text, images, videos, links, connected routes, etc. It will also copy it in all the selected languages.
  • Delete step:
    The step can be deleted. Please note that the step is deleted directly after selecting the delete option without a confirmation prompt.
  • Move up:
    To change the order of the steps, the selected step can be moved upward.
  • Move down:
    To change the order of the steps, the selected step can be moved downward.
  1. Testing Routes and Automation

User can test the steps in your route in two ways:

Test Route: Runs the captured steps in normal mode. Each step and its tooltip are displayed in the application.

Test Automation: Runs the captured steps in automation mode with the same behavior.
For Automation, user has to activate toggle of Automation enabled from step settings.

  1. Tooltip Designer

    In the Route Planner, the Tooltip Designer allows you to add details for each step. Using the Froala editor, user can include text, media (images or videos), links, and even connect other routes, making it easy to provide clear instructions and rich information for every step in your route.

For more Route details :


Pins

Pins allow you to highlight specific elements within an application and provide users with helpful actions such as starting a route, showing announcements, or displaying hints. This guide explains how to create, edit, and manage Pins in AppNavi.

Pins creation

Once you have successfully logged in, your initials will appear in the thumbnail of the menu and you will be able to use authoring functions such as adding Pins ("+" icon).

Pins are part of a Pins set. The Pins set can consist of any number of Pins within an application.

  • After you are logged in click on the "Pins" icon in the AppNavi menu bar.
  • Now click on the "+" icon to initiate the Pins planner.

Note:
The Pins icon in the AppNavi menu bar only appears while you are logged in as an author in AppNavi. This allows you to create and manage Pins. Users (they cannot log in) will see the Pins directly in the application, but not in the AppNavi menu.

In case you cannot see the Pins icon although you are logged in, you need to activate this feature first in the app within the customer portal.

Pins properties

The Pins planner consists of 3 sections:

  • General:
    Information about the Pins set such as the language of the Pins set and title.
  • Pins:
    List of all Pins that belong to a Pins set.
  • Details:
    To edit the selected Pins in terms of headlines, texts, images, videos, links and iframes - as well as detailed settings on Pins level such as search.

Now fill in the Pins set properties:

  • Language:
    Select the language in which you want to capture the Pins in that Pins set (in a later step you can translate the texts into any other language). The languages can only be added from the portal.
  • Title
    Give the Pins set a very short, meaningful title. This title will appear in the Pins menu beside the respective Pins set.

The Pins menu now displays the Pins sets that have been created. The number of Pins per Pins set is displayed - as well as the options for editing and deleting a Pins set.

Initiate the Pins recorder

If you want to add Pins to your Pins set, you have to initiate the Pins recorder:

  • Click on the "+" icon in the Pins menu.
  • Click on the "+" icon in the "Pins" section of the Pins planner.

Now the Pins recorder will open in your application. Using the Pins recorder is analogous to using the step recorder in the route planner.

Select the appropriate type in the Pins recorder

You can drag-and-drop the Pins recorder to any place in your application so that it does not interfere with the capturing of your Pins.

Select any Pins (action) type from the menu by clicking on the appropriate Pins type icon.

  • Start route:
    Use this option if you want the user to be able to start a route at this point.
  • Display announcement:
    Use this option if you want the user to see an announcement at this point.
  • Display hint:
    Use this option if you want the user to see a hint at this point.

Capture Pins

"Capture a Pin" means, that the relevant element to which a Pins refers, is precisely captured. The intelligent AppNavi algorithm ensures that the element is still found even if the properties of an element change (e.g. search field is no longer at the top left but at the top right). The maintenance of the pin is thus reduced to an absolute minimum.

The capture element can be done in two ways: by pressing the CTRL key (default behavior) or by pressing the SHIFT key. The CTRL option directly captures elements without allowing you to fine-tune the captured path. With the SHIFT key, you can fine-tune the captured path as you get a detailed path which you can select from.

Capture with CTRL :

  • Select the Pins type in the Pins recorder.
  • Move your mouse over the application to the element you want to capture.
  • As soon as a sea-color frame appears around the desired element, capture the element by pressing the CTRL key.
  • The recorded element now appears directly in the Pins recorder. Assign a meaningful title to this element directly to simplify editing in the planner.

Capture with SHIFT :

  • Select the step type in the Pins recorder.
  • Move your mouse over the application to the element you want to capture.
  • As soon as a sea-color frame appears around the desired element, capture the element by pressing the SHIFT key.
  • A dialog appears with the different elements of the selected area: select any element which you want to capture (see image below).
    • click on img tag to capture an img element only - or
    • click on div tag to capture specific division of that element - or
    • click body to select whole page - or
    • click html to select whole html of that specific page.
  • The captured element now appears directly in the Pins recorder. Assign a meaningful title to this element directly to simplify editing in the planner.

Cancel Pins capturing

You can cancel the creation or modification of a Pin at any time. The changes or additions made will then not be saved.

  • Initiate the Pins recorder as described above.
  • Select a Pins type.
  • Move your mouse to the element of your application you want to capture.
  • A sea-color border appears. If you want to cancel the capturing press the ESC key.
  • AppNavi returns to the Pins recorder without capturing the element.

Adding more steps and editing

There are numerous ways to customize a Pins set: Pins can be tested, deleted or changed in sequence in the Pins planner. The step recorder just allows to delete the recorded Pins.

Edit in Pins recorder

  • Click with the right mouse button on the desired Pins in the Pins recorder.
  • Select the option "Delete" to delete the captured Pins.

Edit in Pins planner

  • Click with the right mouse button on the desired Pins in the "Pins" section of the Pins planner.
  • Select one of the options that appear - or just edit the Pins in the "Details" section.

Pins options

  • Test Pins
    All Pins of a Pin set will be tested.
  • Delete Pins
    The Pins can be deleted. Please note that the Pins are deleted directly after selecting the delete option without a confirmation prompt.
  • Move up
    To change the order of the Pins the selected step can be moved upwards.
  • Move down
    To change the order of the Pins the selected step can be moved downwards.

Add a step in the Pins planner

  • Click on the "+" icon in the "Pins" section of the Pins planner.
  • When the Pins recorder appears, capture Pins as described above.

Editing a Pins right in the application

Besides the possibility to change a Pins in the Pins Planner, Pins can also be changed directly in the application.

  • Click with the left mouse button on the Pins you want to change.
  • Choose one of the options in the dialog that appears.

The following options are available here:

  • Start Pin: The Pins are executed immediately (start route, display hint or announcement).
  • Edit Pin: The Pins planner opens and the Pins to be edited are selected.
  • Delete Pin: A security question appears asking if the Pins should really be deleted. The deletion can be confirmed with "OK" or canceled with "Cancel".

Note:
These options are displayed only to logged-in authors. If an end user clicks on a Pin, the corresponding action is executed immediately.

Save or discard Pins

As soon as you have captured a Pin with the Pins recorder, it appears in the Pins recorder. With the option "Apply" you can take over the captured Pins. The Pins planner appears and shows these Pins. If you want to discard the captured Pins, click on the "Cancel" button.

Configure "Start a route" Pins

In the "Details" section of a Pins there are 2 tabs: Content (default) and Settings. While the "Content" tab is intended for the basic definition of a Pins, further, more detailed settings can be made in the "Settings" tab.

Content

  • Title: Give the Pins a meaningful title.
  • Select route: Select the available route that a user will take through when clicking these Pins.
  • Select step: Select the step, where the route should start when a user clicks on that Pin.

Content Settings

  • Style: There are two Styles available "Icon" (default) and "Frame". Icon as the name suggests shows only the icon on top of captured element while Frame lets you highlight the captured element with a sea-color border.
  • Display Type: This setting defines the visibility of pin in page. There are three types "Visible" (default), "Invisible" and "Hover". Visible always shows pin on the page. Invisible type hides the pin from the page (it will trigger the custom code events, but it will not start and track user interactions like starting a route when clicking). Lastly "Hover" the pin is only visible if we hover the captured element.
  • Positions: define where the Pins should appear "Top", "Bottom", "Left", "Right".

Search Settings

  • Consider path: This setting defines if the URL of the page will be considered or not. So in case the current URL does not match with the one when the Pins were captured, the Pins won't be shown.
  • Search mode: "Ai Search" (default), "Fuzzy Search"
  • Relative Path: Define the precise URL path for this step.

For more details of search, click here AppNavi Element Search

A Pin can be tested by clicking on "Test Pins". As soon as all settings are c

orrectly defined, the Pins can be saved by clicking on the "Disk" icon or canceled by the "x" icon (close).

Configure "Display announcement" Pins

Content

  • Title: Give the Pins a meaningful title.
  • Select Post: Select the available news that a user will see as an announcement.

The settings correspond to the settings for the Pins type "Start route".

Configure "Display hint" Pins

Content

The creation of the tooltip for the Pins type "Display hint" is identical to the design of tooltips within the route creation. Create a route

The settings correspond for the most part to the settings for the Pins type "Start route".

Captures Settings

Captures are a simple way to specify alternative display elements for a pin. If the main element captured for a pin is not found, the AppNavi algorithm searches for an alternative element. This mechanism is ideal for pages with responsive design, where the arrangement of elements changes with screen resolution. With AppNavi Pin Captures, the same pin can work across different designs on a page.

How Pin Captures Work

Follow these steps to manage captures for pins:

  1. In Pins Planner, select the pin you want to configure.
  2. Under the Details section, click on Search.
  3. Scroll down to find the section named Captures.
  4. Here you will see the main captured element for the pin along with three options:
    • Add Capture (plus icon)
    • Test & Train Capture
    • Record Again (camera icon)

Add Captures

Click Add Capture (plus icon) to add an optional capture to the existing captured element. If the primary element is not found, AppNavi will move to the newly added capture element.

Responsive pages often adapt their structure based on screen size, causing elements to shift or disappear. In such cases, the same pin can still function by adding additional captures. AppNavi searches through the list of captures one by one until the correct element is found.

To learn about Deviation and Weighting, click here: Deviation and Weighting

Record Again

Recording the same element helps improve the identification mechanism for dynamic pages.

Case 1: If the wrong element was captured, use Record Again to overwrite it with a new element.

Case 2: If the page structure changes (dynamic content), Record Again allows you to re-capture the element without losing the pin details. The AppNavi Engine automatically adjusts attributes for both old and new elements. Check updates in the Element Properties window.

To learn more about Test and Retrain Capture, click here: Test and Retrain

Delete Capture

If there are more than one capture, user has an option to delete any capture which is no longer required.

Test Pins

After the Pins set has been created completely or partially, it can be tested before or after saving. The test can be performed on the entire Pins set - or only on the selected Pins.

Test Pins set:
"Test Pins set" can be initiated with the "Play" icon in the "Pins" section of the Pins planner. After the test is initiated, a window displays the test results.

380

Test results for the entire Pins set

Test a single Pins:
Select the desired Pins in the Pins planner, section "Pins" and click on "Test Pins". After the test is initiated, a window displays the test results.

Save or discard Pins set

Once all or part of the Pins set has been created, it can be saved. By saving, the Pins set becomes visible and modifiable for other authors of the same subscription. For end users, the Pins set becomes visible only after publishing.

  • You can save Pins set by clicking on the "Upload" icon in the upper right corner of the route planner.
  • If you want to cancel the Pins set creation or discard the changes, you can click on the "x" icon.
  • If you want to open the pins on the portal then you can click on the context menu.
  • A confirmation popup will appear asking to save or discard changes
    • On selecting "Save" it will save the whole content.
    • On selecting "Discard" it will discard all changes and will not save them.

Now it is a good time to publish your Pins set. The procedure is largely analogous to the publication, republication or un publication of a route.
Publish, republish or unpublish a route


Collections

Collections in AppNavi are designed to group multiple routes into organised sets, making it easier for users to find and execute related processes. This feature helps structure guidance for various scenarios—such as grouping processes by department, application area, or business function—ensuring a more intuitive and efficient user experience.

What are Collections for?

For on boarding - or preliminary Collections
Collections allow bundling routes into logical groups. On the one hand, this can be used for the onboarding of new employees; on the other hand, it can also be used to map learning scenarios.

Optimal onboarding experience
Optimally designing on boarding is very important for a number of reasons: a positive on boarding experience maintains and increases an employee's attachment to the company. Secondly, a high level of efficiency and effectivity can be achieved much more quickly. To achieve this, App-Navi can be used on the intranet. There, routes for core processes can be summarized in chapters. For example, "Everything about projects", "Report absences" or "Orders". On the very first day, employees can execute relevant processes without having been trained for even 1 minute. This makes the new employee happy - and reduces the burden on colleagues for collections.

Preliminary collections for very complex applications
If very complete applications are rolled out, it may make sense to offer hands-on collections directly in the system. For this purpose, collections(chapters) can be created so that the user can experience and learn the application practically along a collections storyboard even before the actual roll out. The routes created for this purpose can be used in two ways: first, they can be referenced to a learning system and thus enable playful learning without changing real data. The same route can be assigned to the productive system - without further adjustments - and is then available for productive use in the "Routes" area. In order to keep an eye on the learning progress, a check mark indicates whether the route of a learning chapter has already been completed.

Functionality of Collections

This can be used for the onboarding of new employees, and it can also be used to map learning scenarios. If very complex applications are rolled out, collections(chapters) can be created so that the user can experience and learn the application practically along a training storyboard even before the actual roll out. The routes created for this purpose can be used in two ways: first, they can be referenced to a learning system and thus enable playful learning without changing real data. The same route can be assigned to the productive system - without further adjustments - and is then available for productive use in the "Routes" area.

There are four basic functionalities of every content, so do its in collection. User can make changes in collection for e.g.: changing title, description and route assignment, delete collection, make multiple copies of collection and move collection to other subscription.

  • Edit Collection
  • Delete Collection
  • Copy Collection
  • Move Collection

Create Collection

There are two ways to create collection.

  • Portal
  • Avatar (Client side)

Steps to create Collection via Portal

  1. Login into portal
  2. Navigate to the Guidance tab
  3. Go to content tab under guidance
  4. Click on collection card to add a collection
  1. Click + Icon to create new collection from main card or from listing page.
  1. Fill the Title field
  2. Fill the Description field
  3. Click save changes

Steps to create Collection via Client Side

  1. Open Avatar
  2. Go to Collection
  3. Click context menu and select Add Collection.
  4. It will redirect to portal to create collection.
  5. Follow same steps, as mentioned above.

Steps to Assign Route

  1. Go to the Route section
  2. Click + Icon
  3. Select the routes, maximum limit is 25
  4. Click Assign

Assignment of Collection

Collections can be assigned to multiple applications, it will be visible to authorized user only if it’s assigned to any application, if a collection is published than it will be visible to guest and authorized user both.

Steps for Assignment of a collection

  1. Click the arrow adjacent to "Save Changes"
  2. Click "Save and Publish"
  3. A dialect will open, choose application.
  4. Click "Publish"

Collection at Client Side

User can play collections at client side, through avatar user will select any one collection and play the route which is required. Collection will give details that how many routes have been played by showing a tick mark. It also notifies with a congratulations message, when user complete all the routes in the collection.

Translate Collection

User can translate collections into multiple language through translate option given in collection. User can select primary language and its dialect. For further information about translation, you may go through the following links.

Useful Link:
https://docs.appnavi.eu/docs/content-language-translation


Posts

With posts, information can be sent in a very targeted manner. If a user opens the AppNavi widget in an application, he only sees information in the posts area that concerns this application. Posts reach the employee at exactly the right point in the work process: at the right time, at the right place - and for the right employees.

Steps to create Posts

  1. Login into Portal
  2. Navigate to the Guidance tab
  3. Go to content tab under guidance
  4. Click on Posts card to add a post
  1. Click on + icon
  2. Add Title, description
  3. Click Save

Post Translation

Posts can be translated manually or automatically. Manual translation allows translation into any number of languages. For automated translation, > 28 languages are currently available. Of course, automatically translated texts can also be edited manually. Primary Language is one with which the user has created the post. Users can select the option "New Language", to translate it in different languages.


Delete Post

User can delete posts if its require to from post table through context menu.

Copy Post

User can copy posts to one or more work spaces through "copy" option from context menu in the table.

Move Post

User can move posts to one or more work spaces through "move" option from context menu in the table.


Announcements

Announcements offer a user-friendly way to communicate important updates to users through a modal dialogue. These messages are informative posts that appear on-screen, helping teams to share news, updates, or alerts within the application environment.

Overview of Announcements

Announcements are displayed as modal windows and serve as short, informative messages or updates. They are visible only once per user by default, but this behaviour can be adjusted through the Manage Content Settings to one of the following:

  • Once.
  • Every time.
  • Daily (once per day).
  • Weekly (once per week).
  • API call through custom code When multiple announcements are available, they appear side by side within the same modal window.

Steps To change the visibility of the content

  1. Go to guidance tab.
  2. Navigate to applications tab.
  3. Select the specific application and click on manage content
  4. In the manage content all the section displayed e.g. routes, post, pins, Announcement.
  5. Select the content and click on the republish button
  6. .In the dialogue change the display rules.

When is an announcement considered read?

AppNavi has an intelligent mechanism that registers when a user reads an announcement entry. If it is considered read, it is not displayed to the user again (exception is that a new version has been created). An announcement is considered read when a user has displayed the text of a post item for at least 1 second in the visible area of the announcement window.

Create Announcement

Announcement is created via portal, user can add a new announcement or assign already created announcement to an application. Here are the steps to create a new announcement

  1. Login to portal.
  2. Navigate to the Guidance tab.
  3. Go to content tab under guidance.
  4. Click on Announcement card will open a announcement page.
  1. Click on plus icon present on top right.
  1. Hover to the tile the plus icon will appear click on the icon will open the dialogue to create announcement instantly.

  1. In the dialogue User can create the announcement with the system design templates or create with scratch.
  1. Add content of your announcement and click save changes.
  2. Click on drop down arrow present on save changes button.
  3. Select save and publish.
  4. Select applications where User want to publish the announcement.

Announcement Template Gallery

The Announcement Templates feature enables efficient creation, reuse, and management of announcement content within the AppNavi portal. It supports both system-provided and user-defined templates, allowing consistent and rapid communication across applications.

Types of Templates

System Templates:
Predefined templates available globally across all tenants. These templates are editable but can be used as a base for editing and publishing announcements.

User-Defined Templates (My Templates):
Custom templates created and saved within a tenant. These templates are editable, reusable, and only visible to users within the same tenant.

Note: Templates are optional. If no template is selected, announcements can also be created directly using the Start from Scratch option.

Accessing the Announcement Section

To access the announcement feature:

  1. Navigate to the Guidance tab.
  2. Open the Contents section.
  3. Select the Announcements tile.
  4. On the Announcement listing page, click the three-dot menu (⋮) to view available actions:
  • Add – Create a new announcement
  • Manage Templates – Open the template gallery
  • Refresh – Reload the announcement list

Creating a New Announcement

To create an announcement:

  1. Select the Add option from the three-dot menu
  2. A dialog box will appear with the following creation options:
  • System Templates: Use a predefined layout
  • My Templates: Select from previously saved tenant-specific templates
  • Start from Scratch: Begin with a blank layout
  1. Selecting any template opens the Announcement Editor with pre-filled content.
  2. Modify the title, description, media, and tooltips as required.
  3. Images can be added using the Media Library or by uploading a custom file.
  4. After editing, choose to Save or Publish the announcement. Published announcements will appear within the associated application interface.

Managing Templates

Accessing Template Management

To manage templates:

  1. From the Announcement page, click the three-dot menu (⋮).
  2. Select Manage Templates to open the Template Gallery.

Creating a New Template

  1. In the Template Gallery, click the three-dot menu (⋮) and choose Add.
  1. The Edit Template view will open.
  2. Provide the following details:
  • Template Title
  • Template Description
  • Preview Image (optional – select from Media Library or upload)
  • Add content using tooltips, text fields, and images
  1. Click the Save as Template button to store the new template.

Editing or Deleting a Template

  1. In the Template Gallery, each template includes a three-dot menu (⋮) with options to:
  • Edit: Open the template in the editor for modification
  • Delete: Permanently remove the template from the tenant’s gallery

Important Notes

  • System Templates are available to all tenants but cannot be modified permanently.
  • User Templates are only visible within the same tenant and can be edited, updated, or deleted.
  • Templates and announcements are independent. Editing an announcement will not affect the original template.
  • Templates are stored in the system under a specific content type (announcement template Gallery).
  • There is no retention limit for templates—they remain until deleted manually.

Announcement View

When announcement is assigned to an application, it should now display on application side.

  • Open application
  • The announcement published will be displayed

Republishing Announcements

It is possible to make changes to existing announcements. When announcement item is republished a new version is created. If the user has already viewed the original announcement, the change will still be displayed again with new version.

Connected Routes in Announcements

Connected routes can be used to connect routes with each other. Within each step the author can integrate possible connections to other existing routes. End users get the option to select from one or more routes they can jump to. Doing so it is not only possible to connect routes from within the same application – users can also jump to routes within other systems. This allows to provide a set of sub routines which can be combined in an intelligent way. AppNavi has created the possibility to create announcements including connected routes.

On clicking the connected route icon, a dialogue will appear to select the routes available on the tenant. Users can select multiple routes to add in the announcement.

On selecting the routes, the steps can be selected from drop downs. Users can select from which step the route has to be started.


Preview of Announcements with Connected Routes

The routes added in the announcement will be added in dialogues. The routes can be sorted using drag and drop. The routes can be separated from the dialogue as well. The user can also change the width of the dialogues as per their design requirements.

Add / Remove Connected Routes

In order to add or remove any connected route from the announcement preview, users can hover on the dialogue top right and a context menu will appear with a edit button. On clicking the edit button, the add connected route dialogue will open in which users can select or deselect the connected routes to add or remove the routes.

Check out more details for connected routes here.

Working with connected routes

Add connected routes to a step

Connected routes can be used to connect routes with each other. Within each step the author can integrate possible connections to other existing routes.

End users get the option to select from one or more routes they can jump to. Doing so it is not only possible to connect routes from within the same application – users can also jump to routes within other systems. This allows to provide a set of sub routines which can be combined in an intelligent way.

  • Open the respective route in edit mode by hovering the route tile and clicking on the "Edit" icon
  • Select any of the steps
  • Click in the tool tip text area of this step in the "Details" tab
  • Now click on the option "Connected routes"
  • In the dialog that opens, the available routes are now displayed (grouped into the available apps).
  • Select one or more routes. You can recognise the selected routes by the coloured "Check" icons.
  • Click on "OK" if all appropriate routes are selected - or cancel the process by clicking on the "x" icon. Open the dialog for connected routes
  • Select appropriate connected routes

Connected routes are displayed to end users

Sorting order for Connected Routes

The routes can be sorted according to any order using the drag and drop function present in the planner view above. Once the user has added the connected routes in a listing manner then they can drag and drop the connected routes in any order in the planner view and the same order will be displayed to end users once the route has been published.

For example the above connected routes added in this dialogue can be saved as New route 01 to New route 05 in ascending or descending order just by dragging the connected route upwards or downwards according to the users requirement of sorting.

Default Language for Contents

Overview

The default language for content creation is determined by the language selected at the Application level by going to application edit page and selecting language. This applies when users create content directly from Manage Content within a specific application.

Language at Application Level

How Default Language is Applied

When a user navigates to Manage Content of a specific application and creates any of the following:

  • Route - created from Avatar planner
  • Post
  • Pin - created from Avatar Planner
  • Collection
  • Announcement

The newly created item will automatically use the language selected in the application settings.

Manage Contents


Creating New Content

Impact on Existing Content

The default language applies only to newly created content.

  1. Existing content is not affected.
  2. If a route, post, pin, collection or announcement is already saved in a particular language, it will continue to appear in that language.
  3. This ensures no changes or overrides occur on previously created items.

Announcements – Case

New announcements created from Manage Content → Start from Scratch , will only use the default language defined at the application level.

Important Note

The default language does not apply when:

  1. Selecting System Templates
  2. Selecting My Templates

These templates already contain predefined content and therefore retain the language they were originally created in.