Content Flow

AppNavi has a very simple but powerful content flow. This mechanism specifies how content is created by an author and how the content can then be made available to Anonymous users. Each content (routes, news, hotspots, etc.) is initially assigned to a tenant. By the logical subscription level, it is also possible to distribute content to different areas of responsibility. Furthermore, a content can be assigned to several applications. For example, if a route is assigned to an application, it is first visible to the author in the avatar and can be edited. To make a content visible to all users, it must be published. Each time a content is changed, a new version of the content is created. When publishing a content, it is always published in the current version. If the content is subsequently changed, new versions are created again, but these do not change the existing publications.

The example shows how a content is changed over time. Immediately after creation, version 1 was published for app 1. After some changes, version 4 was published for App 2. App 1 still has version 1 at this point. It was not until version 6 that the content was republished for the App 1. At this point, the app 1 therefore has the latest version of the content. App 2, however, still has version 4.