Managing Contents in AppNavi

AppNavi Contents help you provide users with in-application guidance, instructions, announcements, and access to business processes. You can create different types of content, organize related guidance, and publish it to the applications where users need it.

This guide explains which content type to use, how to create and configure it, and how to verify that it is available to the intended users.

Choose the right content type

Choose the content type based on what users need to do or learn. For example, use an announcement to communicate a release update, a route to explain how to use the updated application, and a collection to group that route with other related processes.

Before you begin

Make sure you have the following:

• Access to the AppNavi Portal or Avatar authoring functions, depending on the content type.
• Access to the application for which you are creating guidance.
• The required authoring permissions.
• A clear title, description, and intended audience for the content.
• The required application and content configuration, including the appropriate language and publication settings.

Some authoring actions are available through Avatar in the target application, while others are performed in the Portal. The relevant sections below explain where to start.

1. Create and manage Routes

What is a Route?

A Route guides users through an application by highlighting interface elements and presenting instructions at each step. Routes can support onboarding, software rollouts, infrequently performed tasks, and automated workflows.

Create a Route

1. Open the application for which you want to create the Route.
2. Open the AppNavi widget (Avatar).
3. Log in using your author account.
4. Open the Routes section from the AppNavi menu.
5. Open the Route menu and select the option to create a Route.
6. Configure the basic details:
   • Language: Select the language in which the Route will be created.
   • Icon: Choose an icon that helps users recognize the Route.
   • Title: Enter a short, meaningful title.
   • Description: Explain what the user will accomplish by following the Route.
   • Start Mode: Choose the appropriate mode, such as Learning or Automation, where supported by the Route configuration.
7. Add the required steps using the step recorder.
8. Configure the instructions and settings for each step.
9. Test the Route before making it available to end users.
10. Save the Route and publish it through the applicable content-management workflow.

Add and configure Route steps

A Route consists of steps that guide the user through a task. Select the step type that matches the interaction you want the user to perform.

To add a step:

1. Open the Route Planner.
2. Select the option to capture a step.
3. Choose the appropriate step type.
4. Move the recorder over the relevant application element.
5. Capture the element when the highlight appears.
6. Enter a meaningful title for the captured element.
7. Add instructions, images, videos, links, or other supported tooltip content as needed.
8. Apply the captured step to the Route.

You can also add an informational step when you need to explain something without capturing an application element.

Capture the correct application element

AppNavi supports two capture methods:

• CTRL: Quickly capture the highlighted element.
• SHIFT: Open a selection of elements in the highlighted area so you can choose the specific element to capture.

Use SHIFT when several elements overlap or when the default capture does not select the intended element.

If the wrong element is captured, record it again before continuing. Use meaningful titles for captured elements to make the Route easier to maintain.

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.

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.

Working with Captures

Captures are a simple way to specify alternative display elements for a step. If the main element captured for a step is not found, the AppNavi algorithm searches for an alternative element. This mechanism is very suitable for pages with a responsive function, for example. On these pages, the design, i.e., the arrangement of the elements, often changes as the screen resolution changes. With AppNavi captures, the same route can be used for different design arrangements on a page.

How captures work

Follow the steps to learn about how captures work.
On Route Planner, click on Step and then on Search under the Details section
Scroll down and find a section named "Captures"
Here you will see the already captured step along with three options: the "Add Capture" (plus icon), “Test & Train Capture”, and the "Record Again" icon.

1. Add captures
Clicking on Add captures (plus icon) will add an optional capture to the already captured element.
In the event that the element is not found, it will move to the newly added capture element.

If the element structure of a page is adapted to different resolutions (responsive website), certain elements may no longer be found by AppNavi or are simply no longer present on the page. In this case, the same route can still be used by adding additional captures to the steps. AppNavi then searches the list of captures one by one and checks whether the element can be found.

To know about Deviation and Weighting, click here Deviation and Weighting

2. Record Again
Recording the same elements helps the user improve the element identification mechanism on dynamic pages.

Case 1: The user has selected the wrong element and wants to overwrite it with a different one.
Record Again will help authors capture page elements again and replace the previous capture.
If an author captures an element on the page but decides to change it, use the "Record Again" option to capture a different element on the same step.

