Applications

What are applications for?

Single or multiple applications
Applications are the basis for AppNavi. AppNavi can support (almost) any browser-based application. To make AppNavi available in an application, it must be created in the Applications section of the Customer Portal. Within a tenant, any number of applications can be created.

Data of an application
An application is stored in AppNavi with the following information:

1. Avatar image: Users can add an image or update the image to their added application by using css option in custom theme
2. Application name: Add a name to your application.
3. URL: Add the main URL of your required application.
4. Pattern: Click on this field after entering the URL, this will fill the field with the proper pattern. Use * at the end of the link to apply it on all pages.
5. Language: A User can select the language in which he wants to see AppNavi content. By default, AppNavi shows content in the browser's language. However, by selecting a language from the dropdown, the user can specify the language to show content in that selected language.
6. Avatar Position Avatar Icon will appear according to the selected position. The default position of the avatar icon is Bottom Left. This can be helpful for Applications which has a bottom toolbar or an area at the bottom left corner where user interaction can happen.
7. Avatar Visibility Select the visibility mode. There are two options,

• 1. Visible (default)
  2. Restricted mode
     When "Restricted Mode" is selected, the Restriction Keys option gets enabled which the user can use to specify up to 5 keys. In Restriction Mode, AppNavi can be visible by setting one Nf the Restriction Keys in the localStorage in appnavi_visibilityRestrictionKey.

8. Code Execution Mode: AppNavi supports two kinds of code executions,
   -1. Dynamic (eval) which is the default
   -2. Inline.

• Dynamic (eval), the code is directly run.

• In Inline mode, all the custom code is placed inside the script tag and injected into the head element. This approach though makes the process clean but has the disadvantage of the restrictions by the CSP policies.
  So it is advised to use Dynamic (eval) in all cases unless its causing issues, only then the user can switch to Inline mode.

  9.Select Authentication Mode:
  Users at the client side have the option to select from two login modes, and they also have the flexibility to choose multiple modes simultaneously, providing them with a range of login choices.

1. Username/Password
2. Single Sign On

10. Application Disable: If we switch on this toggle, this will disable the application and the avatar will not display on the application. By default, it is set as disabled. Therefore, the avatar will display on the application. Using this option, the user can temporarily disable the Application so that AppNavi doesn't run on the URL.

For each application, you can decide which of the content elements (routes, posts,...) will be displayed in the application.