What are Collections for?

For onboarding - 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 onboarding is very important for a number of reasons: a positive onboarding 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 rollout. 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.