Case 2: The user wants to improve the search mechanism on dynamic pages.
If the user captured an element before and added details on that step, but because of the dynamic page, the captured page element is changed, it will not be able to find that again.
For this purpose, the user can record the element without losing the added details from that step. The AppNavi Engine then automatically adjusts the attributes so that they work in both cases. You can check the change in the Element Properties window.

To know more about Test and Retrain capture, click here Test and Retrain

The following table shows how an element property changes when it is re-recorded.

Attributes that disappear completely from the dome remain as attributes in the list of element properties but are deactivated.

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

Step Settings

Each step within a route has different settings. By using AppNavi most of the settings are predefined for you already. Settings vary with step type.

1. Enabled This setting is available for all types of steps. It allows a user to activate or deactivate a step within a route. By default, it is "On" (enabled) but on switch "Off" (disabled), the step will be deactivated and it will be skipped when the route is processed.

2. Tooltip Moveable This setting is available for all types of steps. If this option is active your end users will be able to drag your tooltips around.

3. Show Overlay This setting is available for all types of steps. By default, it is set as "On" to show the page overlay on the step. A user can decide if the page overlay on a step is to be shown or not.

4. Back button enabled This setting is available for all types of steps except the first and last steps. In some situations, a back button doesn't make sense. This is the case when the UI element for the previous step is not on the screen anymore. Just imagine the user was inside a modal dialog, which is now closed. In this situation, you can deactivate the back button because clicking "Back" won't take you anywhere. a user can specify the target step on the back button. By default, it will be the "Previous Step". A user can update it to any step except the last step.

5. Set Focus This setting is available for all types of steps except the "inform" step. It focuses element being shown. If set focus is enabled on a text field, a cursor will be shown indicating a focus on the other hand, If we disable set focus, it will not show a cursor.

6. Alternative Step This setting is available for all step types. By default, it is "Off". When enabled, the end user can select an alternative step, which will be executed if the original step element is not found. In certain situations, an element may be missing due to dynamic content changes, conditional visibility, or navigation differences. Enabling this setting ensures that the workflow continues smoothly by executing the alternative step instead of failing due to a missing element.

7. Automation This setting is available for all types of steps. By default, it is "Off". Switch "On", to reload the page before the next step will be searched. In some situations, screens can have different states: A menu can be open or not, a tab can be visited or not, etc. If you want the screen to be more predictable a reload of the page can be helpful before the next step is searched. In such a case you can use this setting.

8. Reload page This setting is available for all step types except the "Inform" step. By default, it is "Off". when enabled, a delay field will appear, allowing the end user to set a time duration before automation starts. Once the duration is set, clicking the "Automation" button will trigger the route to automatically play through all the steps without manual interaction.

9. Prevent Redirect When a step is captured, AppNavi stores the URL of that step. On processing the route, there is a mechanism to check the current URL and compare it with the one where the step was captured. In this case if the "Prevent Redirect" is enabled or On the route will start immediately - no matter if both URLs match or not whereas if the "Prevent Redirect" is disabled or Off, there will be a redirection if the URLs do not match.

10. Prevent PointerDown event This setting is available for all types of steps except the "inform" step. By default, it is set as "Off". In case you do not want a click inside your tooltip to be considered as a click inside the page, just switch it to "On". A very common example is when you are showing some element inside a menu that is hidden when the user clicks "somewhere" inside the page. Also a click on "Next" would be a click on "Somewhere".

11. Check Overlap During route run, if anything overlaps target element, AppNavi would consider that the target element has been hidden and it has to find the element again. However there are times when the target element is overlapped by the non-visible element which for the eyes of the user nothing is overlapping the target element.

    Therefore to overcome this issue, we have added a new option (Check Overlap, by default set to true) that allows user to disable overlap check, so that AppNavi will allow target element to be overlapped.

12. Destination Our search algorithm is hustling a lot. As soon as the route is continued, it searches for the next step. However, in some situations, you may not want it to do so. For example, if the next step is on the next page, you can tell AppNavi to wait until the page is loaded again before proceeding with the search. This setting will be available to all step types except the last step. There are two options,

    1. "Same page" (default): AppNavi will start searching immediately after proceeding from the last step
    2. "New page": AppNavi will wait until the new page or tab has loaded

13. Event binding For click steps, AppNavi will bind an Event on the highlighted element. If clicking this element won’t proceed with the Route, three other bindings can be used.

    1. Element (jQuery)
    2. Element (Javascript)
    3. Document (jQuery)
    4. Document (Javascript)

14. Relative Location This setting is available for all types of steps. In this field, the user can define the precise URL path for this step. This can be used in connection with the "Prevent redirect" option.

15. Tooltip position AppNavi is checking the space for the tooltip on the screen before it is rendered. Doing so checks the position of the found element and checks if the tooltip with its size will fit on certain positions considering the screen's top, right, bottom and left edges. However, there might be situations in which you want to precisely put a tooltip in a certain position.

    This setting is available for all types of steps except the "inform" step. By default, "Auto" is selected, In case you are not able to find a position that will always (in all screen resolutions etc.) make sense, you can make the tooltip movable.

Test a Route

Before publishing, use the Route testing options in the Route Planner.

1. Select Test Route to check the Route and its instructions in normal mode.
2. Check that each step highlights the correct element.
3. Verify that the instructions are clear and that the user can proceed to the next step.
4. Check that clicks, inputs, and navigation behave as expected.
5. If automation is configured, enable the relevant automation settings and use Test Automation.
6. Correct any failed or unreliable steps and test again.

Expected result: The Route guides the user through the intended process and behaves as expected in the selected mode.

2. Create and manage Pins

What are Pins?

Pins highlight specific elements within an application and can offer actions such as starting a Route, displaying an announcement, or showing a hint.

A Pins set groups one or more Pins for an application.

Create a Pins set

1. Open the target application and launch Avatar.
2. Log in with your author account.
3. Open the Pins section in the AppNavi menu.
4. Select the option to create a Pins set.
5. Enter the Pins set details:
   • Language: Select the language for the Pins set.
   • Title: Enter a short, descriptive title.
6. Add Pins using the Pins recorder.
7. Configure the action and content for each Pin.
8. Test the Pins set.
9. Save the Pins set.

Languages available for content creation are managed through the Portal.

Add a Pin

1. Open the Pins set in the Pins Planner.
2. Select the option to add a Pin.
3. Choose the appropriate Pin type:
   • Start route: Start a selected Route.
   • Display announcement: Show an announcement.
   • Display hint: Display a helpful explanation.
4. Move the recorder over the relevant application element.
5. Capture the element.
6. Apply the captured Pin to the Pins Planner.

Configure a Pin

The available options depend on the Pin type.

For a Start route Pin, configure the following:

For a Display announcement Pin, select the announcement that should appear.

For a Display hint Pin, configure the tooltip content and relevant display settings.

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 and save Pins

1. Select Test Pins in the Pins Planner.
2. Verify that the Pin appears on the intended element.
3. Select the Pin and confirm that the configured action works.
4. Check the display type, position, and URL-related settings.
5. Save the Pins set when the result is correct.

Expected result: The Pin appears in the intended location and performs the configured action.

If the Pin cannot find its element reliably, review its capture and search settings. For responsive or dynamic pages, additional captures may help AppNavi identify the element when its position or layout changes.

Increase Pins Reliability

In SAP and other dynamic applications, elements can move to a different position after a page refresh. If a Pin becomes unreliable, retrain the capture and move the weightage slider towards Text. This helps AppNavi identify the element based more on its text than its position, which improves reliability when the element stays within the same parent container but changes position. For more information, please check AI Search

3. Create and manage Posts

What are Posts?

Posts provide information relevant to a specific application. Users can access them through the Posts area of the AppNavi widget.

Use Posts when users need reference information or updates that they can open while working, rather than a step-by-step walkthrough or a modal announcement.

Create a Post

1. Log in to the AppNavi Portal.
2. Open Guidance and navigate to the content area.
3. Open the Posts section.
4. Select the option to add a Post.
5. Enter a meaningful title and description.
6. Save the Post.

Use a title that clearly communicates the subject. Keep the description focused on what users need to know or do.

Translate a Post

Posts can be translated manually or by using the available automatic translation functionality.

1. Open the Post you want to translate.
2. Select the option to add a new language.
3. Choose the required language.
4. Enter or generate the translated text.
5. Review and edit the translation for accuracy.
6. Save the changes.

The language in which the Post was originally created is its primary language. Automatically translated content can also be edited manually.

Copy, move, or delete a Post

Open the Post list and use the relevant context-menu action:

• Copy: Create a copy in one or more selected workspaces.
• Move: Move the Post to one or more selected workspaces.
• Delete: Remove the Post when it is no longer needed.

Check the destination workspace before copying or moving content. Verify the result in the relevant workspace after the operation.

Verify a Post

1. Make sure the Post is assigned or published to the intended application.
2. Open that application.
3. Open Avatar and log in if required for your test.
4. Open the Posts area.
5. Confirm that the Post appears with the correct title and content.

Expected result: The intended Post is available in the Posts area for the application to which it has been assigned.

4. Create and manage Announcements

What are Announcements?

Announcements display important information in a modal window within an application. They are useful for communicating changes, updates, alerts, or other messages that users should notice.

Announcements are considered read when the announcement text has been visible in the visible area of the announcement window for at least one second. A read announcement is not shown again under the default behavior unless a new version has been created.

Create an Announcement

1. Log in to the AppNavi Portal.
2. Open Guidance and navigate to the content area.
3. Open the Announcements section.
4. Select the option to add an Announcement.

1. Choose how to start:
   • System Templates: Start with a predefined template available across tenants.
   • My Templates: Start with a tenant-specific template that your team has saved.
   • Start from Scratch: Create the announcement without a template.

1. Edit the announcement title and content.
2. Add supported media, such as images, where needed.
3. Review the message for clarity and accuracy.
4. Save the announcement.
5. Use the publishing option to publish it to the intended application or applications.

System and tenant-specific templates provide a starting layout. Review the content before publishing, even when using a template.

Control how often an Announcement appears

You can configure the display behavior through the content-management settings when publishing or republishing the Announcement.

The documented options include:

To change the display rule:

1. Open Guidance in the Portal.
2. Navigate to Applications.
3. Select the relevant application.
4. Open Manage Content.
5. Locate the Announcement.
6. Select it and choose the republish action.
7. Change the display rule in the publishing dialog.
8. Complete the publishing action.

AI Powered Announcement Generation

The AI Powered Announcement feature helps users to create high quality, structured announcements quickly by using AI assistance while still keeping user in full control of the final content. This feature enables announcement creators to generate professional announcement text using AI.

Step-by-Step Flow

1. Open the Announcement Editor
2. Click on “Generate with AI”
3. Enter optional custom instructions in AI content generator
4. Submit your request
5. AI generates announcement text (text-only)
6. AI generates announcement with images if it's mention in instructions
7. Review the generated content in preview mode
8. Choose to:
   • Edit the content
   • Accept it
   • Reject it
9. All interactions are automatically recorded in the history panel - AI content generator dialog.

Custom Instructions

You can guide the AI output by providing additional context or instructions, such as:

• “Make this sound exciting”
• “Keep it short and formal”
• “Highlight key benefits clearly”

These instructions are combined with the system defined announcement context to produce more relevant results.

Conversation History Panel

A dedicated panel on the right hand side of the editor displays the last 5 interactions between user and the AI.

It Includes:

• AI-generated suggestions
• User's actions (Accept / Reject)
• Iterative changes and refinements

Example Scenario

User wants to announce a new feature release.

• User open the editor and click “Generate with AI”
• Add instruction: create an announcement for a new feature "announcement updates" with image
• AI generates a polished announcement draft
• User make changes in few lines and accept it
• The interaction is saved in the history panel for future reference

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.

Verify an Announcement

1. Open the application to which the Announcement was published.
2. Check that the Announcement appears as expected.
3. Review the title, message, and media.
4. Confirm that the display frequency matches the configured rule.
5. If the Announcement does not appear again, check whether it has already been considered read and whether its display settings explain the behavior.

Expected result: The Announcement displays in the intended application according to its configured display behavior.

