The sub list feature in Applaud lets you display a list inside another list item. This is especially useful in HR scenarios where you need to show related records, such as an employee’s direct reports, a manager’s open tasks, or a project with its assigned team members.
To use the sub-list feature, your main list block must be based on a model that has a related model defined.
How the sub list feature works
- Each list item can show another list directly under the list item.
- The sub-list pulls data from a related model, keeping all information in context.
- You can style the sub list like other list blocks, with text, avatars, and actions.
For example, in an Employee Directory, a manager’s profile can show their direct reports:
Examples
Here are ways to apply sub-lists in HR use cases:
- Manager–employee hierarchy: Show each manager with a sub-list of their direct reports.
- Onboarding tasks: Display a new hire record with a sub-list of assigned tasks.
- Training programs: Show a course with a sub-list of enrolled employees.
- Leave requests: Show each employee with a sub-list of their pending or approved leave requests.
Best practices for sub lists
| Best practice | Why it matters | HR example |
|---|---|---|
| Keep sub lists short | Too many nested items can overwhelm users. | Show only active direct reports, not historical records. |
| Use clear labels | Helps users understand the relationship between lists. | “Direct reports” or “Assigned tasks” as sub list headings. |
| Make sub lists actionable | Add secondary actions so users can drill deeper. | “View profile” or “Approve leave” within the sub list. |
| Use sub lists for context, not storage | Avoid clutter by showing only related data that supports the main list item. | Training records shown only under an employee’s profile. |
| Avoid deep nesting | More than one level of sub lists becomes confusing. | Keep to one layer (manager > direct reports). |