Revamped Applications Page Layout

Overview

We have revamped the layout for the case management applications details page. This document guides you through the different sections, what data they display, what purpose they serve, and the conditions under which they are displayed or hidden.

Prerequisites

• Access to HV One Dashboard with a role allowed to view the applications tab.

Purpose & use case

Who is this for? Everyone.

When should this be used? When finding it difficult to navigate through the application details page on case management.

Deep dive

Core concepts

There are four primary sections on the application details page in case management:

• Overview — A quick glance of the most important and relevant information about the application.
• Timeline — Know the sequence of events in the user's journey.
• Recordings — Dig deeper into every action the user took during their onboarding journey.
• All Modules — The most verbose details of the user's journey (our old friend).

TODO

Screenshot: Applications details page showing the four primary sections (Overview, Timeline, Recordings, All Modules). (Pending migration from Notion.)

Technical details & behaviour

Overview Tab

Purpose: Glance through the most important information about the application without spending too much time looking into it.

When is it displayed?

• When the application is auto approved — users see a success message.
• When the application is auto declined or needs review AND failure reasons are configured along with the contributing modules which led to the failure.
  • Users see only the modules that led to the auto-decline or manual-review state — helpful to convey what went wrong and needs to be fixed.

TODO

Screenshots: Overview tab for auto-approved and auto-declined/needs-review applications. (Pending migration from Notion.)

Timeline Tab

Purpose: Go through the actual sequence of API calls a user made throughout their journey, different times they dropped off, reached an end state, or resumed.

When is it displayed? Always.

Deep dive:

• Shows the events of the transaction in chronological order.
• Displays all the API calls made by the user as part of the transaction.
• Displays all end states in the user journey.
• Displays all times the user dropped off and resumed.
• Displays the SDK version the user resumed on.
• API calls display a flag if they failed (if response summary config is configured).
• Clicking on an API call item displays the data for the API call.
• API call items display their status — Pass, Fail, Retake, etc.
• End-state items display the failure reason (if configured).

TODO

Screenshot: Timeline tab showing a chronological sequence of API calls, drop-offs, and end states. (Pending migration from Notion.)

Recordings Tab

Purpose: Display the session recordings useful to dig deeper into each action taken by the user during their onboarding journey.

When is it displayed?

• If session recording is enabled for the client.
• If there are more than one recording available.

Deep dive:

• All available recordings are displayed.
• By default, the user lands on the latest recording.
• Webview is currently not captured.
• It has to be explicitly enabled for clients to view the recordings.
• Currently, by default, only HV users can see the recordings.

TODO

Screenshot: Recordings tab listing available session recordings. (Pending migration from Notion.)

All Modules Tab

Purpose: View all the details of the transaction — API calls made throughout the user journey, inputs, and user details.

When is it displayed?

• Always.
• If there were no visible API calls made, a fallback screen is shown conveying that there is no data available.

Deep dive — three primary panels:

Left panel

• Lists all the different modules the user attempted throughout their journey.
• Clicking on any module brings the corresponding module card into view and highlights it.

Center panel

• Displays all the different details about the application.
• The Application Details / summary section at the top displays metadata, inputs, user details, and some media for the application.
• For HV users, it also displays the Finish Transaction payload if any FT call was made.
• Below Application Details are the different API module cards, rendered per the configurations.

Right panel

• Displays the current status of the application.
• For manual-review status, Approve and Decline buttons are shown.
• Has a comments section for reviewers/admins to add comments.
• If application assignment is enabled, the assignee details are shown.
• If CPR state reset is enabled, it is also displayed.

TODO

Screenshots: All Modules tab left panel (module list), center panel (application summary and module cards), and right panel (status, actions, comments, assignee). (Pending migration from Notion.)