We have currently separated into 3-different business entities. To improve the Move Requests Center so you can quickly see which Business (or Business Unit) each person belongs to—without drilling into every record—especially during peak onboard/exit periods.
Proposed Change Summary
• Add a new header/column: Business
• Column position: between Description and Requester
• Data source: “User Allocations” — use the “Business” field if present; otherwise fall back to “Business Unit”
• Behavior: Display the employee’s current/active business at time of viewing; update dynamically if allocations change
• Goal: Reduce time spent opening individual requests during high-volume periods
Recommended Implementation Approach
1. Clarify data source and precedence
• Primary field: Business
• Fallback field: Business Unit (if Business is null)
• Edge cases: Multiple active allocations—deterministic rule needed (e.g., most recent effective date or primary flag)
2. Modify list view schema
• Insert the Business column between Description and Requester in the Move Requests Center grid
• Enable sorting and filtering on Business to batch actions by Business
• Allow column to be added to exports
3. Data retrieval logic
• Join/lookup User Allocations by Employee ID for current effective allocation
• Apply precedence: Business → Business Unit
• Cache lightly for performance, but refresh on list reload to reflect recent changes
4. UX considerations
• Tooltip/hover on Business to show source field and effective date (e.g., “Business via User Allocations, effective 2025-01-15”)
• If multiple allocations exist, show the chosen one and an icon indicating multiple—click opens detail
• Preserve column in saved views so teams can set “Onboards by Business” and “Exits by Business” views
5. Performance safeguards
• Use server-side filtering and pagination to avoid slowdowns for large queues (20–40+)
• Retrieve Business in the main query to avoid N+1 lookups
• Index User Allocations on Employee ID and Effective Date
6. Data quality and governance
• Define a single system of record for Business
• Set validation to prevent empty Business and Business Unit for active users
• Add an exception state (e.g., “Unassigned”) with a reconciliation dashboard