Overall, Apty Insights functions in scope of 3 main steps:
1. define how certain use case is expected to be performed,
2. let users complete this use case without assistance, and
3. compare the expected actions versus real user behavior.
Each step of this scope is accomplished by the means of respective application component:
This tool is used to define the expected action pattern required to perform some Activity within the hosting application.
Details covered in this article.
Apty Insights Admin
Apty compares user behaviour with the expected action pattern defined via Apty Lens and analyses the application usage to help building effective strategies of system resource expenditure.
How Apty Lens Works:
Apty Lens can be accessed by installing Apty Studio that connects to the browser with an open hosting application for Admin user to create a blueprint of certain Activity or, in other words, the scenario for desired flow of user actions.
The essence of creating an Activity lies in going though all steps required to complete a specific use case and letting Apty Lens "remember" which user interface elements were involved in this Activity.
Example: Let's assume we are creating a new "Project" entity within some system. In order to do that a user performs the following actions:
- provide a name of the project in the Title field,
- define the expected in the Close Date field,
- select some option in the Type field,
- add the Stage of the project,
- provide a calculated Budget, and
- click Save to add project details to the system.
To save this pattern as an Activity in Apty Lens, admin user activates capturing, completes each step of the procedure, stops capturing, and saves the Activity. For Apty Lens capturing is essentially tracking which user interface elements were involved in the procedure and order in which steps were completed. Once saved, Activities can be access at the Apty Insights Admin > Scenario mapping and can be re-captured or deleted at any time.