Internal service catalog

Anne leads an HR team and oversees a project that functions as an internal employee service desk. She wants to create an internal service catalog.

Here’s a breakdown of how the cascading select field levels might be structured based on the provided context:

Workflow:

• Anne asked the admin to create a custom multilevel select field named “Service Catalog”
• The Multilevel Select field has levels:

Service Categories

• Technical Support
  • Hardware Issues
    • Laptops
    • Desktops
  • Software Issues
    • Apps Error
      • App XYZ
        • Crashes
        • Features
        • Slow performance
      • App ABC
        • Crashes
        • Features
        • Slow performance
    • Software Installation
  • Network Issues
    • Connectivity Problems
    • VPN Setup
• Project Management
  • Project planning
    • Requirements Gathering
    • Resource Allocation
  • Execution and Monitoring
    • Task Tracking
    • Status Reporting
  • Project Closure
    • Deliverable Handover
    • Post-Implementation Review
• Development Services
  • Web Development
    • Frontend Development
    • Backend Development
  • Mobile App Development
    • iOS Development
    • Android Development

For example, Alice is tester in Technical Support team and works on features in ABC apps. So she chooses Technical Support -> Software Issues -> App ABC -> Features .

Benefits:

• Improved Usability: Users can easily find and select the relevant options without being overwhelmed by numerous fields.
• Enhanced Readability: A single cascading select field with logical groupings makes the form more readable and reduces cognitive load.
• Time Efficiency: Employees save time by quickly locating the necessary options, thus improving productivity and reducing frustration.
• Cost Savings: By streamlining the process, the company reduces the time and resources spent on navigating and filling out complex forms, leading to cost savings.