5. Create and manage Collections

What are Collections?

Collections group related Routes into an organized set. They help users find the right guidance for a department, application area, job role, or learning scenario.

Use a Collection when several Routes belong together and users would benefit from finding them in one place.

Create a Collection in the Portal

1. Log in to the AppNavi Portal.
2. Open Guidance.
3. Navigate to the content area.
4. Open the Collections section.
5. Select the option to create a Collection.
6. Enter a meaningful title.
7. Add a description explaining which processes or Routes the Collection contains.
8. Save the changes.

Assign Routes to a Collection

1. Open the Collection.
2. Navigate to its Route section.
3. Select the option to add Routes.
4. Choose the Routes you want to include.
5. Select Assign to confirm the selection.

The documented limit is 25 Routes per assignment operation. If you need to assign more Routes, repeat the process as appropriate.

Choose Routes that serve a shared purpose. A clear Collection title and description help users understand which guidance they should open.

Create a Collection from Avatar

1. Open Avatar.
2. Navigate to Collections.
3. Open the context menu.
4. Select Add Collection.
5. Continue in the Portal and complete the Collection creation steps.

Manage an existing Collection

Depending on the available actions and permissions, you can:

• Edit: Update the Collection title, description, or assigned Routes.
• Delete: Remove the Collection when it is no longer required.
• Copy: Create a copy in selected workspaces.
• Move: Move the Collection to selected workspaces.

Before deleting or moving a Collection, check that you are working with the intended item and destination.

Verify a Collection

1. Confirm that the correct Routes are assigned.
2. Confirm that the Collection has been published or made available as required.
3. Open the relevant application and AppNavi interface.
4. Locate the Collection.
5. Open it and check that its Routes are available.

Expected result: Users can find the Collection and access the Routes grouped within it.

6. Publish content to an application

Creating content does not by itself guarantee that users will see it. The content must also be published or assigned through the appropriate workflow.

AppNavi supports two publishing approaches:

Publish or republish content

1. Open the AppNavi Portal.
2. Select Guidance.
3. Open Applications.
4. Select the application you want to configure.
5. Open Manage Content.
6. Locate the required content type and item.
7. Select the appropriate publish, unpublish, or republish action.
8. Review the publication settings.
9. Configure the required display rules and target audience, where available.
10. Complete the publishing action.

The available options can vary by content type and publishing workflow. Use the relevant content section for type-specific instructions.

For more information, see Content Publication and Content Management.

7. Control which users see the content

AppNavi supports content segmentation so that users can receive guidance relevant to them. Depending on the configured setup, content visibility can be based on criteria such as user attributes, roles, or other available labels.

For example, a Route intended for Finance users should be configured and published so that it is available to the intended audience.

When configuring an audience:

1. Identify which users should receive the content.
2. Confirm that the relevant audience criteria or labels are available.
3. Configure the content's publication or audience settings.
4. Publish the content.
5. Test with a user who meets the criteria.
6. Test with a user who does not meet the criteria.

Expected result: The content is available to the intended audience according to the configured rules.

If the content is missing for a user, check the publication status, application assignment, and audience configuration before recreating the content.

8. Set the default language for new content

The default language for content created through Manage Content is determined by the language selected in the application's settings.

This applies to newly created:

• Routes
• Posts
• Pins
• Collections
• Announcements created from scratch

Configure the application language

1. Open the AppNavi Portal.
2. Navigate to the application's settings or edit page.
3. Select the required application language.
4. Save the application settings.
5. Open Manage Content for that application.
6. Create a new content item and verify its language.

Important behavior

• The application language applies to newly created content.
• Existing content retains its previously saved language.
• Announcements created from scratch use the application's default language.
• Announcements created from System Templates or My Templates retain the language of the selected template.

If new content uses an unexpected language, check the application's language setting and whether the content was created from a template.

Related documentation

• Content Publication — publish, unpublish, and republish content.
• Content Management — understand content management and workspace handling.
• Agent Triggers — configure triggers for Agents.
• Guidance — learn about AppNavi guidance capabilities.

Next step: Create a small content item, publish it to a test application, and verify its behavior as an end user before rolling it out more broadly.