Sone-166 Extra Quality -

For some users, SONE-166 serves as a key to accessing specific content. This has led to discussions about content categorization and the importance of efficient content retrieval systems.

Without more details, it's difficult to provide a specific answer about "SONE-166". If you have any additional context or clarification about the document, I'd be happy to try and help further! SONE-166

| # | Requirement | Details | |---|-------------|---------| | FR‑1 | | The client fetches a list of candidate actions for the current route ( GET /api/quick‑actions?view=dashboard ). The server returns an ordered array based on the scoring algorithm (role + usage + state). | | FR‑2 | Scoring algorithm | score = w_role * roleWeight + w_usage * usageCount + w_state * stateWeight . The weights ( w_* ) are configurable via an admin UI. | | FR‑3 | Overflow handling | If >3 actions are eligible, the 4th+ go into an overflow dropdown (⋯). The overflow is keyboard‑navigable (ARIA‑menu). | | FR‑4 | Action metadata | Each action definition includes: id , icon (FontAwesome/Material) , label , tooltip , url (or client‑side handler), disabledWhen (function or flag). | | FR‑5 | Permission gating | Server only returns actions the requesting user is allowed to execute. | | FR‑6 | Telemetry | Each click on a Quick‑Action fires an event ( quick_action_clicked ) to the analytics pipeline (incl. userId, view, actionId). | | FR‑7 | Graceful fallback | If the API call fails, the bar falls back to the static default set defined in the client bundle. | | FR‑8 | Responsive design | Horizontal layout on ≥768 px, collapsible vertical list on smaller screens. | | FR‑9 | Admin configuration UI | A simple CRUD page under Settings → Quick‑Actions where admins can: • Add new actions (choose icon, label, URL, required role) • Re‑order actions (drag‑and‑drop) • Set weight values for the scoring algorithm | For some users, SONE-166 serves as a key