Asset UI Validation and Feedback
Summary
Asset UI validation is client-side and minimal: the form requires asset Type and asset Name. Feedback is delivered through inline errors, confirmation modals, toasts, and empty states. The compatibility endpoints are tenant-scoped; fine-grained validation and authorization are not enforced at the backend layer the UI calls.
Audience
- Developers implementing validation and feedback.
- QA engineers verifying enforcement layers.
- Support engineers interpreting errors and toasts.
- Security engineers assessing enforcement boundaries.
Reference Content
Validation matrix
| Screen | Field/action | Rule | UI enforcement | API/domain enforcement | Error presentation | Blocking | Source path |
|---|---|---|---|---|---|---|---|
| Employee request form | Asset Type | Required | Yes (client) | Requires confirmation (tenant-scoped compat, not role-authorized) | Inline "Asset type is required." | Yes | UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsx |
| Employee request form | Asset Name | Required | Yes (client) | Requires confirmation | Inline name-required error | Yes | UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsx |
| Admin create form | Asset Code | Uppercase transform | Yes (client, forced uppercase) | Requires confirmation | n/a (transform) | No | UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsx |
| Admin create form | Type / Condition | Fixed option set | Yes (fixed select options) | Requires confirmation | n/a | No | UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsx |
| Workspace | Approve / Reject | Confirmation before action | Yes (modal) | Compat status endpoint | Modal + toast | No | microservices/src/asset-service/Api/AssetCompatEndpoints.cs |
UI-only vs API-backed vs domain vs missing
- UI-only: required Type/Name checks, uppercase code transform, fixed dropdown option sets, confirmation modal.
- API-backed: status change, request creation, and delete are executed against compatibility endpoints.
- Domain: full asset domain rules (status set, conditions) exist in the backend but are not surfaced or enforced through the UI form beyond the subset shown.
- Missing: no client-side cross-field validation beyond Type/Name; backend role authorization at the compatibility layer is not present (tenant-scoped only) — classified Requires confirmation for domain-level enforcement.
Feedback mechanisms
- Inline field errors ("Asset type is required.", name required).
- Confirmation modal ("Approve Asset Request" / "Approve Asset").
- Toasts: "Asset request submitted.", "Asset issued.", "Asset rejected.", "Asset deleted."
- Empty state: "No assets" ("No asset requests or assignments found.").
Source References
UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsxmicroservices/src/asset-service/Api/AssetCompatEndpoints.cs
Related Articles
See Also
Keywords
validation, feedback, toasts, inline error, confirmation modal
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly